mim login does not work ....

Hello,
I have tried to use the instructions to setup this example. I have docker and docker-compose on Linux machine (Fedora)
[kamran@kworkhorse uda-jellyfish-data-example]$ docker version
Client: Docker Engine - Community
 Version:           23.0.2
 API version:       1.42
 Go version:        go1.19.7
 Git commit:        569dd73
 Built:             Mon Mar 27 16:19:37 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          23.0.2
  API version:      1.42 (minimum version 1.12)
  Go version:       go1.19.7
  Git commit:       219f21b
  Built:            Mon Mar 27 16:16:40 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.20
  GitCommit:        2806fc1057397dbaeefbea0e4e17bddfbd388f38
 runc:
  Version:          1.1.5
  GitCommit:        v1.1.5-0-gf19387a
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
[kamran@kworkhorse uda-jellyfish-data-example]$ docker-compose version
docker-compose version 1.29.2, build unknown
docker-py version: 5.0.3
CPython version: 3.10.10
OpenSSL version: OpenSSL 3.0.8 7 Feb 2023
[kamran@kworkhorse uda-jellyfish-data-example]$

I installed mim too, using the RPM:
[kamran@kworkhorse uda-jellyfish-data-example]$ mim version
v0.14.0

I see the two containers running:
[kamran@kworkhorse uda-jellyfish-data-example]$ docker ps
CONTAINER ID   IMAGE                            COMMAND      CREATED          STATUS          PORTS                                                 NAMES
e2c37a5afa39   mimiro/objectstorage-datalayer   "./server"   16 minutes ago   Up 16 minutes   <IP_ADDRESS>:4344->4344/tcp, :::4344->4344/tcp, 8080/tcp   jellyfish
17e0946fc1aa   mimiro/datahub:latest            "./server"   16 minutes ago   Up 16 minutes   <IP_ADDRESS>:4242->4242/tcp, :::4242->4242/tcp, 8080/tcp   datahub
[kamran@kworkhorse uda-jellyfish-data-example]$

However, when I follow instructions in the README, I can't login:
[kamran@kworkhorse uda-jellyfish-data-example]$ mim login add --alias "dh1" --type=user --server="http://localhost:4242"
Login added to keyring

[kamran@kworkhorse uda-jellyfish-data-example]$ mim login ls
     | Alias | Server                | Type | Token | ClientId | ClientSecret | Authorizer | Audience | Subject
 ->  | dh1   | http://localhost:4242 | user |       |          |              |            |          |

[kamran@kworkhorse uda-jellyfish-data-example]$ mim login dh1
 SUCCESS  Updated config file
login starting...
  ERROR   Login missing configured clientId

[kamran@kworkhorse uda-jellyfish-data-example]$

What am I missing? Any help would be appreciated.

Hi, apologies, I didnt see this earlier. We have updated the security to be more standards compliant and there is a mismatch in the cli and datahub. Please pull latest datahub image and also the latest MIM cli release.

Thanks a lot. It seems to be working now.
[kamran@kworkhorse compose]$ docker-compose up -d
Creating network "compose_default" with the default driver
Creating jellyfish ... done
Creating datahub   ... done

[kamran@kworkhorse compose]$ mim login add --alias "dh1" --type=unsecured --server="http://localhost:4242"
Login added to keyring

[kamran@kworkhorse compose]$ mim login dh1
 SUCCESS  Updated config file
login starting...
login success.

[kamran@kworkhorse compose]$ mim datasets ls

# Listing datasets on http://localhost:4242/datasets

# | Dir | Items         | Name
1 |     |             0 | core.Dataset

[kamran@kworkhorse compose]$ mim dataset create ocean.jellyfish
 SUCCESS  Dataset 'ocean.jellyfish' has been created

[kamran@kworkhorse compose]$ cd ../jobs/

[kamran@kworkhorse jobs]$ mim jobs add -f sync.json
 SUCCESS  Read config file
 SUCCESS  Added job to server

[kamran@kworkhorse jobs]$ mim jobs operate load-jellyfish-data -o run

# Execute operation run on job with id: load-jellyfish-data (load-jellyfish-data) on http://localhost:4242

 SUCCESS  Job was started

[kamran@kworkhorse jobs]$ mim dataset entities ocean.jellyfish --pretty
{
  "id": "@context",
  "namespaces": {
    "ns0": "http://data.mimiro.io/core/dataset/",
    "ns1": "http://data.mimiro.io/core/",
    "ns2": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "ns3": "http://ocean.data.example.org/jellyfish/reports/",
    "ns4": "http://data.mimiro.io/models/flatgeo/",
    "ns5": "http://ocean.data.example.org/jellyfish/"
  }
}
,{
  "id": "ns3:116",
  "recorded":<PHONE_NUMBER>071927296,
  "deleted": false,
  "refs": {
    "ns2:type": "ns4:Feature",
    "ns4:geotype": "ns4:Point"
  },
  "props": {
    "ns4:bbox": [100, 456.34, 600],
    "ns4:coordinates": [32.355448, 34.790955],
    "ns5:Activity": "Yacht",
    "ns5:Area": "Center",
    "ns5:Date": "01/07/2011",
    "ns5:Distance from coast": "200 meters-1 mile",
    "ns5:Gold": "1",
    "ns5:Jellies on the beach": "1",
    "ns5:Lat.": "32.355448",
    "ns5:Location": "Had-Jsr",
    "ns5:Long.": "34.790955",
    "ns5:Month": "7",
    "ns5:Quantity": "50",
    "ns5:Report": "Offshore",
    "ns5:Report ID": "116",
    "ns5:Season": "Summer",
    "ns5:Size": "Oct-30",
    "ns5:Species": "Rhopilema nomadica",
    "ns5:Stinging Water": "1",
    "ns5:Time of submition": "9",
    "ns5:Website version": "1.0",
    "ns5:Week": "27",
    "ns5:Year": "2011",
    "ns5:Zone": "9"
  }
}
,{
  "id": "ns3:117",

[. . . output snipped . . . ]

 "ns5:Website version": "1.0",
    "ns5:Week": "28",
    "ns5:Year": "2011",
    "ns5:Zone": "19"
  }
}
,{
  "id": "@continuation",
  "token": "AAgAAAACAAAAAAAAA/U="
}
[kamran@kworkhorse jobs]$


Unsupported class file major version 61 when running

Library information:

Version:  'com.kizitonwose.calendar:compose:2.4.0-beta01'

Describe the bug**
IDE got Unsupported class file major version 61  when running project

Hi, thanks for reporting this. Kindly let me know how to reproduce this as there is not much I can do with the limited information provided.

jdk version mismatch, change Java_17 to your Java version

jdk version mismatch, change Java_17 to your Java version

Hi, thanks for reporting this. Kindly let me know how to reproduce this as there is not much I can do with the limited information provided.

this issue can be closed now. jdk version mismatch, change Java_17 to your Java version

Hi, thanks for reporting this. Kindly let me know how to reproduce this as there is not much I can do with the limited information provided.

this issue can be closed now. jdk version mismatch, change Java_17 to your Java version

I got some issues when updated to jdk 17, so it would be nice if you could downgrade calendar to like jdk11

Hi, thanks for reporting this. Kindly let me know how to reproduce this as there is not much I can do with the limited information provided.

Your project is built under jdk 17, thats why I got this problem. Please consider downgrade to support more jdk versions :)

There are no plans to downgrade the jdk version in the library, unfortunately. Sorry for the inconvenience.

Any workaround for this issue? Thanks

None that I know. But maybe some Googling might help.

There are no plans to downgrade the jdk version in the library, unfortunately. Sorry for the inconvenience.

Hi @kizitonwose I am getting the same error in my project after upgrading the library to 2.x.x. Can you please provide us the proper resolution?

@AhmadAyyaz1993 As I wrote here, I cannot reproduce this jdk version mismatch issue using the sample project. If anyone in this thread would be kind enough to provide me with a working sample project where I can reproduce this issue, I would be happy to take a look.
However, the way I see it, sooner or later most projects will be on JDK 17, so I am not even sure I want to spend a lot of time on this issue (still very happy to take a look). If you have a version that currently works in your project then stick with it until the project is ready to migrate to JDK 17.

Closing this for now as I still cannot reproduce it. As mentioned above, if someone is willing to prove a sample, I will take a look.


Upload state button not showing up

The button was not showing up for me on firefox or sahil on safari

Closed by #204


Device tracker settings are ignored

I've been using asuswrt device tracker without issue until recently. It was moved to a full on component. When I started moving things in the configuration because it was broken, I realized that interval_seconds is ignored.
From the look of it, now that it's a component, we don't parse the configuration properly. If I defined the interval in the device_tracker section, it's parsed properly the first time, but then the discovery recreate the component anyway.
This is what I have:
device_tracker:

platform: asuswrt
interval_seconds: 90

I commented out the async_listen_platform call, and now it's not every 12s as default, but every 30 (?).

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!


Add chest itself position to notification template

sometimes it would be hard to find chest, so It would be good to add chest itself's position to notification.

Would you like to adjust the comments in the config.yml? 😀


sidebarAccordion-fix

PR Fixes:

1 . This pr changes the default behaviour of sidebar accordion to toggle the currentId (file changed - src/components/sidebar.tsx)

Resolves #[Issue Number if there]
Checklist before requesting a review

[ x] I have performed a self-review of my code
[ x] I assure there is no similar/duplicate pull request regarding same issue

Need a screenshot of all the changes ser

Can you add a video of the change that is made?

@aakash2330 closing it for now too many conflicts, feel free to raise it again


Update glog to support stack trace on arm64

I'm working with an arm64 processor on Linux.
When a graph aborts due to an error, the stack trace is not printed. E.g.
F20210523 21:24:28.664880 10807 packet.h:750] Packet::Get() failed: Expected a Packet of type: float, but received an empty Packet.
	*** Check failure stack trace: ***
Aborted (core dumped)

Or, if I run google::InstallFailureSignalHandler(); in main(), I get
*** Check failure stack trace: ***
PC: @                0x0 (unknown)
Aborted (core dumped)

After some research, I found that arm64 stack trace is not supported on the glog version used in mediapipe, as indicated here:
https://github.com/google/glog/issues/531
Note that this is the glog version referenced by the mediapipe WORKSPACE file.
arm64 stack trace is now supported in glog, as of version 0.5.0.
Are you able to update the glog dependency to 0.5.0 to enable stack trace on arm64 and hence ease development?

Thanks for investigating the glog versions and limitations.  Maybe you can help me to validate MediaPipe with glog version 0.5.0.  Can you update the glog version in your mediapipe WORKSPACE file and verify that the newer version works ok and provides stack traces in your environment?
I'm glad to start updating the mediapipe WORKSPACE file in the MediaPipe upstream repository.  I believe I will be updating target "com_github_google_glog" as follows:
v0.5.0, 2021-05-07
http_archive(
name = "com_github_google_glog",
sha256 = "62efeb57ff70db9ea2129a16d0f908941e355d09d6d83c9f7b18557c0a7ab59e",
strip_prefix = "glog-d516278b1cd33cd148e8989aec488b6049a4ca0b",
urls = ["https://github.com/google/glog/archive/d516278b1cd33cd148e8989aec488b6049a4ca0b.zip"],
)
I will also need to update "com_github_glog_glog_no_gflags" and one patch to it, and have the update tested and reviewed.

Hi @DeanIsMe, Could you please check the above comment. Thanks!

Hi @DeanIsMe, Could you please respond to the above comment. Thanks!

Sorry for the delay.
About a month ago I updated the glog version in my workspace file to:
http_archive(
name = "com_github_google_glog",
sha256 = "21bc744fb7f2fa701ee8db339ded7dce4f975d0d55837a97be7d46e8382dea5a",
strip_prefix = "glog-0.5.0",
urls = ["https://github.com/google/glog/archive/v0.5.0.zip"],
)
I then had huge problems compiling mediapipe examples. Even after reverting the glog version back to the mediapipe default, my mediapipe build process failed when linking OpenCV libs. I later had issues with the mediapipe examples opening the camera stream (which uses OpenCV).
I ended up spending about a day getting the mediapipe build & run process back to a functional state.
I could try this again and record more useful information about the failures, but I'll need to wait a week or 2 so that I have a free day again >_<

I changed the http_archive for com_github_glog_glog in WORKSPACE to the comment above by hadon. When I tried to build a mediapipe project, this is the error that I received:
ERROR: /home/lounge/Lounge-client/Lounge_mediapipe/third_party/BUILD:22:11: no such package '@com_github_glog_glog//': The repository '@com_github_glog_glog' could not be resolved and referenced by '//third_party:glog'
ERROR: Analysis of target '//mediapipe/lounge:lounge_main' failed; build aborted: Analysis failed
INFO: Elapsed time: 3.628s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (4 packages loaded, 5 targets configured)

I am facing a similar issue as @DeanIsMe
When using mediapipe facemesh in a loop, first a warning about glog:
WARNING: Logging before InitGoogleLogging() is written to STDERR
F20211111 12:28:54.792228 380909056 threadpool_pthread_impl.cc:51] Check failed: res == 0 (35 vs. 0) pthread_create failed
*** Check failure stack trace: ***

Hi @DeanIsMe ,
Are you still looking for the resolution on this issue.

Hi @sureshdagooglecom, I am not working with mediapipe for now. However, I think stack trace on ARM64 would be valuable to many users.

Hello @DeanIsMe,
We are upgrading the MediaPipe Legacy Solutions to new MediaPipe solutions However, the libraries, documentation, and source code for all the MediaPipe Legacy Solutions will continue to be available in our GitHub repository and through library distribution services, such as Maven and NPM.
You can continue to use those legacy solutions in your applications if you choose. Though, we would request you to check new MediaPipe solutions which can help you more easily build and customize ML solutions for your applications. These new solutions will provide a superset of capabilities available in the legacy solutions.


Generate html output from a template

Implement html output generation as a whole using a jinja template instead to generate using rust code to write the html by parts.

it is perfectly done.


Fix: Deleted files were still cached as "added" after "git rm" was ex…

Deleted files were still cached as "added" after "git rm" was executed. This causes a revert to fail if, for example, you create a new actor in unreal, then delete it. To reproduce:

Create a new actor and save it to disk. Unreal should automatically stage it for commit upon saving.
Delete the file. Unreal with automatically run "git rm", but fails to update the cache.
Click Source Control -> Revert, then OK to the prompt.
Unreal complains that the file you deleted doesn't exist and says the revert failed.

Great, thank you!


[Enhancement]: 'Snake Game' Design Enhancement

Is your enhancement request related to a problem? Please describe.➕
Is your enhancement request related to a problem? Please describe.➕
No. It's an enhancement in the existing design of the game.
Screenshots
Current Design

Expected Updated Design

Describe the solution you'd like
Working on the styling properties of the game in order to improve its design.
Improving the colors, margin, padding, etc. of the game.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @iamRabia-N !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @iamRabia-N ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Sparse label training with very low ACC

hello, Dr.HuguesTHOMA,

When I modified the loda_subsampled_clouds function to facilitate label sparse extraction for sub_lables, and the procedure runs, it is very strange that the ACC is almost 0, but there are results when validating. As shown below, could you give me some advice?

In this case, I won't be able to help too much, because you are trying new stuff that was not in my original code. You have to debug what happens, try printing the values of the predicted labels, are they all zeros? Try verifying the target labels in the loss function of the network, etc...


Add SPM Support.

Adds support for Swift Package Manager. Since Swift and C-family languages have to be split up, they are listed as two separate targets.

Hmm.. Since SPM requires that they be split up under two targets building normally fails.

Thanks for contributing 👍🏻


chore: classify "apply → induction" porting notes

Classifies by adding issue number #11443 to porting notes claiming

apply → induction

@eric-wieser I've resolved the  "apply → induction" porting notes by removing them.


Code blocks do not wrap

Code blocks do not wrap, this is not desirable for PDFs.

It probably won't matter because I reckon most people don't include code in their gamebook. But I intend to use it on the tutorial and example document, so it's nice if it would get fixed.

Closing, this currently works in the ff.css stylesheet.


ARROW-16617: [C++] Add support for multi-byte system error message on Windows

Did you validate that it fixes the issue?

Partially, yes. I just confirmed that C++ uses UTF-8 instead of not the current code page but didn't confirm for PyArrow.
I used $BUILD_DIR/DEBUG/arrow-file-to-stream.exe XXX to confirm this. It outputs Could not convert to stream: IOError: Failed to open local file 'xxx'. Detail: [Windows error 2] 指定されたファイルが見つかりません。 on Japanese Windows. The output encoding was changed to UTF-8 from ShiftJIS (the current code page on Japanese Windows) with this change.

Now rebased.


Extend the Functionality of the JavaScript Language Service

VSCode Version: 1.10.2
OS Version: Lubuntu 16.04 (Linux 4.8.0-41-generic)

The Problem:
The JavaScript Language Service doesn't recognize interfaces defined in .ts and .d.ts files.
As a result, interfaces doesn't show up in the "quick suggestions" list.
Moreover, interfaces and even classes defined in those files cannot be used to declare types using JSDoc comments.
This prevents the programmer from taking advantage of the contract defined in the interface or class to write type-checked and bug-free code.
The Proposal:
JavaScript IntelliSense is provided through the TypeScript Language Service.
As of now, the TypeScript Language Service has been used already to provide the same functionality described above in other products. See Here
Here is the relevant part of the article:

Because JavaScript and TypeScript are now based on the same language service, they are able to interact in a richer way. For example, JavaScript IntelliSense can be provided for values declared in a .d.ts file, and types such as interfaces and classes declared in TypeScript are available for use as types in JsDoc comments.
Below, we show a simple example of a TypeScript definition file providing such type information (via an interface) to a JavaScript file in the same project (using a JsDoc tag).

It seems possible that we can extend the functionality of the TypeScript Language Service to provide such a cool and needed feature like this.
I would love to work on this. Sadly, I don't have experience with the VSCode project.
Nevertheless, Everyone in the VSCode community who can help or provide technical insights is very much welcome.

Thanks you for the write up.
I believe we already do what you describe.
For one, d.ts files from @types power our Javascript intellisense for external modules. You should also be able to create local d.ts that enrich your JavaScript intellisense.
As for mixed JS and TS projects, try creating a tsconfig.json file at the root of your workspace with allowJS set:
{
    "compilerOptions": {
       "allowJS": true
     }
}

This will allow you to use JS and TS files in the same projects

Could you please provide examples of what is currently not working for you in these scenarios?

I think I didn't clarify what I meant.
Here is an example (.ts file):
export interface Person
{
    firstName: string;
    lastName: string;
    age: number;
}

export class Employee implements Person
{
    firstName: string;
    lastName: string;
    age: number;
    jobTitle: string;
    salary: number;

    constructor(firstName: string, lastName: string, age: number,
                jobTitle: string, salary: number)
    {
        this.firstName = firstName;
        this.lastName = lastName;
        this.age = age;
        this.jobTitle = jobTitle;
        this.salary = salary;
    }

    getPersonalInfo(): string
    {
        // code
    }

    getJobDescription(): string
    {
        // code
    }
}

What goes wrong?
After compiling the example above into the corresponding .js and .d.ts files, then using the produced .js file in a require() statement, the following problems occur:

JavaScript IntelliSense doesn't recognize interface Person and, as a result, it doesn't appear in the "quick suggestions" list.
IntelliSense doesn't recognize class Employee or interface Person as a type in the JSDoc comment, which means, for example, that a function parameter of type Employee will be treated as if it has type any.

For example (.js file):
var ex = require('./the_previous_example.js');

/**
 * @param {ex.Emplyee} employee
 * @param {string} newJobTitle
 * @param {string} newSalary
 */
function promoteEmployee(employee, newJobTitle, newSalary)
{
    employee.jobTitle = newJobTitle;
    employee.salary = newSalary;
}

The problem is that parameter employee is treated as a variable of type any and as a result, its members (such as jobTitle & salary) are NOT recognized by IntelliSense.
Moreover, the function signature is wrong. As a result, it diminishes the usefulness of IntelliSense because the programmer needs to go back and read the function definition if he is not familiar with the function.
Here is the "Function Signature" as reported by VSCode:

function promoteEmployee(employee: any, newJobTitle: string, newSalary: string): void

Final Comment
Currently, I am working on Node project that requires extending some of the built-in node functionality.
However, I feel like getting lost between variables and parameters, all of whom have the type any.
I mean I am unable to declare that this variable should have the type ReadableStream or declare that this parameter is supposed to be http.ServerResponse.
This is because ReadableStream and ServerResponse are "interfaces" and Not recognized by IntelliSense, and even if they were "classes" they would also be Not recognized because of JSDoc inability to recognize classes and interfaces as "types".
What I meant in the first post is that it seems possible to add this functionality as described Here.
Here is a quote of the functionality that is being discussed:

Because JavaScript and TypeScript are now based on the same language service, they are able to interact in a richer way. For example, JavaScript IntelliSense can be provided for values declared in a .d.ts file, and types such as interfaces and classes declared in TypeScript are available for use as types in JsDoc comments.
Below, we show a simple example of a TypeScript definition file providing such type information (via an interface) to a JavaScript file in the same project (using a JsDoc tag).

Thanks for the more detailed explanation. Your example should work using import statements such as:
import {Person} from './x'

/**
 *
 * @param {Person} e
 */
function func(e) { }

or
import * as ex from './x'

/**
 *
 * @param {ex.Person} e
 */
function func(e) { }

The problem with require not picking up types is tracked by https://github.com/Microsoft/TypeScript/issues/14056 We're working with the TypeScript team to get this fixed


The Desktop Icon of the exported executable is blurry

Godot version
3.5 Steam version
System information
Windows10
Issue description
The Desktop Icon of the executable is blurry and I don't know how to fix this. I already redownloaded rcedit, cleared the cache, restarted the computer and reexported the project, but it is still blurry. (the .pck is not embeded)

Please help me
Steps to reproduce
It worked fine 2 weeks ago, but yesterday, when I wanted to export my game, a error message appeared, saying I would need to update to 3.5. After the update finished, I exported the game, but for some reason the Desktop icon was really blurry.
Minimal reproduction project
No response

This is not a Godot issue. The .ico file you're using needs to contain all the sizes required for proper hiDPI support. There's an ImageMagick command listed in the documentation which you can use for this purpose.

Thank you for the reply
The .ico file contains all sizes which are suggested in the docs, also it worked earlier only after the update it doesn't work
Ico.zip
.

I zoomed in on it, it works in windows by itself so that means Godot malforms it no?
Could you download resource hacker and check if the icon is properly overridden?

download image magic display then converts the png to ico using this command:
magick convert icon.png -define icon:auto-resize=256,128,64,48,32,16 icon.ico
then add it to you're project and export it to a different folder then it's good

Silenced Person i downloaded resource hacker what now?
Outseet i already have a ico file why do it again?

@Nikzea because it's giving more quality and resolution are great and also it'S better and faster than do it your self and it's in Godot documentation I think using image magic display is going to fix it

@Nikzea also change the export to a new path

Silenced Person I downloaded resource hacker what should I do now?
Outseet I already have a ico file why do it again?

drag and drop your game.exe into the resource hacker

You should see something like this but the godot icon will be replaced by your icon.
is that correct?

@SilencedPerson  yes it's correct he need that his .ico file have all the resolution:
256,128,64,48,32,16
and this by using a software scale it like gimp or fastest way is using ImageMagick

@SilencedPerson yes it's correct he need that his .ico file have all the resolution: 256,128,64,48,32,16 and this by using a software scale it like gimp or fastest way is using ImageMagick

Outseet, his Icon does indeed have all the correct resolutions, we are trying to determine if Godot malforms it. ImageMagic won't help in this case as we are not determining if he has correct formatting but if Godot has a bug or not.

@SilencedPerson yes it's correct he need that his .ico file have all the resolution: 256,128,64,48,32,16 and this by using a software scale it like gimp or fastest way is using ImageMagick

Outseet, his Icon does indeed have all the correct resolutions, we are trying to determine if Godot malforms it. ImageMagic won't help in this case as we are not determining if he has correct formatting but if Godot has a bug or not.

i was using gimp and it'S giving me blurry icon and I have all resolution when I used ImageMagick it worked and it's great

wait i have found something did you Clear the Icon Cache it maybe works I found it on youtube and documentation

That is still not the point, his icon is correct.
Godot should be able to use it.
Please, stop read the issue again, he did clear his cache and the ICON did work in the past.

That is still not the point, his icon is correct. Godot should be able to use it.
Please, stop pointlessly commenting and read the issue again, he did clear his cache and the ICON did work in the past.

ok but i use the same version and it's working maybe it's a bug

he did clear his cache and the ICON did work in the past.

Clearing font icon caches in windows is notoriously unreliable, something could have corrupted on one export, and then be fixed but windows might not decide to display it for another few days.

Sorry for only replying now, but I went to bed.

You can also download the exe on itch
https://nikzea.itch.io/marble-testing-facility

Oh I think I see the Problem for some reason the images are assigned to the wrong resolution

Yep, they seem to be in inverse order. Can you somehow verify that this is problem with the ICON? Or does this happen in Godot?
It seems to me that it is the later, since the icon works before the project is imported.

I reversed the order in gimp but it still shows the same in Resource Hacker and the icon is still blurry.

I reversed the order in gimp and now resource hacker shows it in the right order but it is still blurry.

SilencedPerson it should be a Problem with the new Godot version because in 3.4 it worked fine and I didn't change anything in the ico file since than.

CC @bruvzg

Godot do not do anything to the icon, it's only feeding it to the rcedit, so it's probably something with the export template. The only 3.5 change that might be responsible for is this is - https://github.com/godotengine/godot/pull/57850

I solved the problem, after exporting to linux the icon is now how it should be.

So Godot holds your icon ransom until make a linux export. Good.

I can confirm this bug, it was driving me crazy D:
(I did everythig as the doc says, my icon had all the sizes, I made it using the imagick command (but also tried GIMP, online generators, etc)). But nothing.
After exploring the .exe in Resource Hacker I saw that it was also pairing wrongly the image and the resolution.
The thing that worked was also reverseing the order of the .ico:
A) In Gimp

B) Reverseing the order of sizes in the magick command:
Using this:
magick convert icon.png -define icon:auto-resize=16,32,48,64,128,256 icon.ico
Instead of resize=256,128,64,48,32,16 (as the doc says).
Both things worked correctly, and I also tried the to use the "reversed" icon normally in other folders and shortcuts and they work as expected. Seems like the order is only relevant for Godot when exporting.

I recently had the same problem. Using godot 3.5.1 stable. As much as I use magisk and the command to clear cache (following everything the documentation says) and the icon still appears blurry.

Attached .ico file and .exe file
icons.zip

So the issue is size order, rcedit only set it correctly if new icon have the same order as icon already in the executable.
https://github.com/godotengine/godot/pull/57850 icon has it reversed, so only icons with 16,32,48,64,128,256 sizes will work, and with old icon only 256,128,64,48,32,16 was working, it's not directly related to the compression.

ICO format is quite simple, so I guess we can preprocess ICOs (and allow generating one from PNG) and correct the size order during export.

I've submitted two pull requests to resolve this issue in the docs. One for the order reversal and another for some troubleshooting tips after the order is fixed: https://github.com/godotengine/godot-docs/pull/8564.


Problem when copy and paste multiline with Unicode(Non English)  characters

when copy and paste non english characters change to "?"
" ?? ?????? ???? ?????" ;

I can't reproduce this with non-english characters. Can you share the characters here that causes the issue, please?

Yes. Orginal  html:

صفحه اصلی

کارتابل

when copy and pasted:

???? ????

???????

Thank you!  problem solved.


extended datasets

pvc0 and pvc2 in same file for all notebooks

Will remain under review until we get permissions on the HELIUS dataset, and then this also needs to be put together

Completed, but datasets extended with even more variables


Add job to validate commit messages

@rsalevsky so why exactly do we need to enforce SCRD or bsc's in the git commit subject?

@dirkmueller maybe because the subject automatically ends up in rpm .changes files (via trackupstream) which automatically triggers bugzilla updates by my 'obsbugzilla' scripts.
Also other tracking by QAM might be helped.
I guess, as an alternative, we could extend the change-entry generation behind trackupstream to also pull in bug references outside the subject. @aspiers might be interested

@bmwiedemann I am okay with referencing bugs if there is a bug referenced. but requiring a bugreport for every commit seems strange

I took the current ardana policy as a reference. If I'm not mistaken then it is a SCRD or a bsc reference correct?

Other projects solve this by marking certain patches as "trivial" that dont require NEWS entries and bug refs.
E.g. we dont want to open a bug for every documentation typo fix. Probably users wouldnt even want to read it in the changelog, because it makes finding relevant changes harder (aka SNR)

@jesusaurus I don't think there is much to discuss as there is a technical reason for this. For the package changelog we only use the header and as the bsc has to be visible in the changelog it has to be in the header.

@bmwiedemann commented on 10 Sep 2018, 09:05 BST:

@dirkmueller maybe because the subject automatically ends up in rpm .changes files (via trackupstream) which automatically triggers bugzilla updates by my 'obsbugzilla' scripts.
Also other tracking by QAM might be helped.
I guess, as an alternative, we could extend the change-entry generation behind trackupstream to also pull in bug references outside the subject. @aspiers might be interested

@bmwiedemann I proposed this ~11 months ago: https://github.com/openSUSE/obs-service-tar_scm/issues/207
If you are in favour then please add your support there and help the objectors to see the light ;-)

@rsalevsky commented on 18 Sep 2018, 15:39 BST:

@jesusaurus wrote:

The job looks good as-is, but this change should also add a trigger so that the job will run automatically.
Also, this seems to be a good time to re-consider requiring bugs/tickets in the commit subject (I personally think they belong in the commit footer, but lost that battle last time around);

@jesusaurus You didn't lose that battle because it hasn't even really started in earnest yet, let alone been won or lost :-)

though that is a discussion is too large to happen in review comments, so maybe it's time to start an email thread on the topic?

I already made the proposal in https://github.com/openSUSE/obs-service-tar_scm/issues/207 - please add your feedback there.

@jesusaurus I don't think there is much to discuss as there is a technical reason for this. For the package changelog we only use the header and as the bsc has to be visible in the changelog it has to be in the header.

@rsalevsky You are assuming the status quo cannot change, but that is not true.  As I wrote about this topic on cloud-devel last year:

Let's ensure the tools work for us, rather than us working for the tools ;-)

@jesusaurus please go ahead, I think that at the beginning it slows thing but in the mid/long term it forces us to follow best practices and document better the changes

Also, this seems to be a good time to re-consider requiring bugs/tickets in the commit subject (I personally think they belong in the commit footer, but lost that battle last time around); though that is a discussion is too large to happen in review comments, so maybe it's time to start an email thread on the topic?

@aojea commented on 19 Sep 2018, 08:52 BST:

@jesusaurus please go ahead, I think that at the beginning it slows thing but in the mid/long term it forces us to follow best practices and document better the changes

I agree it's a discussion worth having sooner rather than later.

Also, this seems to be a good time to re-consider requiring bugs/tickets in the commit subject (I personally think they belong in the commit footer, but lost that battle last time around); though that is a discussion is too large to happen in review comments, so maybe it's time to start an email thread on the topic?

Or maybe just propose a spec and announce it on cloud-devel, so that the majority of discussion happens as a review on the spec?  I suspect we'll make faster progress that way.  It's too easy for a mailing list thread to turn into bike-shedding ;-)


Update documentation

I thought it would be nice to have one page per iterative method and give some short, general information about the method as well as a few lines on notable implementation details.

See https://haampie.github.io/IterativeSolvers.jl/latest/
I think it is done

I've also added a section on the "iterator approach" https://haampie.github.io/IterativeSolvers.jl/latest/iterators.html


Performance degradation after running snakemake for some time

Snakemake version

Snakemake 8.16.0
Describe the bug

When running snakemake for a certain period of time, the scheduler gradually becomes lazy. Job finalization, job selection and job starting will all become slower and slower.
Correspondingly, the NLWP in htop (which is the number of threads) of snakemake main process gradually increases, from ~100 to ~1000. CPU usage also increases. The number of opened /proc/****/stat in lsof output also increases.
This issue is observed in both snakemake 7 and the newest snakemake 8, and in both local executor and slurm executor. It seems that performance degrades faster when the number of files or jobs is large.
For possible reason of this issue, without much time to dig further for now, my current guess is some kind of performance degradation with concurrent.futures.ThreadPoolExecutor in the executor, or with asyncio event loop.
Logs

Minimal example

Additional context

I am observing the same symptoms - after about 20k jobs, Snakemake takes a minute to submit the next (small) set of jobs.
I am not seeing an increase in NLWP, however. What I'm seeing is lots of stat() and openat() calls on `.snakemake/metadata'. Always the same pattern: stat, openat, fstat, read, close, repeating 5 times for the same metadata file, then moving on.
I'm on 7.32.2 with this .

I am observing the same symptoms - after about 20k jobs, Snakemake takes a minute to submit the next (small) set of jobs.
I am not seeing an increase in NLWP, however. What I'm seeing is lots of stat() and openat() calls on `.snakemake/metadata'. Always the same pattern: stat, openat, fstat, read, close, repeating 5 times for the same metadata file, then moving on.
I'm on 7.32.2 with this .

Maybe you can try removing .snakemake/metadata and use --drop-metadata when running snakemake. This improves performance a lot in my cases, though it will still degrade, just degrades slower.

To clarify:
This is not about general performance issues with metadata or DAG build (tag = enhancement).
This is about the severe degradation during run time. It can be fixed by restarting Snakemake (tag = bug).
Something is accumulating while Snakemake operates and eventually leads to <1 job/minute scheduled. There is a bug somewhere.

It appears that my use of --notemp for development purposes also had a large negative impact, possibly even causative. Without this, it seems to work acceptably again.

@laf070810 Are you using checkpoints in your pipeline? I've done some debugging with PDB. My issue is somewhere inside update_checkpoint_dependencies(). If you aren't, I should probably make a different ticket for my issue.

@laf070810 Are you using checkpoints in your pipeline? I've done some debugging with PDB. My issue is somewhere inside update_checkpoint_dependencies(). If you aren't, I should probably make a different ticket for my issue.

I have use cases both with checkpoint and without checkpoint, and the performance degradation looks basically the same.

@johanneskoester I've been looking over the code in that area and used signal triggered yappi to see where it's eating through so many cycles at least on my end. A few questions:

Any reason why the dag.finish() process is run for each job individually? It can handle group jobs, so it should be able to bulk finish everything that completed in one round. That might save a little bit.
The cache is turned off after the launch phase, and there is a note that it mustn't be turned on again. When the rerun triggers are on, this means that the metadata file is even read several times for each file (that's why I was seeing 5 stats per file, one for each trigger type). Is there any reason not to, say, have a "with" block around the postprocess step that enables a temporary cache? To avoid redundant reads and stats on the same files over and over.
There may be some deeper issue here since it is indeed degrading. It's just doing too much. It might be related to "collect" type jobs that pick up lots of results and get updated with every completed job.

CC @tamasgal - this may be a similar concern as your ticket.


Adds vmservices to retrieve android applink settings

fixes https://github.com/flutter/flutter/issues/120408
Added two gradle tasks, one for grabing the application id, one for grabbing app link domains.
Added a new vmservices to call these two gradle tasks and return the result.
The expected work flow is that the devtool will first call a vmservices to grab all avaliable build variants. It will then choose one of the build variant and call this new services to get application id and app link domains.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hi, @chunhtai is this still a work in progress? Seems like you have some tests failing

These tests failures seem to be related to https://github.com/flutter/flutter/issues/126557


global translateKey method

hey @PanJiaChen ,
I was looking at the new login/index.vue page and I saw the method:
translateKey(key) {       return this.$t('login.' + key)     },
Wouldn't it be better if this method was made global as a mixin or something so all component can use it instead of declaring it again on each component?

I have some hesitation in this part of the code. May be direct use vue-i18n global function $t is the most simple and convenient. But I'm afraid a lot of beginners don't know what this is.

I thought about it, l wii direct use vue-i18n global function $t and add it to documentation.

Sounds good, anyone delving into an admin interface made with vuejs should be able to search for something he didn't understand.


(i18n): Request to add Japanese Documentation

Subject
Request to add Japanese Documentation
Description
First of all, thank you chakra-ui community for this awesome library!
I've just started usnig chakra and I think its wonderful!
But, It's hard for some Japanese developers to read English documentation.
Therefore, I would like to add Japanese documentation.
I can help with the Japanese translation if need be.
Thank you.

Closing translation issues for now. See https://github.com/chakra-ui/chakra-ui-docs/issues/86#issuecomment-983356376.


delay when changing speed with slickSetOption

when calling .slick('slickSetOption', 'speed', $otherspeed, false);
there is a huge delay until the new Option is being used.
====================================================================
[  https://jsfiddle.net/b0r7/tdfo1z0f/  ]
Fiddle Link
====================================================================
Steps to reproduce the problem

call .slick('slickSetOption', 'speed', $otherspeed, false);

where $otherspeed is a different speed than the original configured speed
====================================================================
What is the expected behaviour?
After calling slickSetOption have the new parameter be applied (almost) instantly
====================================================================
What is observed behaviour?
Huge Delay

====================================================================
More Details
Which browsers/versions does it happen on?

Chromium Version 49.0.2598.0 (64-bit)

PaleMoon Version: 26.2.2 (x64)

Firefox Developer Edition 48.0a2 (2016-05-24)

Which jQuery/Slick version are you using?
latest (as of 2016-05-24)

Hey @b0rt thanks for making the issue. Correct me if I'm mistaken, but it seems like the delay just the time remaining on the transition of the current slide. Unfortunately, the library's support for linear continuous scrolling is not well developed, so there's no existing support for it. I wish you luck in trying to hack a solution together!


Implement number-range validation and test it

Implements: https://github.com/Palindrom/Palindrom/issues/170 & https://github.com/Starcounter/level1/issues/4016

https://github.com/Palindrom/Palindrom/issues/170

Thank you! Your comments inspired me a lot of other enhancements.


Unable to connect to Radarr and Sonarr

I installed Petio on my Qnap NAS using docker-compose, as described here: https://docs.petio.tv/install-guides/docker.
Installation works fine and I can access Petio on the IP address of my NAS: <IP_ADDRESS>:7777.
Going through the setup also works fine.
However, configuring Radarr or Sonarr fails. When I test the connection, I get connection failed.
Petio uses a separate petio-network in bridge mode.
I have Radarr and Sonarr also setup using a different network using gluetun. All Radarr and Sonarr traffic goes through a VPN using the gluetun app. The ports for Radarr (7878) and Sonarr (8989) are configured in gluetun. The gluetun network has an IP address of  <IP_ADDRESS> and a gateway address of <IP_ADDRESS> (but I believe these are only internal on the NAS, I cannot access these directly from my PC). I can access Radarr and Sonarr by using the IP address of my NAS though: <IP_ADDRESS>:7878 and <IP_ADDRESS>:8989 work perfectly fine.
When setting up Radarr and Sonarr in Petio, I use the IP of my NAS: <IP_ADDRESS> and the ports 7878 (Radarr) and 8989 (Sonarr). But  testing the connection fails.
I have also tried using <IP_ADDRESS> and <IP_ADDRESS> but they won't work either. Also using the hostname gluetun of the gluetun container doesn't work.
How can I get this to work?

Put your gluetun container on the Petio network and use container names or figure out your config so it routes the traffic properly with your VPN from Petio. This isn't a bug, this is you making your life harder by VPNing your sonarr/radarr when they shouldn't be.

Sorry, I should have used discussion instead of creating a bug.
Managed to get it working without defining a separate petio-network.


The Schema should contain ApplyToExecutable for the parameter

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.

Steps to reproduce
see issue: https://github.com/PowerShell/Crescendo/issues/30
Expected behavior
See issue: https://github.com/PowerShell/Crescendo/issues/30

Actual behavior
See issue: https://github.com/PowerShell/Crescendo/issues/30

Error details
Object model currently supports ApplyToExecutable - missing from Schema. Tests are already included.

Environment data
See issue: https://github.com/PowerShell/Crescendo/issues/30

Version
1.0
Visuals
No response

fixed in #161

Thank you! Fixed/closed - in release: https://www.powershellgallery.com/packages/Microsoft.PowerShell.Crescendo/1.1.0-RC1


Add @lelia as triager

I'm nominating myself for the triager role. I have been an active participant in and facilitator of Scorecard community meetings for the past ~6 months, most recently doing work on issue triage, label cleanup, survey feedback and persona development.

meeting notes

Following our contributor ladder:

Have been active in the community for more than 1 month
Have reported issues / feedback on various Scorecard projects, contributed to Scorecard Monitor
Have knowledge about the codebase (from a technical and project management perspective)
Have actively participated in community meetings since January

cc: @spencerschrock @justaugustus

I am recused from sponsorship, given @lelia is my direct report.
Tagging @ossf/scorecard-maintainers @jeffmendoza for sponsorship!

I can be the sponsor. Thanks Lelia for your help managing the issues and survey data

(Assigned to @spencerschrock and put this on today's agenda for discussion.)

+1, thank you Lelia!

+1

Welcome to @ossf/scorecard-triagers, Lelia!


Not storing settings

The Pipeline ID and Run index values I enter do not get saved.
Also, no matter what Project I use the icons all change when there is an update to 1 of the pipelines.

The Pipeline ID and Run index values I enter do not get saved.
Also, no matter what Project I use the icons all change when there is an update to 1 of the pipelines.

Looking into it

Any luck?

I experience the same issue as OP. Please inform us if you have a chance to look into it. Atm running StreamDeck 6.0.2 (17735) on MacOS 12.6.3

Has been fixed. New Update send to Elgato (v1.1) and will available soon.


Update CI

codecov.yml to ignore directories on Codecov
Include drone.bat to run Windows tests

At https://drone.cpp.al/CPPAlliance/url/settings/secrets the codecov_token secret should be re-added with Pull Requests enabled.

Merged, thanks


Crash on Xiaomi Mi 9T Pro (Out of Memory or GPU related)?

Good day, I am moving a marker with these lines of code every time there is a location update.
    cameraBuilder.bearing((float) MarkerUtil.bearingBetweenLocations(from, to))
    .target(to)
    .zoom(16f);

   cameraBuilder.tilt(0).zoom(16f);

    CameraPosition position = cameraBuilder.build();
    CameraUpdate cameraUpdateFactory = CameraUpdateFactory.newCameraPosition(position);

    mMap.animateCamera(cameraUpdateFactory);

    final ValueAnimator valueAnimator = ValueAnimator.ofFloat(0, 1).setDuration(3000);
    final MarkerUtil.LatLngInterpolatorNew latLngInterpolator = new MarkerUtil.LatLngInterpolatorNew.LinearFixed();
    valueAnimator.setInterpolator(new LinearInterpolator());
    valueAnimator.addUpdateListener(valueAnimator1 -> {

        if (isDestroyed())
            return;

        float v = valueAnimator1.getAnimatedFraction();
        LatLng newPos = latLngInterpolator.interpolate(v, from, to);
        currentMark.setPosition(newPos);
        currentMark.setAnchor(0.5F, 0.5F);
        currentMark.setRotation((float) MarkerUtil.bearingBetweenLocations(from, to));
        oldLatLng = to;

    });
    valueAnimator.start();

And it works fine but when I change the camera view and angle with this
cameraBuilder.tilt(90).zoom(20f);
then move around for a couple of seconds it will crash but all I got from logcat was a huge number of this:
2020-08-26 15:16:27.588 11903-16505/? E/Adreno-GSL: <gsl_memory_alloc_pure:2297>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed. W/Adreno-GSL: <sharedmem_gpuobj_alloc:2713>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
So far I only tested this with 2 device and only occur with Xiaomi Mi 9T Pro device but everything seems okay on LG K10 K430dsy.

Looks like this issue isn't related to the samples available in this repository and instead potentially an issue with the Maps SDK for Android itself. I recommend filing this on our Issue Tracker to receive better support. Please also provide a more detailed stack trace to help with debugging this issue.


Using recommenders in my own codebase

Description
Looking for best practices on how to use recommenders and especially reco_utils with my own codebase. Do I simply clone the repo in a parallel directory and then reference reco_utils that way? I see #774 but until it is available via pip or conda, I'm not sure how best to do this.
Other Comments

Hey @atimesastudios so far the recommended way to use reco_utils is to clone the repo and reference the utilities in reco_utils as modules in your Python own scripts/codes.

Thank you @yueguoguo


Does not detect MPLv2 header in source file

lib.rs
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at http://mozilla.org/MPL/2.0/.

struct X;

$ askalono --version
askalono 0.3.0

$ askalono id --optimize src/lib.rs
Error: Confidence threshold not high enough for any known license

The MPLv2 has the following exhibit which confirms that the header is correct:
Exhibit A - Source Code Form License Notice
-------------------------------------------

  This Source Code Form is subject to the terms of the Mozilla Public
  License, v. 2.0. If a copy of the MPL was not distributed with this
  file, You can obtain one at http://mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely to look
for such a notice.

Interesting, I'd have thought that MPL header would be in the SPDX dataset but it doesn't appear to be. This is something that'll need to get fixed on that end; I'm happy to get that going but acknowledge that I can be a bit slow on that point.
I think https://github.com/spdx/license-list-XML/blob/master/src/MPL-2.0.xml more or less needs a standardLicenseHeader block, and then the license-list-data repository needs to be regenerated.

You're not wrong; we should add the license header text to the definition of that license. But I'd also ask you to consider using SPDX Short Identifiers in source code, for a more succinct and more machine-friendly application of any license on the SPDX License List to your sources: https://spdx.org/ids
Up to you and your project, of course, but I mention because not a lot of people know about that option.

@bradleeedmondson Absolutely, SPDX short identifiers are the way to go. But in this case, askalono is something that tries to identify licenses from texts -- the issue here is that some of the text it should be identifying is missing from its dataset.

https://github.com/spdx/license-list-XML/issues/849 has been fixed.
Can we update askalono to include this header so this issue may be closed?

Working on pulling in new SPDX data now. Interestingly, it's causing a unit test to fail (a self-test to ensure MIT is detected as MIT). I suspect the format may have changed slightly. Digging into that.

Pulled in and verified:
❯❯❯ cat test.txt
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at http://mozilla.org/MPL/2.0/.

struct X;

❯❯❯ just cli id --optimize ./test.txt
 ...
./target/release/askalono id --optimize ./test.txt
License: MPL-2.0 (license header)
Score: 0.972
Containing:
  License: MPL-2.0 (license header)
  Score: 1.000
  Lines: 0 - 4
  Aliases: MPL-2.0-no-copyleft-exception

This will go out in the next release, which I hope to prepare soon. :)


move route_ack_test

e2b9f372-0b67-432b-abc7-16671298885c

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.423%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1050

Relevant Lines:
1491

💛  - Coveralls


face_location and face_encoding

face_recognition version:
Python version:
Operating System:

Description
hi this is not an issue but more of a question. i have successfully detected faces using the face_location with cnn model. i saw that it locates the faces in a left to right direction. before the face_compare, the usual thing to do is face_encoding and after invoke the face_compare. i return results as json so that i can examine it on the browser looking at the result. i saw that the face_encoding locates the faces from right to left. is there a way to tell the face_encoding to do the same as that of the face_location? i am currently making a web service. the procedure is first i upload the photo to get the locations, then display a box on the detected faces for reference, then do a face_compare in order of faces detected.
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

If you are already detecting the face locations first as a separate step, you can pass those face locations into face_encoding() so it doesn't have to re-detect them.  That makes it easy to match them up to draw boxes around them.
You can look at these lines in the webcam example to see how that works.

thank you for the guidance got it working on the front end also


Ability to disable plugins

I've had a good look around, but can't seem to find it.
I'm trying to find a way to disable the tiling plugin, and tie that to a KHD hotkey set, so I can disable tiling at will.
Is there something like this? Perhaps it's related to unloading plugins, but that didn't seem to work out for me directly in KHD or the terminal

To unload
chunkc core::unload tiling.so

To load
chunkc core::load tiling.so


 Are you able to clone other repos, or git clone and build the project manually without go get?

i apologize it happened a couple of times in a row and other(smaller) repos were getting cloned with no errors in the meanwhile.  must have been because of network issues


Wrong indentation when the last line in a case is a right brace

Description
The indentation is wrong if the last line of code is a right brace in a case code block.
However, if you put another statement (something other than a comment) after the right brace, it becomes correct.
Input
The code looked like this before beautification:
switch (a) {
    case 'foo':
    case 'bar':
        if (foo == bar) {
            console.log(a);
        } else {
            console.log(a);
        }
    case 'baz':
        console.log(a);
}

Expected Output
The code should have kept the same after beautification:
switch (a) {
    case 'foo':
    case 'bar':
        if (foo == bar) {
            console.log(a);
        } else {
            console.log(a);
        }
    case 'baz':
        console.log(a);
}

Actual Output
The  code actually looked like this after beautification:
switch (a) {
    case 'foo':
    case 'bar':
        if (foo == bar) {
            console.log(a);
        } else {
            console.log(a);
        }
        case 'baz':
            console.log(a);
}

The last case is mistakenly indented.
If you add one line after the brace, it will keep the same:
switch (a) {
    case 'foo':
    case 'bar':
        if (foo == bar) {
            console.log(a);
        } else {
            console.log(a);
        }
        console.log(a);
    case 'baz':
        console.log(a);
}

Environment
OS: macOS 10.14.5
Settings
As default:
{
  "indent_size": "4",
  "indent_char": " ",
  "max_preserve_newlines": "5",
  "preserve_newlines": true,
  "keep_array_indentation": false,
  "break_chained_methods": false,
  "indent_scripts": "normal",
  "brace_style": "collapse",
  "space_before_conditional": true,
  "unescape_strings": false,
  "jslint_happy": false,
  "end_with_newline": false,
  "wrap_line_length": "0",
  "indent_inner_html": false,
  "comma_first": false,
  "e4x": false,
  "indent_empty_lines": false
}

@bitwiseman Hello! Can I give this issue a try?

@marianayap Please do!

@bitwiseman Hello! I won't be able to continue with the issue. It's open for anyone that wants to contribute. Thank you!

@bitwiseman Hello! I won't be able to continue with the issue. It's open for anyone that wants to contribute. Thank you!

Hello, I have been given a  task to contribute to an open source repo and I am interested in this project! Could I please be assigned this issue?


Add waits in ListenerPrimaryTests to mitigate race with List.Add

Same fix @natemcmaster applied in #1769.

We should do this across all branches (1.0, 1.1 and dev), to all applicable tests.

@cesarbs I think #1230 was the more important post-1.0 fix to he flakiness in ListenerPrimaryTests.
Are you sure #1769 fixed any flakiness? I'm suspect it might not have considering @natemcmaster said he couldn't reproduce the issue even in a tight loop prior to the changes.
As far as I can tell, the only way #1769 could have possibly helped is by effectively increasing the timeout for the secondary listener to connect from 10 seconds (that used by #1769) to 30 seconds (the maxWait in #1769). My reasoning for this based on the premise that AssertResponseEventually can't possibly complete until after the UvPipeHandle is added to _dispatchPipes.
I would just backport #1230 and increase the default maxRetries to 300 to get the increased 30 second timeout. I would also change maxRetries to 300 in the dev branch and revert #1769 unless someone can explain how #1769 helps reduce flakiness given AssertResponseEventually.

Updated with backport of #1230. @Eilon This doesn't involve any product code change and stabilizes tests.

Updated with 30 second timeouts.


Cannot drop diagram onto Camunda Modeler anymore

Describe the bug
When I try to drop a diagram onto the modeler then path as a property is no longer provided. This means that our drop logic blows up with the following error:
Cannot read properties of undefined (reading 'split')
    at getFileTypeFromExtension (webpack://camunda-modeler-client/src/app/App.js:2344:0)
    at readFileFromPath (webpack://camunda-modeler-client/src/app/App.js:726:0)
    at Array.map (<anonymous>)
    at App.readFileList (webpack://camunda-modeler-client/src/app/App.js:709:0)
    at Object.handleDrop (webpack://camunda-modeler-client/src/app/App.js:1974:0)
    at handleDrop (webpack://camunda-modeler-client/src/app/drop-zone/DropZone.js:78:0)

Steps to reproduce

Open Modeler
Drop file from local file-system
See error pop up

Expected behavior
I can drop (and open) files from the local file system.
Environment

OS: Linux (Ubuntu)
Camunda Modeler Version: v5.26.0
Execution Platform: Any
Installed plug-ins: None

Works in Camunda Modeler v5.25.0.
Additional context
Capture visualizing the issue:

I can reproduce it on nightly (MacOS, dropping a file from the Desktop)

file.path is not attached:

Now it's time to read the Electron breaking changes :D

Yes, it is an Electron BC:

Removed: File.path
The nonstandard path property of the Web File object was added in an early version of Electron as a convenience method for working with native files when doing everything in the renderer was more common. However, it represents a deviation from the standard and poses a minor security risk as well, so beginning in Electron 32.0 it has been removed in favor of the webUtils.getPathForFile method.

https://www.electronjs.org/docs/latest/breaking-changes#removed-filepath

I played with this a bit, and it requires us to modify the preload script. This will then introduce a requirement on the file drop handler (dropzone) to also connect to the preload script.
tldr: I suggest we downgrade Electron for now, and resolve the issue for the next release under assumption that the "broken dropdown issue" is not breaking due to downgrade.

I am checking v31.4.0 right now.

Result: https://github.com/camunda/camunda-modeler/pull/4485

When we upgrade to v32, we need to adjust to the breaking change.

Fortunately, in the app we don't usually deal with web File objects, so that should ease the migration. We can still carry file.path around as a plain javascript object property like we do in Tabs.


Display the HResult as well as Message for TrackErrrors

Describe the solution you'd like
In the track errors tab the Exception Message is shown, but it would be useful for the HResult value to be shown too.
Describe alternatives you've considered
I currently have to add a dictionary item for every call to trackerror
Additional context
Some handled exception reports could be managed better by checking in code. At the moment I would have to do a string compare on the message which seems like a bad way to implement checking. int compare would be better and so showing me the int value would help

Thanks for the feature request! We don't have immediate plans to address this but we'll incroporate this feedback into our planning and post here with any updates.
I understand attaching custom properties to your errors might not be an ideal solution but that's the best suggestion I have at the moment. Thanks!


Upgrade Linux Kernel for flatcar-3602 from 5.15.120 to 5.15.121

Subject says it all.

See instead https://github.com/flatcar/scripts/pull/1008


Support Cookbook Uploads

As a user, I would like to be able to upload cookbooks using the go-chef/chef library.
Ruby Chef Cookbook Uploader: https://github.com/chef/chef/blob/main/lib/chef/cookbook_uploader.rb
General Process:

Parse local cookbook, generating checksums for all cookbook files.
Create a sandbox with the generated checksums to determine which files will need to be uploaded.

Use chef.Sandbox Post

Upload each cookbook file into the sandbox that has needs_upload set to true in the chef.Sandbox Post JSON response by performing a PUT to the provided sandbox item url.
Commit the sandbox.

Use chef.Sandbox Put

Upload the cookbook version manifest.

I am currently taking a look at implementing this and submitting a PR.

Cool.  Just to note I've never been able to get the sandbox api client to work at all.

Cool. Just to note I've never been able to get the sandbox api client to work at all.

I haven't had any trouble with it so far, but it may be due to different Chef Server versions. Were you seeing issues against Chef Server, CINC Server, or Goiardi?

I usually test against the current chef server.  The test suite for this project has a cookbook that spins up a chef server  I run the integration tests against and where I do development.  Good to hear you have it working.


RC Test: Geometric Optics 1.3.0-rc.1

RC Test
Mentions: @arouinfar @kathy-phet @KatieWoe
Simulation links

github repository for issues
phet top-level directory
sim: all_phet.html
phet-io wrapper index
link to phet-io zip file

Test Matrices

General Test Matrix
PhET-iO Test Matrix

Features included

[x] PhET-iO
[x] Alternative Input
[x] UI Sound

- [ ] Sonification
- [ ] Description
- [ ] Voicing

Focus and Special Instructions
This RC test should be done with https://github.com/phetsims/qa/issues/945 (RC Test: Geometric Optics: Basics 1.3.0-rc.1).
Issues to Verify
None.

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Test the Game Up harness on at least one platform.
Check this LoL
spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.
As the RC ends, please review the QA credits in the about dialog.  If the QA credits are complete and correct, please add a comment in the RC test issue indicating so.  If not, please open a new issue and specify what changes should be made.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
random platform.
Conduct a memory test on the stand alone sim wrapper (rc.1).
Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
Test that the sim works offline:

Click the link to the phet-io zip file (at top of issue) to download the zip file.
Unzip it to a spot locally.
Open index.html by double clicking it on your desktop or in a Finder-view.
It should look like the standalone version of the sim in PhET-iO brand.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

In Slack#dev-public, @jessegreenberg said:

I am starting a batch maintenance release for basically all sims that support alt input (will put list in thread). Please coordinate with me if you need to do maintenance work on release branches. Tracking in https://github.com/phetsims/tasks/issues/1123.

This affects geometric-optics, will patch the 1.3 branch, and will generate 1.3.0-rc.2.  So rather than start testing on 1.3.0-rc.2, please pause this test.  I'll self-assign this issue, fix up the links after 1.3.0-rc.2 is published, and let you know when to resume.

A new RC (1.3.0-rc.2) was published by @jessegreenberg, and testing will resume in https://github.com/phetsims/qa/issues/947.  Closing.


failed to inject span: opentracing: Invalid Inject/Extract carrier

ERROR: failed to inject span: opentracing: Invalid Inject/Extract carrier
when i use the Latest release version of zipkin-opentracing-go, some exception appears.It seems like the new version don't support "TextMapCarrier map[string]string"
func (p *textMapPropagator) Extract(
	opaqueCarrier interface{},
) (opentracing.SpanContext, error) {
	if extractor, ok := opaqueCarrier.(propagation.Extractor); ok {
		sc, err := extractor()
		if sc != nil {
			return SpanContext(*sc), err
		}
		return SpanContext{}, err
	}
	if httpCarrier, ok := opaqueCarrier.(opentracing.HTTPHeadersCarrier); ok {
		req := &http.Request{Header: http.Header(httpCarrier)}
		sc, err := b3.ExtractHTTP(req)()
		if sc != nil {
			return SpanContext(*sc), err
		}
		return SpanContext{}, err
	}
	return nil, opentracing.ErrUnsupportedFormat
}

I believe this line:
if httpCarrier, ok := opaqueCarrier.(opentracing.HTTPHeadersCarrier); ok {

should be
if textMapCarrier, ok := opaqueCarrier.(opentracing.TextMapCarrier); ok {

Any thoughts @basvanbeek ?

Nope... I think there is a good use case for having a map carrier for zipkin go which we could make TextMapCarrier compatible for this bridge

Not sure I am following. Correct me if I am wrong, is it that here the issue is that the so called TextMapCarrier is expecting a ot.HTTPHeaders instead of it.TextMapCarrier?

I am having the same issue here, 142

@ONG-YA can you check if the latest in master fixes your issue?

Closing this issue as TextMapCarrier is not only implemented now but also has a unit test. @ONG-YA please re-open if we missed something.

@ONG-YA can you check if the latest in master fixes your issue?

Solved！thanks guys.


Return meaningful errors on worng syntax

If the json is incorrectly typed and run through jsondbc it returns no meaningful error on where the syntax is wrong. I need to pre parse the json with jq to understand where the missing comma is.

Moreover with an incorrect json structure at the definition level (incorrectly written json) the application just ends with return code 146. Need more debug info. Try this json https://termbin.com/ejvl

It uses the default go/json parser and if you try parse a wrong json file, it returns an error. I've added the validation level for all the fields marked as "required" in the doc (remember: a required INT field which can be of value 0 can be omitted)

The returned information is a lot better but still the line number where the syntax is incorrect is not displayed. Is this fixable?

I found a work-around to get the line num of a json syntax and type errors. For the errors regarding the validation of the CAN models it's not possible to reference the line. If the convertion is dbc->json, the line is shown


Consider replacing deb with Snap or AppImage or similar

I feel deb packaging in maven is a dead road. There are practically no good examples and documentation is superbad.

both suck. Need to think about this.


When NANO is selected, the derivation path is hard-coded and the tool's BIP39/BIP44 derivation path is ignored

When NANO is selected, the derivation path is hard-coded to m/44'/165'/n' for account #n, and the tool's BIP39/BIP44 derivation path is silently ignored.
This means that the Ian Coleman BIP39 tool cannot be used to get NANO addresses and private keys from arbitrary user-defined derivation path.
Any user-specified derivation path is silently ignored and NANO addresses purportedly derived from that path are in fact derived from the hard-coded path m/44'/165'/n' .
This bug was acknowledged by https://www.reddit.com/user/Joohansson/ , the author of the NANO code in the tool. See discussion in this thread: https://www.reddit.com/r/nanocurrency/comments/mo4ga7/nano_mnemonic_vs_bip39/gv2p9k7/?utm_source=reddit&utm_medium=web2x&context=3
Note: NANO Team does not advise BIP39-compliant wallets to use a BIP44 derivation path, but rather the 3-elements BIP32 derivation path m/44'/165'/n', specified here: https://docs.nano.org/integration-guides/key-management/?h=bip#mnemonic-seed . Also note that the NANO addresses displayed under the BIP44 tab are not derived from this BIP44 path, because of this bug.

There are some bip44 derivations (eth on ledger, coinomi) that differ from bip44 despite having purpose set to 44, see https://github.com/iancoleman/bip39/issues/128#issuecomment-351655304
Looks like the best way to manage this is use bip32 tab with a modified / non-compliant / non-standard bip44 style derivation path. Pretty confusing from coins and tools that use bip44 but don't comply to bip44 standard.


ESDoc 0.4.7  issue with dependency

Getting the following when doing require on node_modules/esdoc/out/src/Publisher/publish.js (for using the API).
let logger = new _colorLogger2.default('IceCap');
^^^
SyntaxError: Unexpected strict mode reserved word
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/tmp/esdoctest/node_modules/esdoc/out/src/Publisher/publish.js:20:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

Getting same error when trying to run esdoc -h.
usr/local/lib/node_modules/esdoc/node_modules/ice-cap/out/src/IceCap.js:18
let logger = new _colorLogger2.default('IceCap');
^^^
SyntaxError: Unexpected strict mode reserved word
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/usr/local/lib/node_modules/esdoc/out/src/Publisher/publish.js:20:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)

It looks like ESDoc 0.4.7 requires at least node version 4 because of the IceCap dependency. IceCap is using some es6 feature that are not included in node 0.12.
Is that by purpose ?

Yes, IceCap requires Node v4 or greater.  Please upgrade your Node version.

Ok, I filed two bugs with Ice-Cap/Color-Logger.  The problem appears to be that Color-Logger was updated to use Babel/ES6 syntax (cool) but one itty bitty capability was removed.... you can not instantiate Logger with a "tag" (logger name).  It used to be there in older versions and it was removed with the latest.  Even though you may refer to 0.0.3 version, they are not using releases in github.  Since it would appear the "package" in the source package and there is no official version in github (gulp at least) appears to be compiling latest which does not refer to the contructor anymore.   On the esDoc side the fix is simply let logger = Logger; or whatever you imported from color-logger.

Please check latest ESDoc with Node.js v6


Can't override colorcheme colors in vimrc

First, thank you for lightline is awesome!
My problem is:
I'm using the powerline colorscheme, by default it looks like:

but I want it to look like this:

what I have done to accomplish this, is override the colors in the powerline.vim colorscheme, but that is not optimal, so I decided to instead of doing that just override the colors in my vimrc with the following:
vimrc
let g:lightline = {
      \ 'colorscheme': 'powerline',
      ...

let s:cuicolor = {
            \ 'darkestgreen'   : 22,
            \ 'brightgreen'    : 148,
            \ 'gray0'          : 233,
            \ 'gray1'          : 235,
            \ 'gray2'          : 236,
            \ 'gray3'          : 239,
            \ 'gray4'          : 240,
            \ 'gray5'          : 241,
            \ 'gray6'          : 244,
            \ 'gray7'          : 245,
            \ 'gray8'          : 247,
            \ 'gray9'          : 250,
            \ 'gray10'         : 252,
            \}

let s:palette = g:lightline#colorscheme#{g:lightline.colorscheme}#palette
let s:palette.normal.left = [ [s:cuicolor.darkestgreen, s:cuicolor.brightgreen, 'bold'], [s:cuicolor.gray4, s:cuicolor.gray1] ]

but this isn't working.
I'm getting the following error when I open vim with this configuration:

The palette colours is:
let s:palette.{mode}.{where} = [ [ {guifg}, {guibg}, {cuifg}, {cuibg} ], ... ]

So  you can configure as:
let s:palette.normal.left = [ ['#005f00', '#afdf00', s:cuicolor.darkestgreen, s:cuicolor.brightgreen], ['#585858', '#121212', s:cuicolor.gray4, s:cuicolor.gray1] ]

That works, thank you!


fix compile warning

https://stackoverflow.com/questions/18039275/retained-block-property-does-not-copy-the-block-use-copy-attribute-instead
"Retain'ed block property does not copy the block - use copy attribute instead"
Not sure if this should be copy or strong.

I updated my flutter install and this issue went away... probably due to switching from old build project to new build project in xcode.

reopened per #60

Thanks @lookfirst


Notebook tests in Cypress

Trying JHub Client within Cypress, e.g. to test Dask Gateway

Testing on https://github.com/danlester/cypressjhubtest/actions/workflows/test.yaml


chore: filter vulnerability status by the analysis type

The 'gcloud container images describe' command returns two entries for the discovery_summary field. We only need the status from 'projects/goog-analysis/notes/PACKAGE_VULNERABILITY'.
Example output:
{
  "discovery_summary": {
    "discovery": [
      {
        "createTime": "2024-05-27T01:18:40.728858Z",
        "discovery": {
          "analysisStatus": "FINISHED_SUCCESS",
          "continuousAnalysis": "ACTIVE"
        },
        "kind": "DISCOVERY",
        "name": "projects/config-management-release/occurrences/400738d4-d91e-46cc-abae-8bfb265a8f2e",
        "noteName": "projects/goog-analysis/notes/COMPLIANCE",
        "resourceUri": "https://gcr.io/config-management-release/otelcontribcol@sha256:2f93890991d10870bf0a04586522db3ced65a152ca3f0f30aa9961f82d72aea7",
        "updateTime": "2024-05-27T08:58:38.638961Z"
      },
      {
        "createTime": "2024-05-27T01:18:40.873202Z",
        "discovery": {
          "analysisStatus": "FINISHED_SUCCESS",
          "continuousAnalysis": "ACTIVE",
          "lastScanTime": "2024-05-28T15:17:14.544092857Z"
        },
        "kind": "DISCOVERY",
        "name": "projects/config-management-release/occurrences/7272fdba-beee-4812-9c96-2bf7cae7732e",
        "noteName": "projects/goog-analysis/notes/PACKAGE_VULNERABILITY",
        "resourceUri": "https://gcr.io/config-management-release/otelcontribcol@sha256:2f93890991d10870bf0a04586522db3ced65a152ca3f0f30aa9961f82d72aea7",
        "updateTime": "2024-05-28T15:17:14.613273Z"
      }
    ]
  },
  "image_summary": {
    "digest": "sha256:2f93890991d10870bf0a04586522db3ced65a152ca3f0f30aa9961f82d72aea7",
    "fully_qualified_digest": "gcr.io/config-management-release/otelcontribcol@sha256:2f93890991d10870bf0a04586522db3ced65a152ca3f0f30aa9961f82d72aea7",
    "registry": "gcr.io",
    "repository": "config-management-release/otelcontribcol"
  },
  "package_vulnerability_summary": {
    "not_fixed_vulnerability_count": 0,
    "total_vulnerability_found": 0,
    "vulnerabilities": {}
  }
}

b/342954704

/retest


Get "Unhandled exception. ROS2.RuntimeError: publisher's context is invalid, at ./src/rcl/publisher.c:389" when I run example more than 20+ minutes.

OS: Ubuntu22.04
ROS2 Humble
.NET 6.0
Hi,
I have modified example "ROSTalker" and "ROSListener" files to implement these two nodes can send and receive data at the same time. Details as below:

After build and launch, everything goes well. But 20mintues later, I get an exception as below:

Please Help. Thanks.

Can reproduce this issue on Ubuntu with Ros2 Humble and the talker example, removing the Sleep call speeds the whole process up.

Can reproduce this issue on Ubuntu with Ros2 Humble and the talker example, removing the Sleep call speeds the whole process up.
I think it is somehow caused by the garbage collector since removing all calls to Shutdown does not fix this issue while calling GC.TryStartNoGCRegion (or GC.GetGCMemoryInfo, I dont know why) seem to prevent it.
Furthermore, the issue does not occur using the changes in #47, which allocate the structs in native memory.

Hi Deric,
According to your suggestion, I revert my changes on listener and talker example. After launching program, it's running smoothly for over 5 hours. It seems that my changes caused the issue, and I don't know why...
Thanks for your responding!
Nick

Hi,
I was able to reproduce the error with the normal talker example included in this repository, which means the error is still present but it seems it is triggered erratically.
I try to find out what exactly is causing it.

@Nickiven was this issue resolved for you?


mesact/buildini.py [HAL] missing io.hal

https://github.com/jethornton/mesact/releases/tag/1.2.3
When a new project is created and a the .ini file is generated, the inclusion of the io.hal under the [HAL] section is missing.
Expection:
[HAL]
HALFILE = <project>.hal
HALFILE = io.hal
HALFILE = custom.hal

To reproduce create new project and check .ini
OS =  Debian 10

https://github.com/jethornton/mesact/blob/9b05831083ab56203294c4be5f001788cc49e597/mesact/src/libmesact/buildini.py#L134

Fixed


Muting local camera/microphone does not stop sending media via MediaTrack

When user using Videoroom decides to mute microphone/camera he is still sending media to the server, therefore generating traffic and SFU load.

Setting MediaStreamTrack.enabled to false will cause sending blackness for video tracks and silence for audio tracks so indeed our server will be still receiving data.
I think we are doing it properly as in docs there is This can be used to intentionally mute a track. and in other place Note: You can implement standard "mute" functionality by setting enabled to false. The muted property refers to a condition in which there's no media because of a technical issue.
https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/enabled

Yup, this is a problem as the blackness will still be sent with the same framerate as the video (in our case it is 30 fps, should be lowered by the way).
Replacing video track with fake canvas track should do the job as it does not send any packets whatsoever.


Query and return the index of the doc in a data set

Hi, I'm trying to figure out if it is possible to run a query for a particular key-value-pair with a customized sort setting and then in the returned doc it will returns the index of the doc in the database along with the doc. Do you think it is doable? Thanks.
For example:
I have a database that has 10 docs, and I am looking up the one with name=john, with sorting on address. I wish Cloudant can return me the doc that has name=john while also letting me know its index in this data set with sorting applied is 5.

'while also letting me know its index in this data set with sorting applied is 5.' - for a sec u had me wondering if that 'sort' referred to the sort on address, but that can't be the case since one can decipher that from the result.
I am a little curious what the higher level use-case is that u are going after.

If I understand the question correctly, you have 10 docs. You have a map function which indexes the name field of these docs. If you were to return all 10 results of this index by name you would see (for example):

Andrew
Ashley
Bessie
Everett
John
Karl
Lee
Lora
Louise
Ollie

You want to run a query for all documents having the name field with a value of "John". However, you don't just want the results, you want to know where in the above list the results are. Meaning, you want to know that "John" is at position 5. Is this correct?

Thanks, @bradley-holt yes, that's correct. To make it a little complicated than your excellent example  - besides the index and name columns, there is a third column named "zip code". The use case is to sort on "zip code" and then find the row with name="John" and the index of this row.
@mariobriggs, the high level use case is the application wants to first find a particular record (e.g., row with name="John" in @bradley-holt 's example) and then use the row's index to apply pagination. Thanks!

Let's assume you have a dataset with the following columns: name, zipcode.  You would like this dataset to be sorted by zipcode, so you've probably created an index using Cloudant Query like so:
curl -X POST -d '{
    "index": {
        "fields": [
            {"zipcode": "asc"},
            {"name": "asc"}

        ]
    },
    "name": "zipcode-name",
    "ddoc": "zipcode-name"
}' https://account.cloudant.com/db/_index

Cloudant Query has defined a design doc for you named "_design/zipcode-name" which essentially contains a MapReduce view:
{
  "_id": "_design/zipcode-name",
  "_rev": "1-9b5c5a6b2d1f986f53766e75e61e0de5",
  "language": "query",
  "views": {
    "zipcode-name": {
      "map": {
        "fields": {
          "zipcode": "asc",
          "name": "asc"
        }
      },
      "reduce": "_count",
      "options": {
        "def": {
          "fields": [
            {
              "zipcode": "asc"
            },
            {
              "name": "asc"
            }
          ]
        },
        "w": 2
      }
    }
  }
}

So now you can query it using /db/_find endpoint, but you can also use it via /db/_design/zipcode-name/_view/zipcode-name endpoint directly:
curl -X GET https://account.cloudant.com/db/_design/zipcode-name/_view/zipcode-name?reduce=true&endkey=["John", "20066"]

Two things to notice here:

reduce={true,false}  can trigger aggregations defined on the view. In our case that's _count.
we can also specify the startkey and endkey.  The key is determined by the fields array attribute that was used to create our zipcode-name. In this case, the key is an array of [name, zipcode].

So all you have left is determine what your endkey needs to be and with reduce=true, you'll get a number of records up to and including that endkey.
You already know the name because that is what you are searching by.  You need to figure out what the corresponding zipcode is for the first occurence of say "John" in the in the index. To do that you can define another index but flip the order of columns like so:
curl -X POST -d '{
    "index": {
        "fields": [
            {"name": "asc"},
            {"zipcode": "asc"}

        ]
    },
    "name": "name-zipcode",
    "ddoc": "name-zipcode"
}' https://account.cloudant.com/db/_index

So to figure out your endkey given that name = "John", you can query this view like so:
curl -X POST -d '{
    "selector": {"name":{"$eq": "John"}},
    "sort": [{"name": "asc"}, {"zipcode": "asc"}],
    "limit": 1
}' https://account.cloudant.com/db/_find

Once you construct the endkey, you can query against the first view using /db/_design/zipcode-name/_view/zipcode-name with reduce=true and the endkey you just prepared.

Closing this issue as I don't think any changes are required from this.


Integrate mode switch for automated tests

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PO-118
https://tools.hmcts.net/jira/browse/PO-120
https://tools.hmcts.net/jira/browse/PO-129
https://tools.hmcts.net/jira/browse/PO-131
Change description
adding the ability to test both legacy and opal routes
adding tests for the above tickets
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Current failure valid, waiting on fix for PO-120

@sabahirfan the legacy-db stub doesn't look to be running in the dev pipelines, so all the legacy tests are failing


Fix duplicated entries in successes

https://issues.redhat.com/browse/HACBS-2268

I'm getting 20 successes with this patch. If I use ec-cli from before the issue was introduced, I get 18. The two additional ones are cve.cve_results_found and provenance_materials.git_clone_source_matches_provenance.
I'm digging into what is actually expected here. Was there a bug that got fixed to explain this?

Merging this. the failed RHTAP CI seems unrelated. Trying to address it here: https://github.com/enterprise-contract/ec-cli/pull/731


auto renew-subscription

When I purchase a non-consumable product (Subscription) with tester account, everythings work perfectly. After purchase I can get “order ID, status, etc… But when monthly subscription renews after 5 minutes (or yearly subscription after 30 minutes as a tester), I don’t get old or renew purchase information, so I get the result as not purchased. How to get subscription information, when it renews?

Hi @user723. This library returns a list of available products. When you purchase an already subscribed product, Google will throw an error stating that the product is already purchased. If you want to know the status of your product, you can have that feature configured at server-side using Google's APIs.
https://docs.huihoo.com/android/4.4/google/play/billing/gp-purchase-status-api.html
If this is not what you are looking for, please elaborate your issue along with library output and logs if available,

When I purchase first subscription product, I can get the status of subscription product until the subscription renews automatically. After renew subscription, I don't get any product status anymore.

You shouldn't rely on billing API delegates to manage the current state of purchased products. This issue can also be observed in Android's in-app demo. Server-side in-app integration will help you along with other features like cancelation notification and much more.
Closing the issue as it is Google billing API issue.