Where can the official images be found

@nekojan
I don't know where I can find you official images to add some different libraries which we can use in SageMaker.
In https://github.com/aws/sagemaker-tensorflow-container/issues/43#issuecomment-393710684_) you wrote that you publish them for publicly use. But where can I find them? :)

The instructions on this repository are focused on how to build the official SageMaker docker images. However, for normal use, you don't need to do this as we publish official versions that are publically available for use. Mostly, this would be useful if you want to change the code or dependencies in the image.

Because building from scratch takes a real long time and needs some memory adjustments for the docker building environment etc. This takes me a long time to figure out. Perhaps that could be added in the README file?
Thanks you.
Greetz
André

Hi @devTechi ,
I am not sure if I get your question. I guess you are looking for the public official SageMaker TensorFlow container that you could just pull?
The official image is in following format:
520713654638.dkr.ecr.{region_name}.amazonaws.com/sagemaker-tensorflow:{tensorflow_version}-{processor}-{python_version}
For example, if you want the cpu image in us-east-1 with tensorflow 1.11.0 in python 2. The image is:
520713654638.dkr.ecr.us-east-1.amazonaws.com/sagemaker-tensorflow:1.11.0-cpu-py2
For current supported versions, please refer to README (https://github.com/aws/sagemaker-python-sdk/blob/master/README.rst#tensorflow-sagemaker-estimators)
Thanks

Hi @yangaws
thanks for you answer. That was exactly what I was looking for.
Did I miss those information or where could I have found them?
Anyways yes. I want to use the already built images from you ECR or another registry without the need to build them on our own. This is really time consuming and needed adjustments in the local docker preferences (at least on my mac).
So this was really helpful. Given that we can close this issue, but may I suggest that you add this really important information to the README.md or another documentation on aws?
Kind regrads
André


reduce size of sdimg file

via MENDER_STORAGE_TOTAL_SIZE_MB to speed up image programming

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Merge v2.11 into v3.0

What does this PR do?
Merge current v2.11 into v3.0.
Motivation
To be in sync.
More

[ ] Added/updated tests
[ ] Added/updated documentation

Hello, just for feedback, this merge request is hard to evaluate when reading the changelog.


get_followers returns an error

Brief Description: when get_followers is called, the server returns a 500 error with this message:
sqlite3.OperationalError no such column: serializedFollowers
Operating System (OS and version): Win10
OpenBazaar version: Master 1.1.4+
This can be reproduced every time on my local node, but does not affect the Vader test node.

Did you run the followers PR on the same db then switch back? That PR runs a migration.

Ah, that must be it.


Equivalent command to Get-AzureRmLog for formal auditing?

I'd like to access the audit logs for a specific resource group in the same way as Get-AzureRmLog. I can try to rummage inside every deployment, but that doesn't give me the same info.

This might be part of insights, which is currently still being worked on.

Thanks, is it scheduled/on roadmap so that I can assess if I need to develop a workaround?

On 13 Jan 2017, at 20:05, Travis Prescott<EMAIL_ADDRESS>wrote:
This might be part of insights, which is currently still being worked on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@tjprescott agree with @rcarmo this is really important! I don't know why we are releasing 2.0 sdk that not giving the same features as 1.0...

Cleaning u old issues, reopen if this is still active.

Yeah, this is still active - on a cleanly installed az, there is still no equivalent command that I can fathom. Why close this without verification?

On 3 Nov 2017, at 02:57, Jason R. Shaver<EMAIL_ADDRESS>wrote:
Cleaning u old issues, reopen if this is still active.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm going to reopen this so we don't lose track of this.

This is a really important feature for us...

I believe the command you are looking for is az monitor activity-log list


a Sanic extension that generates APIs from python function and classes.

I have a transmute framework for sanic. basically, it is a sanic extension that generates APIs from python function and classes. and it's very easily integrate with Swagger with zero effort, just do
# add swagger
add_swagger(app, "/api/v1/swagger.json", "/api/v1/")

find out more here:
http://sanic-transmute.readthedocs.io/en/latest/

Would you like to submit a PR to add this to the extensions documentation? https://github.com/channelcat/sanic/blob/master/docs/sanic/extensions.md

Closed with #782


init nix-python script for unify haskell and python script

plan to support haskell and python at the same time.
the dependency is manage by nix as nix can support all language library and binary file.

hold for a moment, it seems the schema can't match the data.
i'll fix it.


Proposal: standard GitHub organization

It may be time to consider moving all standard GitHub projects into its own organization.
Why?
Standard spans across many packages at the moment:

standard
eslint-config-standard
eslint-config-standard-jsx
eslint-config-standard-react
eslint-plugin-standard
standard-www
standard-packages
standard-engine
standard-json

And there are some "somewhat officially sanctioned" standard derivatives, maintained by standard maintainers themselves:

semistandard
standard-react

Benefits

Simplified collaboration: This will drastically simplify adding collaborators into the project. By adding them into the org team, they'll get access to all related standard repos.

Adopting forks: there are some standard derivatives that are stagnating. If there's enough community interest in them, they can be adopted into the standardjs organization and co-maintained by standard maintainers.

Naming
As for name candidates, the name @standardjs has been stagnating for a while, and @standard-js is not taken.

I think moving to an organization is a great idea! Unifying all the standard packages in one place seems like a huge win
I managed to get my hands on the name @standard thanks to a kind anonymous soul who is totally amazing! 🎉
Can't wait to hear what the haterzzz are gonna say when this repo goes from feross/standard to standard/standard.  I KID, I KID!

All the repos that were owned by @feross are now owned by @standard – wohoo! 🤘
Anyone who had commit on a standard related repo should have gotten an invite to the organization. Note: If you don't have Two-Factor Authentication set up, you may have lost commit rights. Set that up and let me know if you need to be re-added.
Remaining repos to transfer:

https://github.com/Flet/standard-engine (cc @Flet)
https://github.com/Flet/standard-json (cc @Flet)
https://github.com/xjamundx/eslint-plugin-standard (cc @xjamundx)

It's debatable whether these should be added, but I'm okay if that's what @Flet wants.

https://github.com/Flet/semistandard
https://github.com/Flet/SublimeLinter-contrib-standard

If other maintainers of editor plugins want to move their plugins into the organization, I'm fine as long as we add the maintainers to the organization so those plugins actually get maintained. 💪

CC'ing owners of other plugins. Just FYI, StandardJS is now in a GitHub organization (@standard):

https://github.com/gustavnikolaj/linter-js-standard-engine (cc @gustavnikolaj)
https://github.com/chenxsan/vscode-standardjs (cc @chenxsan)
https://github.com/ishamf/brackets-standard/ (cc @ishamf)
https://github.com/capaj/vscode-standardjs-snippets (cc @capaj)
https://github.com/TimonVS/vscode-react-standard (cc @TimonVS)
https://github.com/gaboesquivel/atom-standardjs-snippets (cc @gaboesquivel)
https://github.com/stephenkubovic/atom-standard-formatter (cc @stephenkubovic)

I'm wondering if it's desirable to put editor plugins into the organization. I don't feel strongly either way -- curious to hear what people think.

This consolidation seems like the right thing to do, yay! :tada:
As for editor-plugins, I am in line with @feross - I really don't know if they fit better in- or outside the organization. Either way, linter-js-standard-engine is small enough that I don't feel I qualify to vote. :smile:
As I see it, the main benefit of adopting editor plugins is (as mentioned under benefits in this issue) that the community can step in and take over if a maintainer disappears. This will help make a more coherent ecosystem and avoid stagnation. But it comes at a price of course - it's will be a much bigger pile of code with a much wider scope, which means a larger demand for contributors.
I'm not sure how that trade-off will balance out, but I guess the conservative approach would be to postpone it for now, and see how the first step of the transition to the org goes. If it's massively successful, then it might not be a problem to on-board all the editor integrations too...
I'll be happy to handover the project to the new org, should that be the direction that you all choose to go with.

Great move @feross! I was hoping this would happen at some point! 🎉

@feross I think it's desirable. Anyone who is new to standard and is browsing the organisation on github will be able to see standard is supported well in all major editors.
One thing though-it would probably make sense to try to align the snippets as best as we can across all three editors in the future. There will always be some differences because snippets work differently in every editor, but there is certainly some common set of snippets we could make work in all editors.

Can't wait to hear what the haterzzz are gonna say when this repo goes from feross/standard to standard/standard

hahaha, I did receive some complains for vscode-standardjs because of standard.
Mostly i agree with @gustavnikolaj. The only problem to me would be my code quality - it's not tested, although it works :)

I'd be open to having the plugins live in the org. For someone viewing the org, it may make it easier to distinguish how all the pieces fit together and what the responsibilities are of each.

@standard!  that's awesome!  I think this change will consolidate the tooling and community around standard.  We move atom snippets repo, makes sense to me.

https://github.com/mattdesl/standardize  @mattdesl

For what its worth, I own https://www.npmjs.com/org/standardjs but I'm not sure we should start name-spacing our modules.

Standard and all ecosystem around it is welcome to the @Standards org. I got it in the beginning, in first months after StandardJS was release and a bit before Standard-Engine was born. The idea was to move everything there, even the Standard Readme and such standards.
Long time after that @leog came and reached me with some interesting idea. Which now is seen in the org and is described in its website. And the old content of the org was moved to the @gh-standards (which was @leog's org) as backup place for the idea that i had with few forks and opened issues.
So, long story short, i'm okey with that most of the StandardJS ecosystem to come to the org. All maintainers and devs who want can have separate team and we won't mess with the repos if you want. I'm totally okey, even more, i don't have any time for anything, recently. If @leog is okey too, i believe we can allow one exception from our rule, for StandardJS ecosystem.
Later in time StandardJS as standard can be first validated (more about the process read on the site and on the so called "meta" standard).
If anything need more clarification or need to chat, reach us at our gitter Lobby.

Would you accept tunnckoCore/modern-javascript-snippets? It have VSCode (on the Marketplace) and Atom (atom's registry) snippets, most complete StandardJS-driven snippets.

https://github.com/timoxley/standard-loader  @timoxley

timoxley/standard-loader is now standard/standard-loader
https://github.com/standard/standard-loader

I switched editors from Brackets years ago... I think the plugin no longer works, sorry.
I'll transfer the repo, at least for the name and links.
https://github.com/ishamf/brackets-standard/

Hi @tunnckoCore. I already reached @feross about using @standards org. AFAIU there was no interest in using it as it defines a different process to produce valid and scalable standards than he first thought of for standardjs.
FYI, I already changed a little bit the process to not rely on moving the defined standards to the org, they can live in any place and still show up on the standards initiative.
Anyway, I'm completely open to change it in any way to promote a healthy environment to produce standards. As a learning experience I've been also using the same @standards org process on Autodesk (http://standards.autodesk.com) to produce standards inside Autodesk on its enterprise GitHub instance and it's working really good, getting traction while people gets used to collaborate using GH.

@feross Trying to move the atom snippets package I'm getting this message
You don’t have the permission to create repositories on standard

@gaboesquivel Just added you

This is a thing now! 🎉 🎉 🎉

@feross Recently I don't find any time maintaining vscode-standardjs, is it still valid that I can transfer it into standard organization so someone might be interested in maintaining it?

Funny enough, I've not been using the sublime plugin I wrote as much these days, and have been using @chenxsan's vscode plugin.  Moving both to the org would increase the number of people with commit access and help get fixes out if needed.

@chenxsan I'm in favor of this and volunteer as tribute to help maintain it :)

Using that plugin every day, would love to help maintain it 👍

Invited @chenxsan to the org :)

@Flet @LinusU @bcomnes Transfered :)

@chenxsan @Flet Thanks!

Re-opening this as a note to self: I want to take a look through the list of plugins and see if there are any left that still need to be transferred into the @standard org, so we can ping the authors.

I'd be interested in transferring my Atom plugin into the org. https://github.com/stephenkubovic/atom-standard-formatter

@stephenkubovic Nice. You can transfer it to @standard and we'll accept the request. I'll add you to the organization right now.
Are you interested in continuing to lead the maintenance/development on it? Or looking to find a new maintainer?

@feross transfer request sent!
Regarding ongoing development - admittedly I haven't found the time recently to spend on it. If someone is interested in maintaining it, that would definitely help move things forward.


Refactor arg and config variables to struct

Summary
As developers
I want control over when variables can be edited
So that I can better reason about what happens in the code and therefore focus on the task at hand.
Context
#359 moved the wrestic code into the k8up repository, but did try to changes as little as possible of the architecture.
cmd/restic/main.go contains the legacy structure with module-scoped variables. These should better be wrapped into it's own struct.
Out of Scope

Feature Changes

Further links

https://github.com/vshn/k8up/pull/474#discussion_r687471273

Acceptance criteria

The number of global or module scoped variables is reduced to the bare minimum.

Implementation Ideas
The suggestion of @ccremer:
type Command struct {
  check bool
  ...
  log logr.Logger
  resticCLI ...
  Command *cli.Command
}
func NewCommand(...) *Command {
  ...
  c.command = &cli.Command{
    Action: c.runCommand,
    ...
  }
}

func (c *Command) runCommand(ctx *cli.Context) error {
...
}

Have a look at other code in cmd/ and elsewhere if they have such avoidable variables as well.

This happens in #477, no need for an additional issue.


autocert: Include the domain in the SAN of the CSR

More compliant with the spec and allows autocert to work with Pebble (see https://github.com/letsencrypt/pebble/issues/304). Fixes https://github.com/golang/go/issues/39746.

What do you say?

Is there any news on this?

Please merge this PR @FiloSottile

Huh, looks like gopherbot didn't fire on this PR and it was not imported into Gerrit.
@golang/release?

@FiloSottile GerritBot waits for @googlebot to add a "cla: yes" label before starting work. For some reason that hasn't happened here yet.

It should work now. But, from GerritBot logs:
2021/02/19 21:40:32 GitHub: 0/5000 calls remaining; Reset in 7m52.975721092s

It likely shares rate limit with GopherBot, so issue #44406 may be relevant here.

@FiloSottile could you please tell when we should wait for PR merge?


New collective page: customize primary calls to action

Following up on https://github.com/opencollective/opencollective/issues/2228#issuecomment-511093177

One thing that appears in @nemchik's feedback is that different collectives will have different expectations about the primary calls to action.
Currently we've defined that the primary call to actions should be Donate and Contact. For my example, I'd prefer for my collective CaptainFact to have Donate (because one time contributions are something we're looking for and we want to make it simple) and Website (because some people arrive on our OC page without knowing about the project and there's no chance that they will donate if they haven't seen our main product yet). Having a contact button is actually a problem for us because we have clear paths to handle communications and having emails on collective admin's inboxes is messing up with our processes.
Another example: we don't care about the "Donate" button for OC engineering collective, but the "Submit expense" is very important: people come there to claim bounties.
That being said, we should of course have smart defaults and I think that the ones we already defined are good because they're based on very relevant feedback from support requests, users and examples from other websites.
Feature summary
Collective admins can pick up to 2 calls to actions to put on their collectives Hero amongs the following:

Contact
Donate
Website
Github
Submit Expense
[Custom?]

@raulgrafico @cuiki not to implement in the edit mode before we have a consensus, but opinion welcome.
Also @alanna @piamancini @xdamman as you have strong opinions about what we should put there.
PS: to be clear I'm talking about this:

Hmmm. It's an interesting idea but I'm not sure it's the way to go.
When it comes to "contact", the problem is that the core contributors might not think it's important because they are not the ones ever looking for the contact button. It's everyone else who is trying to reach them and getting confused and failing because it's hidden.
To me, it seems far more important that the design is consistent, so people only have to figure out these things one time (where is the contact button, where is the submit expense button, where is the contribute button). If these are in different places for each Collective it could be a nightmare. Different users have different top actions. Some only contribute financially. Others only submit expenses. Others just want to get to their dashboard to approve expenses, etc.
That said, I do think actions which are very important to some Collectives are too hidden in the new design, such as the website link, repo link if they have one, subscribe to updates, etc. Can we just try to reveal all of these a bit more, so whatever someone is looking for is easy to find near the top of the screen?
I would focus on making creating custom tiers part of the Collective onboarding process, so the Collectives have a lot of control over the words and CTAs that appear in the top section of their page (Contribute). We really hammer home the contribution thing in that section, so I don't think we need yet another contribute button in another place.

To me, it seems far more important that the design is consistent, so people only have to figure out these things one time (where is the contact button, where is the submit expense button, where is the contribute button). If these are in different places for each Collective it could be a nightmare. Different users have different top actions. Some only contribute financially. Others only submit expenses. Others just want to get to their dashboard to approve expenses, etc.

I agree, the main risk of customization is often inconsistent design and hardly predictable paths. It's a tough thing to find the right balance between allowing enough customization for users to feel that they own this page without breaking the experience for all the other visitors.
So I understand that there is a danger if one collective has a big Contribute button there while a sibling collective has a Submit Expenses button instead. But I still think that we must somehow bring more flexibility here, if not by picking the precise buttons at least the page should better adapt to the collective usage.
Another example for this is the ~Get Updates~ Follow button: most collectives never create updates on the platform. I'm pretty sure that a good part of them don't really care about adding a Follow button. On the other end we got feedback that collectives do care for a more prominent Contribute button (https://github.com/opencollective/opencollective/issues/2228).

@cuiki @raulgrafico Your experience about UX would be valuable in this conversation, especially about how customizing these CTAs could lead to confusion for users.

Hi. The challenge, IMO, is to make sense of all the incoming feedback and put it together and apply strategically. Most of what you said in the initial comment is already addressed but this could be a matter of hierarchy and sequence. Some users think that their CTA could be submitting an expense but it could only mean that the action of submitting is hard to find or buried too deep into the page.
I think we should aim for consistency (reinforcing the action of contributing which seems the most recurring feedback) but rethinking what are the important contexts that matter to users, rather than thinking about a single action.

Closing this for now as we prefer to target consistency

Sorry I missed this issue. Only seeing now with the notification that you closed it ;-)
Thanks for sharing your experience with CaptainFacts. We need more stories like those to better understand the different use cases.
I agree with @alanna that consistency across all the collective pages for the main actions is important.
But I also agree with @Betree that the “Submit expense” is an important CTA that for now, should be put much more forward.
I say for now because to this day, the main use case for open collective is “collect and disburse money”, so it only makes sense that those should be the two top CTA (especially on mobile with limited screen real estate). Then “Contact”.
@cuiki @raulgrafico could you share it a desktop and mobile screenshot of having those 3 CTA in that order? (Donate, Submit Expense, Contact)
@Betree maybe one way to reconciliate the need for consistency with the need of customization, why don’t we let the collective customize where the “contact” button goes? By default it could be info@:collectiveSlug.opencollective.com but people could for example put another email or a URL such as https://github.com/CaptainFact/captain-fact/issues/new

maybe one way to reconciliate the need for consistency with the need of customization, why don’t we let the collective customize where the “contact” button goes? By default it could be info@:collectiveSlug.opencollective.com but people could for example put another email or a URL such as https://github.com/CaptainFact/captain-fact/issues/new

Yep that'd be a good way to solve the contact issue that I'm pretty sure other collectives will complain about at some point. Opening an issue for that now.

Yup I think thats a good level of customization for now. :)


No namespace symbol uses when subsequent id isn't resolved in open expression

Fixed in https://github.com/Microsoft/visualfsharp/pull/4012


[Bug]: Widget Navigation doesnt work when you have container type widget in the page

Is there an existing issue for this?

[X] I have searched the existing issues

Description
https://www.loom.com/share/8b2e3b3225344331a90340d972f60040
Steps To Reproduce

Take 2 pages
In one page , add one container
Switch pages and see if you can navigate to the container again

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Production

Working fine, verified it on release.


Add growfs systemd service to bootc images

This is a little hacky to just get this in.  Would be better if we shared this all with the recipes subdir, but for speed I just want to get this in.
We will need to revisit the Makefile.common concept to share more between recipes and training.

@sallyom PTAL


fix: refactor to docker-netcheck

Making this consistent with the other docker repos published on Docker Hub.


Electron 4 Win64 Support

Expected Behavior

v0.4.0 Should work with Electron on Windows x64.
Current Behavior

While macOS and Ubuntu are fine, I can't use the newest version on my Windows machine. I get a "Module did not self-register" error when starting the app.
Steps to Reproduce (for bugs)

Use electron-example in this repo.
Change Electron version to ^4.0.4
Run yarn start

Your Environment

Version used: v0.4.0
Environment name and version (e.g. Chrome 39, node.js 5.4): electron 4.0.8
Operating System and version (desktop or mobile): Windows 10

Is this related to my system only ? @anoadragon453 did you see anything like that ?

Haven't tested Windows myself yet (can do on Monday), but @kolnogorov seemed to find success.

Yes, I've managed to build it under Mac, but i have no Windows machine, so i tried to build iohook under Virtual Machine on Windows, but haven't succeeded due to lack of Visual Studio and other libraries I've tried to install but still couldn't compile.

@kolnogorov : It might be related to you PATH (i.e. Windows not knowing where to find VS).
I was able to compile it on Windows, but unable to use it in a Electron 4 env (NodeJS 11 is ok).

@Djiit i thought i added everything related to VS in PATH, but to insure, could you please tell what should i have installed and added to PATH to compile it? Because, on mac it compiles out of the box, but I have not many experience with Windows.
Thanks in advance!

I don't know either, you can check this great list : https://github.com/Microsoft/nodejs-guidelines/blob/master/windows-environment.md#compiling-native-addon-modules.
But AppVeyor successfully builds it so you should be able to pull prebuilt binaries when you run yarn add iohook(i.e. no need to build it).

@kolnogorov Make sure you've installed resources for VS C++ 2017, as that's what we're using now.

I get Error: The specified module could not be found in ...\resources\app.asar...\iohook.node, but mac application works fine.
env: Parallels Windows 10 x64
electron: 4.0.8
iohook: 0.4.0

I get Error: The specified module could not be found in ...\resources\app.asar...\iohook.node , but mac application works fine.

Does this file exist?

(FWIW, this file is present on my machine. Just corrupted or unusable in some way)

@anoadragon453 Yes, it does. The full path - \resources\app.asar.unpacked\node_modules\iohook\builds\electron-v69-win32-x64\build\Release\iohook.node

Here:
iohook: Error: The specified procedure could not be found.
\?\c:\test\node_modules\iohook\builds\electron-v69-win32-x64\build\Release\iohook.node
(the file exist)

I am getting the same windows error, @karacas .
Please advise if you have found a solution.

I can confirm, I'm getting the same error by "iohook: Error: The specified procedure could not be found." even if the iohook.node exists.
I'm using iohook v0.4.0 and electron 4.0.0 too. (Windows here)

Since you are use cmake-js here instead of node-gyp, I think you may need a version of cmake-js with this PR merged.
Consider forking cmake-js maybe?

If people could try with this PR branch and report back if it works that would be most appreciated https://github.com/wilix-team/iohook/pull/157

Hoping to get this sorted to roll out an upstream feature!

Closed by https://github.com/wilix-team/iohook/pull/159

Hi I am trying to make this work with Electron 4.2.2 but I get this error:
Uncaught Error: Cannot find module 'C:\Users\digit\Desktop\workspace\proj\node_modules\iohook\builds\electron-v69-win32-x64\build\Release\iohook.node'

electron-v69-win32-x64 does not exist
In my package.json I have:
"iohook": {
    "platforms": [
      "win32"
    ],
    "arches": [
      "x64"
    ],
    "targets": [
      "node-67",
      "electron-69"
    ]
  }

Any ideas?

Hi!
I don't know why but iohook doesn't seem to works with electron-packager --asar option. If I don't use it it works fine, but if I do it encounter the exact same error.

I ended up fixing this issue by adding the following option to electron-packager:
--asar.unpack="**/node_modules/iohook/**"
hope it helps!


check that yaml keys are unique

also removed the obsolete file_accessor, yaml_files does the same thing basically

Looks good to me. Caught the duplicate entry in #413


Cannot Install app

I'm using Sony A6300 with 2.01 Firmware version. Here's the error that I got (It is the same with all other OpenMemories app except the limit tweak)
Loading app list
Found 11 apps

Using drivers Windows-MSC, Windows-MTP
Looking for Sony devices

Querying mass storage device
Sony DSC is a camera in mass storage mode

Model:              ILCE-6300
Product code:<PHONE_NUMBER>
Serial number:      04532299
Firmware version:   2.01
Lens:               Model 0x18a08019 (Firmware 1.81)

Using drivers Windows-MSC, Windows-MTP
Looking for Sony devices

Querying mass storage device
Sony DSC is a camera in mass storage mode

Switching to app install mode
Waiting for camera to switch...
Downloading apk
Analyzing apk

Package: com.jonasjuffinger.timelapse
Version: 1.0.0

Starting task
Starting communication
Traceback (most recent call last):
  File "C:\projects\sony-pmca-re\pmca-gui.py", line 76, in do
  File "C:\projects\sony-pmca-re\pmca\commands\usb.py", line 291, in installCommand
  File "C:\projects\sony-pmca-re\pmca\commands\usb.py", line 84, in installApp
  File "C:\projects\sony-pmca-re\pmca\installer\__init__.py", line 84, in install
ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it

And it still refuses even though I'm using MTP mode

Did you try it with another computer? It's probably better to ask questions about pmca here: https://github.com/ma1co/Sony-PMCA-RE. I cannot really help you, sorry.


runtime-v2: add validation for runtime name

add validation for runtime name, if runtime name is invalid,
containerd will got panic.
Signed-off-by: Ace-Tang<EMAIL_ADDRESS>The problem is found when I test with kata-shim, and write the wrong runtime
#ctr run --runtime containerd-shim-kata-v2 -d reg.docker.alibaba-inc.com/base/busybox:latest c1 top
ctr: transport is closing: unavailable

containerd panic log
panic: runtime error: index out of range

goroutine 129 [running]:
github.com/containerd/containerd/runtime/v2/shim.BinaryName(0xc42003f4e0, 0x17, 0x3, 0x6)
    /home/ace/gosrc/src/github.com/containerd/containerd/runtime/v2/shim/util.go:76 +0x157
github.com/containerd/containerd/runtime/v2/shim.Command(0x7fcfef4c4f60, 0xc4205232c0, 0xc42003f4e0, 0x17, 0xc42035a000, 0x1f, 0xc4203cc640, 0x38, 0xc420315ac0, 0x3, ...)
    /home/ace/gosrc/src/github.com/containerd/containerd/runtime/v2/shim/util.go:51 +0x1af
github.com/containerd/containerd/runtime/v2.(*binary).Start(0xc42083d560, 0x7fcfef4c4f60, 0xc4205232c0, 0x0, 0x0, 0x0)
    /home/ace/gosrc/src/github.com/containerd/containerd/runtime/v2/binary.go:63 +0x155
github.com/containerd/containerd/runtime/v2.(*TaskManager).Create(0xc4203c7180, 0x7fcfef4c4f60, 0xc4205232c0, 0xc420157e08, 0x2, 0xc420523380, 0xc420315a80, 0x1, 0x1, 0xc420374210, ...)

Codecov Report

Merging #2729 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2729      +/-   ##
==========================================
- Coverage   43.75%   43.73%   -0.03%
==========================================
  Files         100      100
  Lines       10725    10731       +6
==========================================
  Hits         4693     4693
- Misses       5301     5307       +6
  Partials      731      731

Flag
Coverage Δ

#linux
47.4% <0%> (-0.03%)
:arrow_down:

#windows
40.88% <0%> (-0.03%)
:arrow_down:

Impacted Files
Coverage Δ

runtime/v2/shim/util.go
0% <0%> (ø)
:arrow_up:

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 9c1db67...5b2136e. Read the comment docs.

LGTM

LGTM


line 186

Hi Anshul lab,
I tried your script with no options specified but got an error. The same error occurred when I ran your example command. Any ideas of that?
Thanks.
Brian$ python3 ENCODE_downloader.py
File "ENCODE_downloader.py", line 186
print '# of downloads exceeded the limit (%d), retrying in 20 seconds...' % (args.max_download,)
^
SyntaxError: invalid syntax

I updated the code to take in search query URL in command line argument.
Please see an example on README.


Orders error missing headers

I am trying to figure out how to get the StatusCode and timestamp from the Headers of an error response. Is this even possible? When logging out the response and error when throttled, there is no StatusCode or Header fields that I can see.
Code:
const params = {
    Version: '2013-09-01',
    Action: 'ListOrders',
    SellerId: process.env.SELLER_ID,
    'MarketplaceId.Id.1': 'ATVPDKIKX0DER',
    MWSAuthToken: process.env.MWS_TOKEN,
    LastUpdatedAfter: '2018-12-14T00:00:00.000Z',
};

amazonMws.orders.search(params, (error, response) => {
    console.log(response);
    console.log(error);
});

Logged in the console:
null
{
  Type: { },
  Code: 'RequestThrottled',
  Message: 'Request is throttled',
  RequestId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'
}

@median-man
I have tried in many different way and I always found the statusCode & Header.
    amazonMws.orders.search({
        'Version': '2013-09-01',
        'Action': 'ListOrders',
        'SellerId': 'RANDOM',
        'MarketplaceId.Id.1': 'RANDOM',
        'LastUpdatedAfter': '2018-12-14T00:00:00.000Z'
    }, function (error, response) {
        if (error) {
            console.log('error ', error);
            return;
        }
        console.log('response', response);
    });

{
    Type: {},
    Code: 'RequestThrottled',
    Message: 'Request is throttled',
    Headers:
      {
          'x-mws-quota-max': 'unknown',
          'x-mws-quota-remaining': 'unknown',
          'x-mws-quota-resetson': 'unknown',
          'x-mws-timestamp': '2018-12-17T11:20:12.477Z',
          'content-type': 'text/xml',
          'content-charset': 'unknown',
          'content-length': '291',
          'content-md5': 'unknown',
          date: 'Mon, 17 Dec 2018 11:20:12 GMT'
      },
    StatusCode: 503,
    RequestId: 'RANDOM'
};

Thanks for getting back to me. Do you think the problem I'm experiencing (missing Headers and StatusCode) could somehow be related to the Node version or OS? I'm using Windows 10 and Node 10.13.

My apologies. I joined the project and just now noticed that it was using v 0.0.18. After upgrading to 0.0.26 I get status codes. Thanks for sharing your work.


[Docs] Guidance on how to add components, routes

I'd like to see some guidance on how to add components, routes, etc to the project.
For example, the components have a folder structure a bit similar to what angular-cli generates, is it recommended to add new components via angular-cli generator?
Some other (maybe yeoman etc) generator?
Some specific npm/gulp tooling?
Just manually create the folders and files? (which is OK, if that's the expectation)
Same of course for other things like routes, pipes, etc. but I think it's more of a question for components.
I couldn't find that in the readme or wiki. The wiki shows adding external stuff, but not project items like components.
Can someone please mention the recommended approach for these?

Uh. That was actually meant to be https://github.com/mgechev/angular2-seed/issues/605
What's the difference between both?


i18n - fiat

Changes

Put strings in localization macro
I think we were moving away from "camel case" (e.g. "Connect A Bank Account" --> "Connect a bank account"), so I have that changed.
Fix concatenated strings (hard to translate)

??

There are strings hardcoded to "Odysee". Leaving as is for now, should probably be a variable.

@kauffj, assigning to you for review since you were gonna update the strings.  If it ends up with lots of delta, just close this one and I'll re-open a new one with your changes.

I don't want to merge this and cause extra work for @mayeaux to reconcile. Anthony, please bring this into your ongoing work.

We can merge this and I can pull it into my current workflow without any issue.


fix: contract examples with new genvm

Fixes #634
What

fixed football prediction market contract example
added tests to check resolution data

Why

to check potential failures in executing a contract that calls a website

Testing done

tested the new feature
tested the bug fix
executed integration tests

Decisions made

Checks

[X] I have tested this code
[X] I have reviewed my own PR
[X] I have created an issue for this PR
[X] I have set a descriptive PR title compliant with conventional commits

Reviewing tips
Check the new contract version regarding the access of the storage variables
User facing release notes
Improved example contracts and integration tests

@cristiam86 why didn't has_success_status catch these bugs in the contract?

@cristiam86 why didn't has_success_status catch these bugs in the contract?

Because the transaction execution is done and they all agree that it is an error. That's something we need to add to the tests.


[WIP/Idea] Implement inbuilt function print

Add environment to lir::evaluate
This is just a quick & somewhat dirty approach of implementing #44
@christianpoveda Was my way of implementing it correct or is there a easier way. Some parts are just copy&paste.
I added a LangEnv type for stdout so I can overwrite it the tests but I'm open to discuss different approaches to solve the underlying problem of global variables that are accessed during evaluation.

Oh wow, I didn't expect this PR! Thanks! I will be AFK today so I'll drop my raw, unedited comments here:
So, I think that stateful evaluation is an step in the right direction. We'll need that if we want to have a decent language in terms of performance.
However, I think it will be more future proof to write a Machine struct (probably inside a new top-level module called eval or machine idk) and let the evaluation environment be a field of that new struct.
I'm asking for this because eventually we will have more state, some of it will be to interact with the OS like print but also the actual runtime of the language, like the heap, the stack  and even a GC instead of relying on Rust for memory management. And putting all that as arguments of a function won't take us very far.
The idea would be to (eventually and in another PR) move all the logic of lir/eval to this new machine.
My second comment goes about the IR of these new built-in functions. I think it would me more scalable to keep them contained in a single type. Something like
enum BuiltIn {
    Print
}

And add a new variant inside lir::Term:
enum Term {
    ...
    BuiltIn(Builtin),
}

Such that the LIR of a print call looks like Term::App(box Builtin(Builtin::Print), box t1).
There are some questions that we haven't answered yet, like what happens if someone writes:
print = fn(x: Int) do x end
print(10)

Should we forbid print as a name for variables and parse it always as a BuiltIn? Is not like is hard to do but we have to take that decision.
Thanks for this PR, I'd never imagine that this project will gain this level of traction so quickly, I hope these comments I wrote above aren't discouraging.

Thanks for this PR, I'd never imagine that this project will gain this level of traction so quickly, I hope these comments I wrote above aren't discouraging.

No problem the comments are great I will try experimenting with it a bit more.
PS: Have a nice AFK time 😄

Tried to follow your second comment. The code is far from perfect. It is not clear who manages the global knowledge about the bulletins during type checking and lowering operations. But it works (tests pass). I added a test for the redefined case to see the result in the test case.
Feel free to comment 😃.

Makes sense to forbid print from being a variable name 👍

I like the new BuiltInFn type. However I think we can move its creation all the way back to parsing. Can you move it to the ast module and add a new module parser::built_in_fn to parse them? I think you need to get into parser::name and add "print" to KEYWORDS to avoid parsing ambiguities.
Doing things that way forbids programs like print = 5 because the parser will say that print is a BuiltInFn instead of a Name

Another batch of changes. I added the either crate to differentiate between a builtin fn call and a normal one.
Also I added a first version of a Machine struct. I'm not sure if we still need the step_in_place method now. The only benefit I see is that we reuse a created Box but maybe the overhead of un/packing is higher than just creating a new Box?

Hmm your changes made me think that we might need to do certain fixes to allow more than names in calls. In other words if we are able to parse stuff like:
(fn(x: Int) do x end)(1)

Then we can change Node::Call(Name, Block) to Node::Call(Node, Block) and then add primitive functions as simple Nodes. Which would simplify a lot of what needs to be done in the other IRs.

Sure open a issue for the encountered problems. And implement this nicer when we have a more generic representation of function calls.

Moved the non pub evaluation functions of Machine to the eval submodule.
Changed Machine and LangEnv to be generic over Write instad of using &dyn Trait. It makes creating a Machine a bit easier because we don't have to worry about lifetimes since it can take ownership of its members. But if we add more members with different generics the Machine signatur may become harder to read.

Sure open a issue for the encountered problems. And implement this nicer when we have a more generic representation of function calls.

Yes we can come back to this when we have all the missing parts. I think that we could do this an small project goal and tag the issues we need to get here.

I've created https://github.com/christianpoveda/pijama/issues/54 and https://github.com/christianpoveda/pijama/issues/55 to address the improvements we need to do before getting here.

Made this a draft because it doesn't make sense to merge it in its current form and if we can implement it it is probably better to to it in another PR. But we should keep it open to preserve the discussion until the underlying issue is implemented.

Yes I feel we're missing a space to have this sort of quick discussions. But let's keep this one to recycle the parts you've already changed.


.dev.js files included production builds

Expected Behavior
Ideally, for NODE_ENV=production builds, we should produce builds that are as small and optimised as feasible.
Current Behavior

Code from redux-devtools can be found in build output
As-is, a minimal react + redux-bootstrap build is ~400KB minified
Manually dropping .dev.js files in redux-bootstrap results in build that is ~280KB
Admittedly this only ends up with an extra ~120KB
For a minimal app this is quite a waste, but this will likely be a much smaller fraction of a fully-featured complex app

Possible Solution
Should we decide this is something that should be addressed, I'm not 100% sure how to achieve this.

If end up with no require('....dev') lines prior to build tools crawling the module dependency graph, then they won't be included at all.
Or perhaps the build tools themselves can be configured to stub these out when NODE_ENV=production, in which case we could supply instructions on how to configure this.

Steps to Reproduce (for bugs)

Create a fresh React project using https://github.com/facebookincubator/create-react-app
add redux-bootstrap as we instruct
npm run build
observe file sizes in the build directory
change node_modules/redux-bootstrap/lib/containers/root.js to avoid require('./root.dev')
change node_modules/redux-bootstrap/lib/store/configure_store.js to avoid require('./configure_store.dev')
npm run build
observe file sizes in the build directory

Your Environment

Version used: 1.0.0-rc.1
Environment name and version (e.g. Chrome 39, node.js 5.4): node 6.3.1
Operating System and version (desktop or mobile): ArchLinux
Link to your project: https://github.com/jokeyrhyme/react-redux-bootstrap-example

By the way, redux-bootstrap works terrifically with create-react-app. Very simple to combine.
I'll try to put a blog post up about it.

Do you know what is used internally by create-react-app to create the build output? is it webpack or browserify?

@remojansen looks like its webpack: https://github.com/facebookincubator/create-react-app/blob/master/package.json#L58

Here's the example project: https://github.com/jokeyrhyme/react-redux-bootstrap-example

Do you have access to the webpack config file? If so you should be able to configure the environment:
plugins: [
  new webpack.DefinePlugin({
    'process.env': {
      'NODE_ENV': JSON.stringify('production')
    }
  })
],

Then the non-production modules should not be included in the build.

@remojansen they already set that:

https://github.com/facebookincubator/create-react-app/blob/v0.1.0/scripts/build.js#L10

https://github.com/facebookincubator/create-react-app/blob/v0.1.0/config/webpack.config.prod.js#L113

I think the problem is that NODE_ENV === 'production' is a run-time check, where as require('...') has static implications during build. Build tools don't parse that run-time check, but they do honour the static imports.

I don't really know how to fix it them :( I know in webpack you are allowed to do:
if(NODE_ENV === 'production') {
  import "A";
}  else {
  import "B";
}

But in typescript all imports must be in the top of the file (this is based on the ECMAScript standard):
 import * as A from "A";
 import * as B from "B";

if(NODE_ENV === 'production') {
  export { A };
}  else {
  export { B };
}

Well, for webpack, maybe we can use this:

https://webpack.github.io/docs/configuration.html#resolve-alias

We could alias the .dev.js files to the .prod.js files? This is still something the developer would have to do, but we provide instructions perhaps?

It would be nicer if there was a more automatic or built-in way of doing this though. As the Facebook React CLI doesn't really let you mess with configuration without completely "ejecting" from all the nice automatic stuff it does for you.

@remojansen I took a look at starter kit: https://github.com/davezuko/react-redux-starter-kit/blob/3fabc5f4/src/store/createStore.js#L17
It looks like they don't directly require() the dev tools module. They just hook into it if it is already present and globally-exposed. I'll keep looking for more examples of how to handle this.

Hi the code sample that you have provided requires the users to have the redux-devtools chrome extension installed. Maybe we can ask for help at https://github.com/facebookincubator/create-react-app/issues/102 ?

Hi @jokeyrhyme did you solve this problem? I think the solution is something like https://github.com/blacksonic/typescript-webpack-tree-shaking

Tree shaking would be the answer, but it would require particularly thorough tree shaking. All conditions would need to be evaluated at build time, which seems more than what most people consider to be tree shaking.
My understanding is that tree shaking performs build-time static analysis of all import and export statements, determines which variables within each module are at all referenced by anything that leads to an export, and ditches all code that is unrelated.
I've personally just ditched the redux dock / panel and switched over completely to the devtools extension:

https://github.com/zalmoxisus/redux-devtools-extension#usage
https://github.com/blinkmobile/ketchum-all-ui/blob/master/src/redux/store.js

The extensions is a much better experience than the panel ever was, and it's actively maintained (unlike the panel).

Thanks for that. I will try to migrate to the extension then 😄

This should be fixed on 3.1.0 you need to use https://github.com/zalmoxisus/redux-devtools-extension to access the devtools.


Stashed entries

As shown in bash-git-prompt we could have a way to show stashed entries.
User stories:

[ ] As a user I want to see the number of items in stash.

Related to #3 because of extra symbols being used.

After having a quick look at the API for git2-rs stash query it seems that there is nothing suitable when having an immutable repository reference. I'll leave this as a future improvement.


git push -u origin master

Right now we don't have a website I will update you once we already have
one this is a fresh server.
On Thu, Jul 13, 2023 at 9:00 PM Daniel Filho @.***>
wrote:

@.**** commented on this pull request.
In supported_servers.json
https://github.com/4RTools/4RTools/pull/207#discussion_r1262524118:

@@ -745,6 +745,11 @@
"site": "https://landverse.com/",
"hpAddress": "0x012BE4CC",
"nameAddress": "0x012C0F08"

},
{
"name": "uMMO",
"hpAddress": "010DCE10",
"nameAddress": "010D5DA8"
}

⬇ Suggested change

In supported_servers.json
https://github.com/4RTools/4RTools/pull/207#discussion_r1262524898:

@@ -745,6 +745,11 @@
"site": "https://landverse.com/",
"hpAddress": "0x012BE4CC",
"nameAddress": "0x012C0F08"

},
{
"name": "uMMO",
"hpAddress": "010DCE10",
"nameAddress": "010D5DA8"
}

Hey @DaemonSpade https://github.com/DaemonSpade, thanks for the PR. Do
you mind to add the site of this server?
—
Reply to this email directly, view it on GitHub
https://github.com/4RTools/4RTools/pull/207#pullrequestreview-1528385123,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHV5UOELGA5TTRX4TGUDAKTXP7WQLANCNFSM6AAAAAA2IK77GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


chore: use Batteries test driver directly in the lake file

With leanprover/lean4#4261, we can specify a test driver from a dependency. We do this with Batteries test driver. Previously, the test driver from Batteries was called via scripts/test.lean which is now removed.

@semorrison I was looking at lake test for my class and noticed this todo. Local testing seems good but you would know better. Let me know if anything is amiss.

I don't really know how to review this, since I do not know the implications of the changes!  However, I can see that CI was successful and that the tests have been run, so this looks good to me!  :smile:

@semorrison Could you take a look at this when you have a spare moment?


Support dumping out rendered cloudformation templates for each stack

Output looks like:
$ stacker build -r us-west-2 conf/lunohq/development.env conf/lunohq/config.yaml --dump dump
[2016-05-17T14:05:33] Dumping "Create/Update stacks"...
[2016-05-17T14:05:33] Writing stack "dev-lunohq-vpc" -> dump/vpc-3ea2d331.json
[2016-05-17T14:05:33] Writing stack "dev-lunohq-empireDB" -> dump/empireDB-2bc493a4.json
[2016-05-17T14:05:33] Writing stack "dev-lunohq-empireMinion" -> dump/empireMinion-6b3bcb53.json
[2016-05-17T14:05:33] Writing stack "dev-lunohq-empireController" -> dump/empireController-92678c3c.json
...

Awesome 👍 Did you get a chance to look at the local parameters 'issue'?

Sweet 👍 this will be really nice to have.
I was thinking it would be cool if stacker just compiled all of the blueprints down to a single "metastack" template, which could then be executed by stacker itself. If we exposed a subcommand to execute a metastack template, then this could open up other use cases for stacker (people that want the "stack glue" aspect of stacker, but not troposphere/python), and you could just dump the metastack to stdout (e.g. stacker compile | stacker execute).
Anyways, definitely not something we should do in this PR, just something I was thinking about.

Honestly for the non-troposphere/python users, I think we should provide a concept of 'drivers'.  You don't need to use a Blueprint in that case, we could have a 'json' driver or something that just reads a regular old CF template and uses that.


Constant not defined

n_components is not defined in the usege example.

This is a fork; the main repository is here: https://github.com/mmp2/megaman


⚠ ClamAV has degraded performance

In 7a52d71, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 476 ms

Resolved: ClamAV performance has improved in bb8cf0f.


[enhancement]: Please support FLUX.1

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
<EMAIL_ADDRESS>What should this feature add?
Please support the new open-weights models from Black Forest Labs, FLUX.1.
https://huggingface.co/black-forest-labs
Alternatives
No response
Additional Content
No response

yes please really really need it

Flux is super impressive, can't wait!

Flux is super impressive, can't wait!

🙏yes please

Can't wait to see fulx support in InvokeAi

please add flux，thanks alot

After extensively testing the versatility and accuracy of the Flux 1 model I can confidently say adding this model to Invoke AI would be a very large +. The quality of this model is like none other, creating accurate text at 98% times of the requests, having the prompt accuracy of Dall-E yet the versatality of Midjourney supporting Art-mediums from Watercolor painting to Anime/Manga Sketches. A rather impressive creation of Black Forrest indeed.

Having that would be awesome!!!

I already have Flux working in an InvokeAI workflow

I already have Flux working in an InvokeAI workflow

would you be able & willing to create instructions as to how you did this? I think it would be very useful for other users as well as Flux is a very high-end model but at the moment most people need to use ComfyUI to use it.

I already have Flux working in an InvokeAI workflow

would you be able & willing to create instructions as to how you did this? I think it would be very useful for other users as well as Flux is a very high-end model but at the moment most people need to use ComfyUI to use it.

New Diffusers release now supports FluxPipeline now: https://github.com/huggingface/diffusers/releases/tag/v0.30.0

If that didn't work for you, then this:

If that didn't work for you, then this:

I can't do either.
I downloaded models from Civit and Hugginface and when it tries to import them via scan folder, invoke just crashes in the commandline.
I can't import it from hugging face since you have to sign in.

please support flux ！

didn' t worked downloading form HF black-forest-labs/FLUX.1-schnell

I already have Flux working in an InvokeAI workflow

would you be able & willing to create instructions as to how you did this? I think it would be very useful for other users as well as Flux is a very high-end model but at the moment most people need to use ComfyUI to use it.

yeah Lies

Howdy folks, I have no doubt that the Invoke team will be more than aware of Flux, what a leap forward it is and how the community is very keen to get it working with their favourite tool.
Although it's great to see the enthusiasm in the comments I would suggest showing your interest with an emoji reaction on the post, freeing up the comments for folks that have suggestions on how to help implement it.
This will help keep the signal to noise ratio high and although I'm not a maintainer - I could imagine I might find it a little stressful or feel like it's being demanded / expected (although I'm sure that's not the case).
Just my 2c and a ❤ out to the maintainers of such a great open source tool.

Fair point
On Fri, Aug 9, 2024 at 17:41 Sam @.***> wrote:

Howdy folks, I have no doubt that the Invoke team will be more than aware
of Flux, what a leap forward it is and how the community is very keen to
get it working with their favourite tool.
Although it's great to see the enthusiasm in the comments I would suggest
showing your interest with an emoji reaction on the post, freeing up the
comments for folks that have suggestions on how to help implement it.
This will help keep the signal to noise ratio high and although I'm not a
maintainer - I could imagine I might find it a little stressful or feel
like it's being demanded / expected (although I'm sure that's not the case).
Just my 2c and a ❤ out to the maintainers of such a great open source
tool.
—
Reply to this email directly, view it on GitHub
https://github.com/invoke-ai/InvokeAI/issues/6712#issuecomment-2278790316,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJSLCLGZ2AZJZEU5E6YQZO3ZQUZRNAVCNFSM6AAAAABL5FTWSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYG44TAMZRGY
.
You are receiving this because you commented.Message ID:
@.***>

I already have Flux working in an InvokeAI workflow

so was this a lie?

I already have Flux working in an InvokeAI workflow

so was this a lie?

Yes because they didn't screenshot the import outcome like @MDsniper  did. (╯°□°)╯︵ ┻━┻

Error is
[2024-08-10 13:49:18,230]::[ModelInstallService]::ERROR --> Model install error: black-forest-labs/FLUX.1-dev
InvalidModelConfigException: Unable to determine model type for /mnt/Store/Applications/InvokeAi/models/tmpinstall_dd9x7x7x/FLUX.1-dev; class FluxPipeline is not one of the supported classes [StableDiffusionPipeline, StableDiffusionInpaintPipeline, StableDiffusionXLPipeline, StableDiffusionXLImg2ImgPipeline, StableDiffusionXLInpaintPipeline, LatentConsistencyModelPipeline, AutoencoderKL, AutoencoderTiny, ControlNetModel, CLIPVisionModelWithProjection, T2IAdapter]

bump!

UP！

Any updates would be great!

This is why we use other interfaces  The devs here dont care that you want it.  Nor do they care about Playground 2.5, or Kolors, or Aura, Flux, SD 3, or presets for Pony, or for so much, so much, because you aren't a paying customer.   Search all you like, there is no guide to install these major models.  So, download pinokio and choose from several different UI's to use them.. Even if you have 4 gigs of vram.. Some people just care enough to get things to work (and in 1 click installs). pinokio.computer (web site/download the app) will only give you one problem.. harddrive space.

For what it's worth, I've been using "Draw Things" on my Mac, which already supports Flux. The UI is a little quirky, but it's a native app and runs very well. And it's free.

Folks, come on it's ok to be excited and even a little impatient at times but there's no need to rip out open source maintainers that write software for you for free. They owe you nothing.

We're thinking in the simple way. If other apps can run flux with a little research and upgrades, why anybody in community not making a PR for flux?

I'm fairly sure there are PRs underway to get Flux working, e.g. https://github.com/invoke-ai/InvokeAI/pull/6739 - it just seems they're not ready yet.
When you compare InvokeAI to some of the other tools out there that have implemented it - InvokeAI is more of a product, it's large and is generally held to high standards, this is quite different from something like Comfy which is esentially a lot of different peoples scripts and packages that can be glued together in various ways - people can make great things due to the flexibility but - it's also a lot harder and much less refined.
I'm sure that if it was as simple as simply supporting the model, invoke would already have flux, but while I have no insider knowledge I'm assuming it's probably included as part of a larger piece of work with the intent of a better integrated outcome. (I'm just guessing here).

You're right. I think I got a little too exited about flux. Also that pr was opened 2 days ago. I've subscribed now and will keep a close eye on it.

bump!

well, 4 thumbs down from devs I guess. Deleting invokeAI. I'll will try pinokio as @kwal559 mentioned
Thank you @sammcj

From the record, I am one of the people that downvoted you and I am neither a developer of nor contributor to Invoke. The reason being that when you're subscribed to an issue GitHub sends an email for each comment. Your comment of "bump!"  There isn't even anything to "bump" since this isn't a classic forum thread where visibility is affected by the most recent comment. It's also especially glaring in light of the extremely kind and patient comment from @sammcj earlier informing people that the proper way to express interest in an issue on GitHub is via reaction emojis.
Now, I have to apologize to everyone I have further spammed for simply making this comment, but I wished to clarify things in case passerbys were left with the wrong impression due to your misattributed slight.

@sammcj - Thanks. :)
For all, please recognize that unlike many other UIs, we have a much wider maintenance and development mandate. I appreciate people voicing their interest in it.
We’re aware of Flux, and we’re actively looking at setting up the foundation to support it long term, but that is a rapidly changing landscape.
In addition to building this application, we’re actively spearheading work with the Open Model Initiative (joined the Linux Foundation this week), working to develop stronger IP protection for creators using these tools, and working on one of the biggest updates there has ever been to the canvas. We’re doing a lot for the ecosystem.
If you’re interested in seeing the process of adopting new features speed up, consider participating as a contributor. Else, I’d ask that you serve as an active cheerleader and vocal evangelist of our efforts as opposed to an entitled user of free and open source software.
Thanks to all who’ve been patient advocates - I hope you’ll be pleased with what we’ve got planned for you.

We're thinking in the simple way. If other apps can run flux with a little research and upgrades, why anybody in community not making a PR for flux?

If it's so simple, what are you waiting for to contribute to this repo ? :roll_eyes:

we need flux,please

@sammcj - Thanks. :)
For all, please recognize that unlike many other UIs, we have a much wider maintenance and development mandate. I appreciate people voicing their interest in it.
We’re aware of Flux, and we’re actively looking at setting up the foundation to support it long term, but that is a rapidly changing landscape.
In addition to building this application, we’re actively spearheading work with the Open Model Initiative (joined the Linux Foundation this week), working to develop stronger IP protection for creators using these tools, and working on one of the biggest updates there has ever been to the canvas. We’re doing a lot for the ecosystem.
If you’re interested in seeing the process of adopting new features speed up, consider participating as a contributor. Else, I’d ask that you serve as an active cheerleader and vocal evangelist of our efforts as opposed to an entitled user of free and open source software.
Thanks to all who’ve been patient advocates - I hope you’ll be pleased with what we’ve got planned for you.

So you mean flux is not your first priority. I dont think you guys care ppls thoughts on this platform. Even though you removed upgrade section cuz it is not working and we must download new installer. Dude just forget everything and make flux your first priority.

We're thinking in the simple way. If other apps can run flux with a little research and upgrades, why anybody in community not making a PR for flux?

If it's so simple, what are you waiting for to contribute to this repo ? 🙄

It is not about me. It is about even simple apps have managed to work with flux so why not invoke? Also it's been 2 weeks(18 days) since flux released. Enough said, up! bump! you guys have to make this one for your first priority.
Feel free to thumbsdown this comment. I'll thank you later

@sammcj - Thanks. :)
For all, please recognize that unlike many other UIs, we have a much wider maintenance and development mandate. I appreciate people voicing their interest in it.
We’re aware of Flux, and we’re actively looking at setting up the foundation to support it long term, but that is a rapidly changing landscape.
In addition to building this application, we’re actively spearheading work with the Open Model Initiative (joined the Linux Foundation this week), working to develop stronger IP protection for creators using these tools, and working on one of the biggest updates there has ever been to the canvas. We’re doing a lot for the ecosystem.
If you’re interested in seeing the process of adopting new features speed up, consider participating as a contributor. Else, I’d ask that you serve as an active cheerleader and vocal evangelist of our efforts as opposed to an entitled user of free and open source software.
Thanks to all who’ve been patient advocates - I hope you’ll be pleased with what we’ve got planned for you.

So you mean flux is not your first priority. I dont think you guys care ppls thoughts on this platform. Even though you removed upgrade section cuz it is not working and we must download new installer. Dude just forget everything and make flux your first priority.

We're thinking in the simple way. If other apps can run flux with a little research and upgrades, why anybody in community not making a PR for flux?

If it's so simple, what are you waiting for to contribute to this repo ? 🙄

It is not about me. It is about even simple apps have managed to work with flux so why not invoke? Also it's been 2 weeks(18 days) since flux released. Enough said, up! bump! you guys have to make this one for your first priority.
Feel free to thumbsdown this comment. I'll thank you later

+1

@sammcj - Thanks. :)
For all, please recognize that unlike many other UIs, we have a much wider maintenance and development mandate. I appreciate people voicing their interest in it.
We’re aware of Flux, and we’re actively looking at setting up the foundation to support it long term, but that is a rapidly changing landscape.
In addition to building this application, we’re actively spearheading work with the Open Model Initiative (joined the Linux Foundation this week), working to develop stronger IP protection for creators using these tools, and working on one of the biggest updates there has ever been to the canvas. We’re doing a lot for the ecosystem.
If you’re interested in seeing the process of adopting new features speed up, consider participating as a contributor. Else, I’d ask that you serve as an active cheerleader and vocal evangelist of our efforts as opposed to an entitled user of free and open source software.
Thanks to all who’ve been patient advocates - I hope you’ll be pleased with what we’ve got planned for you.

So you mean flux is not your first priority. I dont think you guys care ppls thoughts on this platform. Even though you removed upgrade section cuz it is not working and we must download new installer. Dude just forget everything and make flux your first priority.

We're thinking in the simple way. If other apps can run flux with a little research and upgrades, why anybody in community not making a PR for flux?

If it's so simple, what are you waiting for to contribute to this repo ? 🙄

It is not about me. It is about even simple apps have managed to work with flux so why not invoke? Also it's been 2 weeks(18 days) since flux released. Enough said, up! bump! you guys have to make this one for your first priority.
Feel free to thumbsdown this comment. I'll thank you later

+1

+1

@brhndursun

Deleting invokeAI. I'll will try pinokio as @kwal559 mentioned

This is not an airport, no need to announce your departure

Thank you for your funny joke but I think I can tell anything except hurting your feelings. Did that hurt you?
Also I made my own way to use flux. I told you, it is not that hard. I guess invoke core system makes it harder to implement. I can use comfy too but I just want to use it in invoke that's all.

@brhndursun

Deleting invokeAI. I'll will try pinokio as @kwal559 mentioned

This is not an airport, no need to announce your departure

Thank you for your funny joke but I think I can tell anything except hurting your feelings. Did that hurt you?
Also I made my own way to use flux. I told you, it is not that hard. I guess invoke core system makes it harder to implement. I can use comfy too but I just want to use it in invoke that's all.

So if you found your own way, you could of found a way to implement it into invokes codebase and shared it.

So why not just fork and push and share it with us?

@brhndursun

Deleting invokeAI. I'll will try pinokio as @kwal559 mentioned

This is not an airport, no need to announce your departure

Thank you for your funny joke but I think I can tell anything except hurting your feelings. Did that hurt you?
Also I made my own way to use flux. I told you, it is not that hard. I guess invoke core system makes it harder to implement. I can use comfy too but I just want to use it in invoke that's all.

So if you found your own way, you could of found a way to implement it into invokes codebase and shared it.

So why not just fork and push and share it with us?

It is working on pure python without front end or invoke. I don't have time to work with invoke system. You can use ComfyUI or huggingface spaces too.

As much as I love comfyUI I would also like to be able to use invoke with Flux, so please add support.

I am also waiting for it!

An initial experimental implementation of Flux is now available on v4.2.9rc1! We will be working on extending it to support different formats of the base model as well as loras/img2img/etc over the next week or two. Please refer to the release notes to see how flux is installed and used in its current form within Invoke if you choose to install this release candidate. Thank you everyone for your patience!

Love your work! ❤

Thank you everyone for your patience
...
everyone
👀
🤣 😅

Seriously, looking at your changes that was quite an effort - well done!

@brandonrising and everyone else who contributed to that PR, Thank you!

So today I  saw flux in invoke to downlaod but I can't select it to use:

If any one knows how to use it please let me know

https://github.com/invoke-ai/InvokeAI/releases/tag/v4.2.9rc1
https://private-user-images.githubusercontent.com/6750888/361906910-474d2f8a-cc72-4c09-8a82-fe434afbc37e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ4ODg4MjksIm5iZiI6MTcyNDg4ODUyOSwicGF0aCI6Ii82NzUwODg4LzM2MTkwNjkxMC00NzRkMmY4YS1jYzcyLTRjMDktOGE4Mi1mZTQzNGFmYmMzN2UucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjhUMjM0MjA5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NGNiZTM5Y2FhMTBiZWMyYTdmNWE0NGIxMDNhZGQyYjI4MDQ4MDViM2MyYTM1NjYzYTVhNWYwOWJjN2U4Mzk1MyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.aaxXlOdJfvgTIce_uRFJEBj0ijL1-KDGGTegwebS8NI

Below are additional details on which model to use based on your system:

FLUX dev quantized starter model: non-commercial, >16GB RAM, ≥12GB VRAM
FLUX schnell quantized starter model: commercial, faster inference than dev, >16GB RAM, ≥ 12GB VRAM
FLUX dev starter model: non-commercial, >32GB RAM, ≥24GB VRAM, linux OS
FLUX schnell starter model: commercial, >32GB RAM, ≥24GB VRAM, linux OS

Are these minimum requirements ?
Or recommendations for better performance ?

Hi @JorgeR81, by enabling CPU offloading I'm able to run FLUX.1-dev on my laptop with Nvidia RTX 500 Ada Generation (4094MiB) and it takes around 260 seconds to generate an image 1024x1024.
But currently I'm not able to run it with InvokeAI since (in the best of my knowledge) CPU offloading is not configurable. In case, it would be awesome to make it configurable

I'm fairly sure there are PRs underway to get Flux working, e.g. #6739 - it just seems they're not ready yet.
When you compare InvokeAI to some of the other tools out there that have implemented it - InvokeAI is more of a product, it's large and is generally held to high standards, this is quite different from something like Comfy which is esentially a lot of different peoples scripts and packages that can be glued together in various ways - people can make great things due to the flexibility but - it's also a lot harder and much less refined.
I'm sure that if it was as simple as simply supporting the model, invoke would already have flux, but while I have no insider knowledge I'm assuming it's probably included as part of a larger piece of work with the intent of a better integrated outcome. (I'm just guessing here).

"Glued together" one way of saying its unprofessional. geesh lol


RegisterWithoutUsername view has a localization Bug

Describe the bug
Localization bug
all labels show english code names for all translations
To Reproduce
Steps to reproduce the behavior:
just open the form after setting the appsettings.json ResolutionPolicy = Email
Relevant parts of the log file
None

Thank you! Fixed in 1.0.0-rc3 #703


Add Event.custom

See https://github.com/eeue56/elm-html-test/pull/29/files/8369f064287ca2692b60f79da9ae1279688c1274#diff-bb04a6441906f123b8fabc331ba4634e

@eeue56 ping! 😄

@eeue56 I'd like to do a release - are we good without this, or do you think it's necessary? Or something else?

sorry, been busy

It's all good, thanks! 🤘


False alarm from ClassInitializationDeadlock for inner enum implementing outer interface with default method

Error Prone 2.27.0 produces a ClassInitializationDeadlock warning for the following code:
public interface TestInterface {

  default Object foo() {
    return null;
  }

  public enum TestEnum implements TestInterface {
    INSTANCE;
  }
}

The exact message is
TestInterface.java:8: warning: [ClassInitializationDeadlock] Possible class initialization deadlock: TestEnum is a subclass of the containing class TestInterface
    INSTANCE;
    ^
    (see https://errorprone.info/bugpattern/ClassInitializationDeadlock)

Interestingly, it does not happen with a class instead of an enum, nor if I remove the default method.
My assumption is that this is a false alarm, because I don't see how initializing TestInterface would require initializing TestEnum.

Thanks, this is a bug, it should be handling enums as well as classes here, instead of scanning the member enum's fields:
https://github.com/google/error-prone/blob/fd9b826d595cabe56a66c060ce52504cd24630af/core/src/main/java/com/google/errorprone/bugpatterns/ClassInitializationDeadlock.java#L74-L75
If there was a field declared directly in TestInterface (instead of nested instead the enum) that could deadlock:
public interface TestInterface {

  default Object foo() {
    return null;
  }

  static final TestInterface FOO = TestEnum.INSTANCE; // possible deadlock

  public enum TestEnum implements TestInterface {
    INSTANCE;
  }
}

It is only reported if the interface has a default method, because interfaces with default methods can participate in class initialization cycles due to the bit about interfaces with 'non-abstract, non-static methods' in JVMS 5.5

Having the same issue. It so far has broken our builds on every project internal and my open source projects.
@cushon assuming this is fixed for the enum implements interface problem will it still report if you have an interface with default methods and/or static final fields even if those fields and/or methods are not used by the enum?
I assume it is just with cycles but given this bug I'm not sure I understand how this check works.

it will continue to report cases where there's a cyclic dependency between class initializers, including cycles that involve interfaces with default methods and enums.

I pushed a 2.27.1 release with a fix for this.


Proposal: Credentials Retrieve Requests must not request disjoint authentication domains

Background
Currently the OpenYolo specification allows clients to request credentials that are disjoint from the caller's authentication domain.

The set of authentication domains specified in the request may be disjoint from the set of domains known to be related to the requester (via its package name): such requests would allow trusted intermediaries (e.g. keyboard apps, mail clients, etc.) to request credentials that they do not directly own. It is the responsibility of the credential provider to determine whether to permit such requests. Typically, requests should only be permitted for an authentication domain that is provably associated with to the requester, or if the app has been explicitly whitelisted (by the user or provider) to request credentials outside its equivalence class.

Motivation

The motivation to support requesting disjoint authentication domains appears to be an edge case and opens a path for a regression in good identity practices. Retrieving these credentials allows for a 3P to impersonate a user and circumvent good authorization practices. I believe that any client that wishes to request a disjoint authentication domain should instead forward their request to the given requested authentication domain which then may use OpenYolo if they choose.
This change will reduce the complexity of the API and SPI resulting in less work for both credential providers and credential requesters implementing OpenYolo.

Proposal
Remove the ability for clients to request a set of authentication domains in credential retrieve requests.  In its place only the implied authentication domain as determined by the caller's package and signature must be used.
Interested in everyone's thoughts.  Is there a motivating use case to support it?

@smarkovik and @StanKocken were the originators of this idea, it would be good to hear their perspective. I think I support removing this for the initial release and more carefully think about the use cases for "masquerading" as another app for credential retrieval. The most prominent use case (keyboard integration) should have no UI, so that may actually deserve it's own API methods for direct credential retrieval.

At last some chatter on openYolo. I must say it's refreshing to reply on a thread in this repo.
I believe this is quite an important feature in a final api, as it would allow any app to request any credential, which is the sole purpose of a credential manager To manage your credentials. like any browser can open any protocol (ftp, file etc.. ), not only http/s.
True, the. usage is a bit of an edge case, if you're thinking of Google, facebook twitter and linkedin, as they're the BIG authentication domains. which provide a clear entry point however if you think about the wider use case, like, zoom requires my company account to work, same with outlook, even gmail, may reqiure a non-gmail credential to work. So it's an edge case in the Big world but out of 200+ which i have in my account only 10 of them are in the Google Facebook etc. list.
however, I also agree this is a feature we can surely postpone for a future release. Even more to the point, you don't all have to share my opinion, and if everyone here thinks it's obsolete or not required I would agree as there needs to be consensus.
So in short, I am all in favor of postponing it, but I believe it's a feature which has merit.
your thoughts?

A concret example can be a third-party app like Tinder. You can (at least was the case few years ago) use only a Facebook credential. What to do in this case? Tell the developers of this app "you cannot use OpenYolo" or we have to find an alternative solution.
I'm good with the first answer for now, maybe think about the second later?
The way we wanted to do that, as a Password Manager, was to say "This is not the Facebook app, are you sure to provide your Facebook credential".

I think the case you describe for Tinder is actually OK - Tinder can request a credential hint, and specify that it supports Facebook as an authentication method. The user can then select their Facebook account from the hint list, and Tinder uses this hint to begin Facebook authorization for that account. If authorization succeeds, Tinder saves a credential with authentication method "https://www.facebook.com" for future retrieval.
The scope of what @dxslly is discussing is the ability to ask for saved credentials for other apps and domains. The use case I remember discussing with @smarkovik was for an email app to be able to ask for the ID and password for your Google account in order to automatically configure POP3 / SMTP. It is currently the responsibility of the credential provider to decide what to do with such a request:

The provider must correctly identify that the app does not belong to the Google authentication domain equivalence class. This shouldn't be too difficult, using Digital Asset Links, but it's a likely source of security critical bugs.

The provider must decide what to do with such a request. In the Smart Lock for Passwords implementation, we ignore any requests for credentials from authentication domains the app is not provably associated to. Others may instead with to display a picker with a modified, scarier prompt to try and make sure the user understands what they are consenting to.

Both steps are a cause for concern, which is why I think that more careful consideration of this feature is required. A different API method for this case, with much more clearly defined semantics, may be better.

I would also be in favour of a cautious approach here. The example of providing Google credentials to an email app definitely highlights an edge-case that users and third-party apps might want supported. Whether it should be supported is something that I think warrants more discussion though, for the reasons that @dxslly and @iainmcgin have highlighted above. With that in mind, I would be happy to see support for requesting disjoint authentication domains removed for now.

+1
http://www.contentsquare.com/
Stanojko Tancho Markovikj
https://data.sigilium.com/signatures/rcevuJOOuCK6-0hyNCIuGCIISRCzQrc/link?element=name
Mobile Engineering Manager
https://data.sigilium.com/signatures/rcevuJOOuCK6-0hyNCIuGCIISRCzQrc/link?element=job
+33 6 51 17 53 54
https://data.sigilium.com/signatures/rcevuJOOuCK6-0hyNCIuGCIISRCzQrc/link?element=mobile
<EMAIL_ADDRESS>50 avenue Montaigne - 75008 Paris
https://data.sigilium.com/signatures/rcevuJOOuCK6-0hyNCIuGCIISRCzQrc/link?element=map_marker
https://www.facebook.com/ContentSquareGlobal
https://twitter.com/ContentSquare
https://www.youtube.com/user/Weballwin1
https://www.linkedin.com/company/contentsquare
https://data.sigilium.com/signatures/rcevuJOOuCK6-0hyNCIuGCIISRCzQrc/redirect_link
On Wed, Mar 1, 2017 at 10:32 PM, Michael Verde<EMAIL_ADDRESS>wrote:

I would also be in favour of a cautious approach here. The example of
providing Google credentials to an email app definitely highlights an
edge-case that users and third-party apps might want supported. Whether it
should be supported is something that I think warrants more discussion
though, for the reasons that @dxslly https://github.com/dxslly and
@iainmcgin https://github.com/iainmcgin have highlighted above. With
that in mind, I would be happy to see support for requesting disjoint
authentication domains removed for now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openid/OpenYOLO-Android/issues/5#issuecomment-283477102,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8OPeIhzydF4WLlCiaHe2I-BIAHNtllks5rheP6gaJpZM4MOtrz
.

"The example of providing Google credentials to an email app definitely highlights an edge case"
Actually there is nothing the email app can do with your Google password, we don't allow IMAP authentication via Google passwords (anymore). Such apps need to use OAuth (via OAuth for Native Apps).

The same principle applies to accessing ISP controlled mail servers (e.g. Comcast) and other smaller regional players, though.
Anyway, it sounds like we're all in agreement that we can drop this feature from the spec for the implementor's draft, and reintroduce it later with specific treatment if desired.

For reference it is RFC7628 in combination with Oauth best practices for native apps https://tools.ietf.org/html/draft-ietf-oauth-native-apps (AppAuth is the OIDF SDK name).
Email apps taking passwords is one of the largest security threats we have as it stops people from being able to do multifactor everyware.
Microsoft and apple have proprietary versions of RFC7628 that they support.   It would be good to move email apps on to the newer model where they would query for a hint  and use that to do OAuth to Google or other Mail provider to get a access token for IMAP/SMTP.
That is the pattern that I prefer to promote.

Code changes to finalize this made in #11.


Grad-Cam Example

Hello,
It seems, that the heatmap is shifted in some cases.
Is it because of keras.resize interpolation limitations in `jet_heatmap = jet_heatmap.resize((img.shape[1], img.shape[0])) or there another explanation for this?
The image below is an example from official documentation: https://keras.io/examples/vision/grad_cam/

@michael135 ,
The reported behaviour os some shift in heatmap still observed. I can see similar heat map as earlier in the attached gist.
Needs to be checked whether this is expected.

@michael135 -
The model used for this example is xception model, which is quite old backbone.  If you switch to a new model like ResNet or do fine-tuning the model might give localize better in gradcam results.  This notebook gives you an approach on how to reason about the predictions and confirm that model is learning the right things.
For example - If the dataset had images of person playing golf outside and is trained for golf activity, it might associate background field to Golf and not the actual activity.  GradCam can help understand what parts of the image resulted in the prediction to identify leakage, biases and shortcuts that network might be taking.
Its not going to localize perfectly since we never told the neural network what to attend to like a bounding box, segmentation etc.  Closing this issue as no action needs to be taken.  Please let us know if you have followup questions.


Fire Event After results have rendered in dropdown

I have posted this question on the forum but it seems this functionality does not exist  yet. I want to run some code right after the results have been populated in the ul. I have tested all the events and they all either run only when select is first opened (select2:opening), or after user has selected an item. But there doesn't seem to be an event for after render of the results. I feel like its a pretty common use case to want to have a callback for this specific event as the current events are when the items do not exist yet. templateResult is good to format the html but I need to initialize the actual element after they've been rendered with templateResult.

While this is a common use case, it is not one which we intend to support because nobody can quite agree on when to trigger an event like this (and why). So as a result I am going to direct this as a usage question, so it can be asked in forums where it is more likely to get a solution.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


Website - Typo

Hello,
On the website, on the page https://jsoup.org/cookbook/extracting-data/selector-syntax
:has(seletor): find elements that contain elements matching the selector; e.g. div:has(p)
Should be selector ;)
Regards,
Anael

Thanks! Fixed (pending publish shortly)


k3s on arm on rancher

We are not able to use arm64 k3s clusters with Rancher server: rancher/rancher/pull/18574

@cjellick are we also planning to support armv7 with Rancher?


media: Improve icon size

See https://github.com/cdr/code-server/pull/2383#issuecomment-738024951

On the left is the new icon, right is the old one.
Dock icon looks the same but is slightly larger.

Thanks for reporting @reaseno!

@nhooyr is the dock icon from Chrome A2HS?

@agneevX Yes!

Now the favicon isn't visible when having black browser tabs because the white background is gone 😞
I recommend additional colors.

Opened https://github.com/cdr/code-server/issues/2538

Opened https://github.com/cdr/code-server/issues/2538


chore: fix copyright banner

depend on https://github.com/istio/common-files/pull/717
Signed-off-by: Loong<EMAIL_ADDRESS>

I will run make update-common after https://github.com/istio/common-files/pull/717 merged.


Exclude stories from storyshots or change Jest environment

Storybook Stories that use the DOM (Modal for instance, need JSDOM mode.

either DOM or visuals
update test readme with directions

We also could switch node/JSDOM with Jest. https://jestjs.io/docs/en/configuration.html#testenvironment-string
The question how to do that with Storyshots.

All DOM snapshots run in jsDOM environment now.


Use editor config for cross ide/editor formatting

http://editorconfig.org/
Editor Config didn't use to support eclipse and it does now.
https://github.com/editorconfig/editorconfig/issues/108
@dsyer @marcingrzejszczak @adriancole @philwebb

Thanks to @mraible for the tip.

Looks interesting but a little limited compared to our checkstyle config.

That was intentional (I hate the Fascist Boot bot).

The checkstyle config enforces formatting during build. Editor Config configures your editor rather than having to import the eclipse rules into intellij (which has flaws).


Consider adding a column for field group

Issue in ./help/implement/aep-edge/variable-mapping.md
I'm just wondering if it might be helpful here to have another column that shows which field groups these items are in. If there is somewhere else where that is laid out, let me know, but I think somewhere we have to let people know which field groups they should add to their schema if they are going to push data back to Analytics when using the Web SDK.
Thanks,
Doug Moore

They should all be in the 'Adobe Analytics ExperienceEvent Template' field group. I've added that information to the top of the page.


[Bug]: Issue with search bar, user details can't be searched, error is console logged.

What happened?
I found a BUG 🐞 Regarding the search bar on the website, whenever I put any character in the search bar instead of showing result the page goes blank, and when I see the console there I noticed that a error is logged i.e.
Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase') at a (Homepage.jsx:64:10) at Homepage.jsx:73:16 at Array.filter (<anonymous>) at onSearch (Homepage.jsx:71:42) at Search.jsx:24:7 at al (react-dom.production.min.js:244:332) at Su (react-dom.production.min.js:286:111) at react-dom.production.min.js:282:391 at k (scheduler.production.min.js:13:203) at MessagePort.A (scheduler.production.min.js:14:128)
I have a screen recording of it, that I am attaching below.
Screencast from 05-10-24 09:08:40 PM IST.webm
I just want to let you know I got the bug found and fixed it in my forked repo, but I want you to assign this issue to me with gssoc-extd and hacktoberfest labels so that I can raise a PR.
Thank you for your value able time.
Below I attached the screen recording of the project after I fixed the issue in my local system.
2024-10-05_20-48-34 [MConverter.eu].webm
Add screenshots
This is the screenshot of the page when I type any character on the search bar.

What browsers are you seeing the problem on?
Brave
Code of Conduct

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

📢 Invitation to Join the DevDisplay WhatsApp Community!
We are excited to invite you to join the WhatsApp community of DevDisplay, where developers and contributors come together to collaborate and share their ideas.
Collaborative Support: If you are interested in working together with extensive support, we encourage you to join our community.
Open Source Contribution: If you would like to contribute to the DevDisplay open-source project, your participation is welcomed in our WhatsApp group.
By joining, you will have the opportunity to connect with like-minded individuals, discuss project developments, and contribute to our shared goals.
For more information and to join the community, please visit: Join DevDisplay WhatsApp Community.
We look forward to your participation!


Classic Hollandaise Sauce Recipe

https://www.thespruceeats.com/classic-hollandaise-sauce-4122491

Part of 5 Mother Sauces.

Duplicate of #39


added AnirudhPanda

resolve #596

Hey @schmelto can you review this PR, already getting too much merge conflicts

Sorry for the inconvenience @AnirudhPanda. Thanks for contributing :)


Error message on timeout

Whadduppp folks!
It looks we currently don't throw an error message when a deployment times out. This can be confusing if there isn't an error message explaining why: one could wonder if it's something with their internet connection, for example.
Unless we have a technical limitation to not do this, I would suggest we create and throw errors in the event of timeout in a way that is builder specific. e.g for Rust projects, we expect build times to be slow and therefore timeouts can be frequent.
So an error along the lines:

This build timed out cuz it look longer than 15m. Currently Rust projects take a while to ship because there’s ongoing work on the compiler. Please read [link] for more info.

would be useful!

Closing because Now CLI shows a message saying "Check the logs" at this point, which would lead to the 15 minute timeout in the logs.


chore(doc): fix error in classes/accessors section

Before this commit, when the playground to try class instance accessors
was launched the "errors" tab was saying the "_fulName" property was not
properly initialized. This commit fixes this issue.
fixes #1037

Thanks! Looks good to me, it's great to see little docs improvement PRs


Only rendering picture child elements when picture enters viewport

Fix for #36

I don't believe so, but I guess it depends on how the browser evaluates which src from the <picture> to show, given that the <source> is now injected at a different time. But I think that will work


bin: add drain to reboot script

What this PR does / why we need it: The reboot script now drains each node before rebooting them.
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] requires draining and/or replacing nodes.
[ ] will break the cluster.
I.e. full cluster migration is required.

I didn't test it. But it looks good to me!!

Shouldn't we cordon, drain, reboot, uncordon?
For inspiration, please find Kubespray's way of doing that:
* https://github.com/kubernetes-sigs/kubespray/blob/master/docs/upgrades.md#graceful-upgrade

* https://github.com/kubernetes-sigs/kubespray/blob/10c30ea5b1e1c08c7715aa00c0e2bbecba05a14d/roles/upgrade/pre-upgrade/tasks/main.yml#L50

kubectl drain both cordons and removes the pods. So I'm not sure why you would first want to cordon the node separately.
https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/#use-kubectl-drain-to-remove-a-node-from-service
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#drain

TIL 😁
On Mon, 1 Nov 2021, 13:55 Viktor, @.***> wrote:

Shouldn't we cordon, drain, reboot, uncordon?
For inspiration, please find Kubespray's way of doing that:

https://github.com/kubernetes-sigs/kubespray/blob/master/docs/upgrades.md#graceful-upgrade

https://github.com/kubernetes-sigs/kubespray/blob/10c30ea5b1e1c08c7715aa00c0e2bbecba05a14d/roles/upgrade/pre-upgrade/tasks/main.yml#L50

kubectl drain both cordons and removes the pods. So I'm not sure why you
would first want to cordon the node separately.
https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/#use-kubectl-drain-to-remove-a-node-from-service
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#drain
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elastisys/compliantkubernetes-kubespray/pull/132#issuecomment-956208519,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMVPIKAHBUFO2SHR2UPLO3UJ2E5PANCNFSM5HDVZ46A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.