make session-name configurable for assumed-role, update related docs …

Previously, IAM Role session name is defined with fmt.Sprintf("terragrunt-%d", time.Now().UTC().UnixNano()). This PR try to tackle issue defined in #1027 , where user can configure IAM Role session name used by terragrunt.
This is my first contribution to open source, please let me know  if I miss something, or anything need to be check for this PR.
Thanks

Hi @yorinasub17 , I've updated as you requested. Please let me know if anything needed. Thanks !

LGTM! Merging this in.


Question: Expressions in Decision tables

Hi. Is it possible to use expressions in decision tables?
For example, I want to use "contains" or "startsWith" for input matching instead of "equals"
I've not found examples of such cases
Thank you!

Hi, @stefan-gorules. This is exactly what I need. Thanks a lot!


Run query should format data as hex/base64

Currently the result of running a query looks like this:
{
  "data": {
    "0": 123,
    "1": 34,
    "2": 97,
    "3": 109,
    "4": 111,
    "5": 117,
    "6": 110,
    "7": 116,
    "8": 34,
    // ...
  }
}

In which network/contract do you see this problem?
It works for http://localhost:3000/contracts/cosmos1r856krgwz2r98jmtzgerxe4scg8m93akp2ur7q via
yarn start-heldernet

yarn start-stargate
http://localhost:3000/contracts/wasm1vs2vuks65rq7xj78mwtvn7vvnm2gn7ad78g6yp

I mean, ideally the stargate queries would be decoded further, but this issue is about a general way of displaying binary data.

@willclarktech all CosmWasm contracts are designed to use the CosmWasm Binary type for binary data. This is base64 encoded when going through JSON.
So there is a decoding step missing in Stargate that exists in Launchpad. Could you create a CosmJS ticket for that?

@webmaster128 https://github.com/cosmos/cosmjs/issues/590

Fixed via CosmJS upgrade:


How can I derive the active state for links?

I don’t see an option to set an active class on the Link component. What would be the workflow to get this working?
I thought I might use useMatchedRoute but it is not really the same as an active indicator.
In reach-router there is a function getProps you can return props you want to add the props of the rendered link. It gives you two variables isPartiallyCurrent and isCurrent this is really handy if you have in main menu and sub navigation.

Interesting idea. Maybe usePartiallyCurrent or useIsCurrent would be smart additions. I'm not really in favor of a getProps function as it introduces a new kind of complexity. You could easily wrap the Link component in a component of your own to set the class when usePartiallyCurrent or useIsCurrent is set.
At the moment the Link component is not aware of routes if I remember correctly. So I rather not add this complexity to the Link component
I'm not sure if we should add these methods to the library. It seems these hooks can be implemented quite easily (from the top of my head, so might contain errors):
function useIsCurrent(route) {
  const pick = usePick()
  return Boolean(pick(route))
}

function useIsPartiallyCurrent(route) {
  const pick = usePick()
  const routes = asRouteChain(route)
  const pickedRoute = pick(...routes)
  return Boolean(pickedRoute) && pickedRoute !== route
}


Reflection error when calling AddAspNetCore

System.Reflection.ReflectionTypeLoadException: 'Unable to load one or more of the requested types.
Could not load type 'Vortext.Common.Domain.Model.Entity' from assembly 'Vortext.Common.Domain, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.

I get 4 of these on the call to options.AddAspNetCore()
 private void IntegrateSimpleInjector(IServiceCollection services)
{
    _container.Options.DefaultScopedLifestyle = new AsyncScopedLifestyle();

    services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();

    services.AddSingleton<IControllerActivator>(new SimpleInjectorControllerActivator(_container));
    services.AddSingleton<IViewComponentActivator>(new SimpleInjectorViewComponentActivator(_container));

    services.AddSimpleInjector(_container, options =>
    {
        // AddAspNetCore() wraps web requests in a Simple Injector scope.
        options.AddAspNetCore()
            // Ensure activation of a specific framework type to be created by
            // Simple Injector instead of the built-in configuration system.
            .AddControllerActivation();
    });

    Bootstrapper.Bootstrap(_container, Configuration);

}

No other information about why or anything.  I tried moving the SimpleInjector registrations before this call but still no luck.  Clearly this is a problem with my library not yours but is there some way to better troubleshoot the actual problem?  The Entity object in question is actually an abstract class so I don't understand why it would be constructed anyway.
I've called container.Verify() before AddSimpleInjector() in order to troubleshoot things and the errors I get are things that I am already register in the services collection, e.g. IHttpContextAccessor (see line 5 in code above)

not calling options.AddAspNetCore() gives me this error
SqlConnection is registered using the 'Async Scoped' lifestyle, but the instance is requested outside the context of an active (Async Scoped) scope. Please see https://simpleinjector.org/scoped for more information about how apply lifestyles and manage scopes.

I think this is expected since options.AddAspNetCore() wraps requests in SI scope.

Are those first-chance exceptions? Does this happen in the debugger, does the program continue when you press F5 or does the program crash?

they are not first-chance exceptions.  The program spits out the DeveloperExceptionPage as a result of F5

This means that now is the timenyou post the exception details. Full stack trace of the exception and that of all inner eexceptions.

LOL! of course @dotnetjunkie it is.
System.TypeLoadException: Could not load type 'Vortext.Common.Domain.Model.Entity' from assembly 'Vortext.Common.Domain, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'
Seriously, that is it!

Can you post the srack trace in textual form?

OH!  sorry Stephen, here you go
   at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
   at System.Reflection.RuntimeAssembly.get_DefinedTypes()
   at Microsoft.AspNetCore.Mvc.ApplicationParts.AssemblyPart.get_Types()
   at Microsoft.AspNetCore.Mvc.Controllers.ControllerFeatureProvider.PopulateFeature(IEnumerable`1 parts, ControllerFeature feature)
   at Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager.PopulateFeature[TFeature](TFeature feature)
   at SimpleInjector.SimpleInjectorAspNetCoreBuilderMvcCoreExtensions.RegisterMvcControllers(Container container, ApplicationPartManager manager)
   at SimpleInjector.SimpleInjectorAspNetCoreBuilderMvcCoreExtensions.AddControllerActivation(SimpleInjectorAspNetCoreBuilder builder)
   at Vortext.RCM.Api.Startup.<>c.<IntegrateSimpleInjector>b__6_0(SimpleInjectorAddOptions options) in C:\dev\vortext-main-new\vortext-web\Vortext.RCM.Api\Startup.cs:line 68
   at SimpleInjector.SimpleInjectorServiceCollectionExtensions.AddSimpleInjector(IServiceCollection services, Container container, Action`1 setupAction)
   at Vortext.RCM.Api.Startup.IntegrateSimpleInjector(IServiceCollection services) in C:\dev\vortext-main-new\vortext-web\Vortext.RCM.Api\Startup.cs:line 65
   at Vortext.RCM.Api.Startup.ConfigureServices(IServiceCollection services) in C:\dev\vortext-main-new\vortext-web\Vortext.RCM.Api\Startup.cs:line 53
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.InvokeCore(Object instance, IServiceCollection services)
   at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.<>c__DisplayClass9_0.<Invoke>g__Startup|0(IServiceCollection serviceCollection)
   at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.Invoke(Object instance, IServiceCollection services)
   at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.<>c__DisplayClass8_0.<Build>b__0(IServiceCollection services)
   at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.UseStartup(Type startupType, HostBuilderContext context, IServiceCollection services)
   at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass12_0.<UseStartup>b__0(HostBuilderContext context, IServiceCollection services)
   at Microsoft.Extensions.Hosting.HostBuilder.CreateServiceProvider()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at Vortext.RCM.Api.Program.Main(String[] args) in C:\dev\vortext-main-new\vortext-web\Vortext.RCM.Api\Program.cs:line 23

Looking at the call stack, this isn't so much a Simple Injector exception, but the problem would likely exist if you use the built-in container as well. All the ASP.NET Core integration for Simple Injector does is call MVC's Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager using the Microsoft.AspNetCore.Mvc.Controllers.ControllerFeature the same way MVC does for loading controllers. The error is thrown by .NET while loading a specific type from your assembly.
You seem to have your Vortext.Common.Domain project added as application part, and for some reason (a reason I cannot see) loading that particular type from that assembly fails.
My advice is the following: try building a minimal, reproducible example by starting with an empty ASP.NET Core MVC project, using the built-in container, using standard configuration, and slowly start adding things until the error pops up. When this happens, backtrack until you understand what is causing that type to fail.
One possible cause that comes to mind is that Vortext.Common.Domain.Model.Entity can't be loaded because it depends on a type from another assembly that can't be loaded. Perhaps due to a missing binding redirect?

Thank you @dotnetjunkie I will have a go at that.  I know it is going to be something simple and silly.  I don't register that library in core so I don't know why it would try to load that but I'll try your suggestion.

well drat that turned out to be a reference to another of my libraries that referenced an older version of my common library where Entity existed.  Once removed all worked well.  I'm still not sure why that project was called during registration of aspnetcore but it's fixed now.  Sorry for the hassle @dotnetjunkie .


Recommended pattern for resetting to index 0 on pause?

In the case where the Play component is remove to pause the animation, I would like to reset the sprite index to 0 (an idle "looking" state). Manually update the Frame?
Also, thanks for the great library!

Update: looks like the pattern that works is to update the TextureAtlasSprite component of the entity, manually setting its index back to 0 when the Play component is removed.

Yes. I think benimator should expose the animation state component with a fn reset(&mut self) function.

Update: looks like the pattern that works is to update the TextureAtlasSprite component of the entity, manually setting its index back to 0 when the Play component is removed.

Mmh. Maybe. I'm kind of surprised that it works actually. I'll investiguate how it behaves (or should behave) in this scenario.


Update odh-manifests 8/27/21

Update odh-manifests submodule to https://github.com/red-hat-data-services/odh-manifests/commit/e6218ef867c248aef7443686fdf2f186555ce887

/retest


Improve detached legend

investigates and resolves #1765

I'm happy to see this feature is being used, but sorry if it creates additional workload for you !


(SF) Ensure bulk api output is in requested order

After 4 years of request, Salesforce now allows Foreign Key Relationships within their Bulk API. However, the csv response provided does not always return in the same order as requested. This PR ensures that the output csv is written in the same order as it was requested.
Description

For CSV content type, output is written in the same order as the fields of the input SOQL query.
Motivation and Context

Of my 8 daily Salesforce SOQL Queries, 4 of them do not return with the same column order as was requested in the SOQL. This PR ensures that.
Have you tested this? If so, how?

I have run this with my tasks and it works for me. I have specified this check only for CSV content type as it is the only one I use and cannot speak to the validity of return types for other approved SF content types.

Hey @dacort , could you review (as you're the only other Salesforce contributor)?

My only thought is regarding UTF-8 output. Since the original code just wrote the raw file, I wonder if there's anything different that needs to be done to ensure this change also consistently writes UTF-8 files.
@dlstadther Is this something you can confirm locally? Example using the current code:
› file data/salesforce_account.csv
data/salesforce_account.csv: UTF-8 Unicode text

Otherwise, looks good to me!

@dacort I'm not sure i understand your concern.
There wasn't previously any guarantee that the output would be utf-8. Are you saying that guarantee should be added here?

I'm saying that a non-UTF-8 file shouldn't be written in the event that it has UTF-8 characters in it. I'm not sure if the CSV module handles this intelligently or not.

From python2.7 csv doc, The csv module doesn’t directly support reading and writing Unicode. However, python3 doesn't mention any explicit issues with unicode, but does say it can handle any sequence type (which includes unicode).

Hm, ok. Will try to evaluate this week to verify that the change works as expected.

@colemanja91, mind taking a look since you're also a SF user? Thanks

@dlstadther just tried it with a few different queries - returns all columns in expected order. Code looks good to me!

I no longer use nor have access to Salesforce anymore. So I'll leave it up to @dacort whether i should resolve the conflicts and merge, or just close this PR.


kubeadm - Ha upgrade updates

Update kubeadm upgrade docs for HA upgrades.

Still finishing off final details
/hold

/assign @Bradamant3 @chuckha

/assign @timothysc @fabriziopandini
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews

@timothysc @Bradamant3 ok! instructions complete!

/hold cancel

/assign @rdodev

per review comments ^^ all's ready to go on all fronts
/lgtm
/approve


nova: 3.6.4 -> 3.7.0

Description of changes
Changelog: https://github.com/FairwindsOps/nova/releases/tag/v3.7.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

hashes are not updated.

My bad, this is fixed


remark validate links

This PR introduces remark-validate-links to verify links and images references exist in documents.
The attached example points out the links on the Access Control docs are incorrect. Along with another 20 issues
This would require #1059 be merged first as this includes the same commits.
For a clearer comparison see https://github.com/BarryThePenguin/keystone-5/compare/remark-toc...remark-validate-links
Example output...
docs/api/README.md: written
docs/api/access-control.md
       11:9-11:63  warning  Link to unknown file: `guides/access-control.md`                                                                     missing-file             remark-validate-links
       12:1-12:55  warning  Link to unknown file: `guides/authentication.md`                                                                     missing-file             remark-validate-links
    627:20-627:71  warning  Link to unknown heading: `admin-ui-display-forms`. Did you mean `admin-ui-display--forms`                            missing-heading          remark-validate-links

docs/api/hooks.md
         9:2-9:35  warning  Link to unknown file: `docs/hooks`                                                                                missing-file             remark-validate-links
         9:2-9:35  warning  Link to unknown heading in `docs/hooks`: `list-hooks`                                                                missing-heading-in-file  remark-validate-links
        9:37-9:72  warning  Link to unknown file: `docs/hooks`                                                                                missing-file             remark-validate-links
        9:37-9:72  warning  Link to unknown heading in `docs/hooks`: `field-hooks`                                                               missing-heading-in-file  remark-validate-links
       9:74-10:34  warning  Link to unknown file: `docs/hooks`                                                                                missing-file             remark-validate-links
       9:74-10:34  warning  Link to unknown heading in `docs/hooks`: `field-type-hooks`                                                          missing-heading-in-file  remark-validate-links
    157:33-158:42  warning  Link to unknown file: `docs/hooks.md`                                                                                missing-file             remark-validate-links
    157:33-158:42  warning  Link to unknown heading in `docs/hooks.md`: `hook-excecution-order`                                                  missing-heading-in-file  remark-validate-links

Related: #892 (may close that issue?)

Related: #892 (may close that issue?)

Yeah, this would solve that issue.
The only thing this wouldn't handle is references to anything outside this git repo

Hi @BarryThePenguin, this looks super useful! As part of this PR could I get you to also update the circle CI config to run this linter and fix the existing issues. If you have any trouble with any of them feel free to shout out and we can help work out where they should be point.

Good to know, thanks!
I've added linter to CI, you should be able to see all the reported issues. I'll have a look at what I can fix

The main confusion is around files that do or don't exist in api, discussions, or guides.
eg /api/access-control refers to /guides/access-control.md and /guides/authentication.md, neither which exist. But there is a /discussion/access-control.md and a /discussion/authentication.md.
There's only one /authentication.md, so I'm guessing every reference should point to that?

Yep, if there's only one version of a particular file name but it appears to be in the wrong place then it's probably the case that it was moved from one directory to another at one point but the links weren't updated, so feel free to work on that assumption.

These are the ones I'm unsure about

hooks.md exists in api/hooks.md and discussions/hooks.md
access-control.md exists in api/access-control.md and discussions/access-control.md
packages/arch/packages/alert/README.md links to files that don't exist
packages/arch/packages/example.md has links that no longer exist

docs/discussions/access-control.md
    116:18-116:75  warning  Link to unknown file: `guides/access-control.md`                                                                     missing-file             remark-validate-links

docs/discussions/lists.md
      35:48-35:86  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links

docs/discussions/mutation-lifecycle.md
      64:19-64:57  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links
     64:76-64:102  warning  Link to unknown file: `docs/hooks.md`                                                                                missing-file             remark-validate-links
   105:74-105:126  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links

docs/discussions/performance.md
       37:1-37:39  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links

packages/access-control/README.md
      9:106-9:160  warning  Link to unknown file: `guides/access-control.md`                                                                     missing-file             remark-validate-links

packages/arch/packages/alert/README.md
      39:32-39:55  warning  Link to unknown file: `packages/arch/packages/alert/theme`. Did you mean `packages/arch/packages/alert/README.md`    missing-file             remark-validate-links
     145:1-145:17  warning  Link to unknown file: `packages/arch/packages/alert/LICENSE`. Did you mean `packages/arch/packages/alert/README.md`  missing-file             remark-validate-links

packages/arch/packages/example.md
      76:20-76:73  warning  Link to unknown file: `packages/arch/packages/docs/lists-and-keys.html`                                              missing-file             remark-validate-links
      76:20-76:73  warning  Link to unknown heading in `packages/arch/packages/docs/lists-and-keys.html`: `keys`                                 missing-heading-in-file  remark-validate-links
  177:188-177:223  warning  Link to unknown heading: `getting-started`                                                                           missing-heading          remark-validate-links
  239:121-239:154  warning  Link to unknown heading: `getting-started`                                                                           missing-heading          remark-validate-links

docs/discussions/access-control.md
    116:18-116:75  warning  Link to unknown file: `guides/access-control.md`                                                                     missing-file             remark-validate-links

Should be api/access-control.md

docs/discussions/lists.md
      35:48-35:86  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links

Should be ./access-control.md.

docs/discussions/mutation-lifecycle.md
      64:19-64:57  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links
     64:76-64:102  warning  Link to unknown file: `docs/hooks.md`                                                                                missing-file             remark-validate-links
   105:74-105:126  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links

Should be ./access-control.md and hooks.md.

docs/discussions/performance.md
       37:1-37:39  warning  Link to unknown file: `docs/access-control.md`. Did you mean `docs/api/access-control.md`                            missing-file             remark-validate-links

Should be ./access-control.md.

packages/access-control/README.md
      9:106-9:160  warning  Link to unknown file: `guides/access-control.md`                                                                     missing-file             remark-validate-links

Should be ../../discussions/access-control.md

packages/arch/packages/alert/README.md
      39:32-39:55  warning  Link to unknown file: `packages/arch/packages/alert/theme`. Did you mean `packages/arch/packages/alert/README.md`    missing-file             remark-validate-links
     145:1-145:17  warning  Link to unknown file: `packages/arch/packages/alert/LICENSE`. Did you mean `packages/arch/packages/alert/README.md`  missing-file             remark-validate-links

We can just remove both these links I think and leave the raw text.

packages/arch/packages/example.md
      76:20-76:73  warning  Link to unknown file: `packages/arch/packages/docs/lists-and-keys.html`                                              missing-file             remark-validate-links
      76:20-76:73  warning  Link to unknown heading in `packages/arch/packages/docs/lists-and-keys.html`: `keys`                                 missing-heading-in-file  remark-validate-links
  177:188-177:223  warning  Link to unknown heading: `getting-started`                                                                           missing-heading          remark-validate-links
  239:121-239:154  warning  Link to unknown heading: `getting-started`                                                                           missing-heading          remark-validate-links

We can also simply remove these links as well.

Thanks @timleslie, that was helpful. The markdown link validation should be 🍏 now


Add Tidal provider

Adds a provider for the Tidal web player.
Everything works as it should, with some minor caveats. Play/Pause seems to be a bit buggy, but this seems to be an issue in general.
Seeking, setting track position, loop, shuffle etc. all works.
The only thing is that the player is not recognized before you play a video, which I believe is due to the fact that there is no audio element in the dom. However, just queuing a video seems to do the trick, after that it's fine.
I also added gmail to the block list, because hangouts was being picked up, so I had a useless media player for all my gmail tabs. (I can remove this if necessary)

Hey @LudvigHz, thanks for this. I was on vacations, let me give it a quick check and i'll be happy to merge it.

Merged! Thanks for this


[Trade API] If one of asset_type is missing, return 400 instead of 500

http://localhost:8000/trades?base_asset_type=native&counter_asset_code=CMA&counter_asset_issuer=GBWZHAVWY23QKKDJW7TXLSIHY5EX4NIB37O4NMRKN2SKNWOSE5TEPCY3&start_time=1525444269552&end_time=1526308269552&resolution=300000
Or
http://localhost:8000/trades?counter_asset_type=native&base_asset_code=CMA&base_asset_issuer=GBWZHAVWY23QKKDJW7TXLSIHY5EX4NIB37O4NMRKN2SKNWOSE5TEPCY3&start_time=1525444269552&end_time=1526308269552&resolution=300000
{
  "type": "https://stellar.org/horizon-errors/server_error",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "An error occurred while processing this request.  This is usually due to a bug within the server software.  Trying this request again may succeed if the bug is transient, otherwise please report this issue to the issue tracker at: https://github.com/stellar/go/services/horizon/internal/issues. Please include this response in your issue."
}

After code change:
{
  "type": "https://stellar.org/horizon-errors/bad_request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request you sent was invalid in some way",
  "extras": {
    "invalid_field": "asset_type",
    "reason": "this endpoint supports asset pairs but only one asset supplied"
  }
}

This will always return correctly:
http://localhost:8000/trades?base_asset_type=native&counter_asset_type=credit_alphanum4&counter_asset_code=CMA&counter_asset_issuer=GBWZHAVWY23QKKDJW7TXLSIHY5EX4NIB37O4NMRKN2SKNWOSE5TEPCY3&start_time=1525444269552&end_time=1526308269552&resolution=300000
Close #466

@tomerweller
If counter asset issuer is missing:
{
  "type": "https://stellar.org/horizon-errors/bad_request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request you sent was invalid in some way",
  "extras": {
    "invalid_field": "counter_asset_issuer",
    "reason": "encoded value is 0 bytes; minimum valid length is 3"
  }
}

If counter asset code is missing
{
  "type": "https://stellar.org/horizon-errors/not_found",
  "title": "Resource Missing",
  "status": 404,
  "detail": "The resource at the url requested was not found.  This is usually occurs for one of two reasons:  The url requested is not valid, or no data in our database could be found with the parameters provided."
}

If base asset issuer is missing
{
  "type": "https://stellar.org/horizon-errors/bad_request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request you sent was invalid in some way",
  "extras": {
    "invalid_field": "base_asset_issuer",
    "reason": "encoded value is 0 bytes; minimum valid length is 3"
  }
}

If base asset code is missing
{
  "type": "https://stellar.org/horizon-errors/not_found",
  "title": "Resource Missing",
  "status": 404,
  "detail": "The resource at the url requested was not found.  This is usually occurs for one of two reasons:  The url requested is not valid, or no data in our database could be found with the parameters provided."
}

This looks pretty consistent to me.
So I think what I'm going to do, is to use the 400 message with details of 'counter_' or 'base_' like this:
I will just need to play with the error message and set reason to
"invalid asset type: was not one of 'native', 'credit_alphanum4', 'credit_alphanum12'"

{
  "type": "https://stellar.org/horizon-errors/bad_request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request you sent was invalid in some way",
  "extras": {
    "invalid_field": "base_asset_type",
    "reason": "invalid asset type: was not one of 'native', 'credit_alphanum4', 'credit_alphanum12'"
  }
}

Let me know what you think.

regression test.

Handle every field check in
func (base *Base) MaybeGetAsset(prefix string) (xdr.Asset, bool) { }


Damage calculation incorrect

Some of this is combat luck but also some additional confusion.

Should be resolved in #1367


Bug Fix

Issue #56

Description

Related Issue

Other Information:

Not properly fixed, my bad

I'll let the pros deal with it :dum:


add pre-processor

add pre processor:

handle different pre-processing : min-max, std scaler, z-normalisation, ...
piping diagram for train/ test sets

Pre-processer creation should be done using factory pattern and returning the correct one based on arguments

Fixed with PRs #24 #25 #26


Adopt SemVer v2 for Package Versioning

Right now, the site seems to be using SemVer v1. While that's not a big issue, I'd say it's worth upgrading to SemVer v2. Not so recently, I tried uploading a valid SemVer package that looked something like “v1.0.0-rc.1” and had a rather vague error when it failed. When I tracked it down to the version tag, that's when I realized the site didn't fully support SemVer.
Upgrading would allow for more flexible versioning, such as:

1.0.0-alpha.2
3.3.0-alpha.1.22.45
9.8.0-alpha.4.5.6
2.5.4-alpha.<IP_ADDRESS>
1.2.3-pre.4+build.5

This only made me slightly more confused when I saw that the actual SemVer v2 specification has been around since Early 2014 — Late 2013. So, I'm not entirely sure what the actual issue or reason is, but I did feel the need to bring it up.

I think it needs to be supported in choco as well, it's not just a repository thing:
https://github.com/chocolatey/choco/issues/508

This should also be added to documentation. There's no mention how the package name must be to publish a prerelease version.

@savornicesei If there is something missing from the documentation, can you file a new issue over at the docs repository:
https://github.com/chocolatey/docs/issues

As there is nothing more to do here, I'm going to go ahead and close this. We can always reopen again later if needed.


expo 51 EAS build failing on iOS

Describe the bug
[RUN_FASTLANE] ▸ ** ARCHIVE FAILED **
[RUN_FASTLANE] ▸ The following build commands failed:
[RUN_FASTLANE] ▸ SwiftCompile normal arm64 Compiling\ noop-file.swift /var/folders/xr/37snnd7d1275sdjnphp8p28c0000gn/T/eas-build-local-nodejs/9729f3db-6d12-46d4-aa00-c1cfd59002fd/build/iOS/xxx/noop-file.swift (in target 'xxx' from project 'xxx')
[RUN_FASTLANE] ▸ SwiftCompile normal arm64 /var/folders/xr/37snnd7d1275sdjnphp8p28c0000gn/T/eas-build-local-nodejs/9729f3db-6d12-46d4-aa00-c1cfd59002fd/build/iOS/xxx/noop-file.swift (in target 'xxx' from project 'xxx')
[RUN_FASTLANE] ▸ SwiftCompile normal arm64 /Users/xxx/Library/Developer/Xcode/DerivedData/xxx-fynpvwcehmfobngujoedeivujnxz/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/xxx.build/Release-iphoneos/xxx.build/DerivedSources/GeneratedAssetSymbols.swift (in target 'xxx' from project 'xxx')
[RUN_FASTLANE] ▸ SwiftCompile normal arm64 /var/folders/xr/37snnd7d1275sdjnphp8p28c0000gn/T/eas-build-local-nodejs/9729f3db-6d12-46d4-aa00-c1cfd59002fd/build/ios/Pods/Target\ Support\ Files/Pods-xxx/ExpoModulesProvider.swift (in target 'xxx' from project 'xxx')
[RUN_FASTLANE] ▸ (4 failures)
[RUN_FASTLANE] ** ARCHIVE FAILED **
Ignite version
9.7.1
Additional info
System
platform           darwin
arch               arm64
cpu                8 cores          Apple M1 Pro
directory          ObservationApp   /Users/xxx/ObservationApp
JavaScript (and globally-installed packages)
node                22.4.1       /opt/homebrew/bin/node
npm                 10.8.1       /opt/homebrew/bin/npm
@expo/ngrok       4.1.0
create-expo-app   2.1.1
eas-cli           10.1.1
lodash            4.17.21
n                 9.2.0
npm               10.8.1
react-devtools    4.28.0
yarn                1.22.19      /opt/homebrew/bin/yarn
pnpm                -            not installed
bun                 -            not installed
expo                51.0.20      managed
Ignite
ignite-cli         9.7.1        /Users/xx/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src         build        /Users/xxx/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java               17.0.11      /usr/bin/java
android home       -            undefined
iOS
xcode              15.4
cocoapods          1.15.2       /opt/homebrew/bin/pod
Tools
git                git version 2.39.3 (Apple Git-146)   /usr/bin/git

Hi @Janendran sorry you're having troubles.
Can you provide some more information? What ignite options did you start the project with and what command are you using to make your build that is failing?
I can't reproduce this issue

✅ Do you want to use Expo? · Expo
✅ Which Expo workflow? (You can switch between them later with a little work -- here's how: https://ignitecookbook.com/docs/recipes/SwitchBetweenExpoGoCNG) · Expo Go
✅ Do you want to initialize a git repository? (Y/n) · Yes
✅ Remove demo code? We recommend leaving it in if it's your first time using Ignite (y/N) · Yes
✅ Which package manager do you want to use? · npm
✅ Do you want to install dependencies? (Y/n) · Yes
failing on eas build --profile production --platform ios

@Janendran can you paste a snippet with the failure from EAS?

@frankcalise
[RUN_FASTLANE] ** ARCHIVE FAILED **
[RUN_FASTLANE]
[RUN_FASTLANE]
[RUN_FASTLANE] The following build commands failed:
[RUN_FASTLANE] 	SwiftEmitModule normal arm64 Emitting\ module\ for\ Observation (in target 'Observation' from project 'Observation')
[RUN_FASTLANE] 	SwiftCompile normal arm64 /Users/username/Library/Developer/Xcode/DerivedData/Observation-efmwtjejxaecyegcnlwxmnvapxpi/Build/Intermediates.noindex/ArchiveIntermediates/Observation/IntermediateBuildFilesPath/Observation.build/Release-iphoneos/Observation.build/DerivedSources/GeneratedAssetSymbols.swift (in target 'Observation' from project 'Observation')
[RUN_FASTLANE] 	SwiftCompile normal arm64 Compiling\ ExpoModulesProvider.swift /var/folders/xr/37snnd7d1275sdjnphp8p28c0000gn/T/eas-build-local-nodejs/ce2f2db6-8bf1-4f36-9b7b-11d010152eae/build/ios/Pods/Target\ Support\ Files/Pods-Observation/ExpoModulesProvider.swift (in target 'Observation' from project 'Observation')
[RUN_FASTLANE] 	SwiftCompile normal arm64 /var/folders/xr/37snnd7d1275sdjnphp8p28c0000gn/T/eas-build-local-nodejs/ce2f2db6-8bf1-4f36-9b7b-11d010152eae/build/ios/Pods/Target\ Support\ Files/Pods-Observation/ExpoModulesProvider.swift (in target 'Observation' from project 'Observation')
[RUN_FASTLANE] (4 failures)
[RUN_FASTLANE] Exit status: 65

@Janendran is this a standard new ignite project or have you added dependencies?
Can you paste your package.json contents?
This doesn't seem like an Ignite issue at first glance, if it's specific to Expo you can post there or find help in their discord

@frankcalise thanks, this is a standard new ignite
{
"name": "observation",
"version": "0.0.1",
"private": true,
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"compile": "tsc --noEmit -p . --pretty",
"format": "prettier --write "app/**/*.{js,jsx,json,md,ts,tsx}"",
"lint": "eslint App.tsx app test --fix --ext .js,.ts,.tsx && npm run format",
"patch": "patch-package",
"test": "jest",
"test:watch": "jest --watch",
"test:maestro": "maestro test .maestro/FavoritePodcast.yaml",
"adb": "adb reverse tcp:9090 tcp:9090 && adb reverse tcp:3000 tcp:3000 && adb reverse tcp:9001 tcp:9001 && adb reverse tcp:8081 tcp:8081",
"postinstall": "patch-package",
"bundle:visualize": "npx react-native-bundle-visualizer",
"bundle:visualize:dev": "npx react-native-bundle-visualizer --dev",
"build:ios:sim": "eas build --profile development --platform ios --local",
"build:ios:dev": "eas build --profile development:device --platform ios --local",
"build:ios:prod": "eas build --profile production --platform ios --local",
"build:android:sim": "eas build --profile development --platform android --local",
"build:android:dev": "eas build --profile development:device --platform android --local",
"build:android:prod": "eas build --profile production --platform android --local",
"start": "npx expo start",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "npx expo start --web",
"bundle:web": "npx expo export --platform web",
"serve:web": "npx server dist",
"prebuild:clean": "npx expo prebuild --clean"
},
"dependencies": {
"@expo-google-fonts/space-grotesk": "^0.2.2",
"@expo/metro-runtime": "~3.2.1",
"@react-native-async-storage/async-storage": "1.23.1",
"@react-navigation/native": "^6.0.2",
"@react-navigation/native-stack": "^6.0.2",
"@shopify/flash-list": "1.6.4",
"apisauce": "3.0.1",
"date-fns": "^2.30.0",
"expo": "~51.0.8",
"expo-build-properties": "~0.12.1",
"expo-font": "~12.0.5",
"expo-linking": "~6.3.1",
"expo-localization": "~15.0.3",
"expo-splash-screen": "~0.27.4",
"expo-status-bar": "~1.12.1",
"i18n-js": "3.9.2",
"mobx": "6.10.2",
"mobx-react-lite": "4.0.5",
"mobx-state-tree": "5.3.0",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.74.3",
"react-native-gesture-handler": "~2.16.1",
"react-native-reanimated": "~3.10.1",
"react-native-safe-area-context": "4.10.5",
"react-native-screens": "3.31.1",
"react-native-web": "~0.19.6"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/plugin-proposal-export-namespace-from": "^7.18.9",
"@babel/plugin-proposal-nullish-coalescing-operator": "^7.0.0",
"@babel/plugin-proposal-optional-chaining": "^7.0.0",
"@babel/plugin-transform-arrow-functions": "^7.0.0",
"@babel/plugin-transform-shorthand-properties": "^7.0.0",
"@babel/plugin-transform-template-literals": "^7.0.0",
"@babel/preset-env": "^7.20.0",
"@babel/runtime": "^7.20.0",
"@types/i18n-js": "3.8.2",
"@types/jest": "^29.2.1",
"@types/react": "~18.2.14",
"@types/react-test-renderer": "^18.0.0",
"@typescript-eslint/eslint-plugin": "^5.59.0",
"@typescript-eslint/parser": "^5.59.0",
"babel-jest": "^29.2.1",
"eslint": "8.17.0",
"eslint-config-prettier": "8.5.0",
"eslint-config-standard": "17.0.0",
"eslint-plugin-import": "2.26.0",
"eslint-plugin-n": "^15.0.0",
"eslint-plugin-promise": "6.0.0",
"eslint-plugin-react": "7.30.0",
"eslint-plugin-react-native": "4.0.0",
"eslint-plugin-reactotron": "^0.1.2",
"jest": "^29.2.1",
"jest-expo": "~51.0.2",
"patch-package": "6.4.7",
"postinstall-prepare": "1.0.1",
"prettier": "2.8.8",
"react-test-renderer": "18.2.0",
"reactotron-core-client": "^2.8.13",
"reactotron-mst": "^3.1.7",
"reactotron-react-js": "^3.3.11",
"reactotron-react-native": "^5.0.5",
"ts-jest": "^29.1.1",
"ts-node": "^10.9.2",
"typescript": "~5.3.3"
},
"engines": {
"node": ">=18"
},
"prettier": {
"printWidth": 100,
"semi": false,
"singleQuote": false,
"trailingComma": "all"
},
"eslintConfig": {
"root": true,
"parser": "@typescript-eslint/parser",
"extends": [
"plugin:@typescript-eslint/recommended",
"plugin:react/recommended",
"plugin:react-native/all",
"standard",
"prettier"
],
"plugins": [
"@typescript-eslint",
"react",
"react-native",
"reactotron"
],
"parserOptions": {
"ecmaFeatures": {
"jsx": true
}
},
"settings": {
"react": {
"pragma": "React",
"version": "detect"
}
},
"globals": {
"DEV": false,
"jasmine": false,
"beforeAll": false,
"afterAll": false,
"beforeEach": false,
"afterEach": false,
"test": false,
"expect": false,
"describe": false,
"jest": false,
"it": false
},
"rules": {
"@typescript-eslint/ban-ts-ignore": 0,
"@typescript-eslint/ban-ts-comment": 0,
"@typescript-eslint/explicit-function-return-type": 0,
"@typescript-eslint/explicit-member-accessibility": 0,
"@typescript-eslint/explicit-module-boundary-types": 0,
"@typescript-eslint/indent": 0,
"@typescript-eslint/member-delimiter-style": 0,
"@typescript-eslint/no-empty-interface": 0,
"@typescript-eslint/no-explicit-any": 0,
"@typescript-eslint/no-object-literal-type-assertion": 0,
"@typescript-eslint/no-var-requires": 0,
"@typescript-eslint/no-unused-vars": [
"error",
{
"argsIgnorePattern": "^",
"varsIgnorePattern": "^"
}
],
"comma-dangle": 0,
"multiline-ternary": 0,
"no-undef": 0,
"no-unused-vars": 0,
"no-use-before-define": 0,
"no-global-assign": 0,
"quotes": 0,
"react-native/no-raw-text": 0,
"react/no-unescaped-entities": 0,
"react/prop-types": 0,
"space-before-function-paren": 0,
"reactotron/no-tron-in-production": "error"
}
}
}

@Janendran curious have you tried to build it on EAS cloud?
Some other local things to think about:

did you rename your project or is there some mismatch in your app.json? the build log says Observation but your package json says testApp so if app.json has a mismatch somewhere that could be an issue

open Xcode and log into your developer account? building prod will do code signing and might be getting hung up there


meter_billing() hook should return a list of record ids

Metering for multiple dimensions, in some cases, may result in multiple submissions to the associated CSP, so we should be returning a list of record ids, rather than just a single record id.

Sorry I double checked the aws docs for batch_meter_usage api and it's for saas offerings. This means we have to call meter_usage many times for multiple dimensions. Thus I think we will need this to be a dict return type. Something that maps each meter call dimension to the billing id:
{'dimension_1': '1234567890', 'dimension_2': '987654321'}
This ends up in cache alongside the dimension to quantity map for cross reference.
{'dimension_1': 15, 'dimension_2': 10}
This would provide all the details necessary.


Adds helper to Makefile

Adds helper target to list make targets to the Makefile.
Usage:
$ make list
egrep: warning: egrep is obsolescent; using grep -E
all
boilerplate-commit
boilerplate-freeze-check
boilerplate-update
build
build/_output/compliance-audit-router
clean
default
isclean
osd-container-image-build
osd-container-image-build-push
osd-container-image-build-push-one
osd-container-image-login
osd-container-image-push
prow-config
serve
test
vet

Signed-off-by: Chris Collins<EMAIL_ADDRESS>

/lgtm


Landing Page Re-Thinking

Problems (as opined by @davideast and @jeffbcross):

It's ugly, feels cold and unwelcoming, feels outdated
Too much information on one page. This page should primarily act as a feeder to other content.
Primary calls to action (view on Github and Download) don't reflect actual goals
Confusing navigation. E.g. Learn link takes users away from the controlled experience, "Develop" isn't clear that this is where Docs live.
Random content thrown onto page (videos take a lot of space, random codeschool link)
Tiny fonts with lots of text, makes users less likely to read (too much time commitment)
Examples are lacking context (Ie the basics requires interaction with annotations before anything is explained). There should probably be one in-context example that gives the gist of Angular, and links to other documentation.
Edit Me links cause SSL warning because they post to non-https.

Proposals:

Think more about the experience for these types of users: developers who are new to Angular (What's Angular about?), advanced angular developers looking for specific reference (How do I use this service?), occasional developer looking for tutorial or guide (What's the best way to define a complex directive), (secondary user: non-developers curious about angular)
Start with fresh content outline for the page, and write content more purposefully and succinctly
Relevant, targeted content and calls to action above the fold. (TBD what is most relevant)
Re-think navigation from user perspective
Create parts of IA to allow for content that's currently randomly placed throughout page

Lots of good feedback and suggestions here!

random codeschool link
This appears to have been removed.

Edit Me links cause SSL warning because they post to non-https.
These appear to go to https links on Plunker now.

It's odd that we use 88 KB (44 + 44) just to show a preview image of the videos and half of it is just to show a red YouTube icon over the top on hover.
I also find it odd that I have to click on 'DEVELOP' when I'm looking to start searching the docs. There should be a search box on the home page.
Clicking on LEARN->Videos takes you to a channel that is mostly unrelated to AngularJS (the first two rows are Angular). Redirecting to a curated playlist would probably be better.
Clicking LEARN->Case Studies takes you to https://www.madewithangular.com which may not be maintained anymore. The maintainer listed on the site goes to a 404 on GitHub. The associated Twitter account hasn't tweeted in about 3 years.
DEVELOP->Contribute, and even the next link for 'Contributing', doesn't mention that the project is in LTS and how likely contributors efforts are to be accepted.
DEVELOP->'Seed App project template' goes to a seed that is significantly out of date. It doesn't use components, doesn't use webpack or typescript (or even types), etc.
DISCUSS

Blog goes to an out of date blog that redirects you to blog.angular.io which doesn't have any recent AngularJS content.
Twitter goes to an Angular account that doesn't tweet about AngularJS

The "DESIGN DOCS & NOTES" button above the fold takes you to a empty Google Drive folder.

@Splaktar At this point, when AngularJS is in LTS mode and in a year or so support will stop completely, I don't think it makes sense to focus on any significant docs revamp.

Within those constraints, I agree.


please version murmur3

Hello,
Could you please tag this repository?
I am the Debian Maintainer for this project and tags would help Debian keep up with new releases/bugfixes.
See:

http://semver.org/
http://dave.cheney.net/2016/06/24/gophers-please-tag-your-releases

Hello,
You're right, it was great time for a tag, it's done now.
Thanks for your Debian work.
Sebastien

Time for new version update? 😅

Sure, v1.1 you now have ;)..
On Mon, Dec 4, 2017 at 10:09 AM, Jonathan ES Lin<EMAIL_ADDRESS>wrote:

Time for new version update? 😅
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/spaolacci/murmur3/issues/16#issuecomment-348901877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKpOEaMslNfUchPxLPGtmu3z3h_4Gwqks5s87bWgaJpZM4Os4yy
.


CSU-2364: set managedByCASTAI to false

iSpot.TV raised an issue that their Evictor was still being automatically upgraded even though they had self_managed set to true. This is due to the managedByCASTAI flag not being set to false

Closed in favor of: https://github.com/castai/terraform-castai-eks-cluster/pull/114


don't merge it!!!

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Patch coverage has no change and project coverage change: +0.11 :tada:

Comparison is base (c23f6a5) 46.47% compared to head (267f96f) 46.59%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #724      +/-   ##
==========================================
+ Coverage   46.47%   46.59%   +0.11%
==========================================
  Files         150      150
  Lines       16017    16017
==========================================
+ Hits         7444     7463      +19
+ Misses       8240     8224      -16
+ Partials      333      330       -3

Flag
Coverage Δ

go-1.19.x
46.49% <ø> (?)

go-1.20.x
46.53% <ø> (+0.05%)
:arrow_up:

macOS
46.53% <ø> (?)

unit
46.59% <ø> (+0.11%)
:arrow_up:

windows
46.49% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 5 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat: add wagmi send tx guide

Description
add wagmi send tx guide
Tests

[x] - Ran the changes locally with Docusaurus. and confirmed that the changes appear as expected.
[x] - Applied the corrections suggested by Cspell on the .mdx files with changes.

Preview/s
https://reown-docs-git-feat-add-wagmi-send-tx-guide-reown-com.vercel.app/appkit/recipes/wagmi-send-transaction

@rtomas, can you run a quick grammar check with ChatGPT?

@rtomas, can you run a quick grammar check with ChatGPT?

done ..


DxScheduler: moths view is awfully slow when loading lots of events

We have implemented DxScheduler in our application. Our clients can create more 1000 events per months. The ajax call takes about 400 milliseconds while the browser is taking about 5 to 10 seconds to render all the events during which the UI is blocked and the page appears unresponsive.
Here is live example to reproduce it https://plnkr.co/edit/a2ISU3lwyZxSKjB9DYBC?p=preview
We noticed that every item is inserted in the DOM, then it is removed after calculation its position and finally only two apointments with "show more" remain in the DOM.

Please help us! What are some reasonable ways of remedying the situation? Maybe
we can limit rendering items per day somehow?

Hello @yurzui
It looks like this issue is not related to the Angular 2 integration. I have created a corresponding ticket in our Support Center.


ModuleNotFoundError: No module named 'unsloth'

After successfully running the following
`%%capture
!pip install "unsloth[colab-new] @ git+https://github.com/unslothai/unsloth.git"
from torch import version; from packaging.version import Version as V
xformers = "xformers==0.0.27" if V(version) < V("2.4.0") else "xformers"
!pip install --no-deps {xformers} trl peft accelerate bitsandbytes triton`
I tried to import FastLanguaugeModel from unsloth
from unsloth import FastLanguageModel
But I am getting the following error.
ModuleNotFoundError: No module named 'unsloth'
Can I please get a suggestion?

@vidithirve Try removing %%capture - you might see an error message

@danielhanchen After removing %%capture, I got this
Defaulting to user installation because normal site-packages is not writeable Collecting unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git   Cloning https://github.com/unslothai/unsloth.git to /tmp/pip-install-le4e3sy4/unsloth_f5290c82c45e405d9ab342196dc99907   Running command git clone --filter=blob:none --quiet https://github.com/unslothai/unsloth.git /tmp/pip-install-le4e3sy4/unsloth_f5290c82c45e405d9ab342196dc99907   Resolved https://github.com/unslothai/unsloth.git to commit 6c534341bb229b136f9504443f0161645d2070c5   Installing build dependencies ...   Getting requirements to build wheel ...   Installing backend dependencies ...   Preparing metadata (pyproject.toml) ...   WARNING: Generating metadata for package unsloth produced metadata for project name unknown. Fix your #egg=unsloth fragments. Discarding git+https://github.com/unslothai/unsloth.git: Requested unknown from git+https://github.com/unslothai/unsloth.git has inconsistent name: filename has 'unsloth', but metadata has 'unknown' ERROR: Could not find a version that satisfies the requirement unsloth (unavailable) (from versions: 2024.8) ERROR: No matching distribution found for unsloth (unavailable) Defaulting to user installation because normal site-packages is not writeable Requirement already satisfied: xformers in /home/crholmes/.local/lib/python3.10/site-packages (0.0.28.post1) Requirement already satisfied: trl in /home/crholmes/.local/lib/python3.10/site-packages (0.10.1) Requirement already satisfied: peft in /home/crholmes/.local/lib/python3.10/site-packages (0.12.0) Requirement already satisfied: accelerate in /home/crholmes/.local/lib/python3.10/site-packages (0.34.2) Requirement already satisfied: bitsandbytes in /home/crholmes/.local/lib/python3.10/site-packages (0.43.3) Requirement already satisfied: triton in /home/crholmes/.local/lib/python3.10/site-packages (3.0.0)
but after this, I tried running the next cell and it gave me the same error
ModuleNotFoundError: No module named 'unsloth'

Try pip install --upgrade pip then also pip uninstall unsloth -y and finally pip install --upgrade --no-cache-dir "unsloth[colab-new] @ git+https://github.com/unslothai/unsloth.git"

Thank you @danielhanchen it worked out after doing as you mentioned.

Great!

@danielhanchen : tried with your approach , still not working , error showing

error showing as "No module named 'unsloth'

@KRoy1979 Can you try import unsloth - does that not work?

having the same problem. Just tried to use import unsloth
Executed
`!pip install unsloth
Also get the latest nightly Unsloth!
!pip uninstall unsloth -y && pip install --upgrade --no-cache-dir "unsloth[colab-new] @ git+https://github.com/unslothai/unsloth.git"`
No error message as shown below
`
!pip install unsloth
Also get the latest nightly Unsloth!
!pip uninstall unsloth -y && pip install --upgrade --no-cache-dir "unsloth[colab-new] @ git+https://github.com/unslothai/unsloth.git"
Collecting unsloth
Using cached unsloth-2024.10.1-py3-none-any.whl (161 kB)
Collecting packaging
Using cached packaging-24.1-py3-none-any.whl (53 kB)
Collecting datasets>=2.16.0
Using cached datasets-3.0.1-py3-none-any.whl (471 kB)
Collecting peft!=0.11.0,>=0.7.1
Using cached peft-0.13.2-py3-none-any.whl (320 kB)
Collecting numpy
Using cached numpy-2.1.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (16.3 MB)
Collecting wheel>=0.42.0
Using cached wheel-0.44.0-py3-none-any.whl (67 kB)
Collecting tqdm
Using cached tqdm-4.66.5-py3-none-any.whl (78 kB)
Collecting torch>=2.4.0
Using cached torch-2.4.1-cp310-cp310-manylinux1_x86_64.whl (797.1 MB)
Collecting triton>=3.0.0
Using cached triton-3.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (209.5 MB)
Collecting psutil
Using cached psutil-6.0.0-cp36-abi3-manylinux_2_12_x86_64.manylinux2010_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (290 kB)
Collecting bitsandbytes
Using cached bitsandbytes-0.44.1-py3-none-manylinux_2_24_x86_64.whl (122.4 MB)
Collecting protobuf<4.0.0
Using cached protobuf-3.20.3-cp310-cp310-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (1.1 MB)
Collecting tyro
Using cached tyro-0.8.12-py3-none-any.whl (108 kB)
Collecting trl!=0.9.0,!=0.9.1,!=0.9.2,!=0.9.3,<=0.11.1,>=0.7.9
Using cached trl-0.11.1-py3-none-any.whl (318 kB)
Collecting sentencepiece>=0.2.0
Using cached sentencepiece-0.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.3 MB)
Collecting xformers>=0.0.27.post2
Using cached xformers-0.0.28.post1-cp310-cp310-manylinux_2_28_x86_64.whl (16.7 MB)
Collecting unsloth-zoo
Using cached unsloth_zoo-2024.10.1-py3-none-any.whl (39 kB)
Collecting huggingface-hub
Using cached huggingface_hub-0.25.2-py3-none-any.whl (436 kB)
Collecting hf-transfer
Using cached hf_transfer-0.1.8-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.6 MB)
Collecting transformers<4.45.0
Using cached transformers-4.44.2-py3-none-any.whl (9.5 MB)
Collecting accelerate>=0.34.1
Using cached accelerate-1.0.1-py3-none-any.whl (330 kB)
Collecting pyyaml
Using cached PyYAML-6.0.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (751 kB)
Collecting safetensors>=0.4.3
Using cached safetensors-0.4.5-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (435 kB)
Collecting fsspec[http]<=2024.6.1,>=2023.1.0
Using cached fsspec-2024.6.1-py3-none-any.whl (177 kB)
Collecting aiohttp
Using cached aiohttp-3.10.10-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.2 MB)
Collecting pyarrow>=15.0.0
Using cached pyarrow-17.0.0-cp310-cp310-manylinux_2_28_x86_64.whl (39.9 MB)
Collecting dill<0.3.9,>=0.3.0
Using cached dill-0.3.8-py3-none-any.whl (116 kB)
Collecting filelock
Using cached filelock-3.16.1-py3-none-any.whl (16 kB)
Collecting xxhash
Using cached xxhash-3.5.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (194 kB)
Collecting requests>=2.32.2
Using cached requests-2.32.3-py3-none-any.whl (64 kB)
Collecting multiprocess
Using cached multiprocess-0.70.17-py310-none-any.whl (134 kB)
Collecting pandas
Using cached pandas-2.2.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.1 MB)
Collecting typing-extensions>=<IP_ADDRESS>
Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Collecting fsspec>=2023.5.0
Using cached fsspec-2024.9.0-py3-none-any.whl (179 kB)
Collecting sympy
Using cached sympy-1.13.3-py3-none-any.whl (6.2 MB)
Collecting nvidia-cuda-cupti-cu12==12.1.105
Using cached nvidia_cuda_cupti_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (14.1 MB)
Collecting nvidia-cuda-nvrtc-cu12==12.1.105
Using cached nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (23.7 MB)
Collecting nvidia-cublas-cu12==<IP_ADDRESS>
Using cached nvidia_cublas_cu12-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (410.6 MB)
Collecting networkx
Using cached networkx-3.4.1-py3-none-any.whl (1.7 MB)
Collecting nvidia-cufft-cu12==<IP_ADDRESS>
Using cached nvidia_cufft_cu12-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (121.6 MB)
Collecting nvidia-curand-cu12==<IP_ADDRESS>
Using cached nvidia_curand_cu12-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (56.5 MB)
Collecting nvidia-cusolver-cu12==<IP_ADDRESS>
Using cached nvidia_cusolver_cu12-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (124.2 MB)
Collecting nvidia-cusparse-cu12==<IP_ADDRESS>
Using cached nvidia_cusparse_cu12-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (196.0 MB)
Collecting nvidia-nccl-cu12==2.20.5
Using cached nvidia_nccl_cu12-2.20.5-py3-none-manylinux2014_x86_64.whl (176.2 MB)
Collecting nvidia-nvtx-cu12==12.1.105
Using cached nvidia_nvtx_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (99 kB)
Collecting nvidia-cuda-runtime-cu12==12.1.105
Using cached nvidia_cuda_runtime_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (823 kB)
Collecting triton>=3.0.0
Using cached triton-3.0.0-1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl (209.4 MB)
Collecting nvidia-cudnn-cu12==<IP_ADDRESS>
Using cached nvidia_cudnn_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl (664.8 MB)
Collecting jinja2
Using cached jinja2-3.1.4-py3-none-any.whl (133 kB)
Collecting nvidia-nvjitlink-cu12
Using cached nvidia_nvjitlink_cu12-12.6.77-py3-none-manylinux2014_x86_64.whl (19.7 MB)
Collecting regex!=2019.12.17
Using cached regex-2024.9.11-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (782 kB)
Collecting tokenizers<0.20,>=0.19
Using cached tokenizers-0.19.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.6 MB)
Collecting rich>=11.1.0
Using cached rich-13.9.2-py3-none-any.whl (242 kB)
Collecting docstring-parser>=0.16
Using cached docstring_parser-0.16-py3-none-any.whl (36 kB)
Collecting shtab>=1.5.6
Using cached shtab-1.7.1-py3-none-any.whl (14 kB)
Collecting frozenlist>=1.1.1
Using cached frozenlist-1.4.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (239 kB)
Collecting attrs>=17.3.0
Using cached attrs-24.2.0-py3-none-any.whl (63 kB)
Collecting aiohappyeyeballs>=2.3.0
Using cached aiohappyeyeballs-2.4.3-py3-none-any.whl (14 kB)
Collecting multidict<7.0,>=4.5
Using cached multidict-6.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (124 kB)
Collecting yarl<2.0,>=1.12.0
Using cached yarl-1.15.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (313 kB)
Collecting async-timeout<5.0,>=4.0
Using cached async_timeout-4.0.3-py3-none-any.whl (5.7 kB)
Collecting aiosignal>=1.1.2
Using cached aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Collecting charset-normalizer<4,>=2
Using cached charset_normalizer-3.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (144 kB)
Collecting certifi>=2017.4.17
Using cached certifi-2024.8.30-py3-none-any.whl (167 kB)
Collecting urllib3<3,>=1.21.1
Using cached urllib3-2.2.3-py3-none-any.whl (126 kB)
Collecting idna<4,>=2.5
Using cached idna-3.10-py3-none-any.whl (70 kB)
Collecting pygments<3.0.0,>=2.13.0
Using cached pygments-2.18.0-py3-none-any.whl (1.2 MB)
Collecting markdown-it-py>=2.2.0
Using cached markdown_it_py-3.0.0-py3-none-any.whl (87 kB)
Collecting MarkupSafe>=2.0
Using cached MarkupSafe-3.0.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (20 kB)
Collecting multiprocess
Using cached multiprocess-0.70.16-py310-none-any.whl (134 kB)
Collecting python-dateutil>=2.8.2
Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
Collecting tzdata>=2022.7
Using cached tzdata-2024.2-py2.py3-none-any.whl (346 kB)
Collecting pytz>=2020.1
Using cached pytz-2024.2-py2.py3-none-any.whl (508 kB)
Collecting mpmath<1.4,>=1.1.0
Using cached mpmath-1.3.0-py3-none-any.whl (536 kB)
Collecting mdurl~=0.1
Using cached mdurl-0.1.2-py3-none-any.whl (10.0 kB)
Collecting six>=1.5
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting propcache>=0.2.0
Using cached propcache-0.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (208 kB)
Installing collected packages: sentencepiece, pytz, mpmath, xxhash, wheel, urllib3, tzdata, typing-extensions, tqdm, sympy, six, shtab, safetensors, regex, pyyaml, pygments, psutil, protobuf, propcache, packaging, nvidia-nvtx-cu12, nvidia-nvjitlink-cu12, nvidia-nccl-cu12, nvidia-curand-cu12, nvidia-cufft-cu12, nvidia-cuda-runtime-cu12, nvidia-cuda-nvrtc-cu12, nvidia-cuda-cupti-cu12, nvidia-cublas-cu12, numpy, networkx, mdurl, MarkupSafe, idna, hf-transfer, fsspec, frozenlist, filelock, docstring-parser, dill, charset-normalizer, certifi, attrs, async-timeout, aiohappyeyeballs, triton, requests, python-dateutil, pyarrow, nvidia-cusparse-cu12, nvidia-cudnn-cu12, multiprocess, multidict, markdown-it-py, jinja2, aiosignal, yarl, rich, pandas, nvidia-cusolver-cu12, huggingface-hub, tyro, torch, tokenizers, aiohttp, xformers, transformers, bitsandbytes, accelerate, peft, datasets, trl, unsloth-zoo, unsloth
Successfully installed MarkupSafe-3.0.1 accelerate-1.0.1 aiohappyeyeballs-2.4.3 aiohttp-3.10.10 aiosignal-1.3.1 async-timeout-4.0.3 attrs-24.2.0 bitsandbytes-0.44.1 certifi-2024.8.30 charset-normalizer-3.4.0 datasets-3.0.1 dill-0.3.8 docstring-parser-0.16 filelock-3.16.1 frozenlist-1.4.1 fsspec-2024.6.1 hf-transfer-0.1.8 huggingface-hub-0.25.2 idna-3.10 jinja2-3.1.4 markdown-it-py-3.0.0 mdurl-0.1.2 mpmath-1.3.0 multidict-6.1.0 multiprocess-0.70.16 networkx-3.4.1 numpy-2.1.2 nvidia-cublas-cu12-<IP_ADDRESS> nvidia-cuda-cupti-cu12-12.1.105 nvidia-cuda-nvrtc-cu12-12.1.105 nvidia-cuda-runtime-cu12-12.1.105 nvidia-cudnn-cu12-<IP_ADDRESS> nvidia-cufft-cu12-<IP_ADDRESS> nvidia-curand-cu12-<IP_ADDRESS> nvidia-cusolver-cu12-<IP_ADDRESS> nvidia-cusparse-cu12-<IP_ADDRESS> nvidia-nccl-cu12-2.20.5 nvidia-nvjitlink-cu12-12.6.77 nvidia-nvtx-cu12-12.1.105 packaging-24.1 pandas-2.2.3 peft-0.13.2 propcache-0.2.0 protobuf-3.20.3 psutil-6.0.0 pyarrow-17.0.0 pygments-2.18.0 python-dateutil-2.9.0.post0 pytz-2024.2 pyyaml-6.0.2 regex-2024.9.11 requests-2.32.3 rich-13.9.2 safetensors-0.4.5 sentencepiece-0.2.0 shtab-1.7.1 six-1.16.0 sympy-1.13.3 tokenizers-0.19.1 torch-2.4.1 tqdm-4.66.5 transformers-4.44.2 triton-3.0.0 trl-0.11.1 typing-extensions-4.12.2 tyro-0.8.12 tzdata-2024.2 unsloth-2024.10.1 unsloth-zoo-2024.10.1 urllib3-2.2.3 wheel-0.44.0 xformers-0.0.28.post1 xxhash-3.5.0 yarl-1.15.4
Found existing installation: unsloth 2024.10.1
Uninstalling unsloth-2024.10.1:
Successfully uninstalled unsloth-2024.10.1
Collecting unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git
Cloning https://github.com/unslothai/unsloth.git to /tmp/pip-install-igudkuid/unsloth_e9e977b826f246b2a2ab81169f1d761a
Running command git clone --filter=blob:none --quiet https://github.com/unslothai/unsloth.git /tmp/pip-install-igudkuid/unsloth_e9e977b826f246b2a2ab81169f1d761a
Resolved https://github.com/unslothai/unsloth.git to commit 38663b01f5dd0e610b12475bd95b144303cff539
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: tqdm in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (4.66.5)
Requirement already satisfied: numpy in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.1.2)
Requirement already satisfied: wheel>=0.42.0 in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.44.0)
Requirement already satisfied: tyro in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.8.12)
Requirement already satisfied: transformers>=4.44.2 in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (4.44.2)
Requirement already satisfied: packaging in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (24.1)
Requirement already satisfied: datasets>=2.16.0 in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.0.1)
Requirement already satisfied: huggingface-hub in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.25.2)
Requirement already satisfied: sentencepiece>=0.2.0 in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.2.0)
Requirement already satisfied: hf-transfer in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.1.8)
Requirement already satisfied: protobuf<4.0.0 in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.20.3)
Requirement already satisfied: unsloth-zoo in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2024.10.1)
Requirement already satisfied: psutil in ./env/lib/python3.10/site-packages (from unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (6.0.0)
Requirement already satisfied: requests>=2.32.2 in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.32.3)
Requirement already satisfied: fsspec[http]<=2024.6.1,>=2023.1.0 in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2024.6.1)
Requirement already satisfied: xxhash in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.5.0)
Requirement already satisfied: dill<0.3.9,>=0.3.0 in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.3.8)
Requirement already satisfied: multiprocess in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.70.16)
Requirement already satisfied: filelock in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.16.1)
Requirement already satisfied: pyarrow>=15.0.0 in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (17.0.0)
Requirement already satisfied: pyyaml>=5.1 in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (6.0.2)
Requirement already satisfied: pandas in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.2.3)
Requirement already satisfied: aiohttp in ./env/lib/python3.10/site-packages (from datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.10.10)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from huggingface-hub->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (4.12.2)
Requirement already satisfied: tokenizers<0.20,>=0.19 in ./env/lib/python3.10/site-packages (from transformers>=4.44.2->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.19.1)
Requirement already satisfied: safetensors>=0.4.1 in ./env/lib/python3.10/site-packages (from transformers>=4.44.2->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.4.5)
Requirement already satisfied: regex!=2019.12.17 in ./env/lib/python3.10/site-packages (from transformers>=4.44.2->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2024.9.11)
Requirement already satisfied: shtab>=1.5.6 in ./env/lib/python3.10/site-packages (from tyro->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.7.1)
Requirement already satisfied: docstring-parser>=0.16 in ./env/lib/python3.10/site-packages (from tyro->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.16)
Requirement already satisfied: rich>=11.1.0 in ./env/lib/python3.10/site-packages (from tyro->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (13.9.2)
Requirement already satisfied: trl!=0.9.0,!=0.9.1,!=0.9.2,!=0.9.3,<=0.11.1,>=0.7.9 in ./env/lib/python3.10/site-packages (from unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.11.1)
Requirement already satisfied: peft!=0.11.0,>=0.7.1 in ./env/lib/python3.10/site-packages (from unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.13.2)
Requirement already satisfied: accelerate>=0.34.1 in ./env/lib/python3.10/site-packages (from unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.0.1)
Requirement already satisfied: triton>=3.0.0 in ./env/lib/python3.10/site-packages (from unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.0.0)
Requirement already satisfied: torch>=2.4.0 in ./env/lib/python3.10/site-packages (from unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.4.1)
Requirement already satisfied: multidict<7.0,>=4.5 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (6.1.0)
Requirement already satisfied: aiosignal>=1.1.2 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.3.1)
Requirement already satisfied: yarl<2.0,>=1.12.0 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.15.4)
Requirement already satisfied: attrs>=17.3.0 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (24.2.0)
Requirement already satisfied: async-timeout<5.0,>=4.0 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (4.0.3)
Requirement already satisfied: aiohappyeyeballs>=2.3.0 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.4.3)
Requirement already satisfied: frozenlist>=1.1.1 in ./env/lib/python3.10/site-packages (from aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.4.1)
Requirement already satisfied: certifi>=2017.4.17 in ./env/lib/python3.10/site-packages (from requests>=2.32.2->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2024.8.30)
Requirement already satisfied: idna<4,>=2.5 in ./env/lib/python3.10/site-packages (from requests>=2.32.2->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.10)
Requirement already satisfied: charset-normalizer<4,>=2 in ./env/lib/python3.10/site-packages (from requests>=2.32.2->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.4.0)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./env/lib/python3.10/site-packages (from requests>=2.32.2->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.2.3)
Requirement already satisfied: pygments<3.0.0,>=2.13.0 in ./env/lib/python3.10/site-packages (from rich>=11.1.0->tyro->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.18.0)
Requirement already satisfied: markdown-it-py>=2.2.0 in ./env/lib/python3.10/site-packages (from rich>=11.1.0->tyro->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.0.0)
Requirement already satisfied: networkx in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.4.1)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (12.1.105)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (12.1.105)
Requirement already satisfied: sympy in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.13.3)
Requirement already satisfied: nvidia-nccl-cu12==2.20.5 in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.20.5)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (12.1.105)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (12.1.105)
Requirement already satisfied: jinja2 in ./env/lib/python3.10/site-packages (from torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.1.4)
Requirement already satisfied: nvidia-nvjitlink-cu12 in ./env/lib/python3.10/site-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (12.6.77)
Requirement already satisfied: python-dateutil>=2.8.2 in ./env/lib/python3.10/site-packages (from pandas->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2.9.0.post0)
Requirement already satisfied: tzdata>=2022.7 in ./env/lib/python3.10/site-packages (from pandas->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2024.2)
Requirement already satisfied: pytz>=2020.1 in ./env/lib/python3.10/site-packages (from pandas->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (2024.2)
Requirement already satisfied: mdurl~=0.1 in ./env/lib/python3.10/site-packages (from markdown-it-py>=2.2.0->rich>=11.1.0->tyro->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.1.2)
Requirement already satisfied: six>=1.5 in ./env/lib/python3.10/site-packages (from python-dateutil>=2.8.2->pandas->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.16.0)
Requirement already satisfied: propcache>=0.2.0 in ./env/lib/python3.10/site-packages (from yarl<2.0,>=1.12.0->aiohttp->datasets>=2.16.0->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (0.2.0)
Requirement already satisfied: MarkupSafe>=2.0 in ./env/lib/python3.10/site-packages (from jinja2->torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (3.0.1)
Requirement already satisfied: mpmath<1.4,>=1.1.0 in ./env/lib/python3.10/site-packages (from sympy->torch>=2.4.0->unsloth-zoo->unsloth[colab-new]@ git+https://github.com/unslothai/unsloth.git) (1.3.0)
Building wheels for collected packages: unsloth
Building wheel for unsloth (pyproject.toml) ... done
Created wheel for unsloth: filename=unsloth-2024.10.0-py3-none-any.whl size=161146 sha256=229c3318f7237e0873376595d001e0dea3b822ebc3a3b03eeaf412ef81340a6f
Stored in directory: /tmp/pip-ephem-wheel-cache-mkycimw1/wheels/ed/d4/e9/76fb290ee3df0a5fc21ce5c2c788e29e9607a2353d8342fd0d
Successfully built unsloth
Installing collected packages: unsloth
Successfully installed unsloth-2024.10.0`
`Package                  Version

accelerate               1.0.1
aiohappyeyeballs         2.4.3
aiohttp                  3.10.10
aiosignal                1.3.1
async-timeout            4.0.3
attrs                    24.2.0
bitsandbytes             0.44.1
certifi                  2024.8.30
charset-normalizer       3.4.0
datasets                 3.0.1
dill                     0.3.8
docstring_parser         0.16
filelock                 3.16.1
frozenlist               1.4.1
fsspec                   2024.6.1
hf_transfer              0.1.8
huggingface-hub          0.25.2
idna                     3.10
Jinja2                   3.1.4
markdown-it-py           3.0.0
MarkupSafe               3.0.1
mdurl                    0.1.2
mpmath                   1.3.0
multidict                6.1.0
multiprocess             0.70.16
networkx                 3.4.1
numpy                    2.1.2
nvidia-cublas-cu12       <IP_ADDRESS>
nvidia-cuda-cupti-cu12   12.1.105
nvidia-cuda-nvrtc-cu12   12.1.105
nvidia-cuda-runtime-cu12 12.1.105
nvidia-cudnn-cu12        <IP_ADDRESS>
nvidia-cufft-cu12        <IP_ADDRESS>
nvidia-curand-cu12       <IP_ADDRESS>
nvidia-cusolver-cu12     <IP_ADDRESS>
nvidia-cusparse-cu12     <IP_ADDRESS>
nvidia-nccl-cu12         2.20.5
nvidia-nvjitlink-cu12    12.6.77
nvidia-nvtx-cu12         12.1.105
packaging                24.1
pandas                   2.2.3
peft                     0.13.2
pip                      22.0.2
propcache                0.2.0
protobuf                 3.20.3
psutil                   6.0.0
pyarrow                  17.0.0
Pygments                 2.18.0
python-dateutil          2.9.0.post0
pytz                     2024.2
PyYAML                   6.0.2
regex                    2024.9.11
requests                 2.32.3
rich                     13.9.2
safetensors              0.4.5
sentencepiece            0.2.0
setuptools               59.6.0
shtab                    1.7.1
six                      1.16.0
sympy                    1.13.3
tokenizers               0.19.1
torch                    2.4.1
tqdm                     4.66.5
transformers             4.44.2
triton                   3.0.0
trl                      0.11.1
typing_extensions        4.12.2
tyro                     0.8.12
tzdata                   2024.2
unsloth                  2024.10.0
unsloth_zoo              2024.10.1
urllib3                  2.2.3
wheel                    0.44.0
xformers                 0.0.28.post1
xxhash                   3.5.0
yarl                     1.15.4
`

@rodrigofvale Wait in the logs it says Unsloth got installed correctly. Are you using the same env?

@SnehaKumari14 Apologies on the delay as well - oh yep I think I commented reinstalling - does that not function even today? Would asking on our Discord server be more helpful - you can get a faster response time


The Leading blog page looks cluttered.

The leading blog page looks cluttered and unorganised
Steps to reproduce the behavior:

Go to 'https://anshika-26.github.io/WordWise/'
Click on 'Leading blogs'
Scroll down to 'Previous post and new post section'
Thing are looking messed up here. The comments heading is merged into the previous and next post section. The next and previous section content is also not nicely separated

Expected behavior
The comments heading should look clean, bold and different. The next and previous post section should show photo on top and then text in bottom having read more option.
Screenshots

Please assign this to me and add tag for hackoctoberfest-accepted.

I feel like the issue is unique. Can you please reopen this?

@divyansharma001 any progress ?

working in it

@divyansharma001 ?

closing issue due to lack of response


[BUG] sqlalchemy relationship fields are absent in router response

There is still an issue with sqlalchemy Data Models similar to the https://github.com/tiangolo/fastapi/issues/4
If one has such models relationship as:
Base = declarative_base()

class Parent(Base):
    children = relationship("Child", back_populates="parent")

class Child(Base):
    parent_id = Column(
        Integer,
        ForeignKey('parent.id', onupdate='CASCADE', ondelete='CASCADE'),
        index=True
    )
    parent = relationship("Parent", back_populates="children")

then the JSON response body of the API call does return only parent_id correct value and parent field has undefined value.
However when one uses a helper method like:
def json(self):
       return {
           'parent_id': self.parent_id,
           'parent': self.parent
       }

then response bode has all proper values.
UPDATE:
the same issue occurs with all SqlAlchemy hybrid_property fields.

This is due to SQLAlchemy lazy-loading behavior.
By the time a model is converted to a dict, the data has not been populated (fetched from the DB) yet.
If you do anything that calls child.parent, even a single expression with that, SQLAlchemy will go and fetch the data for you. Having it available for serialization.

The current implementation takes whatever is returned by your path operation function, does it's best effort to convert it to something serializable with JSON (e.g. a dict) and then, if there was a Pydantic model declared as the response, passes it to that model.
And as the SQLAlchemy model doesn't really have a parent property yet at that time, it is not passed to the Pydantic model.

I'm thinking about changing the serialization implementation when there's a Pydantic model declared, to instead of trying to convert whatever is returned to a dict before passing it to the Pydantic model, to use the fields declared in the Pydantic model and try to extract them from that returned object.
This would probably solve the SQLAlchemy lazy-loading issues.

There's something else to have in mind. If FastAPI tried to extract the data directly without a Pydantic model, circular relationships would be a problem, as it would be trying to get child.parent.children[0].parent.children[0].partent, etc.
But if there's a Pydantic model with some specific non-circular fields declared, FastAPI could make SQLAlchemy generate/fetch the needed data before serializing it. Would that work for you?

Thank you for the detailed explanation.
I hope your suggestion will help. As about circular relationships, i suppose i already encountered them even with proper Pydantic models, though i have to test it more...

Just so you know, I just opened a PR in Pydantic: https://github.com/samuelcolvin/pydantic/pull/520 that would help us improve this.

same issue
while waiting for the PR, i'm setting the relationship to load every time:
parent = relationship("Parent", back_populates="children", lazy=False)

to follow on that, here is a simplified gist of how i'm "translating" from sqlalchemy to pydantic
https://gist.github.com/pourquoi/dd88e08e72b4a2a4e960a0106bdeda24
the pydantic models must be designed to prevent circular reference
I'm still new to python so i would appreciate any comments on how you guys are doing it.

The latest Pydantic version includes "ORM mode", to solve these specific use cases.
I just finished a deep integration of it into FastAPI, just released it in version 0.30.0 :tada:
Here are the new docs: https://fastapi.tiangolo.com/tutorial/sql-databases/
It should solve lazy-loading, hybrid-properties, dynamic attributes, relationships, and others. And it should work with all the ORMs, SQLAlchemy, Peewee, Tortoise ORM, GINO, etc.
You declare the data you want to export in Pydantic models and they take care of extracting it from your ORM models.


Generate apk doesn't work on windows

Is this a bug report?
Yes
Have you read the Bugs section of the Contributing to React Native Guide?
Yes
Environment
Windows
react-native -v: (I have tried different versions)
SDK Build Tools 25
Then, specify:

Target Platform (e.g. iOS, Android):
Development Operating System (e.g. macOS Sierra, Windows 10):
Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant):

Steps to Reproduce
I followed the tutorial on https://facebook.github.io/react-native/docs/signed-apk-android.html First problem: there is no gradle.properties file at C/Users/User/.gradle/
Inside the .gradle folder, I can only find 4 other folders: 'caches', 'native', 'daemon', 'wrapper'
Second Problem: I have generated the .apk, but it says 'release-unsigned'. It doesn't install on my Android phone.
Expected Behavior
I could find "gradle.properties" and generate a signed .apk

Can you post the latest RN version that you tried?
Did you try using the 23 SDK Build Tools?

I could successfully build it after updating my Android Studio and my gradle to 3.3


implement left and right

fixes #86
my linter accidentially replaced var with const. hope you don't mind... (const is anyway better to use)
I released it to test under @panter/react-native-modalbox

Is it going to be merged soon? useful PR for me!

@theohdv try installing @panter/react-native-modalbox

Then you I just need to set entry attribute to 'right' for example?
<Modal
  animationType={"slide"}
  visible={true}
  entry='right'/>

looking forward to this addition!

@kirushi check this lib react-native-modal (as this one seems to not be maintained anymore).


Fixed snippet behaviour in the middle of an attribute

Fixes: https://github.com/dotnet/razor-tooling/issues/6724
New fixed behaviour:

This seems like a perfectly good workaround, but I'm going to see if I can chat with some VS platform people about whether this is their issue or not. Seems like $0 should never actually appear in users code regardless. The extra ="" is different though, so we would probably want this anyway.
Does the issue exist/this fix it if you have <form act$$ion ></form> and invoke completion at that location?

In 17.4 Preview 1 <form act$$ion ></form> is working as expected with both Tab and =:

Seems like $0 should never actually appear in users code regardless

Yeah, I also thought about that. But in our case even if it worked fine, it would just apply snippet and be the same as the third variant I described in the issue, so the fix on razor-tooling side would be required anyway


PR stacks from different users interfere if they share the same local branch name

Unfortunately it seems https://github.com/ejoffe/spr/pull/304 introduced an issue:

Bob creates a stack in his local master branch and runs git spr update.
Alice runs git spr update from her local master branch. git spr assumes the PR branches beginning with spr/main/ belong to her. Her local main happens to be pointing to origin/main, and git spr closes the "missing" PRs

As I mentioned in https://github.com/ejoffe/spr/discussions/301 , in my opinion the better way to handle this is as Gerrit does... filter the PRs by the local commit stack, even if this means losing the "auto close" feature.

There is still a foreseeable issue with sharing stacks though, I forget how Gerrit handles this.
Spr does a force push of your stack on spr update, this means that if Bob pulls Alices's stack and amends a commit, the next time Alice runs spr update, Bob's change will be gone. I'm not quite sure how to handle this case gracefully.

True, I have been giving this some thought... if memory serves, gerrit doesn't handle this any differently... i.e. if you have checked out a series of patches pushed by someone else, then change the history, and then push to refs/for/master, it will essentially replace what was there too. The only real difference is that gerrit would show it as "revision N+1" and "revision N" would still be viewable (and therefore easily restorable). I don't think this is a huge deal... the collab workflow just requires a little more thought and staying in communication w/the people you are collaborating with.
Perhaps some sort of heuristic where you compare commit dates and warn/prompt if the commits being pushed are "older" than the previous revision? Although I don't think git spr really prompts for anything yet so that may not be a line you want to cross.

I have fixed this bug, and also removed the branch name from the pr namespace. I'm very happy with this change, thank you for proposing it.
PRs actually do mostly get closed automatically. With a few exceptions which could be improved.

should be fixed in v0.12.1

I have fixed this bug, and also removed the branch name from the pr namespace. I'm very happy with this change, thank you for proposing it. PRs actually do mostly get closed automatically. With a few exceptions which could be improved.

Thank you! This will make things much nicer for my team. I appreciate all your efforts.


How to delete a database?

Correct me if I am wrong. From what I understand db.js doesn't provide a way to delete a database.
It would be nice to have this functionality.

I think this issue can be closed now as #130 implements.

Yep done.


Pubsub/Bigquery

Same as: https://github.com/sigstore/rekor/issues/191

Closing, I don’t see a need for pub sub pushing of issued certificates if this is implemented in Rekor.


Insteon Hub 2245-222 Cannot Authenticate

Home Assistant release with the issue:

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io - raspberry by 3b+
Component/platform:
insteon
Description of problem:
I have followed the instructions at https://www.home-assistant.io/components/insteon and cannot get my insteon hub to connect to home assistant.  I have verified the host in my router and the credentials in my iPhone app.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
insteon:
  host: "<IP_ADDRESS>"
  ip_port: 25105
  username: "insteon_username"
  password: "insteon_password"
  hub_version: 2

Traceback (if applicable):
2018-11-25 22:26:15 ERROR (MainThread) [insteonplm] Athentication error, check your configuration
2018-11-25 22:26:15 ERROR (MainThread) [insteonplm] If configuration is correct and restart the Hub
2018-11-25 22:26:15 ERROR (MainThread) [insteonplm] System must be restared to reconnect to hub
2018-11-25 22:26:15 WARNING (MainThread) [insteonplm] Connection failed, retry in 1 seconds: <IP_ADDRESS>
2018-11-25 22:26:15 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.2 seconds.
2018-11-25 22:26:15 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.2 seconds.
2018-11-25 22:26:16 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 2.6 seconds.
2018-11-25 22:26:17 INFO (MainThread) [insteonplm] Connecting to Insteon Hub on <IP_ADDRESS>
2018-11-25 22:26:17 ERROR (MainThread) [insteonplm] Athentication error, check your configuration
2018-11-25 22:26:17 ERROR (MainThread) [insteonplm] If configuration is correct and restart the Hub
2018-11-25 22:26:17 ERROR (MainThread) [insteonplm] System must be restared to reconnect to hub
2018-11-25 22:26:17 WARNING (MainThread) [insteonplm] Connection failed, retry in 2 seconds: <IP_ADDRESS>
2018-11-25 22:26:19 INFO (MainThread) [insteonplm] Connecting to Insteon Hub on <IP_ADDRESS>
2018-11-25 22:26:19 ERROR (MainThread) [insteonplm] Athentication error, check your configuration
2018-11-25 22:26:19 ERROR (MainThread) [insteonplm] If configuration is correct and restart the Hub
2018-11-25 22:26:19 ERROR (MainThread) [insteonplm] System must be restared to reconnect to hub
2018-11-25 22:26:19 WARNING (MainThread) [insteonplm] Connection failed, retry in 3 seconds: <IP_ADDRESS>
2018-11-25 22:26:23 INFO (MainThread) [insteonplm] Connecting to Insteon Hub on <IP_ADDRESS>
2018-11-25 22:26:23 ERROR (MainThread) [insteonplm] Athentication error, check your configuration
2018-11-25 22:26:23 ERROR (MainThread) [insteonplm] If configuration is correct and restart the Hub
2018-11-25 22:26:23 ERROR (MainThread) [insteonplm] System must be restared to reconnect to hub
2018-11-25 22:26:23 WARNING (MainThread) [insteonplm] Connection failed, retry in 5 seconds: <IP_ADDRESS>
2018-11-25 22:26:25 WARNING (MainThread) [homeassistant.setup] Setup of insteon is taking over 10 seconds.

Additional information:
I have tried restarting hub as stated in logs, version: 1, removing port.  Hub is rev 2.2 - 4916.  Router is RT-AC87U
.

Do you have quotes around the host IP address or any of the other strings? If so, please remove them.

Same result with config sans quotes.  I am restarting home assistant then power cycling my insteon hub while keeping on eye on the ha logs.
insteon:   host: <IP_ADDRESS>   ip_port: 25105   username<EMAIL_ADDRESS> password: passwordfromsetupofhub   hub_version: 2
2018-11-26 19:08:16 INFO (MainThread) [insteonplm] Connecting to Insteon Hub on <IP_ADDRESS> 2018-11-26 19:08:16 ERROR (MainThread) [insteonplm] Athentication error, check your configuration 2018-11-26 19:08:16 ERROR (MainThread) [insteonplm] If configuration is correct and restart the Hub 2018-11-26 19:08:16 ERROR (MainThread) [insteonplm] System must be restared to reconnect to hub 2018-11-26 19:08:16 WARNING (MainThread) [insteonplm] Connection failed, retry in 57 seconds: <IP_ADDRESS> 2018-11-26 19:09:14 INFO (MainThread) [insteonplm] Connecting to Insteon Hub on <IP_ADDRESS> 2018-11-26 19:09:14 ERROR (MainThread) [insteonplm] Athentication error, check your configuration 2018-11-26 19:09:14 ERROR (MainThread) [insteonplm] If configuration is correct and restart the Hub 2018-11-26 19:09:14 ERROR (MainThread) [insteonplm] System must be restared to reconnect to hub 2018-11-26 19:09:14 WARNING (MainThread) [insteonplm] Connection failed, retry in 86 seconds: <IP_ADDRESS>

Use any web browser and enter the URL:
http://<IP_ADDRESS>:25105
This should prompt you with a login box. Enter the username and password.  This should return a page that looks like this:
INSTEON HUB2 Details
Hub2-V04-20140904
PLM Version:A4
Firmware:1017 Build Jul 18 2018 11:21:08
Insteon ID:A1.B2.C3

For device control visit connect.insteon.com
User Manual
Technical Support

Please confirm this works.

Ok the credentials on the bottom definitely do not work when it asks me to authenticate. I assume my only recourse is to hard reset the hub and setup my devices again?

Can you connect using the Hub app? From there you can reset the username and password.

Tom thank you for you time!  That ended up being the best route.  The only thing I can surmise is that I was not typing in the credentials correctly, but in my defense the font on the label is so bad that insteon has a support page dedicated to it: https://www.insteon.com/support-knowledgebase/2015/5/1/incorrect-hub-user-name-or-password
I personally recommend putting your own credentials in the hub as to not run into my same issue.

Good to here. BTW, some people have reported having issues getting the Hub app to save their self-generated credentials so be sure to test it per the directions above to confirm the settings were saved.
I assume you can close this issue, correct? I cannot close it since I am not an admin.

Everything is working and pulling into hassio as expected, thank you.