Fix instance typing and cleanup typing

Description

Fixes 'InstantInTime' typing. Functions do not work as input checks.
Reformats the YailTypeToBlocklyTypeMap so that it is more readable.
Adds support for an opt_currentType that can be passed to YailTypeToBlocklyType. This is helpful for my current dropdowns project because we must get the Blockly types of the abstract (enum) type and the concrete type separately, then combine them.

@BeksOmega Have you tested this with malformed projects. For example, if I connect a false block into an instant slot, will the project fail to load due to Blockly's validation code when opening the project with this branch?

@ewpatton Yeah it breaks the project :/
But I really don't want to leave Instances untyped. Do you think it would be possible to write an upgrader for this? Or do some other workaround?

@BeksOmega Likely what we would want to do is patch the XML parser to handle when the connection is no longer valid by marking the block bad rather than throwing. Granted, bad code that exists now still won't work after this change because false isn't a valid instant in time.

@BeksOmega Maybe another thing, which doesn't require patching core, is instead to have the input check still be a function (a la the text block) that allows a connection if the workspace is loading and marks the block bad if the connection is bad.

@BeksOmega Maybe another thing, which doesn't require patching core, is instead to have the input check still be a function (a la the text block) that allows a connection if the workspace is loading and marks the block bad if the connection is bad.

That might be a lot better. Patching it was not going to be fun because it's patched in the other repo at the moment. Plus some other issues I had with maintainability.
So I'll look into that :D

So I looked into this and I remembered that the function type checking done with the text block isn't exactly a type check. It's an event listener which sets the type check.
My concerns with implementing this for InstantInTimes are twofold:

I'm not sure what event we would hook into to tell if the XML is loading or not. We would probably have to write a custom event, unless a custom event is already implemented.
The patch would be ineligant. The event listener would have to live on both the component_method and component_property blocks, separate from where the normal type checking code lives.

I'm not sure that the benefits of fixing this are worth the costs of implementation and maintainability. I'm happy to implement it! But I wanted to give you a chance to stop me before I did (┏－‿ ◕)┏

My recollection is that it's a connection check, which is enforced both when attempting to connect a block at runtime as well as validated at parse time (which is why it caused projects to fail to load). This situation, in effect, is the same thing. We have a situation where people could have connected invalid blocks because the check wasn't working as expected. Now we are changing the semantics so that the validation is enforced. When the workspace is loading, we can simply return true regardless, but mark the block bad if it wouldn't really succeed, and if the workspace has already loaded then we return false if the check fails.
So if we call the check something like Blockly.util.checkInstantInTime, we could have the check type be ["InstantInTime", Blockly.util.checkInstantInTime]. The function checks to see if the other check array includes "InstantInTime" and fails if it doesn't.

Sorry about that! Please disregard my previous comment. I was confused is because Blockly doesn't support function checks natively (at this time anyway). I searched for a place where App Inventor might have added this behavior, but I couldn't find one. I must have searched on github instead of in my local instance :/
Again, I'm really sorry about that. I've implemented the behavior you suggested. Currently it checks if the blocks are rendered to tell if they are being loaded from XML or not.
Tested and confirmed that old projects are upgraded correctly.

@BeksOmega No worries. Thanks for taking the time to implement this.


Find out why automatic baud rate switch requires two cycles

In some cases, the automatic baud rate switch seems to require two cycles instead of one:

It does work, but the additional cycle could be a symptom of a deeper issue.
Reported by @hubmartin.

I wasn't able to reproduce the double baud rate switch case. In my experiments, the first switch from 19200 to 9200 always succeeded.  Below is the output from one of my test. Note that the timestamps in the output below pretty much correspond to the timestamps above, so the difference is most likely not due to timing.
0.55 <D> LoRa syncTX: AT
0.60 <D> LoRa TX: AT
0.80 <D> NO response @9600
0.80 <D> Higher baudrate 19200
0.80 <D> LoRa syncTX: AT
0.86 <D> LoRa syncTX: AT+UART=9600
0.92 <D> LoRa syncTX: AT+REBOOT
0.92 <D> Lower baudrate 9600
1.92 <D> LoRa syncTX: AT
1.97 <D> LoRa TX: AT
2.17 <D> LoRa RX: +OK
2.17 <D> OK response @9600
2.17 <D> LoRa TX: AT
2.27 <D> LoRa RX: +OK
2.27 <D> Response: +OK

@hubmartin, if you still see this problem with newer firmware versions, please let me know.


[style] Fix the code style defined by class member variables in query…

Proposed changes
fix code style in QueryStatistics
Problem Summary:
The definition of class member variables in Doris BE usually starts with an underscore, but in the two classes NodeStatistics and QueryStatistics, class member variables are not defined in this form. Should this be modified to this form?
Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No)
Has document been added or modified: (No)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

@morningman Can this pr be merged?


Startup crash

SAM Startup Error
An error occurred on application startup. 'The invocation of the constructor on type 'SAM.ViewModels.MainWindowViewModel' that matches the specified binding constraints threw an exception.' Line number '20' and line position '10'.
errors.txt
log.txt
Everything was working a couple days ago, but now this error appears on startup

It was a problem on the steam/steamcommunity side. It's resolved now


Support cascade replication in get_stats_replication_delays

When monitoring a cluster with cascade replication the current query
fails with "get_stats_replication_delays". We can instead monitor the
diff using pg_last_wal_receive_lsn, this will emit metrics showing how
much replication delay the replica has compared to the upstream node
(but not relative to the primary instance of the cluster).

LGTM

@dflemstr PTAL


Show msg in UI when LoadBalancer work is not ready

React UI starts as soon as the app is launched but the LoadBalancer work takes time to spawn.
We need to show msg that LoadBalancer is not ready for the first few minutes. We can use a condition for dream_url.
cc: @pritamsoni-hsr

resolved!


vehicle identifiers not possible with UI

Describe the bug
After switching to 0.126.2 due to the PSA token issue the car was new created over UI.
The old yaml car entry was manually commented out. Over the UI there is no option to set the identifier for RFID chip.
Steps to reproduce

create vehicle over UI
try to add the value "identifiers" for the vehicle

Configuration details
network:
  schema: http
  host: *****
  port: 7070
log: warn
levels:
  cache: error
interval: 10s # control cycle interval
sponsortoken: *****
meters:
- type: template
  template: tesla-powerwall
  usage: grid
  host: *****
  password: *****
  name: grid1
- type: template
  template: tesla-powerwall
  usage: pv
  host: *****
  password: *****
  name: pv2
- type: template
  template: tesla-powerwall
  usage: battery
  host: *****
  password: *****
  name: battery3
chargers:
- type: template
  template: go-e-v3
  host: *****
  name: wallbox4
loadpoints:
- title: Garage
  charger: wallbox4
  mode: pv
  phases: 0
  soc:
    poll:
      mode: always
      interval: 30m
    estimate: true
vehicles:
  - name: Heidi
    type: template
    template: id
    title: Heidi # Wird in der Benutzeroberfläche angezeigt # Optional
    user: *****
    password: *****
    vin: *****
    capacity: 52 # Akku-Kapazität in kWh # Optional
    identifiers:
    - ID4

site:
  title: Mein Zuhause
  meters:
    grid: grid1
    pv:
    - pv2
    battery:
    - battery3
  residualPower: 100

tariffs:
  currency: EUR # (default EUR)
  grid:
    type: fixed
    price: 0.2837 # [currency]/kWh
  feedin:
    type: fixed
    price: 0.0634 # [currency]/kWh
mqtt:
  broker: *****
  topic: evcc # root topic for publishing, set empty to disable
  user: *****
  password: *****

Log details
no log

What type of operating system are you running?
Linux
Version
0.126.2

Ja, die Fahrzeug UI ist auch noch experimental. Haben wir aber natürlich auf dem Zettel.


Rename roles

Thanks Next one for Voucher.test.ts ?

@gfournieriExec You are right, here it is Update role names in Voucher.test.ts !


Noissue: Aurora perf test

I wrote quick perf test for you.
Perf test result is very good 👍 see the comment
But this is on my very fast computer. Also there might be some optimizations going on underneath. So this is not very certain but it's best what we have at the moment.
I would love to run this with randomized log content and in lambda environment with their basic vCPU.
Can you please organise this and include into codebase? I think this should be in some separate test. Otherwise this test will get very long once we add more check. Not sure how it should look like. But if transformation_full.py takes too long this might discourage devs from this test :D

I guess cleanup here would be to move this to maybe tests/perf by copying this specific test but with only chosen pytest param(s). So then you can run tests/unit and tests/perf separately locally. In travis job we would have to add tests/perf execution


Initial eslint config

I decided it was easiest to just start from eslint-config-standard and adjust to what I think we usually aim for.
Applying this to strong-supervisor requires a handful of fixes in the code and a few overrides to turn a bunch of errors in to warnings so we don't need to fix them all at once.
{
  "extends": "strongloop",
  "rules": {
    "comma-dangle": 1,
    "curly": 1,
    "new-parens": 1,
    "operator-linebreak": 1,
    "no-inner-declarations": 1,
  }
}

Can I see example output from the supervisor run?
I'm not a fan of warnings, I strongly prefer either an error, or inline lint exception in the code to mark a error as having been human verified to not be a problem.

The only ones left were ones with lots of occurances - hence making them warnings instead of errors so they don't all have to be fixed at once. We could just turn off the related rules entirely, though. I was just erring on the side of consistency.
><EMAIL_ADDRESS>lint /Users/ryan/work/strong-supervisor
> eslint ./

/Users/ryan/work/strong-supervisor/lib/capabilities.js
   40:10  warning  Missing trailing comma  comma-dangle
   49:10  warning  Missing trailing comma  comma-dangle
   59:10  warning  Missing trailing comma  comma-dangle
   60:8   warning  Missing trailing comma  comma-dangle
   61:6   warning  Missing trailing comma  comma-dangle
   73:10  warning  Missing trailing comma  comma-dangle
   82:10  warning  Missing trailing comma  comma-dangle
   83:8   warning  Missing trailing comma  comma-dangle
   84:6   warning  Missing trailing comma  comma-dangle
   96:10  warning  Missing trailing comma  comma-dangle
  105:10  warning  Missing trailing comma  comma-dangle
  115:10  warning  Missing trailing comma  comma-dangle
  116:8   warning  Missing trailing comma  comma-dangle
  117:6   warning  Missing trailing comma  comma-dangle
  130:10  warning  Missing trailing comma  comma-dangle
  131:8   warning  Missing trailing comma  comma-dangle
  132:6   warning  Missing trailing comma  comma-dangle
  145:10  warning  Missing trailing comma  comma-dangle
  146:8   warning  Missing trailing comma  comma-dangle
  147:6   warning  Missing trailing comma  comma-dangle
  160:10  warning  Missing trailing comma  comma-dangle
  161:8   warning  Missing trailing comma  comma-dangle
  162:6   warning  Missing trailing comma  comma-dangle
  175:10  warning  Missing trailing comma  comma-dangle
  176:8   warning  Missing trailing comma  comma-dangle
  177:6   warning  Missing trailing comma  comma-dangle
  212:27  warning  Missing trailing comma  comma-dangle

/Users/ryan/work/strong-supervisor/lib/config.js
   64:3   warning  Move function declaration to program root  no-inner-declarations
   67:3   warning  Move function declaration to program root  no-inner-declarations
   70:3   warning  Move function declaration to program root  no-inner-declarations
   73:3   warning  Move function declaration to program root  no-inner-declarations
  129:15  warning  Missing trailing comma                     comma-dangle
  173:25  warning  Missing trailing comma                     comma-dangle
  311:46  warning  Missing trailing comma                     comma-dangle
  316:23  warning  Missing trailing comma                     comma-dangle

/Users/ryan/work/strong-supervisor/lib/debug.js
  10:5  warning  Expected { after 'if' condition  curly

/Users/ryan/work/strong-supervisor/lib/expander.js
  11:3  warning  Expected { after 'if' condition  curly
  13:3  warning  Expected { after 'if' condition  curly
  15:3  warning  Expected { after 'if' condition  curly
  17:3  warning  Expected { after 'if' condition  curly

/Users/ryan/work/strong-supervisor/lib/log-writer.js
  18:42  warning  Missing trailing comma  comma-dangle

/Users/ryan/work/strong-supervisor/lib/metrics.js
  39:5  warning  Expected { after 'if' condition  curly

/Users/ryan/work/strong-supervisor/lib/options.js
   17:41  warning  '?' should be placed at the beginning of the line  operator-linebreak
   18:37  warning  ':' should be placed at the beginning of the line  operator-linebreak
   42:54  warning  '?' should be placed at the beginning of the line  operator-linebreak
  188:33  warning  Missing trailing comma                             comma-dangle
  190:21  warning  Missing trailing comma                             comma-dangle

/Users/ryan/work/strong-supervisor/lib/runctl.js
   36:24  warning  Missing trailing comma           comma-dangle
  185:7   warning  Expected { after 'if' condition  curly
  185:7   warning  Expected { after 'else'          curly

/Users/ryan/work/strong-supervisor/lib/targetctl.js
  49:25  warning  Missing trailing comma           comma-dangle
  89:7   warning  Expected { after 'if' condition  curly
  89:7   warning  Expected { after 'else'          curly

/Users/ryan/work/strong-supervisor/lib/tracer.js
  35:3  warning  Expected { after 'if' condition  curly

/Users/ryan/work/strong-supervisor/lib/watcher.js
  29:11  warning  Missing '()' invoking a constructor  new-parens

/Users/ryan/work/strong-supervisor/lib/watcher/cpu-profile.js
  27:5  warning  Expected { after 'if' condition  curly

/Users/ryan/work/strong-supervisor/lib/watcher/express-records.js
  7:21  warning  Missing trailing comma  comma-dangle

/Users/ryan/work/strong-supervisor/test/test-ws-control.js
  20:12  warning  Missing trailing comma  comma-dangle
  29:12  warning  Missing trailing comma  comma-dangle

/Users/ryan/work/strong-supervisor/test/test-ws-errors.js
  41:12  warning  Missing trailing comma  comma-dangle

/Users/ryan/work/strong-supervisor/test/watcher.js
  26:19  warning  Missing trailing comma               comma-dangle
  55:17  warning  Missing '()' invoking a constructor  new-parens

✖ 62 problems (0 errors, 62 warnings)

Those warnings are in addition to some small fixes for trivial things like indentation:
 bin/sl-run.js    |   6 ++++--
 bin/sl-runctl.js |  12 ++++++------
 lib/runctl.js    |  10 +++++-----

I don't think we should force comma-dangle, do you? I guess we can make it default, and turn it off for current repos.
I don't like operator-linebreak.
curly I'm 'meh' on - its not how we currently do things, I think it shouldn't be a warning, or at least I'd turn it off on current repos.
So, I'd suggest removing operator-linebreak, and making curly and comma-dangle mandatory, and then for all existing repos that don't use that style,customizing the eslintrc to disable comma-dangle and curly.
Also, this repo needs adding to waffle.I'll do.

also, I'd remove new-parens, I don't see why syntactically meaningless quotes should be forced into our js.

no-inner-declarations leaves me on the fence, too. if its valid V8, why warn? In strict mode, its even well defined now (though not v10). though I understand its historically a source of confusion for browsers, do we care? Maybe we should. I just like the code its warning about, it works perfectly and is clearly readable (lib/config.js:64). But if you think its a bad habit, I'll stop defining functions in conditionals.

Ah, I hadn't actually read the no-inner-declarations rule yet... I definitely don't like the idea of a function declaration being conditional. It doesn't make a lot of sense making something look block scoped in a language that doesn't do block scoping, so I find it confusing. Putting functions at the end of a scope at least suggests acknowledgement of hoisting, but putting them inside conditionals makes me wonder what intention the author was trying to convey with that choice... maybe I read some code too closely :-P
But if you're willing it give up that habit, I can move on :-)

I can give up inner declarations, and doing so is easier with a lint rule.

LGTM

Updated from the discussion so far, the strong-supervisor overrides are now even more reasonable:
{
  "extends": "strongloop",
  "rules": {
    "comma-dangle": 1,
    "no-inner-declarations": 1
  }
}


Global configuration

Is there a way to use a global env configuration with this? I don't want to pollute various directories with .env, and having a global ~/.autoenv.yaml or whatever would be much easier for me to track in my dotfiles repo and sync across computers.

Yes, I agree with @sirajulm, this is the best approach. Putting yaml logic (or anything like this) into autoenv would make the project too complex.

I was actually (somewhat lazily) waiting for this issue to be fixed to use autoenv (lazy in the sense that for now I just do things the old fashioned way). This way seems about as hacky as just forking autoenv and doing it the right way (again, though, I'm lazy, so I doubt it will happen).


Remove version: Jackett.Jackett version 0.20.4101

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.4101/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Missing Container

[Mon Jan 09 15:13:49.391760 2017] [:error] [pid 28104] [client <IP_ADDRESS>:3900] PHP Fatal error:  Uncaught PhutilMissingSymbolException: Failed to load class or interface 'Container': the class or interface 'Container' is not defined in the library map for any loaded phutil library.\n\nIf you are not a developer, this almost always means that a library is out of date. For example, you may have upgraded phabricator without upgrading libphutil, or vice versa. It might also mean that you need to restart Apache or PHP-FPM. Make sure all libraries are up to date and all services have been restarted.\n\nIf you are a developer and this symbol was recently added or moved, your library map may need to be rebuilt. You can rebuild the map by running 'arc liberate'. For more information, see:\n\nhttps://secure.phabricator.com/book/phabcontrib/article/adding_new_classes/ in /var/www/phabulous/vendor/phacility/libphutil/src/phutil_library_init.php:25\nStack trace:\n#0 [internal function]: __phutil_autoload('Container')\n#1 [internal function]: spl_autoload_call('Container')\n#2 /var/www/phabulous/vendor/symfony/symfony/s in /var/www/phabulous/vendor/phacility/libphutil/src/phutil_library_init.php on line 25

It's a know issue with libphutil, as the author does not believe in Composer!
You can read more here: Why doesn't Phabricator (or Arcanist, or libphutil) support Composer?
But using the Symfony's DEV Environment should work: if you are using bundled(etc/nginx/sites-available/phabulous.conf) NginX configuration then browsing to http://phabulous.localhost/app_dev.php/ should do it.
Currently I'm working on dropping libphutil as dependency in favor of using Guzzle with Conduit APIs directly. Any other ideas are appreciated.

I've tried that..I;m then prompted for a username/password.Is this supposed to be my Phab username passsword? We use google auth.
ThanksDave
  From: Mohammad Shokri<EMAIL_ADDRESS>
To: slashsBin/phabulous<EMAIL_ADDRESS>Cc: Dave Minogue<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Sent: Monday, January 9, 2017 4:28 PM
Subject: Re: [slashsBin/phabulous] Missing Container (#1)
It's a know issue with libphutil, as the author does not believe in Composer!
You can read more here: Why doesn't Phabricator (or Arcanist, or libphutil) support Composer?
But using the Symfony's DEV Environment should work: if you are using bundled(etc/nginx/sites-available/phabulous.conf) NginX configuration then browsing to http://phabulous.localhost/app_dev.php/ should do it.
Currently I'm working on dropping libphutil as dependency in favor of using Guzzle with Conduit APIs directly. Any other ideas are appreciated.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Default Username/Password is admin. Actually it does nothing(No Access-Level or similar concept) now.
It's not your phabricator username/password yet, phabulous currently only supports in-memory username/passwords. Supporting phabricator OAuth is the next step.

@JeanFred
First please note that Phabulous is no longer in active development nor is maintained anymore, so I'll recommend reconsidering using it.
Phabulous is a standalone Symfony web app, not a plugin/extension for phabricator. This means you should install it separately, then configure it to connect to your phabricator instance via bots.
Installation steps are located in the project's readme file here. We assume you already know how to install a Symfony app, if not follow their original guide here. There is also a sample NginX webserver config in the project repository, which will publish phabulous on your machine at http://phabulous.localhost, make sure to change it to match your setup(server name, the path to project, ...).
After setting up, there will be a new file located in "app/config/parameters.yml". Set your phabricator bot spec in this file to allow phabulous to connect to phabricator.
The idea of bots and usage of maniphest queries is to dynamically create phabulous chart data directly from phabricator, by first creating a sample maniphest query(let's say all the tasks currently defined in phabricator) and configure this query in phabulous to draw its chart from it, then you can change/update the query in phabricator(let's say filter it by a specific project) and refresh the chart to see it with new data.
Please also see my comment above.
Hope this was of any help.

@slashsBin Thank you for the answer!
Right, I do understand that this is a separate Symfony app. As I said, I run it using Docker containers (one for Nginx, one for PHP) separate from the Phabricator instance. If you are interested, you can see the setup at https://github.com/JeanFred/docker-phabulous.


docs: add example use cases for expansion cards

-added several examples of modern use cases for expansion cards and reasons for utilizing them

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

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

@wongco, everything LGTM! Thank you for helping us improve this section of the guide. Looking forward to your next contribution! :+1: :+1:


[QUESTION] Auth via securitySchemes

I need auth by securitySchemes and security. But I cant find any generate method for send API Key.

Could you please describe the problem?
If you need to send API key feel free to use interceptors
https://github.com/lejard-h/chopper/issues/122
Please provide a way how you want to do it using clear chopper or HTTP client, to understand how generation can help.

Thank u. Its works.


Multithreading not working

I don't know why. Multithreading is not working for me.
Yes, I see the CPU only go up by like 8%, but it's nothing like I've been seeing previous users CPU usage % in the 95%+
I have tried B1-B5, and Multithreading is just not working for me.
Windows 11 24H2 build, could be the problem. But, it's not working when selecting default, or even random thread count from 10 to 256.
I've tried CLI command and exe with Run As Admin ticked as well.
Also, when I use command like WindowsThumbsPreloader.exe -m 10(or any n) -r  it only opens the program and not preload. But if I remove the n from -m it works.

Hello, on Beta 5, do you have logging enabled? I'd like to check a log file to see if multithreading is actually being enabled properly or some other issue is occurring such as a specific file format causing a problem.

Yes, I see the CPU only go up by like 8%, but it's nothing like I've been seeing previous users CPU usage % in the 95%+

I also wonder what the disk usage is while running the program as multithreaded, since hard drives may max out their read speeds a lot faster than the cpu being fully utilized.
Also, this version of the program is a lot more optimized in multithreaded mode for CPU usage compared to previous forks which means the CPU usage will be a lot less while preloading much faster, which may cause drives to max out more easily or may otherwise cause a bottleneck elsewhere such as with Windows.

Also, when I use command like WindowsThumbsPreloader.exe -m 10(or any n) -r it only opens the program and not preload. But if I remove the n from -m it works.

As for the command line arguments, the number should be connected to the -m flag such as -m10 or -m:10 to set the number of threads.

Thanks, I will give that program a try.
Here's a log along with a screenshot of task manager. Looks like one CPU is being used while others are slightly used.

WinThumbsPreloaderLog_20240509.txt

It does indeed work on B5 for me

but as Mutahar said, check to see if you're not capped by something else. I also don't specify the number of threads at all when using -m.

@VL4DST3R
I'm leaning more into the fact that it could be very well it's my Windows 11 / 24h2 26100.1 build. As I'm also noticing, I'm having a memory leak issue with Icaros, consistently rises before it crashes.

@Mfarooq360
Just installed Windows 11 LTSC and one CPU is being maxed out while disk is also doing 100% but my thread count and cpu usage is nowhere near as @VL4DST3R

Have you tried to generate it on another divice? From your task manager it shows you're doing this on an usb external device, maybe it is just slow? Try on a regular sata/m.2 ssd and see if there's any difference in speed.

This is bordering o grasping at straws territory but all i can think of is:

Eyther you have one of the new E and P core config cpu - maybe it doesn't play nice with multithreading in that case?

Or secondly, try spinning up a windows 10 VM and see if it behaves differently there. I can help test the second one in the opposite config (w10 host with w11 vm) and see if it is indeed related to windows 11, although AFAIK Mutahar is also using w11 so it would make sense he tested on that first.

I am also wondering how this is happening as the logs state that multithreading is enabled with 255 threads, I initially thought that perhaps the program wasn't actually enabling multithreaded mode, but it seems to work for @VL4DST3R, so it may be Windows or perhaps Icaros is causing problems.

Eyther you have one of the new E and P core config cpu - maybe it doesn't play nice with multithreading in that case?

Looks like the CPU being used is an i9-10850K which uses regular cores, though this is also grasping at straws, but perhaps the affinity was manually set, though I doubt it.

he core affinity was manually set, though I doubt it.

Yeah, something like that may be at fault. Any funky settings within bios @beakwood?

Also another thing that came up while discussing this issue with Mutahar - what files are you generating thumbs for @beakwood?

Some good news. I did try another OS build. This time around, I tried a custom OS, Ghost Spectre. I have seen the CPU working a bit more and files were being processed at a good 30 files. Utilization jumped up to about 32% and CPU's we're slightly below half usage per this single directory.

I did come across the issue thread regarding @Mfarooq360 perhaps providing a BULK option. As this was what I was doing a majority of the time as well. For example, I have a folder with many subdirectories and including all the files is 354997 in total. When using winthumbpreloader on parent directory with -r, it only will process the files 3 at a time. But, as I suspect, it's limitation in the way winthumbs processes such large sum files and directories.
I also did a few other tweaks that may or may not have helped. For example, I disabled Storage Sense and unchecked delete temporary thumbnail cache. I also used winaero tweaker, and increased the thumbnail cache to 65535 KB/s.
Also, my extensions are as follows avif,bmp,gif,heic,heif,jpg,jpeg,mkv,mov,mp4,png,svg,ts,tif,tiff,webp
I am having a problem with backup, as I never tried it before and wanting to give it a go but error
`See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
 I'd like to see if there's any difference made, although it could also be an internal difference or problem within either Windows or the program.
I'd also like to know what version of Windows that the custom install is using (like 23H2) in case the problem is due to a more recent version of Windows.

@Mfarooq360 Windows 11 Pro 23H2 - 22631.3447
I currently have it preloading the large directory I spoke of regarding the 300K files, as it's at 70% now with 104450 files remaining. I'm not sure if I try preloading another directory will it slow it down the current preloading. But, I will most certainly grab a log for you.

@Mfarooq360 I tested another directory with 20+K files using debug log. Then, when it was done, I preloaded using 1100 files using the  All Logging, and it showed at least 20 thread was being used in the log.
WinThumbsPreloaderLog_20240511.txt

@Mfarooq360 Yes, it seems as though it's not able to preload recursively when it's more than 100 or so subdirectories.
Yesterday and Today, 300K files between 1500 subdirectories, that are not being backup & preloaded. It takes 6 hours to complete and at the end. Winthumbspreloader does not save a backup. I've been testing highlighting 15 directories at a time and right-clicking and winthumbs recursively. But, even just 15 highlighted doesn't seem to back up correctly either.
Which then raises the question, is there a way for winthumbspreloader, to start from top of the directory and work it's way down, one at a time?

@beakwood Sounds like the Windows cache reset issue which automatically resets the cache when it gets too big. I did notice that in the previous log you sent me, the backup appears to be 4.5GB in size so the cache is probably not doing too well. We're still looking for a way to prevent Windows from resetting the thumbnail cache, though so far we haven't found a concrete fix yet.

Which then raises the question, is there a way for winthumbspreloader, to start from top of the directory and work it's way down, one at a time?

I believe it does do that as it scans the subdirectories in a folder before moving onto the subdirectories of the subdirectories, which it then preloads in alphabetical order.

@Mfarooq360
Thank you, appreciate everything!

@Mfarooq360 Yes, it seems as though it's not able to preload recursively when it's more than 100 or so subdirectories. Yesterday and Today, 300K files between 1500 subdirectories, that are not being backup & preloaded. It takes 6 hours to complete and at the end. Winthumbspreloader does not save a backup. I've been testing highlighting 15 directories at a time and right-clicking and winthumbs recursively. But, even just 15 highlighted doesn't seem to back up correctly either. Which then raises the question, is there a way for winthumbspreloader, to start from top of the directory and work it's way down, one at a time?

Have you considered using a bat file to recursively go through the folders and call winthumbs on each without the -r flag? Basically handle the actual folder selection outside the program itself and see if it makes a difference. Also don't be tempted (like i was early on when i found this tool) to launch all the folder gens in parallel/at once, you can very quickly peg your whole machine and render it unresponsive.

@VL4DST3R
I never thought about doing it that way. Let alone, I don't even know what script commands I would need to put in the batch file to get it to run as described.
Now, I have been using CLI and added folder paths limiting it to about 50 folders in the CLI line following calling winthumbs. As it seems limiting to about 50 directories seem to back up successfully.
Now, I've also been testing "deny" special permissions' explorer cache folder. So windows doesn't delete automatically. This "seems" to be helping. But, I haven't gone BIG on cache size like @Mfarooq360 stated, with the cache rising as high as 4.5GB.
I could try one more time, let it preload for six hours and hopefully it backups.

Yes, it still crashed at the end and didn't backup, unforutnately.

2024-05-13 06:59:21.342: Total items count: 348217
2024-05-13 06:59:21.343: Preloader state: Processing
2024-05-13 06:59:21.350: Process priority set to Below Normal
2024-05-13 06:59:21.350: Thread count: 256
2024-05-13 06:59:21.350: Preloading thumbnails
Use Debug Logging for more detailed information (Slows thumbnail generation)
2024-05-13 11:40:41.086: Cache check timer stopped
2024-05-13 11:40:41.086: Preloader state: Done
2024-05-13 11:40:41.086: Preloader has finished
2024-05-13 11:40:41.086: Instance completed, ending instance.

Was auto backup turned on in the cache form of the GUI or did it still just not backup at the end?

2024-05-13 11:40:41.086: Instance completed, ending instance.

I also wonder how it crashed since it does look like it states that the instance completed successfully.

@Mfarooq360
It finished, yes. But, it didn't back up in explorer cache or winthumbspreloader cache.
This is why I've been doing 50 directories at a time. Because, once it completes. It even shows in the dialog box, backing up.... then it closes. It cache TO BOTH explorer cache and winthumbspreloader cache.
But, when I do straight starting from parent directory and recursive that way, it doesn't say it at the end. It just finishes and closes. And does not cache to winthumbs or explorer cache. That's exactly what it shows in the log above. It never says, back up complete.


Support functional decomposition of code blocks

Feature Request: Support functional decomposition of code blocks
Description
Being able to decompose code blocks into separate functions can improve code readability and reuse.
Motivation
Allow developers to decompose code blocks into different functions.
Importance
This will allow for cleaner and more modular code.
Example:
https://github.com/amzn/smoke-framework-application-generate/blob/swift_syntax/Sources/SmokeFrameworkCodeGeneration/ServiceModelCodeGenerator%2BgenerateHandlerSelector.swift#L64
Alternatives Considered
I have tested this ability with the following change-
https://github.com/tachyonics/swift-syntax/commit/27c159b653fce0783aa612a56fa4d3e5fdda5a16
However I hadn't created a pull request on this change immediately as I am looking for guidance on if this change is a good idea, if there is some other way to achieve this or if this is the best way to incorporate it into the repository.

I think what you are asking for is exactly what is being fixed by https://github.com/apple/swift-syntax/pull/462, right?

Yes, exactly. Thanks for point that out.
I'll resolve this in favour of the change in #462.


Updated fidelity testing

This change proposes a revised test authoring scheme and unified screenshot creation for our fidelity test suite. It builds upon @elalish 's initial work to migrate us towards an exclusively browser-based screenshot creation scheme in #676 / #682 .
Critical details include:

Canonical test configuration is now entirely contained in the config (test/fidelity/config.json)
A linkable "scenario selection" UI has been added w/ support for arbitrary browser-based renderers
A <filament-viewer> element has been introduced to streamline Filament's usage in fidelity tests
Specific renderers can now be excluded from individual tests via the config
Individual renderers can be configured with "setup" script (via the config) that will be run prior to generating a screenshot with that renderer

This pattern can be extended to other lifecycle stages as needed as we move to include additional renderers

A platform-specific cmgen binary is downloaded from Github when running on Linux and OSX
.jpg IBLs are automatically converted to .png before being processed by cmgen
Our Travis config should be fixed to allow for proper test result deployment to Github Pages, but we won't know for sure until we land this change

Unified fidelity test viewers

Latest results with this change

Fixes #434
Fixes #515
Fixes #655
Fixes #673

There is a dropdown that lets you review incremental changes by commit e.g., https://github.com/GoogleWebComponents/model-viewer/pull/713/commits/1e33320ae47f01f4fe12d7cd7d715ec158b02599

Oh wow, almost all your changes are just in that commit, aren't they? Cool, thanks.

I see what you mean about the framing being off randomly. Very strange, and definitely wasn't there in my version of this PR (I spent a fair bit of time checking that it was single-pixel aligned). However, I also noticed a couple of other bugs you can see in this screenshot:

First, both filament and  get a scrollbar, but only sometimes, again at random. When they are rendering I notice that they render first at one size and then they expand to roughly double, and that's when the scrollbar appears. Sadly, doesn't seem to correlate with the issue above.
Second, Filament is using the HDR sunrise for both of these. I originally fixed this by appending _LDR, _HDR to their names because otherwise they end up in the same cache entry; I'm guessing that's what happened here.

Good catch, I'll fix the filename issue.
Strangely, I have never seen that scrollbar. Regarding the offset, I was actually talking about this:

You can see from the outline in the bottom right that the two models are offset vertically from each other. Back to back comparison also shows the difference:

Yes, I saw it too; my point is it wasn't there in my PR. I'll see if I can find the culprit as I code review.

Have you seen this?

I went to http://<IP_ADDRESS>:8000/test/fidelity/renderers/filament/index.html and noticed that at first nothing loaded but a black square. Then I changed the drop down and it started working fine, but after changing models a few times, they now all render in grayscale. Then after a new more changes, only the skybox renders. Seems to be fine for the model-viewer site though.

Yeah, I have talked to @prideout about some of this stuff. All of the models will load and render if they are the first model, and there are various bugs that occur for subsequent models. I decided that the best path forward would be for us to land these changes and then file issues against Filament with links to broken cases.

Those diff stats. 👏
Do you think it's strongly preferable that any future third-party renderers added here should also be rendering in the browser? Just wondering about the feasibility of diffing offline renders from something like Mitsuba or Arnold, eventually.

For path tracers, I doesn't seem like we'll get a lot of value from maintaining our own "runners" to launch renders with them the way we did for Filament. I suspect we will get the most bang for our buck by maintaining golden renders for those.
That said, to the extent that any path tracer can scripts / worked into some kind of automation, I think we could definitely incorporate them into our golden update flow. I see this is parallel to the actual fidelity testing flow.
For everything else, it would probably be helpful to do a survey of realtime renderers that we are likely to be interested in. The ones we have talked about as low hanging fruit include:

Babylon
Cesium
Khronos Reference Renderer

These are all able to be run on the web. Separately, we have found ourselves compared to realtime rendering in Adobe Dimension and Substance Painter. I'm sure we will eventually be compared to similar tools in the future. These will be a bit more tricky to incorporate, but I don't want to rule out the idea of incorporating them somehow.

Agreed on just maintaining golden renders for path tracers, I don't think we need to launch renders online either. 👍
I'd be very curious whether game engines like Unity or Godot that support WebGL+WASM packaging could be used to create a viewer that's sufficient for loading models at runtime, but that's probably a big project. PlayCanvas is another to think about.
The three web libraries you mention are the better places to start though, for sure.

Yeah, that's a very interesting idea. We are already incorporating Filament via WASM. It might be mostly a licensing question in Unity's case. We already have some experience working with the Unity glTF loader plugin.
I don't know much about Godot, but says it is open source. Do they already support runtime loading of glTFs?

Looks like Godot's glTF support is good, but not available at runtime currently: https://github.com/godotengine/godot/issues/24768

I suppose we could just compile all the models we are testing into a single Godot binary?
More realistically, we'll probably have to wait until that issue sees some movement.


HDDS-2141. Missing total number of operations

What changes were proposed in this pull request?
Sum request counts and use it as fallback in case explicit "Ops" metric is not available.
https://issues.apache.org/jira/browse/HDDS-2141
How was this patch tested?
Ran ozonefs robot test, checked OM metrics page.

/label ozone

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
164
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
35
hadoop-ozone in trunk failed.

-1
compile
25
hadoop-ozone in trunk failed.

+1
mvnsite
0
trunk passed

+1
shadedclient
1088
branch has no errors when building and testing our client artifacts.

+1
javadoc
206
trunk passed

_ Patch Compile Tests _

-1
mvninstall
41
hadoop-ozone in the patch failed.

-1
jshint
106
The patch generated 1393 new + 2737 unchanged - 0 fixed = 4130 total (was 2737)

-1
compile
26
hadoop-ozone in the patch failed.

-1
javac
26
hadoop-ozone in the patch failed.

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
802
patch has no errors when building and testing our client artifacts.

+1
javadoc
265
the patch passed

_ Other Tests _

-1
unit
227
hadoop-hdds in the patch failed.

-1
unit
108
hadoop-ozone in the patch failed.

+1
asflicense
114
The patch does not generate ASF License warnings.

3663

Reason
Tests

Failed junit tests
hadoop.ozone.lock.TestLockManager

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1462

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient jshint

uname
Linux 03d06927b330 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c474e24

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/branch-compile-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/patch-mvninstall-hadoop-ozone.txt

jshint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/diff-patch-jshint.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/patch-compile-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/testReport/

Max. process+thread count
306 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/1/console

versions
git=2.7.4 maven=3.3.9 jshint=2.10.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
40
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
31
hadoop-ozone in trunk failed.

-1
compile
20
hadoop-ozone in trunk failed.

+1
mvnsite
0
trunk passed

+1
shadedclient
1004
branch has no errors when building and testing our client artifacts.

+1
javadoc
187
trunk passed

_ Patch Compile Tests _

-1
mvninstall
34
hadoop-ozone in the patch failed.

-1
jshint
93
The patch generated 1392 new + 2737 unchanged - 0 fixed = 4129 total (was 2737)

-1
compile
26
hadoop-ozone in the patch failed.

-1
javac
27
hadoop-ozone in the patch failed.

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
802
patch has no errors when building and testing our client artifacts.

+1
javadoc
176
the patch passed

_ Other Tests _

+1
unit
262
hadoop-hdds in the patch passed.

-1
unit
31
hadoop-ozone in the patch failed.

+1
asflicense
36
The patch does not generate ASF License warnings.

3123

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1462

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient jshint

uname
Linux c8863d1e4b09 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e97f0f1

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/branch-compile-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/patch-mvninstall-hadoop-ozone.txt

jshint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/diff-patch-jshint.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/patch-compile-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/testReport/

Max. process+thread count
440 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1462/2/console

versions
git=2.7.4 maven=3.3.9 jshint=2.10.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

/retest

Thanks @elek for reviewing and merging it.


Multi environment SSO issue

Description:
When UI running separately make GET request to self IDP
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Improvement has added with this PR (Thanks to @RenukaFernando ): https://github.com/wso2/carbon-apimgt/pull/4843


Song support

Create a class hierarchy to handle songs.
Create a code structure to handle the <elements> element, and the child elements <song> and <dialogue>.

Commit:
https://github.com/cjcodeproj/medialibrary/commit/a76cc48c7712d33ca08795c0a93465405f327d2c

Closing Notes
Complexity
What the code considers elements are tricky, because they have share attributes from the parent object that contain them.
For example, on a Van Halen CD, the album artist is obviously Van Halen.  And if individual songs in the XML structure do not have <catalog> elements that identify the artist as Van Halen, then the Song object needs to reference the Album object and grab the artist values from that.
Which is good, because the code is capable of doing all the heavy lifting, and it's a better trade off than having more XML elements than necessary.  I should only have to list the artist as Van Halen once.


Creating group should add the user to the group

I think this is more a Lagoon concern than the CLI tool - so thought it would be best to create here. Currently when you create a new group it does not assign the user who created the group to the group and as a result they are not able to add any other users to the group.
They can however add the group to projects that they have access to, which makes the process for creating users and groups slightly awkward as I would need to raise a ticket to add my user to the new group.
For example:
$ lagoon add group -N new-group
Result: success
id: 61b571ee-1ae5-406e-b42d-e311ad11682b

$ lagoon add project-group -p my-project -N new-group
Result: success
id: 1

$ lagoon add user-group --email<EMAIL_ADDRESS>-N new-group -R maintainer
Error: graphql: Unauthorized: You don't have permission to "addUser" on "group".

In this example:

My user is part of org-group
My project is included in org-group
My user can add the new group
My user can add the new group to the project (based on RBAC of org-group)
My user cannot add users to the new group

The use case for this is:

Providing scoped maintainer access to targeted projects via a new group

Currently - to provide a developer maintainer access for projects managed by Lagoon I would have to give them maintainer access to the broad group that all projects are part of.

+1 to this issue. When you create a group, you should immediately be added as an OWNER IMO.

The current work on Organizations should provide a framework to define who can create groups/projects within an existing boundary.
Hopefully, we can straighten this out a bit

The current work on Organizations should provide a framework to define who can create groups/projects within an existing boundary.
Hopefully, we can straighten this out a bit

Organizations is transitional though, in that Lagoon can still operate without orgs being utilized. I've put a PR up that resolves this for non-org usage.


add states montana texas and colorado.

@bsardo you think you will get to it anytime soon?

Hi @aryehlev, we might have some time next week to give this a look.


[CI] Updated RBE Windows Image (MSVC 2022 only)

Updated the Windows RBE image to use MSVC 2022
Related to https://github.com/grpc/grpc/pull/37987

Closed in favor of https://github.com/grpc/grpc/pull/38063


feat(contributing): add more details to issue reporting

Adds in some content that was in our CONTRIBUTING.md file but not on this page.
cc @helgi

Well said--thanks for updating and making this more user-friendly.


Revert "kubevirt, e2e: Skip advanced multinet for CI"

This reverts commit 1927260efe20f338f421fd74b0dc7152ce978454.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/test e2e-kubevirt-aws-ovn
We are going to test it three times

/test e2e-kubevirt-aws-ovn
Not related to resources, all VMs are fine and the rest of nodepool tests are passing.
--- FAIL: TestNodePool/HostedCluster0/Main/TestNodePoolReplaceUpgrade (1955.85s)

/test e2e-kubevirt-aws-ovn
Third run, if this passes we are fine.

/hold cancel

/jira refresh

/jira refresh

Failing at non related kubevirt external cluster test for autoscaling.


Add Python3 and Visual Studio 2015 support

Modified matplotlibcpp.h a bit to support more environments
Added WinBuild.cmd and CMakeLists.txt for Visual Studio 2015 support

Hi, thanks for contributing!
The PR looks pretty nice, so I'll probably merge it after the issues are fixed, although please remember in the future to squash your commits before making a PR to make the comment history look less messy ;)

Thank you for your feedback. This is a kind of first PR in my life, so sorry about squashing. (If there's way to fix it now, I'll follow it)
Please take a time to consider about python.h matter and I'm happy to get some advice for preprocessor descriptions if we choose a preprocessor strategy.

OK. Here's my modification for your homework.

Ok, merged. Thanks for contributing!


Fix typo in message.

No big deal, obviously, but I noticed it, so I fixed it. :-)

That one always gets me...
Thanks for the PR!


Add API Endpoint for Listing LLM Provider Models

Description:

Implemented a new API to list available models for a given LLM provider.
This enhancement improves user access to LLM models by provider.

@sajosam , Attach postman screen shot of API response

@agberoz Here is the reponse,

@ashmilhussain  The spacing changes were auto-corrected by the pre-commit linter.


Webpack allows unhandled promise rejection to fail silently

Bug report

What is the current behavior?
We recently had a bad build deploy successfully and found that an outdated plugin was causing an unhandled promise rejection that didn't cause the build to fail.
If the current behavior is a bug, please provide the steps to reproduce.
This repo contains a minimal package list & webpack config to reproduce the problem:
https://github.com/ebbishop/webpack-silent-fail
The webpack.config.js in this repo forces webpack to fail. The bad plugin is not the bug. While fixing/updating/removing the offending plugin is important, webpack should exit the process with a non-zero code.
What is the expected behavior?

When webpack runs into an UnhandledPromiseRejectionWarning, it should exit the node process with a non-zero code
This will allow automated ci/cd scripts to fail once the webpack process fails.

Other relevant information:
webpack version:  5.9.0
Node.js version: 10.16.3
Operating System: macOS 10.14.5

Please use tapPromise, for tapAsync you need to run cb, your code is not executed

@alexander-akait The change you suggest does not solve the problem I'm reporting. I know the plugin causes the build to fail - that's the point. What I and others need is a way to have webpack exit the node process with a non-zero when there's an unhandled promise rejection.
This is problem that sometimes comes up in automated deployments: a plugin is updated and suddenly breaks the webpack build, but the node process doesn't exit.  So then, our builds continue on without the build files we expect webpack tor produce.
The expected result is not that webpack build files when a plugin is broken, but that it fail in such a way that the node process exits.

You just do not call cb. what is you expected?

The FailingPlugin is meant to simulate any possible plugin with an unhandled promise rejection.
Expected: when there's an unhandled promise rejection, webpack exits the node process with a non-zero exit code.
Why: this will allow us to kill a deployment if a webpack build is broken.

@alexander-akait
The logs for npm run build in my test repo are this:
npm WARN prepare removing existing node_modules/ before installation

><EMAIL_ADDRESS>install /webpack-silent-fail/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v5.0.0/darwin-x64-72_binding.node
Download complete ░⸩ ⠋ :
Binary saved to /webpack-silent-fail/node_modules/node-sass/vendor/darwin-x64-72/binding.node
Caching binary to /.npm/_cacache/node-sass/5.0.0/darwin-x64-72_binding.node

><EMAIL_ADDRESS>postinstall /webpack-silent-fail/node_modules/node-sass
> node scripts/build.js

Binary found at /webpack-silent-fail/node_modules/node-sass/vendor/darwin-x64-72/binding.node
Testing binary
Binary is fine
added 467 packages in 5.692s

><EMAIL_ADDRESS>build /webpack-silent-fail
> webpack

rejecting promise
(node:66709) UnhandledPromiseRejectionWarning: undefined
(node:66709) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:66709) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

><EMAIL_ADDRESS>postbuild /webpack-silent-fail
> npm run clean

><EMAIL_ADDRESS>clean /webpack-silent-fail
> rm -f css/*.js

What I'd like to see is something more like this:
1 ERROR in child compilations
webpack 5.9.0 compiled with 1 error in 493 ms
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.

Sorry, handling Unhandled promise rejection on your code side, you can add to this any own logic

@alexander-akait What happens when we don't control the plugin? That's the use-case I'm most concerned about. Currently, webpack fails to build, but lets the node process continue. That seems like a bug to me.

Please read again:
(node:66709) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

so wepback doesn't exit with non zero exit code

@ebbishop  did you ever figure out this issue? For me this most certainly should qualify as a bug. Webpack needs to support a --unhandled-rejections flag or an uncaught error should cause the node process to fail.

@technocookie webpack should not generate Unhandled promise rejections are deprecated, maybe problem in not official loaders/plugins, can you trace it?


⚠ Processors has degraded performance

In 8306c5d, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 53 ms

Resolved: Processors performance has improved in 8dc80a7.


expand tildes in cli paths

we currently interpret --foo=bar as {foo: bar} and --foo bar as {foo: true, _: ['bar']}
we should probably document this options behavior more clearly in the CLI usage/help
however, the only thing that doesnt work as expected is paths with ~ in them.

i propose we fix it by using this to expand them manually since bash doesn't handle it for us
https://www.npmjs.org/package/expand-home-dir

This is fixed now.


Import css error in a project created with yarn workspaces

Version
3.0.3
Reproduction link
https://github.com/mqhe2007/error-yarn-workspaces
Node and OS info
Node 8.11.2/ yarn 1.9.4 / macOS 10.13.6
Steps to reproduce
in project root directory run:

yarn install
yarn workspace frame run serve

What is expected?
no error
What is actually happening?

used iView ui

As a workaround, add these lines to vue.config.js
module.exports = {
  css: {
    loaderOptions: {
      postcss: {
        path: __dirname
      }
    }
  }
}

@sodatea 果然是配置问题，但是当时没有找到具体改哪个地方，非常感谢！Thank you very much!

@sodatea, you just saved me from a major migraine after running around in circles trying to solve this issue. Thank you so much 👍


Feature Request: Gotify Notification Support

Hi,
it would be nice to have options regarding the notification backends.
Would it be possible to implement notification support for gotify?
There is a REST-API you could use:
https://gotify.net/api-docs
Could be configured via a environment variable just like shoutrrr:
-e "GOTIFY_URL=..."
Regards

Hi, it would be nice to have options regarding the notification backends. Would it be possible to implement notification support for gotify?
There is a REST-API you could use: https://gotify.net/api-docs
Could be configured via a environment variable just like shoutrrr: -e "GOTIFY_URL=..."
Regards

Hi!
Shoutrrr already supports notifications to gotify and many other. For example:
SHOUTRRR_URL="gotify://<IP_ADDRESS>:8083/AwQqpAae.rrl5Ob/?title=Unknown host detected&DisableTLS=yes"
Here is the full list of options:
https://containrrr.dev/shoutrrr/v0.5/services/overview/


Viewport Addon

Description
This is a fairly early PR of a viewport plugin which allows you to resize the iframe of storybook.
Remaining Tasks

[ ] Fix lint issues
[ ] Add unit tests
[ ] Add documentation and screenshots to readme.

Possible Features

Responsive hooks, basically add the ability to drag the ends of the iframe to change the size
Improve interaction with the iframe rather than just grabbing the iframe from the DOM add listeners to the iframe to allow us to interact with it

Screen Cap

Issues
Fixes #1624

Really great addon! Thanks for doing this!
I would add "write readme" to "Remaining Tasks".
I didn't dig into a code yet but I wonder whether it will be compatible with upcoming multistory feature (#1394)? Although not sure that it should, just want to share this thought

@saponifi3d @ndelangen I'd like to merge this into a feature branch in the storybook repo and add @saponifi3d to the storybooks org so we can more easily collaborate on fixing this up. OK?

Welcome @saponifi3d ! 👍

Where is the git repo for this? Downloaded module from npm at https://www.npmjs.com/package/@storybook/addon-viewport -- all cool, but I have possible bugfix.

@markoshust it's part of the storybook monorepo, if you go into addons/viewport it'll be there :)

@markoshust contact me on slack if you need help getting set up.
There's also the CONTRIBUTING.md document.
We're currently working off the release/3.3 branch as @saponifi3d mentioned.


[Menu] Mixed Accordion + Menu cursor problem

Hi,
Missing pointer cursor when Accordion and Menu is mixed.
JSFiddle here: http://jsfiddle.net/7sne24yp/
around line 85 in accordion.less
solution example:
.ui.accordion.menu a,
.ui.accordion .menu a {
cursor: pointer;
}
thanks, Gabor

I'm not seeing this issue currently.


Add backstepping position controller for multicopters

Resolves #28, #29
Summary
Add a backstepping position controller for multicopters.
Note that the implemented code does not consider faults, although the original paper addresses fault tolerant control.
Sim result

Run test/algorithms/backstepping_position_controller.jl:

Notes

command could be a privileged name for the output of controllers.
Method sim with an argument env::AbstractEnv has been deprecated (#29).
Move test files to test.

@hnlee77 sim 의 용법이 사소하게 바뀌었으니 참고~


how to define an index route?

I'm looking to define a route for / but I'm not sure how to do this. I was hoping that the value of initialRouteName would be used to define the base route, but that isn't the case.

I figured this out, the following works:
const AppContainer = createBrowserApp(
  createStackNavigator(
    {
      Home: {
         screen: Home,
         path: ''
    },
      Profile,
    },
    {
      initialRouteName: 'Home',
    },
  ),
)

I had been trying to use / as the path that causes issues!


GH-40498: [GLib] Remove arrow-glib/gobject-type.h

Rationale for this change
It's needed for GLib < 2.44 but we require GLib >= 2.56. So we don't need it now.
What changes are included in this PR?
Remove arrow-glib/gobject-type.h.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

GitHub Issue: #40498

+1


fix form data and blob compat

FormData, Blob, and FileReader need to be on the self object, otherwise thinks they aren't supported

@calvinmetcalf window isn't always available.

ok now it should work in web workers, will get a test next

@calvinmetcalf LGTM, thanks for catching this one!

I'd be happy to add a test for this, but I'm not familiar enough with how the ember tests are setup to add the first test to this repo.

some places to look:

test likely could go here: https://github.com/stefanpenner/ember-fetch/blob/master/tests/acceptance/root-test.js
if you need to fake the underlying XHR, we use pretender

if you have other specific questions i can try to answer them

done, though I do need to point out that qunit is terrible for async tests (also in general)

@calvinmetcalf you can actually just return the promise. And qunit will automatically go async, and also assert fulfillment and assert against rejection.  Should cleanup stuff and make qunit more tolerable.

well that certainly is an improvement over having to call stop

Some last few comments. Once addressed, we can merge and I'll release

fixed
On Mon, Sep 28, 2015 at 3:45 PM Stefan Penner<EMAIL_ADDRESS>wrote:

Some last few comments. Once addressed, we can merge and I'll release
—
Reply to this email directly or view it on GitHub
https://github.com/stefanpenner/ember-fetch/pull/5#issuecomment-143855153
.


Field visibility

You cannot set field visibility currently.
I have added it in my branch @ https://github.com/LegNeato/codegen/tree/issue-3-and-4-field-documentation-annotation and will put up a PR when https://github.com/carllerche/codegen/pull/6 lands.

I got around this by having the name of the field have the word pub in the field name, e.g.
s.field("pub num", "usize");

But yeah, +1 to having this be supported!


BAFopathy and its subtypes

Preferred gene-related syndrome label
ACTB-related BAFopathy
ACTL6A-related BAFopathy
ACTL6B-related BAFopathy
ARID1A-related BAFopathy
ARID1B-related BAFopathy
ARID2-related BAFopathy
BCL11A-related BAFopathy
BCL11B-related BAFopathy
PBRM1-related BAFopathy|
SMARCA2-related BAFopathy
SMARCA4-related BAFopathy
SMARCB1-related BAFopathy
SMARCC1-related BAFopathy
SMARCC2-related BAFopathy
Synonyms
Not sure
Parent term (use OLS, or your favorite ontology browser)
Definition
Please write the definition in the format: Any BAFopathy in which the cause of the disease is a mutation in the [gene name] gene.
**Definition source (Please give PubMed ID, if applicable, in format PMID:#######)
https://jhu.pure.elsevier.com/en/publications/expanding-the-spectrum-of-baf-related-disorders-de-novo-variants-
https://www.sciencedirect.com/science/article/pii/S0002929718304105
Children terms (if applicable) Should any existing terms be re-classified as children underneath this new proposed term?
Comment
ClinVar has received several submissions from Baylor using this term:
https://www.ncbi.nlm.nih.gov/clinvar/?term=bafopathy
I do not have any expertise in determining which of these are equivalent to the intent of gene-related disorders for Coffin-Siris or  Nicolaides-Baraitser

1) Import genes into Mondo
(note that the other genes are already in Mondo)
ACTL6B = http://identifiers.org/hgnc/160
ARID2 = http://identifiers.org/hgnc/18037
BCL11B = http://identifiers.org/hgnc/13222
SMARCC2 = http://identifiers.org/hgnc/11105
DPF2 = http://identifiers.org/hgnc/9964
ACTL6A = http://identifiers.org/hgnc/24124
PBRM1 = http://identifiers.org/hgnc/30064
SMARCC1 = http://identifiers.org/hgnc/11104
2) Create a new term: BAFopathy
Definition: Disorder caused by mutations in the various subunits composing the BAF complex.
(PMID:30580808)
Parents: Mendelian disease (MONDO:0003847)
Note: @nicolevasilevsky - can you please confirm this is correct (if you know). This is consistent with what we did with RASopathy
Children:
From PMID:30580808 : “The most recognizable syndrome associated with BAF abnormalities is Coffin-Siris syndrome (...). CSS can result of pathogenic changes in other chromatin remodeling proteins with no direct interaction with BAF complex, including SOX11 (MIM: 600898)18 and PHF6 (MIM: 300414).19”
→ children of BAFopathy need to be specific,ie “CSS" cannot be the child of BAFopathy since some of CSS children are not a BAFopathy.
3) create new terms/update existing terms

based on OMIM records, some Mondo terms should be updated and the gene should be added
based on PMID:30580808 and this issue: some terms should be children of BAFopathy
some NTR are already in Mondo (under another name). Therefore a synonym should be added instead of creating new terms
The working table is here.
@nicolevasilevsky, could you take a look at it and comment, please. My questions are mostly related to the xref and source, specifically:
--col F and G
--col L
--col M (see comment in line 7)
Once this table is reviewed, I will create a ROBOT template.

This looks good Sabrina, really nice work. :)


Update "Jupyter Kernel for Deno" Quickstart guide for VSCode

Added simple instructions for creating a Jupyter notebook file in the VSCode example.

Accidentally duplicated in #995


Ubuntu 22.04

NVIDIA have now released CUDA images running on Ubuntu 22.04. It would be great to have pixel streaming base images that use this newer stack. I'm happy to help.
https://catalog.ngc.nvidia.com/orgs/nvidia/containers/cuda/tags

@luc122c apologies for the extended delay in adding support for Ubuntu 22.04! Back in May 2022, NVIDIA stopped publishing updates to their CUDA + OpenGL "cudagl" base image, which meant there wasn't an Ubuntu 22.04 version of it available for consumption by downstream projects like ue4-runtime. NVIDIA described this as a "temporary hiatus", so I waited patiently for them to resume publishing new cudagl images. Over a year later, this still hasn't happened.
Today I set about removing Ubuntu 18.04 support from the ue4-runtime codebase, since Canonical ended official support for 18.04 a few months ago, and I've recently received reports from community members that Unreal Engine 5.2 crashes with Vulkan errors when running under Ubuntu 18.04-based containers. When I noticed that the upstream cudagl base image still hadn't been updated, I decided to finally give up on waiting for NVIDIA, and implemented a workaround instead. The build script now manually builds cudagl images for each version of CUDA, allowing ue4-runtime to support both the latest version of Ubuntu and the latest version of CUDA. This does increase the build time a bit when building images for a lot of different CUDA versions, so I've also switched to just building images for the newest minor version of each major version of CUDA. These changes should help ensure the ue4-runtime codebase is in a position to more rapidly adopt support for new versions of Ubuntu in the future.


lipo create fails only on linux/amd64: invalid magic number in record at byte 0x0

The same command lipo -create -output bin/ios bin/ios-amd64 bin/ios-arm64 runs OK in a linux/arm64 container running on my macOS Apple Silicon, but fails in linux/amd64 and Github Actions runner with ubuntu-22.04
Version: v0.9.2
root@6a8c80cef904:/tmp/go-ios-main# file bin/ios-arm64
bin/ios-arm64: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=xWhc55l_Kd_AK6iiE8Cu/e9kCmftPGWgyYYWt0UH1/sOw6UAnw1MwWgLebIWyX/YtLa1QyQOKGxlZHJkm9_, stripped

root@6a8c80cef904:/tmp/go-ios-main# file bin/ios-amd64
bin/ios-amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=CauiLtY_-v1HBKfENqfE/2-Cd9sOdFKHlsRYisnHg/k-eNxZxKdTWHF-fx0Egw/ajjRbI8swoDK8BW2yePs, stripped

root@6a8c80cef904:/tmp/go-ios-main# lipo -create -output bin/ios bin/ios-amd64 bin/ios-arm64
Error: invalid magic number in record at byte 0x0

Thank you for reaching out to me.
In my understanding, Linux does not support fat binaries in the first place.
The built-in lipo tool on macOS also does not support Linux OS, which is based on ELF.
So, your comment seems a bit curious.

The same command lipo -create -output bin/ios bin/ios-amd64 bin/ios-arm64 runs OK in a linux/arm64 container running on my macOS Apple Silicon, but fails in linux/amd64 and Github Actions runner with ubuntu-22.04

$ sw_vers
ProductName:    macOS
ProductVersion: 12.4
BuildVersion:   21F2081

$ GOOS=linux GOARCH=amd64 go build -o amd64 example/main.go
$ GOOS=linux GOARCH=arm64 go build -o arm64 example/main.go
$ file arm64 amd64
arm64: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=tgAeXC5UM4Tal3tGO_1c/mIGhJMz4_VmOCis-ZZ2M/7vQDx-GM45N1EJ9xAKXE/070jc3zI_IROugfQWyux, with debug_info, not stripped
amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=NIn0SOF_BhQNWe4k4eNI/Kkmkadqfso8brZMVh6o0/0OrPifiIyfVUlngMwpUm/gUe4h_BsM2rzpjeaSTGp, with debug_info, not stripped

# build-in lipo on mac os
$ lipo -output hello-world -create arm64 amd64
fatal error: /Library/Developer/CommandLineTools/usr/bin/lipo: can't figure out the architecture type of: arm64

https://en.wikipedia.org/wiki/Fat_binary

A proof-of-concept Ubuntu 9.04 image is available.[47] As of 2021, FatELF has not been integrated into the mainline Linux kernel.[citation needed][48][49]


The examples/protocols/mqtt/ssl demo cannot use TLS 1.3 to connect with MQTT broker. (IDFGH-13029)

I enabled TLS 1.3 via menuconfig for examples/protocols/mqtt/ssl demo in IDF 5.2.1 SDK, but the ssl demo still used TLS 1.2 to connect with MQTT broker. I attached 2 packet data screenshot, please help to find what is the issue? how to enable TLS1.3 in IDF 5.2.1 SDK?

Hi @robbinlu-ayla thanks for reporting.
The issue here is that the version should be set through the transport layer and mqtt client doesn't offer the option. I'm working on the solution to make it easier for users to set options to the transport in use.
One possible work around is to use the custom transport in the mqtt client.
The steps would be:

create a ssl transport using esp_transport_ssl_init
set all the required options using the esp_transport API
Pass the transport configured as an option to esp_mqtt_client_init through the configuration field network.transport.

Other alternative would be to set only TLS 1.3 in menuconfig in the mbedTLS options, disabling TLS 1.2.

Hi @euripedesrocha,
I tried enable TLS 1.3 and disable TLS 1.2 in menuconfig, then build the ssl example, but
[ ] Support TLS 1.2 protocol
[*] Support TLS 1.3 protocol

Hi @euripedesrocha,
Thanks your reply. We didn't use components/mqtt in our project.
We will update and test after get your fix code.

@robbinlu-ayla didn't understand your comment about not using components/mqtt.
About the compilation issue setting only TLS 1.3, below are the settings to disable TLS v1.2:
CONFIG_MBEDTLS_SSL_PROTO_TLS1_3=y
CONFIG_MBEDTLS_SSL_RENEGOTIATION=n
CONFIG_MBEDTLS_SSL_PROTO_TLS1_2=n
CONFIG_ESP_WIFI_MBEDTLS_TLS_CLIENT=n

@euripedesrocha
I set these config items in sdkconfig, rebuilt project, flashed app bin into ESP32 DevKit, the app cannot connected with our cloud server. The TLS1.3 still doesn't work.
CONFIG_MBEDTLS_SSL_PROTO_TLS1_3=y
CONFIG_MBEDTLS_SSL_RENEGOTIATION=n
CONFIG_MBEDTLS_SSL_PROTO_TLS1_2=n
CONFIG_ESP_WIFI_MBEDTLS_TLS_CLIENT=n
Which esp-idf version could support TLS1.3?

Hi @robbinlu-ayla,
using IDF 5.2.1 and the settings I shared you should be able to use TLS 1.3
If you follow the path of creating a transport and passing it to mqtt client after setting the required configuration, it should work.
If you use the latest master from mqtt client, we still need to move it to IDF and backport to older versions, you will be able to use the code presented here
Could you share the errors you are facing, so I can try to help you?

We are using IDF 5.2.1, using the below config,
CONFIG_MBEDTLS_SSL_PROTO_TLS1_3=y
CONFIG_MBEDTLS_SSL_RENEGOTIATION=n
CONFIG_MBEDTLS_SSL_PROTO_TLS1_2=n
CONFIG_ESP_WIFI_MBEDTLS_TLS_CLIENT=n
And we didn't use esp mqtt client components, we wrote a mqtt client(based components/mbedtls), our mqtt client cannot connect with our cloud with TLS1.3.

@robbinlu-ayla I'm a bit confused here, since the issue is regarding one of the examples from idf that uses the mqtt client.
I need you to share the logs with the errors that you are facing, so I can try to identify potential misconfiguration from your side.

We use socket to connect to the service on the port 443, after the connection is established, it uses mbedtls_ssl_setup to setup the context for the TLS handshaking, and then use mbedtls_ssl_handshake to handshake. According to your mentioned, I think that you want us to specified TLS 1.3 in the SSL context? I have two questions,

How to specified TLS version by mbedtls API?
If the service only supports TLS 1.2, does it will fall back to TLS 1.2 if I specified TLS 1.3?

Hi @hawkhan / @robbinlu-ayla
For usage of the mbedtls API directly you can refer to this exmple.
The TLS version in use decision will be part of the TLS negotiation between client and server, so if you have both set and there is only TLS 1.2 in one of the sides that will be selected.
If there is a decision to use only TLS 1.3, you can use mbedtls_ssl_conf_min_tls_version to set it as the minimum.


Strange issues with file-descriptors

What happened?
This might be a PHP issue, but I'd expect the following to work:
fopen("php://fd/$fd", "rb"); // PHP Warning:  fopen(php://fd/9): Failed to open stream: operation failed
fopen("/proc/$pid/fd/$fd", "rb"); // PHP Warning:  fopen(/proc/97337/fd/12): Failed to open stream: No such file or directory
var_dump(scandir("/proc/$pid/fd"));

// outputs:

array(12) {
  [0] =>
  string(1) "."
  [1] =>
  string(2) ".."
  [2] =>
  string(1) "0"
  [3] =>
  string(1) "1"
  [4] =>
  string(1) "2"
  [5] =>
  string(1) "3"
  [6] =>
  string(1) "4"
  [7] =>
  string(1) "5"
  [8] =>
  string(1) "6"
  [9] =>
  string(1) "7"
  [10] =>
  string(1) "8"
  [11] =>
  string(1) "9"
}

For some reason, I cannot open file-descriptors from other threads (as you'd expect to be able to do in C/go). Still digging into the underlying cause.
Use-case: experimenting with frankenphp for running "workers" and having a means of communicating between them.
Build Type
Docker (Debian Bookworm)
Worker Mode
No
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
N/A currently

Relevant log output
No response

Ah, only the "CLI" SAPI is allowed to access FD's, and it is hardcoded that way.
if (strcmp(sapi_module.name, "cli")) {
			if (options & REPORT_ERRORS) {
				php_error_docref(NULL, E_WARNING, "Direct access to file descriptors is only available from command-line PHP");
			}
			return NULL;
		}

Strangely, that error message doesn't make it to the user.
Anyway, that is unfortunate. I'll look into adding support to the SAPI handlers for it though. It would be quite handy to share pipes between different PHP threads (sending jobs, running async code, etc).

And https://github.com/php/php-src/issues/9551 closing this...


[MSL] Conflict with Function Named Divide

I'm quite a few steps removed from spirv-cross here is all the information I have easily available, if you need more, ask and I can dig it up.
When running on MoltenVK with a shader that contains a function called divide with arguments vec3 divide(vec3, vec3) it runs into the following MSL compilation error.
[mvk-error] VK_ERROR_INITIALIZATION_FAILED: Shader library compile failed (Error code 3):
program_source:516:42: error: call to 'divide' is ambiguous
            linearBlended = srgbToLinear(divide(srgbBase, srgbOver));
                                         ^~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/32023/Libraries/lib/clang/32023.26/include/metal/metal_math:5099:19: note: candidate function
METAL_FUNC float3 divide(float3 x, float3 y)
                  ^
program_source:277:8: note: candidate function
float3 divide(float3 base, float3 over)
       ^
.
[mvk-error] VK_ERROR_INVALID_SHADER_NV: Fragment shader function could not be compiled into pipeline. See previous logged error.

I tried running with MVK_CONFIG_DEBUG=1 but I'm not getting additional messages with shader contents, maybe something is up with my logging configuration.

It looks like your shader is defining a function that also happens to be defined by Metal. SPIRV-Cross has code to remap conflicting identifiers, but it looks like we're not handling that one.


Knowledge - [SHOULD NOT HAPPEN] failed to update managedFields  error= seen in logs when deleting agent when ingestion of files is still in progress.

Steps to reproduce the problem

Create an agent with few local knowledge files.
When ingestion is still in progress, delete the agent.

Following errors are seen in logs:
ERRO[3460] [SHOULD NOT HAPPEN] failed to update managedFields  error="failed to convert new object (default/wksp1vw2g9; otto.gptscript.ai/v1, Kind=Workspace) to smd typed: .status.currentIngestionRunName: field not declared in schema" name=wksp1vw2g9 namespace=default versionKind="{\"Group\":\"otto.gptscript.ai\",\"Version\":\"v1\",\"Kind\":\"Workspace\"}"
INFO[3460] Handling request: method POST, path /workspaces/create  id=27674f36-5175-4683-93b6-f60004474e31
INFO[3460] Handled request: method POST, path /workspaces/create  id=27674f36-5175-4683-93b6-f60004474e31
warning: expected name after CMapName in cmap
INFO[3471] Deleting default/ks175vfn due to missing a1j5m99  logger=/pkg/controller/handlers/cleanup
INFO[3471] Deleting default/wksp1fvqxb due to missing a1j5m99  logger=/pkg/controller/handlers/cleanup
INFO[3471] Handling request: method POST, path /workspaces/delete  id=0e236b62-21ed-4f24-8b36-3aafb19deee3
INFO[3471] Handled request: method POST, path /workspaces/delete  id=0e236b62-21ed-4f24-8b36-3aafb19deee3
INFO[3475] Handled request: method POST, path /run       id=dbc748a3-4860-4e91-8f29-82da6f717fed
ERRO[3475] error syncing '_t default/wksp1vw2g9': handler otto-controller otto.gptscript.ai/v1, Kind=Workspace: [routes.go:91] KnowledgeSet.otto.gptscript.ai "ks175vfn" not found, requeuing
INFO[3475] Deleting default/wksp1vw2g9 due to missing a1j5m99  logger=/pkg/controller/handlers/cleanup
ERRO[3475] error syncing 'default/wksp1vw2g9': handler otto-controller otto.gptscript.ai/v1, Kind=Workspace: [routes.go:91] KnowledgeSet.otto.gptscript.ai "ks175vfn" not found, requeuing
INFO[3475] Handling request: method POST, path /workspaces/delete  id=93c5503d-772a-4351-9fc0-f27c8823fbcc
INFO[3475] Handled request: method POST, path /workspaces/delete  id=93c5503d-772a-4351-9fc0-f27c8823fbcc
ERRO[3475] [SHOULD NOT HAPPEN] failed to update managedFields  error="failed to convert new object (default/wksp1vw2g9; otto.gptscript.ai/v1, Kind=Workspace) to smd typed: .status.currentIngestionRunName: field not declared in schema" name=wksp1vw2g9 namespace=default versionKind="{\"Group\":\"otto.gptscript.ai\",\"Version\":\"v1\",\"Kind\":\"Workspace\"}"

Note - I dont seen any other issue with ingestions relating to other agents.

This error is caused when folks merge changes to the types without first running go generate. Running go generate produces no changes, so this issue has been addressed. Moving to "Testing" for verification.


Force hook standalone tests to single device

What does this PR do?
A few failures in standalone tests are due to the fact that hook tests cannot be run on multiple devices (at least the way they are written), since prepare_data only runs on rank 0. This was the cause of rather obscure failures.
Since hook tests are verifying the sanity of the sequence of hooks, it's ok to limit to single device.

📚 Documentation preview 📚: https://pytorch-lightning--20491.org.readthedocs.build/en/20491/

Does the fallback to single device defeat the purpose of the test?


Subscribe/Unsubscribe for Python Client

Implemented the unsubscribe call in init.py
Implemented subscribe and unsubscribe in the interactive client. To test execute the client and after authorization execute "subscribe Vehicle.Speed". Subsequently execute the command (e.g. tail -f /log_Vehicle.OBD.EngineLoad_1650736673.377693) printed on the client in another terminal instance.

Signed-off-by: nayakned<EMAIL_ADDRESS>

The commit 44ebac0e88653296934108d74a5437d23b9e5619 fixes the issues on subscribing on machines without xterm and also the exceptions thrown when incorrect subscription ids are passed.


What's the point using first 10,000 points in training set for training, and last 5,000 points in test set for evaluation?

I have same question.


[feat] Export/Import device configuration

Some device models (particularly Aeotec and Inovelli products) have so many configuration options, which is good, but it makes it a chore to get all of the config settings just the way you want them.  And then, after I spend a bunch of time configuring a device, let's say an LZW31-SN, if I have to exclude and reinclude the device for some reason I have to spend that time again getting the settings back to where they were.  Or, if I add an additional LZW31-SN, I bring up the configs for both and point-by-point make the new one configured the same as the existing one.
A mechanism to export and import a device's configuration, probably at least all of command class 112 and maybe also 132, would solve for both the backup use case and also the "make this device look like that device" use case.  Additionally, a way to schedule exports (or at least programmatically trigger them) would make backups even easier.
I saw #1942, but I'm not sure we're talking about the same thing.
Thanks a lot for considering!

Duplicate of #1918 . Follow updates there

Oh, I didn't see that one.  Sorry about that.

No worries :) This helps me to know where I need to focus, if it's so demanded I will give that more priority

@kdknigga BTW right now you could do that using a driver function if you are interested doing some experiment with that.


Small fixes for contributing

Hi, wanted fork the module and came across some minor issues while setting up - like missing npm dev dependencies, failed linting and a typo on package.json.
Observed that the tests are failing.
Edit: fixed the failing test, also found that it('does not match', function () {...} is wrong and doesn't test as it was xin before, but tests are failing on it. will try to fix it.
Plan to add a new method .replace for replacing all urls in a text to something.
Edit: is it really needed to filter out private ip addresses space? It narrows the usecases

Thank you

Edit: fixed the failing test, also found that it('does not match', function () {...} is wrong and doesn't test as it was xin before, but tests are failing on it. will try to fix it.
Plan to add a new method .replace for replacing all urls in a text to something.
Edit: is it really needed to filter out private ip addresses space? It narrows the usecases

Sounds like a thing to be discussed in an issue.


Publish snapshots for Python 3.12 container images.

Part of #29149

In-flight test run: https://github.com/apache/beam/actions/runs/9024733127/job/24799142929

#20 [linux/amd64 third_party_licenses 4/4] RUN if [ "true" = "true" ] ; then       pip install 'pip-licenses<5' pyyaml tenacity &&       python /tmp/license_scripts/pull_licenses_py.py ;     fi
#20 18.18 Skip pulling license for  bs4
#20 18.18 Traceback (most recent call last):
#20 18.18   File "/tmp/license_scripts/pull_licenses_py.py", line 190, in <module>
#20 18.18     raise RuntimeError(
#20 18.18 RuntimeError: Could not retrieve licences for packages ['pyproject_hooks'] in Python3.12 environment.

New run: https://github.com/apache/beam/actions/runs/9025292420/job/24800756821


[FLINK-18700][FLINK-18705][debezium] Fix Debezium-JSON throws NPE when tombstone message and PG table's IDENTITY config is not FULL

What is the purpose of the change

Fix NPE when tombstone message is received
throw a better exception message instead of NPE when PG table's IDENTITY config is not FULL.

Brief change log

Skip null or empty input data in DebeziumJsonDeserializationSchema.
check if "before" is null, then throw a better exception message

Verifying this change

Tests are added in DebeziumJsonDeserializationSchemaTest.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @leonardBang

Merging...


Better Error Logs

The Errors logs just shows Go's usual Panic Output. Maybe we could wrap an abstraction for that. Like
Request Error or Check the URL/URI and Authentication

I have this working. Errors are bubbling up instead of panicking, and some of them have added context to the error. I'll wait till PR #9 is finished and merged, before I open a PR.

🤩


Display User Details for Task Progress Updates

Date: 10 Dec 2024

Developer Name: @AnujChhikara

Issue Ticket Number

Implement User Attribution for Task Progress Updates
Description
This PR  implementing a feature to display the details of the user who made the task progress update. The user image will be shown as a clickable link that leads to their user management page, ensuring accountability and transparency in task progress updates. When you hover over the user image it also show their username.

Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[x] Yes
[ ] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Updated UI

Mobile UI

Dev Flag Working

Test Coverage

Screenshot 1

Additional Notes

Currently, the progress data does not include the userData field. After discussing with Ankush, we decided to proceed with the frontend changes behind a feature flag. Once this is complete, I will work on the backend implementation.

To handle the ?dev=true query parameter, I utilized useRouter in the code. In the tests, I mocked useRouter to simulate scenarios where the dev query parameter is set to true or false.

Additionally, I wrote extra tests to improve the overall test coverage.

Design Doc

Can you please add mobile UI changes recording also.

Can you please add mobile UI changes recording also.

added


Program ip:port combinations as possible host headers in virtual_host.domains for HTTP routes

Please describe the Improvement and/or Feature Request
Currently, OSM only programs service FQDNs (foo.bar.svc.cluster.local, foo.bar, etc.) as a part of virtual_host.domains in the route configuration. However, the HTTP request could have a host header corresponding to the IP:Port combination (ip:port, ip), in which case traffic will not be allowed because of ip:port not being programmed as acceptable domains.
Scope (please mark with X where applicable)

New Functionality          [ ]
Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [X]
CLI Tool                   [ ]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [ ]
CI System                  [ ]
Project Release            [ ]

Possible use cases
Allows HTTP requests to a service when the host header is not based on the service's FQDNs, but rather ip:port combination.

What would the SMI policies look like in this scenario?

What would the SMI policies look like in this scenario?

The SMI policies would not influence the IP:Port combinations that a client could use to access the destination. This issue was more applicable to ingress than SMI, where ingress controllers can route HTTP traffic directly to service endpoints rather than the service IP (clusterIP).  However, with the latest Ingress implementation, this capability is no longer necessary.
It's also possible that clients use an IP address to access a destination, such as when they configure probes (not necessarily k8s probes) to check if the endpoint is alive, in which case they are going to have to use the endpoint IP instead of service FQDN to route it directly to a service's endpoints.


Decouple OVR

OVR is used at the moment for its OVRSkeleton capabilities. Find a way to decouple it so other hand tracking solutions can be added such as Leap Motion or Hololens

Using IGrabNotifier and SkeletonData provider


[KARAF-6009] Be able to add filter on elasticsearch rest appender

I add a new property in the config file to declare a filter:
index.filter
Also, to use factory, I changed the default configuration file name:
org.apache.karaf.decanter.appender.elasticsearch.rest-default.cfg

@jbonofre I made the changes, can you review please ?


Issue #2370 Don't use custom action to delete install folder during uninstall

Use wix RemoveFile element which is more fault tolerant then the custom action
Fixes #2370

/retest


Add option to switch count from unread to all notifications

Allow attribute to notification bell web component to enable display of all notifications rather than just unread.

@bjagg the icon currently lists all notifications. Are you referring to the notification count number on the badge?

Yes, per title. I'll update the description


spatial_cnn overfitting

hello all,
when i run the spatial_cnn.py, i found the loss function for test is very strange. does someone have the same problem?
many thanks!

Hello, I am preparing to run this model. I don't know what this specific environmental requirement is. I want to ask you, thank you very much!

我也碰到了过拟合的问题，请问楼主后来解决了吗？

@Robinxin123 Can you tell me the learning rate you are keeping?
I am getting these result, prec@1 and prec@2 on just two epochs but this is really so strange?

Should I run all 500 epochs for training only? then check the validation or should I run both? because the epoch for validation is taking 21-22min and 19-20 mins for training, add them it will be 40mins, for each epoch it is taking 40 minutes. If I run it for 500 epochs it will take almost 13 days for training validation, I am using RTX 3080 10 GB + i9 10th generation.


Remove classifier from published jar

without this the jar gets published to jaxrs-clients-all-1.0.0-rc4-all.jar. the extra -all directly before .jar is incorrect

@uschi2000 tested this locally and we're now pulling in the jaxrs clients jar correctly. without this change we would get the pom file correctly but be missing the jar. @nmiyake for SA