I'm not receiving log when I run the built rat [PLEASE HELP]

I ran the built rat myself for test and I didn't receive anything on my webhook (Discord server)...
Please help.

i need the error??

How to see? It just built the file and when i ran it i didnt get anything

send me a ss of the file and post your hook here

i will also need both log files (roselog.log, rosecompile.log)

alright here
roselog.log
rosecompile.log

and what do you mean hook?

your webhook? if you didnt enable the features on the features tab and entered your webhook on the home page, it clearly wont work

and wheres the ss of the sample?

https://discord.com/api/webhooks/1165564744841822218/mPtjYxDkgIVzpOvEQBk7SqSj9TMXIBd_n0QrRoJy03NkUVBYsdgsFeWh5iSJEhDN2JRt

i enabled features too

third time that im telling you i'll need a screenshot of the final exe...

ok

this right?

just record/explain what exactly happens after you run it

alright

have you enabled antivm and your username, ip, hwid or something like that is blacklisted??

antivm

so i run it right now

whats your computer hostname?

my selfie camera flashed

some command prompts pop up and close

thats all and i dont get info

have you enabled the stealer features??

whats your computer hostname?

?

DESKTOP-2JA56DM

this is

have you enabled the stealer features??

?

yes

pretty much everything on the grabber

except "spread malware"

nah i havent

i enabled these

what could affect it?

no white and red msg box pops up

and you antivirus isnt blocking the file?

its off

i dont have any quaranteed threads too

so what could possibly cause this?

anti-vm?

i upload it there?

yeah, create an account, upload, press submit, choose windows as an os and press analyze, then i hope it comes up to your webhook, if not, disable antivm and try to run the stub on your device again, if it still doesnt work, send me a stub without antivm or antidebug on telegram, its linked in our readme

alright let me try

im uploading it, how long does it take?

go to the submit page and upload there

OH

I turned off Anti-VM and now i got log

it also gave me some erorr

ah thanks next update should include a fix

ah thanks next update should include a fix

This should be fixed now, if it doesn't find an SSID or BSSID to a network then it just passes over it.


Image is offset from edge of screen in vertical and horizontal

Hey hey,
I just installed this module and so far it's looking promising (crossfingers). The only issue I have is that for some reason the image is offset on the screen. Both X and Y are offset by lets say 50 pixels or something, so the image isn't sitting flush to one side and the bottom. Is there a setting to fix this?
All the images I'm using are the same pixel size as the screen, I'm not using fixed size, and I have the module on "fullscreen_below".
Any help is appreciated.
Thanks.

Figured it out! Had to tweek the margin in custom css.


Grafting does not respect deterministic failed status

To reproduce:

Have a subgraph fail with a deterministic error at block N.
Graft it at block N.
The grafted subgraph will continue syncing from N + 1, when it should be failed at block N.

The graft feature always starts from the base subgraph at block N + 1. Upon testing the described scenario on graph-node version 0.24.2, I bumped into this error message:
✖ Failed to deploy to Graph node http://<IP_ADDRESS>:8020/: subgraph validation error: [the graft base is invalid: failed to graft onto `QmWt3quQnYFhwypj93Uco7ex3UmtdeRrLAhYY5cbQL2Vn6` at block 11416275 since it has only processed block 11416241]

Which makes sense, because it was only on 0.25.X that graph-node started processing deterministic failures (saving the deployment pointer).
My proposal is to validate at creation time, just like the error above, that subgraphs can't be created at the failed block, because grafts start at N + 1.
If a developer wishes to reproduce the failure in a graft, they should define in their manifest block N - 1 (N being where the base failed). We can give a nice error message in the validation suggested above 🙂
What do you think @leoyvens ?
This is where the failure happens for the curious ones: https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/subgraph/mod.rs#L478


Releases are duplicated on Sentry

Description

When deploying to prod, 2 releases are created in Sentry. It seems there's a mismatch between sentry.config.ts and the Github action
Steps to reproduce

Environment

OS: e.g., Windows, macOS, Linux
Runtime/Browser/Version: e.g., Node 22, Chrome 120
Wallet: e.g., MetaMask, Trust, Coinbase Wallet

Proposed fix

With the change in #636 the Sentry release named after the GitHub release is no longer duplicated. However, there still appears a release named with the commit of the GitHub release, so there is still some investigation to do.

Closed by #665 - Releases are no longer duplicated when deploying to prod


Broken images in documentation

Some images are not showing as expected on the main documentation

In some images the extension is in uppercase throwin a 404 on the github


Error in placement hints: Regex and barrel annotations

I am not sure about the rest of the pipeline but the regex inside atlas-placement-hints  does not work well with barrel annotations:
https://github.com/BlueBrain/atlas-placement-hints/blob/d4a57b7d390c14d5f65f3f17ccfab6963f39add8/atlas_placement_hints/layered_atlas.py#L81C[…]81C81
This kind of regex will struggle with the annotations pattern:
SSp-bfd:
    SSp-bfd-C1
        SSp-bfd-C1-1
        SSp-bfd-C1-2
        SSp-bfd-C1-3
...

I attach the comparison of the two [PH]y.nrrd files, with and without barrel annotations.
The first one was downloaded from production, the second one was an outcome of a pipeline run with the modified annotations.

Alexis used the following code that made us spot the issue:
from neurocollage import get_layer_annotation
from voxcell.nexus.voxelbrain import Atlas
from region_grower.atlas_helper import AtlasHelper

atlas_path = "/gpfs/bbp.cscs.ch/project/proj100/atlas/mouse/atlas-mouse-barrels"
circuit_path = "/gpfs/bbp.cscs.ch/data/scratch/proj100/mouse-circuits/ssp-bfd/alexis/auxiliary/circuit.somata.h5"
atlas = AtlasHelper(Atlas.open(atlas_path), region_structure_path="region_structure.yaml")

# get layer anotation into an nrrd file to be loaded by itk-snap
layers = get_layer_annotation(
    {"atlas": atlas_path, "structure": "region_structure.yaml"}, "Isocortex"
)
layers["annotation"].save_nrrd("layers.nrrd")

withregion_structure.yaml:
  layers:
  - 1
  - 2
  - 3
  - 4
  - 5
  - 6
  names:
    1: layer 1
    2: layer 2
    3: layer 3
    4: layer 4
    5: layer 5
    6: layer 6
  region_queries:
    1<EMAIL_ADDRESS>    2: '@.*2[a|b]?$'
    3<EMAIL_ADDRESS>    4<EMAIL_ADDRESS>    5<EMAIL_ADDRESS>    6: '@.*6[a|b]?$'
  thicknesses:
    1: 69
    2: 135
    3: 100
    4: 208
    5: 248
    6: 451

path for the two[PH]y.nrrdfiles :

with artifacts
/gpfs/bbp.cscs.ch/project/proj100/atlas/mouse/atlas-release-barrels-may2023/placement_hints_ccfv3_l23split_barrel/[PH]y.nrrd

without
/gpfs/bbp.cscs.ch/project/proj148/scratch/test_circuit/.atlas/[PH]y.nrrd

Here are more plots:
PHy with proper values, we see the barrel, but we should not:

PHlayer_1 (bottom value, aka [:, :, :, 0]), we also see the barrels:

and if I zoom out the same PHlayer_1, I'm not convinced it is so 'good', we see a red spot top right, and not a uniform increase in top left pprojection

I hope this helps improving the qualities of PH files!

Also the cell_densities files are wrong:

Also orientations fields:

I am not sure about the rest of the pipeline but the regex inside atlas-placement-hints does not work >
This kind of regex will struggle with the annotations pattern:
SSp-bfd:
    SSp-bfd-C1
        SSp-bfd-C1-1
        SSp-bfd-C1-2
        SSp-bfd-C1-3
...

Which part is of the regex is suspicious? AFAIK, the part highlighted won't matter ([ab]?$) as ab are optional.  I'm more concerned by the 1 at the end of the region name: SSp-bfd-C1; since this "looks" like
it belongs to layer one.
I think it would be useful to work with @lecriste to isolate the step within the pipeline where the results start to differ, so it can be narrowed down to this regex, or potentially something else.
The use of regular expressions in these atlases has always been fraught (ie: [and] Now You Have Two Problems), but I'm not sure when/if we'll be able to tackle that, so, in the meantime, tracking down to make sure that this is the problem would be helpful.

@lecriste here is a PHy of another atlas I was working on this morning (which we use for striatum). I'm not sure which one is 'correct' isocortex, I quickly loose track of the latest atlas folder on gpfs.

in any case, these PH are distances to smooth boundaries (or meshes), hence they should be smooth inside the atlas as well.
@mgeplf probably reruning the pipeline with a regex that does not confuses the entire barrel columns with layers would work. I'm not good enough with regex to know how to update it, but aleksandra had a try before she left and said it should be possible.

The only input (other than hierarchy and annotation volume) to calculate placement hints is direction-vectors. If the direction-vectors volume looks fine, than the different regex can be tested with the command The only input (other than hierarchy and annotation volume) to calculate placement hints is direction-vectors. If the direction-vectors volume looks fine, than the different regex can be tested with the command
atlas-placement-hints isocortex  --hierarchy-path <hierarchy-path>  --annotation-path <annotation-path>  --direction-vectors-path <direction_vectors_path> --algorithm voxel-based
where <hierarchy-path> and <annotation-path> are the hierarchy and annotation volume linked to the Staging atlas release.:
atlas-placement-hints isocortex  --hierarchy-path <hierarchy-path>  --annotation-path <annotation-path>  --direction-vectors-path <direction_vectors_path> --algorithm voxel-based
where <hierarchy-path> and <annotation-path> are the hierarchy and annotation volume linked to the current atlas release in Nexus Staging.

hi, yes @mgeplf the problem is, as you worried, the numbered names and numbered layers. The 1 at the end of the barrel is assumed to be layer 1, etc. and then the whole barrel becomes part of a layer.
I think the issue is propagated in the pipeline that's in staging, as the files from there seem to all have corrupted inputs as shown by Alexis.
@lecriste can we re-run the things with new regex and I can examine if the files are all in check?

Which new regex?
I would need a PR in this repo to fetch and re-run the pipeline.

I test-run, the two sections of the atlas pipeline, which are directly changed by the PR.
The missing part is a full re-run of the pipeline and inspection of the complete atlas files.

The missing part is a full re-run of the pipeline and inspection of the complete atlas files.

Can you help with that @lecriste? I'd like to get this PR closed, if possible.

Yes but not before February.

Fixed by https://github.com/BlueBrain/atlas-placement-hints/pull/14


[Bug] [Worker/Master]  Data duplication caused by worker faking death

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

Because of cpu load is too high, worker lost connection with Zookeeper.
Master failover the worker and restart the tasks, but cannot kill the tasks.
Then the same  task would be run twice and result data would be duplicate.

What you expected to happen

Worker should check resource before submitting task to execution thread.
Can worker actively reduce CPU load through killing task ?

How to reproduce

CPU load  is too high:

worker lost connection with zk:

Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

hi i also have the similar problem

What's the task type? Is it a yarn manage task?

Submit the yarn task through the shell. When the workload of the worker is relatively high, the shell task that has been started has not been submitted to the yarn cluster. The master has fault tolerance. When killing the yarn task, the appid is not found. The master schedules the task to other workers. When the workload of the worker is lower, the shell submits the task to yarn. At this time, the yarn cluster has two identical tasks, Data duplication will occur


Fix topic chip navigation from ForYou screen

[work in progress]
What I have done and why
I have converted the ForYou navigation graph from a single destination containing only ForYouScreen, to a navigation graph with 2 destinations: ForYouScreen and TopicScreen. Tapping on a topic chip inside the ForYou screen will now navigate to the Topic screen inside the ForYou navigation graph (previously tapping would do nothing).
The ForYou feature remains independent of the Topic feature by providing an API for:

a navigation lambda when a topic chip is tapped
a destination for the topic content

fun NavGraphBuilder.forYouSection(
    onTopicClick: (String) -> Unit,
    topicContent: NavGraphBuilder.() -> Unit
){
    navigation<ForYouBaseRoute>(...) {
        composable<ForYouRoute> { ... }
        topicContent()
    }
}

Fixes: #1463 #1614 #1597 #920

Test is failing on CI. This is likely because the API 26 emulator window height isn't sufficiently large to allow the topic tag to be visible even after scrolling down to the news resource card. Example:

What about using a performScrollTo?

@Jaehwa-Noh Unfortunately that doesn't work because of https://issuetracker.google.com/234597156


add argocd client and repository resource

Signed-off-by: Jan Willies<EMAIL_ADDRESS>This PR adds initial support for ArgoCD repositories:

<EMAIL_ADDRESS>https://argo-cd.readthedocs.io/en/stable/user-guide/private-repositories/

Fixes https://github.com/crossplane-contrib/provider-argocd/issues/1. Tests are still missing.
ArgoCD does not allow to connect via user/pass, instead we have to create a jwt at the ArgoCD API and use that. This is currently a manual step described here and needs to be repeated every couple of days. We should be able to automate that.

thanks @hasheddan! I'll open tickets for the missing parts once this is in 👍


Critical MongoId error due to null in arrays

SPT Version
3.10
Project Type
Modules
Expected Result
Call to GetUserItemPrice should return successfully for all traders.
Actual Result
Call to GetUserItemPrice throws a "Critical MongoId error" for traders Lightkeeper (638f541a29ffd1183d187f57) and BTR Driver (656f0f98d80a697f855d34b1).
Steps To Reproduce
Call GetUserItemPrice or CanBuyItem on an Item from an instance of TraderClass for the above trader IDs (explicitly or by looping over ClientAppUtils.GetMainApp().GetClientBackEndSession().Traders).
This issue is filed under Server because it's caused by null values in the database that cause the client to fail.
The client now strictly uses MongoIds and null is not a valid MongoId.
The offending lines are:
https://github.com/sp-tarkov/server/blob/ad41c249b8a2cf008bd4794de39c035fd6b91f52/project/assets/database/traders/638f541a29ffd1183d187f57/base.json#L27-L30
https://github.com/sp-tarkov/server/blob/ad41c249b8a2cf008bd4794de39c035fd6b91f52/project/assets/database/traders/656f0f98d80a697f855d34b1/base.json#L27-L30
Both of these "category" arrays should have been simply empty.
Server Log
Irrelevant.
BepinEx Log
Irrelevant.
Client Log
ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: Critical MongoId error: incorrect length. Id:
  at EFT.MongoID..ctor (System.String id) [0x00020] in <be9862b1593e41e48ad89bd48723d349>:0
  at EFT.MongoID.op_Implicit (System.String id) [0x00000] in <be9862b1593e41e48ad89bd48723d349>:0
  at EFT.InventoryLogic.ItemTemplate.IsChildOf (System.String parentTemplateId) [0x0000f] in <be9862b1593e41e48ad89bd48723d349>:0
  at BackendConfigSettingsClass+TraderSettings+HandbookEntities.Contains (EFT.InventoryLogic.ItemTemplate itemTemplate) [0x0003b] in <be9862b1593e41e48ad89bd48723d349>:0
  at EFT.Profile+TraderInfo.CanBuyItem (EFT.InventoryLogic.ItemTemplate itemTemplate) [0x0000b] in <be9862b1593e41e48ad89bd48723d349>:0
  at EFT.Profile+TraderInfo.method_2 (EFT.InventoryLogic.Item subItem) [0x00007] in <be9862b1593e41e48ad89bd48723d349>:0
  at System.Linq.Enumerable.All[TSource] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] predicate) [0x0002c] in <351e49e2a5bf4fd6beabb458ce2255f3>:0
  at EFT.Profile+TraderInfo.CanBuyItem (EFT.InventoryLogic.Item item) [0x0002a] in <be9862b1593e41e48ad89bd48723d349>:0
  at TraderClass.GetUserItemPrice (EFT.InventoryLogic.Item item) [0x00022] in <be9862b1593e41e48ad89bd48723d349>:0

Player Profile
No response
Screenshots
No response

The referenced data is directly from live dumps, I'm assuming BSG doesn't expect that method to be called for the BTR or Lightkeeper, since they aren't actual traders?

The referenced data is directly from live dumps, I'm assuming BSG doesn't expect that method to be called for the BTR or Lightkeeper, since they aren't actual traders?

I see. Must be, since there's no access point to those two's trader UI, otherwise EFT would crash as well.
Although, I'm not sure what's the right way to exclude fake traders.

You could probably filter on the availableInRaid field, as only Lightkeeper and the BTR have that set to true (And I'm assuming any future in-raid traders would as well)

You could probably filter on the availableInRaid property, as only Lightkeeper and the BTR have that set to true (And I'm assuming any future in-raid traders would as well)

You're right, that seems to work. I was worried that Arena Manager (6617beeaa9cfa777ca915b7c), which has availableInRaid set to false would also appear, but he doesn't appear in Traders at all, so all good. Thanks dude.


Fix source map tracing for HMR updates

HMR is handled via an eval(newCode), and that eval will inherit the filepath of the currently running file (in our case, the chunk file that contains the runtime code). To properly trace, we need to know both the chunk and the item ids, so we trace via the correct item's source map.
Thankfully, we can use the (underspecified) //# sourceUrl  meta comment to name the file we're currently evaluating. That'll get used as the stack frame's file. We can then encode the chunk path and item id into the filename, and let next's stack tracing code handle the rest.
This also fixes an off-by-one on the column. Source maps are 0-based, but the line/column of a file as displayed in an editor or dev tools are 1-based.

Snapshots need update


Cannot open a file chooser dialog from a 386 binary on 64bit Windows

I'm trying to create an small application providing a file chooser, and I saw an unexpected error only on 386 binary running on Windows 10 64bit.
An amd64 binary built from the same source running on Windows 10 64bit works as expected.
Should this error be tracked on this project? Or, should I report this to other place?
Thanks,
Steps to reproduce

Prepare a golang development environment. I'm using go1.16.6 linux/amd64 on Ubuntu on WSL1 on Windows 10.

Create testcase.go under a directory, as:
package main

import (
	"github.com/harry1453/go-common-file-dialog/cfd"
	"github.com/harry1453/go-common-file-dialog/cfdutil"
	"log"
)

func main() {
	result, err := cfdutil.ShowOpenFileDialog(cfd.DialogConfig{
		Title: "Title",
		Role:  "TestCaseRole",
		FileFilters: []cfd.FileFilter{
			{
				DisplayName: "File",
				Pattern:     "*.*",
			},
		},
		SelectedFileFilterIndex: 0,
		FileName:                "file",
		DefaultExtension:        ".txt",
	})
	log.Fatal(err)
	log.Fatal(result)
}

Start bash on Ubuntu on WSL1.

Change working directory to the directory testcase.go placed at.

Run gox -os="windows" . to build binaries.

Then two binaries golang-testcase_windows_amd64.exe and golang-testcase_windows_386.exe are built.

Start cmd.exe on Windows.

Run golang-testcase_windows_amd64.exe on the command prompt. A file chooser dialog appears, so close it.

Run golang-testcase_windows_386.exe on the command prompt.

Expected result
A file chooser dialog appears, same as golang-testcase_windows_amd64.exe.
Actual result
No dialog appears and an error:
C:\Users\piro>>C:\Users\piro\golang-testcase_windows_386.exe
Exception 0xc0000005 0x0 0x140d8b64 0x779cef90
PC=0x779cef90

syscall.Syscall(0x75d08a90, 0x2, 0x1222df0, 0x1, 0x11c06290, 0x0, 0x0, 0x0)
        /usr/local/go/src/runtime/syscall_windows.go:330 +0xbb
github.com/harry1453/go-common-file-dialog/cfd.(*iFileDialogVtbl).setFileTypes(0x75cc18b4, 0x1222df0, 0x11c04180, 0x1, 0x1, 0x1, 0x31d44c50)
        /home/piro/go/src/github.com/harry1453/go-common-file-dialog/cfd/vtblCommonFunc.go:51 +0x11e
github.com/harry1453/go-common-file-dialog/cfd.(*iFileOpenDialog).SetFileFilters(0x1222df0, 0x11c04180, 0x1, 0x1, 0x1222df0, 0x11c06201)
        /home/piro/go/src/github.com/harry1453/go-common-file-dialog/cfd/iFileOpenDialog.go:104 +0x41
github.com/harry1453/go-common-file-dialog/cfd.(*DialogConfig).apply(0x11c5deb8, 0x410754, 0x1222df0, 0x0, 0x0)
        /home/piro/go/src/github.com/harry1453/go-common-file-dialog/cfd/DialogConfig.go:99 +0xef
github.com/harry1453/go-common-file-dialog/cfd.NewOpenFileDialog(0x3e659e, 0x5, 0x3e7965, 0xc, 0x0, 0x0, 0x0, 0x0, 0x11c04180, 0x1, ...)
        /home/piro/go/src/github.com/harry1453/go-common-file-dialog/cfd/CommonFileDialog_windows.go:20 +0x76
github.com/harry1453/go-common-file-dialog/cfdutil.ShowOpenFileDialog(0x3e659e, 0x5, 0x3e7965, 0xc, 0x0, 0x0, 0x0, 0x0, 0x11c04180, 0x1, ...)
        /home/piro/go/src/github.com/harry1453/go-common-file-dialog/cfdutil/CFDUtil.go:9 +0x68
main.main()
        /home/piro/testcase.go:16 +0x8e
eax     0x140d8b64
ebx     0x0
ecx     0x1222de4
edx     0x140d8b66
edi     0x140d8b64
esi     0x0
ebp     0x10ff9d8
esp     0x10ff9d4
eip     0x779cef90
eflags  0x10202
cs      0x23
fs      0x53
gs      0x2b

C:\Users\piro>

Environment

host OS: Windows 10 Pro 21H1 (64bit)
guest OS: Ubuntu 18.04.5 LTS (on WSL1)
go: 1.16.6 linux/amd64
go-common-file-dialog revision: 5bfd6087eee4a36d95f3a3fa9d915317bd9e6ae9

Additional info
I've not tested this on 32bit Windows environment yet.

I'm investigating this now, I've found where the crash occurs and will try to resolve this.

@snurbol Thanks for the report. I can replicate this but I have no idea what is causing it. I don't know what would cause it to behave differently on a 32-bit platform. Worst of all, I have replicated my code in C++ and Rust and it works fine.


Shorted urls

Since I started Working on my custom fork of this site I always had to remove the url that points to your website and change it to start with a / , this improves load times and to make my life easier, so I wanted to to merge those changes into the main repo, I have deployed a test site with these changes at https://alexa-rr.github.io/CircuitsV2Resources/ that is the same as yours, I hope you will be able to merge this pull request and going forward not using the base url in the markdown files,
Much Love
Alexa <3

it also improves load times for your website as well,
Also what do you think about making my fork the main site, I would maintain it so you wouldn't have to worry about that

We would not make your fork the main site even if it becomes better (and I hope it does!). However, we are always willing to take in useful changes like this. Thanks a ton!

So I merged this in but the site went down. I think there is an issue with the shortening. Your sample site isn't working for me either. I think you are missing the first part of the path for these.

In other words, I think they need to be like /CircuitsV2Resources/designs/ rather than just /designs/ etc.

hmm that's weird, let me fix that


[GLUTEN-7800][VL] Add config for max reclaim wait time to avoid dead lock when memory arbitration

What changes were proposed in this pull request?
Add config spark.gluten.sql.columnar.backend.velox.reclaimMaxWaitMs to avoid dead lock when memory arbitration has bug, default timeout is 60min.

@zhztheplayer would you help take a look?

@Yohahaha
A bit dramatical that upstream Velox really updated the function name in SharedArbitrator.h...
See https://github.com/facebookincubator/velox/commit/62b0a128702f4092b1680c4387d892d1d6829d20#diff-00e1979427f8bb6a5bda4f62c02e98dfd2cc0bdadb9219772e667946ffe1421dR111
It causes main CI build failure and let's revert this PR


missing query parameter shouldnt return 404

Hi, I've noticed that using QueryParamDecoderMatcher in a HttpService returns a 404 for a missing param. I dont think this is quite right.
I think people expect a 400 bad request saying that the param is required. If I get a 404, I think I've got the path wrong. See also this stackoverflow that suggests using 422
Im not sure if we want to introduce a breaking change to change this, maybe some people like it and are depending on the behaviour. But perhaps we could add a new Matcher similar to ValidatingQueryParamDecoderMatcher to do this. Or even just document the behavour and a alternative.
I'd like to work on this, Im looking for advice and support on what we should do.
Consider these examples
  "gives 404 on missing query param" >> {
    object NameQueryParamMatcher
        extends QueryParamDecoderMatcher[String]("name")

    val service = HttpService[IO] {
      case GET -> Root :? NameQueryParamMatcher(name) =>
        Ok(s"hello $name")
    }

    val getRoot = Request[IO](Method.GET, uri("/"))

    val io = service.orNotFound(getRoot)

    io.unsafeRunSync().status.code must beEqualTo(404) // would be better if it was bad request
  }

  "gives 400 on invalid query param manually parsed" >> {
     // how to achieve desired result by manually parsing the request.
    val service = HttpService[IO] {
      case req @ GET -> Root =>
        req.params.get("name") match {
          case None =>
            BadRequest("missing name")
          case Some(name) =>
            Ok(s"hello $name")
        }
    }

    val responseWithName =
      service.orNotFound(Request[IO](Method.GET, uri("/?name=cat")))
    responseWithName.unsafeRunSync().status.code must beEqualTo(200)

    val responseWithoutName =
      service.orNotFound(Request[IO](Method.GET, uri("/")))
    responseWithoutName.unsafeRunSync().status.code must beEqualTo(400)
  }

  "gives 400 on present but invalid query param" >> {
    implicit val yearQueryParamDecoder: QueryParamDecoder[Year] =
      QueryParamDecoder[Int].map(Year.of)

    object YQP extends ValidatingQueryParamDecoderMatcher[Year]("year")

    val service = HttpService[IO] {
      case GET -> Root :? YQP(y) =>
        y.fold(
          nelE => BadRequest(nelE.toList.map(_.sanitized).mkString("\n")),
          year => {
            Ok(s"hello $year")
          }
        )
    }

    val getRoot = Request[IO](Method.GET, uri("/?year=lastyear"))

    val io = service.orNotFound(getRoot)

    io.unsafeRunSync().status.code must beEqualTo(400)
  }

I'm not sure what I think here.  I don't think I like 422, which is for entities, which this is not.
http://example.com/foo/?id=42
Is the resource the foo with id = 42 or is the resource the collection of foos, filtered by id = 42?  What status would you return if there were no foo with ID 42?  What status would you return for ?id=syntacticallyInvalidForThisIdSpace?
These questions lead me to being able to defend 400 or 404.  Since there is no entity involved, I find 422 harder to justify.

Yea I don't really like 422 either. But if you have a required param, 'id'
and that is missing, I think it should be 400 and say "param id is required
"
On Sun, 20 May 2018, 12:44 Ross A. Baker<EMAIL_ADDRESS>wrote:

I'm not sure what I think here. I don't think I like 422, which is for
entities, which this is not.
http://example.com/foo/?id=42
Is the resource the foo with id = 42 or is the resource the collection of
foos, filtered by id = 42? What status would you return if there were no
foo with ID 42? What status would you return for
?id=syntacticallyInvalidForThisIdSpace?
These questions lead me to being able to defend 400 or 404. Since there is
no entity involved, I find 422 harder to justify.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/http4s/http4s/issues/1868#issuecomment-390453566, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAsX5TVDgqRSfkBrCQKmo7D-iMlA_Iweks5t0NiqgaJpZM4UF7Rw
.

A plausible way that people could be depending on the current behavior:
    val service = HttpService[IO] {
      case GET -> Root / "foo" :? Id(id) =>
         getFoo(id).fold(NotFound())(Ok(_))
      case GET -> Root / "foo" =>
         // No filtering by ID, so show them all
         Ok(listFoos)
    }

Suppose we wanted to change that so the first case returns a 400 on missing id, or introduce a new base matcher for Id.  What would its unapply return?  It could return a Validated[String, A], but then it's the right hand side's responsibilty to fold that into a BadRequest or a response.  It could throw an exception, but that would be very un-FP of us and compose terribly with other matchers.  I guess it could return an F[A] and raise error, but that's just as manual as the Validated[String, A].
I think this is an interesting idea, but I'm not yet sure how it fits with an extractor DSL.  What do you think?

Right, the optional can be folded.  Or an alternative one that returned a Validated could be folded and contain the message for the BadRequest.  (Careful: echoing back information from the request is a vector for XSS attacks.  Something vague like "missing name" is good.)
A good example would be welcome in the docs.
I think making it less manual could be done with a directives-style DSL: those can raise an error in F instead of a sum type that requires folding.

Feel like it's obligatory to post the OWASP Article on testing for reflected XSS which is what @rossabaker is talking about.
Sorry for the tangent, but yeah.


Support nodejs16.x runtime

Really appreciate you maintaing a fork.
https://aws.amazon.com/blogs/compute/node-js-16-x-runtime-now-available-in-aws-lambda/

@mLupine I am willing to do this if you don't have time. Please let me know how to do this.


feat: add testTag for automated testing

Is your feature request related to a problem? Please describe.
When writing automated test on compose screen using component like OutlinedDropdown the lack of testTag modifier on subComponent make those screen hard to test
Describe the solution you'd like
Add testTag on component with userInteraction, for example to trigger the click on the trailing Icon of the anchored Outlined of a OutlinedDropdown

Can you be more precise about "subComponent" inside the OutlinedDropdown? Options declared in the outlined dropdown is declared by you and so, you can attach your own test tag who can fit your needs for the test strategy of your product.

Hello @GerardPaligot
Currently if we set a testTag as a Modifier in the OutlinedDropdown parameters it add it to the Dropdown component.
Problem is if you need to access the anchored Outlined or even the Icon of that Outlined for exemple to open or close the DropDown

Ok got it. You don't speak about options of a dropdown but atomic elements inside the text field. Interesting.
We need to think of a approach who can let you give us these test tags because we can't apply the test tag for all text inputs in a screen.

Closed by https://github.com/Decathlon/vitamin-compose/pull/169


chore: Migrate Junit 4 to Junit 5 for showcase

fixes #2728, attempt to remove Junit 4 support after migration.
Other than POM dependency migrate, changes include:

package name changes
Junit 5 syntax upgrades, e.g. @Before --> @BeforeEach, Replace assertion methods
remove public modifier on tests and test classes.
Refactor JUnit 4 TemporaryFolder @Rule in ITGdch.java to JUnit 5 @TempDir
Replace @Test(timeout = 15000L) in ITClientShutdown.java with @Timeout(15)
Update @RunWith(Parameterized.class) test in ITHttpAnnotation.java to @ParameterizedTest with @MethodSource("data")

Note: #2737 creates a new test class with JUnit4 syntax. Depending on merging order, I will either update in this pr, or #2737. Updated.
Due to truth library depending on junit 4 (see issue), junit 4 cannot be completely removed, or will encounter java.lang.ClassNotFoundException: org.junit.runner.notification.RunListener running tests with maven surefire. To keep things cleaner, excluding the implicitly junit brought in from truth and junit-vintage-engine. We could also do the reverse, and make a comment if that's prefered.

Since Min is OOO, I will take a look a final few things for this issue and merge if everything else looks fine.

[INFO] --- maven-failsafe-plugin:3.2.5:integration-test (default) @ gapic-showcase ---
[INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

Looks like the ITs aren't actually running.

I see it is running the tests now:
[INFO] --- clirr-maven-plugin:2.8:check (default) @ gapic-showcase ---
[INFO] Skipping execution
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for GAPIC Showcase Client Core Parent 0.0.1-SNAPSHOT:
[INFO]
[INFO] GAPIC Showcase Client Core Parent .................. SUCCESS [  2.109 s]
[INFO] proto-gapic-showcase-v1beta1 ....................... SUCCESS [  1.008 s]
[INFO] grpc-gapic-showcase-v1beta1 ........................ SUCCESS [  2.228 s]
[INFO] GAPIC Showcase Client .............................. SUCCESS [01:39 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:45 min
[INFO] Finished at: 2024-05-17T19:11:27Z
[INFO] ------------------------------------------------------------------------


Room 301

Version
3.0.1
Seed
R731-KX5H-T0ZE06309F0005ZTW940ZZZZZZZZZZZZ00Z     Player: 0 Jill
Scenario
RE 3 (Jill)
What happened?
Crashes entering from the dining room 302 room to 301.

Are you able to provide a same game?
What were had you done so far in the game?

Well i was just going to the room nothing in the clock tower was done at the time besides getting into the clock tower section of the game went to the dining area and tried to go to the piano room through the dining area and it just crashed going through the door. everything up to that point in the city was complete that is a just incase info you needed. Was just playing the game all the way through like normal until i got to that point in that seed.

Duplicate of #314


Should local cache be saved first then save server change token?

https://github.com/apple/sample-cloudkit-privatedb-sync/blob/d0e8f9cbe76033629def38eeb1f61dc5211405b4/PrivateSync/ViewModel.swift#L81-L85
Hi there, I noticed this sample app saves the server change token before local cache were being saved.
Doesn't this mean if the app exits before local cache saved to the UserDefaults, the app will only fetch changes from the newest token the next time it starts and ignoring all previous changes?

Good call — this has been fixed in https://github.com/apple/sample-cloudkit-privatedb-sync/commit/fbd72540261d3270949db6789f324b1bdc805d16. Thanks!


Text Layer gets flattened.

I notice that the Sketch Plugin will attempt to create a text layer but will put nothing in it. Any text layers identified in the Canvas DOM is also treated as one single image output.

Thats the idea of the plugin, we place a transparent rectangle so you can select and comment on a particular component.


docs: update badges and clean

Self explanatory.

Codecov Report

Merging #25 (680a956) into main (e3c5690) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage   84.61%   84.61%
=======================================
  Files           1        1
  Lines          13       13
=======================================
  Hits           11       11
  Misses          2        2

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


How to get auth token which i can interally use in my application for api calls?

Hi team,
I have client-id and client-secret, But I am not able to get token for it, I was following this documentation: https://code.nsa.gov/skills-docs/skills-client/auth.html
For example:  I want to make an API call to this API: http://localhost:8081/api/projects

How should I get token
How should I pass token to API's

Thank you

sounds like you very close to making it work! see if there are any errors in the logs of your backend server as well as the skills-service's logs
I just followed Quick Start and was able to retrieve token implemented by ControllerExample
My steps are:
terminal 1:
docker run --name skills-service-1.4.4 -d -p 8080:8080 skilltree/skills-service:1.4.4
java -jar ~/Downloads/java-backend-example-1.1.0.jar

terminal 2:
$ curl<EMAIL_ADDRESS>{"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOlsic2tpbGxzLXNlcnZpY2Utb2F1dGgiXSwic2NvcGUiOlsicmVhZCIsIndyaXRlIl0sInByb3h5X3VzZXIiOiJ1c2VyMUBlbWFpbC5jb20iLCJleHAiOjE2MjAxMDY4NTgsImF1dGhvcml0aWVzIjpbIlJPTEVfVFJVU1RFRF9DTElFTlQiXSwianRpIjoiM1NXQUhweTM3SW5ZY1Uzc0VzYWt0YUdsYXk0PSIsImNsaWVudF9pZCI6Im1vdmllcyJ9.P-YyaT7SnpVW0hui9VfRuuFFYn4EW06RlzkEscArrDbPvnRCyPfsYwzqoJbE0fBKKauk805wIDK8fARUOrcmN3V3DyBbW47HyM6uay2eHCdoBPdyiTMpr_0lWikbK66qy-Fl8ORGpXZdlRlgvloLP4Kmo1WenAGNvZhNi95bMYbxxOvJh71grnXhSWXMsFyAxu3GL7HyXzC6Saud8Nawz_mhXtZJfHqfxYn4VEzwEUZ9UoxoG1w5RNZnlfAmWrsI4ITD57epTJXum9mdivAY829FQ5YFYtW1sni7Z_w2vS9tI4mRBqOmbeMYHWYUb1WzKG9-IY1FQGthLPczot15vw","token_type":"bearer","expires_in":43199,"scope":"read write","proxy_user":"user1@email.com","jti":"3SWAHpy37InYcU3sEsaktaGlay4="}

best of luck!

@sudo-may thanks a lot now getting the token.
And also the dashboard panels and all is visible on running the docker image.
But what different I am doing compared to what is mentioned on the quickstart is:

Cloned this repo : https://github.com/NationalSecurityAgency/skills-service
Build/clean/install and started service present at path: https://github.com/NationalSecurityAgency/skills-service/tree/master/service which runs on 8080
Now when I hit localhost:8080, I get: An error happened during template parsing (template: "class path resource [templates/error.html]")

Q1. what could be the reason.
Q2. And what is the docker(present on quickstart page) running - is it internally running: https://github.com/NationalSecurityAgency/skills-service/tree/master/service
or anything else? If it's the same then why do I see this error: An error happened during template parsing (template: "class path resource [templates/error.html]")

@TEJAPS once you've cloned skills-service, you need to issue npm run build in both the dashboard and client-display projects before running build/clean/install on service - the pom.xml file in service copies those UI resources during packaging

@TEJAPS  - see if the comment here helps to make anything more clear https://github.com/NationalSecurityAgency/skills-service/issues/600#issuecomment-839947719 if not, feel free to reply and we'll provide further guidance.


Fastlane action broken on ubuntu-xlarge

Description
Same issue as i had on MacOS a little while ago: https://github.com/actions/runner-images/issues/9341
Now happening with using ubuntu-xlarge_a41492fcb2fe
Image: ubuntu-22.04
Version: 20240324.2.0
Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240324.2/images/ubuntu/Ubuntu2204-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240324.2
I can't apply the workaround i used with MacOS as my yaml is slightly different with linux/android builds
  deployForAndroid:
    name: 🤖 Deploy for Android
    runs-on: ubuntu-xlarge
    needs: buildForAndroid
    if: startsWith(github.event.ref, 'refs/tags/deploy') || startsWith(github.event.ref, 'refs/tags/Deploy') || startsWith(github.event.ref, 'refs/tags/androiddeploy')
    env:
      GOOGLE_PLAY_KEY_FILE_PATH: ${{ format('{0}/fastlane/google-fastlane.json', github.workspace) }}
      ANDROID_BUILD_FILE_PATH: ${{ format('{0}/build/Android/myapp.aab', github.workspace) }}
      ANDROID_PACKAGE_NAME: com.myapp
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
          lfs: true

      - name: Download Android Artifact
        uses: actions/download-artifact@v4
        with:
          name: Build-Android
          path: build/Android

      - name: Add Authentication
        run: echo "${{ env.GITHUB_ORG_SECRETS_GOOGLE_PLAY_KEY_FILE }}" | base64 -d > $GOOGLE_PLAY_KEY_FILE_PATH

      - name: 🚀 Set up Fastlane
        uses: ruby/setup-ruby@v1
        with:
          ruby-version: 2.7.2
          bundler-cache: true

      - name: Upload to Google Play Internal
        uses: maierj/fastlane-action@516faaa1c6c7b366ecd238b4e4608d286874dd94
        with:
          lane: 'android internal' # Change to upload to a different lane

      - name: Cleanup to avoid storage limit
        if: always()
        uses: geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af
        with:
          name: build-Android

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Image: ubuntu-22.04
Version: 20240324.2.0
Is it regression?
worked last week
Expected behavior
fastlane should run without error
Actual behavior
Same as the MacOS issue with libsodium load errors
Repro steps
Try to deploy Android build to Google Play

Hello @geeklingo, we will take a look

@geeklingo, could you also share error messages and build links?

@geeklingo, could you also share error messages and build links?

2024-04-05T09:54:20.0890131Z Executing lane android internal on Linux.
2024-04-05T09:54:20.9438733Z bundler: failed to load command: fastlane (/home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/bin/fastlane)
2024-04-05T09:54:20.9453198Z /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/erb_template_helper.rb:20:in `<module:Fastlane>': uninitialized constant Fastlane::OpenStruct (NameError)
2024-04-05T09:54:20.9457336Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/erb_template_helper.rb:1:in `<top (required)>'
2024-04-05T09:54:20.9460571Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/actions/s3.rb:1:in `require'
2024-04-05T09:54:20.9464193Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/actions/s3.rb:1:in `<top (required)>'
2024-04-05T09:54:20.9467321Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/actions/actions_helper.rb:113:in `require'
2024-04-05T09:54:20.9470864Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/actions/actions_helper.rb:113:in `block in load_default_actions'
2024-04-05T09:54:20.9474018Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/actions/actions_helper.rb:112:in `each'
2024-04-05T09:54:20.9477253Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/actions/actions_helper.rb:112:in `load_default_actions'
2024-04-05T09:54:20.9480210Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane.rb:38:in `load_actions'
2024-04-05T09:54:20.9482935Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/commands_generator.rb:34:in `start'
2024-04-05T09:54:20.9485990Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
2024-04-05T09:54:20.9488812Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/gems/fastlane-2.220.0/bin/fastlane:23:in `<top (required)>'
2024-04-05T09:54:20.9491122Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/bin/fastlane:23:in `load'
2024-04-05T09:54:20.9493339Z 	from /home/runner/work/myapp/myapp/vendor/bundle/ruby/2.7.0/bin/fastlane:23:in `<top (required)>'
2024-04-05T09:54:20.9495538Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:58:in `load'
2024-04-05T09:54:20.9497725Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:58:in `kernel_load'
2024-04-05T09:54:20.9499903Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:23:in `run'
2024-04-05T09:54:20.9502168Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli.rb:492:in `exec'
2024-04-05T09:54:20.9504433Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
2024-04-05T09:54:20.9507207Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
2024-04-05T09:54:20.9510062Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor.rb:527:in `dispatch'
2024-04-05T09:54:20.9512444Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli.rb:34:in `dispatch'
2024-04-05T09:54:20.9514936Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
2024-04-05T09:54:20.9517637Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli.rb:28:in `start'
2024-04-05T09:54:20.9519999Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/exe/bundle:37:in `block in <top (required)>'
2024-04-05T09:54:20.9522660Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
2024-04-05T09:54:20.9525112Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/exe/bundle:29:in `<top (required)>'
2024-04-05T09:54:20.9526747Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/bin/bundle:23:in `load'
2024-04-05T09:54:20.9527972Z 	from /opt/hostedtoolcache/Ruby/2.7.2/x64/bin/bundle:23:in `<main>'
2024-04-05T09:54:20.9629593Z ##[error]Error: Executing lane android internal failed.
2024-04-05T09:54:20.9638444Z ##[error]Executing lane android internal failed.

@geeklingo hey! you are running ruby version 2.7.2 which is deprecated and not cached in the image (but it is still available, if you wish, that is true) and fast lane version is different from what we have installed in the runner (well, because it is pulled by ruby's bundler I believe). All that makes me believe it is not a runner image bug, so I am going to close the issue, but if you have more image-connected questions, feel free to ask.

What ruby version should I be running?

From: Mikhail Koliada @.>
Sent: Friday, April 5, 2024 21:21
To: actions/runner-images @.>
Cc: Noeneel Sharma @.>; Mention @.>
Subject: Re: [actions/runner-images] Fastlane action broken on ubuntu-xlarge (Issue #9639)
@geeklingohttps://github.com/geeklingo hey! you are running ruby version 2.7.2 which is deprecated and not cached in the image (but it is still available, if you wish, that is true) and fast lane version is different from what we have installed in the runner (well, because it is pulled by ruby's bundler I believe). All that makes me believe it is not a runner image bug, so I am going to close the issue, but if you have more image-connected questions, feel free to ask.
—
Reply to this email directly, view it on GitHubhttps://github.com/actions/runner-images/issues/9639#issuecomment-2039550883, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIWQFEEJ22OCYAVU32PD2JDY32CLJAVCNFSM6AAAAABFYFIDK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZZGU2TAOBYGM.
You are receiving this because you were mentioned.Message ID: @.***>


Add unittests - 2

[Auto generated]
Number: [#2]

python-simple-logger: Closing issue for PR: Add unittests.
PR was closed.


Multiple clients, same backend

Hello,
I'm currently planning a collaborative application. Meteor seems to provide a lot of useful functionality, but I want to make my front-end in angularjs. I'd like to split this up in an admin and user client, but with a shared meteor backend. I could make this into one big client with routing, but really, the clients have not a lot in common, so I'd like to split this into two clients for maintainability (e.g. I could later upgrade one of two clients to angularjs 2 and still leave the other on angular 1).
I can see how this would be possible with asteroid, as the client is fully seperated. Yet I'd like to take advantage of some of the benefits from angular-meteor (mainly how meteorcollections behave as normal arrays and sync happens transparent for the developer. Don't care about blaze templates though). But is it possible to create multiple clients for the same backend using angular-meteor?

Yes, you can just define 2 separate AngularJS applications.
Each AngularJS application is a module and you can load each one based on the current platform (Meteor.isCordova) or path (with a parent AngularJS application that initializes the right module).
Hope it helps


Karma becomes unresponsive instead of failing

I'm starting my Karma like this (in Java) :
ArrayList<String> karmaTestCommand = new ArrayList<String>();
boolean isWindows = System.getProperty("os.name").startsWith("Windows");
if (isWindows) {
  karmaTestCommand.add("cmd"); //on Windows, NPM is not an executable, but a .cmd file
  karmaTestCommand.add("/c");
}
karmaTestCommand.add("npm");
karmaTestCommand.add("run");
karmaTestCommand.add("test");

ProcessBuilder karmaProcessBuilder = new ProcessBuilder(karmaTestCommand);
karmaProcessBuilder.inheritIO();
Map<String, String> karmaProcessEnv = karmaProcessBuilder.environment();
karmaProcessEnv.put("RIA_TESTSERVER_PORT", Integer.toString(testserverPort));
karmaProcessEnv.put("KARMA_SERVER_PORT", Integer.toString(karmaServerPort));
Process karmaProcess = karmaProcessBuilder.start();

boolean completed = new ProcessWatchDog(karmaProcess).waitFor(20, TimeUnit.MINUTES);
if (!completed) {
  System.err.println("Tests timed out after 20 minutes!");
  RIATestReport.writeTestTimeoutReport("target/junit_reports/test-results.xml", RunKarmaTests.class.getName());
}

This starts the following script :
"scripts": {
  "test": "karma start common/test/karma/karma.conf.js --singleRun=true || (exit 0)"
}

Due to some issue with Firefox on one of our Jenkins slaves, Karma behaves like this :
[java] 02 04 2019 14:06:25.834:WARN [launcher]: Firefox have not captured in 60000 ms, killing.
[java] 02 04 2019 14:06:25.891:DEBUG [launcher]: Process Firefox exited with code 0
[java] 02 04 2019 14:06:25.891:DEBUG [temp-dir]: Cleaning temp dir C:\Users\release\AppData\Local\Temp\karma-95416947
[java] 02 04 2019 14:06:25.897:INFO [launcher]: Trying to start Firefox again (1/2).
[java] 02 04 2019 14:06:25.897:DEBUG [launcher]: Restarting Firefox
[java] 02 04 2019 14:06:25.897:DEBUG [temp-dir]: Creating temp dir at C:\Users\release\AppData\Local\Temp\karma-95416947
[java] 02 04 2019 14:06:25.898:DEBUG [launcher]: C:\Program Files\Mozilla Firefox\firefox.exe http://localhost:51005/?id=95416947 -profile C:\Users\release\AppData\Local\Temp\karma-95416947 -no-remote
[java] 02 04 2019 14:07:25.898:WARN [launcher]: Firefox have not captured in 60000 ms, killing.
[java] 02 04 2019 14:07:25.961:DEBUG [launcher]: Process Firefox exited with code 0
[java] 02 04 2019 14:07:25.961:DEBUG [temp-dir]: Cleaning temp dir C:\Users\release\AppData\Local\Temp\karma-95416947
[java] 02 04 2019 14:07:25.967:INFO [launcher]: Trying to start Firefox again (2/2).
[java] 02 04 2019 14:07:25.967:DEBUG [launcher]: Restarting Firefox
[java] 02 04 2019 14:07:25.967:DEBUG [temp-dir]: Creating temp dir at C:\Users\release\AppData\Local\Temp\karma-95416947
[java] 02 04 2019 14:07:25.968:DEBUG [launcher]: C:\Program Files\Mozilla Firefox\firefox.exe http://localhost:51005/?id=95416947 -profile C:\Users\release\AppData\Local\Temp\karma-95416947 -no-remote
[java] 02 04 2019 14:08:25.968:WARN [launcher]: Firefox have not captured in 60000 ms, killing.
[java] 02 04 2019 14:08:26.038:DEBUG [launcher]: Process Firefox exited with code 0
[java] 02 04 2019 14:08:26.038:DEBUG [temp-dir]: Cleaning temp dir C:\Users\release\AppData\Local\Temp\karma-95416947
[java] 02 04 2019 14:08:26.045:ERROR [launcher]: Firefox failed 2 times (timeout). Giving up.

This causes Karma to become unresponsive and will result in the process reaching a timeout after 20 minutes.
Is there any was I can get this process to end immediately, so I don't block my Jenkins slave for nothing?

The launcher is supposed to see browser_process_failure and exit.
https://github.com/karma-runner/karma/blob/c311ac00cef4a957f889ed613238793c0ffa95a2/lib/launchers/base.js#L111
For some reason this does not happen in your case.
To solve this we need to add encapsulated management of the state of launcher and log its transitions.  We did this for browser in #3202.  Then --logLevel=DEBUG will guide us to the issue.

To solve this we need to add encapsulated management of the state of launcher and log its transitions.
We did this for browser in #3202.

I'm not entirely sure what you're saying here.
Anyway, do you need anything from me for this?

If you want to try to debug your issue you can add logging to the copy of karma-runner base.js to see what values prevent the line above from being executed.  Since there is no practical way for us to reproduce your issue, ultimately better logging is all we can do.

I spent some time debugging this issue. You can easily reproduce it by setting an extremely low captureTimeout (like 2ms). When trying to run multiple browsers, you'll notice that Karma hangs after giving up on restarts.
Upon further investigation, I noticed that the browser_process_failure listener in https://github.com/karma-runner/karma/blob/13ed69522bb19a2d26b61fe72f1ce43b64ac30c3/lib/launcher.js#L77 is never invoked.
The event is emitted in https://github.com/karma-runner/karma/blob/13ed69522bb19a2d26b61fe72f1ce43b64ac30c3/lib/launchers/base.js#L121. Emitting the event on this (similar to the done event a few lines above it), fixes the issue:
if (this.error && this.state !== BEING_FORCE_KILLED && this.state !== RESTARTING) {
      emitter.emit('browser_process_failure', this) // trigger the server's event listener
      this.emit('browser_process_failure') // trigger the launcher's event listener
}


Support reading and writing of complex-valued data

I'm proposing (and volunteering) to add support for reading and writing of complex-valued data. I like to get buy-in here before proceeding.

I confirm that no one else is doing it (afaik)
As you know, writing is already implemented for all standard Rust types. + RGB. This leads to code duplication which I really don't like. One of our goals was to merge write_nifti and write_rgb_nifti in order to have a single write_nifti function. As always, we forgot about it :)
I would prefer not having a write_complex_nifti function alongside two other writing functions, but I understand that playing with traits in Rust is much more complex and constrained than in C++. This being said, maybe it's super simple, maybe you simply need to add Complex to DataElement, I haven't checked.

Okay, to summarize:

create a patch that adds the ability to write complex valued and RGB data to write_nifti
make sure reading works the same

I wrote about RGB because I don't like the current design, but you don't have to "fix" anything. If your goal is to handle complex number, you're free to do only that :)

Just a heads-up, I made some progress, and I can successfully write and mostly read everything I want. A major change I'm making is to remove safe_transmute in favor of bytemuck, which will simplify a lot of stuff.

Since this is merged, can we push a new version of the crate to crates.io, please?

Done!


new temporary endpoint getEmployeeID_by_employeerequest_ID

As a MIS
I want to have possibility to get employee_id having employee_request_id using MIS token
So that I can restore availability of my services after /employee_requests/ has been restricted
@AlekzandrV FYI

WS speced apiary


[2.0] Remove shapely.geos.lgeos ctypes interface to GEOS

This is on top of https://github.com/Toblerity/Shapely/pull/1161 and https://github.com/Toblerity/Shapely/pull/1162 (tests will fail here until both of those are merged).
This removes the content shapely/geos.py and shapely/ctypes_declarations.py.
The shapely.geos module is kept for now just for the geos_version(_string) variables (we should discuss whether we want to keep them long term in a geos submodule or move them top-level as we have in pygeos, but I think that's something we can see later).

I updated this PR now the last PRs that were removing usages of the ctypes interface are merged.

Coverage increased (+1.3%) to 78.55% when pulling f73628840d686e4b563d5d9d1788fd5ad2dbf64a on jorisvandenbossche:refactor-remove-lgeos into da8fd74dc23610b7f472b96c60cb69650a205a13 on Toblerity:shapely-2.0.


fixes #8

Puppet Enterprise 2016.4.0 removes the pe-internal-orchestrator.pem certificate which ncio previously relied on.
On a fresh install of Puppet Enterprise on a host called puppet.demo.internal, only the following certificates are now present at time of install:
[root@puppet ncio]# ls /etc/puppetlabs/puppet/ssl/private_keys/
pe-internal-mcollective-servers.pem
pe-internal-puppet-console-mcollective-client.pem
pe-internal-peadmin-mcollective-client.pem
puppet.demo.internal.pem

Of these files, the certificate incorporating the hostname will have access to the node classifier as this is a Puppet Enterprise master.
This PR updates the code to use this new naming convention

Note:  3 tests were failing before this PR was created - same number failing now but none appear to relate to this code change


Wordpress posts table gives InvalidValue error

I'm trying to use this script with a Wordpress database. I followed the README and created this simple import.rb file.
require 'contentful/database_importer'

class WordPressPostsTable
  include Contentful::DatabaseImporter::Resource

  self.table_name = 'wp_posts'
  self.content_type_id = 'wordpress_posts'
  self.content_type_name = 'Wordpress Post'

  id Contentful::DatabaseImporter::IdGenerator::Base, template: '{{content_type_id}}_{{title}}_{{index}}'

  field :post_title, maps_to: :title, type: :string
  field :post_content, maps_to: :content, type: :text
end

Contentful::DatabaseImporter.setup do |config|
  config.space_name = 'Blog'
  config.database_connection = 'mysql://wordpress:wordpress@db:3306/wordpress'
  config.locale = 'en-US'
end

Contentful::DatabaseImporter.run!

But when I try to run this with bundle exec ruby import rb, it returns with this stacktrace.
/usr/local/lib/ruby/2.3.0/time.rb:302:in `local': ArgumentError: argument out of range (Sequel::InvalidValue)
    from /usr/local/lib/ruby/2.3.0/time.rb:302:in `make_time'
    from /usr/local/lib/ruby/2.3.0/time.rb:366:in `parse'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/core.rb:334:in `string_to_datetime'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/timezones.rb:136:in `convert_input_timestamp'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/timezones.rb:77:in `convert_timestamp'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/database/misc.rb:300:in `to_application_timestamp'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:387:in `call'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:387:in `block in yield_rows'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:387:in `each'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:387:in `yield_rows'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:333:in `block in fetch_rows'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:192:in `_execute'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/utils/mysql_mysql2.rb:37:in `block in execute'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/database/connecting.rb:301:in `block in synchronize'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/connection_pool/threaded.rb:107:in `hold'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/database/connecting.rb:301:in `synchronize'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/utils/mysql_mysql2.rb:37:in `execute'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/dataset/actions.rb:1135:in `execute'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:374:in `execute'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/adapters/mysql.rb:318:in `fetch_rows'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/dataset/actions.rb:155:in `each'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/dataset/actions.rb:52:in `block in all'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/dataset/actions.rb:1052:in `_all'
    from /usr/local/bundle/gems/sequel-4.49.0/lib/sequel/dataset/actions.rb:52:in `all'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer/resource_class_methods.rb:74:in `all'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer/json_generator.rb:43:in `create_entries'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer/json_generator.rb:14:in `block in generate_json'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer/json_generator.rb:11:in `each'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer/json_generator.rb:11:in `generate_json'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer/json_generator.rb:78:in `generate_json!'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer.rb:37:in `generate_json!'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer.rb:42:in `generate_json_file!'
    from /usr/local/bundle/gems/contentful-database-importer-0.6.0/lib/contentful/database_importer.rb:71:in `run!'
    from import.rb:28:in `<main>'

Any idea what this could be?

Hey @rainmaker2k,
I'm not entirely sure what may be going on without more context, apparently, the SQL Driver is failing to fetch a date from your wordpress table, but I can't for sure confirm this without knowing the structure of your database.
Cheers


Add total result count?

Elasticsearch provides TotalHits, we could include it in the interface if we feel it adds value?

:+1: for adding total number of matching documents --- it could be displayed as a small grey number above or below the search results.

PR sent https://github.com/commonsearch/cosr-front/pull/29

Fixed by @chaconnewu :)


Show "Loading..." when opening Wave app.

Wave app opens.
Loading label appears.
WebView loads site offscreen in a tiny frame.
Site gets loaded.
Css and javascript gets injected.
Frame gets resized to fill window, and gets centered.
Loading label disappears.

Closing this since this project is kind of dead.


Implemented a type check in copy method of QuantumCircuit class

Summary
Forces the arguments to be of string or None type for copy method of QuantumCircuit Class hence solving issues that may rise due to unsupported/unwanted types.
Details and comments
The code checks if the 'name' argument is of string or None type.
If 'name' is of string or None type, Then the following code creates a copy of the provided circuit.
Else, It raises a TypeError.
Closes #10487

By the way, there's no need to close and open PRs.  You can just push commits to the PR you've already got open.

By the test do you mean adding the following?
self.assertRaises(TypeError, qc.copy, namearg) # where namearg is not an str or None type

Sure, something like
class TestCircuitOperations(QiskitTestCase):
    def test_circuit_copy_rejects_bad_types(self):
        qc = ...
        with self.assertRaises(TypeError):
            qc.copy(name=...)

Sorry, I realise I wasn't super clear: I didn't mean literally one line, I was being a bit imprecise and just meant that it only needs to be a very short test.

I did take it literally. No problem :)

Should I write tests for both methods under just one function or two?
What I mean to say is:
Should I do this -
class TestCircuitOperations(QiskitTestCase):
    def test_circuit_copy_rejects_bad_types(self):
        ...

or
class TestCircuitOperations(QiskitTestCase):
    def test_circuit_copy_rejects_bad_types(self):
        ...
    def test_circuit_copy_empty_like_rejects_bad_types(self):
        ...

Sorry for so many questions.

Don't worry it's ok - we all need to learn. Here, it's probably best for you to write two separate functions. It's ok in tests if the code is a little more duplicated, because test code should look really obviously correct to someone reading the test, as far as possible.

@jakelishman
I know you are very busy right now (as I can see from the frequent pull requests). Can you please review the updates so that this issue can be closed?
Thank you

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
11 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.01%) to 85.895%

Files with Coverage Reduction
New Missed Lines
%

crates/accelerate/src/sabre_swap/mod.rs
1
97.53%

crates/qasm2/src/lex.rs
4
90.63%

crates/qasm2/src/parse.rs
6
97.13%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
73065

Relevant Lines:
85063

💛  - Coveralls


Support for asynchronously running a kernel

Implement a way to asynchronously run a kernel with also an easy way to wait for the kernel to end like:
Kernel k = ...;
Execution ex = k.executeAsync(...);
ex.waitUntilFinished();

@CC007 There is an easy path for this (run each kernel in its own cpu thread) but i dont like that. It should be possible to do from a single thread in theory. I like this feature and want to try to add a bounty to try to get this one implemented. With a bounty in place would you have any interest in taking this up? If not I have a group that usually takes on most bounties, wanted to give you first dibs.


Translations In "YAML" Files Not Recognized

Describe the bug
If you try to do normal translations with the PyI18n class based on .yaml files (not .yml), you will get an error message for each key that a suitable translation could not be found, even though they actually exist in the files. If you change the file extension back to .yml, everything works fine.
To Reproduce
I have uploaded the example code to this repository.
Note that pyi18n_example_does_work returns the correct string Hello World! while pyi18n_example_should_work returns missing translation for: en.hello.
The two packages are identical except for the extensions of the YAML files.
Expected behavior
Files with the .yaml extension should behave the same as files with the .yml extension.
Additional context
The problem was supposedly already solved in #17, but apparently it didn't work completely.

Hello, thanks for your issue. Did you download the package using pip? if yes then you have to wait a bit because the version with the fix is not released yet, I will do it as soon as possible.

I released the package into PyPi https://github.com/sectasy0/pyi18n/releases/tag/stable-1.2.2


BSQL Q08 fails multi-node SF10K with UVM off

BSQL Q08 fails at SF10K on the 17-node cluster with TCP and UVM off ("existing" allocator for blazing)

No longer relevant.


Refactor device provision methods and implement debug logging

PR DESCRIPTION
Student
Name: Chew Kah Chun
Matric No: U2102859/1
Project: ThingsBoard
Reengineering Task
Refactor device provision methods and implement debug logging

(DeviceProvisionServiceImpl.java)

Issue Addressed

Missing Debug Logs (whole file)
There is an opportunity to add more logging for debugging purposes in certain critical points, such as after checking if the device exists or while processing device credentials.

Checking Device Credentials (provisionDeviceViaX509Chain Method)
Currently, the checking for an existing device's credentials and the update of the device's certificate is done somewhat rigidly. It can be refactored to improve readability and make it more robust.

Execution Exception Handling (processProvision Method)
This method throws a ProvisionFailedException when it encounters an ExecutionException. This could be refined by handling the exception more granularly.

What Have Been Reengineered

Added Detailed Logging at the Start and End of Critical Methods
This task is focused on enhancing the logging for the start and end of critical methods, at decision points, and at significant events in the DeviceProvisionServiceImpl class. Essential debug logs have been added at key points, such as when the provisioning process begins, when devices are being created or updated, and when exceptions occur.

Updated Device Credentials When Certificates Change (provisionDeviceViaX509Chain Method)
Previously, the logic for updating device credentials in case the certificate changed was less flexible, sometimes leading to unnecessary failures or manual intervention. In the reengineered version, more flexible checks are allowed by examining credentials in a more detailed and context-aware manner.

//Previous if-checking:
if (DeviceCredentialsType.X509_CERTIFICATE.equals(deviceCredentials.getCredentialsType())) {

//Modified if-checking:
if (DeviceCredentialsType.X509_CERTIFICATE.equals(deviceCredentials.getCredentialsType())  && !deviceCredentials.getCredentialsValue().equals(provisionRequest.getCredentialsData().getX509CertHash())) {

Modified Exception Handling to Log Specific Causes of Failure (processProvision Method)
The modification of the code includes more granular exception handling to log the specific causes of failures during the provisioning process. By logging error messages with additional information about the error context and the values involved, errors and issues can be easily identified and troubleshot when they occur.

// Previous exception handling
      catch (InterruptedException | ExecutionException e) {
          throw new ProvisionFailedException(ProvisionResponseStatus.FAILURE.name());
      }

// Refined exception handling
      catch (InterruptedException e) {
          Thread.currentThread().interrupt(); // Preserve interrupt status
          log.error("Provision interrupted for device {}", device.getName(), e);
          throw new ProvisionFailedException(ProvisionResponseStatus.FAILURE.name());
      } catch (ExecutionException e) {
          log.error("Execution error during provisioning device {}", device.getName(), e);
          throw new ProvisionFailedException(ProvisionResponseStatus.FAILURE.name());
      }

Reengineering Strategy or Approach Used

Rework Strategy
The core logic of the device provisioning process was adjusted to better align with the evolving requirements and potential edge cases. This involved refining the way credentials are handled, especially in cases where certificates are updated, and improving the flexibility of the provisioning system. By enhancing error handling and making credential management more adaptable, we ensured that the system remains robust in various situations. The rework aimed to improve specific areas like exception handling, credential updates, and logging, ensuring a smoother operation without a complete overhaul of the system.

Incremental Approach
Changes were implemented step-by-step to avoid disruption and ensure continuous operation. This allowed us to test the system after each change, verify that the enhancements were effective, and adjust based on feedback and new findings. By incrementally improving the provisioning process, we could address specific issues, such as the rigidity in credential handling, without affecting the overall system integrity. This approach also made it easier to handle complexities as they emerged during the reengineering phase, and it ensured a controlled, risk-mitigated update process.

Impact of Changes

Increased Traceability
By adding detailed logging, every step in the provisioning process is now clearly documented. This enhances traceability, making it much easier to audit and monitor the system, especially in production environments. In the case of errors, the logs provide vital information that can speed up issue resolution.

Reduced Errors in Device Provisioning
The refinement of the credential update logic increases the system’s ability to handle certificate changes without manual intervention. This leads to fewer errors and smoother device provisioning, reducing the burden on system administrators and increasing overall system uptime.

Faster Troubleshooting
With more granular exception handling and specific failure causes being logged, troubleshooting becomes faster and more efficient. Issues can now be pinpointed with greater accuracy, which reduces downtime and enhances the overall support experience.

Improved Flexibility
If the current service is rigid or not scalable, it may be difficult to add new device types, handle evolving configurations, or manage large numbers of devices. A flexible, well-structured implementation allows the platform to handle diverse devices and use cases more effectively.

Very good!


pcars2 collision magnitude tuning

Still getting 'good pass' messages with max collision threshold at 0.1, probably need to reduce this and test a bit by bouncing off the ai

2cents - in rf2 implementation there's no min collision threshold - any contact is dirty racing.

Was also watching a stream where the guy got the good pass message even though the other guy was off track, i think we might need to add a few more checks for this.

it's not that I don't trust PCars2's data, but I don't trust PCars2's data. I'll reduce the collision magnitude threshold and do a bit of testing, but I'm not convinced we'll be able to filter out bump-n-run passes without disabling this entirely.
Establishing if an opponent is off-track isn't really possible for some games (pcars, r3e). The app currently checks if there's a high speed difference between the 2 cars and disables 'good pass' messages in this case, which catches a lot of cases where an opponent is off track when you pass him


fix to be compatible with LS 5.0 core

LS 5.0 introduces log4j2 logging, so this PR updates the plugin to support that.

LGTM, travis passes.


Remove cython from install_requires

Having cython in install_requires creates a problem down the line in the conda-forge package, which does not carry cython as a runtime dependency, which in turn leads entry_point resolution in downstream packages to a failure.
Of course, one solution is to add cython as a runtime dependency to the conda-forge package, but I am wondering if cython is actually needed as a runtime dependency. Isn't it enough to have it in setup_requires?

@bjlittle, what's your take on this?

@zklaus Sorry, I'm super late to this... :blush:
The install_requires is there for pip really... how are you hitting this problem through conda? Just curious. I'm not really understanding the context of the problem

For pip, or any other Python packaging, I guess you only need setup_requires. When you add it to install_requires it becomes a run time dependency and pip check will fail if you don't have it installed. It is not really a conda issue, we only catch it b/c we run pip check in our CIs.

@zklaus Okay, I'm going to address this today, and push another release of python-stratify :+1:

Thanks @bjlittle, and no worries. To add to what @ocefpaf said, when using entry_points this check now happens automatically on running a program. That may be a relatively recent change since entry points now use importlib_metadata instead of pkg_resources by default at least on python 3.8, but here we are. Basically, on every run of a program as a first step all declared runtime dependencies are checked, regardless of whether they are actually used.

@zklaus Ahhh okay, lovely thanks, now I finally understand the context of what you were originally saying... thanks for clarifying.
Much appreciated :beers:

Closed by #41


Added statement on 3rd party tech usage

This relates to the text on "using 3rd party technologies" that Jeffrey Richter and I created & reviewed offline with the architectural board.  I've merged that text into the Dependencies section.  I also fixed a few markdown errors that I found elsewhere in this file while I was in there.
If further work is needed on the 3rd party tech piece, reviewers are asked to provide replacement text as required -- thank you!

Looks good! Thanks for this update to the guidelines. I think it's a nice improvement.


add github issue templates

What is the change?

Add  bug_report.md  to enable Github's new issue template form

https://youtu.be/qQE1BUkf2-s?t=23

Add config.yml file to direct user's to the right place if they are looking to create an issue or  ask question

Motivation

encourage's bug reporter's to put more care into their bug report before submission
this may help react-flow's maintainer's receive more detailed & higher quality bug report's (benefits user's / readers as well)
prevents bug reporter from submitting a bug IF they do not fill in the required fields specified in the bug_report.yml file
adds helpful tips for user's during the process of creating a bug/issue report

Demo of Change

https://github.com/cliffordfajardo/TEST-react-flow-gh-template/issues/new/choose

@chrtze @moklick

Hey @cliffordfajardo
thanks a lot for your work here! This is super helpful.


i cant install plugins (krnl cause im poor)

when ever i execute the script using krnl, it doesnt allow me to install any plugins, yes, i do click the install button, how ever, nothing seems to work

haha im the first one to request an issue

oh nvm it worked eventually

bad


[Bug]: Click on data archive to jump to logic change again

ODC version
ODC432
OB version
independent
What happened?
Click on data archive to jump to logic change again

What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?
。
Anything else we need to know?
No response

Fixed In Commit 6c75e27e69a337e5e73d82fc447bffc111348e89
------
畅晚
Fri Sep 13 09:57:13 2024 +0800

pass


Documentation improvement for macOS

Is your feature request related to a problem? Please describe.
The python quickstart sample that accesses the microphone did not work out of the box for me on macOS.
I needed to grant access to the microphone to the 'Terminal' application via the 'privacy' tab.

Describe the solution you'd like
It would be nice if the documentation mentioned this (or if it already does to mention it in a place that's more likely to be seen by the average user).
I haven't found a way to make the java sample work (running from Intellij). I think it could be a similar reason, but intellij is not in the list of applications that can be granted access to the microphone.

I made the change under Build and Run app in this document. Should be live by 4/28.


v0.25.0 otlp example fails

Bug Report
Version
0.25.0, latest jaeger (1.59.0)
Platform
macOS
Explaining
opentelemetry-otlp example returns an error and is not consistent generating traces.
executing the example opentelemetry-otlp  with cargo run --example opentelemetry-otlp it returns  the following:
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.21s
     Running `target/debug/examples/opentelemetry-otlp`
2024-07-24T18:36:12.618578Z  INFO foo: opentelemetry_otlp: handle foo monotonic_counter.foo=1 key_1="bar" key_2=10
2024-07-24T18:36:12.618741Z  INFO foo: opentelemetry_otlp: histogram example histogram.baz=10
{"resourceMetrics":{"resource":{"attributes":[{"key":"deployment.environment","value":{"stringValue":"develop"}},{"key":"service.version","value":{"stringValue":"0.25.0"}},{"key":"service.name","value":{"stringValue":"tracing-opentelemetry"}}]},"scopeMetrics":[{"scope":{"name":"tracing/tracing-opentelemetry","version":"0.25.0"},"metrics":[{"name":"foo_named","sum":{"dataPoints":[{"attributes":[{"key":"key_1","value":{"stringValue":"bar"}}],"startTime":"2024-07-24 18:36:12.618","time":"2024-07-24 18:36:12.623","startTimeUnixNano":1721846172618688000,"timeUnixNano":1721846172623969000,"value":1}],"aggregationTemporality":"Cumulative","isMonotonic":true}}]}],"schemaUrl":"https://opentelemetry.io/schemas/1.26.0"}}
Other("[ExportErr(Status { code: Unimplemented, message: \", detailed error message: unknown service opentelemetry.proto.collector.metrics.v1.MetricsService\" })]")

The last line contains an unimplemented error, regarding the metrics service.
The traces that this example would generate, are generated RANDOMLY (sometimes appear on jaeger, sometimes don't) when executing the example, even tho we are getting an error.
If we execute this same example in v0.24.0 we get the following:
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/examples/opentelemetry-otlp`
2024-07-24T18:44:48.482155Z  INFO foo: opentelemetry_otlp: handle foo monotonic_counter.foo=1 key_1="bar" key_2=10
2024-07-24T18:44:48.482344Z  INFO foo: opentelemetry_otlp: histogram example histogram.baz=10
{"resourceMetrics":{"resource":{"attributes":[{"key":"service.version","value":{"stringValue":"0.24.0"}},{"key":"service.name","value":{"stringValue":"tracing-opentelemetry"}},{"key":"deployment.environment","value":{"stringValue":"develop"}}]},"scopeMetrics":[{"scope":{"name":"tracing/tracing-opentelemetry","version":"0.24.0"},"metrics":[{"name":"foo_named","sum":{"dataPoints":[{"attributes":{"key_1":{"stringValue":"bar"}},"startTime":"2024-07-24 18:44:48.482","time":"2024-07-24 18:44:48.494","startTimeUnixNano":1721846688482274000,"timeUnixNano":1721846688494701000,"value":1}],"aggregationTemporality":"Cumulative","isMonotonic":true}}]}],"schemaUrl":"https://opentelemetry.io/schemas/1.25.0"}}

No error, works as expected, and it generates the traces every time we execute it.
If we revert the changes made to the example, and change a little bit the method to work with the new version changes, It will not work as well.
Tried downgrading jaeger, and error keeps happening.
The error seems to be coming from the following code, when an OtelGuard is dropped:
 impl Drop for OtelGuard {
    fn drop(&mut self) {
        if let Err(err) = self.meter_provider.shutdown() { // <- ERROR HAPPENS HERE
            eprintln!("{err:?}");
        }
        opentelemetry::global::shutdown_tracer_provider();
    }
}

I probably won't have time to look into this in detail. Would suggest looking through the opentelemetry-otlp changelog in some detail to see if something stands out.

Their otlp example returns the same error (https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-otlp/examples/basic-otlp).

Okay, I recommend you open an issue against the upstream repo, then.


Allow other subscription configurations for default matrix

The default test matrix was always overriding the subscription configuration. This removes those overrides and we are already defaulting to the normal configuration via the default parameter value for SubscriptionConfiguration. So this change should be a no-op for everyone except for the pipelines that try to override the configuration in their tests.yml which should now work.

/azp run java - keyvault - tests

failed test leg is unrelated to this change so going ahead and merging.


Report UserAgent in API calls

The packngo API calls should report a CCM specific user-agent so the CCM usage can be quantified.
Currently, the User-Agent reported is the default packngo/v0.1.0 UA

Want to open a PR? We can get it in before the next release is cut end of week.


Module is broken after 0.92 update on Hassio

After update to 0.92 on hassio it doesn't even complete the config check. Error is:
Configuration invalid
Integration sony not found when trying to verify its media_player platform.

I am unable to replicate this error at the moment.
Does the custom component still exist in the right directory after the hassio update?

@dilruacs Yes and I've reinstalled it just in case. A custom card on lovelace I created to check updates etc is working properly so custom_updater is loaded and on 5.0.0 version.
Can't figure out why.
I've created a folder called sony on folder custom_components and copy the 2 files. Save and check config, all ok. Restart assistant, all ok.
Go to configuration.yaml to add the media player

platform: sony
host: 192.x.x.x
Check config : Integration sony not found when trying to verify its media_player platform.

Ok so figured it out. For some reason hass thought there were files inside sony folder and probably tried to load them. Force deleted the folder from command line, recreated it and voila! Case closed! When you have the time I'd be grateful to check the other problem I still have with the error "Failed to read command list from device!

@drageloth Thanks for the update, I was just installing a fresh HassIO to try to replicate your problem.
I will have a look at the other issue later today.