We need a real name for the shading language...

Right now it's just SDL Shading Language (SDLSL).
Which is fine, whatever, but maybe something better would be nice, if anyone has a good idea.

I'd not worry for the name for it yet, unless you want to advertise it straightaway.
Why not any of the following?

DMSL - DirectMedia Shader Language

Maybe pronounce it (or even write it) as Damsel?

ISLE - The Icculus Shader Language Extraordinaire

Naming things after yourself is always a good idea! Linux and Git and both named after Linus Torvalds after all)

Iccken or Slolus

Share the love and name it after yourself and slouken

Sizzl

SDL Shader Language -> SSL -> Szl -> Sizzle -> Sizzl
Because you want to date your name to a fashion from 10 years ago of dropping vowels)

Athena, Minerva, Ptah, or Bragi

Who doesn't love naming a language after a god? 👀

Linux and Git and both named after Linus Torvalds after all

Hah!

Honestly, SDSL would be perfect for multiple reasons:

GLSL and HLSL both have 4 letters, and end with SL, so SDSL already fits right in.
It could just stand for Simple DirectMedia Shader Language, which is logically sound.
It doesn't stray too far away from SDL's name itself, as much as I love the other options, this is important.

SDLSLSL ;P
SDL Simple Little Shader Language

Tesseract
You can project a tesseract into 3D space into various different ways. Be it cell-first, face-first, edge-first or vertex-first. In a way, its like translating the higher dimension geometry into a simpler dimension.
One of the stated goals with SDL Shader Language was to compile down to a bytecode, then be able to translate that bytecode into another.
Since Shading Languages can deal with geometry, it seemed fitting to me. Or maybe I'm thinking too much and trying to compare apples (translating bytecodes) to oranges (projecting higher dimension geometry to lower ones).

Tesseract

I'm probably not going to do this, but I really want to do it for the A Wrinkle in Time reference.   :)

I'm late to the party but

Tesseract
might lead to confusion with the open source Tesseract game (tesseract.gg), maybe

I'm not a fan of acryonyms so I think I'll keep saying "SDL shader language" because the association is simple.

"ah, it's SDL 's shader language"
Meanwhile, if a project using a lot of acronyms already may lead to a letter soup
"what does < insert 7 digit long acronym here > even mean? What is WTFPL, what is DX12?"

Why not simply use the WebGPU Shader Language (https://www.w3.org/TR/WGSL/), It aims to be a cross platform one.
Why create another one? It feels like How-Standards-Proliferate yet again.

SDLSL is perfectly fine in my opinion. Simple and to the point, just like the language itself is presumably supposed to be.

Why not simply use the WebGPU Shader Language (https://www.w3.org/TR/WGSL/), It aims to be a cross platform one.

https://github.com/libsdl-org/SDL_shader_tools/blob/main/docs/README-SDL_gpu.md#why-a-new-shader-language

Why not simply use the WebGPU Shader Language (https://www.w3.org/TR/WGSL/), It aims to be a cross platform one.

https://github.com/libsdl-org/SDL_shader_tools/blob/main/docs/README-SDL_gpu.md#why-a-new-shader-language

Disclaimer: I'm in the peanut gallery with respect to SDL_gpu, but have been a long time SDL user, but I think the rationale articulated here needs to be rethought, or reworded.

HLSL, GLSL, and Metal Shader Language are all fairly complex languages, so to support them we would either need to build something that handles all their intricacies, or pull in a large amount of source code we didn't write and don't have a strong understanding of...including, perhaps, a dependency on something massive like LLVM.

They are complex because shading is complex. Control flow, barriers, wave/group semantics, data uniformity, execution uniformity, helper lanes, and all sorts of constructs need semantic grounding in the language. Some of the complexity is accidental, sure, but a lot of it is not. And something "massive like LLVM" isn't all that massive when juxtaposed with the problems that need to be solved.

By writing the compiler ourselves for a simple language, we could guarantee it'll be small, run fast, offer thread safety (so you can distribute compiles across CPU cores), accept a custom allocator, and be easily embedded in offline tools and also in games that want to compile shaders on-the-fly.

Nobody I know in the industry cares about parallel computation of an individual shader. If you author a shader where this performance delta would be important, you've likely hit your GPU's shader instruction limit. We gain throughput by compiling many shaders in parallel (and games ship hundreds to tens of thousands of them).
Furthermore, existing compilers like DXC already support custom allocators directly, and this is common practice in all major game engines.

Tools are readily available that will translate shader source from one language to another, so our gamble is that in the worst case, it's just one more target and developers can write in HLSL/GLSL as they would anyhow.

More often than not, these tools do not exist, are not integrated, or are bad for various reasons (bad source mappings, or at the very least, another artifact you need to carry around in your debug pipeline). It's important for tools like PIX, RenderDoc, RGA, NSIGHT, and a plethora of other tools to be able to map bytecode back to source code. Most of these tools support HLSL and GLSL and I have no idea what "source to source" translation tools are integrated in any of the above.

But also...I think this is worth saying out loud: almost every popular shading language made a conscious choice to be as close to C code as possible, and we can make some changes to that syntax to make a better language. We don't have to reinvent the wheel here, just make it a bit more round.

HLSL has templates. Templates! And classes, inheritance, namespaces, interfaces, and plenty of other constructs that don't resemble C. Making a new shading language is reinventing the wheel by definition...

And something "massive like LLVM" isn't all that massive when juxtaposed with the problems that need to be solved.

What do you need LLVM for in a basic transpiler? You can leave complex optimization passes to the backend, that's probably a better idea anyway.

We gain throughput by compiling many shaders in parallel (and games ship hundreds to tens of thousands of them).

The paragraph you are quoting is talking about parallel shader compilation, not computation.

HLSL has templates. Templates! And classes, inheritance, namespaces, interfaces, and plenty of other constructs that don't resemble C. Making a new shading language is reinventing the wheel by definition...

I don't think SDLSL (or whatever the name ends up being) really needs any of those things. Just being able to write truly cross-platform shaders without crazy preprocessor hacks, and to compile them at runtime without a massive dependency, is much more valuable for me. As far as I'm aware, that wheel hasn't been invented so far, and it's a damn shame.

More often than not, these tools do not exist, are not integrated, or are bad for various reasons (bad source mappings, or at the very least, another artifact you need to carry around in your debug pipeline). It's important for tools like PIX, RenderDoc, RGA, NSIGHT, and a plethora of other tools to be able to map bytecode back to source code. Most of these tools support HLSL and GLSL and I have no idea what "source to source" translation tools are integrated in any of the above.

 If SDLSL shaders can store some basic debugging information like variable and function names, and the transpiler is able to translate that into the backend format (e.g. SPIR-V), which can be decompiled into GLSL or HLSL by those tools, that should be good enough for debugging. It'll probably end up being pretty close to the actual source code too, if the language is kept simple.

What do you need LLVM for in a basic transpiler? You can leave complex optimization passes to the backend, that's probably a better idea anyway.

It's not just LLVM, in the case of DXC, it's clang, which provides a full frontend with diagnostics and other features that operate on the AST itself, in addition to reflection capabilities used to reflect bindings, struct layouts, and other such niceties.

The paragraph you are quoting is talking about parallel shader compilation, not computation.

Yes obviously.

I don't think SDLSL (or whatever the name ends up being) really needs any of those things. Just being able to write truly cross-platform shaders without crazy preprocessor hacks, and to compile them at runtime without a massive dependency, is much more valuable for me. As far as I'm aware, that wheel hasn't been invented so far, and it's a damn shame.

The premise of the original statement was that "other languages are just based on C" which is trivial to refute. It honestly probably only applies somewhat to GLSL, but even that's not entirely fair.

 If SDLSL shaders can store some basic debugging information like variable and function names, and the transpiler is able to translate that into the backend format (e.g. SPIR-V), which can be decompiled into GLSL or HLSL by those tools, that should be good enough for debugging. It'll probably end up being pretty close to the actual source code too, if the language is kept simple.

Getting symbols to show up properly for an NSIGHT capture is non-trivial, even if you go the DXC -> DXIL route. If you have a custom shading language, have fun, but good luck when you're trying to diagnose a bad page fault or performance issue.
If you want to make your own shading language and bytecode "just because," go for it, but the rationale as stated makes little sense to me.

If using SDL_gpu means pulling in a big 3rd-party shader compiler and possibly a large WebGPU/WGSL runtime, well then forget it.
The point of SDL_gpu doesn't seem to be for ultra-high-performance AAA-quality 3D graphics anyway, but instead for developers that want less demanding 3D (or 2D with shaders) without having to write and maintain their own backends for each platform they want to support. Using WGSL would mean having to add a lot more complexity and surface area to the SDL_gpu API to support all the additional complexity of WGSL.

Let's not all have this argument in the "what should we name the shading language?" issue, please.

Was wondering why I was getting so many notifications all of a sudden from this.
SDSL is still what I call it, because it has the same rhythm as GLSL/HLSL. And frankly -as I stated preciously- it makes the most sense.
All other tangents here are just cluttering this space, and they're all redundant towards the original question. It's up to icculus to choose regardless


Feature request: Support use ctrl/cmd+n to switch files or terminals

Is your feature request related to a problem? Please describe.
I'd better using keyboard all the time when I working with code (It will improve my speed).
But I must use my cursor to switch file if I am working with multi files.
Describe the solution you'd like
Use ctrl(On Windows/Unix) or cmd(on MacOS) + n (A number key 1-9 left 9 files, and 0 as the most right one ) to switch file
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I believe Linux typically uses Alt+n.

I believe Linux typically uses Alt+n.

So it could be configured


Dockware image: 'dockware/dev:<IP_ADDRESS>" mysql server not able to start

I wanted to get a dev environment, dockware/play:<IP_ADDRESS> works just fine, dev is not able to start mysql server

hi
can you try to delete all internal volumes and see if it works then? thank you

Hey there,
thx for your reply. That didn't do the trick, I use Docker 4.19 btw
Anything else I could try?

I did delete all images and local containers

hi
from the last line i can see there is a localhost-root entry
could it be that you have a mounted database? there is still something existing
and what just happens is that there is a mysql error being thrown...if you could help me to understand what is in the domain table in your database then i can see if i can do anything more fail-safe in that script
i think its the script for domain changing
also...sry i could have seen that earlier....thought its a starting mysql failed error

We found the error in the docker-compose.xml
version: '3'

services:

  shopware-update:
    container_name: shopware
    image: 'dockware/dev:latest'
    ports:
      - "22:22"     # ssh
      - "80:80"     # apache2
      - "8888:8888" # watch admin
      - "9998:9998" # watch storefront proxy (not needed if you start with "make watch-storefront")
      - "9999:9999" # watch storefront
    networks:
      - web
    environment:
      - MYSQL_USER=sam
      - MYSQL_PWD=root
      - PHP_VERSION=8.2

networks:
  web:
    external: false

# docker-compose up -d

environment:
  - MYSQL_USER=sam
  - MYSQL_PWD=root

Needs to be deleted

aaa custom mysql user creation in mysql8 then
i think my colleague has fixed this in the v2 version
need to double check it
thx for your help

Same problem here. If i set MYSQL_USER and MYSQL_PWD environment variables, i get the following error:
ERROR 1062 (23000) at line 1: Duplicate entry 'localhost-root' for key 'user.PRIMARY'
using
`*******************************************************
** DOCKWARE IMAGE: dev
** Tag: <IP_ADDRESS>
** Version: 1.6.0
** Built: Tue Jul  4 20:40:47 UTC 2023
** Copyright 2022 dasistweb GmbH

`

Hi,
the difference is that the entry (host=localhost, user=root) already exists in mysql.user table. As such it fails on this line in the entrypoint.sh which is only hit when MYSQL_USER and MYSQL_PWD variables are set.
I ran two containers without those variables set. One older one with tag <IP_ADDRESS> and a newer one with <IP_ADDRESS>:
Then I checked the entries in mysql.user table:

You can see that the old working image does not have an entry for root@localhost, while the newer one does.
Doing some history digging, I found a commit which I think broke it.
You can see that the prior SQL query was removed:
use mysql; update user set host='%' where host='localhost';

Instead two new were added.
 TO 'root'@'%' WITH GRANT OPTION;FLUSH PRIVILEGES

The result is an entry root@localhost which then fails in the entrypoint.sh.
The original intent of the entrypoint in the custom mysql user case is to "block remote access for root", which is not needed anymore when a custom mysql user is given. Instead of the update query, a delete query for root@'%' might do the job here.


Refactor modules to comply with architecture proposal

Add security components and background services access.
Status: Done first draft for background services.
WIP: Security components

The pending responsibilities from this issue are related with #3 . So this ticket will be close.


feat: implement 0xF4 - DELEGATECALL

Since
Byzantium
Group
System operations
Description
0xF4 - DELEGATECALL
see https://www.evm.codes/#f4?fork=merge

First implementation is proposed by @ClementWalter in https://github.com/sayajin-labs/kakarot/pull/335, will need a few tweaks to be fully operational:)

See comment for issue #256


new subroutine for nicer layout of user variable (LET) definitions

Reported by steven c hankin on 7 Nov 2013 23:30 UTC
This routine would be useful in SHOW VAR and SHOW VAR/TREE (and elsewhere).
A definition like
LET v = IF cond1 THEN exprn1 ELIF cond2 THEN exprn2 ELSE exprn3
should be laid out as
IF cond1 THEN
expr1
ELIF cond2 THEN
expr2
ELSE
exprn3
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2102

Comment by steven.c.hankin on 8 Nov 2013 00:07 UTC
oops.  Ansley pointed out that our LET syntax doesn't include an in-line ELIF.  It is only available as a syntax to control the flow of execution of lines in a script file.


Fix legacy build to be ES3 compatible

The legacy build should not include ES6 syntax, but currently the webpack preamble, contains an arrow function.
This change configures webpack to use a preamble that is ES3 compatible, only for the legacy build.

The legacy build should not include ES6 syntax, but currently the webpack preamble, contains an arrow function.

Yes, and that should be OK since we no longer support any environments/browsers without e.g. arrow functions; please refer to https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support for the (current) support information.

This change configures webpack to use a preamble that is ES3 compatible, only for the legacy build.

Sorry, but I really don't think that it makes sense for us to re-introduce support for old and discontinued browsers (since that'd unnecessarily increase the maintenance/support burden).


Xcode 10 fails

Xcode 10 won't complile Utils.swift...
Reason:
Voodoo CharRanges are too big for the compiler -> Time out!!!
Take a look here:
private static let headCharRanges: [CountableClosedRange]
Solution:
A quick fix or hack is to split the array in small arrays and combine them later.
Note:
"...Du kannst von Glück sagen, dass ich meine Hose noch an hab" ;-)

Project now builds again on Xcode 10 without the necessity for hosen and wrappers.


Should I add children to sprites instead of creating containers for performance?

I've been seeing a few GitHub issues within this repository lately about adding sprites/graphics/text inside other sprites/graphics/text lately (which I didn't think you could do, coming from a flash/AS3 background) asif each sprite/graphics/text also acts as a container, is this method faster for rendering?
for example I created a toggle button (checkbox) with this structure
-container (container)
---on state (sprite)
---background (sprite)
and then I add a mouse event to the container to toggle the visibility of the onstate sprite.
whereas from what i've read recently i can do this
-background (sprite)
---on state (sprite)
This is the simplest example I could think of but I'm using the container method multiple times across many menus
Does the method without the container make any considerable difference in rendering performance? shy of reducing the computation loops by 1, which in my experience on mobile platforms, rendering is the bottleneck for performance.

if each sprite/graphics/text also acts as a container, is this method faster for rendering?

They are containers, they act exactly like containers, no difference.

Does the method without the container make any considerable difference in rendering performance?

Not really, wide scene graphs are better than deep ones but the difference between one or two sprites really just doesn't matter.


sworkstyle consuming all CPU after switching to i3

Hey,
I guess this is a minor problem, nevertheless I think it is worthwhile reporting: Occasionally I start sway (with sworkstyle running), but then (have to) switch to i3 for some reason. In this situation, sworkstyle keeps running in i3 and keeps consuming 100% of CPU (which is not that surprising in an i3 session, but still annoying) and the process has to be killed.
My expectation was that sworkstyle would terrminate once the sway session is closed.

Not sure what you use to switch wm, but if you fully exit sway it should close all programs inside it including that ones that started with exec. Also not really a sworkstyle problem I think more with the general setup.

Mabye you're also running multiple sworkstyle sessions, that's why it's running with 100%?

Hi,
I switch WMs by closing all programs, exit sway via the swaynag keybinding and then login to i3 via the display manager.
So sworkstyle should be closed as all other programs started at login (such as waybar, dropbox, and so on).
There is only one instance of sworkstyle running, which is consuming 100%.
I start sworkstyle as shown in the README:
exec sworkstyle &> ~/.cache/sworkstyle.log

Can you share output of sworkstyle --log-level=debug

Sure, see here. (## are comments).
   1   │ 2021-07-20 21:33:54,116 DEBUG [sworkstyle] Subscribing to window events
...
  12   │ 2021-07-20 21:35:03,944 DEBUG [sworkstyle] rename workspace "3:  " to "3"
  13   │ 2021-07-20 21:35:08,490 DEBUG [sworkstyle] rename workspace "2:  " to "2"
  14   │ 2021-07-20 21:35:14,281 DEBUG [sworkstyle] rename workspace "1:  " to "1" ## logout and re-login now
  15   │ 2021-07-20 21:35:17,093 DEBUG [sworkstyle] rename workspace "1" to "1:  " ## logged in i3

and nothing afterwards. Line 15 is the first and last line logged in i3, no matter what I open/close, nothing will be logged anymore in sworkstyle.log.
Furthermore, when starting with sway, I find two processes with ps aux:
myuser      783  0.1  0.0   7256  2908 ?        S    21:15   0:00 /bin/sh -c sworkstyle &> ~/.cache/sworkstyle.log
myuser      788  0.1  0.0 750412  3512 ?        Sl   21:15   0:00 sworkstyle  ## 100% CPU

where the second process is the one using 100% CPU in i3.
Does this info help?

Yeah so it makes sense that it will be 100% due to the two processes fighting each other on renaming workspaces.
When you use the latest version of sworkstyle it will actually check for other running instances. This will ensure that there always is only one running instance.
Might want to use the latest version and see if the issue persists.

I am on arch and I am using sworkstyle 1.1.0-1 from the AUR, which is (I think) the latest version, right? So this occurs also with the latest version.

Also, one or two processes does not really matter, if they don't exit when I exit sway, no?

When running one instance can you check if /tmp/sworkstyle.lock exists? Does it start when you open a second instance? Two processes does matter due to high cpu usage when there are multiple instances.

When running one instance can you check if /tmp/sworkstyle.lock exists? Does it start when you open a second instance? Two processes does matter due to high cpu usage when there are multiple instances. I'll have to look into it keep running after closing sway.

Yes, the lockfile does exist (it's empty though). When I manually try to start another sworkstyle process, it errors out with stating that 'Sworkstyle already running'.

First off, this package is great and thanks for all your hard work!
I'm experiencing similar behavior as @zauster but without i3 (exit sway then log back into a sway session). The workspace icons no longer show up and sworkstyle is consuming ~100% of the CPU usage.
Just wanted to share before I forget, I will try to find time to dig deeper this week.

So this happens after logging out (back to gnome display manager) and logging back in. Regardless of whether you starting an i3, gnome session, etc. etc.
After logging back in, the icons no longer appear and sworkstyle is running rampant on the cpu

I get in this situation if wayland crashes and I restart it. There's one process clipping the CPU. I'm starting it with exec sleep 3 && sworkstyle & (the sleep part is just to deprioritize the process startup, shouldn't affect the termination afaik).

I think I may know what's going on... I noticed as well that sworkstyle keeps running after quitting sway, you can easily see this by running
user@foo$ swaymsg 'exec --no-startup-id sworkstyle'
user@foo$ swaymsg exit

Then logging on another TTY and running top will show sworkstyle still running at 100% CPU ujse.
I think the problem is that when the connection to the way IPC is broken, the loop here turns into an infinite loop:
https://github.com/Lyr-7D1h/swayest_workstyle/blob/da48e5eb5e0d3eced367805ad2c8c6a22efe289b/src/main.rs#L143
To fix it, it should be enough to add some error handling like so:
diff --git a/src/main.rs b/src/main.rs
index 64a9740..d79ea9e 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -8,7 +8,7 @@ use args::Args;
 use async_std::prelude::StreamExt;
 use config::Config;
 use fslock::LockFile;
-use log::{debug, error};
+use log::{debug, error, warn};
 use simple_logger::SimpleLogger;
 use swayipc_async::{Connection, EventType, Node, NodeType};

@@ -145,6 +145,9 @@ async fn subscribe_to_window_events(mut config: Config) -> Result<(), Box<dyn Er
             if let Err(e) = update_workspaces(&mut con, &mut config).await {
                 error!("Could not update workspace name: {}", e);
             }
+        } else {
+            warn!("Connection broken, exiting");
+            break;
         }
     }

Thanks @joanbm I've implemented your solution I'll try and see if this solves the problem.

@joanbm it seems it solves the problem! Big thanks for your help @joanbm !!!!! :100:


add phpdoc to every method for autocompletion

add phpdoc for the methods, so with the barryvdh/laravel-ide-helper there is autocompletion with IDEs like PhpStorm

Coverage remained the same at 94.647% when pulling aec7d9f096a5d25200259a41a27c205ed5095747 on bussnet:master into 8056cea6743de85e079d69bc43ee8e358553a9a7 on adamwathan:master.

now fixed the messed up indention

Coverage remained the same at 94.647% when pulling 398e247cdd21cff09c466990e5e0dd37d10a3f78 on bussnet:master into 8056cea6743de85e079d69bc43ee8e358553a9a7 on adamwathan:master.

I feel for this to be accepted there should also be descriptions
@param string $value

@param string $value Blah blah blah

I'm not worried about the descriptions at all, honestly. Will merge this if you can fix the merge conflicts @bussnet, thanks!


Simplify package name

dnsinfo is easy to read, type and remember. Let's ditch the -

Or dns? 🤷♂

❤
On Mon, 30 Oct 2017 at 10:02, Sebastian De Deyne<EMAIL_ADDRESS>wrote:

Or dns? 🤷♂
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spatie/dns-info/issues/3#issuecomment-340382423, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdiDWybrH09mgGJIEr6xfpfrSJA_PM_ks5sxZCvgaJpZM4QK0ZK
.

--
Freek Van der Herten https://spatie.be +32 495 84 27 91

Renamed to Dns 🎉


iOS - Player closes after preroll and new player opens to play new content

If you view one of the samples on iOS (https://googleads.github.io/videojs-ima/examples/simple/), you can see after the preroll finishes you briefly see the main webpage again, then the video opens in a new view. Is there a way to have the main content play in the same view the preroll is shown in?

Hi @TylerZubke ,
I wanted to ask if you are still experiencing this issue, or if you had found a solution to it?

@Kiro705
I ended up using a different plugin on iOS because I couldn't get around this issue. I'll try the newest version of this plugin at some point and see if the issue is still occurring.


pdm-project as a Verified Creator

Hello. I was wondering if there were any plans for pdm-project to become a Verified Creator on Github?
Apologies as this is not necessarily an issue, but just wanted to raise as some organisational policies can restrict Actions usage based on this status. Appreciate all of the work you do on this project, thanks.

+1 It would be nice to see this implemented

It's not on the main path of the project. So +1 if anyone would like to contribute. But I will be using the GitHub actions for now

Right now the issue is that any repository with DCO requirements enabled cannot merge the auto-generated PR, since the workflow is not embedding the required "signed-off-by" tag in the commit message. I assume that is why this issue has been raised? Right now, anybody requiring DCO has to pull down the PR and amend the commit message to manually add this. Seems to break the whole concept, which is to schedule the action and make the update easier to perform; i.e. just check the PR content and merge it. This creates some unpleasant additional friction. I could maybe take a look at this in the future, but I'm short on time right now.

Actually, it seems that these issues are separate, although I think the publisher verification would still have merit, given the standing of the PDM project. I'm going to raise an issue at the repository here for my query above: https://github.com/pdm-project/update-deps-action

Frost Ming,
You have requested whether anybody from the community would like to pickup this action (to contribute time/effort to get the PDM project added as a Github verified creator). I work for the Linux Foundation and would happily work with the project to deliver that, although right now I have no particular affiliation with the PDM project/organisation. How might we proceed if I was to volunteer?

Matt

@ModeSevenIndustrialSolutions You can join the discord and we can start the chat there: https://discord.gg/Phn8smztpv

So, I believe the steps required to get listed as a GitHub verified publisher is simply documented here: https://docs.github.com/en/apps/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization
GitHub Docs
Applying for publisher verification for your organization - GitHub ...
This looks to be really straightforward; you need to generate a TXT token in the GitHub portal and add that to your project's DNS records. Once the DNS record is added, it is just a few more clicks in the GitHub portal, really only ten minutes work in total. This does require a user account with access to the GitHub ORG (which I don't have for PDM), and the ability to add a DNS record to the project domain: pdm-project.org
It would seem to be a good idea to get this small piece of admin done? It links the PDM project site in a verified way to the related content on GitHub. I think this helps users confirm that they are dealing with the project and original content, not forks and other potential sources of confusion?

Should I close this issue and create one containing the information above under the main PDM project GitHub page/area?

Should I close this issue and create one containing the information above under the main PDM project GitHub page/area?

Sure, I can close this one after you have created a new.

See: https://github.com/pdm-project/pdm/issues/2557
Feel free to proceed and close this issue!

Sorry, I still can't understand why verified creator is related to this "GitHub action".
All documents referred here say it applies to a published "GitHub App", and the verified creator tab in org settings also says:

There must be 1 or more GitHub/OAuth App registered by the organization to request publisher verification

This action, is obviously not an App.
If you mean a pull request initiated by a bot can't comply with your security policy. You can use a Personal Access Token associated to a member of your organization and use it as the token value:
steps:
      - uses: actions/checkout@v3

      - name: Update dependencies
        uses: pdm-project/update-deps-action@main
        with:
            token: ${{ secrets.GH_PAT }}

I think it's the marketplace that is the common element.
The bottom of this page would suggest verification can be applied to actions?
https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace
At the end of the day, validating your domain and authenticity in this case is not a huge amount of work. Why the resistance? ;-)

Here is I think a good example of why some people feel this is worth pursuing:

There's a configuration option for:
Allow actions by Marketplace verified creators

The request is pending review

Exactly as @ModeSevenIndustrialSolutions mentioned.
I'm seeing a lot of larger organisations that look towards new tools adoption have this restriction in place.
Thanks for considering this!

Fine, it's more difficult than you and me would think to gain such a badge.

GitHub Docs Applying for publisher verification for your organization - GitHub ...
This looks to be really straightforward; you need to generate a TXT token in the GitHub portal and add that to your project's DNS records. Once the DNS record is added, it is just a few more clicks in the GitHub portal, really only ten minutes work in total. This does require a user account with access to the GitHub ORG (which I don't have for PDM), and the ability to add a DNS record to the project domain: pdm-project.org

I doubt if anybody in this thread has succeeded in publishing a verified action into marketplace. I've finished the steps mentioned above and finally get approved. To prove i am not lying, here it is:

But you as you can see, the published action still doesn't get a "Verified" badge. The place seems to be related to OAuth Apps and GitHub Apps only, which I've repeated many times but nobody hears.

All documents referred here say it applies to a published "GitHub App", and the verified creator tab in org settings also says:

There must be 1 or more GitHub/OAuth App registered by the organization to request publisher verification

This action, is obviously not an App.

However, at the bottom of this page(thanks to @ModeSevenIndustrialSolutions ), it seems to mention Action badge, but that requires the org to be a partner of GitHub and I have to fill in a partnership form which I don't think eligible for PDM org.
Also look at the list of verified actions, all belong to a startup company or tech organizations much bigger than PDM.

Alternatives for you with such restrictions:

setup-pdm: actions/setup-python + pipx install pdm
update-deps-action: set up a periodic workflow to run pdm update

Thanks frostming; I do think GitHub could be clearer on the benefits and the actual process involved. I did read the partnership documentation, and it does indeed seem to be geared towards larger commercial entities, primarily selling GitHub applications. I guess that might change, and could later be adapted to better suit smaller open source projects. If the work/effort gets parked here at this point, then we can always wait until the situation changes or we get some clarity? If this ticket were to stay open, then at least the conversation is logged and available as a record of the issues and related discussion.

Just noticed that pdm-project is now a Verified Creator!
See 'Verified' badge on project homepage:
https://github.com/pdm-project
Thanks so much @frostming 😄


Resolve TODOs in class documentation

Godot version
master branch
System information

Issue description
I randomly stumbled upon one of these documentation TODOs, and I couldn't find an issue tracking these...
Current state of the class docs in master branch:

[ ] Control.xml:11 - [b]FIXME:[/b] No longer valid after DisplayServer split and Input refactoring.

Will be fixed by #65424

[ ] Geometry2D.xml:161 - // TODO: This code is not valid right now. Ping @aaronfranke about it before Godot 4.0 is out.

@aaronfranke not sure if this comment still applies?

[ ] ProjectSettings.xml:1700 - [b]FIXME:[/b] No longer valid after DisplayServer split:

Should probably be replaced by OS.get_current_rendering_driver_name but this method is not currently bound.

[ ] RenderingServer.xml:3084 - FIXME: The method seems to be non-existent.

Can't find any set_attach_to_screen_rect or related method in the current code base. Not sure what the new approach for this is.

[ ] SurfaceTool.xml:89 - [b]FIXME:[/b] Document possible values for [param flags], it changed in 4.0. Likely some combinations of [enum Mesh.ArrayFormat].

Seems to be all ARRAY_FLAG_* but I can't really confirm.
Parameter is called p_compress_flags in C++, so the bound argument name might need to be updated as well?

Steps to reproduce
Search *.xml documentation files for (TODO|FIXME) to find them.
Minimal reproduction project
No response

I ran VSCode's search tool for "TODO" and there are 1385 results across 568 files and 245 results across 151 files for "FIXME". VSCode even hung up for a moment.
How the hell did it get this bad?

@atirut-w This issue is about the class documentation so you should filter on *.xml only.
Other TODOs in code can be there for a variety of reasons, quite often as a hint for future self or future contributors that things could be improved in terms of code quality/performance. It's not particularly "bad" as you point it out, it's one aspect of code documentation to be able to point out what could be improved even if it's not critical to do it at a given point in time. In other cases, it does point at missing features / bugs that need to be solved, and those cases can be worth tracking in dedicated issues.
Finally, you should exclude thirdparty code when you search, we don't care about other projects' internal hints for future potential work.
$ rg "TODO" | wc -l
1374
$ rg "TODO" -g'!thirdparty' | wc -l
510


Use Base64 string as source

Hi,
Is it possible to use a base64 string a source?

Yes. See this example. I didn't want to make the URL enormous, so the image is very low resolution.

I would not recommend specifying an image as a URL parameter (as I just did), at least with the current release, since the entire image is sent to the server. I just added support for using the fragment identifier, which isn't sent to the server, instead of the query string (# instead of ?), so it will at least be feasible to do with the next release, although I still wouldn't recommend it.
Using a base64 encoded image in a JSON configuration file or with the API should be fine with the current release.

@mpetroff when looking at your example i only see the following:

Apparently it works fine on Firefox but doesn't work with Chrome. Making it work on Chrome would require restructuring how images are loaded, which I don't really want to do, since I generally don't think using base64 encoded images is a good idea. Blob objects are better suited for passing around image data client-side.

I used a work around for this, Hope it helps:
    var imageToUse = angular.copy(base64Image);//Here you get the image
    var base64DataPrefix = imageToUse.substring(0, imageToUse.indexOf(',')+1);

/Getting the browser prefix for parsing the image in case it's retrieved, in case not use the atob function directly on the retrieved data/
var binaryStringData = imageToUse.substring(imageToUse.indexOf(',')+1, imageToUse.length);
var binaryString = window.atob(binaryStringData);
var binaryLen = binaryString.length;
var fileContent = new Uint8Array(binaryLen);
for (var i = 0; i < binaryLen; i++) {
var ascii = binaryString.charCodeAt(i);
fileContent[i] = ascii;
}
var blob = new Blob([fileContent], {type: 'application/octet-stream'});
var fileURL = window.URL.createObjectURL(blob);
    setTimeout(function() {
      pannellum.viewer('panorama', {
        "type": "equirectangular",
        "target":"_blank",
        "panorama": fileURL,
        "title": 'hello image',
        "multiRes":{
          "tileResolution": 512,
          "cubeResolution": 8432
        }
      });
    }, 250);

Hello, and thank you in advance for your time.
If I create a new image with JS and then set the image source, how would I set this image in pannellum? Otherwise, if I have a blob, then how do I set the image of pannellum to be a blob? I only see a way to set the panorama which has to be a string, which seems like the base64 is the only other option along with the URL. I see that you mentioned Blob objects in the two tickets concerning this, but I cannot find an example of getting this accomplished, and the documentation seems to only support a string.
I saw that the renderers init configuration allows you to pass an Image object, would this be the only way to get it done? Can you provide more information for getting this accomplished, or at least point me in the right direction please. Thank you.

You need to create a blob URL from the blob object, e.g. var url = URL.createObjectURL(blob);, where blob is the blob object. The returned URL will start with blob:. This URL can then be passed to Pannellum.

How do i do this if i am self hosting it on a different server. My website interiorpup.com requests 360.interiorpup.com via iframe to do this.


Fix container start timeout in latest Windows image

What this PR does / why we need it:
We switch to use "latest" Windows Server image and in recent Windows Update, the container start time takes more than the default 2 minutes. It causes subsequent code path to be executed to setup Windows container. This PR extends the timeout for Windows, specifically for start container here.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #959
Special notes for your reviewer:
Release note:

This change is

@JiangtianLi would this fix the outbound internet issue (https://github.com/Azure/acs-engine/issues/959)?

@seanknox  Yes, it is exactly to fix that issue.

I'm going to manually test myself first and then merge in.

@seanknox Thanks. I also am doing manual test. I'll see if it is quick to add to regression test.

@JiangtianLi does it mean we need to expect up to 10 minutes to start the Windows container?

@robbiezhang That parameter is the timeout limit according to here. So I guess the bigger, the safer. It may affect other scenario so that it wait longer time to timeout. To mitigate the issue, we need to choose some number in-between. If 5 minutes has worked for most scenario, we can use that.

My understanding of this toggle is it's to short-circuit long-running Docker operations, e.g. an image pull or starting a (Windows) container. It looks like we have a performance regression with the Windows VM we're using on agents that requires us to increase the default 2m timeout to something larger. Waiting (up to) 10m on Docker operations seems reasonable in this case (sluggish Windows performance) though I'm not sure what the other operational impacts there might be. Long-term, we should of course improve the VM performance.


[try-slang]: we need to support write-only texture for wgsl

Currently slang only have read-only and read-write texture support. That will make it hard to work with WebGPU, because it means that we can only use very limited texture format in the shader for storage binding.
here is the list for the access of each texture format:
https://www.w3.org/TR/webgpu/#texture-format-caps

This is done.


Forward the mongoDB client to the doc manager

Hi,
What do you think to allow the doc manager to fetch the original document from mongoDB instead of the destination?
In our case, we only index some attributes and modify some others to improve the indexing and reduce the size of the index. It's not possible to retrieve the original document from the search engine but this document is still available in mongoDB.
I'm not sure if it's better to have one shared client or to create one client per doc manager. If you have any feedbacks, I'd be happy to improve it :)
Thanks!

I'd need this too, although I temporarily fixed this with just
diff --git a/mongo_connector/oplog_manager.py b/mongo_connector/oplog_manager.py
index c3fc542..158636b 100755
--- a/mongo_connector/oplog_manager.py
+++ b/mongo_connector/oplog_manager.py
@@ -91,6 +91,9 @@ def __init__(self, primary_client, doc_managers,
             err_msg = 'OplogThread: No oplog for thread:'
             LOG.warning('%s %s' % (err_msg, self.primary_connection))

+        for dm in self.doc_managers:
+            dm.mongo = self.primary_client
+
     @property
     def fields(self):
         return self._fields

Hello!
This looks pretty good, would you mind rebasing with master and adding tests? I can help you get the test suite running, but any new change should come with tests to make sure nothing breaks it in the future.
Thank you for contributing!

Closing. It looks like all this adds is a reference to self.main_conn in the Connector. This was added as part of #563.


add Lone Wolf & Tzen checks to NFP

From Trello card: https://trello.com/c/k2dgb75V/46-revisit-checks-included-in-no-free-characters-espers-lone-wolf-tzen-thief
Testing TBD

I made the requested mod on the dev branch: https://github.com/ff6wc/WorldsCollide/pull/109/commits/eee33d783d63c2791225e76f9eb34c928bd59d13

Merged with https://github.com/ff6wc/WorldsCollide/pull/116


Using cwd option

Hi, thanks for this extension it is super useful for auto documenting cli tools!
One thing I can't get to work though is to get the "cwd" option. I don't think the documentation tells how this option should be used?
Note that I am trying to get this work with Sphinx+MyST, so what I am trying is the following (note I am using 3x acute tilde so they are not incorrectly interpreted here)
´´´{command-output} pwd
---
cwd ..
---
´´´

This is, I am just trying to go up one folder before I can execute "pwd". However I get a big error when doing so:
File "*****/.venv/lib/python3.9/site-packages/myst_parser/parsers/directives.py", line 144, in parse_directive_options
    for name, value in list(options.items()):
AttributeError: 'str' object has no attribute 'items'
The full traceback has been saved in /tmp/sphinx-err-l59_ympn.log, if you want to report the issue to the developers.

Actually, what I would really like to get more info about is regarding on what environment are these commands really running on. This is, on what shell environment is this running? I guess on a one provided by python's subprocess? Is it possible to update $PATH document-wide via some python command on conf.py?
Thanks

File "*****/.venv/lib/python3.9/site-packages/myst_parser/parsers/directives.py"

As you can see, your error is coming from your myst extension, not this package. So I can't help you with that.

Actually, what I would really like to get more info about is regarding on what environment are these commands really running on. This is, on what shell environment is this running? I guess on a one provided by python's subprocess? Is it possible to update $PATH document-wide via some python command on conf.py?

Yes, this package runs commands using the subprocess module. Whether or not is uses a shell depends on whether you turn on the shell option or not. The PATH and the rest of the environment variables are entirely up to you, set them however you want to. Relative paths are interpreted as Sphinx normally interprets them.

I guess the question I was asking is, independently of that error which, you are right, comes from myst, is that syntax the expected one for "cwd" ? Or, in other words, doc doesn't give an example of how would one write it down in normal rst sphinx's markdown? would it be like so?
.. command-output:: echo "$USER"
   :cwd:

Thanks


HttpError: Resource not accessible by integration

If the pull request is coming from a fork, it may trigger the error HttpError: Resource not accessible by integration when attempting to add a label.
May same to the error: actions/labeler#12

how to check title like :-- i had made changes with JIRA  ticket
now i want to match string if JIRA exist in  PR Title.
please suggest me regex for that

Assuming you just want to check if JIRA exists anywhere in the PR title, use: "JIRA"


Add signal loss calculation based on Pascua+2024

This PR adds the signal loss calculation from the FRF Signal Loss Paper to the single baseline processing notebook. The calculation implemented here only considers signal loss contributions from the crosstalk and main-lobe filters. I have some concerns about how the calculation I patched together handles the weights—even though the nsamples used for computing the weights are band-averaged, the sky temperature evolution causes the weights to vary as a function of frequency. For now, I'm just taking the band-averaged weights, but it's worth taking a closer look down the line.
Note that I had to move the FRF summary table to after the inpainting/delay filtering section, since I needed the weights to do the calculation (and those are computed downstream of inpainting/delay filtering). I ran some quick sanity checks, and things look fine. For the example data I tested this out on, the signal loss hovers around 4-6%, and the filter transfer matrix looks about right. If desired, then I can add some plots of what the filter transfer matrices look like, but there's already a lot going on in this notebook. As for compute intensity: it takes about a minute to compute the signal loss for all of the bands.
Another concern I have is that the weights differ between polarizations. For now, I'm just taking the average of the weights over ee/nn and hoping that there aren't issues. I don't think the differing weights will have a major effect, but I'm sure there are nuanced things happening because of it (e.g., the filter applied to ee isn't exactly the same as the filter applied to nn). The signal loss paper took the super simple limit of a uniformly weighted incoherent average for estimating the power spectrum, so I haven't taken a close look at the nuances that come up when the weights have various degrees of variability. (For this PR, I basically just did linear least squares -> generalized linear least squares to extend the formalism from the paper.)
One last thing, I didn't update the text describing the FRF summary table—I only removed the text saying that in the future it will be updated to the filter transfer-based calculation.
Remaining outstanding TODOs regarding signal loss:

Merge this stuff into hera_cal
Extend the signal loss calculation to include coherent averaging and time interleaving. I have the coherent average calculation sitting around in a notebook somewhere, but the time interleaving is new territory (I'm fairly certain the signal loss formalism can handle it, though).

Also, don't worry about tests failing


mini.indentscope will not show indent if there are blank lines in between

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.indentscope
Description
https://github.com/user-attachments/assets/73119af1-6c95-4023-81ac-b3c8dcc4a4a2
Neovim version
0.10
Steps to reproduce
same as video.
Expected behavior
the innder "if" node is expected to be identified.
Actual behavior
If node is ignored if there is a blank line in between

Thanks for the issue!
Behavior in video is as expected. When z characters are removed, the line becomes blank. In this case its indent is computed based on previous and next non-blank lines. In this case (assuming default config.options.border being 'both') it will be the same as both if ... and } lines. So it shows a scope of lines which have at least this indent (as per definition) and it happens to be the parent for scope.
Closing as working as expected.

Thanks, sorry I did not read the documentation carefully. May I suggest that distinguish between zero length lines and lines containing only blank characters and tabs, because the former if what we really want to ignore but the latter makes sense taking into account like the video.

May I suggest that distinguish between zero length lines and lines containing only blank characters and tabs, because the former is what we really want to ignore but the latter makes sense taking into account like the video ( sometimes I want to dai on the not yet completed if).

I don't think that is a good idea. Mostly because of the nature of the indent itself: it is a whitespace before the "main part" of the line. With blank lines any separation might result in indent and main part.
Plus, blank lines are not ignored: their indent is computed based on the surroundings.
So although I can understand the issue of not being able to dai in this case, I don't this this is going to change.

With blank lines any separation might result in indent and main part.
I don't understand that, could you give me an example?

With blank lines any separation might result in indent and main part.

I don't understand that, could you give me an example?

The line \t\t can (in theory) be considered as

'' indent and '\t\t' main part.
'\t' indent and '\t' main part.
'\t\t' indent and '' main part.

If define "main part" as "any non-whitespace charater", then there is none in blank lines. So fall back to neighbor lines.

I think this problem can be delegated to vim.fn.indent though, where it will report the whole \t\t as indented.


Add IAI_CALLGRIND_<triple>_VALGRIND_INCLUDE

For cross compilation like CARGO_TARGET_<triple>_RUNNER.
Example:
IAI_CALLGRIND_X86_64_UNKNOWN_LINUX_GNU_VALGRIND_INCLUDE

Thanks for your interest in iai-callgrind!
Can you please explain a little bit more? What do you expect iai-callgrind to do when it encounters such a environment variable?

Hi, from doc:

When building iai-callgrind with client requests, the valgrind header files must exist in your standard include path (most of the time /usr/include). This is usually the case if you've installed valgrind with your distribution's package manager. If not, you can point the IAI_CALLGRIND_VALGRIND_INCLUDE environment variable to the include path. So, if the headers can be found in /home/foo/repo/valgrind/{valgrind.h, callgrind.h, ...}, the correct include path would be IAI_CALLGRIND_VALGRIND_INCLUDE=/home/foo/repo (not /home/foo/repo/valgrind)

so for cross benches I must to set this variable every time, example:
IAI_CALLGRIND_VALGRIND_INCLUDE=/aarch64/valgrind/include cargo bench --target aarch64-unknown-linux-gnu

IAI_CALLGRIND_VALGRIND_INCLUDE=/x86_64/valgrind/include cargo bench --target x86_64-unknown-linux-gnu

My proposal:

Find IAI_CALLGRIND_<triple>_VALGRIND_INCLUDE variable
Find IAI_CALLGRIND_VALGRIND_INCLUDE
...

This allows to set the path once per target:
IAI_CALLGRIND_AARCH64_UNKNOWN_LINUX_GNU_VALGRIND_INCLUDE=/aarch64/valgrind/include
IAI_CALLGRIND_X86_64_UNKNOWN_LINUX_GNU_VALGRIND_INCLUDE=/x86_64/valgrind/include

Then just run benches:
cargo bench --target aarch64-unknown-linux-gnu
cargo bench --target x86_64-unknown-linux-gnu

Also, it would be nice if the reports were grouped by target

Thanks for clarifying. Sounds good. Regarding the grouping, you should already be able to achieve something like that by saving baselines per target. See the README https://github.com/iai-callgrind/iai-callgrind?tab=readme-ov-file#comparing-with-baselines.

Regarding the grouping, you should already be able to achieve something like that by saving baselines per target.

I think this is a little different - there is no point in comparing two targets, moreover it looks terrible and is easy to make a mistake:
cargo bench --target aarch64-unknown-linux-gnu -- --save-baseline=aarch64_main
cargo bench --target aarch64-unknown-linux-gnu -- --save-baseline=aarch64_new
cargo bench --target x86_64-unknown-linux-gnu -- --save-baseline=x86_64_main

cargo bench --target x86_64-unknown-linux-gnu -- --save-baseline=x86_64_new

It's not the same and maybe not ideal for this usecase but for the time being there's a possibility to achieve a comparison between the same target and you're not completely lost. Maybe consider using just, a Makefile or a little script etc. to avoid the typing and typos? I'm going to have a look into it asap. I didn't have much time time to work on iai-callgrind lately.

I didn't have much time time to work on iai-callgrind lately.

I was just interested to hear your opinion. This way I can do the PR when I have time.

Closing this as completed with #103, #104, #158 and #160


result about run inference.py

Perform inference. py tests a picture, and the segmentation result shows no complete outline of the object, but a lot of color spots. How to solve it? Looking forward to your reply!!
@DrSleep

Hi @DrSleep,
I also meet the problem when I run the inference.py. I retain the model using the following setup, because the original batch size is out of memory I changed it to 4
BATCH_SIZE = 4
DATA_DIRECTORY = '/PASCAL/SemanticImg'
DATA_LIST_PATH = './dataset/train.txt'
IGNORE_LABEL = 255
INPUT_SIZE = '321,321'
LEARNING_RATE = 2.5e-4
MOMENTUM = 0.9
NUM_CLASSES = 21
NUM_STEPS = 20001
POWER = 0.9
RANDOM_SEED = 1234
RESTORE_FROM = './deeplab_resnet.ckpt'
SAVE_NUM_IMAGES = 2
SAVE_PRED_EVERY = 1000
SNAPSHOT_DIR = './snapshots/'
WEIGHT_DECAY = 0.0005
the train.txt is as follows:
/JPEGImages/2007_000032.jpg /SegmentationClass/2007_000032.png
/JPEGImages/2007_000039.jpg /SegmentationClass/2007_000039.png
/JPEGImages/2007_000063.jpg /SegmentationClass/2007_000063.png
/JPEGImages/2007_000068.jpg /SegmentationClass/2007_000068.png
/JPEGImages/2007_000121.jpg /SegmentationClass/2007_000121.png
/JPEGImages/2007_000170.jpg /SegmentationClass/2007_000170.png
/JPEGImages/2007_000241.jpg /SegmentationClass/2007_000241.png
/JPEGImages/2007_000243.jpg /SegmentationClass/2007_000243.png
/JPEGImages/2007_000250.jpg /SegmentationClass/2007_000250.png
/JPEGImages/2007_000256.jpg /SegmentationClass/2007_000256.png
/JPEGImages/2007_000333.jpg /SegmentationClass/2007_000333.png
/JPEGImages/2007_000363.jpg /SegmentationClass/2007_000363.png
/JPEGImages/2007_000364.jpg /SegmentationClass/2007_000364.png
/JPEGImages/2007_000392.jpg /SegmentationClass/2007_000392.png
/JPEGImages/2007_000480.jpg /SegmentationClass/2007_000480.png
/JPEGImages/2007_000504.jpg /SegmentationClass/2007_000504.png
/JPEGImages/2007_000515.jpg /SegmentationClass/2007_000515.png
/JPEGImages/2007_000528.jpg /SegmentationClass/2007_000528.png
/JPEGImages/2007_000549.jpg /SegmentationClass/2007_000549.png
/JPEGImages/2007_000584.jpg /SegmentationClass/2007_000584.png
/JPEGImages/2007_000645.jpg /SegmentationClass/2007_000645.png
/JPEGImages/2007_000648.jpg /SegmentationClass/2007_000648.png
/JPEGImages/2007_000713.jpg /SegmentationClass/2007_000713.png
/JPEGImages/2007_000720.jpg /SegmentationClass/2007_000720.png
/JPEGImages/2007_000733.jpg /SegmentationClass/2007_000733.png
/JPEGImages/2007_000738.jpg /SegmentationClass/2007_000738.png
/JPEGImages/2007_000768.jpg /SegmentationClass/2007_000768.png
.
.
.
The total number of training images is 1464 , the name of the images is from the VOC2012 trian list.
The logs is showing as follow:
Restored model parameters from ./deeplab_resnet.ckpt
The checkpoint has been created.
step 0 	 loss = 1.268, (16.858 sec/step)
step 1 	 loss = 3.971, (1.734 sec/step)
step 2 	 loss = 1.308, (1.339 sec/step)
step 3 	 loss = 2.991, (1.329 sec/step)
step 4 	 loss = 1.252, (1.346 sec/step)
step 5 	 loss = 1.344, (1.335 sec/step)
step 6 	 loss = 8.126, (1.331 sec/step)
step 7 	 loss = 4.652, (1.339 sec/step)
step 8 	 loss = 5.097, (1.339 sec/step)
step 9 	 loss = 1.318, (1.334 sec/step)
step 10 	 loss = 1.769, (1.353 sec/step)
.
.
.
step 19990 	 loss = 1.191, (1.419 sec/step)
step 19991 	 loss = 1.183, (1.425 sec/step)
step 19992 	 loss = 1.197, (1.424 sec/step)
step 19993 	 loss = 1.183, (1.422 sec/step)
step 19994 	 loss = 1.184, (1.408 sec/step)
step 19995 	 loss = 1.192, (1.416 sec/step)
step 19996 	 loss = 1.183, (1.419 sec/step)
step 19997 	 loss = 1.183, (1.414 sec/step)
step 19998 	 loss = 1.183, (1.420 sec/step)
step 19999 	 loss = 1.183, (1.437 sec/step)
The checkpoint has been created.
step 20000 	 loss = 1.183, (12.276 sec/step)
It looks normal right?
but when I run the inferency. py the results are all background,even though I use  the training image.
Also if I use the deeplab_resnet.ckpt for inference, the output has both background and the segmented image.
Do you have any suggestion about this error?
Thank you!

@sunbin1205

E tensorflow/stream_executor/cuda/cuda_diagnostics.cc:303] kernel version 384.90.0 does not match DSO version 387.26.0 -- cannot find working devices in this configuration

Something with the drivers I assume. Can't help with that one.
@minnieyao
You are restoring from the already pre-trained model, hence the learning rate might be too high. Try to restore from the init model and check the progress in tensorboard, should be alright

Hi, @minnieyao.
I git the same problem. Did you solve it?
I restored from the deeplab_resnet_init.ckpt


Python: adding external tokenizer to python text_chunker

Motivation and Context

addressing issue #1387
chunking text should allow use of an external tokenizer
Description

added pass-through of an token counting function, defaulting to the existing _token_counter() method
while fixing a type hint bug I got sucked into making a few changes to clean up the code.
future work would be nice to add chunk overlap functionality similar to langchain's TextSplitter
Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

@gramhagen Cool change! Thanks for the contribution.
Welcome to Semantic Kernel!


[Bug]: Change PA log name

Describe the bug
PA log has been moved out of /tmp dir to $OPENSEARCH_HOME/logs/PerformanceAnalyzer.log PR. Please change PA log name here from performance-analyzer.log to PerformanceAnalyzer.log.

Awaiting:

https://github.com/opensearch-project/opensearch-build-libraries/pull/186

PR:

https://github.com/opensearch-project/opensearch-build/pull/3394

Complete now.


fix: ensure location-changed event is timed after window.location update

Fixes #340

This change is

Thanks @platosha! I just saw the GitHub tag, but the new version is not in npm. Have you published it? Thanks!


Problem closing lightning pool account

I'm having an issue with closing an account on the lighting pool. I send back the fund with too low fees hoping to open a channel with higger fees later to bump the closing transaction. However, there was some issue with the channel transaction. It never appeared in the mempool but appears in my node as pending. Thus, I can't move the funds and am waiting for confirmation of that transaction. Is it possible to bump that transaction fee? I will pay you the fees if it does.
Pool closing transaction:
df338aaaf768499d521f869c608261c5c432364b55097ca3dfee5e94efcaa694

It looks like the tx fee is too low to fit in the "standard" mempool size (300Mb)
The current purging threshold for the 300Mb mempool is ~8 sat/vbyte while the tx was broadcasted at 5 sat/vbyte.
To bump the tx with a CPFP the tx must be in the mempool. You can try increasing the size of your mempool and then you will be able to broadcast and bump the tx.
In order to have it propagated to the miners, other nodes MUST also have the closing tx (5 sat/vbyte) in their mempool. So even if your node tries to broadcast it to the network you may have to wait a bit until the initial tx fee is higher than the mempool purge threshold.

I did that. change the side to 500mb. bumped the fee and only appear in my mempool.
Bumped transaction
420342ee4a9ceaa9f05939c00eb928807061fdbbaa9339d399ee42fd3429f07c

Looks like the TX got confirmed.


add flag to minify the service-worker.js

HI all,
i think shuold be good to put a flag to minify the service-worker.js file.
sw-precache [--min] --root=dist --verbose --config=sw-precache-config.js
i don't know if is even possible to uglify.
Thank you

add this to the end of build script code : && uglifyjs build/service-worker.js -o build/service-worker.js

It Works!
Thanks, i suggest to add this into the documentation ;)


FileBundle updates (grouping & descendedFrom)

discussed offline with @lzehl

descendedFrom should be 0 - 1, because it shouldn't be more than what the FileBundleGrouping states
fileOrigin category need to be added to all specimen(set)s as well, because a file bundle could begrouped by e.g. a subject and collect data for more than one state

FYI @olinux

@UlrikeS91 can you take this over?


Bugfix _iosrtcVideoHandled flag when removing node

This bug was being triggered if you removed the video element from the DOM and try to add it later.

Right, thanks!


vgPattern is not selecting correct volume group

What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.]

Created storage class with vgPattern as lo* for my volume group starting with lo initials.
volume should have been created from this volume group but it was created on a volgroup named lvmvg

spec:
  capacity: "48318382080"
  ownerNodeID: lvm-node2
  shared: "no"
  thinProvision: "no"
  vgPattern: lo*
  volGroup: lvmvg
status:
  state: Ready

here vgPattern doesn't match in volume group  name still this volgroup was selected for creation lvm volume
lvmuser@rack2:~/aman$ k get lvmvol -n openebs pvc-fc577d03-dd57-4ab8-b4cd-2e96a9c327e7 -o yaml
apiVersion: local.openebs.io/v1alpha1
kind: LVMVolume
metadata:
creationTimestamp: "2021-04-20T09:57:07Z"
finalizers:
- lvm.openebs.io/finalizer
generation: 3
labels:
  kubernetes.io/nodename: lvm-node2
managedFields:
- apiVersion: local.openebs.io/v1alpha1
  fieldsType: FieldsV1
  fieldsV1:
    f:metadata:
      f:finalizers:
        .: {}
        v:"lvm.openebs.io/finalizer": {}
      f:labels:
        .: {}
        f:kubernetes.io/nodename: {}
    f:spec:
      .: {}
      f:capacity: {}
      f:ownerNodeID: {}
      f:shared: {}
      f:thinProvision: {}
      f:vgPattern: {}
      f:volGroup: {}
    f:status:
      .: {}
      f:state: {}
  manager: lvm-driver
  operation: Update
  time: "2021-04-20T09:57:07Z"
name: pvc-fc577d03-dd57-4ab8-b4cd-2e96a9c327e7
namespace: openebs
resourceVersion: "1204269"
uid: 6cfa2ef0-b608-4885-a0c7-325681e0f14d
spec:
capacity: "48318382080"
ownerNodeID: lvm-node2
shared: "no"
thinProvision: "no"
vgPattern: lo*
volGroup: lvmvg
status:
state: Ready

/closing
Yes, it was correct working.
Actually lo* regex will work as first l and then zero or more occurances of o
so it took l and zero o this time so pattern become only l and which is obviously a substring for lvmvg


Update help text in sub commands and validate import

Purpose
Fixes: https://github.com/ballerina-platform/ballerina-standard-library/issues/3967
Examples
Checklist

[x] Linked to an issue
[ ] Updated the specification
[ ] Updated the changelog
[x] Added tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Danesh Kuruppu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Replaced AppBar brightness with systemOverlayStyle

AppBar's brightness property will be deprecated in https://github.com/flutter/flutter/pull/86198. The new property was introduced in https://github.com/flutter/flutter/pull/71184 and has the same effect as AppBar.brightness did.

Thanks!


Use Git Submodules for development

This solves a couple of issues:

Users that pass --no-build --use-submodules can now use Argo
without running into errors from missing framework search paths
(fixes #121)
Users that want to use Submodules as a dependency management solution
can now do so without having to jump through any additional hoops.

We're still going to use Carthage as a development dependency, but it's
going to act as a semantic wrapper around submodules, instead of relying
on the binaries.
I'm not super happy about this change, but it seems like it's the most
pragmatic way to move forward.

Interestingly enough, the move to a workspace means we might be able to add a playground directly to this project, which would be nice for educational purposes.

ping @thoughtbot/ios on this

:+1:


User identity document improvement

https://portal.microsofticm.com/imp/v5/incidents/details/485610146/summary improvement initiated customer struggling to add a user identity in ICM
New PR created, reflecting https://github.com/MicrosoftDocs/entra-docs/pull/852

@barclayn  @Court72  hello, I created a same PR as https://github.com/MicrosoftDocs/entra-docs/pull/852.
Could you please review/merge?

@grizzlytheodore thank you for your submission. We appreciate your help. #sign-off


Resize border box overflow the editor

ScreenShot

ScreenShot

You can try to add the "overflow:auto"  to the editor container

@morining but the pic can't be fit for the dashed box.

@morining but the pic can't be fit for the dashed box.

I am using the following class to style the editor.If you don`t have a flex editor,you should use "max-height : xxx" and overflow : auto to style the editor simultaneously

        .flex-editor {
            flex: 1;
            display: flex;
            flex-flow: column nowrap;
            overflow: auto;
        }

@morining it don't work.

Take a look at the Demo at the repo .The code snippet from demo using the max-height and overflow to style the editor.
<!DOCTYPE html>

    <meta charset="utf-8">
    <title>Quill Image Resize Module Demo</title>

    <link href="//cdn.quilljs.com/1.2.2/quill.snow.css" rel="stylesheet">

Quill Image Resize Module Demo

Click on the Image Below to resize

Some initial bold text

Also see quill-image-drop-module,
    a module that enables copy-paste and drag/drop for Quill.

thx, I fixed.

thx, I fixed.

Thanks mate, that helps a lot!


Error with latest version of terraform mixin

Mixin version 1.0.0
Porter is adding the following RUN command during build which is causing the following error: #15 2.833 Too many command line arguments. Configuration path expected.
#15 ERROR: executor failed running [/bin/sh -c cd $BUNDLE_DIR/terraform &&  terraform init -backend=false &&  rm -fr .terraform/providers &&  terraform providers mirror /usr/local/share/terraform/plugins]: exit code: 1
RUN cd $BUNDLE_DIR/terraform &&
terraform init -backend=false &&
rm -fr .terraform/providers &&
terraform providers mirror /usr/local/share/terraform/plugins
I am using terraform 0.12.31 which does not support terraform provider mirrors.

Thanks for raising that the mixin isn't compatible anymore with pre 1.0 versions of terraform. We will get the README updated with a compatibility matrix going forward so that we don't surprise people with breaking changes again.


🐣 Create client_data Dict if it does not exist yet

Hello!! 👋
I tried Olive for the first time and it did not work :( After giving my name in the setup wizard, the terminal showed this error and the progress bar got stuck:
┌ Error: handle_connection handler error
│   exception =
│    KeyError: key "fonzyy" not found
│    Stacktrace:
│     [1] getindex(h::Dict{String, Dict{String, Any}}, key::String)
│       @ Base ./dict.jl:484
│     [2] (::Olive.var"#262#266")(c::Toolips.Connection)
│       @ Olive ~/.julia/packages/Olive/YuQss/src/Olive.jl:177
│     [3] (::Toolips.var"#serve#63"{Vector{Toolips.AbstractRoute}, String, Vector{Toolips.ServerExtension}, Vector{Toolips.ServerExtension}})(http::HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.ConnectionPool.Connection{Sockets.TCPSocket}})
│       @ Toolips ~/.julia/packages/Toolips/L3oiV/src/server/Core.jl:0
│     [4] #invokelatest#2
│       @ ./essentials.jl:816 [inlined]
│     [5] invokelatest
│       @ ./essentials.jl:813 [inlined]
│     [6] handle_connection(f::Function, c::HTTP.ConnectionPool.Connection{Sockets.TCPSocket}, listener::HTTP.Servers.Listener{Nothing, Sockets.TCPServer}, readtimeout::Int64, access_log::Nothing)
│       @ HTTP.Servers ~/.julia/packages/HTTP/z8l0i/src/Servers.jl:447
│     [7] macro expansion
│       @ ~/.julia/packages/HTTP/z8l0i/src/Servers.jl:385 [inlined]
│     [8] (::HTTP.Servers.var"#16#17"{Toolips.var"#serve#63"{Vector{Toolips.AbstractRoute}, String, Vector{Toolips.ServerExtension}, Vector{Toolips.ServerExtension}}, HTTP.Servers.Listener{Nothing, Sockets.TCPServer}, Set{HTTP.ConnectionPool.Connection}, Int64, Nothing, Base.Semaphore, HTTP.ConnectionPool.Connection{Sockets.TCPSocket}})()
│       @ HTTP.Servers ./task.jl:514
└ @ HTTP.Servers ~/.julia/packages/HTTP/z8l0i/src/Servers.jl:461

This PR fixed the error 🎉 I was not sure what the type of the Dict should be, so I used Dict{Any,Any}, but maybe you want to change this to Dict{String,String} or something else.
Looking forward to try Olive!!

I believe what happened with your error, by the way, is that OliveDefaults is not yet addable (due to Olive not being in the registry,) and then the progress bar got stuck because the package name could not be found (I meant to switch the buttons around to have no be the default anyway,) but the addition of OliveDefaults happens just before the client info is saved and loaded into the OliveCore, I am presuming that when it got stuck you refreshed the page, and this gave you the error if this is the case.
Certainly is nice to have a catchall, though, only makes sense if the key is already authenticated.


cleaned up YAML spacing and related items

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: _Cleaned up YAML that was not spaced correctly and added information about where the YAML is to be inserted
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6631151f6e24412cd2cddc66--harness-developer.netlify.app

@xingchi-jin Could you please review? Some of the updates change content we recently implemented in the topic.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66312e24d6b8e0009df4cfb9--harness-developer.netlify.app


release(prod): Update miner to latest GA 2<IP_ADDRESS>

Update miner to latest GA 2<IP_ADDRESS>
Ref #268
Pushed to testnet at Tue Nov 23 06:15:44 UTC 2021

https://engineering.helium.com/2021/11/22/blockchain-release-sync-emergency.html

Guys, with all respect what you are doing, why is PR not automerged to production branch after two approvals? It looks like step of authorized users to click "Merge" button is redundant and it is creating a bottle neck.

@usalis I think they forgot how important this is. Because many devices are stuck now because this PR is not merged yet..

@justkidding96, I do not think they forgot about importance, just because PR and actions related were done at night. We appreciate it. I am questioning a release to production process. If all checks passed (2 reviews + testnet), but we still wait for one person to do a merge. Isn't it a counter productive?

Testnet checks are not always immediate which is why we don't want to auto merge. But thanks for the suggestions

@shawaj, my understanding is that testnet checks are done by human observation: someone checks hotspot activity for a first beacon witnessed after deployment to testnet to confirm it is working. I am sure there will be volunteers in a community to help to automate this, if there are no plans or resources to do it soon.

@usalis it isn't really something the community can help with per-se as we need someone on our team who knows the codebase quite intimately to perform tests internally on our testnet (this part isn't documented here on the README currently for the internal part)
Having said that, we potentially could put some customers devices onto our testnet to help verify releases....however I dont think many people will be interested in that as the devices will have a considerable amount more down time on testnet than in production and people don't like that
open to ideas though for sure

@shawaj We'd be happy to see if some of our hosts are opening to running an internal beta hotspot in addition to their regular hotspot. They're all experiencing so much downtime due to firmware issues already that I don't think anyone would mind.

@rawrmaan will discuss this internally and see if there is an easy way to achieve something like this. perhaps we could have two levels of testnet or something. need to have a think and see what can fit in with the existing pipeline/workflow. And will need to make sure that people are fully aware that it will be far more reliable to be on bleeding-edge updates flow.
unfortunately though, the vast majority of issues at the moment are coming from helium side - either due to the excessive number of issues on the network (including a GA every 2 days on average the last few weeks, 2 major chain halts and a "slow down"!) as well as the fact that GAs are not well documented with breaking changes and often breaking changes are dropped with no prior warning.
To be honest, it feels like there needs to be something more substantial from the helium side - building a robust CI/CD pipeline with lots of automated testing but also a better / more standardised release flow as per https://github.com/helium/HIP/issues/309
Whilst the manufacturer has responsibility for a lot of stuff on the hardware and software side, AFAIK helium right now does not test on all vendors hardware/software stack when pushing GAs which is bound to cause issues and these will only increase as the network (and number of different types of hardware) grows. Helium also has the resources and the recurring incentives (large %% of HNT earnings) to fix this - more so than any other network stakeholder IMO.
Probably worth further discussion though I guess from all aspects.

I understand that Helium has been in massive flux and nothing is stable right now. It has to be very frustrating to deal with this as you're trying to improve your own software and systems.
However, writing 3 paragraphs about how Helium needs to fix things when Nebra is uniquely failing to get their hotspots working is not a good look.

No other major manufacturer has such an awful PoC success rate. We have first-hand experience with large sample size that shows Nebra hotspots are failing to even boot at a 10-30% rate. This happens before any of Helium's code comes into the picture.
Look, I get it. Software is hard. I've built companies. Sometimes you ship to production 20 times in a row and it's still broken and you don't know why.
We need an acknowledgement that you guys are having issues stabilizing the firmware and openness about what issues you're seeing and how you're planning to fix it. Since this is an open source project, maybe we could even help fix the issues if we know what's wrong.
What will it be, @shawaj? Continued denial and gaslighting your customers, or acknowledging the situation so we can all move forward constructively?

We aren't having issues stabilising the software. If you are having problems, please reach out to our support at<EMAIL_ADDRESS>We use balenaCloud which is extremely reliable (I believe Emrit and others use it too)


fix(installation documentation): grammatical error

Fixes a single grammatical error in the installation documentation.
Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:bug: Bug fix or new feature
:memo: Documentation Fix
:book: New/Updated Documentation Content

Thanks!


[plugins/digitalocean][fix] fix the retry decorator

Description

Fixed a bug where the retry decorator did not work
To-Dos

[x] Add test coverage for new or updated functionality
[x] Lint and test with tox
[x] Document new or updated functionality (someengineering/resoto.com#XXXX)

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report

Merging #741 (7a61961) into main (77e4f0b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #741   +/-   ##
=======================================
  Coverage   89.69%   89.69%
=======================================
  Files          69       69
  Lines        9677     9677
=======================================
  Hits         8680     8680
  Misses        997      997

Flag
Coverage Δ

resotocore
89.69% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Component: Create image - with caption design specs

As an adopter or developer on the DDS team I need to know the design specs for image - with caption pattern. Currently, the only documentation we have is dev/code.
Tasks

[x] Create a Sketch file with image - with caption design and specs
[x] Create Box folder for image - with caption (if not already there)
[x] Add design specs and Abstract version to Box folder
[ ] Update any links or documentation that needs image - with caption specs

Specs for image with caption complete and added to Box + Abstract.
@photodow you might need to update the func specs doc? Not sure.

README added here.

@larahanlon2 this looks great. Thank you. One QQ: should the focus border be 3 px like other buttons? And should there be inner white border fo a11y?

@wonilsuhibm thanks. All buttons have 2px border, not 3px. Unless something has changed from Carbon? I think the white inner border works when the button is one color i.e all blue. In that case the white border is needed to separate the focus outline and the default button background. like so:

But I'm not sure we need that inner border for this button because the blue outline already contrasts with the dark button background and the white search icon. With:

without:

I prefer without the white inner border but if it's an a11y requirement of you want it to be I can make the change.

@larahanlon2 I see that the design kit uses 2px border while their storybook is coded with 3px borders. I asked on the #carbon-design-system channel. Let's see what they say.
As for the while inner border, it is necessary because the blue and the dark gray bg are not discernable enough.

@wonilsuhibm ok cool I'll add the white border and wait for Carbon's response.

@larahanlon2 Thank you. Lauren from Carbon says it's supposed to be 2px. Let's go with 2.

@larahanlon2 I need to create the functional specs for this this sprint.

@larahanlon2 is that magnifying glass button different from the icon only buttons from carbon?


install bash v4 or later on macOS

needed for openj9

openj9 has always needed bash v4 or above. Without it you get this error:
Bash version 4.0 or later is required!

interestingly would allow us to upgrade our build scripts to Bash4+ as we held Bash back for Mac OS X reasons.


Fix bucket auto delete objects on destroy removal policy

cdk update changed the path to the handler, this should resolve that.
Also, this auto-delete-object code hasn't worked for a while, since a cdk update a year or 2 back meant that the handler only empties the bucket when a tag is present on the bucket - this tag was never added to the SST code.
This was added because when removing the setting on the cdk bucket (changing autoDeleteObjects from true to false), it would delete the CR but this has a side effect of deleting all objects in the bucket (lol). So now the handler checks for this tag to be present, before nuking the bucket.
I have also added a guard of policy === "destroy", as the CR was being created on every removal policy type - I felt a bit uneasy applying this tag to buckets in apps that have removal policy of retain.

https://github.com/aws/aws-cdk/issues/16603 for reference

Here is a stack trace I'm getting from it:
> sst dev

SST v2.24.1  ready!

➜  App:     test-sst
   Stage:   seawatts
   Console: https://console.sst.dev

⠸  Checking for changesBundling asset seawatts-StageDNS/CrossAccountZoneCertificateRecordProvider/Handler/Code/Stage...

  .sst/dist/bundling-temp-9a8b5417be6e381de517f6bb8f5a1cc0f099e8876ed5f2a4c5ceccdd39d627d6/index.js  2.8mb ⚠

⚡ Done in 176ms
✖  Checking for changes
   Error: cannot find ./node_modules/.pnpm/aws-cdk-lib<EMAIL_ADDRESS>       at new CustomResourceProvider (./node_modules/.pnpm/aws-cdk-lib@2.91.0_constructs@10.2.69/node_modules/aws-cdk-lib/core/lib/custom-resource-provider/custom-resource-provider.js:1:3206)
       at CustomResourceProvider.getOrCreateProvider (./node_modules/.pnpm/aws-cdk-lib@2.91.0_constructs@10.2.69/node_modules/aws-cdk-lib/core/lib/custom-resource-provider/custom-resource-provider.js:1:2652)
       at App.applyRemovalPolicy (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/constructs/App.js:291:53)
       at file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/constructs/App.js:323:58
       at Array.forEach (<anonymous>)
       at App.applyRemovalPolicy (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/constructs/App.js:323:31)
       at file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/constructs/App.js:323:58
       at Array.forEach (<anonymous>)
       at App.applyRemovalPolicy (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/constructs/App.js:323:31)
       at App.finish (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/constructs/App.js:201:26)
       at async Module.synth (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/stacks/synth.js:64:9)
       at async build (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/cli/commands/dev.js:161:34)
       at async file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/cli/commands/dev.js:265:9
       at async Object.handler (file://./node_modules/.pnpm/sst@2.24.1_@types+react@18.2.20/node_modules/sst/cli/commands/dev.js:321:5)

^C ELIFECYCLE  Command failed.

Thanks @jamesgibbons92.
I made a cosmetic change to call the private enableAutoDeleteObjects() function instead of replicating the code here. Not optimal, but w/ the tests we added, this seems safe.


Various improvements

add js stacktraces in Julia (@ezramarks)

Thanks for sending that along! I didn't know where to begin with accessing 'exception.stack' and 'AssetRegistry.registry', so it's really nice to see how easy that part is.

remove AssetRegistry, since it has a different scope from whats needed (serializing the registered files to disk for inter process communication)


can we use gpu when run demo fin_model?

when i run "rdagent fin_model", it works well on my cpu to train a GRU. How to use gpu device such as "cuda:0" to run this demo?
Some outputs of my terminal when running this script are as follows:
[1:MainThread](2024-10-21 03:13:05,144) INFO - qlib.GeneralPTNN - [pytorch_general_nn.py:74] - GeneralPTNN pytorch version...
[1:MainThread](2024-10-21 03:13:05,157) INFO - qlib.GeneralPTNN - [pytorch_general_nn.py:92] - GeneralPTNN parameters setting:
n_epochs : 100
lr : 0.001
metric : loss
batch_size : 2000
early_stop : 10
optimizer : adam
loss_type : mse
device : cpu
n_jobs : 20
use_GPU : False
weight_decay : 0.0001
seed : None
pt_model_uri: model.model_cls
pt_model_kwargs: {'num_features': 20, 'num_timesteps': 20}
[1:MainThread](2024-10-21 03:13:05,158) INFO - qlib.GeneralPTNN - [pytorch_general_nn.py:129] - model:
EnhancedDeepGRUModel(
(gru): GRU(20, 256, num_layers=5, batch_first=True, dropout=0.4)
(fc): Linear(in_features=256, out_features=1, bias=True)
)

Hi,
You could firstly check if you've chosen the correct base image in your Dockerfile to support GPU functionality.
The Dockerfile can be found at rdagent/scenarios/qlib/docker.

Also, it seems the docker container can correctly detect the gpu device, the log detail are listed below.
2024-10-21 20:20:18.348 | INFO     | rdagent.utils.env:_gpu_kwargs:269 - GPU Devices are available.


Allow custom admin site

Sometimes we do insane things with the admin, which require custom admin site. This PR includes a simple fix that enables developer to specify which admin site should be used instead of the default django.contrib.admin.site.
Usage:
in settings.py:
ADMIN_REORDER_SITE = 'myapp.custom_admin.site'

That's it. Of course, if setting is missing, the default site will be used.

Idea for the future: enable reorder to work on multiple sites.

Coverage decreased (-0.07%) to 0.971% when pulling c6da2877a61eddd689dc0da281a9a813aebc77ee on frnhr:allow_custom_admin_site into 6de6a7293e68efa7bddbe52f58eb3333843c4243 on mishbahr:master.

Hey @frnhr, I'm on holiday at the moment .. I'll look into this as soon as I'm back.

Has there been any progress on this or #20 ? I was hoping to use this with two different admin sites in a single Django project.


Added Empty PVC label selector change

When the user doesn't specifya PVC label selector in VRG spec, Ramen VRG should protect all PVs of the namespace

I think this is obsoleted by #453 if so can this PR be closed?

Closing older PRs that are not applicable at present (or stale). Reopen if required.


fix: prevent double resolve/reject on pin

Same return code can also be added for setDynamic method:
https://github.com/NePheus/capacitor-android-shortcuts/blob/52a838be690e8c941781ae34be2dfc586bc0c2ce/android/src/main/java/nepheus/capacitor/androidshortcuts/AndroidShortcutsPlugin.java#L44-L48

I added both returns and published 6.0.1. Thanks for your help!


Update HTTP to HTTPS links where it can be done safely.

Describe the pull request
This PR updates HTTP link (e.g. http://foo) to HTTPS where it can be done safely.
"Safely" means that the HTTP-based link gave a 200 response with identical
content to the HTTPS version of the link. For links containing
variables, we checked the interpolated (real) link.
This PR covers the first 15 changes.

What does your PR fix?

#20219 (partial fix, additional PRs to come)

Which triplets are supported/not supported? Have you updated the CI baseline?

<all / no>

Does your PR follow the maintainer guide?

Yes, though this covers multiple ports as per guidance from #20219.

N/A
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@scovetta Do you want to merge this now? Next time you need to do version updates to the vcpkg.jsons next to the relevant portfile.cmakes.

Ping @scovetta for response, Is work still being done for this PR?

@scovetta ping for response

@scovetta ,It looks like this pr is ok, ready for review?

@scovetta ,Can you please resolve the conflicts against master?

I also asked Michael over Teams.

@scovetta ,Can you please resolve the conflicts against master?

@scovetta ,Can you please resolve the conflicts against master?

I took care of it :)

Thanks @BillyONeal!
Since I'm super short on cycles for this, (and have been for some time), I've uploaded the script that I used to find, validate, and rewrite certain files. Feel free to use it as you wish.
https://gist.github.com/scovetta/51e15537309d25f3617f908fcd2a1327

@BillyONeal do you want to merge this?

@strega-nil-ms Yes XD


Old testnet txs not found in tendermint indexer

Describe the Bug
It was reported that for 2 blocks on testnet, eth_getTransactionReceipt is returning null (eg. block https://athens.explorer.zetachain.com/block/911330) . Upon closer look, tx_search json rpc tendermint method is not returning those txs, and this method is used by rpc to further parse tx, therefore bug is not in rpc code. Transactions in block 911332, just 2 blocks after are working fine, so it appears that for some reason just couple of blocks are not indexed in tendermint indexer.
Since this was 1 year ago, and it is testnet, it is not huge priority, as there could be a lot of reasons why indexer missed in testnet phase before mainnet - incomplete or buggy functionality, network upgrades etc.
One of the ways to  try to reindex them is to introduce reindex-event command which is currently removed from tendermint/comet. TBD if this is necessary, if its just for couple of old testnet blocks then it is not priority.
To Reproduce
Example transaction from above mentioned block, empty result is returned:
https://zetachain-athens.g.allthatnode.com/archive/tendermint/tx_search?query="ethereum_tx.ethereumTxHash='0x7d02ea99085583a9b360d91bf7956323d64827e70c177cdad4c043920d296f6a'"

Expected Behavior
tx_search should return it, eg for working transaction:
https://zetachain-athens.g.allthatnode.com/archive/tendermint/tx_search?query="ethereum_tx.ethereumTxHash='0x528f1575be118dd6b1219bb3e6af713a9618d3962af73d4b370b31a23edd2e00'"

Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS
Version used

to fix your trouble check this solution click
maybe this will solve your problem.


Add missing sbs blueprint setting

@hangwan97
If you want the regular Jhipster generator to run before the ASA generator is applied, you should merge this.
Otherwise, if the goal was to only run the ASA generator without the regular Jhipster output, then you can ignore it

#sign-off


What is the pytorch version to run this github?

What is the pytorch version to run this github?

3.7