Add option to specify output language for CLI input

I am not sure if this is the best approach, but I wanted to propose it for consideration.
What this Pull Request (PR) does
Add option to specify output language for CLI input

Added --output-language (-L) argument to specify the output language for CLI input. Default is English.
Updated main function to include the output language instruction in the input text if specified.

This allows users to set the desired output language for responses directly from the command line.
Related issues
https://github.com/JFK/fabric/issues/5

Would it not be possible to simply add a line in the system.md pattern file text indicating what the output language should be?

@silverstreak

Would it not be possible to simply add a line in the system.md pattern file text indicating what the output language should be?

I tried to add a line into system.md but it did not work...
Anyway I can understand English.

I'll also try it at my end and let you know. But in general, if it works, then it should be fairly easy to provide an input parameter like --output-language and then programmatically append/prepend "The output should be in xxx language" to the system.md file text that is sent to the model.

... to the system.md file text that is sent to the model.

I've don't similarly with a context.md (& the -c flag) to good effect. I was getting some French responses prior but not when using my modified context file.
Side note: I saw someone mention adding functions to specify different context files. This seems like it would be super useful in the case of switching response languages per fabric command (among other things).

I'll also try it at my end and let you know.

OK so here's the result of my investigation.

--context option

The documentation on the --context option is quite sparse (almost non-existent)
Created context.md in ~/.config/fabric
Added this to it: # FINAL INSTRUCTION \n All the output should be in French.
Command used: pbpaste | fabric -c -p extract_wisdom
Outcome: nothing happens. The context file appears to be ignored
Note: maybe I'm using --context wrong

Append a line to an existing pattern

Used extract_wisdom as an example
Appended the same line to the end of it: # FINAL INSTRUCTION \n All the output should be in French.
Outcome: output is in French

So I really think the most intuitive way to implement this feature (and actually, more generally, to add custom instructions to any pattern) is to do it this way: append whatever custom instructions you want to the system.md text that is sent to the model. Allow the user to input them via a file and using an option like --custom_instructions. My 2 cents.

We're getting ready to migrate to Golang; please resubmit then if this hasn't been addressed. Thank you!


[embedded] Ignore 'do not specialize' @_semantics attributes in embedded Swift mode

We cannot allow the 'do not specialize' @_semantics attributes in embedded Swift because specialization is mandatory for soundness of the resulting compilations. The attached test crashes (triggers a "unexpected unspecialized function found during IRGen" assert) without the fix.
We have been a bit lucky that so far the parts of the stdlib that we have for embedded Swift didn't use these attributes, but I have observed that some other parts (e.g. Dictionary implementation) do use them, so we need to fix this problem.

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform


https://github.com/Bunlong/react-screen-capture/issues/10 - Seems to …

…break on all screens above 1080p - fixed

fixed

fixed

could you please merge and release?

@Bunlong please merge


Compute NWP means & std over the complete dataset

Currently computed using:
nwp_ds.data.isel(init_time=slice(0, 10)).mean(dim=['step', 'x', 'init_time', 'y']).compute()

Using 100 init_times crashes (dask tries to use > 64 GB of RAM).
Try again with a VM with more RAM

Closing.  This is a duplicate of #407


Cannot reconnect to using 'Connect to Previous IBM i' using ssh key

Describe the bug
When using password only the 'Connect to Previous IBM i' works great.  I can set up a connection with my id_rsa ssh key generated on my IBMi in a qsh session using  ssh-keygen -t rsa -N "". However when I try to use the 'Connect to Previous IBM i feature i get the error message:
Not connected to mysvr.domain! Error while signing data with privateKey: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR
VS code -  Version: 1.59.0
Code for IBM i ext - v0.6.7
IBM i OS - v7r2

Can you connect successfully using another client, e.g. PuTTY, or ssh in windows?  This might help clarify where the problem lies.
@sleepy-l0c0

Connecting the first time isn't an Issue at all. It the connect to previous
option. Yes I can ssh from (wsl) terminal in vs code using same key.
On Fri, Aug 20, 2021, 10:47 SJLennon @.***> wrote:

Can you connect successfully using another client, e.g. PuTTY, or ssh in
windows? This might help clarify where the problem lies.
@sleepy-l0c0 https://github.com/sleepy-l0c0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/halcyon-tech/vscode-ibmi/issues/249#issuecomment-902746522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK52JQEFTGTTADGZZBQWLZ3T5ZTHNANCNFSM5COMQLGQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Is possibly the same issue as #209

@sleepy-l0c0 Whats the status here?

I haven't figured it out yet. If it's just me feel free to close the issue.
On Sun, Nov 7, 2021, 10:24 barry @.***> wrote:

@sleepy-l0c0 https://github.com/sleepy-l0c0 Whats the status here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/halcyon-tech/vscode-ibmi/issues/249#issuecomment-962630065,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK52JQDGGS6HL52MSJWQCB3UK2KZ3ANCNFSM5COMQLGQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@sleepy-l0c0 I won't close the issue yet.
I want to make sure we solve any open issues and make sure you have a good experience. Are you able to provide detailed steps for me to recreate this issue?

Not currently in front of my computer. I will give it a go and see if I can
recreate my issue detailing my steps a I proceed.
On Sun, Nov 7, 2021, 10:57 barry @.***> wrote:

@sleepy-l0c0 https://github.com/sleepy-l0c0 I won't close the issue yet.
I want to make sure we solve any open issues and make sure you have a good
experience. Are you able to provide detailed steps for me to recreate this
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/halcyon-tech/vscode-ibmi/issues/249#issuecomment-962635651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK52JQAP6X7VD3JIOTAWBZDUK2OX7ANCNFSM5COMQLGQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Well good news. I have tried a couple of times and was not successful in
recreating the issue. I'm not sure what changed, however I'm glad it works
now.
Here were my steps:

remove existing profile (only had one set for password)
create a new ssh key on my wsl with ssh-keygen command.
3)scp pub file to the 400 with password auth.
cat the pub key to authorized_keys on my profile
copy private key to easier to access location for vscode.
setup connection profile in code for ibm I
connect successfully
(This has been the case always)
close vscode reopen
used to prompt me a button "reconnect to previous ibmi".
9a) this time I hit a green 'play' triangle and it connected again.

On Sun, Nov 7, 2021, 11:41 Coulyb Javer @.***> wrote:

Not currently in front of my computer. I will give it a go and see if I
can recreate my issue detailing my steps a I proceed.
On Sun, Nov 7, 2021, 10:57 barry @.***> wrote:

@sleepy-l0c0 https://github.com/sleepy-l0c0 I won't close the issue
yet.
I want to make sure we solve any open issues and make sure you have a
good experience. Are you able to provide detailed steps for me to recreate
this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/halcyon-tech/vscode-ibmi/issues/249#issuecomment-962635651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK52JQAP6X7VD3JIOTAWBZDUK2OX7ANCNFSM5COMQLGQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@sleepy-l0c0 Nice!!
Thanks for sharing your steps. Please feel free to close this issue.


Second table fix

First time, I didn't do it right; this should be right now. The "rowspan" lines were missing an end

Q
A

content fix?
yes

New article?
no

What's in this Pull Request?
These should be the correct fixes for these tables.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/design/themes-colors.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Bug handling of spatial filter in add update and delete

https://github.com/R-ArcGIS/arcgislayers/blob/ea13571ff95b88398e3ff08313c9ae733de3184a/R/arc-add-update-delete.R#L265C10-L265C10
CC @elipousson

This line uses the CRS of x and ignores the spatial reference of filter_geom. It should prefer CRS of filter_geom and if is sfg or is.na() we use that of x

Closed by #80

Should taking the CRS from filter_geom vs. x be controlled by an option? I get the logic but also kind of weird for the output CRS to be determined by the spatial filter object. Is there still an option to set an output CRS that could override both filter_geom and x?

It doesn't. The spatial filter object can have a different CRS than the feature layer. The CRS of  prepare_spatial_filter() is used to to determine what CRS the spatial filter object is in--not the output.

Aha. Thanks for clarifying. Probably should have waited until I was looking at the code again before asking!


Which example is about Commission Fee is not Enough: A Hierarchical Reinforced Framework for Portfolio Management (AAAI 2021)

It is a great honor to read this paper published in AAAI in 2021,
Commission Fee is not Enough: A Hierarchical Reinforced Framework for Portfolio Management.
I would like to know which example I can refer to for the HRPM architecture of this paper.
Thanks.

The code of HRPM is not available in the current code base. We rebuild the whole code structure and since HRPM is a hierarchical framework which is different from other methods. We need more time to reimplement it. Sorry for the inconvenience.

Thank you for your reply.
Please notify me when it is updated if it is not troublesome.

We will let you know when the implementation of the AAAI paper is available. Thanks for your interest on our work.


Google search still gives the old documentation as one of top search results

📰 Custom Issue

Hey guys, just heads up that the old 2.x documentation links still pop up in Google searches in top three results, and could even be the top result (see eg "quickplot" where the actual working link is fourth or fifth result). Not an issue perse but rather a heads up just so you are aware of this, you may get questions from people not finding what they're looking for :+1:

@valeriupredoi I'm going to close this issue, thanks for letting us know.
This trend will change over time, and customising your google searches to between the period 01 Jan 2021 to 14 May 2021 gives:


feat: add languageChange event emitter

User can now subscribe to languageChanged event

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 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
39

💛  - Coveralls


Improved testimonial

I have made posiible changes and now css and js files are working properly .

this is the previous version.

and second one is the new version.
Solved issue #160
@codervivek5  Kindly merge the pr.

kindly solve merge conflict

Ok
On Mon, 13 Mar, 2023, 10:38 pm Vivek Prajapati, @.***>
wrote:

kindly solve merge conflict
—
Reply to this email directly, view it on GitHub
https://github.com/codervivek5/Formfil/pull/163#issuecomment-1466553259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2YSDDGIIHVOFHYUL73XVY3W35H7VANCNFSM6AAAAAAVVTIIWM
.
You are receiving this because you authored the thread.Message ID:
@.***>


An option to add automatic IDs to headings

GitHub flavoured markdown adds automatic IDs to headings, and it would be great to see this as an option here (disclaimer: I'm hoping to see the feature in Stash/Bitbucket server).
This is not in commonmark (and won't be added) though some implementations even do this by default.
In the case of GitHub, a heading #foo gets an ID user-generated-foo to avoid clobbering IDs used elsewhere. There's then some JS that means that you can use #foo in your URL instead of #user-generated-foo.
This would allow us to use tools like markdown-toc or doctoc on Bitbucket server.

Cheeky :). But I agree, this would be useful.
Should be pretty simple to build it as an extension using an AttributeProvider that looks at Header nodes.
I won't have time in the next few weeks, but if someone else wants to take a stab at this, you're welcome.

I've looked into what existing implementations do for converting the heading text to an ID:
http://johnmacfarlane.net/babelmark2/?text=%23+Heading

%23+heading

%23+heading%252

%23+heading{}3

%23+heading+ä

%23+heading+😄

%23+heading+😄

%23+heading+😄

%23+heading++4

%23+1+heading

%23+123

%23+--

%23+00A1¡test

%23+A2¢test
HTML itself doesn't put any restrictions on the format, but other specifications do. One that is probably useful to make IDs conform to is CSS:
http://www.w3.org/TR/CSS21/syndata.html#value-def-identifier
Looks like that is what Pandoc does, except that it strips more characters such as ¢ (U+00A2).
It also avoids duplicates by appending -N.

Here is the implementation I use to replicate GitHub behaviour. It is Kotlin but should be quite readable to Java users.
The header text is mapped as follows:

spaces and dash - map to dash -
underscore unchanged
alpha to lowercase, It is important to handle non-ASCII alpha characters properly. I didn't at first and this resulted in headers that contained all Chinese characters to have no ids.
numeric unchanged
every thing else skipped

If an id was already encountered in a top-down page parse then -# is appended to the id, where # is an incremented integer, starting with 1.
No attempt is made to disambiguate id's appearing further down the page. So # abc # abc and # abc-1 will produce three headers with the following ids: abc, abc-1, abc-1. This is how GitHub does it, last I checked.
It sounds like the AttributeProvider is the right approach. I implemented something similar in my pegdown fork to do this. My use of the parser would require many user selectable options that change the parser and HTML generator flavours to match the algorithm of the target markdown processor.
In idea-multimarkdown plugin I implemented inspections that validate links and anchor refs for being undefined or having duplicates. I also have anchor ref completions and refactoring so it is important for me to have the same behaviour as GitHub, otherwise inspections would be meaningless and completions/refactoring would result in erroneous anchor refs.
class GitHubHeaderIdComputer: HeaderIdComputer {
    protected val headerBaseIds = HashMap<String, Int>()

    override fun computeHeaderId(node: HeaderNode, anchorLinkNode: AnchorLinkNode?, headerText: String): String {
        var baseRefId = computeHeaderId(headerText)

        if (headerBaseIds.containsKey(baseRefId)) {
            var index = headerBaseIds[baseRefId] as Int
            index++
            headerBaseIds.put(baseRefId, index);
            baseRefId += "-$index"
        } else {
            headerBaseIds.put(baseRefId, 0)
        }

        return baseRefId
    }

    companion object {
        fun computeHeaderId(headerText: String): String {
            var baseRefId = ""
            for (c in headerText) {
                when (c) {
                    ' ' -> baseRefId += '-'
                    '-' -> baseRefId += '-'
                    '_' -> baseRefId += '_'
                    else -> {
                        if ( c.isAlphaNumeric()) baseRefId += toLowerCase(c)
                    }
                }
            }
            return baseRefId
        }
    }
}

Thanks for the insights, @vsch.
Just released 0.7.0 with an extension for this, thanks @paulthom12345 🎉: https://github.com/atlassian/commonmark-java/releases/tag/commonmark-parent-0.7.0


GitPython locked to old version causes PackingType exception

My first issue here, so I wanted to say thanks for bringing the loveliness of semantic release to python!
Today I ran into an issue with GitPython that has already been fixed in a newer version https://github.com/gitpython-developers/GitPython/issues/687
It seems that the requirements.txt file here is locking GitPython to an old version.  Any chance that could be updated?

Yeah, sure I might be able to do this in the end of the week. If you want it faster a PR is always welcome. :v:

Fixed in v3.11.1 thanks to @blackHatMonkey


src/std/process.d: _spawnvp error handling is broken

danny.milo (@daym) reported this on 2014-11-19T21:33:14Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=13753
CC List

bugzilla (@WalterBright)

Description
The _spawnvp in src/std/process.d is broken.

First, if the child process (say it has pid B) fails to execvp, it's a bad idea to then throw an Exception. The entire point of spawnvp in general is to hide the fact that the current process A was forked off. But now the Exception propagates through process B, so certainly the caller will notice that something is off (the caller is suddenly inside another process than he started out in).

Later on, the waitpid result is not checked. It is possible for waitpid to return (-1). In that case, errno contains the error code and "status" contains garbage, which is then compared against.

Also, all Posix system calls can return (-1) and errno = EINTR (see <http://www.jwz.org/doc/worse-is-better.html>, search for "PC loser-ing") to indicate that while the user process asked for action S to be performed, really it should be checking and doing some other action T before.

So for the latter there really should be some global delegate that is called on EINTR which decides whether to do anything about it, possibly terminating the loop (or not, it depends).

This is not specific to process.d but all functions that do system calls should call this. Even std.stdio.File functions should do this.

Also, it throws an Exception (literally that) using strerror_r to build it instead of just using ErrnoException. Why?

!!!There are attachements in the bugzilla issue that have not been copied over!!!

bugzilla (@WalterBright) commented on 2019-12-10T10:27:22Z
spawnvp seems only to exist for windows now. But I did not check if this has been the case in 2014 too.

Tried to adapt the test for "browse":

```
import std.process;
import core.thread;

int main() {
        auto pidBefore = getpid();
        try {
                browse("DOESNOTEXIST");
                assert(false);
        } catch(Exception e) {
                auto pidAfterwards = getpid();
                assert(pidBefore == pidAfterwards); // make sure we are still in the same process
        }
        return 0;
}
```

This produces an Assertion failure (POSIX). And the process seems still to be running after the main process has stopped.

danny.milo commented on 2014-11-19T22:00:46Z
See http://www.gnu.org/software/libc/manual/html_node/Interrupted-Primitives.html

danny.milo commented on 2014-11-25T18:25:13Z
Also, both the OSX and the Posix version of browse in the same file are broken in the same way...

danny.milo commented on 2014-11-19T21:36:22Z
Created attachment 1454
Tests whether spawnvp magically forks processes for the caller

Tests whether spawnvp magically switches processes. Try with version(Posix) implementation of spawnvp.

danny.milo commented on 2014-11-19T21:56:03Z
Created attachment 1455
Patch to make _spawnvp less bad

checks waitpid() return value, does not magically put the caller into a new process. Does not properly handle EINTR.


Training ControlNet without a control

Hi,
I am trying to train ControlNet with my own data.
I use this great tutorial at blob/main/docs/train.md
My data has no spatial hint, but I still want to customize SD with my own image domain and corresponding prompts.
How can I do that?
Thanks!

Can you project your information onto an image? The pose format ultimately also wouldn't have to be an image but the projected onto an image and controlnet just "connects the dots".
I collect information about this topic here: https://civitai.com/articles/2078#heading-3617 -> Q: Is it possible to use non-image inputs for control nets?
See [Double Control] What model is most needed? and adding more "hint" to training process


[FLOC-4101] Add build number to github -> jenkins links.

https://clusterhq.atlassian.net/browse/FLOC-4101

Nice, thanks for this. Go ahead and merge.


Can Breakfast/Brunch co-exist with Sprockets?

I've recently been working with converting a project gradually from Sprockets to Webpacker, but I'm getting frustrated, and finding Webpack messy, counter-intuitive and full of weird, barely-documented "features".
So I'm trying Breakfast, and it seems promising, but I can't get it to work and Rails complains about app.css not being in the asset pipeline. Could it be that it's because I still have a few assets that are handled by Sprockets? Webpacker and Sprockets can happily co-exist, but since Breakfast uses the same stylesheet_link_tag, I'm starting to suspect this is not the case with Breakfast?
Sorry if this is obvious, but I can't find any mention of this in the docs.
(I think the fact that Breakfast's running as a sub-process of rails s and that it's using the same stylesheet and javascript tags for Rails views are strengths, but I can see if it makes co-existing with Sprockets difficult, and it would make converting my project step by step much harder, sadly.)

Hey, I've used both side by side and it worked out pretty well. What version of Rails are you running? Last time I tried this was an early 5.x or maybe a late 4.x version of Rails, and I suspect there's a few things I might need to patch up.

I'm on Rails 5.1.7. Could be that I'm the one doing something wrong. I'll do some more testing.
But, logically, with the same magic keyword (stylesheet_link_tag), wouldn't Sprockets give me an error message regardless? I suspect I'm not even reaching Breakfast because Sprockets fails looking for app.css.
Inversely, how would I even use the Sprockets' application.css?


[URGENT] QR CODE not generating

Hi,
we are unable to generate the QR code - we have tried with fresh installation also and having the same - it keep saying the status " "status": "INITIALIZING","
here is the response

I have the issue, I have tried to delete all the cache, but no luck.

Hi,
I had the same issue with generating the QR code and getting the status "status": "INITIALIZING". I resolved it by updating to the latest version (v2.8.1). I recommend updating your wppconnect-server installation to the latest version, as this fixed the problem for me.
Hope this helps!
Best,
Amir

you must update the project and install the Chrome browser.
note: you may need to change your WhatsApp web version to the latest one.

@renat473 @amir200xven  thanks - it fixed it after i upgraded, but we cant create group - are you also having the same issue?
here is the logs -

Hello sir @renat473 @syahir10syahir can you tell me how to update whatsapp web and install the chrome browser?
im use the docker  like this :
`# FROM node:18-alpine3.19 as base
FROM node:18-alpine as base
WORKDIR /usr/src/wpp-server
ENV NODE_ENV=production PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
COPY package.json ./
RUN apk update &&
apk add --no-cache
vips-dev
fftw-dev
gcc
g++
make
libc6-compat
&& rm -rf /var/cache/apk/*
RUN yarn install --production --pure-lockfile &&
yarn add sharp --ignore-engines &&
yarn cache clean
FROM base as build
WORKDIR /usr/src/wpp-server
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
COPY package.json  ./
RUN yarn install --production=false --pure-lockfile
RUN yarn cache clean
COPY . .
RUN yarn build
FROM base
RUN apk update &&
apk add --no-cache
vips-dev
fftw-dev
gcc
g++
make
libc6-compat
&& rm -rf /var/cache/apk/*
WORKDIR /usr/src/wpp-server/
RUN apk add --no-cache chromium
RUN yarn cache clean
COPY . .
COPY --from=build /usr/src/wpp-server/ /usr/src/wpp-server/
EXPOSE 21465
ENTRYPOINT ["node", "dist/server.js"]
`
and docker-compose like this :
version: "3"
services:
wppconnect:
build:
context: .
volumes:
- ./config.ts:/usr/src/wpp-server/config.ts
- ./wppconnect_tokens:/usr/src/wpp-server/tokens
ports:
- "21465:21465"
volumes:
wppconnect_tokens: {}
please help me


Android Support: Push Notifications

What problem does this solve or what need does it fill?
My game use network communications to bring new data, and I want to use push notifications with Bevy app. How to do this?
What solution would you like?
Any tips, example, or something else about current support of pushes.
Additional context
I am new to Bevy ecosystem, but I didn't get how to use pushes.

If you are looking for pre-existing code for cross-platform notification support in Rust, searching the web gives gives me rust-notifica. Unfortunately, it only implements for Mac, Windows, and Linux.
For Android, it's probably that you have to use the official Android API. Read more about that here, which you can call through Java Native Interface (in Rust use jni crate).


Feature Request: Index all the things!

First, I'd like to say that this whole suite of tools is amazing work. Thank you.
This might be another module or it might integrate nicely into this one, but while this does fantastically with tile sets, it would be great to have this search functionality for non-tile images like token art, etc., that is less structured (likely in a single folder) - basically just the random art that people pull in during the course of play.
Also, there are quite a few sets of structured assets living in the Foundry core and many game systems (D&D 5e and Pathfinder 2 both have extensive icon sets). Having these indexed and easily searchable would also be handy. This might be doable just by allowing more than a single path to be entered for the assets custom path (or having a nice UI that allows selecting folders to index).

When dropping an image in as a token you can select which actor it represents. Is it possible to only direct where it looks for an actor to a specific folder(s) and a default grid/image size for dropped in tokens ?


Unable to run test on Apple Silicon Mac - Simulator Build Fails on simulator iPhone 15 Pro Max iOS 17.5

Steps to reproduce

Build project on an Apple Silicon Mac.
Attempt to run tests on an iPhone 15 Pro Max simulator running iOS 17.5.
Observe the test failures.
Additionally, run tests on an iPhone 15 simulator running iOS 17.5 and note the errors at the end even tho all test passes

Actual results
We are encountering issues when running tests on an Apple Silicon Mac iOS simulators.
Specifically:

On an Intel Mac, all tests run successfully.
On an Apple Silicon Mac:
-     Tests fail to build on an iPhone 15 Pro Max simulator running iOS 17.5.
-     Tests on an iPhone 15 simulator running iOS 17.5 complete but end with errors even tho all test passes.
This issue seems to be exclusive to Apple Silicon Macs, as the Intel Mac does not exhibit these problems as observed.

Logs

Logs
• Running app with entrypoint test_bundle.dart for iOS simulator on simulator iPhone 15 Pro Max...
$ xcodebuild -showsdks -json
Assuming SDK version 17.5 for iphonesimulator
Looking for .xctestrun matching mobile_*iphonesimulator17.5*.xctestrun at /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_integ/Build/Products
Found 1 match(es), the first one will be used
Found /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_integ/Build/Products/mobile_PatrolTestPlan_iphonesimulator17.5-arm64-x86_64.xctestrun
$ xcodebuild test-without-building -xctestrun /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_integ/Build/Products/mobile_PatrolTestPlan_iphonesimulator17.5-arm64-x86_64.xctestrun -only-testing RunnerUITests/RunnerUITests -destination platform=iOS Simulator,name=iPhone 15 Pro Max -destination-timeout 1 -resultBundlePath /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_results_1720590073836.xcresult
        Command line invocation:
            /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild test-without-building -xctestrun /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_integ/Build/Products/mobile_PatrolTestPlan_iphonesimulator17.5-arm64-x86_64.xctestrun -only-testing RunnerUITests/RunnerUITests -destination "platform=iOS Simulator,name=iPhone 15 Pro Max" -destination-timeout 1 -resultBundlePath /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_results_1720590073836.xcresult

        User defaults from command line:
            IDEBuildOperationResultBundlePath = /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_results_1720590073836.xcresult
            IDEPackageSupportUseBuiltinSCM = YES

        Writing result bundle at path:
                /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_results_1720590073836.xcresult

        --- xcodebuild: WARNING: Using the first of multiple matching destinations:
        { platform:macOS, arch:arm64e, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:arm64, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:x86_64, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:arm64e, variant:Mac Catalyst, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:arm64, variant:Mac Catalyst, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:x86_64, variant:Mac Catalyst, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:arm64e, variant:DriverKit, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:arm64, variant:DriverKit, id:00006000-000A08EA0251801E, name:My Mac }
        { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00006000-000A08EA0251801E, name:My Mac }
        { platform:iOS, arch:arm64e, id:00008130-00092D993ED2001C, name:Bashcious’s iPhone }
        { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
        { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
        { platform:macOS, name:Any Mac }
        { platform:macOS, variant:Mac Catalyst, name:Any Mac }
        { platform:tvOS, id:dvtdevice-DVTiOSDevicePlaceholder-appletvos:placeholder, name:Any tvOS Device }
        { platform:tvOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-appletvsimulator:placeholder, name:Any tvOS Simulator Device }
        { platform:visionOS, id:dvtdevice-DVTiOSDevicePlaceholder-xros:placeholder, name:Any visionOS Device }
        { platform:visionOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-xrsimulator:placeholder, name:Any visionOS Simulator Device }
        { platform:watchOS, id:dvtdevice-DVTiOSDevicePlaceholder-watchos:placeholder, name:Any watchOS Device }
        { platform:watchOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-watchsimulator:placeholder, name:Any watchOS Simulator Device }
        { platform:iOS Simulator, id:1501AEA9-B069-4AFC-822F-52AF29F834A5, OS:16.2, name:iPad (10th generation) }
        { platform:iOS Simulator, id:1501AEA9-B069-4AFC-822F-52AF29F834A5, OS:16.2, name:iPad (10th generation) }
        { platform:iOS Simulator, id:1F8C85C9-D264-4062-BD72-3570BF4584DE, OS:17.0.1, name:iPad (10th generation) }
        { platform:iOS Simulator, id:1F8C85C9-D264-4062-BD72-3570BF4584DE, OS:17.0.1, name:iPad (10th generation) }
        { platform:iOS Simulator, id:C284263A-0F5A-400F-8809-76EFD98EC8B0, OS:17.2, name:iPad (10th generation) }
        { platform:iOS Simulator, id:C284263A-0F5A-400F-8809-76EFD98EC8B0, OS:17.2, name:iPad (10th generation) }
        { platform:iOS Simulator, id:A0FE1131-8E79-426D-AF08-DE4164650343, OS:17.4, name:iPad (10th generation) }
        { platform:iOS Simulator, id:A0FE1131-8E79-426D-AF08-DE4164650343, OS:17.4, name:iPad (10th generation) }
        { platform:iOS Simulator, id:DAA4D7B6-C43C-45DB-B219-DFBECB56FCEF, OS:17.5, name:iPad (10th generation) }
        { platform:iOS Simulator, id:DAA4D7B6-C43C-45DB-B219-DFBECB56FCEF, OS:17.5, name:iPad (10th generation) }
        { platform:iOS Simulator, id:52EFE559-CF84-4B09-98CB-30B4DD1B75D5, OS:16.2, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:52EFE559-CF84-4B09-98CB-30B4DD1B75D5, OS:16.2, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:87DE896F-D426-4495-B763-B8CE8DCA3B43, OS:17.0.1, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:87DE896F-D426-4495-B763-B8CE8DCA3B43, OS:17.0.1, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:E2ECE220-D15E-4FF7-A160-839EDD522B5A, OS:17.2, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:E2ECE220-D15E-4FF7-A160-839EDD522B5A, OS:17.2, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:52239E87-0581-4D13-9A0B-2C963A83765C, OS:17.4, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:52239E87-0581-4D13-9A0B-2C963A83765C, OS:17.4, name:iPad Air (5th generation) }
        { platform:iOS Simulator, id:FC0EDEE9-4C29-4234-8119-E9B54761BC05, OS:17.4, name:iPad Air 11-inch (M2) }
        { platform:iOS Simulator, id:FC0EDEE9-4C29-4234-8119-E9B54761BC05, OS:17.4, name:iPad Air 11-inch (M2) }
        { platform:iOS Simulator, id:A42104AE-AD74-48E2-977B-D7E4BD7C11AE, OS:17.5, name:iPad Air 11-inch (M2) }
        { platform:iOS Simulator, id:A42104AE-AD74-48E2-977B-D7E4BD7C11AE, OS:17.5, name:iPad Air 11-inch (M2) }
        { platform:iOS Simulator, id:CDE27CF4-10E3-4549-8500-D3438C6B9C44, OS:17.4, name:iPad Air 13-inch (M2) }
        { platform:iOS Simulator, id:CDE27CF4-10E3-4549-8500-D3438C6B9C44, OS:17.4, name:iPad Air 13-inch (M2) }
        { platform:iOS Simulator, id:A4B80856-AD82-4413-9A01-55C9504C4F36, OS:17.5, name:iPad Air 13-inch (M2) }
        { platform:iOS Simulator, id:A4B80856-AD82-4413-9A01-55C9504C4F36, OS:17.5, name:iPad Air 13-inch (M2) }
        { platform:iOS Simulator, id:1A4AEC21-920D-44B7-9B7F-5D674E8009CF, OS:16.2, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:1A4AEC21-920D-44B7-9B7F-5D674E8009CF, OS:16.2, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:5328B520-6937-43DE-AB18-79C78D78B23A, OS:17.0.1, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:5328B520-6937-43DE-AB18-79C78D78B23A, OS:17.0.1, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:A72F0C01-9205-4C72-BA43-946ABEF129A0, OS:17.2, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:A72F0C01-9205-4C72-BA43-946ABEF129A0, OS:17.2, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:2A255AA0-7B34-4D7A-B1B1-8F642FF09E90, OS:17.4, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:2A255AA0-7B34-4D7A-B1B1-8F642FF09E90, OS:17.4, name:iPad Pro (11-inch) (4th generation) }
        { platform:iOS Simulator, id:CA68C577-3356-4230-AF11-0F55982E4FC3, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:CA68C577-3356-4230-AF11-0F55982E4FC3, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:2C6F9ED9-EE0D-4E5E-B3D4-56BCE2FA39AF, OS:17.0.1, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:2C6F9ED9-EE0D-4E5E-B3D4-56BCE2FA39AF, OS:17.0.1, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:774B9286-6CDE-4202-B827-F9F01192F675, OS:17.2, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:774B9286-6CDE-4202-B827-F9F01192F675, OS:17.2, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:C9CEEBFB-27B8-48E6-AC88-6544A97184DD, OS:17.4, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:C9CEEBFB-27B8-48E6-AC88-6544A97184DD, OS:17.4, name:iPad Pro (12.9-inch) (6th generation) }
        { platform:iOS Simulator, id:4BD58500-623C-49C6-B224-D8149FDC546B, OS:17.4, name:iPad Pro 11-inch (M4) }
        { platform:iOS Simulator, id:4BD58500-623C-49C6-B224-D8149FDC546B, OS:17.4, name:iPad Pro 11-inch (M4) }
        { platform:iOS Simulator, id:0A51D065-04B7-40DB-A880-0E850C715925, OS:17.5, name:iPad Pro 11-inch (M4) }
        { platform:iOS Simulator, id:0A51D065-04B7-40DB-A880-0E850C715925, OS:17.5, name:iPad Pro 11-inch (M4) }
        { platform:iOS Simulator, id:CFD34336-F859-490B-AFB3-B2569E693C5E, OS:17.4, name:iPad Pro 13-inch (M4) }
        { platform:iOS Simulator, id:CFD34336-F859-490B-AFB3-B2569E693C5E, OS:17.4, name:iPad Pro 13-inch (M4) }
        { platform:iOS Simulator, id:4D65FDF8-95D9-4407-8D3A-84EEB72C45D4, OS:17.5, name:iPad Pro 13-inch (M4) }
        { platform:iOS Simulator, id:4D65FDF8-95D9-4407-8D3A-84EEB72C45D4, OS:17.5, name:iPad Pro 13-inch (M4) }
        { platform:iOS Simulator, id:7967926D-A748-46ED-89B4-0337646238A1, OS:16.2, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:7967926D-A748-46ED-89B4-0337646238A1, OS:16.2, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:DBF24E9E-CF03-4B30-9612-9CEFC3CE8160, OS:17.0.1, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:DBF24E9E-CF03-4B30-9612-9CEFC3CE8160, OS:17.0.1, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:D6F1464A-38BA-4767-AC48-597314CC75AF, OS:17.2, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:D6F1464A-38BA-4767-AC48-597314CC75AF, OS:17.2, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:A24696C7-E91E-447F-9BF7-170E29BC2E81, OS:17.4, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:A24696C7-E91E-447F-9BF7-170E29BC2E81, OS:17.4, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:53B22F98-A3BA-408C-9AB0-01DFDEB22952, OS:17.5, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:53B22F98-A3BA-408C-9AB0-01DFDEB22952, OS:17.5, name:iPad mini (6th generation) }
        { platform:iOS Simulator, id:8E013BFE-6CA9-4B7F-8068-193422E8CEB0, OS:16.2, name:iPhone 14 }
        { platform:iOS Simulator, id:8E013BFE-6CA9-4B7F-8068-193422E8CEB0, OS:16.2, name:iPhone 14 }
        { platform:iOS Simulator, id:DE8AF112-0C92-4BA7-801C-C1BC35D35E4D, OS:16.2, name:iPhone 14 Plus }
        { platform:iOS Simulator, id:DE8AF112-0C92-4BA7-801C-C1BC35D35E4D, OS:16.2, name:iPhone 14 Plus }
        { platform:iOS Simulator, id:B6603999-25C6-4B49-8C2E-4D047D4956EA, OS:16.2, name:iPhone 14 Pro }
        { platform:iOS Simulator, id:B6603999-25C6-4B49-8C2E-4D047D4956EA, OS:16.2, name:iPhone 14 Pro }
        { platform:iOS Simulator, id:5173DFFA-8490-49D7-B9C1-AB1A6C1E82B2, OS:16.2, name:iPhone 14 Pro Max }
        { platform:iOS Simulator, id:5173DFFA-8490-49D7-B9C1-AB1A6C1E82B2, OS:16.2, name:iPhone 14 Pro Max }
        { platform:iOS Simulator, id:85736EFC-248A-4904-9A99-9ED87234A411, OS:16.2, name:iPhone 14 Pro Max }
        { platform:iOS Simulator, id:85736EFC-248A-4904-9A99-9ED87234A411, OS:16.2, name:iPhone 14 Pro Max }
        { platform:iOS Simulator, id:ABA9422A-1123-44CB-9201-72F6BB4D78C7, OS:17.2, name:iPhone 14 Pro Max }
        { platform:iOS Simulator, id:ABA9422A-1123-44CB-9201-72F6BB4D78C7, OS:17.2, name:iPhone 14 Pro Max }
        { platform:iOS Simulator, id:E5D13C55-3746-4221-BA75-CD65EDB8243D, OS:17.0.1, name:iPhone 15 }
        { platform:iOS Simulator, id:E5D13C55-3746-4221-BA75-CD65EDB8243D, OS:17.0.1, name:iPhone 15 }
        { platform:iOS Simulator, id:2FE1C928-AA1F-4847-A3E4-227F76E2CB29, OS:17.2, name:iPhone 15 }
        { platform:iOS Simulator, id:2FE1C928-AA1F-4847-A3E4-227F76E2CB29, OS:17.2, name:iPhone 15 }
        { platform:iOS Simulator, id:F5668F4A-BFB0-45F3-BC4C-D77BE8E74F1D, OS:17.4, name:iPhone 15 }
        { platform:iOS Simulator, id:F5668F4A-BFB0-45F3-BC4C-D77BE8E74F1D, OS:17.4, name:iPhone 15 }
        { platform:iOS Simulator, id:1FE73FD3-4556-412B-B7DF-E923A898368E, OS:17.5, name:iPhone 15 }
        { platform:iOS Simulator, id:1FE73FD3-4556-412B-B7DF-E923A898368E, OS:17.5, name:iPhone 15 }
        { platform:iOS Simulator, id:9B54D9AC-9FA8-4809-A447-CF47ED2A696B, OS:17.0.1, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:9B54D9AC-9FA8-4809-A447-CF47ED2A696B, OS:17.0.1, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:A6A27602-6864-4924-89D2-9B53A2A00E7B, OS:17.2, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:A6A27602-6864-4924-89D2-9B53A2A00E7B, OS:17.2, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:6E7E659B-4C4E-4C99-B3AD-0AEF921963FF, OS:17.4, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:6E7E659B-4C4E-4C99-B3AD-0AEF921963FF, OS:17.4, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:49D293E9-118F-4B2B-B54E-B6B0674A93C4, OS:17.5, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:49D293E9-118F-4B2B-B54E-B6B0674A93C4, OS:17.5, name:iPhone 15 Plus }
        { platform:iOS Simulator, id:24D918CD-61C4-4252-AF5F-6E8523CB522D, OS:17.0.1, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:24D918CD-61C4-4252-AF5F-6E8523CB522D, OS:17.0.1, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:CD90A69C-2A38-4E7D-B419-C4D5A451BD8F, OS:17.2, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:CD90A69C-2A38-4E7D-B419-C4D5A451BD8F, OS:17.2, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:1E730749-2037-444B-8B52-E4B5787FF74C, OS:17.4, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:1E730749-2037-444B-8B52-E4B5787FF74C, OS:17.4, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:3E2039CF-B43D-4120-AB38-977361AD3E7B, OS:17.5, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:3E2039CF-B43D-4120-AB38-977361AD3E7B, OS:17.5, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:35E0C381-D42C-4AEF-97D6-CE0C66018EE1, OS:17.0.1, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:35E0C381-D42C-4AEF-97D6-CE0C66018EE1, OS:17.0.1, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:4A4A94A1-E18A-42C7-9F76-555FC1DFC098, OS:17.0.1, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:4A4A94A1-E18A-42C7-9F76-555FC1DFC098, OS:17.0.1, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:3C6FD29F-C883-4CE1-935B-61AAFA21A4B2, OS:17.2, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:3C6FD29F-C883-4CE1-935B-61AAFA21A4B2, OS:17.2, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:850AD8E8-56D8-48F5-88C5-4043381C5EBA, OS:17.4, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:850AD8E8-56D8-48F5-88C5-4043381C5EBA, OS:17.4, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:2A8B8B06-2B1E-490E-BCAB-0DA176EAB48F, OS:17.5, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:2A8B8B06-2B1E-490E-BCAB-0DA176EAB48F, OS:17.5, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:5DCBAA3C-D1D8-4A42-9600-947D5DD5F91C, OS:17.5, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:5DCBAA3C-D1D8-4A42-9600-947D5DD5F91C, OS:17.5, name:iPhone 15 Pro Max }
        { platform:iOS Simulator, id:AB15EE0E-FA08-4772-B9E0-3E6AD315272B, OS:16.2, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:AB15EE0E-FA08-4772-B9E0-3E6AD315272B, OS:16.2, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:1D9DB2AE-DA10-4C29-92AF-CB65DA2DDD14, OS:17.0.1, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:1D9DB2AE-DA10-4C29-92AF-CB65DA2DDD14, OS:17.0.1, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:CBF6730F-3D88-40B7-8FE9-7A1A7BDD3E84, OS:17.2, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:CBF6730F-3D88-40B7-8FE9-7A1A7BDD3E84, OS:17.2, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:32D1F5AB-2BC0-472B-9D27-0AA180866A08, OS:17.4, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:32D1F5AB-2BC0-472B-9D27-0AA180866A08, OS:17.4, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:B22C1FB6-22F0-4AA4-8165-52D0B8E351A0, OS:17.5, name:iPhone SE (3rd generation) }
        { platform:iOS Simulator, id:B22C1FB6-22F0-4AA4-8165-52D0B8E351A0, OS:17.5, name:iPhone SE (3rd generation) }
        2024-07-10 13:41:15.616 xcodebuild[4926:587190]  IDELaunchReport: b6006162cfeb520:b6006162cfeb520: Finished with error: Could not launch “RunnerUITests”
        Domain: IDELaunchErrorDomain
        Code: 20
        Recovery Suggestion: LaunchServices has returned error -10661. Please check the system logs for the underlying cause of the error.
        User Info: {
            DVTRadarComponentKey = 113722;
            IDERunOperationFailingWorker = IDELaunchServicesLauncher;
        }
        --
        The operation couldn’t be completed. (OSStatus error -10661.)
        Domain: NSOSStatusErrorDomain
        Code: -10661
        User Info: {
            "_LSFunction" = "_LSOpenStuffCallLocal";
            "_LSLine" = 4129;
        }
        --
        2024-07-10 13:41:15.616 xcodebuild[4926:587190]  IDELaunchReport: b6006162cfeb520:b6006162cfeb520: com.apple.dt.IDERunOperationWorkerFinished {
            "device_model" = "MacBookPro18,1";
            "device_osBuild" = "14.5 (23F79)";
            "device_platform" = "com.apple.platform.macosx";
            "dvt_coredevice_version" = "355.28";
            "dvt_mobiledevice_version" = "1643.120.2";
            "launchSession_schemeCommand" = Test;
            "launchSession_state" = 1;
            "launchSession_targetArch" = arm64e;
            "operation_duration_ms" = 21;
            "operation_errorCode" = 20;
            "operation_errorDomain" = IDELaunchErrorDomain;
            "operation_errorWorker" = IDELaunchServicesLauncher;
            "operation_name" = IDERunOperationWorkerGroup;
            "param_debugger_attachToExtensions" = 0;
            "param_debugger_attachToXPC" = 0;
            "param_debugger_type" = 1;
            "param_destination_isProxy" = 0;
            "param_destination_platform" = "com.apple.platform.macosx";
            "param_diag_MainThreadChecker_stopOnIssue" = 0;
            "param_diag_MallocStackLogging_enableDuringAttach" = 0;
            "param_diag_MallocStackLogging_enableForXPC" = 0;
            "param_diag_allowLocationSimulation" = 1;
            "param_diag_checker_tpc_enable" = 0;
            "param_diag_gpu_frameCapture_enable" = 3;
            "param_diag_gpu_shaderValidation_enable" = 0;
            "param_diag_gpu_validation_enable" = 1;
            "param_diag_memoryGraphOnResourceException" = 0;
            "param_diag_queueDebugging_enable" = 1;
            "param_diag_runtimeProfile_generate" = 1;
            "param_diag_sanitizer_asan_enable" = 0;
            "param_diag_sanitizer_tsan_enable" = 0;
            "param_diag_sanitizer_tsan_stopOnIssue" = 0;
            "param_diag_sanitizer_ubsan_stopOnIssue" = 0;
            "param_diag_showNonLocalizedStrings" = 0;
            "param_diag_viewDebugging_enabled" = 0;
            "param_diag_viewDebugging_insertDylibOnLaunch" = 0;
            "param_install_style" = 2;
            "param_launcher_UID" = 2;
            "param_launcher_allowDeviceSensorReplayData" = 0;
            "param_launcher_kind" = 0;
            "param_launcher_style" = 0;
            "param_launcher_substyle" = 8192;
            "param_runnable_appExtensionHostRunMode" = 0;
            "param_runnable_productType" = "com.apple.product-type.application";
            "param_structuredConsoleMode" = 0;
            "param_testing_launchedForTesting" = 1;
            "param_testing_suppressSimulatorApp" = 1;
            "param_testing_usingCLI" = 0;
            "sdk_canonicalName" = "macosx14.5";
            "sdk_osVersion" = "14.5";
            "sdk_variant" = macos;
        }

        *** If you believe this error represents a bug, please attach the result bundle at /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_results_1720590073836.xcresult

        2024-07-10 13:41:19.753 xcodebuild[4926:587129] [MT] IDETestOperationsObserverDebug: 4.543 elapsed -- Testing started completed.
        2024-07-10 13:41:19.753 xcodebuild[4926:587129] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
        2024-07-10 13:41:19.753 xcodebuild[4926:587129] [MT] IDETestOperationsObserverDebug: 4.543 sec, +4.543 sec -- end

        Test session results, code coverage, and logs:
                /Users/bashir.isyaka/Desktop/Workspace/mobile/flutter/build/ios_results_1720590073836.xcresult

        Testing failed:
                Could not launch “RunnerUITests”
                RunnerUITests-Runner encountered an error (Failed to install or launch the test runner. (Underlying Error: Could not launch “RunnerUITests”. LaunchServices has returned error -10661. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. (OSStatus error -10661.))))

        ** TEST EXECUTE FAILED **

        Testing started
✗ Failed to execute tests of app with entrypoint test_bundle.dart for iOS simulator on simulator iPhone 15 Pro Max (xcodebuild exited with code 65) (8.9s)
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.execute.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:198:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.execute (package:patrol_cli/src/ios/ios_test_backend.dart:153:5)
<asynchronous suspension>
#4      TestCommand._execute (package:patrol_cli/src/commands/test.dart:336:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:228:23)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:348:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:292:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#10     main (file:///Users/bashir.isyaka/.pub-cache/hosted/pub.dev/patrol_cli-2.8.1/bin/main.dart:6:20)
<asynchronous suspension>

Patrol version
patrol: 3.9.0
Patrol Doctor output

Patrol Doctor output
Patrol doctor:
Patrol CLI version: 2.8.1
Flutter command: flutter
  Flutter 3.22.2 • channel stable
Android:
• Program adb found in /Users/bashir.isyaka/Library/Android/sdk/platform-tools/adb
• Env var $ANDROID_HOME set to /Users/bashir.isyaka/Library/Android/sdk
iOS / macOS:
• Program xcodebuild found in /usr/bin/xcodebuild
• Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc4)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.91.0)
[✓] Connected device (5 available)
[✓] Network resources

• No issues found!

Hi @bash-bigpay
It seems that the problem lies within your local enviroment - I was not able to reproduce it (I ran tests from this repository example app on the setup you mentioned without any problems). If you do not manage to fix it yourself feel free to reach out to community on Patrol Discord server. Maybe someone who had similar problem will be able to help you.


8.3.4 fails to build for edge deployment

8.3.4 fails to build for edge deployment.
The recent update from 8.3.3 to 8.3.4 causes issues in edge environments. Using Astro to build a project for Cloudflare Workers I get this error with 8.3.4:
✘ [ERROR] Could not resolve "crypto"

    node_modules/.pnpm/@simplewebauthn+server@8.3.4/node_modules/@simplewebauthn/server/esm/helpers/iso/isoCrypto/getWebCrypto.js:45:43:
      45 │     stubThisImportNodeCrypto: () => import('crypto'),
         ╵                                            ~~~~~~~~

  The package "crypto" wasn't found on the file system but is built into node. Are you trying to
  bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

 error   Could not resolve "crypto"
  File:
    node_modules/.pnpm/@simplewebauthn+server@8.3.4/node_modules/@simplewebauthn/server/esm/helpers/iso/isoCrypto/getWebCrypto.js:45:43
  Code:
    44 |     // dnt-shim-ignore
    > 45 |     stubThisImportNodeCrypto: () => import('crypto'),
         |                                           ^
      46 |     stubThisGlobalThisCrypto: () => globalThis.crypto,
      47 |     // Make it possible to reset the `webCrypto` at the top of the file
      48 |     setCachedCrypto: (newCrypto) => {

node: imports are not available on edge deployments like Cloudflare Workers (Pages), Deno Deploy, and the evil triangle.
Reproduction Steps
Deploy any sample application to an edge environment. Or build a sample project with Astro and @astrojs/cloudflare.
Expected behavior
The node crypto import should be allowed to fail without a program exit and fall back on globalThis. The specific line in the error, "import('crypto')" is asynchronous and throws if it fails to import. I can get a successful local build by just catching it and doing nothing.
import('crypto').catch(error => { /* idk, just don't fail my build! */ }),

SimpleWebAuthn Libraries
    "@simplewebauthn/browser": "^8.3.4",
    "@simplewebauthn/server": "^8.3.4",
    "@simplewebauthn/typescript-types": "^8.3.4",

Reproduction Steps
Deploy any sample application to an edge environment. Or build a sample project with Astro and @astrojs/cloudflare.

Hello @eglove, I appreciate your following the issue template but you need to give me a clearer picture of what type of project and runtime you're targeting if I'm going to have confidence that I've solved the problem when I work out a solution. "Any sample application" and "an edge environment" are too vague. A basic reproduction will speed up resolution time too.

I figured the error was obvious enough. I think your previous flow of trying the import first was the right way to go.
I don't really have time for a PR this weekend. But that is the most brilliantly clear error message one could ever get. I'd say bravo to Astro for exposing that.

This should be fixed in<EMAIL_ADDRESS>


[Bug]: “—Select—” should have placeholder color

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When we focus on the select component of the Merge tab in the Git modal, the —Select— text appears in bold. It should be a placeholder instead.
Steps To Reproduce
Details are https://www.notion.so/appsmith/Select-should-be-a-placeholder-845c2a569fbf43b5ae45aa01ec6866ae
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud- latest

This has been verified in https://github.com/appsmithorg/appsmith/pull/24012


Update GDNative API version for changes from #50659

Per @Faless, PR #50659 should have updated the GDNative API version defines. This is a quick follow-up to do that!

Thanks!


Support "image/vnd.jpeg-png" format (GeoServer's "smart transparency" for WMS)

It recently came to my attention that (the in-development version of) GeoServer supports a new image/vnd.jpeg-png format to provide "smart transparency" for WMS requests.
Here are some links to explain what I'm talking about:
http://www.geo-solutions.it/blog/geoserver-smart-transparency/
http://docs.geoserver.org/stable/en/user/services/wms/outputformats.html
https://github.com/geoserver/geoserver/commit/ba41769ec67202e18c7aabdeb685c69786508177
While MapProxy currently supports this smart transparency functionality when serving tiles, it would be nice to take advantage of it when fetching data from a remote WMS server that natively supports it.
What do you think?

Added in https://github.com/mapproxy/mapproxy/pull/456


phone-number: add missing edge cases

The phone-number schema was updated to add a new test case.

The existing descriptions for invalid area codes and exchange codes both cite a range, but only test a single value. This PR tests for all values outside the valid range.

Closing due to a similar issue exists and has a wider scope to incorporate changes #92


Switch from arch(1) to "uname -m"

See (multiple) occurrences of arch in:

https://github.com/kata-containers/osbuilder/blob/master/rootfs-builder/rootfs.sh

See also:

https://github.com/kata-containers/tests/pull/607

... and as part of this change, we can then drop the horrible arch hack here:

https://github.com/kata-containers/osbuilder/blob/master/rootfs-builder/alpine/Dockerfile.in#L10

Well, anyone could have jumped in to make this simple fix, but I have now done that on #227 :smile:

When will this get merged?  I have some instructions that use OS Builder and would like to remove my notes to manually edit the script file.   I just pulled the repo and this fix is not there yet.

@eadamsintel - I've re-run the CI (which is been a little volatile recently). That's all now passing so we simply need one more ack to get this landed...

tis done


HTML:a with data method POST enabled inside ActiveForm submit's wrapping form

Here is problematic code
https://gist.github.com/anonymous/b5adea698d297d8cc8ca
The same code was working on another project. (Maybe problem occurred because of update). The problem is HTML:a with data method POST inside ActiveForm submits wrapping form. After moving tis part out of wrapping form all works.
https://gist.github.com/anonymous/daa2d3bba0ea0f0fe8e6
Question is, why a submits wrapping form?

Duplicates #8161


Deduction of LeP after damage roll (Chat)

Describe the bug
When you request damage rolls from the players via Journal, the roll works fine. But the option to automatically assign the damage doesn't work.
To Reproduce
Open journal entry as GM.
Send a roll request to the chat (i.e. damage roll on the first bridge, pinned journal entry)
Click on the chat entry to roll damage
Right-click on the damage, select to deduct the damage from health.
Tested options, same behaviour

as GM and as player
with and without selecting a token
with and without declaring a token as target
with and without activating a battle

Expected behavior
deduct the damage from health, either from selected or targeted token

This is not a damage roll. It is just a normal inline roll, which can appear in any circumstance. F.e. for a random roll for amount of silver to loot.
There is no option planned or intended to add this automatically or replace this with a damage roll (or at leaset with priority close to zero).
Click on the token on the map to edit the healtbars in place.
Updating the health bar is only intended for opposed combat rolls (more specifically for the results chat card)


model parameter appears to be ignored

I was trying to get the model parameter working for me, as I do not have access to GPT 4. It appears like the model parameter is ignored, however:

test('Test Google using GPT', async({ page }) => {
  await page.goto('https://www.google.com/');
  await auto('Search for "something else"', { page, test }, {model: 'gpt-3.5-turbo-1106', debug: true});
});

Maybe it might be good to log the model parameter if debugging is turned on?

@tntexplosivesltd Just a heads up that this repo was cloned from a project called ZeroStep (https://github.com/zerostep-ai/zerostep) without attribution, and much of the text in the README and initial blog post was plagiarized from the ZeroStep project homepage (https://zerostep.com/). I wrote a blog post with proof of what I'm claiming: https://zerostep.com/blog/launch-on-thursday-cloned-by-saturday/


duplicate value for resource attr/itemBackground with config ''

-I have added this library to my android project and everything was working fine until I added design support library ( 'com.android.support:design:27.1.1'), after adding this my gradle build failed with following error
Caused by: org.gradle.internal.UncheckedException: java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource compilation failed MyAppDirectory\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values\values.xml:2489: error: duplicate value for resource 'attr/itemBackground' with config ''.
and when I remove the design support library dependency then everything becomes fine.
Complete problem description : https://stackoverflow.com/questions/51709716/android-resource-compilation-failed

Most likely this is caused by this new attribute:

Looks like the same attribute already exists in the latest support library.
Renaming it should solve the issue.

@markspit93 Indeed, after doing some research, I found that MenuView (The Menu in the Toolbar) has defined this attribute.
<declare-styleable name="MenuView">
    ...
    <!-- Default background for each menu item. -->
    <attr name="itemBackground" format="color|reference" />
    ...
</declare-styleable>

Therefore, in order to fix this issue, I will use <attr name="android:itemBackground" /> instead of
<attr name="itemBackground" format="reference|color" />.

@mdadil2019 Please upgrade to 1.4.1.


connectionTimeZone is not respected

Describe the bug
Hello Team,
I've encountered an issue with the AWS Advanced JDBC Wrapper where it seems to not respect the connectionTimeZone parameter in the connection string.
I'm using the AWS Advanced JDBC Wrapper to connect to a MySQL Aurora database. Here's the connection string I'm using:
jdbc:aws-wrapper:mysql://${endpointName}:3306/" +                         "${schemaName}?connectionTimeZone=UTC&preserveInstants=true&rewriteBatchedStatements=true
MySQL aurora server timezone is UTC, and JVM user.timezone is Europe/Amsterdam, I've set connectionTimeZone to UTC, but the timestamps are being converted to the local timezone when written to the database, and vice versa. As the result:

When I write the UTC timestamp 2022-03-27T01:00:00Z to the database, it gets stored as 2022-03-27T03:00:00Z (timestamp)
And when i read timestamp back from db, it shift two hour back to 2022-03-27T01:00:00Z

In addition, The following exception occurs when reading existing timestamp like 2022-03-27 02:00:00 from db due to DST transition.
(bg thread: 57): Transaction attempt #0 failed: HOUR_OF_DAY: 2 -> 3. Statement(s): null
java.sql.SQLException: HOUR_OF_DAY: 2 -> 3
  com.mysql.cj.jdbc.exceptions.SQLError.createSQLException:130
  com.mysql.cj.jdbc.exceptions.SQLError.createSQLException:98
  com.mysql.cj.jdbc.exceptions.SQLError.createSQLException:90
  com.mysql.cj.jdbc.exceptions.SQLError.createSQLException:64
  com.mysql.cj.jdbc.exceptions.SQLError.createSQLException:74
  com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException:85
  com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp:943
  software.amazon.jdbc.wrapper.ResultSetWrapper.lambda$getTimestamp$77:984
  software.amazon.jdbc.plugin.DefaultConnectionPlugin.execute:130
  software.amazon.jdbc.ConnectionPluginManager.lambda$execute$5:334
  software.amazon.jdbc.ConnectionPluginManager.lambda$null$0:263
  software.amazon.jdbc.ConnectionPluginManager.executeWithTelemetry:240
  software.amazon.jdbc.ConnectionPluginManager.lambda$makePluginChainFunc$1:263
  software.amazon.jdbc.ConnectionPluginManager.executeWithSubscribedPlugins:230
  software.amazon.jdbc.ConnectionPluginManager.execute:331
  software.amazon.jdbc.util.WrapperUtils.executeWithPlugins:244
  software.amazon.jdbc.wrapper.ResultSetWrapper.getTimestamp:978
  com.zaxxer.hikari.pool.HikariProxyResultSet.getTimestamp:-1
  org.jetbrains.exposed.sql.javatime.JavaInstantColumnType.readObject:286
  org.jetbrains.exposed.sql.ResultRow$Companion.create:127
  org.jetbrains.exposed.sql.AbstractQuery$ResultIterator.next:88
  org.jetbrains.exposed.sql.AbstractQuery$ResultIterator.next:69

Expected Behavior
When the connectionTimeZone parameter is set to UTC, I expect the AWS Advanced JDBC Wrapper to handle all timestamp conversions in UTC when interacting with the database.
if I write a UTC timestamp like 2022-03-27T01:00:00Z to the database, it should be stored as 2022-03-27T01:00:00 (in UTC) in the database. When this timestamp is read back from the database, it should be returned as 2022-03-27T01:00:00Z (in UTC).
What plugins are used? What other connection properties were set?
plugin: iam; properties: connectionTimeZone=UTC&preserveInstants=true&rewriteBatchedStatements=true
Current Behavior
connectionTimeZone is not respected, the driver uses jvm timezone when interacting with db
Reproduction Steps

Set up an Aurora MySQL instance with the default server timezone set to UTC. Write a timestamp to a column (type: timestamp) with the value 2022-03-27 02:00:00 (equivalent unix timestamp:<PHONE_NUMBER>)

Query the aforementioned timestamp using the AWS Advanced JDBC Driver for MySQL. Ensure that this is executed in a JVM environment with the timezone set to Europe/Amsterdam (this can be done by setting the -Duser.timezone=Europe/Amsterdam JVM option).

An exception will be thrown. The exception message will contain: HOUR_OF_DAY: 2 -> 3, indicating an issue with the Daylight Saving Time transition.

Note: For other timestamp, the hour will be shift when write to db.
Data source setup:
 val hikariConfig = HikariConfig().apply {
            username = config.iamUser
            dataSourceClassName = AwsWrapperDataSource::class.java.name

            maximumPoolSize = config.maximumPoolSize
            minimumIdle = config.minimumIdle

            addDataSourceProperty(
                "jdbcUrl",
                "jdbc:aws-wrapper:mysql://${config.endpointName}:3306/" +
                        "${schemaName}?connectionTimeZone=${timezoneConfig.connectionTimeZone}&preserveInstants=${timezoneConfig.preserveInstants}" +
                        "&rewriteBatchedStatements=true"
            )

            // The failover plugin throws failover-related exceptions that need to be handled explicitly by HikariCP,
            // otherwise connections will be closed immediately after failover. Set `ExceptionOverrideClassName` to provide
            // a custom exception class.
            setExceptionOverrideClassName("software.amazon.jdbc.util.HikariCPSQLException")

            val targetDataSourceProps = Properties().apply {
                // Enable the IAM authentication plugin
                setProperty(PropertyDefinition.PLUGINS.name, "iam")
                setProperty(PropertyDefinition.USER.name, username)
            }
            addDataSourceProperty("targetDataSourceProperties", targetDataSourceProps)

            // Specify the driver-specific data source for AwsWrapperDataSource
            addDataSourceProperty("targetDataSourceClassName", "com.mysql.cj.jdbc.MysqlDataSource")
        }
        return HikariDataSource(hikariConfig)

Possible Solution
No response
Additional Information/Context
No response
The AWS Advanced JDBC Driver version used
2.3.6
JDK version used
Kotlin version 1.9; openjdk 17.0.5 2022-10-18 LTS
Operating System and version
MacOS Sonoma 14.5

Hi @vuongddang
Thank you for reaching out and raising this issue.
We'll take a look at this and keep you updated as we investigate.
In the meantime, could you provide some additional details regarding the following?

What version of the underlying MySQL JDBC driver are you using?
Besides HikariCP, are you using any other libraries or frameworks? If so, what versions are you using?

Thank you for your patience!

Hi @aaronchung-bitquill
Thank you for looking into this. Here're the lib version i'm using:

mysql-connector-j: 8.3.0
HikariCP: 4.0.3
Dropwizard: 3.0.7
Jetbrains exposed: 0.44.1

One thing to note is that while connectionTimezone is not set in the target JdbcPropertySetImpl, other properties, such as rewriteBatchedStatements and preserveInstants, have been set correctly. I can reproduce and debug the issue, so please let me know if I can be of any help.

Hi @vuongddang
I believe this behaviour may be caused by the underlying MySQL Connector/J Driver.
I tested fetching 2022-03-27 01:00:00 from database and set the JVM user.timezone to Europe/Amsterdam. I tested using the AWS JDBC Driver (with MySQL Connector/J underneath) together with an Aurora MySQL database, and MySQL Connector/J together with a regular MySQL database.
Example code snippet:
'''
public class Example {
public static final String MYSQL_CONNECTION_STRING =
"jdbc:mysql://localhost:3306/test?connectionTimeZone=UTC&preserveInstants=true";
private static final String USERNAME = "user";
private static final String PASSWORD = "password";
public static void main(String[] args) throws SQLException {
System.setProperty("user.timezone", "Europe/Amsterdam");
final Properties properties = new Properties();
properties.setProperty(PropertyDefinition.USER.name, USERNAME);
properties.setProperty(PropertyDefinition.PASSWORD.name, PASSWORD);

// Attempt a connection
try (Connection conn = DriverManager.getConnection(MYSQL_CONNECTION_STRING, properties);

    ) {
  Statement statement = conn.createStatement();
  ResultSet result = statement.executeQuery("select * from test_timestamps");

  System.out.println(getTimestamp(result));

//       System.out.println(getResult(result));
}
}
private static Timestamp getTimestamp(final ResultSet result) throws SQLException {
result.next();
Timestamp ts = result.getTimestamp(1);
return ts;
}
private static String getResult(final ResultSet result) throws SQLException {
int cols = result.getMetaData().getColumnCount();
StringBuilder builder = new StringBuilder();
while (result.next()) {
for (int i = 1; i <= cols; i++) {
builder.append(result.getString(i)).append(" ");
}
builder.append("\n");
}
return builder.toString();
}
}
'''
In both cases, the timestamp was converted to 2022-03-27 03:00:00. This leads me to believe that this is due to the underlying MySQL Connector/J driver. This also makes sense as the AWS JDBC Driver is mostly a wrapper that adds additional functionality to an underlying driver. Pre-existing behaviour and parameters (like connectionTimeZone) of the underlying driver should not be altered.
Interestingly, in the above code snippet, if I unpacked result with printResult(), it did not alter the timestamp and printed as 2022-03-27 01:00:00.
If possible, could you try to reproduce this the MySQL Connector/J (without the AWS JDBC Driver)?
Thank you

Hi @aaronchung-bitquill
Thanks for your input, I'll return the test with MySQL Connector/J base on your code snippets by EOD.
Was you able to reproduce the exception when reading the timestamp 2022-03-27 02:00:00 (equivalent unix timestamp:<PHONE_NUMBER>) from the database via AWS JDBC Driver?
One thing to note is our system is running aws-secretsmanager-jdbc, and it is working with the same version of MySQL Connector/J. This is our current config:
val hikariConfig = HikariConfig().apply {
            jdbcUrl =
                "jdbc-secretsmanager:mysql://${dbConnectionReference.databaseUrl}:3306/${schemaName}?" +
                        "connectionTimeZone=UTC&preserveInstants=true"
            username = dbConnectionReference.secretId
            driverClassName = "com.amazonaws.secretsmanager.sql.AWSSecretsManagerMySQLDriver"
            maximumPoolSize = config.maximumPoolSize
            minimumIdle = config.minimumIdle
            addDataSourceProperty("rewriteBatchedStatements", "true")
        }

Hi @aaronchung-bitquill, I ran the same operation with both jdbc-secretsmanager and aws-jdbc-wrapper, and the exception only happens with aws-jdbc-wrapper
For the jdbc-secretsmanager wrapper, timestamps display in the current JVM timezone but include correct offset information. For instance, the datetime 2022-03-27 02:00:00Z appears as 2022-03-27 04:00:00 with a +0200 time offset (see timestamp-with-correct-offset.png).

Here, we can also see that the connectionTimeZone is correctly set in ResultSetImpl

I'll spend more time tomorrow to debug why the connectionTimeZone property is lost when the wrapper creates the connection and will share my findings with you.

Hi @aaronchung-bitquill
Thank you for looking into this issue.
I found the root cause: MySQL Connector/J added the connectionTimeZone property in version 8.0.23 but didn't generate a setConnectionTimeZone method. The aws-jdbc-wrapper uses reflection to set properties (software.amazon.jdbc.util.PropertyUtils#applyProperties), so without this method, the property isn't set.
As a workaround, I'll use the serverTimezone property instead. For Connector/J 8.0.23 and later, serverTimezone is the same as connectionTimeZone. Ref [1] 2

Thanks @vuongddang for your findings. We'll take note of the absence of the setConnectionTimeZone method.
Since a workaround has been found, we'll be closing this issue. Please feel free to re-open it if you wanted to re-visit this or chat more about it.
Thanks again!


Manageing  inter  communication

Is there any que management possibility with context.object?
My concern is mostly when in a situation where huge loads of emits happens.
Is there a better way to handle it

Do not spam all repos!


AcceptableViewModelSelector returns wrong View Model

I tried using the AcceptableViewModelSelector with this Accept-Header in my request (Its the standard header for HTML in FF):
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Expectation:
It should return "ViewModel" with the given Accept-Header and it should return a JsonModel with "application/json" in my Accept-Header.
Reality:
Testcase 1:
$viewModel = $this->acceptableViewModelSelector(
    [
        JsonModel::class => ['application/json'],
        FeedModel::class => ['application/rss+xml'],
    ]
);

Returns

JsonModel if application/json
FeedModel if application/rss+xml
JsonModel with the Accept-Header above

Testcase 2:
$viewModel = $this->acceptableViewModelSelector(
    [
        FeedModel::class => ['application/rss+xml'],
        JsonModel::class => ['application/json'],
    ]
);

Returns

JsonModel if application/json
FeedModel if application/rss+xml
FeedModel with the Accept-Header above

Testcase 3:
$viewModel = $this->acceptableViewModelSelector(
    [
        FeedModel::class => ['application/rss+xml'],
        JsonModel::class => ['application/json'],
        ViewModel::class => ['text/html'],
    ]
);

Returns

JsonModel if application/json
FeedModel if application/rss+xml
ViewModel with the Accept-Header above

Observation
It seems like the fallback to defaultViewModel does not work and it'll returns the first Model it gets if no match was successfull.

PS:
I tried it with

PHP 7.0.9-1~dotdeb+8.1
zendframework/zend-mvc 3.0.2
zendframework/zend-view 2.8.1

I added this test to the zend-mvc test suite:
    public function testAppropriateFallbackOrderTestCase1()
    {
        $arr = [
            'Zend\View\Model\JsonModel' => ['application/json'],
            'Zend\View\Model\FeedModel' => ['application/rss+xml'],
        ];

        $header   = Accept::fromString('text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8');
        $this->request->getHeaders()->addHeader($header);
        $plugin   = $this->plugin;
        $result   = $plugin($arr);

        $this->assertInstanceOf('Zend\View\Model\ViewModel', $result);
        $this->assertNotInstanceOf('Zend\View\Model\FeedModel', $result);
        $this->assertNotInstanceOf('Zend\View\Model\JsonModel', $result);
    }

and it does fail because $result is a JsonModel, as you suggested it would.  After reviewing the code I think it's a subtle bug in the way AcceptableViewModelSelector builds the accept string used to match against the Accept header.  The default model is not included in the match string when it's constructed (here), so AcceptableViewModelSelector sends this to the Accept header for matching:
application/json; _internalViewModel="Zend|View|Model|JsonModel", application/rss+xml; _internalViewModel="Zend|View|Model|FeedModel",

As those match none of the explicit types specified in the Accept header, it comes down to that last piece */*;q=0.8 which matches everything, and the first acceptable model in the list will always match that.
So, this is caused by AcceptableViewModelSelector not adding the default view model with content type text/html to the list of acceptable types matched by the Accept header.  If the match string looked like this instead:
application/json; _internalViewModel="Zend|View|Model|JsonModel",
application/rss+xml; _internalViewModel="Zend|View|Model|FeedModel",
text/html; _internalViewModel="Zend|View|Model|ViewModel",

It would work (as your Test Case 3 above shows).
TL;DR: when specifying a list of acceptable view models, specify every acceptable one and don't rely on the fallback to render the HTML view.  It can't be added automatically to the list as there might be cases where HTML isn't an acceptable return and you'd then have to opt-out of that by setting a different default.
My recommendation is to update the docs for AcceptableViewModelSelector to make it clear that when specifying a list of acceptable models you must specify every acceptable type.

In reality every browser appends / at the end of the Accept Header so the default view model is only used for the non-browser requests?

FF AJAX: application/json, text/javascript, /; q=0.01
Chrome HTML: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8
Chrome AJAX: application/json, text/javascript, /; q=0.01

Essentially, yes.  The default is used in only two cases:

An empty list of acceptable views models was given.
There are no matches against the Accept header.

However 2 is moot if the Accept header has a *.* since it will always match something.


TypeScript issues

Hi,
I have the latest version installed from NPM (2.7.0), but I don't think it reflects all the changes; for example, chart_instance is supposed to be renamed to chartInstace, but I still see chart_instance
Also, I'm not sure how exporting the defaults is going to be useful in TypeScript since it's an empty object, and if we want to set a property on it, the TS compiler will complain

I'm having the same issue as above, chart_instance is still used in the index.d.ts.

2.7.1 should address this issue.


Make Backend and EventReader be implemented on separate types.

I think the trait Backend should be trait Backend: EventReader. Currently, its not really possible to pass in crossterm backend with a potential device_query event reader.
But this would tie the EventReader to the Backend (such as we have now).
I think if there was:
struct BackendWithEvents<B: Backend, E> {
    backend: B,
    event_reader: E,
}

impl<B: Backend, E> Backend for BackendWithEvents<B, E> {
    // forward to self.backend
}

impl<B, E: EventReader> EventReader for BackendWithEvents<B, E> {
    // forward to self.event_reader
}

We could combine them, and decouple EventReader from the Backend

Reasons for maybe doing this:
device_query uses the window events (e.g. from Win32 or X11) for doing more complex and complete user input reading. It requires a graphical environment for the terminal emulator to run in, though.
I don't know if this is ideal, but personally I would like to play around with it.

I doubt this'll happen


rework azure jobs

@kargakis ptal

fixes up the jobs to work with https://github.com/openshift/openshift-ansible/pull/8121 (now merged)
condenses the 4 almost identical image build jobs into 1
removes the master pr & branch tests because they just don't work yet.  we can readd them when we're closer
other small fixes

cf https://github.com/openshift/release/pull/818
This PR doesn't include the definition of https://ci.openshift.redhat.com/jenkins/job/azure_build_images, how should we deal with that?

This PR doesn't include the definition of https://ci.openshift.redhat.com/jenkins/job/azure_build_images, how should we deal with that?

Unclear what that job is doing. How is it different from the generic build job you introduce here?
/cc pschiffe

Also there is no way to pass environment variables from the prow config to Jenkins so you still need 4 distinct Jenkins jobs. cc @stevekuznetsov

@kargakis ptal again

/lgtm
On May 1, 2018 20:05, "Jim Minter"<EMAIL_ADDRESS>wrote:

Merged #1322 https://github.com/openshift/aos-cd-jobs/pull/1322.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/aos-cd-jobs/pull/1322#event-1603847060, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADuFfzr0Tcsgym67XOIdQTZhfVd210gaks5tuKPNgaJpZM4Tg3vC
.


Battle mode

Yeah two player mode! Bub shoots bubbles out of his butt, sorry.

Awww... bub is always the bridesmaid.


-source choices passed to scalac 3.* via space instead of colon and gets ignored.

scalac respects -source option choices only if they are passed via colon to it: -source:future, -source:future-migration, etc.
As far as I could understand, sbt-tpolecat passes all options along with arguments to scalac as one big List[String] turn lead to ignore or such options.
Could be shown with this scala-cli scripts:

Working one:
//> using scala "3.2.1"
//> using option "-source:future"

def method[A: Numeric](a: A): A => A = { a1 =>
  implicitly[Numeric[A]].plus(a, a1)
}

println(s"method(1)(1) = ${method(1)(1)}")

Incorrect:
//> using scala "3.2.1"
//> using option "-source future"

def method[A: Numeric](a: A): A => A = { a1 =>
  implicitly[Numeric[A]].plus(a, a1)
}

println(s"method(1)(1) = ${method(1)(1)}")

Compilation fails with:
Compiling project (Scala 3.2.1, JVM)
Warning: bad option '-source future' was ignored
[error] ./space.sc:9:38
[error] Found:    (1 : Int)
[error] Required: Numeric[Int]
[error] println(s"method(1)(1) = ${method(1)(1)}")
[error]                                      ^
Error compiling project (Scala 3.2.1, JVM)
Compilation failed

P.S. the same could be said about -Ykind-projector:underscores and other : options.

Hmm...that's frustrating. I wonder when this changed?
In fact, Scala 3.x's own compilation tests provide these as space-separated tokens.


FeignClient: @PathVariable that contains spaces replaced by '+'

We have an issue using @FeignClient with Spring Cloud version Angel.SR4. In a service mapping like this example
@RequestMapping(method = RequestMethod.GET, value = "/{name}")   void update(@PathVariable("name") String name);
if name path variable contains a space (example: "mike james"), the feign client call will replace the space with a '+', so the REST service will receive "mike+james".
Is there any workaround for this issue?

URL's can't contain spaces, so it is url encoded. http://www.w3schools.com/tags/ref_urlencode.asp

Closing this due to inactivity. Please re-open if there's more to discuss.


✨ create compose package

closes #68
This PR adds our custom compose function to the project as a package.

@tzvipm went with react-compose


The meaning of "_w_gs.jsonl" in evaluation data

Thanks for your incredible work!
I notice that there are four files for short form QA in the eval data folder.

popqa_longtail.jsonl
popqa_longtail_w_gs.jsonl
triviaqa_test.jsonl
triviaqa_test_w_gs.jsonl

I am wondering what 'w_gs' means and more specifically,

how the ctxs field is built.
why the ctxs in popqa_longtail.jsonl and popqa_longtail_w_gs.jsonl differ in numbers and values? (some contexts in popqa_longtail_w_gs.jsonl don't have document id and score)
why triviaqa_test_w_gs_df only has 7313 samples while triviaqa_test.jsonl has 11313? how it is filtered?

Hi! _gs indicates that the retrieved results are further enhanced by Google Programmable Searc in addition to the original contriever top 10 documents. We added this new results in our updated manuscript, Section B.2.
That's the reason the number of the contexts differ. The different number of instance seem to be odd, and I may upload incorrect file... Let me double check!

Hi there!
I'm so sorry, but where can I find the eval data folder or How can I generate it?


Debugging interactive window never starts for remote kernel

I was connected to a remote kernel, set a breakpoint in a .py file and clicked the debug cell code lens.
The debugging toolbar appeared, but I don't think the code was submitted and the breakpoint was never hit.

debuggingIWLogs.txt
Jupyter server logs from that time
[I 09:05:34.084 NotebookApp] Creating new notebook in
[I 09:05:34.250 NotebookApp] Kernel started: 99f96b8d-ec2a-4149-bd0a-e2fcd103e9c9, name: python3
[W 09:05:34.284 NotebookApp] delete /script1.py-jvsc-8a40bb87-9c8a-4bd4-9f2b-bd54a3a0178bba999467-a371-4bc6-bdcd-4a1bcfac3640.ipynb

I have not been able to resolve this after Reloading vs Code, trying a different script, killing and starting a new Jupyter server

I think this will be fixed with https://github.com/microsoft/vscode-jupyter/issues/12407


RotationQuaternion: Scalar fixes, wrong sign in Taylor approximation

Double type does not work when using primitive types that cannot implicitly be converted to and from double.
The Taylor approximation has the wrong sign in my opinion.

I agree. Thanks for the fix! Would you mind adding a unit test covering this specific case?

I don't have much time to write a unit test now and it is not directly evident to me how such a test would look like. As far as I know, there's not much to test against in kindr.
Take a look at the symbolic Taylor expansion, it shows that the sign was wrong: http://www.wolframalpha.com/input/?i=taylor+expansion+sin(theta%2F2)+%2F+theta+at+theta%3D0
Can we merge this in?


[rstmgr] Update pok usage in rstmgr_por

POR should use the AST output directly instead of the IO reset.
The IO reset causes the POR signal to assert and then reset the device.

can you guys have a quick look? This is a really straightforward PR that just changes the root reset to AST instead of IO.


Move helm values for subcharts into umbrella chart

Goal
As a user, I want to have easy access to all the possible helm values that can be set for the Keptn Helm chart. This enables me to easily configure options for any of the Keptn components from one place. It also enables me to get the default values file and start my setup from a good default config with all possible Helm values.
Details

copy Helm values from subcharts to umbrella chart
it should be possible to configure helm values for the subchart both from the umbrella chart AND from the subchart
standalone installation of the subcharts should still be possible without restrictions
precedence should be given to the values defined in the umbrella chart

DoD

Helm values are defined both in the subcharts and the umbrella chart

Vote for implementing this ticket with 👍 or 👎 to close it.

A bit more context from my end, feel free to add/edit 😄
All values in one chart(👍 ) :
PROs:

everything is there
if you run helm show values keptn/keptn you will get all the possible configurations for the operators.

CONs:

everything is there,
if I do not care about ex. the lifecycle operator, suddenly the information I need is inconvenient to access and I have to scroll around useless configurations

Separate values file (👎 ):
PROs:

no changes needed,
helm show values keptn/keptn only shows global configurations and the values to turn on and off each operator.

CONs:

again if users care about changing stuff for ex. metrics operator, they need to look for the dependent chart README file to see the description of those values.
Potentially one would have to go trough 3 README files to understand all possible configs.

The vote showed that the team doesn't need to implement this ticket.
Decided in the community meeting of Dec 6th 2023.


[Deliver] Q: Downloading screenshots of (old) live iOS App while new version is Prepare for Submission

[*] Updated fastlane to the latest version
[*] I have read the Contribution Guidelines

Hi,
I have a small question about downloading data/screenshots. I have an application which is 'Ready for Sale' in ITC. A few months ago we've prepared an update with completely different screenshots, which was Pending, but never released.
Today, we want to update the application (for iOS 10), but since the app never really changed, the wrong screenshots are still in the 'update shell' from earlier on. I've developer rejected but of course, I can only remove the 'wrong' screenshots.
Since this app is a cash cow but also pre-historic, we've lost the original screenshots. I'm wondering if it's possible to download the screenshots of the version that is currently Ready for Sale.
Using 'App version = "2.0"' (in the deliver file) doesn't help. It recognizes my input, but still downloads screenshots from the update version which is currently Prepare for Submission and containing the wrong screenshots.
Am I doing something wrong? Is this possible?

Anybody? A yes or no if it is even possible would already suffice for now

Hey @Bureauwlamp, sorry for the late reply. I'm not 100% sure, but you might be able to do so using spaceship: https://github.com/fastlane/fastlane/blob/master/spaceship/docs/iTunesConnect.md

@Bureauwlamp Have you tried running deliver download_screenshots? That downloads all possible screenshots available in iTC. If they aren't available there I'm not sure it's possible through fastlane.


Local scope seems to become global in unit tests.

We had some very confusing and critical bugs in our unit tests. We found the problem in how meteor-jasimine treats local scope in unit tests (not integration tests). In Meteor all variables defined with var are local to the file they are defined in. But unit test framework seems to put them into the global scope.
See and try the following simple Gist (5 files):
https://gist.github.com/tansin/64bbfcefd2b8a0da597d
Please fix this issue, because it's a kind fundamental.
Versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I need to rewrite a lot of the server unit mode when I find some time. You may consider to use the server integration mode for you unit tests in the meantime. The execution is slower, but it uses the Meteor build system.

Thank you for quick reply. I'll try to speed up integration tests somehow.

@tansin, you might also consider wrapping the tests in an IIFE yourself.


Release Google.Cloud.Talent.V4 version 2.5.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)

Created release for Google.Cloud.Talent.V4-2.5.0


Error when counting points in point cloud

In the examples/groundtruth_extraction.py example script there is a small bug. The matrix you get at Line 71 does not take into account the height, width, length should be divided by 2 as it is from the center of the object. The resulting boxes are 2x the size they should be and therefore the mask obtained includes points that are not part of the object.
Changing:
sl, sh, sw = box.length, box.height, box.width  to
sl, sh, sw = box.length/2., box.height/2., box.width/2.
in the utils. get_box_transformation_matrix  fixes the problem in this instance but maybe that breaks the function for other uses?

Thanks for reporting the issue. I am not currently actively using the dataset, so I am not able to test the proposed fix; however, your observation sounds correct. Feel free to create a PR and I can merge it.

Hello, will simply changing the codes as @dgriffiths3 does make the whole thing correct? I am using pytorch and I am struggling when loading waymo dataset. So this is actually  the original issue. So if possible, could u plz share some ideas with me?

Hi, it worked in my case, but I was only using it for the task of counting the points. I was planning to do a PR but haven't found time to check it won't break other functions.

Thanks for your reply. @dgriffiths3


Improve MSL documentation by clearly identifying the target of each link.

Reported by dietmarw on 5 Oct 2009 06:34 UTC
Currently the MSL contains links called "link" or "click here". This is very bad practise and was only used in the very early times when one had to tell the user what to do in order to see more information.
In Guideline 13. Provide clear navigation mechanisms of the Web Content Accessibility Guidelines 1.0 (see what I did there) one can read:
13.1 Clearly identify the target of each link. [Priority 2]
Link text should be meaningful enough to make sense when read out of context -- either on its own or as part of a sequence of links. Link text should also be terse.
For example, in HTML, write "Information about version 4.3" instead of "click here". In addition to clear link text, content developers may further clarify the target of a link with an informative link title (e.g., in HTML, the "title" attribute).
So at one point we should change all "here", "click here", etc. links and this should also go in the documentation guide lines.

Migrated-From: https://trac.modelica.org/Modelica/ticket/220

Comment by dietmarw on 1 Sep 2010 07:09 UTC
Did a grep for "here" links and replaced them where found in 0868d3694cc187e437711b3f724c202b349df2c8.


CAMEL-8464 Remove likeCompanyUpdate endpoint from camel-linkedin

Thanks this PR has been merged. Do you mind closing this?


slide up programmatically

is there any way to invoke the slide up animation programmatically?

@edxe i have a simple approach, I know that this is not the best solution.
go to the library index.js
add this method
open() {
    this.startAnimation(-100, 500, this.state.initialPositon, null, this.state.finalPosition);
    this.props.onRelease && this.props.onRelease(true); // only add this line if you need to detect if the drawer is up or not
 }

then add ref in your drawer calling component:
<Drawer
          ref={(c) => {
            this._drawerRef = c
          }}
          ...

then you can call the open function by using the ref:
openTheDrawer() {
    this._drawerRef.open()
}

there you are the drawer will open like you usually do.
Remember this is a alternate approach and it is not the best obviously but it is better than nothing :)

Updated from PR!


Error adding Plugins

    <!-- Please succinctly describe your issue and steps to reproduce it. -->

    -
    Hyper 1.4.3
    Electron 1.7.5
    win32 x64 10.0.15063

Due to the lack of information, I'm assuming this is a duplicate of #2173. Please follow the issue template so we have more to go off of, next time 😄


fix: make commands work on windows

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: