Session display name (sidebar) : ability to rename

Hello,
I often use multiple session to the same server. In the sidebar (at least on iPad) all the sessions have the server name, so it is difficult to navigate between the sessions. It would be very helpful if one can tap and hold on the session and set up an  additional title.
I.e.: I have a server called B2 and all my sessions are displayed as B2. I would like to have B2 – task one, B2 – task two and so on .
thanks
g

Hello @giulianozor 👋
Very good idea!
I'm planing it

Hey @giulianozor 👋
You can now try WebSSH 28.3.1463 with the ability to rename the session on the sidebar : https://testflight.apple.com/join/QSrBK59z
Best wishes,

@isontheline thanks, it semestre to work great !


pip install fails with 'ascii' codec issue

On linux, here is how it looks like:
(fluidsim) datahome/aponte% pip download pythran
Collecting pythran
  Downloading https://files.pythonhosted.org/packages/82/de/3a0afb468aa3d3a8a46f43d9619e7d620ae88103cef90e718e3d888863b5/pythran-0.9.0.tar.gz (6.7MB)
    100% |################################| 6.8MB 1.3MB/s
  Saved ./pythran-0.9.0.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-download-vrog1g4o/pythran/setup.py", line 174, in <module>
        long_description=longdescr("README.rst"),
      File "/tmp/pip-download-vrog1g4o/pythran/setup.py", line 165, in longdescr
        lines = list(readme)
      File "/home1/datahome/aponte/.miniconda3/envs/fluidsim/lib/python3.6/encodings/ascii.py", line 26, in decode
        return codecs.ascii_decode(input, self.errors)[0]
    UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128)

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-download-vrog1g4o/pythran/

Any idea where this is coming from?
Do you believe this post may solve the issue ?

Adjusting the environment prior to running the pip install fixes the issue:
setenv LC_ALL en_US.UTF-8

I had to use
export LC_ALL='c.UTF-8'


Logging UI V2 Output Sidebar

Users should see a list of outputs in the sidebar of chart options.  Users should be able to configure multiple outputs at the same time.

closing; duplicate of: https://github.com/rancher/dashboard/issues/1027


:bug: jake json output in cyclonedx not parsed

Exisiting jake.json in cyclonedx is not considered in the parser.

@manuel-sommer  We should be checking that CycloneDX files from tool vendors are actually valid per the spec before adjusting the CycloneDX parser. I just had a conversation with Steve Springett (person who created CycloneDX) about vendor tool support and his any my experience agree that vendors say "we output ClycloneDX" but the really output "CycloneDX-ish" files.
If I look at the the JSON unit test file for Jake at https://cyclonedx.github.io/cyclonedx-web-tool/validate, I get:

If it's not valid CycloneDX, it's probably better to create a Jake specific parser rather than make our CycloneDX parser parse invalid CycloneDX.
That validator above was the first online one I found - it may not be the best but I still think the CycloneDX parser should probably only parse valid versions and have vendor-specific parsers when the tool provides invalid formats.
I'll ask around and see if there's a better CycloneDX validator than that one I found online.

@manuel-sommer We should be checking that CycloneDX files from tool vendors are actually valid per the spec before adjusting the CycloneDX parser. I just had a conversation with Steve Springett (person who created CycloneDX) about vendor tool support and his any my experience agree that vendors say "we output ClycloneDX" but the really output "CycloneDX-ish" files.
If I look at the the JSON unit test file for Jake at https://cyclonedx.github.io/cyclonedx-web-tool/validate, I get:
If it's not valid CycloneDX, it's probably better to create a Jake specific parser rather than make our CycloneDX parser parse invalid CycloneDX.
That validator above was the first online one I found - it may not be the best but I still think the CycloneDX parser should probably only parse valid versions and have vendor-specific parsers when the tool provides invalid formats.
I'll ask around and see if there's a better CycloneDX validator than that one I found online.

@manuel-sommer i suggest a specific parser for Jake be implemented instead.

OK. I got curious and ran this official CycloneDX validator from https://github.com/CycloneDX/cyclonedx-cli against the unit test files at django-DefectDojo/unittests/scans/cyclonedx
$ for i in `ls *.json`
> do
> echo "Checking $i"
> ../../../../cyclonedx validate --input-file "$i"
> done
Checking cyclonedx_cwe.json
Unable to validate against any JSON schemas.
BOM is not valid.
Checking issue_8022.json
BOM validated successfully.
Checking issue_9277.json
BOM validated successfully.
Checking jake2.json
BOM validated successfully.
Checking jake.json
Unable to validate against any JSON schemas.
BOM is not valid.
Checking log4j.json
BOM validated successfully.
Checking nested-component-log4j.json
BOM validated successfully.
Checking valid-vulnerability-1.4.json
BOM validated successfully.

So the net result of that was these are valid:

issue_8022.json
issue_9277.json
jake2.json
log4j.json
nested-component-log4j.json
valid-vulnerability-1.4.json

And these are invalid:

cyclonedx_cwe.json
jake.json

I also repeated for XML with these results (all XML unit test files are valid)

cyclonedx_bom.xml
dd_1_15_0.xml
grype_dd_1_14_1.xml
grype.xml
jake.xml
log4j.xml
retirejs.latest.xml
spec1_lowfirst.xml
spec1.xml
valid-vulnerability-1.4.xml

@manuel-sommer So I love that you were fixing an issue with Jake's CycloneDX parser (Thanks for that :pray: ) but it looks like the right path forward is to:
(A) Look at jake.json and figure out how we got an invalid CycloneDX file as a unit-test file. I'd not spend a bunch of time on that but whatever is discovered either:

Remove jake.json and update related unit tests to use a valid file
Run Jake against something to generate a valid jake.json file and update the unit test to use this newly created json output.

2 is the best since we're sure we're getting recent & valid output from Jake. I have no clue how old/state jake.json is but that's one possibility.
(B) Remove the invalid json files and update the unit tests to use valid files instead.
Ideally, you could use the file generated in 2 above to replace the invalid ones as well. I've not had a chance to look at what unit tests use those invalid files but they'll need to be updated once the invalid JSON files are removed so they keep passing when getting called.

I removed jake.json. I don't think I will make a PR to support jake.json as there also exists a jake2.json file which is valid. Maybe, jake.json was an outdated version of jake.
Regarding cyclonedx_cwe.json I was not able to detect on why the schema is invalid. Furthermore, it would be an option to include cyclonedx-cli to validate cyclonedx directly on the input, but it has no python package. I found https://pypi.org/project/cyclonedx-editor-validator/ but that validator is inconsistent and does not look like being stable.

@manuel-sommer

I removed jake.json. I don't think I will make a PR to support jake.json as there also exists a jake2.json file which is valid. Maybe, jake.json was an outdated version of jake.
Regarding cyclonedx_cwe.json I was not able to detect on why the schema is invalid. Furthermore, it would be an option to include cyclonedx-cli to validate cyclonedx directly on the input, but it has no python package. I found https://pypi.org/project/cyclonedx-editor-validator/ but that validator is inconsistent and does not look like being stable.

Understandable about not making a separate Jake parser based on that invalid jake.json file.
I also didn't find a good Python equivalent to cyclonedx-cli in Python. Something we can do in the future.
So this PR now just removes that invalid jake.json file :+1:

@manuel-sommer Before we approve & merge this PR, would you mind removing the cyclonedx_cwe.json file and it's matching unit test so all the invalid CycloneDX files are removed in this PR?
See https://github.com/search?q=repo%3ADefectDojo%2Fdjango-DefectDojo cyclonedx_cwe.json&type=code

Done @mtesauro


feat(home): Update assets

Can you make these fishes less dead?

Optional: Can you make these fishes swim around the text instead of under the text?

Optional: Can you make these fishes swim around the text instead of under the text?

I pushed a commit that should somewhat resolve it for laptop screens, ill try to see what I can do for smaller screens in my other pr


Removing dotenv requirement

Gemspec is not defining dotenv dependency and I don't find any other reference to it, so requiring it fails right now.
I guess this might be originating from the cookiecutter project where it's actually included in the Gemfile.
(Sorry for all the PR's, but I'm unsure if these changes are welcome or not)

I'm still trying to get my head around Lamby and AWS Lambda in general, but why would I not just use Rails 6+ credentials for my environment configuration?
For my existing projects I use the figaro gem, so I'm not interested in having to add additional gems serving the same purpose.
I do understand the usage of dotenv in the cookiecutter project as you are starting from scratch and here it might make sense to showcase. But I think the Lamby gem should be serving existing as well as new projects and I don't see any other reference to the dotenv gem than this single line of code where it's included which is not showing why it should be needed in the first place? (compared to how existing apps might handle configurations already).

but why would I not just use Rails 6+ credentials for my environment configuration?

That is certainly an option for a lot of in app configs. But one failing of that is it will not work for DATABASE_URL and to use it you will still need the RAILS_MASTER_KEY loaded prior to boot. So if you now have at least these two and... often in times when people do use encrypted credentials that have ENV || Credentials patterns in place... you still need some system like Dotenv or Fiagro. About a year ago I the Lamby started tried to use Rails Credentials and because of the issues above, it got too complicated. Hence why we settled on Dotenv and SSM. Do you see another solution for the stater that is a little more simple?

I've only browsed through the code for SSM parameters and how you load it into a dotenv file. But it looks like you end up with all encrypted parameters etc. in clear text inside the final image file in a dotenv file? Is this correct understood?
I would suggest we just upload the master.key to the image (which you essentially already do while building the .lamby dir already). Then you can stick to Rails credentials without having to set RAILS_MASTER_KEY?
Again, I'm not suggesting not to use dotenv if that's your flavor, but why make Lamby dependent on it? Of course it's not a huge deal for the user to remove this one line of code after the generator has run, but it's not apparent that you need to do so. Else you should as minimum make dotenv a dependency in your gemspec file?
Personally I think it's better to support it as a flavor (like you do right now) but similar to how the lamby:ssm:dotenv is commented out in bin/_build right now, you could consider at least commenting out this line as well instead of removing it totally.
Right now this single line makes app.rb fail if you just install Lamby into a new Rails project that isn't including the dotenv gem.

in clear text inside the final image file in a dotenv file? Is this correct understood?

Correct. The ECR image is expected to be encrypted tho. Along with your build pipelines being secure.

I would suggest we just upload the master.key

That is one way. I make no guarantees on building that into an image tho. My assumption is that a) Rails has a default ignore on this file. We honor that. b) that your build system should not add the master key to the project.

Again, I'm not suggesting not to use dotenv if that's your flavor, but why make Lamby dependent on it?

I hear ya. But I think what we are doing is suggesting a convention that you can start with. Much like Rails itself can switch test systems, using any number of methods of for configs and environments. We actually call that out on this page (https://lamby.custominktech.com/docs/environment_and_configuration)... so I think the best I've been able to do now is to start with a simple implementation. One that has actually been exercised by myself and shown to be easier to use. I tried doing a lot of work around encrypted secrets and RAILS_MASTER_KEY... it all ended up being hard and required juggling multiple things. But it will work assuming you do it right.
For example, I would be very open to adding a section to that guide page that mentions alternate implementation. For example, one is to use our SSM wrapper PORO to load super secure credentials at the top of the app.rb file. For example:
ENV['DATABASE_URL'] = Lamby::SsmParameterStore.get!("/config/myapp/secure/DATABASE_URL")
ENV['RAILS_MASTER_KEY'] = Lamby::SsmParameterStore.get!('/config/myapp/secure/RAILS_MASTER_KEY')

Right now this single line makes app.rb fail if you just install Lamby into a new Rails project that isn't including the dotenv gem.

But same would be true if we anticipated SSM above. Hopefully the Lamby template files are the right starting point. Maybe we can comment them out, vs delete?

I've set database url via Rails credentials.
Right now I upload the master.key with the build (read: right now Lamby already upload the master.key intentionally or not) and it works fine. This means I don't have to use either Figaro or dotenv.
The master key should of course be set as an environment variable instead to ensure the image is secure.
I strongly believe Lamby should focus on it's core: mocking rack and supporting an easy SAM setup.
As you linked there's already plenty of documentation of how you could use dotenv if you wanted to.

I've set database url via Rails credentials.

Does that work? How do you load that ENV early enough in the Rails boot process for it to work? I could never get that to work in a handful of Rails versions.

I strongly believe Lamby should focus on it's core

Same, but we are forced to make some convention decisions for the starter. Since Lamby works with Rails 5.0 and up, one decision is to demonstrate basic setup that works for all Rails versions. I explored encrypted credentials heavily in both docs and personal use. Just ended up being too verbose.
What can we change with the guides to help this out? Open for ideas? Also, do let me know how you got DATABASE_URL working with encrypted credentials.

This is my config/database.yml file:
default: &default
  adapter: mysql2
  encoding: utf8
  pool: 50
  username: <%= Rails.application.credentials.dig(:database, :username) %>
  password: <%= Rails.application.credentials.dig(:database, :password) %>
  host: <%= Rails.application.credentials.dig(:database, :host) %>

development:
  <<: *default
  database: development

production:
  <<: *default
  database: production
  pool: 5

test:
  <<: *default
  database: test

No .dotenv, no figaro. Just Rails config.
Granted, I haven't tested this in Rails 5.x yet, but I'm gonna have to deal with that in the coming weeks.

OH POG! That's really cool.

Closing this issue. I'd like to keep Lamby's starter not using encrypted credentials with a basic SECRET_KEY_BASE in place to update as described here. https://lamby.custominktech.com/docs/environment_and_configuration#our-cookiecutter
With regard to Dotenv, I totally get how that could be easily removed and decoupled in favor of many other methods. However, I would like to leave it in since it seems to play well with other guides on using AWS_PROFILE for development and testing and other ENVs for those Rails groups without having to get docker compose involved. I did update the guides here (https://lamby.custominktech.com/docs/environment_and_configuration#using-dotenv-rails) to call out that our starter project is just that, a starter.


See if we can implement pipes now

We weren't able to do that in the past. Let's see if we find a way now

I wonder if this would be possible using something in System.IO.Pipes  AnonymousPipeServerStream? or something else

@Meir017 Chromium uses file descriptors 3 and 4 for pipes.
In the C# world, it would be something like an extra set of StandardInput, StandardOutput, which is something that .NET didn't support in 2018, see https://github.com/dotnet/runtime/issues/26559.

@kblok: I stumbled across this, and I'm wondering what the answer was. Did you figure out a way to implement this? Thanks!

Hey @mscottford, This is now supported through the Playwright driver.

Hi @kblok, could you please explain in more detail how and where it was implemented? I have zero knowledge about Playwright implementation but I'm also struggling with proper handling --remote-debugging-port switch from client side.
I'm also interested in the Windows named pipes approach. AFAIK the issue you're referring to is about Unix descriptors, isn't it?

Hey @seclerp!
This issue was created before playwright-dotnet started using playwright as a driver. playwright-dotnet knows opens a node process and talks to `playwright using stdin/stdout.
If you want to read about the limitations I found in .NET, this is the issue I created on dotnet/runtime.

I see, thanks! I ended up with the similar idea of making a wrapper over Chromium process in Rust. Do you maybe had a chance to work with large CDP payloads going through stdin/stdout? Let's say 1Mb+. Does it work out of the box?


[DC-529]  pylint fix on test module

modifying unit test module curation/unit_tests/data_steward/cdr_cleaner/cleaning_rules/rdr_observation_source_concept_id_suppression_test.py for a pylint fix

looks good to me-- passed the linting_checks!


log.io work

I'll merge this when I've got the log.io harvesters/servers going.

Ack, tried to build from master today and seems to hang on vagrant up stage.
Which branch is 'stable'?
On Tuesday, May 26, 2015, Aron Ahmadia<EMAIL_ADDRESS>wrote:

I'll merge this when I've got the log.io harvesters/servers going.
—
Reply to this email directly or view it on GitHub
https://github.com/memex-explorer/memex-explorer/pull/539#issuecomment-105711292
.

--
Lewis

"stable"?
Try:
git fetch
git checkout origin/master
vagrant reload
vagrant provision

Open an issue if anything's broken, master should be stable-ish.

Ok will try tomorrow I'm heading home
On Tuesday, May 26, 2015, Aron Ahmadia<EMAIL_ADDRESS>wrote:

"stable"?
Try:
git fetch
git checkout origin/master
vagrant reload
vagrant provision
Open an issue if anything's broken, master should be stable-ish.
—
Reply to this email directly or view it on GitHub
https://github.com/memex-explorer/memex-explorer/pull/539#issuecomment-105713595
.

--
Lewis

Great!  Expect significant fixes this evening.  I'm trying to stabilize everything for tomorrow AM.

This is ready for testing.

Who's that lone cowboy merging into master without review?


Add cron job to check for unverified users and delete them periodically

Just a heads up that this could end up becoming more convoluted than expected. We don't really have a good place to run a scheduled job like this per environment (unless we take a shortcut and use the Bastion).
In other containerized apps, we've used CloudWatch Events to schedule the invocation of ECS tasks within the existing ECS cluster.

@hectcastro does it reduce the complexity if its acceptable to run it on all app servers at once?

Sorry for the delayed response here.
I don't think so. Within a given service instance running on Fargate, there really isn't a way to tap into OS level facilities like cron. In other containerized app setups, we've setup CloudWatch Event rules (which can be expressed as cron expressions) to fire off downstream actions (e.g., invoke a Lambda function, run an ECS task, etc.). I think we'd have to do something similar to achieve this functionality here:

CloudWatch Event rules expression fires daily
That kicks off a management command-like ECS task that's run within the ECS cluster and does the necessary database grooming

Closed, but we should figure out how to handle unverified accounts


Updating script for VNet creation

The script for creating VNet is out-dated. Take a look at the script that Srdan Bozovic created here: https://raw.githubusercontent.com/Microsoft/sql-server-samples/master/samples/manage/azure-sql-db-managed-instance/delegate-subnet/delegateSubnet.ps1

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9b750921-0f6a-6de9-23d7-c40aa6a29ced
Version Independent ID: 71a46ea4-9d97-a05f-e8c9-a79b7dac1567
Content: PowerShell example - create a managed instance in Azure SQL Database - Azure SQL Database
Content Source: articles/sql-database/scripts/sql-database-create-configure-managed-instance-powershell.md
Service: sql-database
Sub-service: managed-instance
GitHub Login: @stevestein
Microsoft Alias: sstein

@JocaPC Thank you for the feedback.
This is being assigned to the content author to evaluate and update as appropriate.

I will work on this this week

@KalyanChanumolu-MSFT please assign to me

I'll take care of this but it's going to take me a bit!

@MashaMSFT Thanks! If you want to create an internal work item to track, we can close out the issue and plan this in the December sprint. I'm going to reassign to you for now. #reassign:MashaMSFT

Hi @rothja, sure that sounds good. I've created item (1646786) to track this work, and we can close this Git Issue.
Thanks Jovan!
Masha from the SQL Docs team
#please-close


feat: implementing ansys/actions/changelogs and adding release note in documentation

Implementing release note in documentation, using ansys/actions/changelogs and https://github.com/ansys/pyansys-geometry/pull/1138.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 63.75%. Comparing base (5677d57) to head (d332d77).

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #3019       +/-   ##
===========================================
- Coverage   86.67%   63.75%   -22.93%
===========================================
  Files          52       52
  Lines        9498     9498
===========================================
- Hits         8232     6055     -2177
- Misses       1266     3443     +2177

Is this still a draft? @clatapie

The changelog can be effective but I wanted to add some documentation about commit and branch name conventions. I also have planned to add the ansys/action that checks those names as pyansys-geometry does.

I will resume it next week

As the Contributing section in the PyAnsys dev guide details the naming conventions, adding the action should be enough to ensure a consistent changelog section.
Pinging @germa89 for visibility.

I realised that dependabot also has a prefix for the commits. You might need to adapt that one too.
https://github.com/ansys/pymapdl/blob/365563996bf10116ff3d0c2714fe364c39ac4b84/.github/dependabot.yml#L13

I realised that dependabot also has a prefix for the commits. You might need to adapt that one too.
https://github.com/ansys/pymapdl/blob/365563996bf10116ff3d0c2714fe364c39ac4b84/.github/dependabot.yml#L13

Good catch, thank you @germa89.
I modified the dependabot.yml file as follow:

for the pip package ecosystem: the prefix used is now build as it concerns external dependencies.
for the github-actions package ecosystem: the prefix used is now ci as it concerns CI configuration.

Do we have to change dependabot branch names too?
So far the branch names are something like dependabot/github_actions/actions-0bd1363a87 (https://github.com/ansys/pymapdl/pull/3175).
Shall we check how to change those names? or maybe skip that workflow for dependabot PRs?

As the ansys/action accepts dependabot/ as a branch name, there is no need to modify it.
Also, it seems that this name is not configurable.


Update scalafmt-core to 3.7.5

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.3 to 3.7.5
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (3.7.3).
You might want to review and update them manually.
docs/_layouts/default.html

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #438.


Russian translation added

Hi, $subj.
By the way, linkToMarkDown is not documented but present in code and translations.

Thanks for your translation! :+1:


recommended fix for static attributes doesn't seem to work

$ rubocop \
>   --require rubocop-rspec \
>   --only FactoryBot/AttributeDefinedStatically \
>   --auto-correct
Inspecting 1025 files
.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

1025 files inspected, no offenses detected

$ cat test/factories/info_pages.rb
FactoryBot.define do
  factory :info_page do
    organization

    title 'About US'
    body 'test'
  end
end

factory bot version: 4.11.1

https://github.com/thoughtbot/factory_bot/issues/1173 may help

@josh-m-sharpe were you able to sort this out with the issue I linked to?

If I read #1173 correctly, it suggests the recommended fix doesn't work unless your factories are n the 'correct' spec/ location.  This project uses test unit and my factories are in test/factories/
Also, I've already manually gone through and updated all my factories.

Got it. Thanks for getting back to me. There is a comment in #1173 about how to get the cop working with non-rspec suites, but I think the experience is a bit awkward for non-rspec users. Since we have #1173 to track that issue, I am going to close this one. Thanks for taking the time to open this!


Roll Packages from 5cc0a0160194 to bd8db0338261 (4 revisions)

https://github.com/flutter/packages/compare/5cc0a0160194...bd8db0338261
2024-08-08<EMAIL_ADDRESS>[flutter_markdown] Fix table column alignment (flutter/packages#7327)
2024-08-08<EMAIL_ADDRESS>[interactive_media_ads] Fix names of unit tests (flutter/packages#7336)
2024-08-07<EMAIL_ADDRESS>[url_launcher] Convert Linux to Pigeon (flutter/packages#7215)
2024-08-07<EMAIL_ADDRESS>Roll Flutter from 0a7f8af6d146 to d595e98d85ea (4 revisions) (flutter/packages#7334)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem<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://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


starter scenario update new layout

Hi @thecodester ,
this is an update on the starter scenario. Please publish this only, when @AnnikaGonnermann gives her go.
Thank you.
Best regards,
Merve

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: mervey45:x: Merve TemelMerve Temel 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.

Here is an update on the starter scenario

@mervey45 The email that you are committing with for the last few commits --<EMAIL_ADDRESS>-- is different than email of your account. That's why the PR shows you not having completed the CLA. Please adjust your Git client.

@mervey45 Could you please solve those conflicts and sign the CLA? Thank you.

Hi @thecodester ,
I updated my e-mail address in github (browser) and set it via command line. Do I need to do something else?
Best regards,
Merve

When you commit -- using the locally installed Git -- an email and name is attached to the commit. You can see this in your last commit to production: https://github.com/SAPDocuments/Tutorials/commit/f7c0f0bbe86d7d11908f11c78860b3932bc0d150.patch
This name and email are determined by your Git settings on your desktop. If you look at the installation instructions in my tutorial for authors, you will see this as one of the steps.
But if you sign into GitHub with an account with a different email address, then GitHub will not match the author of your commit (you but different email address) to your GitHub account.
So you must set you local Git settings with the same email address as your GitHub account.

Hi @thecodester,
I did this. I added<EMAIL_ADDRESS>as my primary e-mail address in my github account and also set it via command line in my local github settings. Before that I used the following e-mail address<EMAIL_ADDRESS>Do I need to do something else?
Best regards,
Merve

No, I think that's it -- as long as they match. I think locally you had a typo going to dsap.com.

Hi @MichaelCzcz,
can you mergen my changes. I also signed the CLA.
Thank you.
Best regards,
Merve


docs: docstring for encoders/nlp

@theUnkownName I'll merge this PR. The tests failed because it involves building so many images at one time and this process has run out of disk space on the GitHub instance.


Refine custom entity validations and improve unit conversions

This commit refines the validation of custom entity's state - ensuring it is not null, empty, undefined, or 'unknown'. It also revamps unit conversion functions for better accuracy and precision, specifically the conversion to power and optimizing conversions for kilowatt units in InverterModel.Solis. These changes enhance the representational accuracy and clarity of data.
fixes: #322

@slipx06 the isNaN wasn't properly doing what is was intended. the || was defaulting to the right true whenever the left was falsey, so it would always return true in most cases, it was changed only to nullish ?? so that it only defaults to the right hand side IF the value is null.

Ok I see the issue there, thanks

If you could please test the last commit

If you could please test the last commit

Working perfectly from what I can tell, will be 100% sure tomorrow when the sun comes up.

okay this change didn't fix it, will investigate what the diff between this and mine are now.

@slipx06 okay this pr works (including your recent commits), master doesn't as well as latest release doesn't.

Great will merge

@slipx06 one thing I have noticed now is that I have some weird unit conversions. Are you seeing the same?

@Pho3niX90 Have not noticed. The only change was kw ->w and mw ->kw if values are <1. What are you seeing?

@Pho3niX90 Have not noticed. The only change was kw ->w and mw ->kw if values are <1. What are you seeing?

It seems it might have just been my local dev branch that was incorrectly locally merged with the changes. Resetting it to head fixed the issue.


Bokeh Comms

This PR fixes bokeh comms to retain the order of objects to update fixing issues with colormaps not updating correctly. Additionally the callbacks are also updated and now work with the dev release of bokeh and should be compatible with the upcoming v0.11 release.

Ready for merge, was pretty straightforward.

I'll trust you on this one!
We don't have proper bokeh testing, so I can't rely on the fact that tests are passing (see #334). I'll merge now that you say it is ready.


Select a folder

Thank for your amazing package. It works great.
I read the document but I did not see how to select a folder.
Can you tell me is there has a chance to select a folder?
Thank for any help.

+1 Would love to know, too.

@pacificsoftdevld Pass true as 2nd param to assignBrowse:
.assignBrowse(domNodes, isDirectory) Assign a browse action to one or more DOM nodes. Pass in true to allow directories to be selected (Chrome only). See the note above about using an HTML span instead of an actual button.

resumableRelativePath: The file's relative path when selecting a directory (defaults to file name in all browsers except Chrome).


Is this still maintained?

Hey folks, there was no update for 1 1/2 months and there are 8 open pull requests. Are you guys looking for maintainers by any chance?

@SargoDarya Actually yeah I think so. I was too lazy to handle this but I'll make some time and do something with it...! But yeah if there's anyone who can help, that would be great.

I'd be keen to contribute, how do I get involved?

So sorry for your inconvinience! We've started a brand new implementation of this plugin at next branch. Please wait just a bit more! It would be great if you can give us the feedback for the next branch implementation though! Please join Vuex ORM slack channel and hit me!

Finally, YES IT IS!
The brand new Axios plugin is here! It's very different from what it was, so please check out the docs!
I'll be closing this issue since the library is quite different now. Please feel free to open another issue if there's anything!


Set iOS deployment target back to 8.0

In pr #19 the deployment target was changed to 8.3. I'm assuming that happened by mistake. It won't allow building the framework towards older versions anymore. This pull request reverts the change and sets it again to 8.0.

You're right, I think this was a mistake. However we should be changing this on master now as I have merged swift-2.0 into master a few days ago. I will make the changes

Release 0.9 should be good to go now. Thanks for pointing out the issue @MattesGroeger

Awesome, thanks!


Add optional MessagePack-based media type

MessagePack can represent everything JSON can and more, and it's a much more efficient format. Unfortunately it's not easily readable by humans.
Since MessagePack itself isn't registered, the corresponding Micro API media type would be unregistered as well.
application/x-micro

This could be an optional media type which can be negotiated.

Done https://github.com/micro-api/micro-api/commit/d950a6e6c46a1b7eb73ba2b19499382bf50bb945.


Fix bounds checking error when parsing WWW-Authenticate field

Without the fix:
swift test --filter TestURLProtectionSpace.test_createWithInvalidAuth
Test Suite 'Selected tests' started at 2024-10-11 21:04:24.085
Test Suite 'TestURLProtectionSpace' started at 2024-10-11 21:04:24.095
Test Case 'TestURLProtectionSpace.test_createWithInvalidAuth' started at 2024-10-11 21:04:24.095
Swift/StringIndexValidation.swift:143: Fatal error: Substring index is out of bounds

^C*** Signal 5: Backtracing from 0xffff95642744... failed ***

With the fix:
Test Suite 'Selected tests' started at 2024-10-11 21:19:30.602
Test Suite 'TestURLProtectionSpace' started at 2024-10-11 21:19:30.612
Test Case 'TestURLProtectionSpace.test_createWithInvalidAuth' started at 2024-10-11 21:19:30.612
Test Case 'TestURLProtectionSpace.test_createWithInvalidAuth' passed (0.005 seconds)
Test Suite 'TestURLProtectionSpace' passed at 2024-10-11 21:19:30.617
	 Executed 1 test, with 0 failures (0 unexpected) in 0.005 (0.005) seconds
Test Suite 'Selected tests' passed at 2024-10-11 21:19:30.617
	 Executed 1 test, with 0 failures (0 unexpected) in 0.005 (0.005) seconds

@swift-ci please test

CI failure seems unrelated to my changes.
/Users/ec2-user/jenkins/workspace/swift-corelibs-foundation-PR-macOS/branch-main/swift-corelibs-xctest/Sources/XCTest/Public/XCTestMain.swift:21:23: error: no such module 'SwiftFoundation'
    @_exported import SwiftFoundation
                      ^

note: Using global toolchain override 'Xcode Default'. (in target 'SwiftXCTest' from project 'XCTest')
** BUILD FAILED **

The following build commands failed:
	CompileSwift normal arm64 (in target 'SwiftXCTest' from project 'XCTest')
	SwiftCompile normal arm64 Compiling\ XCTestObservationCenter.swift,\ IgnoredErrors.swift,\

@shahmishal can we get macOS CI turned off on this repo? We don’t build swift-corelibs-foundation for macOS

Agree macOS failure looks unrelated, not unique to this PR


Laravel5/install: remove composer update

Even in local or dev, just composer install ?
It seems preferable that all developers share the same versions, but please refuse the PR if necessary.

Funny thing, I do the same change locally few days ago ;)


Error while running code

I'm facing an error while running your code :
Here is a snippet of it: (Occurs right after I enter mobile number and it requests for otp)
HTTPSConnectionPool(host='cdn-api.co-vin.in', port=443): Max retries exceeded with url: /api/v2/auth/generateMobileOTP (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1108)')))
Exiting Script'
Please help!! :(

Seems like a duplicate of: #17


Gen and Tonic

Fixes #84 and #85.
I've decided to include these as part of the test suite (because you're right, they are very valuable) and link to them in the README as further reading.

:boat:


Only match single quoted strings on the same line

Per a conversation on Discord
The current match type allows single quoted strings to span multiple lines. This causes a problem in LDMud which allows lambda that start with a single quote, example:
funcall(symbol_function('transfer), a,b)
Although this syntax technically isn't for LDMud, both can be accomidated by changing the string.quoted.single.lpc scope to only match on a single line as suggested by @gesslar here

This looks good. Again I'll mention being sleep deprived and will merge later.


Support u128 and i128 behind unstable Cargo.toml flag for nightly users.

In this PR

Added support for i128 and u128. Since this is an unstable feature in
Rust, this is hidden behind the feature unstable which you have to
explicitly opt into in your Cargo.toml file.

:+1: Nothing I can complain about here.

@hellow554  should be fixed once we move to the next rand version; cc https://github.com/AltSysrq/proptest/issues/107


Version 1.1.5 don't work with Vue.js v1.0.17

With the last update 2016-03-08 the tab content don't appear. I'm using Windows 7 and Chrome 49.0.2623.75

This is also happening with me.

I am using Windows 10, and in an attempt to solve the issue I've updated Chrome from version 48 (not sure of the minor version) to 49.0.2623.75. It didn't resolve the issue. I hope there is an easy and fast fix, as I'm using the tool a lot... Thank you.

More news: if I follow the "Manual Installation" instructions from the README, the extension works.
I can see the new "vuex getter" and "router-view" features. :+1: I'm happy I can use vue-devtools again.
I wonder why the installation from Chrome Web Store is failing...

This is also happening for me on Win7 with vue v1.0.16, on Chrome 9.0.2623.75 m.

+1
This is also happening with me

@jbruni @wdmtech @einice I followed "The manual installation". The extension is working now.
But the installation from Web Store don't work

@lincolnbrito All right

Manual installation fixed it for me too :) Cheers for the suggestion, @jbruni and @lincolnbrito :)

Just another +1 for broken devtools after 1.1.5 update. Just following the manual steps from @jbruni now. Hopefully @yyx990803 can shed some light on this soon..

Manual installation works fine but it's broken otherwise for me.

Same issue here on OSX / Chrome 40.0.2564.109

Packing the extension works too, so here is a packed version to tide everyone over until it's fixed.
vue-devtools.zip

Oops, fixed in 1.1.6.


NXP i.MX RT600 DTS peripheral ranges Fix

I am working on a board port and ran into an issue with reworking the memory layout to use FlexSPI Port A.      The Board for the RT685-EVK maps the base of Flash to 0x18000000.   Using a QSPI device on FlexSPI a requires an address of 0x0800000.    When I made the necessary changes in the device tree overlay in the board files,   I noticed in the .map file that the base address of flash would always be 0x50000000.    After some digging, I found the peripheral node in rt6xx.dtsi:
/ {
soc {
sram: sram@30018000 {
ranges = <0x20180000 0x30180000 0x300000>;
};
    peripheral: peripheral@50000000 {
        ranges = <0x0 0x50000000 0x10000000>;
    };
};

};
It looks like this is limiting my ability to set my base address of flash.    If I make a change such as:
peripheral: peripheral@50000000 {
ranges = <0x0 0x00000000 0x60000000>;
};
};
The range allows my flash to be placed at 0x08000000
I am able to patch my device tree with an overlay but It would be nice to get this upstream.  I first would like to understand any possible implications of opening up the peripheral range.  I could submit a pull request once this is sorted out.

Note:     There is discussion here on the topic with a KCONFIG workaround:
https://github.com/zephyrproject-rtos/zephyr/discussions/40091


Add module name expansion during completion

Since version 2.1, merlin has this "smart" completion feature:
    - "smart" (a.k.a "do what I mean") completion:
          `L.m` will expand to `List.map ; List.m... ; ListLabels.map ; ...` if
          `L` doesn't exist.

I don't know if this could be added in this extension of in the ocaml-language-server. But it's a nice feature to have.
Emacs:

VScode:

Interesting. I don't see any reason we couldn't add that. I think it would be a good idea to have an option to allow enabling or disabling it though. Is it used by default in the emacs mode?

It is used by default in emacs with the company-mode. company-mode is one of the 3 or 4 emacs completion backends that are supported by merlin. So the situation may be a big different with the other backends. But as far as I know, they all support this by default. I don't know if it can be turned on and off by a parameter in merlin's protocol.


2016.09.13 cherry picks

Cherry-picks from 9-13. Please disregard PR #26572 which was opened erroneously.
@thaJeztah @SvenDowideit @vdemeester PTAL. CC @riyazdf

One note, otherwise LGTM

LGTM, thanks!


[Cosmos] Upgrade "proxy-agent" to v4 from v3

Azure DevOps scanned and complained of this compromised dependency "netmask" pulled in by cosmos.

Hence, updating the "proxy-agent" library to the latest and ran rush update --full.

Looks like the test failures are not Cosmos related and are coming from Identity
@sadasant Are you aware of any issues in the master branch for Identity that would cause this?
@zfoster, @southpolesteve, Can you review this PR at the earliest?

@ramya-rao-a @HarshaNalluru perf-identity tests can't run yet because they depend on msal-node-extensions. Would the re be a reason this PR runs perf-identity tests and other PRs do not? 🤔 I think I'm missing something.

The Identity (not perf-identity) issue seems related to the error name change, but I have yet to reproduce it locally. I'll be back in a bit with more info.

@HarshaNalluru Why are the Identity perf tests getting triggered for this PR?

@ramya-rao-a identity unit tests are failing here..

Possibly, because of the msal upgrade from 1.4.8 to 1.4.9, pinged @sadasant offline to figure out the cause/fix it.
perf unit test is blocked because of @azure/identity unit test failure and perf step is being run newly because of the change in the rush toolchain in the repro related to the impacted-by flag.
Honestly, it would just be "skipped" even if the unit test command is run for the perf project.

We worked on this earlier and both Harsha and I were able to see this issue go away by doing a rush update --full on a fresh copy of master 🤔 but then it seem to have failed again here: https://github.com/Azure/azure-sdk-for-js/pull/14644 - we're still on it.

@HarshaNalluru Don't we have to include the changes to the lock file? That is causing the cosmos build to fail

I thought I did that! Pushed a new commit.

/azp run js - core - ci


Update README.md

Please fix my grammar

Maybe split yatopia and lag plugin into 2 seperated sections??

I'll do it when I have time, so...

Well, I think they should be in the same sector.


Hiding volume and mute button on Mobile

Maybe someone can help. I can't hide the volume and mute buttons for a specific breakpoint. I tried JS with media queries like so but it doesn't seem to work. Thanks!

It may not be the best way but I have been creating two different players - one for small use and one for bigger. It is easy enough to select different players if using bootstrap for example depending on the screen size, e.g the below would only show the player for size xs and sm

<audio class="js-playersm">
            <source src="https://cdn.plyr.io/static/demo/Kishi_Bashi_-_It_All_Began_With_a_Burst.mp3" /></audio>

It may not be the best way but I have been creating two different players  ```

Thanks a lot! Could you share the JS snippet for that too? Not quite sure how to set a class for js script

Try this js (they will both look the same as I wrote them but here you have js-playersm and js-player:  You can omit some buttons from one or the other or do other stuff. As I said this may not be the best way, and there was some other discussion about fixing the responsiveness and overlapping of controls at small sizes but this works for me
//Big width
document.addEventListener('DOMContentLoaded', () => {
  const player = Plyr.setup('.js-player', {
    controls: ['restart', 'rewind', 'play', 'fast-forward', 'progress', 'current-time', 'duration', 'mute', 'volume', ],
  });
});

//Small width
document.addEventListener('DOMContentLoaded', () => {
  const player = Plyr.setup('.js-playersm', {
    controls: ['restart', 'rewind', 'play', 'fast-forward', 'progress', 'current-time', 'duration', 'mute', 'volume', ],
  });
});

Thanks a lot!

Try this```

Any chance you know of a way to reposition the buttons in the player? I'm trying to make it more suitable for podcast, which usually has central play button and forward/rewind buttons below.

Not 100% sure what you mean nor am I am expert -- but the order of the buttons is determined by the order of the controls listed (see above).
video can have a central button in the poster image so look at that code perhaps if that is what you mean

Not 100% sure what you mean nor am I am expert -- but the order of the buttons is determined by the order of the controls listed (see above).
video can have a central button in the poster image so look at that code perhaps if that is what you mean

Yes mainly my question was about reordering the buttons, I didn't realize that ordering them in the code does it. Thats neat! Thank you very much.
I was also thinking if there is a way to send some buttons on the new line, like 1st line is play buttons, second line is long progress bar.

I was also thinking if there is a way to send some buttons on the new line, like 1st line is play buttons, second line is long progress bar.

Well I would like that so maybe someone else would help. It would get around a lot of problems with responsiveness and overlapping controls too

See the below link for splitting controls over two lines, but it is a substantial hack - perhaps someone can suggest something simpler
https://codepen.io/patriferra/pen/VwLvdKP

Wow this looks promising and just what I was looking for. Thanks a lot!!!
Gonna give it a try

See the below link for splitting controls over two lines, but it is a substantial hack - perhaps someone can suggest something simpler
https://codepen.io/patriferra/pen/VwLvdKP

Success, now it works. But now I'm struggling with removing the restart and mute button from this code. As soon as I remove it, the player stops working. Any ideas?

Maybe someone can help. I can't hide the volume and mute buttons for a specific breakpoint. I tried JS with media queries like so but it doesn't seem to work. Thanks!

Just use @media in css
@media screen and (max-width: 500px) {
  .plyr .plyr__controls button[data-plyr=pip],
  .plyr .plyr__controls button[data-plyr=mute],
  .plyr .plyr__controls button[data-plyr=volume] {
    display: none;
  }
}

@media screen and (max-width: 500px) {
  .plyr .plyr__controls button[data-plyr=pip],
  .plyr .plyr__controls button[data-plyr=mute],
  .plyr .plyr__controls button[data-plyr=volume] {
    display: none;
  }
}

Wow , amazing and so simple, just what I needed! Thanks a lot, I would never figure this out.


Experimental rewrite: Es6 modules, BigInt, (un)parsing and validation

#245 and as well as some of the work we're doing over at https://github.com/bcoe/proposal-standard-module-uuid have had me playing around with what this module might look like if it was rewritten using modern ES features (ES6 modules, BigInt) and with a UUID class for parsing/unparsing and validation.
This is the work-in-progress result.  (Posting this mostly because my laptop's logic board decided to crap out and enough work went into it I'd rather not risk losing it while dealing with Apple repair process.)
Feel free to comment, with the caveat that I don't have a concrete plan (yet) for merging to master here.

how far off is this from landing :D

@DarylThayil: As noted, there's no set plan for landing this.  This is just a my take on what the codebase for this [9-year old module] would look like if it was updated to leverage new and coming language features.  I don't know that there's a lot of demand for this, either.  While it does address a few of the longer-running issues we've had with uuid (ES6 modules, parsing, validation support), none of those are critical.
Probably the biggest issue with this branch is the use of BigInt.  It's not supported on Safari or Edge, nor is there a suitable polyfill for it that I'm aware of.

to be honest a standalone ESM rewrite would do wonders (without the bigint changes, as they should probably be delivered separately).
if there's no plan to at least do the ESM side of things im tempted to fork for now.
in its current state, uuid can't be consumed by es modules AFAIK and can't be used in TS projects targeting ESM.
i'd personally go as far as saying this needs to be split into a node-only build and a browser-build, possibly in separate repos.

@43081j @DarylThayil @dstaley:
Sorry for taking such a long time but we have finally released<EMAIL_ADDRESS>which features native ESModules-Support for the browser:
npm install<EMAIL_ADDRESS>
The master branch README already reflects the API of v7.0.0.
It would be awesome to get feedback from you if this release works well for you.


[FEATURE] Sentiment Analysis using Deep Learning

Description
I want to add the feature of Sentiment Analysis using Deep Learning with better accuracy. I will try to build a better neural network that tries to do sentiment analysis.
Please assign it to me.
Screenshots
No response
Additional information
No response

Status of your work @Garvit414

My exams are going on, so it gets delayed, but I will do it ASAP.
Please understand @Rakesh9100
Sorry for the delay.

Okay @Garvit414


Move repository to libktx organization

Blocked by Maven Central procedures.

Could try jcenter \bintray, heard it's much better for those

More convenient, less accessible. Other repositories might require explicit declarations in Gradle/Maven config files.

I wouldn't consider adding jcenter() or even an external repo noticeably less accessible (it's a simple one liner). Maybe it's less discoverable though from the web?
But I think most just look at the readme, copy and paste what you have.
At least that's what I do, so I don't care what repository any library uses

Some companies do care, although these probably wouldn't consider KTX (or LibGDX, for that matter). Anyway, I don't mind waiting for the permission - once you set it up, it's relatively painless.


SDXL Lora training failing even with square images dataset/captions: RuntimeError: Error(s) in loading state_dict for UNet2DConditionModel:         Missing key(s) in state_dict:

I installed kohya-ss with ease but have had a hard time creating the dataset to get training start on sdxl model. I'm triying to use the dreamturbo model as well as base sdxl model for this with no luck. I have 58 1024x0124 images and the captions are just tags given by tagger in kohya-ss. I've tried the beginner as well as advanced lora training as well. I am on windows 10 executed from powershell with admin privileges. I've tried adam8 optimizer first with no luck so it is lion here I can change that back though. My dataset is in data/train/3_zkz/(images.jpg/png).
Here are my config details:
pretrained_model_name_or_path = "C:/Users/socie/Documents/newui/new_ComfyUI_windows_portable_nvidia_cu121_or_cpu/ComfyUI_windows_portable/ComfyUI/models/checkpoints/sd_xl_base_1.0.safetensors"
train_data_dir = "C:/Users/socie/Downloads/data/train"
resolution = "1024,1024"
enable_bucket = true
min_bucket_reso = 256
max_bucket_reso = 1024
output_name = "aki"
output_dir = "./output"
save_model_as = "safetensors"
save_every_n_epochs = 2
max_train_epochs = 10
train_batch_size = 1
network_train_unet_only = false
network_train_text_encoder_only = false
learning_rate = 0.0001
unet_lr = 0.0001
text_encoder_lr = 0.00001
lr_scheduler = "cosine_with_restarts"
optimizer_type = "Lion"
lr_scheduler_num_cycles = 1
network_module = "networks.lora"
network_dim = 8
network_alpha = 32
logging_dir = "./logs"
caption_extension = ".txt"
shuffle_caption = true
keep_tokens = 0
max_token_length = 255
seed = 1337
prior_loss_weight = 1
clip_skip = 2
mixed_precision = "fp16"
save_precision = "fp16"
xformers = true
cache_latents = true
persistent_data_loader_workers = true
lr_warmup_steps = 0
no_half_vae = true
Here is the error I got:
16:55:53-891443 INFO     Training started with config file / 训练开始，使用配置文件:
C:\users\socie\Downloads\lora-scripts\config\autosave\20240610-165553.toml
16:55:53-894442 INFO     Task 12c7214c-d92d-46a4-85f0-1c18877aa2c9 created
2024-06-10 16:56:01 INFO     Loading settings from                                                    train_util.py:3744
C:\users\socie\Downloads\lora-scripts\config\autosave\20240610-165553.to
ml...
INFO     C:\users\socie\Downloads\lora-scripts\config\autosave\20240610-165553    train_util.py:3763
2024-06-10 16:56:01 INFO     prepare tokenizer                                                        train_util.py:4227
INFO     update token length: 255                                                 train_util.py:4244
INFO     Using DreamBooth method.                                               train_network.py:172
INFO     prepare images.                                                          train_util.py:1572
INFO     found directory C:\Users\socie\Downloads\data\train\3_zkz contains 58    train_util.py:1519
image files
INFO     174 train images with repeating.                                         train_util.py:1613
INFO     0 reg images.                                                            train_util.py:1616
WARNING  no regularization images / 正則化画像が見つかりませんでした              train_util.py:1621
INFO     [Dataset 0]                                                              config_util.py:565
batch_size: 1
resolution: (1024, 1024)
enable_bucket: True
network_multiplier: 1.0
min_bucket_reso: 256
max_bucket_reso: 1024
bucket_reso_steps: 64
bucket_no_upscale: False
                           [Subset 0 of Dataset 0]
                             image_dir: "C:\Users\socie\Downloads\data\train\3_zkz"
                             image_count: 58
                             num_repeats: 3
                             shuffle_caption: True
                             keep_tokens: 0
                             keep_tokens_separator:
                             secondary_separator: None
                             enable_wildcard: False
                             caption_dropout_rate: 0.0
                             caption_dropout_every_n_epoches: 0
                             caption_tag_dropout_rate: 0.0
                             caption_prefix: None
                             caption_suffix: None
                             color_aug: False
                             flip_aug: False
                             face_crop_aug_range: None
                             random_crop: False
                             token_warmup_min: 1,
                             token_warmup_step: 0,
                             is_reg: False
                             class_tokens: zkz
                             caption_extension: .txt

                INFO     [Dataset 0]                                                              config_util.py:571
                INFO     loading image sizes.                                                      train_util.py:853

100%|████████████████████████████████████████████████████████████████████████████████| 58/58 [00:00<00:00, 9664.29it/s]
INFO     make buckets                                                              train_util.py:859
INFO     number of images (including repeats) /                                    train_util.py:905
各bucketの画像枚数（繰り返し回数を含む）
INFO     bucket 0: resolution (1024, 1024), count: 174                             train_util.py:910
INFO     mean ar error (without repeats): 0.0                                      train_util.py:915
INFO     preparing accelerator                                                  train_network.py:225
accelerator device: cuda
INFO     loading model for process 0/1                                            train_util.py:4385
INFO     load StableDiffusion checkpoint:                                         train_util.py:4341
C:/Users/socie/Documents/newui/new_ComfyUI_windows_portable_nvidia_cu121
_or_cpu/ComfyUI_windows_portable/ComfyUI/models/checkpoints/sd_xl_base_1
.0.safetensors
INFO     UNet2DConditionModel: 64, 8, 768, False, False                        original_unet.py:1387
Traceback (most recent call last):
File "C:\users\socie\Downloads\lora-scripts\sd-scripts\train_network.py", line 1117, in
trainer.train(args)
File "C:\users\socie\Downloads\lora-scripts\sd-scripts\train_network.py", line 234, in train
model_version, text_encoder, vae, unet = self.load_target_model(args, weight_dtype, accelerator)
File "C:\users\socie\Downloads\lora-scripts\sd-scripts\train_network.py", line 101, in load_target_model
text_encoder, vae, unet, _ = train_util.load_target_model(args, weight_dtype, accelerator)
File "C:\users\socie\Downloads\lora-scripts\sd-scripts\library\train_util.py", line 4387, in load_target_model
text_encoder, vae, unet, load_stable_diffusion_format = _load_target_model(
File "C:\users\socie\Downloads\lora-scripts\sd-scripts\library\train_util.py", line 4342, in _load_target_model
text_encoder, vae, unet = model_util.load_models_from_stable_diffusion_checkpoint(
File "C:\users\socie\Downloads\lora-scripts\sd-scripts\library\model_util.py", line 1008, in load_models_from_stable_diffusion_checkpoint
info = unet.load_state_dict(converted_unet_checkpoint)
File "C:\users\socie\Downloads\lora-scripts\venv\lib\site-packages\torch\nn\modules\module.py", line 2153, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for UNet2DConditionModel:
Missing key(s) in state_dict: "down_blocks.0.attentions.0.norm.weight", "down_blocks.0.attentions.0.norm.bias", "down_blocks.0.attentions.0.proj_in.weight", "down_blocks.0.attentions.0.proj_in.bias", "down_blocks.0.attentions.0.transformer_blocks.0.attn1.to_q.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn1.to_k.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn1.to_v.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn1.to_out.0.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn1.to_out.0.bias", "down_blocks.0.attentions.0.transformer_blocks.0.ff.net.0.proj.weight", "down_blocks.0.attentions.0.transformer_blocks.0.ff.net.0.proj.bias", "down_blocks.0.attentions.0.transformer_blocks.0.ff.net.2.weight", "down_blocks.0.attentions.0.transformer_blocks.0.ff.net.2.bias", "down_blocks.0.attentions.0.transformer_blocks.0.attn2.to_q.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn2.to_k.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn2.to_v.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn2.to_out.0.weight", "down_blocks.0.attentions.0.transformer_blocks.0.attn2.to_out.0.bias", "down_blocks.0.attentions.0.transformer_blocks.0.norm1.weight", "down_blocks.0.attentions.0.transformer_blocks.0.norm1.bias", "down_blocks.0.attentions.0.transformer_blocks.0.norm2.weight", "down_blocks.0.attentions.0.transformer_blocks.0.norm2.bias", "down_blocks.0.attentions.0.transformer_blocks.0.norm3.weight", "down_blocks.0.attentions.0.transformer_blocks.0.norm3.bias", "down_blocks.0.attentions.0.proj_out.weight", "down_blocks.0.attentions.0.proj_out.bias", "down_blocks.0.attentions.1.norm.weight", "down_blocks.0.attentions.1.norm.bias", "down_blocks.0.attentions.1.proj_in.weight", "down_blocks.0.attentions.1.proj_in.bias", "down_blocks.0.attentions.1.transformer_blocks.0.attn1.to_q.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn1.to_k.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn1.to_v.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn1.to_out.0.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn1.to_out.0.bias", "down_blocks.0.attentions.1.transformer_blocks.0.ff.net.0.proj.weight", "down_blocks.0.attentions.1.transformer_blocks.0.ff.net.0.proj.bias", "down_blocks.0.attentions.1.transformer_blocks.0.ff.net.2.weight", "down_blocks.0.attentions.1.transformer_blocks.0.ff.net.2.bias", "down_blocks.0.attentions.1.transformer_blocks.0.attn2.to_q.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn2.to_k.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn2.to_v.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn2.to_out.0.weight", "down_blocks.0.attentions.1.transformer_blocks.0.attn2.to_out.0.bias", "down_blocks.0.attentions.1.transformer_blocks.0.norm1.weight", "down_blocks.0.attentions.1.transformer_blocks.0.norm1.bias", "down_blocks.0.attentions.1.transformer_blocks.0.norm2.weight", "down_blocks.0.attentions.1.transformer_blocks.0.norm2.bias", "down_blocks.0.attentions.1.transformer_blocks.0.norm3.weight", "down_blocks.0.attentions.1.transformer_blocks.0.norm3.bias", "down_blocks.0.attentions.1.proj_out.weight", "down_blocks.0.attentions.1.proj_out.bias", "down_blocks.2.downsamplers.0.conv.weight", "down_blocks.2.downsamplers.0.conv.bias", "down_blocks.3.resnets.0.norm1.weight", "down_blocks.3.resnets.0.norm1.bias", "down_blocks.3.resnets.0.conv1.weight", "down_blocks.3.resnets.0.conv1.bias", "down_blocks.3.resnets.0.time_emb_proj.weight", "down_blocks.3.resnets.0.time_emb_proj.bias", "down_blocks.3.resnets.0.norm2.weight", "down_blocks.3.resnets.0.norm2.bias", "down_blocks.3.resnets.0.conv2.weight", "down_blocks.3.resnets.0.conv2.bias", "down_blocks.3.resnets.1.norm1.weight", "down_blocks.3.resnets.1.norm1.bias", "down_blocks.3.resnets.1.conv1.weight", "down_blocks.3.resnets.1.conv1.bias", "down_blocks.3.resnets.1.time_emb_proj.weight", "down_blocks.3.resnets.1.time_emb_proj.bias", "down_blocks.3.resnets.1.norm2.weight", "down_blocks.3.resnets.1.norm2.bias", "down_blocks.3.resnets.1.conv2.weight", "down_blocks.3.resnets.1.conv2.bias", "up_blocks.2.attentions.0.norm.weight", "up_blocks.2.attentions.0.norm.bias", "up_blocks.2.attentions.0.proj_in.weight", "up_blocks.2.attentions.0.proj_in.bias", "up_blocks.2.attentions.0.transformer_blocks.0.attn1.to_q.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn1.to_k.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn1.to_v.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn1.to_out.0.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn1.to_out.0.bias", "up_blocks.2.attentions.0.transformer_blocks.0.ff.net.0.proj.weight", "up_blocks.2.attentions.0.transformer_blocks.0.ff.net.0.proj.bias", "up_blocks.2.attentions.0.transformer_blocks.0.ff.net.2.weight", "up_blocks.2.attentions.0.transformer_blocks.0.ff.net.2.bias", "up_blocks.2.attentions.0.transformer_blocks.0.attn2.to_q.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn2.to_k.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn2.to_v.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn2.to_out.0.weight", "up_blocks.2.attentions.0.transformer_blocks.0.attn2.to_out.0.bias", "up_blocks.2.attentions.0.transformer_blocks.0.norm1.weight", "up_blocks.2.attentions.0.transformer_blocks.0.norm1.bias", "up_blocks.2.attentions.0.transformer_blocks.0.norm2.weight", "up_blocks.2.attentions.0.transformer_blocks.0.norm2.bias", "up_blocks.2.attentions.0.transformer_blocks.0.norm3.weight", "up_blocks.2.attentions.0.transformer_blocks.0.norm3.bias", "up_blocks.2.attentions.0.proj_out.weight", "up_blocks.2.attentions.0.proj_out.bias", "up_blocks.2.attentions.1.norm.weight", "up_blocks.2.attentions.1.norm.bias", "up_blocks.2.attentions.1.proj_in.weight", "up_blocks.2.attentions.1.proj_in.bias", "up_blocks.2.attentions.1.transformer_blocks.0.attn1.to_q.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn1.to_k.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn1.to_v.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn1.to_out.0.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn1.to_out.0.bias", "up_blocks.2.attentions.1.transformer_blocks.0.ff.net.0.proj.weight", "up_blocks.2.attentions.1.transformer_blocks.0.ff.net.0.proj.bias", "up_blocks.2.attentions.1.transformer_blocks.0.ff.net.2.weight", "up_blocks.2.attentions.1.transformer_blocks.0.ff.net.2.bias", "up_blocks.2.attentions.1.transformer_blocks.0.attn2.to_q.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn2.to_k.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn2.to_v.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn2.to_out.0.weight", "up_blocks.2.attentions.1.transformer_blocks.0.attn2.to_out.0.bias", "up_blocks.2.attentions.1.transformer_blocks.0.norm1.weight", "up_blocks.2.attentions.1.transformer_blocks.0.norm1.bias", "up_blocks.2.attentions.1.transformer_blocks.0.norm2.weight", "up_blocks.2.attentions.1.transformer_blocks.0.norm2.bias", "up_blocks.2.attentions.1.transformer_blocks.0.norm3.weight", "up_blocks.2.attentions.1.transformer_blocks.0.norm3.bias", "up_blocks.2.attentions.1.proj_out.weight", "up_blocks.2.attentions.1.proj_out.bias", "up_blocks.2.attentions.2.norm.weight", "up_blocks.2.attentions.2.norm.bias", "up_blocks.2.attentions.2.proj_in.weight", "up_blocks.2.attentions.2.proj_in.bias", "up_blocks.2.attentions.2.transformer_blocks.0.attn1.to_q.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn1.to_k.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn1.to_v.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn1.to_out.0.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn1.to_out.0.bias", "up_blocks.2.attentions.2.transformer_blocks.0.ff.net.0.proj.weight", "up_blocks.2.attentions.2.transformer_blocks.0.ff.net.0.proj.bias", "up_blocks.2.attentions.2.transformer_blocks.0.ff.net.2.weight", "up_blocks.2.attentions.2.transformer_blocks.0.ff.net.2.bias", "up_blocks.2.attentions.2.transformer_blocks.0.attn2.to_q.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn2.to_k.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn2.to_v.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn2.to_out.0.weight", "up_blocks.2.attentions.2.transformer_blocks.0.attn2.to_out.0.bias", "up_blocks.2.attentions.2.transformer_blocks.0.norm1.weight", "up_blocks.2.attentions.2.transformer_blocks.0.norm1.bias", "up_blocks.2.attentions.2.transformer_blocks.0.norm2.weight", "up_blocks.2.attentions.2.transformer_blocks.0.norm2.bias", "up_blocks.2.attentions.2.transformer_blocks.0.norm3.weight", "up_blocks.2.attentions.2.transformer_blocks.0.norm3.bias", "up_blocks.2.attentions.2.proj_out.weight", "up_blocks.2.attentions.2.proj_out.bias", "up_blocks.2.upsamplers.0.conv.weight", "up_blocks.2.upsamplers.0.conv.bias", "up_blocks.3.attentions.0.norm.weight", "up_blocks.3.attentions.0.norm.bias", "up_blocks.3.attentions.0.proj_in.weight", "up_blocks.3.attentions.0.proj_in.bias", "up_blocks.3.attentions.0.transformer_blocks.0.attn1.to_q.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn1.to_k.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn1.to_v.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn1.to_out.0.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn1.to_out.0.bias", "up_blocks.3.attentions.0.transformer_blocks.0.ff.net.0.proj.weight", "up_blocks.3.attentions.0.transformer_blocks.0.ff.net.0.proj.bias", "up_blocks.3.attentions.0.transformer_blocks.0.ff.net.2.weight", "up_blocks.3.attentions.0.transformer_blocks.0.ff.net.2.bias", "up_blocks.3.attentions.0.transformer_blocks.0.attn2.to_q.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn2.to_k.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn2.to_v.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn2.to_out.0.weight", "up_blocks.3.attentions.0.transformer_blocks.0.attn2.to_out.0.bias", "up_blocks.3.attentions.0.transformer_blocks.0.norm1.weight", "up_blocks.3.attentions.0.transformer_blocks.0.norm1.bias", "up_blocks.3.attentions.0.transformer_blocks.0.norm2.weight", "up_blocks.3.attentions.0.transformer_blocks.0.norm2.bias", "up_blocks.3.attentions.0.transformer_blocks.0.norm3.weight", "up_blocks.3.attentions.0.transformer_blocks.0.norm3.bias", "up_blocks.3.attentions.0.proj_out.weight", "up_blocks.3.attentions.0.proj_out.bias", "up_blocks.3.attentions.1.norm.weight", "up_blocks.3.attentions.1.norm.bias", "up_blocks.3.attentions.1.proj_in.weight", "up_blocks.3.attentions.1.proj_in.bias", "up_blocks.3.attentions.1.transformer_blocks.0.attn1.to_q.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn1.to_k.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn1.to_v.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn1.to_out.0.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn1.to_out.0.bias", "up_blocks.3.attentions.1.transformer_blocks.0.ff.net.0.proj.weight", "up_blocks.3.attentions.1.transformer_blocks.0.ff.net.0.proj.bias", "up_blocks.3.attentions.1.transformer_blocks.0.ff.net.2.weight", "up_blocks.3.attentions.1.transformer_blocks.0.ff.net.2.bias", "up_blocks.3.attentions.1.transformer_blocks.0.attn2.to_q.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn2.to_k.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn2.to_v.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn2.to_out.0.weight", "up_blocks.3.attentions.1.transformer_blocks.0.attn2.to_out.0.bias", "up_blocks.3.attentions.1.transformer_blocks.0.norm1.weight", "up_blocks.3.attentions.1.transformer_blocks.0.norm1.bias", "up_blocks.3.attentions.1.transformer_blocks.0.norm2.weight", "up_blocks.3.attentions.1.transformer_blocks.0.norm2.bias", "up_blocks.3.attentions.1.transformer_blocks.0.norm3.weight", "up_blocks.3.attentions.1.transformer_blocks.0.norm3.bias", "up_blocks.3.attentions.1.proj_out.weight", "up_blocks.3.attentions.1.proj_out.bias", "up_blocks.3.attentions.2.norm.weight", "up_blocks.3.attentions.2.norm.bias", "up_blocks.3.attentions.2.proj_in.weight", "up_blocks.3.attentions.2.proj_in.bias", "up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_q.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_k.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_v.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_out.0.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn1.to_out.0.bias", "up_blocks.3.attentions.2.transformer_blocks.0.ff.net.0.proj.weight", "up_blocks.3.attentions.2.transformer_blocks.0.ff.net.0.proj.bias", "up_blocks.3.attentions.2.transformer_blocks.0.ff.net.2.weight", "up_blocks.3.attentions.2.transformer_blocks.0.ff.net.2.bias", "up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_q.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_k.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_v.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_out.0.weight", "up_blocks.3.attentions.2.transformer_blocks.0.attn2.to_out.0.bias", "up_blocks.3.attentions.2.transformer_blocks.0.norm1.weight", "up_blocks.3.attentions.2.transformer_blocks.0.norm1.bias", "up_blocks.3.attentions.2.transformer_blocks.0.norm2.weight", "up_blocks.3.attentions.2.transformer_blocks.0.norm2.bias", "up_blocks.3.attentions.2.transformer_blocks.0.norm3.weight", "up_blocks.3.attentions.2.transformer_blocks.0.norm3.bias", "up_blocks.3.attentions.2.proj_out.weight", "up_blocks.3.attentions.2.proj_out.bias", "up_blocks.3.resnets.0.norm1.weight", "up_blocks.3.resnets.0.norm1.bias", "up_blocks.3.resnets.0.conv1.weight", "up_blocks.3.resnets.0.conv1.bias", "up_blocks.3.resnets.0.time_emb_proj.weight", "up_blocks.3.resnets.0.time_emb_proj.bias", "up_blocks.3.resnets.0.norm2.weight", "up_blocks.3.resnets.0.norm2.bias", "up_blocks.3.resnets.0.conv2.weight", "up_blocks.3.resnets.0.conv2.bias", "up_blocks.3.resnets.0.conv_shortcut.weight", "up_blocks.3.resnets.0.conv_shortcut.bias", "up_blocks.3.resnets.1.norm1.weight", "up_blocks.3.resnets.1.norm1.bias", "up_blocks.3.resnets.1.conv1.weight", "up_blocks.3.resnets.1.conv1.bias", "up_blocks.3.resnets.1.time_emb_proj.weight", "up_blocks.3.resnets.1.time_emb_proj.bias", "up_blocks.3.resnets.1.norm2.weight", "up_blocks.3.resnets.1.norm2.bias", "up_blocks.3.resnets.1.conv2.weight", "up_blocks.3.resnets.1.conv2.bias", "up_blocks.3.resnets.1.conv_shortcut.weight", "up_blocks.3.resnets.1.conv_shortcut.bias", "up_blocks.3.resnets.2.norm1.weight", "up_blocks.3.resnets.2.norm1.bias", "up_blocks.3.resnets.2.conv1.weight", "up_blocks.3.resnets.2.conv1.bias", "up_blocks.3.resnets.2.time_emb_proj.weight", "up_blocks.3.resnets.2.time_emb_proj.bias", "up_blocks.3.resnets.2.norm2.weight", "up_blocks.3.resnets.2.norm2.bias", "up_blocks.3.resnets.2.conv2.weight", "up_blocks.3.resnets.2.conv2.bias", "up_blocks.3.resnets.2.conv_shortcut.weight", "up_blocks.3.resnets.2.conv_shortcut.bias".
Unexpected key(s) in state_dict: "down_blocks.1.attentions.0.transformer_blocks.1.attn1.to_k.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn1.to_out.0.bias", "down_blocks.1.attentions.0.transformer_blocks.1.attn1.to_out.0.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn1.to_q.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn1.to_v.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn2.to_k.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn2.to_out.0.bias", "down_blocks.1.attentions.0.transformer_blocks.1.attn2.to_out.0.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn2.to_q.weight", "down_blocks.1.attentions.0.transformer_blocks.1.attn2.to_v.weight", "down_blocks.1.attentions.0.transformer_blocks.1.ff.net.0.proj.bias", "down_blocks.1.attentions.0.transformer_blocks.1.ff.net.0.proj.weight", "down_blocks.1.attentions.0.transformer_blocks.1.ff.net.2.bias", "down_blocks.1.attentions.0.transformer_blocks.1.ff.net.2.weight", "down_blocks.1.attentions.0.transformer_blocks.1.norm1.bias", "down_blocks.1.attentions.0.transformer_blocks.1.norm1.weight", "down_blocks.1.attentions.0.transformer_blocks.1.norm2.bias", "down_blocks.1.attentions.0.transformer_blocks.1.norm2.weight
16:56:06-165346 ERROR    Training failed / 训练失败

loading SDXL into the non-SDXL trainer so make sure it's using the SDXL version (sdxl_train_network.py)


add SIP-keypairs-des-128

@oday0311 this looks promising as an option for storing keys differently--is it something you want to push forward with a PR + adjustments to the SIP?

before we can proceed with code review, can you address my comments to the sip? once we resolve these comments and merge the sip we would love to look more into your code.

Thanks for your SIP proposal. In order to process the SIP, the SIP Editor requires write access to the forked repository in order to change the status and add additional information.
Could you please grant write access on the forked repository to the following GitHub  account:
@Eis-D-Z
Once this has been completed, we can move the proposal to draft.

@Eis-D-Z invite you , please check


LocalAI Supoort

Please add support to https://localai.io/

Dont have time to add this, but open to PRs.


Handle multiple alertmanagers

In order to handle network partitions and down machines, it would be helpful if Prometheus could be given multiple alertmanagers it can talk to, so that if the one it picks doesn't respond in a timely fashion (or fails), it could try one of the others.

We are about to start more detailed planning of a highly available Alertmanager. This will also involve Prometheus being aware of all Alertmanagers for the scenario you described.
The latter alone is not the full story so this will certainly take a while.
How urgent is your use case?

Only medium-term. I'm in the middle of creating a prometheus proof-of-concept, and noticed this when I was setting up the cluster.

It's right on top of our list. Keep an eye on the mailing list if you are interested – a design doc might be posted there sooner or later.

This request was implemented as #1699 and released as version 0.2.0.
Suggest we close this issue?


Added dynamic dns guide.

A simple DuckDNS guide that should help new engineers.

will take a look at it, as soon as i can understand why the pipeline failed.

Also please pull the latest master before any changes so it can fetch the latest changes

Added your changes; let me know anything else you'd like.

all seems fine, i will merge later today to a test branch first as i want to make some changes also

Merged to test.
Will make some adjustments on the website itself and release everything

Deployed


swc typescript parser includes commented out code leading to malformed output

Input:
// type Foo = "Oops";
const Link = "Boo";

Output:
var Link = 'Boo';ps";

Closing as I can't reproduce this with master branch of swc, and test about comment passes.
https://github.com/swc-project/swc/blob/631eff9e8cd33c51700609ccd709a7d68d132e9d/ecmascript/codegen/src/stmt.rs#L110-L118
I also verified that npx swc emits valid file. See https://github.com/kdy1/swc-example/blob/master/inputs/issue-197/issue-197.ts
It results in
// type Foo = "Oops";
var Link = 'Boo';

//# sourceMappingURL=issue-197.js.map


MIVisionX develop build is failing because of missing README.md file

@kiritigowda @samjwu : I think the tot is not installing because of the following error
CMake Error at cmake_install.cmake:46 (file):
file INSTALL cannot find "./MIVisionX/docs/README.md": No
such file or directory.

closed by https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/pull/1072


[Bug/Question] Indexes / new Datatypes with MySQL 5.6.34

Hi,
after solving the first problem, here the next one :)
Since Laravel 5.4 uses utf8mb4 each user with mysql <=5.7.(*/7) will see the following error message(s) while running the migrate command:
[Illuminate\Database\QueryException]
  SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter table `users` add unique `users_email_unique`(`email`))

  [PDOException]
  SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

Question / Possible Solutions:

Should we check for the current mysql version --> if version <= 5.7 then add Schema::defaultStringLength(191); as described in the laravel documentation

Here we have to check, is it mysql / mariadb / postgres - not sure if we generate here some overhead ( like my modified seeds ;) )

Manipulate the database config and change the current charset to utf8

Here we should check, if utf8mb4 is defined - if not, keep it as it is

keep it as it is and add some lines to the installation instructions

Also, the datatype "json" is not available in 5.6.34

Honestly I'd prefer the third option: keep it as it is and add some lines to the installation instructions
I'm not willing to go through such hassle at the mean time, the bare minimum requirements for this package currently (and mostly once it's stable also) is PHP 7.0+, Laravel 5.4+, MySQL 5.7+ 😄

Maybe a new section, something like "Requirements" or so should be enough.
I'm trying to upgrade my local mysql (from mamp) to 5.7.
But i think, we can close this now :)
Thanks for the feedback :)


Merge cmusatyalab/master into master.

What does this PR do?
Where should the reviewer start?
How should this PR be tested?
Any background context you want to provide?
What are the relevant issues?
[You can link directly to issues by entering # then the
number of the issue, for example, #3 links to issue 3]
Screenshots (if appropriate)
Questions:

Do the docs need to be updated?
Does this PR add new (Python) dependencies?

Make sure this updates local branch with the other one. I had to swap auto-generated branch merge options (base was mine and head was theirs). Also the order of the commits was reverse when the PR was being created.


Add Telemetry

See for ideas: https://hexdocs.pm/quantum/telemetry.html#content

Borrow ideas from realtime: https://github.com/supabase/realtime/blob/main/lib/realtime/telemetry/logger.ex


Submodule

This PR has the tests fixed.
I've implemented the submodule feature. The basic work flow seems to work fine: init/status/commit/report. But more tests are very welcome.
Now there is a distinction between the git repo itself (the .git dir in most cases), and the working tree root. Instead of cat ".git", now the work tree root is obtained by open the repository and asking for the working tree root. If I'm missing something please let me know.
Please keep in mind that I just started with golang.
Comments and ideas are more than welcome.

Coverage increased (+0.002%) to 66.53% when pulling b1dc95c448eda7acc4e260a845b7311aec6005b1 on acuarica:submodule into f39c40cdc7afbcc5320e9c614cb7f358803eaaf5 on git-time-metric:submodule.

Thanks Luis.  I appreciate the contribution.  I'm going to merge this into the submodule branch.  I have some changes I'd like to make.  I'll create another PR so you can review them and we can adjust further as needed.


Mastering Python - Second Edition: heading: Useless warnings – How to ignore them safely #1

I do not understand how that code works ?
Where and why and how should I use this.
def _ignore_warning(function):
    @functools.wraps(function)
    def __ignore_warning(*args, **kwargs):
        # Execute the code while catching all warnings
        with warnings.catch_warnings(record=True) as ws:
            # Catch all the warnings of the given type
            warnings.simplefilter('always', warning)
            # Execute the function
            result = function(*args, **kwargs)

        # re-warn all warning beyond the expected count
        if count is not None:
            for w in ws[count:]:
                warnings.warn(w.message)

        return result

    return __ignore_warning

return _ignore_warning

@ignore_warning(DeprecationWarning, count=1)
def spam():
    warnings.warn('deprecation 1', DeprecationWarning)
    warnings.warn('deprecation 2', DeprecationWarning)

with warnings.catch_warnings(record=True) as ws:
    spam()
    for i, w in enumerate(ws):
        print(w.message)

If you are importing code from an external library that is expected to give a warning, this can help you filter out that specific warning without disabling all warnings.


better distinction between Object and dynamic types

Signed-off-by: Harald Fassler<EMAIL_ADDRESS>A proposal (draft) for a step towards better distinction between types of java.lang.Object and dynmic types.
More tests need to be added.

@paulk-asert
Hello Paul,
while working on tests, I stumbled once more over this method:
@Override
    public void visitCatchStatement(final CatchStatement cs) {
        resolveOrFail(cs.getExceptionType(), cs);
        if (ClassHelper.isDynamicTyped(cs.getExceptionType())) {
            cs.getVariable().setType(ClassHelper.make(Exception.class));
        }
        super.visitCatchStatement(cs);
    }

see https://github.com/nineninesevenfour/groovy/blob/93ad2a577c6facc3f5620fd4a6c8167daa43ee74/src/main/java/org/codehaus/groovy/control/ResolveVisitor.java#L1561
And I asked myself if the type shouldn't rather be coerced to Throwable.class than Exception.class to catch unchecked exceptions, too? 🤔
What do you think?
Thank you!
Harald

@paulk-asert
Hello Paul,
while working on tests, I stumbled once more over this method:
@Override
    public void visitCatchStatement(final CatchStatement cs) {
        resolveOrFail(cs.getExceptionType(), cs);
        if (ClassHelper.isDynamicTyped(cs.getExceptionType())) {
            cs.getVariable().setType(ClassHelper.make(Exception.class));
        }
        super.visitCatchStatement(cs);
    }

see https://github.com/nineninesevenfour/groovy/blob/93ad2a577c6facc3f5620fd4a6c8167daa43ee74/src/main/java/org/codehaus/groovy/control/ResolveVisitor.java#L1561
And I asked myself if the type shouldn't rather be coerced to Throwable.class than Exception.class to catch ~unchecked exceptions~ java.langError and other Throwables, too? 🤔
What do you think?
Thank you!
Harald
cc: @eric-milles

Discussed on Slack and catching Throwable seems to be a typical anti-pattern. Question is answered. :-)

On the mailing list I suggested the possibility of deprecating isDynamicTyped in FieldNode, Parameter, etc.  And then removing their use from the compiler/runtime.  IMO there is only a very small bit of code in the compiler/editor that cares about the difference between "Object name" and "def name".
To be able to distinguish between those two, I have considered "ClassNode DYNAMIC_TYPE = ClassHelper.make(Object.class); ClassNode OBJECT_TYPE = DYNAMIC_TYPE.getPlainNodeReference();" so that referential equality is broken between the two constants.  However, I think there is probably a lot of code out there that checks "type == OBJECT_TYPE" or "type.redirect() == OBJECT_TYPE".  So this too would be a breaking change and possibly more impactful than the current condition of isDynamicTyped.
WRT your pull request, I don't think adding more API to ClassNode is the answer.  I'm still hoping for a reduction in API in areas where a consistent answer cannot be provided.  And backwards compatibility should be maintained if at all possible.

@eric-milles
Hello Eric,
thank you very much for your feedback, it is very appreciated!
Independently from the way it is actually solved, I think one benefit of my proposed pull request would have been that through ClassHelper.makeDynamicType() the four relevant places in AstBuilder are very easy to determine.
IMHO found it also more easy to read than just ClassHelper.OBJECT_TYPE.getPlainNodeReference();
Anyway I agree that we have to come up with a better solution.
I will close this pull request and keep the tests in my fork, they could be helpful later maybe.
Thank you and kind regards, Harald

I echo Eric's thanks for your efforts. Some parts of where I think we will end up could be quite similar to some parts of your PR, so nice work in your analysis! I am expecting we won't fully get rid of the dynamic type concept (at least not straight away), perhaps we'll use node metadata though instead of changing the API. I'd actually like to deprecate DYNAMIC_TYPE but we'll have to see how far we can get with that.


Issue with upgrading Danks from one lvl to the next with items inside

I just got an unfortunate bug while playing a SP world with the Dank Storage Mod, I received the Msg "Dank Item Level 4 cannot open dank Inventory Level 3". I can only assume this because I upgraded the dank while it contained items and the NBT that stores the data is not linking properly. Is this a known bug, or is there a way to correct it without spawning/crafting a new one and loosing the items inside?

This was fixed in 3.4.1 already, update


Best practice for iterating over every row of a table?

I have a table with an id and an url column. I need to go through all the rows inside this table and for each row, take a screenshot of the url. One option would be to use .fetchAll() but it isn't efficient if the table has thousands or millions of rows since it loads it all in memory. I was wondering if there was a "best practice" to accomplish this.

The feature you're referring to is usually called 'pagination'. It generally boils down to manipulating the result set with offset and limit. There is a discussion in #435 with a bunch of examples.

I know what pagination is and how to use offset  and limit to achieve it. I have some pagination code in  some of my models but it typically involves a lot of boilerplate code. I was hoping there'd be a generic iterate over every row in a table, 100 at a time function somewhere.

Sadly not, sorry. You're after something like ActiveRecord's ActiveModel#find_each right?

Yep, indeed!


Update tomcat.md

Tomcat 10.1.14 is released.

Hi @asashour, thank you for this update but our automation took care of it (by looking at Maven Central) in https://github.com/endoflife-date/endoflife.date/pull/3766/files.


Revert "Media: Generate and backfill BlurHash for media items"

Reverts #9953
Karma tests began failing starting with that PR and were also super slow due to tons of workers being spun up during tests.
While adding missing baseColor to fixture data helped a bit (see #10016), it did not solve the random browser disconnection errors.
More time is needed to properly investigate this.
A future version of said PR needs to:

Add missing baseColor to all fixture data
Not slow down tests
Ideally improve worker usage so that it doesn't spin up dozens of threads.
It might be more performant to have only 1 worker for all the blurhash generation/backfilling and pass messages back and forth, instead of creating 1 per image

https://www.npmjs.com/package/@shopify/react-web-worker might help with the latter, not sure.
In any case, we will revisit this in the new year.

Looks like the Karma tests are still not completing here:
First run with the disconnected error: https://github.com/google/web-stories-wp/runs/4551529472?check_suite_focus=true#step:6:1453
Second run with a different error: https://github.com/google/web-stories-wp/runs/4552157294?check_suite_focus=true#step:6:1605
Really odd since the BlurHash PR was the first commit where these issues started happening 😕 Would have guessed reverting it would fix things.

Wouldn't it just be easier to just update the a blurhash for all the fixture media elements?

See #10016 for that, as mentioned above.
Neither solution currently works.
That means the bug is somewhere else.

Should we remove this change?


Constructor cannot be invoked without new (question)

Thanks for your time,
In following this tutorial (https://scotch.io/tutorials/building-a-slack-bot-with-node-js-and-chuck-norris-super-powers), I am attempting to inherit the bot using util to create my own. I am able to do this successfully when using version 0.3.0 of this library, but if I update to the current version, I get a "Constructor cannot be invoked without new" error.
Here is some of the code:
var NorrisBot = function Constructor(settings) {
    this.settings = settings;
    this.settings.name = this.settings.name || 'norrisbot';
    this.dbPath = settings.dbPath || path.resolve(process.cwd(), 'data', 'norrisbot.db');

    this.user = null;
    this.db = null;
};

// inherits methods and properties from the Bot constructor
util.inherits(NorrisBot, Bot);

NorrisBot.prototype.run = function () {
    NorrisBot.super_.call(this, this.settings);

    this.on('start', this._onStart);
    this.on('message', this._onMessage);
};

Do you happen to know the proper way to inherit the Bot class?

Have same problem

The tutorial is from some time ago, and it uses slackbots, which apparently has gone through some changes lately.
In my case I'm using ES6 so I can take advantage of its proper classes support:
class JetaBot extends Bot {
    constructor(settings) {
        super(settings);
        this.dbPath = settings.dbPath;
        this.db = null;
    }
    run() {
        super.on("start", this.onStart);
        super.on("message", this.onMessage);
    }
...

That does the trick I guess.

Any help for the below code still getting the same error?
`// lib/bot.js
'use strict';
var util = require('util');
var path = require('path');
var fs = require('fs');
var SlackBot = require('slackbots');
class newBot extends SlackBot {
constructor(settings) {
super(settings);
}
run() {
super.on("start", this.onStart);
super.on("message", this.onMessage);
}
}
module.exports = newBot;
// in index.js
var newBot = require('./lib/bot');
const newbot = new newBot({
token: 'xx-xxx-xxx',
name: 'newBot',
});`
Node Version : v9.5.0


build cdc for multiarch

this will push an app image to ghcr, built for both amd64 and arm64 for use with the sentry dev tools

Are you trying to make our fork of wal2json multi arch as well ? https://github.com/getsentry/wal2json

hmmm!  wasn't aware of this but if I run into it I'll fix it too !


[2.0]: When pushing to Bitbucket, after successfuly push we say Changes pushed to GitHub

This should say Bitbucket

Cant reproduce anymore


docs(progressbar): tune up

Perhaps a lil' verbose, but there are just a few options.

Done that.

LGTM


Add millis to consumed messages

Hi @mostafa,
my scenario is that I am sending kafka requests with Writer to an tested app and I consume response messages with Reader.
I want to measure the duration between sending the message until the app writes a response into result topic.
I guess the time field on the message object coming from the Reader would be the right timestamp to collect as an time when the response was published, but since it is formated in RFC3339 format, I am missing milliseconds.
Would it be possible to use different format that includes millis? Or maybe add new reponse field to keep backwards compatibility?
Thanks a lot for your time and work
Roman

Hey @romankristof,
That is to make Goja (and the user) happy when exporting datetime to JSON, so you can use it in your JS code. I'd be happy to see contributions, though. As in, make this a configurable field on the consume function using the ConsumeConfig struct, which eventually gets passed down to the consume function.

Hey @AndreasKorn,
I'd be happy if you contribute this feature.

A new consumer option for nanos precision was added. You can set nanoPrecision: true in the consumer configuration in order to have the time return in RFC3339Nano format.
To have more flexibility this could be change further to allow specification of the exact format (as per @mostafa). We had questions around the format, whether it be javascript or go formats. Or constants for each format type.

Time field by default =  "time": "2024-04-10T14:13:46+01:00"
With nanoPrecision: true = "time": "2024-04-10T13:08:49.127Z"


Updated de (German) translation

Commit made via Stringlate

Hey! Thanks, but you seem to not have fetched latest translations before translating.
E.g. the strings contain strings.xml now again, which was changed recently.

I want to make sure that everyone understands. Users dont have to understand the internals and the filenames, ala strings.xml.

Ok, thanks


refactor!: remove a layer of lifetimes from PartitionFilter

Description
This commit removes a bunch of lifetime restrictions on the PartitionFilter and PartitionFilterValue classes to make them easier to use. While the original discussion in Slack and #1501 made mention of using a reference type, there doesn't seem to a need for it. A particular instance of a PartitionFilter is created once and just borrowed and read for the remainder of its life.
Functions, when necessary continue to accept the non-container types (i.e, &str and &[&str]), allowing their containerized counterparts to continue working with them without needing to borrow or clone the containers (i.e, String and Vec<String>).
Related Issue(s)

resolves #1501

Documentation

Also took the liberty to remove <T> as partition keys and values are always serialized as a string anyway. https://github.com/delta-io/delta/blob/master/PROTOCOL.md#partition-value-serialization

For an example on the current difficulty on using these.
let optimization = match config.lookback_window {
    Some(lookback_window) => {
        let partition_filters = Box::new(date_partition_filters(lookback_window));

        OptimizeBuilder::new(delta_table.object_store(), delta_table.state)
            .with_max_concurrent_tasks(config.concurrency)
            .with_target_size(config.target_bytes.try_into().unwrap())
            .with_min_commit_interval(config.commit_interval)
            .with_filters(&partition_filters) // <--- partition_filters does not live long enough
            .into_future()
    }
    None => OptimizeBuilder::new(delta_table.object_store(), delta_table.state)
        .with_max_concurrent_tasks(config.concurrency)
        .with_target_size(config.target_bytes.try_into().unwrap())
        .with_min_commit_interval(config.commit_interval)
        .into_future(),
};