Can we edit source(src) at the image popover?

Can support input source directly, also upload from locally.
Before finding this, I have just finished a plugin which is just do this. I think maybe there also can support, that will be good.
If this is not a good idea, please just tell me. Thank you.

And then, there has one issue about Chinese (Traditional) Translation. There should be as below:
tooltipShapeOptions: ['響應式', '圓角', '圓形', '縮圖', '無' ],
instead of
tooltipShapeOptions: ['圓角', '圓形', '縮圖', '無' ],
Translation is just not enough.
ps: I am Chinese, not Chinese Taiwanese, so maybe '響應式' is not good word. I ask my Taiwan friends, he said, 'A little IT terminology.'

I didn't do the language translations, please feel free to do a PR to fix what is incorrect.
With the Image Popover, are you asking about integrating the image-attributes plugin into Summernote's Image Modal. This can't be done without extensively modifying Summernote's functionality, that's why it's a separate plugin.

@StudioJunkyard I can not do do a PR.

I don't say if it's a separate plugin. I just say there can edit title, alt, class and style attributes at the image popover, but can not edit src attribute. Can you understand me? (Sorry for my poor English.)

oh, I get you know, sorry, I was in the middle of thinking about something else. I guess src attribute editing could be handy, I'll have a look at adding it a little later.
Anyone can do PR's, you can edit files using GitHub's pages.

@StudioJunkyard  Thank you. I do a PR.
'Anyone can do PR's', but not work for me. Maybe I have wrong configure locally. I can pull something, but can not push new branch. I can fixed this problem.
Thank you again.

@StudioJunkyard  I have edited files, and do a PR which did not assign any one to check. If you can not see it, please let me know.
And then, I just can do a PR by fork project. I have closed this test PR.

When you do a PR, GitHub will fork it into your account. Then you make changes to the duplicated files in your account. Then you do the PR.
I will then see it, review the changes, then merge it if it's satisfactory.

@StudioJunkyard It works as you said. Thank you.
Best wishes for you.

No worries, glad your having fun. :+1:


Core Mode demo

All demos are using the UI Mode, could you add one for Core Mode too?

How would they be different, other then a couple less options and no template?

I want to use the core mode, but i can't figure out how to display the image name and thumbnail after the images have been selected.
More precisely how to use the drawThumbnail method. Seeing an example would help me understand.

The drawThumbnail method documentation explains parameters that can be passed, and the expected outcome. For example, if you would like to generate a thumbnail onto an <img> tag for a file at ID 0, and want the thumbnail to be no more than 500 pixels tall and 500 pixels wide: your code would look like this:
uploader.drawThumbnail(0, emptyImgElement, 500);

If you need to know exactly when the thumbnail has been drawn on the <img> you provided, drawThumbnail returns a "thenable" value, which can also be called a Promise (though Fine Uploader's promise implementation is unfortunately non-standard, this should be sufficient for your use-case).
These types of questions belong on Stack Overflow under the fine-uploader tag, which is why I include a template when you create an issue (to keep issues and feature requests here - which you deleted). Please include any further support questions on Stack Overflow, and be sure to understand the rules and expectations of posting questions on Stack Overflow before doing so.

I deleted the template because my "issue" was no bug and no feature request, nor would it be allowed on stack overflow.
I only suggested for a core mode demo to be added amongst the UI demos and gave you an example as to why i needed one.
I'm sorry if it's something i should know if i want to use core mode, but i felt a core mode would be helpful.
And sorry if this kind of request is not allowed here, but i don't know were else i could do it.

Your support request for generating thumbnails using the API was completely appropriate for Stack Overflow, as long as you include appropriate details and code that shows your attempt to solve the issue. A request to "add more demos" isn't appropriate anywhere. This is an free open source project and cannot continue to survive with a single person's efforts. If you would like to see more demos, you are welcome to contribute more demos, or ask how you can contribute more demos if that is not clear, or ask specific support questions (on SO) that will lead you to develop a custom integration that will lead to a demoable block of code, which you can then contribute for others in the community to benefit from.

It was merely a suggestion, if you feel it's not worth, no problem.
The way I phrased it might have come as demanding, i'm sorry, i didn't mean to be rude.

Understood, and no problem. But this project really does need the support of the community. While I'm happy to continue to maintain and develop critical and complex features, I had a full-time job and other endeavors on the side (such as maintenance of other libraries, a book, etc).
So, let's say you want to see a specific demo added to FineUploader.com. If you are unable to code that up yourself, the next best thing would be to open up a feature request here in the issue tracker, and explain, in copious detail, exactly what you are hoping to demonstrate and why you think this may be useful to other Fine Uploader users. If you have code to show, such as with an incomplete demo/integration, then you also have the option of posting on Stack Overflow. In that case, an answer would update and complete your code, based on your question. In either case, whatever code you have so far would likely be helpful as well.


Pixel XL Display Ratio Issue

When i open app
There's a little bar in top of this app 4:3 or 16:9 ratio same small bar

While switching from camera to video or qr scan you will see more black border all side of the screen!

And if i pull notification panel once that top bar become bigger

and while that top bar is bigger if i switch from camera to video or qr code side border gets more larger...

qr code mode get cut icons on top while first opening

after pulling notification icons in qr code get down....sorry i am bad at English!...

Device Pixel XL

Is this still an issue?

Hi @IzumiSenaSora,
We're currently primarily working on migrating our camera app to Jetpack Compose and would attempt to try and fix this issue in the process.
We'll update this thread once there is any progress or changes to test specifically for Pixel XL regarding this issue.
Thanks a lot for following back on this issue. We'll get back with some update soon!


Fixes minor typo in basic JavaScript challenge "quoting strings with single quotes"

"should not be be" changed to "should not be"

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

LGTM

Creating a branch on the main repo is fine as long as its deleted after its merged.

@ezioda004 True, but it will be quite a while before it gets merged, because there are still around 700 curriculum PRs ahead of this one.


Dracula Theme for tofi

Dracula Theme for Tofi
tofi is an extremely fast run launcher that works on wayland as a replacement for dmenu and rofi.
Here is the repository with the new theme: https://github.com/juanscr/tofi

Just commenting for removing the stale label. Should I correct something related to the repository, so it is properly formatted?

Awesome!


Update create-a-bot-commands-menu.md

[x] C# samples
[x] TS samples
[ ] context reviewed.

Docs Build status updates of commit c880546:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/create-a-bot-commands-menu.md
:warning:Warning

Details

msteams-platform/includes/prepare-environment.md
:warning:Warning

Details

msteams-platform/bots/how-to/create-a-bot-commands-menu.md

Line 17: [Warning] Invalid file link:(~/bots/how-to/media/bot-menu-sample.png).
Line 29: [Warning] Invalid file link:(~/bots/how-to/media/AppStudio.png).
Line 37: [Warning] Invalid file link:(~/bots/how-to/media/AppStudio-CommandMenu-Add.png).
Line 43: [Warning] Invalid file link:(~/bots/how-to/media/AppStudio-NewCommandMenu.png).

msteams-platform/includes/prepare-environment.md

Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).

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

Docs Build status updates of commit 9d58c0b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/includes/prepare-environment.md
:warning:Warning

Details

msteams-platform/bots/how-to/Media/AppStudio-CommandMenu-Add.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/AppStudio-NewCommandMenu.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/AppStudio.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/bot-menu-sample.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/create-a-bot-commands-menu.md
:white_check_mark:Succeeded

msteams-platform/includes/prepare-environment.md

Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).

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

Docs Build status updates of commit b578078:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/includes/prepare-environment.md
:warning:Warning

Details

msteams-platform/bots/how-to/Media/AppStudio-CommandMenu-Add.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/AppStudio-NewCommandMenu.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/AppStudio.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/bot-menu-sample.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/create-a-bot-commands-menu.md
:white_check_mark:Succeeded

msteams-platform/includes/prepare-environment.md

Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).
Line 3: [Warning] Invalid file link:(~/concepts/build-and-test-your-app/foo.md).

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

One small typo. Look for "commend"; it must be "command".

Docs Build status updates of commit 0951564:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/Media/AppStudio-CommandMenu-Add.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/AppStudio-NewCommandMenu.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/AppStudio.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/Media/bot-menu-sample.png
:white_check_mark:Succeeded

msteams-platform/bots/how-to/create-a-bot-commands-menu.md
:white_check_mark:Succeeded

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


Production Ready Apollo Gateway for GraphQL Services issue

Hi Team,
We are new to GraphQL and we built couple of GraphQl Services using Netflix DGS.
Now we would like to federate those services into single endpoint and started working on it by cloning the apollo gateway federation by netflix example dgs-federation-example/apollo-gateway at master · Netflix/dgs-federation-example · GitHub.
This works perfectly fine on my local machine. But When we deploy the node js app to our AWS EKS env, I am not sure how can I access the apollo server. I always see the Server ready at http://localhost:4000/
I have exposed the port 4000 as well but no use.
Here is my code for creating the apollo server. Please help. I have been trying it for couple of weeks now. I didn’t find a production ready federation example also.
'use strict'

const https = require('https')
const http = require('http')
const config = require('config')
const app = require('./app.js')
const log = require('<custom_logger>')
const { ApolloServer } = require('apollo-server')
const { ApolloGateway, RemoteGraphQLDataSource } = require('@apollo/gateway')
var os = require("os");

var hostname = os.hostname();
console.log("hostname:"+hostname)
let httpListenerPort = 8080
let httpsListenerPort = 8443

log.info('NODE_ENV: ' + config.util.getEnv('NODE_ENV'))
log.info('NODE_APP_INSTANCE: ' + config.util.getEnv('NODE_APP_INSTANCE'))
log.info('NODE_CONFIG_DIR: ' + config.util.getEnv('NODE_CONFIG_DIR'))
log.levels(
  0,
  process.env.LOG_LEVEL
    ? parseInt(process.env.LOG_LEVEL, 10)
    : 'info'
)

log.info('log.levels(): ' + log.levels())

const gateway = new ApolloGateway({
  serviceList: [
    {
      name: 'service1',
      url: '<link_to_service1>/graphql'
    },
    {
      name: 'service2',
      url: '<link_to_service2>/graphql'
    },
    {
      name: 'service3',
      url: '<link_to_service3>/graphql'
    },
    {
      name: 'service4',
      url: '<link_to_service4>/graphql'
    }
  ],
  introspectionHeaders: {
    apikey: process.env.API_KEY
  },
  buildService ({ url }) {
    return new RemoteGraphQLDataSource({
      url,
      willSendRequest ({ request }) {
        request.http.headers.set('apikey', process.env.API_KEY)
      }
    })
  }
})

const httpServer = http.createServer(app).listen(httpListenerPort, () => {
  log.info('app is listening at localhost:' + httpListenerPort)
})

const httpsServer = https
  .createServer(<api_certs>, app)
  .listen(httpsListenerPort, () => {
    log.info('app is listening at localhost:' + httpsListenerPort)
  })

const server = new ApolloServer({
  gateway,
  subscriptions: false,
  tracing: true,
  introspection: true, // TO ENABLE PLAYGROUND IN PRODUCTION
  playground: true, // TO ENABLE PLAYGROUND IN PRODUCTION
  onHealthCheck: () => {
    return new Promise(resolve => {
      resolve()
    })
  }
})

server.listen(4000).then(({ url }) => {
  console.log(`🚀 Server ready at ${url}`)
  console.log(
    `Try your health check at: ${url}.well-known/apollo/server-health`,
  );
}).catch(err => {console.error(err)});

function timeoutExit (seconds = 5) {
  const timeout = setTimeout(() => {
    log.fatal(
      { exitCode: process.exitCode },
      `Application did not gracefully shutdown in ${seconds} seconds. Forcibly terminating.`
    )
    process.exit()
  }, seconds * 1000)
  // un-ref the timer so Node.js exits even with this running timer
  timeout.unref()
  return timeout
}

function closeServers () {
  httpServer.close(() => {
    log.info('HTTP server is shutdown')
  })
  httpsServer.close(() => {
    log.info('HTTPS server is shutdown')
  })
}

process.on('SIGTERM', () => {
  log.info('SIGTERM issued...app is shutting down')
  closeServers()
  timeoutExit()
})

process.on('uncaughtException', error => {
  log.fatal(
    error,
    'Uncaught Exception! The server is now in an unrecoverable state. Terminating...'
  )
  closeServers()
  // the app should exit on its own when there are no daemons running nor events on the event loop

  // forcibly terminate if haven't done so gracefully within timeout
  timeoutExit()
})

process.on('unhandledRejection', (reason, promise) => {
  log.error(
    {
      err: reason,
      promise
    },
    'Unhandled Promise Rejection'
  )
})

Not having any other configs for playground too. Have health check for http server only on top of it. Please suggest on how to spin the apollo server up and running in our K8s environment

You can find the answer here. In essence, if you want to deploy locally you have to create a listing of your services, if you want to deploy using Apollo Studio you should remove those service references in the constructor and rather use Rover CLI to register your services to Apollo Studio. Your gateway will then automatically discover them.


Add SKTetris by @chsxf

[X] Project URL:
[X] Update contents.json instead of README
[X] One project per pull request
[X] Screenshot included
[X] Avoid iOS or open-source in description as it is assumed
[X] Use this commit title format if applicable: Add app-name by @github-username
[X] Use approved format for your entry

There were some formatting issues but I fixed them
Thx!!


 Buttons are a great feature that can be bundled in with more stability and effectiveness. They don't require to use a slash command reply, so it's great for normal commands as well!
Start with slash commands! Discord brought up this amazing (and a bit weird to use) feature that turned into great customization about your elements on a command, to make them more accessible and structured through a panel bundled to the Discord client.  I made an interactions publisher ~(which Max stole)~, a separate interactions handler and folder, and a simple but effective structure for the slashies so they can be published and ran easily! I made a toggle command to turn on and off slashies (which only staff can use), and I bundled a few existing "normal" commands to the folder.
A WAY BETTER blacklisting. The nifty progress can be seen here, but to summarize: I removed the "pluralizer" (check with "s" at the end of a word) because it was causing too much trouble; symbol checking won't override the start-to-end checking; symbols will escape when added through a+addword, a better multi-word blacklisting that'll manually check blacklisting in every word by substrings in the sentence (I swear this took me long to figure out).
Refactoring a lot (most) commands, cleaning them, fixing their help strings, adding and removing stuff, having to fix NEARLY ALL MOD COMMANDS (god i hate those), fixfixfix refactorrefactorrefactor etc
I make better code and slack harder, Max makes more code and copes harder
Welcome messages now follow the nice! funky! cool! new! epic!  A member will be greeted when they just got their verification role removed and their member role added. It'll still unhoist them and log their info at normal join, and guildMemberRemove will work normally.
(so there was this one time it started pinging everyone whose data changed? y'know, because it's guildMemberUpdate... that was funny as hell and took me days to fix)
Tags can be made staff only by using the staff argument on a+addtag. more hidden stuff yay!
oh also the tags can be listed with pagination by using a+listtags

[x] I have tested each and every command. They could still be prone (I checked for edge cases too), but for the most part should be good to go and will hear the bugs as they come along.
[ ] I haven't tested each and every event, but I'm quite certain they're all working. If something broke, it's probably the configs.
[x] I have tested each and every slash command. Same situation as normal commands.
[x] I have tested most of the other things, functions, etc. The most troublesome func would probably be getMember(), and the inner workings of it have been successfully patched (how it's called and used might've not, so I'll have to see those bugs as they come over time)
[x] I have drank water while doing this PR, in fact I just sipped as I'm writing this sentence.

Tofu Bot disband
As more of the "sentimental" part, around a week or two ago, one small joke on the r/JaidenAnimations server having to do with eval and YuriGroove and the server icon turned into an incident in which Tofu Bot was revoked from its permissions, making Max (its owner) kick the bot from the server and scrap its presence on it. That's probably why you can see a branch called max-pr with the latest commit being "Remove Tofu". However, very recently Tofu got reinvited! With admin again as well, to not cause any issue with the bot workings (which was the main reason why it got kicked, the perms purge broke a lot IF NOT ALL Tofu). This story ends with a good ending for now, expecting to keep the collab with Max, the code discussion and the overall ying and yang of our two "Jaiden bots".
That's about it, I'm so happy I am finally able to merge this mf. A lot of work (28 commits LOL) were put into this, and seeing it in the master branch just means going to the moon. To the moon!!!!! 🚀🚀🚀
This PR is doing to be in draft because it's not ready for review.  Enjoy the view over at Mount Chirripó!

wtf is codefactor talking about
how do i fix a "Complex Method" LMAO what

Fixed codefactor score by ignoring issues like that
Ignorance is bliss.

If you're going to request me to review maybe idk give time. If you're going to request review only to merge literally a minute later. I can't read trough 5k+ lines of changes in less than a minute lamo

ok nevermind i'm blind


Update UI text to better match response

Figure: Updated text on buttons group

Codecov Report

Merging #437 (edc2214) into main (a59c707) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #437   +/-   ##
=======================================
  Coverage   32.86%   32.86%
=======================================
  Files          76       76
  Lines        2127     2127
=======================================
  Hits          699      699
  Misses       1428     1428

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a59c707...edc2214. Read the comment docs.


Fix homepage email subscription link

Purpose of the pull request

Fix email subscription link in homepage, see: https://dolphinscheduler.apache.org/zh-cn/community/development/subscribe.html

Brief change log

Already described above.

Verify this pull request

This is a doc fix.

Seems it hasn't taken effect yet. May I ask whether there is anything else I need to change to fix homepage email subscription link? @SbloodyS @zhongjiajie

Seems it hasn't taken effect yet. May I ask whether there is anything else I need to change to fix homepage email subscription link? @SbloodyS @zhongjiajie

It has taken effect now. The documents of the current dev branch are regularly triggered to build the official website, which is different from the dolphinscheduler-website repository.


adding sandbox only for development flavour.

@roknovak I cancelled your PR because the keys were wrong. I am going to merge this but please have a look later on your following morning.


dashboard button back by default

         Hey all, thanks for sharing your stance on this.

As 2.7.0 is released and it doesn't have the Hub link anymore I'm going to close this issue.
Originally posted by @ddtmachado in https://github.com/traefik/traefik/issues/8912#issuecomment-1140018057

The button appears to be back as it shows up on a default photoprism installation on v2.9.10:

How do remove the button?

Hello,
the Hub button has never been removed in v2.7, I think Douglas made a confusion between Pilot and Hub buttons. Related to #9108.
But in v2.10.4 (the latest release), an option has been added to disable it. #10008
API:
  # ...
  disabledashboardad: true
  # ...

[api]
  # ...
  disabledashboardad = true
  # ...

# ...
--api.disabledashboardad=true
# ...


Facing Issue while trying to access JFrog URL from VS Code

I am writing this bug report to bring your attenstion to the following:
Whenever I am trying to access my company's URL for JFrog, the following message is displayed: "Request failed with status code 404".
Can anyone please help me in resolving this error?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


New VarStore.load capabilities

Hello,
I have noticed that capabilities to load Pytorch bin or pt pickle archives seems to now be possible with the library which is a great addition. I have just tried this new feature and I am unfortunately encountering errors.
I am trying to load the following model file, which returns an OrderedDict when loaded in Python with torch.load("path/to/pytorch_model.bin")
Loading the same model with Rust causes the following error:
Error: Tch tensor error: Internal torch error: Unrecognized data format
Exception raised from _load_parameters_bytes at C:\actions-runner\_work\pytorch\pytorch\builder\windows\pytorch\torch\csrc\jit\mobile\import_data.cpp:269 (most recent call first):
00007FFC387CAD1200007FFC387CACB0 c10.dll!c10::Error::Error [<unknown file> @ <unknown line number>]
00007FFC387CA72E00007FFC387CA6E0 c10.dll!c10::detail::torchCheckFail [<unknown file> @ <unknown line number>]
00007FFBF4BE7D0000007FFBF4BE7B40 torch_cpu.dll!torch::jit::_load_parameters [<unknown file> @ <unknown line number>]
00007FF784B2A6F900007FF784B2A660 codebert.exe!at_loadz_callback_with_device [C:\Users\Guillaum\.cargo\registry\src\github.com-1ecc6299db9ec823\torch-sys-0.10.0\libtch\torch_api.cpp @ 419]
00007FF783F4C3F900007FF783F4C2C0 codebert.exe!tch::wrappers::tensor::Tensor::loadz_multi_with_device<ref$<ref$<std::path::PathBuf> > > [C:\Users\Guillaum\.cargo\registry\src\github.com-1ecc6299db9ec823\tch-0.10.1\src\wrappers\tensor.rs @ 681]
00007FF783F5528600007FF783F55170 codebert.exe!tch::nn::var_store::VarStore::named_tensors<ref$<std::path::PathBuf> > [C:\Users\Guillaum\.cargo\registry\src\github.com-1ecc6299db9ec823\tch-0.10.1\src\nn\var_store.rs @ 175]
00007FF783F554BB00007FF783F55480 codebert.exe!tch::nn::var_store::VarStore::load<std::path::PathBuf> [C:\Users\Guillaum\.cargo\registry\src\github.com-1ecc6299db9ec823\tch-0.10.1\src\nn\var_store.rs @ 188]

These seem to be caused by Libtorch itself, but you may know from your own experiments if there are limitations regarding the type of format that can be loaded?

Interesting, I haven't run into this exact issue.
That said my experience so far has not been great, it works on the CLIP weights for diffusers, but on the vae and unet model I run into an "Expected GenericDict but got None" error. This seems to be a well known issue (reported in the ruby bindings torch.rb#21) and the proposed workaround is to tweak the way to save the weights to use a dict rather than an ordereddict but this isn't a convenient workaround for already existing Python model files.
torch.save(dict(model.state_dict()), "mymodel.bin")

As the error message is quite different I doubt it would help in your case though. Googling for "unrecognized data format" and libtorch, I have found some reports of the same error message but no reply (though I haven't searched for more than a couple minutes).

Thanks I will investigate and report back if I find a fix.
Is the loading of Pytorch model a new feature in Libtorch? As far as I know only torchscript models could be loaded from the C++ API (see for example this issue .
Looking at the error stack above, it does indeed seem that the torch::jit::_load_parameters method is called and would indicate that the model should be serialized using jit in Python. Were the CLIP weights saved using jit or a direct torch.save from a nn/Module?

The CLIP weights came from this huggingface repo. I have no clue how they were stored but my guess is through torch.save directly. I also got VarStore.load to work properly on .bin files generated via torch.save by appyling the state_dict hack mentioned before.
I'm not sure how new the underlying feature is, torch::jit::_load_parameters part of the mobile api, the header file mentioned that it should be prefered over using mobile_module_to_parameter_map and looking at the code it seems to handle the unpickling part that should make it compatible with Python's torch.save.


Add export all namespace members

Unable use namespace members so export namespace.

Can you describe the error this fixes? #415? #350?

It may fixed #350. But this PR not for bug fixing, it just for improvement: using ComponentProps and others in my code.

Сhose another solution.