The url inside the composer.json should be in their secure version?

Hi,
I think the urls should be written with http:// instead of http://.
https://github.com/thephpleague/uri/blob/c8dc5e3dad96b118e8724640b3d1b410c999b206/composer.json#L27
What do you think?
Regards

@S-Tian86 nice catch a PR for this quick fix is welcomed 😉

Sure, no problem.
Note: Credits to PhpStorm inspections.


Open interface

Can it be added? When the interface is opened, the blocks in the inventory cannot be dragged and moved.

everything is customized in the configs. maybe one day we will add an in game editor

No
BossShopPro, does not have this function...
BSP-GuiShopManager... only has that function configuration


createBatchingNetworkInteface was missing

"export 'createBatchingNetworkInterface' was not found in 'apollo-client'

If you want to use apollo 2.x, please see the next branch.


keyvault show secret quickly fails after they are recently set

This is an autogenerated template. Please review and update as needed.
Describe the bug
Command Name
az keyvault secret show
Errors:
:confused:
Max retries exceeded attempting to connect to vault. The vault may not exist or you may need to flush your DNS cache and try again later.
To Reproduce:
turn on soft-delete on keyvault

Fill in additional info here
Run: az keyvault secret show --vault-name {} --name {}

Expected Behavior
should not throw error
A clear and concise description of what you expected to happen.
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Shell: cmd.exe

azure-cli                         2.0.62 *

Extensions:
dev-spaces-preview                 0.1.6

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\xiaodoli\.azure\cliextensions'

Python (Windows) 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)]

Additional Context
Add any other context about the problem here.

To print out the issue body locally, run az feedback --verbose

@smartpcr could you please provide more details around this issue using az feedback? Have you followed the guidance here for soft delete - https://docs.microsoft.com/en-us/azure/key-vault/key-vault-soft-delete-cli ?
@jiasli, could you please take a look as well to see if you can repro this issue?

right now, this is only happening for machines that are domain joined (microsoft)
ping me<EMAIL_ADDRESS>if you have questions.

Could you please

Update to the latest CLI version (currently 2.0.72)
Test if this happens with PowerShell
Test if there is DNS change after run  --enable-soft-delete true

Also, does the keyvault recover after some time?

Closing due to no response. If the issue happens again, please let us know.


documentation says usage is df.groupby().get_groups(key) but is df.groupby().getGroup(key)

The documentations points to using get_groups() to return df of a particular group in group by. Documentation shows correct name of function is getGroup()
https://github.com/javascriptdata/danfojs/blob/f272a7eac7fb0a13be313f15e72d3506136093b6/src/danfojs-base/aggregators/groupby.ts#L524-L528

Had the same issue as well, I needed to check the prototype of the object to figure out the name


is the site shut down or private

Hi.  I did indeed take the site down, but you can still install and run the source code locally.  I asked Vyond by email and they said that they wouldn't approve if I kept it up.

how can i run the source code locally

You'll need Node.JS for this, but the rest of the instructions are on the README (go to the main page).

how do i do the commands

i dont understand The README i dont understand what it says

Do you have Node.JS installed on your machine?

yes

what do you do after you set up all of the things in  README.md?
got it all set up

i found out why it shutted down; it's because GoombaYesKyleNo VGCP
contacted vyond to shut it down
real proof
https://www.youtube.com/watch?v=wC06QnCPm3o
https://www.youtube.com/watch?v=JqVZ89tLeQ
https://www.youtube.com/watch?v=JqVZ89tLeQE
Le mer. 5 févr. 2020 à 22:58, John<EMAIL_ADDRESS>a écrit :

what do you do after you set up all of the things in README.md?
got it all set up
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoAnimate-Wrapper/GoAnimate-Wrapper/issues/32?email_source=notifications&email_token=AOMJO7374EVWOBCMA6OGGUTRBMZAVA5CNFSM4KP2FLU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK5EMCQ#issuecomment-582632970,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOMJO76X6IQQBV6YTRPF2K3RBMZAVANCNFSM4KP2FLUQ
.

i found out why it shutted down; it's because GoombaYesKyleNo VGCP contacted vyond to shut it down real proof https://www.youtube.com/watch?v=wC06QnCPm3o https://www.youtube.com/watch?v=JqVZ89tLeQ https://www.youtube.com/watch?v=JqVZ89tLeQE Le mer. 5 févr. 2020 à 22:58, John<EMAIL_ADDRESS>a écrit :
…
what do you do after you set up all of the things in README.md? got it all set up — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#32?email_source=notifications&email_token=AOMJO7374EVWOBCMA6OGGUTRBMZAVA5CNFSM4KP2FLU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK5EMCQ#issuecomment-582632970>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOMJO76X6IQQBV6YTRPF2K3RBMZAVANCNFSM4KP2FLUQ .

No.  I shut it down because Mark Deaton (the COO of Vyond) got in touch with me and prompted me to take down the service.  Vyond don't actively pursue takedown requests, and neither does EvenNode.


GUACAMOLE-890: Security: Allow image to run as non-root user

Hi,
This solves https://issues.apache.org/jira/browse/GUACAMOLE-890, allowing Guacamole Docker image to run as non-root user.
For this, we symlink the guacamole.war file during the build, not at run time.
We also world-chmod the temp directory which strangely enough is not by default.
Finally, we prevent application from being unpacked, as non-root user can't write to the webapps dir.
For this, we change the webapps directory location to one created by the user itself.
We also create a temp directory which is then user-writable.
While here, as another security enhancement, I enabled the remote IP valve, as it's let's say impossible to do it properly at run time, once image is built. IMO not an issue as Docker image is intended to be used behind a proxy...
As it's an important security concern, would be nice to have this in 1.1.0.
Would really be glad to test a new build an confirm everything's OK (it is on my locally-modified image).
Many thanks for your support 👍

You all seem to have missed the point! ;)
Regardless of this change, we should be switching to the jdk8 suffix. It is
not a question of size, it is a question of support. I don't see that there
is an option.
The jre8 suffix is NOT an officially supported tomcat container. See here
for supported tags: https://hub.docker.com/_/tomcat?tab=description or
https://github.com/docker-library/official-images/blob/master/library/tomcat
The jre8 tag is available. It was last updated 8 months ago vs 23 Dec for
the jdk8 image. Unsurprisingly, the jre8 image is not part of the tomcat
docker build process, as you can see from any recent build reports.
Here is the pull request for that change (
https://github.com/docker-library/tomcat/pull/158). I am sure the
requirement for the jdk does not affect us, but I really think we should be
using a supported image and all jre images have been removed.
M.
.
On Sun, 2 Feb 2020 at 21:39, Virtually Nick<EMAIL_ADDRESS>wrote:

@necouchman commented on this pull request.
In Dockerfile
https://github.com/apache/guacamole-client/pull/469#discussion_r373877390
:

@@ -25,7 +25,7 @@

such as --build-arg TOMCAT_JRE=jre8-alpine

ARG TOMCAT_VERSION=8.5
-ARG TOMCAT_JRE=jre8
+ARG TOMCAT_JRE=jdk8
I also don't think a world-writable directory is the right way to go - the
directory should have the correct ownership and permissions, not just the
ones that work because we've blown everything open. If we're trying to
improve security with this issue, making something world-writable seems
contradictory to that effort.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/guacamole-client/pull/469?email_source=notifications&email_token=AB4VJ5A47ODT7FRLO3QA7RLRA44S3A5CNFSM4KNTHIJ2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCT5KAZA#discussion_r373877390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4VJ5E5ESVYKNI3POI6ZI3RA44S3ANCNFSM4KNTHIJQ
.

Feel free to agree all together on the best solution and let me know so that I can finally tune this PR accordingly :)
Whatever the final choice, I'll be glad to test :+1:

OK, I've then switched again to the jdk image.
And let the creation of the temp dir, which is then writable by the user only.
This whole PR should then suit all thoughts / needs :)
Many thanks again 👍

Some news regarding this @mike-jumper @necouchman @manolan1 ?
Thank you 👍

My view is that this must be a common tomcat problem and should be solved
in the tomcat container. However, what they have done doesn't seem to work
for us. I haven't had a chance to look at why not since I thought that was
exactly what they were trying to achieve. I don't need this functionality
right now, so my selfish view would have been to leave it until it is
sorted upstream. But I know that won't work for everyone.
I also think we should definitely move to a supported tomcat container,
though whether that should actually be done under this Jira or under a
different one is a moot point.
I realise that is frustratingly vague, but it is where my thoughts are.
M.
.
On Tue, 3 Mar 2020 at 16:02, Ben RUBSON<EMAIL_ADDRESS>wrote:

Some news regarding this @mike-jumper https://github.com/mike-jumper
@necouchman https://github.com/necouchman @manolan1
https://github.com/manolan1 ?
Thank you 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/guacamole-client/pull/469?email_source=notifications&email_token=AB4VJ5C4UBXYAS3WOVLSNF3RFUSXPA5CNFSM4KNTHIJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENUCBFY#issuecomment-594026647,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4VJ5DRTY6UBMDOLDU4MI3RFUSXPANCNFSM4KNTHIJQ
.

I just pushed a better approach.
start.sh now creates a whole new CATALINA_BASE.
It's then user-writable only, not world-writable, better for security as already stated above.
And this method follows Tomcat guidelines.
Seems perfect IMO.
Regarding jdk vs sdk image, let's discuss this in another Jira / PR.
Let's merge this @mike-jumper @necouchman ?
Thx 👍

However, it is solving a problem that we shouldn't be solving. If we move to the supported tomcat image, then it runs with a non-root user without any of these changes. Surely that is much better than anything else.

I wholeheartedly agree.

By all means add the valve, but I don't think that is solving this same issue, so I believe it is a change that should be made under a different Jira.

Yep.

However, it is solving a problem that we shouldn't be solving. If we move to the supported tomcat image, then it runs with a non-root user without any of these changes. Surely that is much better than anything else.

I wholeheartedly agree.

Allowing the image to run as non-root is a worthy goal, but one that should be implemented within the Tomcat image. Once that's the case (it sounds like it already is?), (...)

No, as already stated here, it's not.
Some details again.
Please read carefully, sorry I'll certainly repeat / reuse some arguments given above.
Here is then the directory structure from the last tomcat:8.5-jdk8  image :
(as a ref base image update PR from jre to jdk is here : #485)
# ls -l /usr/local/tomcat/
-rw-r--r-- 1 root root 19318 Mar 11 10:06 BUILDING.txt
-rw-r--r-- 1 root root  5408 Mar 11 10:06 CONTRIBUTING.md
-rw-r--r-- 1 root root 57011 Mar 11 10:06 LICENSE
-rw-r--r-- 1 root root  1726 Mar 11 10:06 NOTICE
-rw-r--r-- 1 root root  3255 Mar 11 10:06 README.md
-rw-r--r-- 1 root root  7136 Mar 11 10:06 RELEASE-NOTES
-rw-r--r-- 1 root root 16262 Mar 11 10:06 RUNNING.txt
drwxr-xr-x 2 root root  4096 Mar 17 23:14 bin
drwxr-xr-x 1 root root  4096 Mar 27 21:39 conf
drwxr-xr-x 2 root root  4096 Mar 17 23:14 include
drwxr-xr-x 2 root root  4096 Mar 17 23:13 lib
drwxrwxrwx 1 root root  4096 Mar 27 21:39 logs
drwxr-xr-x 3 root root  4096 Mar 17 23:14 native-jni-lib
drwxrwxrwx 2 root root  4096 Mar 17 23:13 temp
drwxr-xr-x 2 root root  4096 Mar 17 23:13 webapps
drwxr-xr-x 7 root root  4096 Mar 11 10:04 webapps.dist
drwxrwxrwx 2 root root  4096 Mar 11 10:03 work

As you can see, logs, temp and work directories of the default CATALINA_BASE have been made world-writable.
But still, the webapps directory is not world-writable, so a non-root user won't be able to link guacamole.war into it. So the Guacamole start.sh script will fail.
So, there's still something missing.
You could then propose to ask the Tomcat image maintainers to chmod 777 webapps.
But, and as you already stated here @mike-jumper, the goal (of running as non-root user) should not be achieved removing restrictions.
In other words, from a security point of view, the method used by the image maintainers does not seem to be the good one.
To confirm this, here's now the default directory structure from a Debian 10 Tomcat installation :
# ls -l /var/lib/tomcat9/
lrwxrwxrwx 1 root   root     12 Jun 13  2019 conf -> /etc/tomcat9
drwxr-xr-x 2 tomcat tomcat 4096 Jun 13  2019 lib
lrwxrwxrwx 1 root   root     17 Jun 13  2019 logs -> ../../log/tomcat9
drwxr-xr-x 2 root   root   4096 Mar 27 22:51 policy
drwxrwxr-x 3 tomcat tomcat 4096 Mar 27 22:51 webapps
lrwxrwxrwx 1 root   root     19 Jun 13  2019 work -> ../../cache/tomcat9
# ls -ld /var/log/tomcat9/ /var/cache/tomcat9/
drwxr-x--- 3 tomcat tomcat 4096 Mar 27 22:51 /var/cache/tomcat9/
drwxr-s--- 2 tomcat adm    4096 Mar 27 22:51 /var/log/tomcat9/

As you can see here, logs, work and webapps directories are only writable by the tomcat user.
It then does not makes sense to make them world-writable so that another user can start its application... Would be a messy / crappy configuration...
On the contrary, as explained above, and as explained in the Tomcat documentation, we should, in this case, create and use a dedicated proper CATALINA_BASE directory structure.
This is what this PR does...
It creates the 5 runtime directories which are then readable / writable only by the user running the application. Link the application into it, and start from it...
Sincerely, it really looks like the way to go.
We follow the Tomcat documentation, the resulting PR is really tiny, it has no side effect, no runtime or performance impact, it allows to run as non-root user, and enforces directory structure security...
I don't see why we wouldn't go for it...
Thank you again if you could then reconsider this 👍

Any thoughts regarding my detailed explanation above ?
Thank you !

5 months have passed since the beginning of this PR...
Any thoughts then regarding my explanation above, which gives all the details to understand why we came to this solution ?
Thank you again for your support !


Requests not being recorded in Laravel Telescope

I'm using the package to manage my API connections in my Laravel application.
In my development environment, Telescope is not recording any Saloon request made with this sender.
Any ideas?
Thanks!

Hey @scajal! Thanks for your issue - which version of the package are you using? Make sure to upgrade to the latest v0.3.1 as we fixed a couple of issues with reporting requests in Telescope.
Also have you made sure to configure the HttpSender in either your config file or within the resolveSender method on your connector?
https://docs.saloon.dev/digging-deeper/laravel-integration#configuration

Hi @Sammyjo20, thanks for the quick response.
I'm using version 0.3.1, and I've the config file configured as follows:

I had to change the namespace to Saloon\HttpSender\HttpSender because the namespace specified in the docs (Saloon\HttpSender\Http\Senders\HttpSender) didn't work for me.

Thank you for letting me know about the namespace in the docs - I have now updated that :)
Are your config files cached in Laravel? Try running php artisan config:clear to reset any config caching that might be going on.
Are your requests being sent properly? Are there any errors with them?
What kind of response type is it?

Tried reseting the cache but nothing happened.
The requests are being sent properly, yes, no errors in them. The response is always JSON.

The requests would be displayed under "HTTP Client" section of Passport - just checking is this where you've been looking? Also have you tried sending a request with the Laravel HTTP Client to make sure Passport is properly capturing requests?

Oh, my bad! I was looking under the "Requests" section of Telescope.
I can see them under "HTTP Client".
Sorry! Thanks for the clarification.

Fantastic! I will update the docs accordingly. Enjoy Saloon 🤠


use a NEWS or NEWS.md file in the root of your package

and provide the developers with sufficient information on release tags, http://r-pkgs.had.co.nz/description.html#version

Under that header, put in sections as needed, including: NEW FEATURES, MINOR IMPROVEMENTS, BUG FIXES, DEPRECATED AND DEFUNCT. Under each header list items as needed. For each item give a description of the new feature, improvement, bug fix, or deprecated function/feature. Link to any related GitHub issue like (#12). The (#12) will resolve on GitHub in Releases to a link to that issue in the repo.
After you have added a git tag and pushed up to GitHub, add the news items for that tagged version to a Release on the Releases tab in your GitHub repo with a title like pkgname v0.1.0
If you use NEWS, add it to .Rbuildignore, but not if you use NEWS.md

Done since release 0.1.2


Do not select disabled options

old logic
https://github.com/toughbyte/selectize.js/assets/31632314/08843898-e04a-4198-a664-2ab438849625
new logic
Uploading simplescreenrecorder-2023-11-30_10.26.45.mp4…

Great!


Add organization membership API methods

Description
Adds methods for organization methods. Removes deprecated methods for adding and removing users from organizations.
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

Codecov Report
Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (ae25324) 87.80% compared to head (a430489) 87.56%.

Files
Patch %
Lines

workos/user_management.py
80.00%
6 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #218      +/-   ##
==========================================
- Coverage   87.80%   87.56%   -0.25%
==========================================
  Files          32       32
  Lines        1173     1198      +25
==========================================
+ Hits         1030     1049      +19
- Misses        143      149       +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Passing non-Sanity props to custom components

In the react docs, it seems possible to render custom components with external props, as seen here in the docs :
const components = {
  types: {
    code: props => (

        {props.node.code}

    )
  }
}

However, in the svelte implementation, the docs suggest that we just pass the name of the Svelte component in the serializer:

<PortableText
    value={value}
    components={{
    types: {
        image: ImageBlock,
        doubleImage: DoubleImage,
        story: Story,
        interview: <InterviewItem name={page.interviewName} />,  // What I'd like to do.
    },
    marks: {
        link: Link,
    },
    block:{
        normal: ArticleText,
    }
    }}
/>

I'd like to be able to pass external props (in this case from the field's parent document) into a PortableText block.  So far, I'm able to get by with Svelte stores, but it feels more like a workaround.

Running into the exact same "problem"! +1

Actually @rscheuer , I just found out this is possible by first looking through the source code, and then the documentation.
See this reference: https://github.com/portabletext/svelte-portabletext/blob/35511cf7043aeb529bad8d2080c7e26b4241bca8/README.md#customizing-rendering
Here's my code:

	<PortableText
		context={{ isBlog }}
		components={{
			types: {
				blockImage: BlockImage,
			},
			marks: {
				annotationLinkExternal: AnnotationLinkExternal,
				annotationLinkInternal: AnnotationLinkInternal,
				annotationLinkEmail: AnnotationLinkEmail,
			},
			listItem: {
				normal: NormalListItem,
			},
			block: {
				normal: Block,
				h2: BlockHeadings,
				h3: BlockHeadings,
				h4: BlockHeadings,
			},
		}}
		value={blocks}
	/>

Then in the Block.svelte, you can access portableText.

<slot />


{github} Update CODEOWNERS

Related command

Add Ethan Yang as code owner of azure-cli-core
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Update code owners


Support for median absolute deviation aggregation?

Hi! Thanks for this library! Is there a support for https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-median-absolute-deviation-aggregation.html
?

This aggregation type will be released with 7.0.15.


System Informer freezes completely running as Admin

Brief description of your issue
If System Informer is run as Admin, right-clicking the tray-icon or selecting the 'System' menu bar item in the window, will freeze the program for minutes to indefinitely.
Steps to reproduce (optional)

Launch System Informer as Admin
Right-click on the tray icon or hover the 'System' item in the menubar.

Expected behavior (optional)
A sub-menu should appear.
Actual behavior (optional)
System Informer freezes. Oddly enough, the tray icons would continue updating normally while SI froze.
Environment (optional)
System Informer 3.0.7660 (Stable) & 3.1.24192 (Canary)
Windows 10 LTSC IOT 2021 (Build: 19044.4651)
Windows 11 LTSC IOT 2024 (Build: ???)

hover the 'System' item in the menubar.

There's a few different things named System. Are you referring to the System process or System Information?

System Informer is run as Admin,

Do you have any extra characters in the window title + or ~?

hover the 'System' item in the menubar.

There's a few different things named System. Are you referring to the System process or System Information?

No. The System Informer's windows itself, in the menubar.

System Informer is run as Admin,

Do you have any extra characters in the window title + or ~?

Can you open cmd.exe and copy the output from bcdedit /v?

Somehow the bcdedit /v hangs?

It showed this after 10 minutes.
A busted BCD config? I re-installed Windows just last week with default settings...

selecting the 'System' menu bar item in the window, will freeze the program for minutes to indefinitely.

The system menu enumerates boot entries so you can restart directly into firmware or Windows Defender Offline Scan:

You'll need to fix bcdedit to resolve the issue with the System menu.

A busted BCD config? I re-installed Windows just last week with default settings...

If the system is booting correctly but bcdedit isn't working then there might be some issue with the partition:
https://superuser.com/questions/1261017/bcdedit-exe-refuses-to-open-system-store

selecting the 'System' menu bar item in the window, will freeze the program for minutes to indefinitely.

The system menu enumerates boot entries so you can restart directly into firmware or Windows Defender Offline Scan:

You'll need to fix bcdedit to resolve the issue with the System menu.

A busted BCD config? I re-installed Windows just last week with default settings...

If the system is booting correctly but bcdedit isn't working then there might be some issue with the partition:
https://superuser.com/questions/1261017/bcdedit-exe-refuses-to-open-system-store

That's exactly what I'm looking at right now. In any case, this isn't a SI bug. Sorry, should I close this?

OK, the problem has been resolved. Just followed the instructions on Minitool's site. Solutions 4 and 6 in particular, both in the Command Prompt of the Recovery Environment:

4. Set an Entry Point in BCD
Some users reported that the error can be solved by setting an entry point in BCD. It may seem strange but worth trying. Here’s how:
Step 1. Open the elevated Command Prompt window as we explained in the first solution.
Step 2. Type the following command and hit Enter. The /set command will set an entry point and enable the system to trust the Windows version that is not trusted by default.
bcdedit /set {current} Description “TheNameYouWant”

*Replaced {current} with {default} in the Recovery Environment

6. Rebuild BCD
If none of the above methods fix the “bcdedit: The boot configuration data store could not be opened” error, you can consider manually rebuilding BCD in WinRE. To do so, you need to use the Windows 10 media creation tool. Here’s how to do that:
Step 1. Plug the installation media into your computer and boot it from the media.
Step 2. Once started, click on Next > Repair your computer > Troubleshoot > Command Prompt in order.
Step 3. In the elevated Command Prompt window, type the following commands in order and hit Enter after each one.
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

bootrec /fixboot failed in my case, but every other command listed here worked.
bcdedit /enum works now, and it listed the in Registry!

Edit:...and it started failing again, when it worked just a while ago. I give up, Windows will give me a stroke.

Not fixed! I can fully reproduce the same hang except it's only a couple seconds long. Bcedit is normal on my end and it instantly enumarates the boot entries across my 3 disks. Using Windows 10 22H2.

The delay is very annoying.
Setting EnableShutdownBootMenu to 0 gets rid of the delay. Maybe you should lazy load the boot entries only as the user hovers on the shutdown boot menu, not every time one clicks on the 'System' menu.

Setting EnableShutdownBootMenu to 0 gets rid of the delay. Maybe you should lazy load the boot entries only as the user hovers on the shutdown boot menu, not every time one clicks on the 'System' menu.

It's already lazy initialized. Windows also caches boot entries in the HKEY_LOCAL_MACHINE\BCD00000000\Objects registry key and we just enumerate these registry keys to show the current boot entries.
If there's a delay it's because something is preventing Windows from caching the HKEY_LOCAL_MACHINE\BCD00000000\ keys.

I exported the registry key. Does it look normal?
BCD00000000_Objects.reg.txt

Edit:...and it started failing again, when it worked just a while ago. I give up, Windows will give me a stroke.

Found the problem...it turns out that having a cheap-@$$ Micro Center SD card with a UEFI boot entry (E.g Ventoy) is enough to hang bcdedit /enum.  It looks for every UEFI boot capable device in the NVRAM, it seems??
Not sure if the SD card's crappy read/write speed is to blame or Ventoy's EFI being borked...the BIOS sees and boots it.
https://superuser.com/questions/1017398/bcdedit-is-having-big-time-delay


Sample code to get bid price using wssclient

Can you show us some sample code which contains a filter to put bid price into a variable please?

from bitfinex import WssClient
import asyncio
def process_ticker(ticker_data):
if isinstance(ticker_data, list) and ticker_data[1] != 'hb':
bid_price = ticker_data[1][0]
print(f'bid price is {bid_price}')
mywss = WssClient()
mywss.start()
mywss.subscribe_to_ticker("BTCUSD", process_ticker)
this is an infinite loop to prevent the program from finishing
asyncio.get_event_loop().run_forever()


Somehow node::AtExit is not invoked

Example Addon Module gist
When I run a script that loads a module that registers atexit, the atexit is not invokes when the process ends when launched with VS code.
If I run the same command node run.js from the command line the atexit code is run.
I don't expect the script to not stop, so I don't think that this applies... https://github.com/Microsoft/vscode-node-debug/issues/1  although it looked similar.
I had put a breakpoint in the script, and as it was paused also attached visual studio and put a breakpoing in the atexit function, and it was not called, except when run from command line or visual studio (not visual code)

I do not plan to fix this in js-debug.


update docs for category page plugin

This is a super tiny pull request but I had to look at the implementation to figure out why it wasn't working for me.

Thanks for the work, but I'm going to be rewriting this joker and releasing a separate plugin. I'll change a lot and this will be removed from the Genesis theme.


How to automatically import  macros file?

@rktjmp I'm wondering how to make macros file available without using import-macros in each module/file?
For example, I have a :core.macros which defines some macros such as if-let, when-let.... I want those available through all modules without using import-macros. Is it possible?

Either the compilerEnv compiler option passed to setup or a plugin probably.
https://fennel-lang.org/api, see compilerEnv but how you define your macro and get it into that option is not obvious to me since there is a bit of a chicken and egg problem. I would first try and inject something simple into there, just a normal function, and see if I could make it work.
I think the example fennel plugin does something quite similar around missing syms, so that would be another route. You can hook onto parse-error I think and inject the symbol. Just be sure to return nil (I think) so other plugins continue to run.
You should be able to just add your plugin to the compiler plugins options in setup but not 100% sure how well that would work re: finding and loading the module etc.
I can't see the option immediately in the docs but I do just pass a plugins option internally, so perhaps it was undocumented but should be stable, it's just mirroring the --plugin option for the CLI.
https://github.com/rktjmp/hotpot.nvim/blob/64b64709f9fb25b7470012caa23f008b755e6284/fnl/hotpot/searcher/module.fnl#L73-L76
I would try to make that work with the fennel CLI then post back and we can look at how to configure hotpot to use it and any possible fixes needed.
Probably the Fennel chat would have some insights too, but primarily get a POC working with the CLI env - to be sure it's actually possible - and then it should be clear how to integrate that into Hotpot.

I'd be curious how you go with a plugin or compileEnv option first as I think that is cleanest and most "fennel"-ly, but it could also be possible to expose a hook, before I call compile, where you could get say, code opts and return code opts after making any modifications you want (in this case pre-pending (import/require-macros ...).
I actually thought about this a while a long while ago (#37) but no one else ever gave a reason to do the work, perhaps its worth revisiting. I can't promise a timeline on this though. Diagnostics might be a burden too.
If the plugin doesn't work, or is too difficult you could always fork for now until (or if?) hooks appear.
Just patch
https://github.com/rktjmp/hotpot.nvim/blob/64b64709f9fb25b7470012caa23f008b755e6284/fnl/hotpot/compiler.fnl#L46
with something like
fnl-code (read-file! fnl-path)
fnl-code (if (string.match fnl-path "some-path-i-know-is-my-code")
             (.. "(require-macros macro-file)" fnl-code)
             fnl-code)

I have a question as I am also interested on at least trying to implement something like this.

I think the example fennel plugin does something quite similar around missing syms, so that would be another route.

Where can I find that default plugin, and where is the plugins documentation for Fennel?
I have only found this, and it doesn't show any example.

I think I was mixing linter.fnl with perhaps some chatter on matrix.
I poked at it for a minute or two but not 100% sure it's possible to return code that the compiler should insert, vs just inspecting code the compiler saw. I would think the best chance is with symbol-to-expression but I don't think you can really modify what the symbol expands to.
I think andreyorst has some plugin that lets you use @ named variables or something which might have some pointers (again this is just from memory, probably from a year ago or so now). That's probably clearer cut though as you'd be probably just inserting a new mangling/sym, not trying to inject a list. I would probably ask upstream if it's even possible to return new code to inject.
This doesn't work but might be useful, as well as grepping for (utils.hook : to find calls.
;; file.fnl
;; fennel --plugin plug.fnl -c file.fnl
(fn a-scope-fn [] (print "this exists to help see the scope"))

(map-seq [1 2 3] #(print &1))

;; plug.fnl
(fn map-seq-fn [seq f]
  (icollect [_ v (ipairs seq)] (f v)))

(macro map-seq-macro [seq f]
  `(icollect [_ v (ipairs ,seq)] (,f v)))

(fn parse-error [...]
  ;; not the way, our code is valid, just unrunnable/uncompilable
  (print :parse-error (view [...])))

(fn assert-compile [cond msg ast something-called-reset]
  ;; seems this cant modifiy scope, see compiler.fnl:50, utils.fnl:358
  (print :assert-compile ast))

(fn symbol-to-expression [ast scope]
  ;; Doing this will get you a "tried to ref macro at runtime", possible pathway here.
  ; (print (view ast {:metamethod? false}))
  (match ast
    [:map-seq] (do
                (tset scope :macros :map-seq (fn [seq f] (list)))
                (print :map-seq-post-scope (view scope))))
  (values nil))

(fn call [ast scope ...]
  ; (print :call (view [ast] {:metamethod? false}))
  (match ast
    [[:map-seq]] (do
                   (tset scope :macros :map-seq (fn [seq f] (list)))
                   (print :map-seq-post-scope (view scope))))
  (values nil))

(fn chunk [ast? scope]
  ; undocumented, compiler.fnl compile-stream
  ; (print :xy (view ast?) (view scope))
  (match ast?
    [[:map-seq]] (do
                   (tset scope :macros :map-seq (fn [seq f] (list)))
                   (print :map-seq-post-scope (view scope)))))

{:name :magic-map-seq
 ; :call call
 :chunk chunk
 ; :symbol-to-expression symbol-to-expression
 ; :parse-error parse-error
 ; :assert-compile assert-compile
 :versions [:1.1.0]}

Did you get anywhere with the plugin idea?

Did you get anywhere with the plugin idea?

No, I couldn't find any way to make it work using plugins, so I scrapped the idea.

;; plugin.fnl

;; must define as function that returns a list
(fn map-seq-fn [seq f]
  `(icollect [_# v# (ipairs ,seq)] (,f v#)))

(fn call [ast scope ...]
  (match ast
    ;; match against symbol and capture arguments
    [[:map-seq] & other]
    ;; written as do for comment clarity
    (do
      ;; expand our macro as compiler would do, passing in capture arguments
      (local macro-ast (map-seq-fn (unpack other)))
      ;; now expand that ast again (this expands icollect etc, *other* macros)
      (local true-ast (macroexpand macro-ast))
      ;; change ast to match macro ast, note that we must
      ;; **modifiy** the ast, not return a new one, as we're
      ;; actually modifying the ast back in the compiler call-site.
      (each [i ex-ast (ipairs true-ast)]
        (tset ast i ex-ast))))
  ;; nil to continue other plugins
  (values nil))

{:name :magic-map-seq
 :call call
 :versions [:1.2.1]}

;; file.fnl
;; fennel --plugin plug.fnl -c file.fnl
(map-seq [1 2 3] #(print $))

-- fennel --plugin plugin.fnl -c file.fnl
local tbl_17_auto = {}
local i_18_auto = #tbl_17_auto
for __1_auto, v_2_auto in ipairs({1, 2, 3}) do
  local val_19_auto
  local function _1_(_241)
    return print(_241)
  end
  val_19_auto = _1_(v_2_auto)
  if (nil ~= val_19_auto) then
    i_18_auto = (i_18_auto + 1)
    do end (tbl_17_auto)[i_18_auto] = val_19_auto
  else
  end
end
return tbl_17_auto

# fennel --plugin plugin.fnl file.fnl
1
2
3

Will patch Hotpot to support custom plugins (should not be hard, just needs to pass through a {:plugins ...} option assuming that can be done via the fennel API.

Going to close this as IMO the plugin method is more precise than a hook that jams text everywhere but still open to that idea in the future. See cookbook for more details.

Here is the result of (print package.path):
/opt/homebrew/Cellar/luarocks/3.9.1/share/lua/5.4/?.lua;/opt/homebrew/share/lua/5.4/?.lua;/opt/homebrew/share/lua/5.4/?/init.lua;/opt/homebrew/lib/lua/5.4/?.lua;/opt/homebrew/lib/lua/5.4/?/init.lua;./?.lua;./?/init.lua;/Users/datwaft/.luarocks/share/lua/5.4/?.lua;/Users/datwaft/.luarocks/share/lua/5.4/?/init.lua

Here is the result of (print (. (require :fennel) :path)) (I couldn't use fennel.path as it doesn't exist):
./?.fnl;./?/init.fnl

A Lua file can be required without any problems but when I try to require a fennel file it fails.

Hi, I wanted to do something similar and was following the cookbook
in core.patch.fnl
(fn map-seq-fn [seq f]
  `(icollect [_# v# (ipairs ,seq)] (,f v#)))

(fn call [ast scope ...]
  (match ast
    ;; match against symbol and capture arguments
    [[:map-seq] & other]
    ;; written as do for comment clarity
    (do
      ;; expand our macro as compiler would do, passing in capture arguments
      (local macro-ast (map-seq-fn (unpack other)))
      ;; now expand that ast again (this expands icollect etc, *other* macros)
      (local true-ast (macroexpand macro-ast))
      ;; change ast to match macro ast, note that we must
      ;; **modifiy** the ast, not return a new one, as we're
      ;; actually modifying the ast back in the compiler call-site.
      (each [i ex-ast (ipairs true-ast)]
        (tset ast i ex-ast))))
  ;; nil to continue other plugins
  (values nil))

{:name :nyoom : call :versions [:1.2.1]}

And then I load the plugin as follows;
if pcall(require, "hotpot") then
	require("hotpot").setup({
		provide_require_fennel = true,
		enable_hotpot_diagnostics = false,
		compiler = {
			modules = {
				correlate = true,
			},
			macros = {
				env = "_COMPILER",
				compilerEnv = _G,
				allowGlobals = true,
				plugins = { "core.patch" },
			},
		},
	})
	require("core")
else
	print("Unable to require hotpot")
end

However it errors out on compilation with a stack overflow (even if I don't use map-seq-fn anywhere):
Clearing cacheError detected while processing /Users/shauryasingh/.config/nvim/init.lua:
E5113: Error while calling lua chunk: /Users/shauryasingh/.config/nvim/init.lua:69: module 'core' not found:Compile error in /Users/shauryasingh/.config/nvim/fnl/core/init.fnl:24:6
  stack overflow

      ^[[7m(import-macros {: command! : let! : set!} :macros)^[[0m

Yeah I think it's a dead end for the idea, it's not really upstream supported and only useful for adding small forms probably.
Probably I will add a hook interface that is similar to the api.make, where you can specify maybe some kind of pattern to match mod-name against and a function-handler, or you specify just functions in a list that are executed in sequence for every compile.
The handler would accept at least the code as a string and should return a string or ... (nil err)? or throw error? (nil err) would match luas normal module loading style.
Probably hooks can only be set at "setup" and not adjusted dynamically unless there is a good reason to support that.
(setup
  {...
  :hooks ["config.stuff" (fn [code {:macro? true|false : some : helpers?}]
                           (.. "(print :hi)" code))]})

(setup
  {...
  :hooks [(fn [modname code {:macro? : some : helpers?}]
            (if (= modname "config.stuff")
              (.. "(print :hi)" code))]})

Not sure if the key should be something more like {:hooks {:on-compile [...]} or just :on-compile [...] directly. :pre-proccess?
Any input on the actual usecase (eg vague pseudo code or descriptions) would be helpful.
There is some muck involved as the compiler has a few entry points that need to keep options separate (e.g the "main" compiler, api.make compiler, api.compile-string) but I have been meaning to clean that up anyway.

Looks good to me

Not sure if the key should be something more like {:hooks {:on-compile [...]}

I think just having :on-compile makes sense, I can't think of anywhere else you'd need a hook except when you're compiling.

Any input on the actual usecase (eg vague pseudo code or descriptions) would be helpful.

I personally would like my configuration macros to feel more "native", it's just a matter of convenience not having to import an autocmd! macro etc. Of course a cleaner way to do this would probably to have an additional macro that splats the rest of the macros in scope, but having hotpot handle feels cleaner to me
Similar to how aniseed appends (require-macros :macros) to every file before compiling it. It doesn't sound like the best way to go about it, which is why I was interested in using compiler plugins but as you said sounds like a dead-end :(

So there is a very beta option preprocessor now, in head (not in the tagged v0.6.0 release but in commits after it.)
It should be a function that accepts fnl-src for modification and a table that contains path (the file being compiled), modname, the modname if the file was required, otherwise it may be nil (eg during diagnostic compilation where the modname is not known!) and macro? which indicates whether the call is in the macro compiler env.
Since modname may be nil, its probably best to match on the path, which should generally be a full path, but also may be nil if a blank buffer has its ft=fennel set and diagnostics is enabled!
Not super happy with how its put together, but any changes will be posted here with some period of deprecation.
      :compiler {:modules {:correlate true}
                 :preprocessor (fn [src {: path : modname : macro?}]
                                 (print path modname (string.match path "config/nvim/"))
                                 (case (string.match path "config/nvim/")
                                   nil src
                                   _any (let [pre "(macro hello [] `(print :hello))"]
                                          (string.format "%s%s" pre src))))
                 :macros {:env :_COMPILER
                          :compilerEnv _G
                          :allowedGlobals false}}})


LoHa trained in Onetrainer don't work with error "ComfyUI execution error: self must be a matrix"

Expected Behavior
Should generate image with selected LoHa.
Actual Behavior
Image isn't generated, instead error "ComfyUI execution error: self must be a matrix"
Steps to Reproduce

Open SwarmUI
Choose SDXL model (in my case it was PonyXL)
Click generate model (using standard settings)
Error will appear

Debug Logs
https://paste.denizenscript.com/View/129211
Other
I am using personal LoHa trained in Onetrainer, it works with Automatic1111 and Forge, but gives error in SwarmUI. Found similar issue in OneTrainer  github "https://github.com/Nerogar/OneTrainer/issues/525".

oh, if it's a specific new custom trainable type and not a well known model variant, it might not yet be supported in ComfyUI (which is the backend that powers Swarm), so, yeah, that issue you linked will have to be resolved first.
Since you're doing custom training, I'd recommend just using a more well established model type

I just want to add, that I tried LoRa trained on same model in Onetrainer and it works, so if somebody have same issue, than solution is to retrain it to LoRa instead of LoHa.


Don't recursively generate files (or do other things that make plank slow when called once per schema)

Incremental builds are suffering since we need to call plank on all schemas whenever touching just one of them. Recreating any models invalidates all of them during our build.
There may be workarounds, but it would be simpler if we could afford to invoke plank once per schema (w.r.t. wall-clock time).

This has been solved by the --no_recursive flag


doc: fix docstring indentation and special characters

Summary

This PR cleans up some inconsistent docstrings to go from

to

Motivation

Author Checklist

[x] Changes are motivated and described in the PR description.
[x] Testing strategy is described if automated tests are not included in the PR.
[x] Documentation is updated if necessary.
[x] Status checks pass.
[x] If the version number is changed, it is updated in pyproject.toml , aineko/__init__.py, aineko/templates/first_aineko_pipeline/{{cookiecutter.project_slug}}/pyproject.toml.

Reviewer Checklist

[ ] Title is accurate and formatted appropriately.
[ ] No unnecessary changes are introduced.
[ ] Description motivates each change.
[ ] Docs are updated if necessary.
[ ] Code is pythonic and consistent with the rest of the codebase.
[ ] The code is consistent with the style guide.

@ricrosales or @craycrayfish
mkdocs still complains about:
INFO    -  The following pages exist in the docs directory, but are not included in the "nav" configuration:
             - aineko_dream.md


[hotfix][streaming] Report correct value of currentProcessingTime in the exception

This is a trivial logging change without test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Yes, good catch. Thanks for spotting this.

Thanks for the quick review @aljoscha. Will merge it with green travis.

Merged


Abort the run if a rate-limit error is hit

We should abort the run if a rate-limit error is hit. Currently, it ends up producing an empty CSV (or an emptier CSV than it would have), giving a false impression that there are fewer vulnerabilities than actually exist.

I don't think this is the case any more. It looks like it was probably fixed by #50 (Release 1.6.1).


Fix combine/styles/etc… using built files

Fixes #3114
Fixes #3104
Fixes #3099
Fixes #2961
Fixes #2907
Fixes #2624
I was gonna wait for v6.1 but the fix here was simple enough.

Turns out it was almost doing what it was supposed to but an eager glob that was running before the build finished caused the files to be dropped. Now we postpone that until the build finishes.
The more appropriate time would be after all assets are emitted instead which I might change in v6.1.


项目跑不起来

e: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errors
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/0464082e81de712709b8918eac577657/jetified-kotlin-stdlib-jdk7-1.6.10.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/06445d7ee3d674db365da5b7e383aeec/jetified-window-1.0.0-beta04-api.jar!/META-INF/window_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/2964b3bd074cce42cde0bddbdb8bb158/jetified-kotlin-stdlib-common-1.6.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/989d7c521cad3a1e2e82ee6a7a836f54/jetified-kotlinx-coroutines-android-1.5.2.jar!/META-INF/kotlinx-coroutines-android.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/9c675fcd73ec0913dfa5836b73d5959f/jetified-window-java-1.0.0-beta04-api.jar!/META-INF/window-java_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/cdd51607f1d98bcc689bce197d763afe/jetified-kotlin-stdlib-jdk8-1.5.30.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.15.
e: C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/ced2a85cd1d4e10ca7b42bb11579f9f7/jetified-kotlinx-coroutines-core-jvm-1.5.2.jar!/META-INF/kotlinx-coroutines-core.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.15.
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (50, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (53, 20): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (54, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (63, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (63, 18): Unresolved reference: startsWith
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (64, 23): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (75, 30): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (76, 25): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (82, 13): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (104, 25): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (105, 25): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (108, 31): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreview.kt: (119, 23): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewApp.kt: (14, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewApp.kt: (16, 29): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewFactory.kt: (16, 10): Class 'FilePreviewFactory' is not abstract and does not implement abstract base class member @NonNull public abstract fun create(@Nullable p0: Context?, p1: Int, @Nullable p2: Any?): PlatformView defined in io.flutter.plugin.platform.PlatformViewFactory
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewFactory.kt: (18, 5): 'create' overrides nothing
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (31, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (40, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (45, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (50, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (55, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (56, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (57, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (58, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (62, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (63, 13): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (64, 24): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (66, 37): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (68, 36): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (69, 36): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (74, 16): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (75, 20): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (78, 20): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\FilePreviewPlugin.kt: (83, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (17, 37): Unresolved reference: lazy
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (17, 49): Class 'kotlin.LazyThreadSafetyMode' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/LazyThreadSafetyMode.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (17, 70): Class 'kotlin.LazyThreadSafetyMode' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/LazyThreadSafetyMode.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (24, 23): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (28, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (32, 12): Unresolved reference: map[TbsCoreSettings.TBS_SETTINGS_USE_SPEEDY_CLASSLOADER]
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (32, 12): No set method providing array access
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (33, 12): Unresolved reference: map[TbsCoreSettings.TBS_SETTINGS_USE_DEXLOADER_SERVICE]
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (33, 12): No set method providing array access
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (34, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (35, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (40, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (41, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (42, 31): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (44, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (46, 24): Unresolved reference: map[TbsCoreSettings.TBS_SETTINGS_USE_SPEEDY_CLASSLOADER]
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (46, 24): No set method providing array access
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (47, 24): Unresolved reference: map[TbsCoreSettings.TBS_SETTINGS_USE_DEXLOADER_SERVICE]
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (47, 24): No set method providing array access
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (48, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (49, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (50, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (59, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\TbsManager.kt: (60, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (42, 29): Unresolved reference: lastIndexOf
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (46, 27): Unresolved reference: substring
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (55, 28): Unresolved reference: substring
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (55, 42): Unresolved reference: lastIndexOf
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (60, 22): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (64, 41): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (66, 26): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (79, 45): Unresolved reference: also
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (79, 58): Unresolved reference: it
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (80, 29): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (84, 34): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (86, 25): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (88, 30): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (91, 23): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (92, 30): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (95, 31): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (97, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (100, 30): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\FileUtils.kt: (102, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (35, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (52, 13): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (54, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (64, 27): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (65, 33): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (68, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (77, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (78, 21): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (80, 21): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (139, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (158, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (158, 47): Unresolved reference: java
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (159, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (159, 44): Unresolved reference: javaPrimitiveType
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (163, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (164, 17): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (167, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (169, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (171, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (173, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (175, 19): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.
The class is loaded from C:/Users/Administrator/.gradle/caches/transforms-2/files-2.1/29b23ea272c7f8f6ce1a3b6be919bcda/jetified-kotlin-stdlib-1.6.10.jar!/kotlin/Unit.class
e: C:\Users\Administrator\Desktop\file_preview\android\src\main\kotlin\com\gstory\file_preview\utils\UIUtils.kt: (214, 77): Unresolved reference: javaPrimitiveType
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':file_preview:compileDebugKotlin'.

Compilation error. See log for more details

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
┌─ Flutter Fix ────────────────────────────────────────────────────────────────────────────────┐
│ [!] Your project requires a newer version of the Kotlin Gradle plugin.                       │
│ Find the latest version on https://kotlinlang.org/docs/gradle.html#plugin-and-versions, then │
│ update C:\Users\Administrator\Desktop\file_preview\example\android\build.gradle:             │
│ ext.kotlin_version = ''                                                      │
└──────────────────────────────────────────────────────────────────────────────────────────────┘
Exception: Gradle task assembleDebug failed with exit code 1

本地kotlin版本与项目版本所需冲突


Stageless

Did a stab at implementing stageless. There is some cursed hairiness with ExclusiveSystem traits in bevy/iyes_loopless, so sorry for hairy code at places.
Note that this requires your state to be pre-initialized before AssetLoader, I think it's limitation of how iyes_loopless does State.

Fixed tests, whew that was fun.

Thanks, will fix the comments.

Should be good now :)

It looks like a cargo fmt --all run is missing.
If you've had enough of fighting with the CI, I could also merge the PR. The CI issues can still be fixed on the stageless branch. Just say the word :slightly_smiling_face:
Thank you for all the work!

Haha, it's fine, this is nothing like a CI at my day job.

Could you try adding --clean-per-run to the cargo hack command?

I also don't understand what's happening here. The test is green, but the process fails. Locally everything seems fine, too.
I will merge and take a look at the CI setup separately.
Thanks again for the implementation 👍


Serve assets directly using nginx

Hi
I'm not sure where to put this, but I notice that the assets where serve trough php, and that is too slow on environments with limited resources (Raspberry Pi). To improve the situation I added the following rule to my nginx host
    location /admin/resource/static {         try_files /vendor/philiplb/crudlex/src/static/$arg_file =404;     }
This will try to serve the assets directly from the filesystem without using php, this improve a lot the performance of the app.
Don't know where to put this in the documentation, so first want to ask the repo maintainer about his thoughts on this
The other idea is to serve the assets directly from a CDN, this will remove the burden for the server and also improve the speed. If you are interested in this route I can create the PR

Good idea. Maybe a chapter "Web Server Optimization" here might do it? https://github.com/philiplb/CRUDlex/blob/master/docs/manual/extendedfeatures.rst
I would investigate something similar for Apache. Should be doable by a rewrite rule.
And then two sub chapters: nginx and Apache.

This is online now in the manual: http://philiplb.github.io/CRUDlex/docs/html/0.12.0/manual/extendedfeatures.html#serving-static-content-via-the-webserver


Add support for py311

Ports of shapely PRs (by @jorisvandenbossche):

https://github.com/shapely/shapely/pull/1388
https://github.com/shapely/shapely/pull/1654
https://github.com/shapely/shapely/pull/1647

I am aiming for a maintenance release, just bumping to the next micro tag of GEOS (3.10.4) and add Py3.11 support.

For the versioneer issue, you can the same patch as we did in shapely:
https://github.com/shapely/shapely/blob/3a6f7b9eb99e0c0a5c3ee0bbbb5826ccbdb42fc8/setup.py#L12-L16

The last GEOS 3.11 fix seems to have broken the CI. I guess I didn’t port everything from your PRs- I’ll have a look tomorrow


OCM-10614 | feat: allow to verify error message for subsystem tests

OCM-10614
Change type

[ ] New feature
[x] Bug fix
[ ] Build
[ ] CI
[ ] Documentation
[ ] Performance
[x] Refactor
[x] Style
[ ] Unit tests
[x] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

is it useful to add function func (r *TerraformRunner) Output() RunOutput to test the terraform output?

is it useful to add function func (r *TerraformRunner) Output() RunOutput to test the terraform output?

Yeah, nothing uses it atm so I didn't include. But sure

/lgtm

/test rosa-hcp-private-critical-high-presubmit

/test rosa-hcp-private-critical-high-presubmit


Add submodules flags to README.md

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

I don't mind adding this but I am a little worried about complicating build steps unnnecessarily and that this documentation could easily go out-of-date.  Do we really think many OpenCL SDK builders will set any of these options to non-default values?  Should we link to the different submodule documentation instead?

Agreed with Ben and Closing PR.


Cannot import NDK Cache Nostr

import NDKCacheAdapterNostr from '@nostr-dev-kit/ndk-cache-nostr';

Error:
Cannot find module '@nostr-dev-kit/ndk-cache-nostr' or its corresponding type declarations.

npm install @nostr-dev-kit/ndk-cache-nostr

installation is successful. I think something is wrong with exports.


Fixed logout div in Sidebar

Fixes issue #134

Attach screenshots @Nikhil7174

Don't work on issues which are not assigned to you @Nikhil7174. First get yourself assigned and then only start working

This time, i am letting this go.. But take care from next time.

I will not do this mistake again.

In the description I have shared the ss which shows that when the shop button is active there is no underline in the logout button. Which was the original issue


Minor updates for correctness and missing info

Add the no-route constant for NO-ROUTE, 312 soft-error
Add a doc string for the Connection.Blocked reason argument
Change Confirm.Select nowait to use the no-wait domain, removing the need for the duplicated documentation

Thanks @gmr !


Roll Flutter Engine from 7651b3cba6ba to f3b784646f0c (2 revisions)

https://github.com/flutter/engine/compare/7651b3cba6ba...f3b784646f0c
2023-08-01<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from wIpcCOc0TtDYasQbl... to lwCo6le6r0X-Srvx3... (flutter/engine#44208)
2023-08-01<EMAIL_ADDRESS>Manual roll Dart SDK from a58ca112af1c to aca45d2e133c (2 revisions) (flutter/engine#44203)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from wIpcCOc0TtDY to lwCo6le6r0X-
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jonahwilliams@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


retrieve id on duplicate with one query

Hi,
I'm executing the following query:
insert into users (username, password) values("username","password") on duplicate key update password=values(password)

The table users has two fields, id (unique key auto incremented), username (unique text) and password
When this query is first executed I get back the inserted row id. But when the username already exists and so I just update the duplicate, I do not get back the id of that record. Is there any way to learn the id without having to execute one more query ??

I believe you cannot avoid the second query. You can see the MySQL documentation at https://dev.mysql.com/doc/refman/5.6/en/insert-on-duplicate.html for more information.


Update example to work locally

Without setting Master to "local" the example throws a SparkException "A master URL must be set in your configuration"
What changes were proposed in this pull request?
explicitly set SparkConf master to "local"
How was this patch tested?
Running the main method using Spark 2.3.1 without the change produces an exception. With the change, the main method executes without error.
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

This seems not a necessary fix. master can be configured via spark-submit argument --master, not a best practice to set it in code.


Passwords are been regenerated every time any server field has changed

I believe this bug appeared after I implemented the settings window.

I noticed this bug last week actually when I was working on getting a MySQL docker set up, prior to the settings window being implemented.