{AKS} Update monitor metrics related option names

This checklist is used to make sure that common guidelines for a pull request are followed.
Deprecate option names --enable-azuremonitormetrics and --disable-azuremonitormetrics, use --enable-azure-monitor-metrics and --disable-azure-monitor-metrics instead, so as to be consistent with the option names in official azure-cli. Fix issue #26600.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS


postfix not installed

Hey can you add
apt-get install postfix?

Done, this should be released soon


Select from Installed Apps can't find all apps installed

As example, I have installed YouTube and X but they are not listed in Select from Installed Apps.
https://github.com/user-attachments/assets/f8a2fe4a-7f5e-4324-9c0a-249778c96ef7

It is supposed to only show apps installed as split APKs. Are you sure these are not apps that you merged already


Moveable Editable With Buttons

Hey, looking to implement a custom control on Moveable elements as shown here:
https://daybrush.com/moveable/storybook/?path=/story/make-custom-able--editable-with-buttons
However I've not been able to work out how to do this with the Vue-moveable wrapper.
Are you able to provide some guidance as to how I can best achieve a similar effect with Vue-moveable?

Excuse me, have you solved this problem now


Strict variance and read-only versions of types

I feel like we should have an open "suggestion" issue with a meaningful title to track the work on stricter variance and read-only versions of types that the TypeScript team is considering, especially as other issues are being duped against it.  The initial design sketch and a few comments are in #17502.
After a little more searching, should this be merged with #10725?

Here is a rough sketch to what we have discussed over the past years regarding variance checking. if we were to implement it we need at least:

A new flag that disables the bivariance comparisons for all functions and methods. https://github.com/Microsoft/TypeScript/pull/18654 does this for function/constructor types but not methods.
A way to declare parameter variance for a function. We have existing suggestions in https://github.com/Microsoft/TypeScript/issues/1394 and https://github.com/Microsoft/TypeScript/issues/10717. Though looking at the issue so far, using a readonly/readwrite/writeonly annotations seem to be more fitting for a structural type system. A long with that we probably need a matching readonly type operator that allows you to get the readonly version of a type, and that is tracked by https://github.com/Microsoft/TypeScript/issues/10725.
A way to declare a lower bound on generic type parameter (https://github.com/Microsoft/TypeScript/issues/14520)

More discussions can be found in https://github.com/Microsoft/TypeScript/issues/18513 and https://github.com/Microsoft/TypeScript/issues/18339

@mhegazy If I understand correctly, does the second suggestion cover function calls that may currently modify readonly types?
In particular, got bitten before by popular "immutable" Object.assign({}, obj, { ... }) pattern when person forgot the empty object and did Object.assign(obj, { ... }) and TS didn't complain despite obj being Readonly.

I think we can do that regardless of variance. the issue here is we do not check readonly flags in assignment compatibility.
type I = { p: number };

declare var i: I;
declare var roi: Readonly<I>;

i = roi; // Not an error!

roi.p = 0; // Error, p is readonly

This was tracked by https://github.com/Microsoft/TypeScript/issues/11481. The reason why we have shied from this check is it forces users to mark their parameters as readonly consistently everywhere once one of their libraries adopts a stricter readonly annotations. This might have been overblown concern, and maybe we should revisit our decision of a new --strictReadonlyChecks flag.

it forces users to mark their parameters as readonly consistently everywhere once one of their libraries adopts a stricter readonly annotations

Hmm, true. But maybe TS could provide a simplified migration path for that concern, automatically "upgrading" any parameter types to readonly whenever it knows that function body doesn't modify the object? Then most of the code would be still compatible across such changes.

that is a possible solution. we have talked about code mods in the past..

I thought rather about runtime type detection than codemod, but codemod would work as well.

Basically:
// only reads `obj.prop`, so TS changes type of `f` to `({ readonly prop: number }) => ...`
function f(obj: { prop: number }) {
  return obj.prop;
}

I'm the maintainer of wix-react-tools
Considering this example:
type One = { one: 1 };
type OneTwo = { one: 1, two: 2 };
declare const useCase: (f: (f:One) => void) => void;
declare const fooOneTwo: (f:OneTwo) => void;

// this fails contravariance
useCase(fooOneTwo);
/* Error: TS2345:Argument of type '(f: OneTwo) => void' is not assignable to parameter of type '(f: One) => void'.
   Types of parameters 'f' and 'f' are incompatible.
    Type 'One' is not assignable to type 'OneTwo'.
      Property 'two' is missing in type 'One'.
*/

This is a straightforward example for the new contravariance check introduced in 2.6, as it protects the user from a scenario where useCase callsfooOneTwo with {one:1}.
function useCase(f: (f:One) => void){
f({one:1});
}

However, in our case, the useCase is a decorator, and f is a class. useCase extends the f argument and returns a new version of it. It is only designed to work on classes that accept a constructor argument that extends One, so fooOneTwo is a valid argument.
Up until now We've given the users a type-safe experience, with full support in strict-mode checks until now. To support typescript 2.6 We now need to choose between asking them to use --strictFunctionTypes flag and opt out of this great new feature, or remove a lot of the type definition value we currently offer.
In all the proposals regarding contravariance checks there was some sort of in/out notation that would have allowed us to avoid this dilemma. I'm very much interested in any plans of supporting such notations.

However, in our case, the useCase is a decorator, and f is a class. useCase extends the f argument and returns a new version of it. It is only designed to work on classes that accept a constructor argument that extends One, so fooOneTwo is a valid argument.

Then shouldn't useCase have this type?
declare const useCase: <P extends One>(f: (f:P) => void) => (f:P) => void;

@mattmccutchen That could be a workaround for some use cases, but what if I don't get to define useCase in my own terms, but rather get it from a generic API?
export type Feature<T extends object> = <T1 extends T>(subj: T1) => T1;
export type ReactFeature<P extends object> = Feature<ComponentType<P>>;
declare const useCase: ReactFeature<One>

@useCase
class X extends React.Component<OneTwo> {}

useCase((p:OneTwo)=>)

@amir-arad Now that I learned the basics of React for unrelated reasons, I took another look at this and didn't see an obvious solution, though I still don't fully understand what you're trying to do.  I don't think discussing your case further in this thread is helpful; I suggest you start a new thread on one of the normal support channels.  Linking to the original code is nice, but to make it easy for people to help you or evaluate a suggestion, you'll probably need to provide a brief explanation of why each type is set up the way it is and what the decorator actually does.

A possible application of that readonly keyword semantic is with the type of React.createRef(); though I'm not entirely sure it's safe to just use it as a heuristic.
The result type of React.createRef<T>() is { readonly current: T | null }; that is, the object is only used as a way to get current as an additional output from a mount operation. This means this object should be usable as a ref for any component that is a subtype of T.
However, typescript thinks that, as this object looks like an input, that the ref parameter wants to read current (instead of write to it); so it's not actually possible to give it to subtypes of T.
A concrete example:
const htmlRef = React.createRef<HTMLElement>();

// type error; HTMLElement not assignable to HTMLDivElement
<div ref={htmlRef}/>;

However, the assignability is supposed to apply the other way around.
This works with function refs because of the bivarianceHack.

I'd like to suggest a solution here: for a lot of the javascript code I work with, the vast majority does not mutate javascript objects in place, and when it does so, it's mutating locally created objects rather than function arguments. This is particularly the case with react and other functional/reactive frameworks.
The good thing about Flow is that it (somewhat) correctly type-checks mutable vs readonly types, by making mutable types invariant, whereas typescript is currently unsound in this regard, in order to be easier to use. The reason Flow is hard to use comes from a few reasons:

Read-only types are verbose, and only indicate that the callee cannot mutate the value: it says nothing about the value being changed elsewhere.
Types being invariant is consistently surprising and painful even when you're aware of this issue, as a lot of code deals with some kind of sub-typing relationships, especially in REST APIs.
$ReadOnly only operates shallowly, and so the intersection of nested types does not work as one might expect.

If typescript is going to add a strictReadonlyChecks flag, then IMO it needs to add the following to avoid the above pitfalls:

A light-weight way to get deeply immutable versions of types. It's not enough to make something shallowly immutable, or deeply readonly. I will put an example below, but you should look at how Rust handles & vs &mut for why this is important.
A standard way to perform a "deep-copy" of an object, which type checks and produces a T from any Immutable<T>.

Example of why it is important to be able to construct a deeply immutable version of a type, and readonly is not sufficient (neither Typescript nor Flow have any "good" way of soundly type-checking this code without introducing a lot of intermediate types):
type Foo = {
    x: { y: number | undefined }
}

// Refine "Foo" for when we know "y" is present
type Bar = Foo & {
    x: { y: number }
}

function takesABar1(bar: Readonly<Bar>) {
    ...
}

function example1(foo: Readonly<Foo>) {
    if (foo.x.y !== undefined) {
        // This should not compile, because even though we've checked the constraint,
        // there's nothing stopping the constraint from being invalidated at a later time
        // by the caller, who has mutable access to the Foo
        takesABar1(foo);
    }
}

function takesABar2(bar: Immutable<Bar>) {
    ...
}

function example2(foo: Immutable<Foo>) {
    if (foo.x.y !== undefined) {
        // This is completely safe, because we are guaranteed by the caller that
        // "foo" will not be changed, and even that "foo.x" will not be changed.
        takesABar1(foo);
    }
}

Here I am manually annotating types as being Immutable, but there are a few different options:

Light-weight syntax for immutable versions of types
Make usage of types immutable by default, except when declared mutable
Infer whether a type is used mutably or immutably by examining the code: mutability or immutability could be specified in specific cases when it cannot be inferred.

The third option would be the hardest, but would also be the least breaking, as much code will just continue to work even with the new flag enabled. The compiler will need to perform some kind of escape analysis to allow going from mutable to immutable values.
Example:
function test(arg: Immutable<Array<number>>) { ... }

const x: Array<number> = []; // New array, compiler can see we have the only reference
x.push(4); // Compiler infers that in this line and the line above, the array should be mutable
test(x);  // OK, because we have the only reference to `x` so we can "convert it" without copying
x.push(3); // Not OK, "test" could have kept a reference to `x`, and we guaranteed that it would be immutable

Read-only support would still be useful in addition to immutability.

Hello everyone,
Just thought I'd drop this here,
https://github.com/anyhowstep/ts-eslint-invariant-mutable-properties
It's a prototype typescript-eslint rule that attempts to make all mutable properties invariant.
I've tested it on some projects at work and it's not 100% accurate but it does the job for the most part.
While waiting for full typescript support, this might be a good interim solution.
There's no npm package yet because this is still a prototype. You can make it a custom rule for your projects, though.

I'm curious if anyone's run into actual bugs in their code from the lack of strict variance checking on assignments and function calls where the source and params are variables.

It's happened to me a bunch of times when I used to write OOP-y code with a lot of state mutations in TS.
I don't do that so much anymore. I mostly treat objects as immutable nowadays. This bypasses a lot of variance problems.
If you look at the table here, https://github.com/microsoft/TypeScript/issues/33234
You'll see that we currently don't have write-only properties, so we can ignore that row.
Readonly properties are considered covariant at the moment and this is sound.
The read-and-write properties are the problem here. They're still considered covariant when they should be considered invariant.
You can see an example on https://github.com/microsoft/TypeScript/issues/33234 for why covariant read-and-write properties are unsound.
However, if you start treating everything as immutable, even read-and-write properties, you've essentially also eliminated that row from the table in https://github.com/microsoft/TypeScript/issues/33234 as well.
All that is left are readonly properties in the table and those are sound. So, by pretending everything is immutable, you side step many problems with variance.

It does make me a little nervous when I have to step back into the "mutating world" though, because I know the type system won't catch me if a trip up

So if we had a linter to ensure that all objects and arrays were immutable then we'd be safe.  That's probably something worth exploring.

In terms of linting for immutable arrays and objects I've been using https://github.com/jonaskello/tslint-immutable which I'm very happy with. It seems like they are migrating it to ESLint with https://github.com/jonaskello/eslint-plugin-functional.

I'm curious if anyone's run into actual bugs in their code from the lack of strict variance checking on assignments and function calls where the source and params are variables.

I've recently started a project to explore working with mobx and ran into a bug when working with a copy constructor in a child class. Took me a time to figure out that I must treat fields as invariant. See #35006
I would really like to a see the introduction of a stricter type checking rule.

I have another use case for strictReadonlyChecks
code below works without compiler error:
interface I {
  readonly a: string
}

class C implements I{
  a= ""
}
const D = new C
D.a = "something"

in order to make property 'a' really readonly I should make it readonly in class definition too!
in other word how can I make sure when I am creating a class by implementing interface I creating it with right modifier?

I also ran against this another time.
My current use case is to identify several components by giving them a name. To easily use these components I created a union type of them and wanted to map to another union type with only their names as string literal types in it for other purposes. E.g.:
interface Component { readonly name: string }

class ComponentA implements Component { readonly name = 'a' }
class ComponentB implements Component { readonly name = 'b' }
export type Components = ComponentA | ComponentB

type GetComponentNames<T extends Component> = T["name"]
export type ComponentNames = GetComponentNames<Components> // "a" | "b"

This works as long as the name property in these classes are really readonly which means that it uses the readonly keyword or is marked with as const. Sadly since the interface can't enforce the readonly property on the class implementation another unaware team member can create a new component ComponentC without the keyword, add it to Components type union which will collaps the type of ComponentNames to a simple string and this destroys our efforts.
...
class ComponentC implements Component { name = 'c' }
export type ComponentNames2 = GetComponentNames<Components | ComponentC> // string

Here is a link to a  tsplayground for these examples.


add auto scroll background

auto scroll background fully css,
line not prettied (using notepad++)
fiddle, credit to someone
http://jsfiddle.net/1kcbpqfu/2/

Thanks @clariokids
But I prefer if we can use slider as a component so we dont need to touch css on every update, it can be use any library like react slick, react image gallery etc.

oh, i thought it's better to use simple css as needed


[cartographer] missing requirements

Describe the bug
Doesn't load due to missing pydantic
Cog Version
latest
To Reproduce
Steps to reproduce the behavior:
Do fresh setup of Red, try to install and load the cog
Expected behavior
it to load
Screenshots
no
Additional context
https://github.com/vertyco/vrt-cogs/blob/3a8331aa5078f27b5a112d2556662e01ad5aaa9f/cartographer/info.json#L12

ty for reporting, just pushed a patch for this


var is not local. (Blazor)

If you believe you have an issue that affects the security of the platform please do NOT create an issue and instead email your issue details to<EMAIL_ADDRESS>Your report may be eligible for our bug bounty but ONLY if it is reported through email.
Describe the bug
A clear and concise description of what the bug is.
 @for (var i = 1; i < int_amount_of_pages + 1; i++)             {             var intpagenr = i;
 SetPageNR( intpagenr.ToString()))"> @i.ToString()
 }
If 'int_amount_of_pages ' is 5, 'i' will always be 6 when given as an argument to 'SetPageNR', Only when you declare a local variable, equate it to 'i' and then give that as an argument is the expected behavior executed.
To Reproduce
Steps to reproduce the behavior:

Using this version of ASP.NET Core '...'
3.0 preview-5
Run this code '....'
see above
With these arguments '....'
see above
See error
unexpected behavior

Expected behavior
A clear and concise description of what you expected to happen.
i is not the max i was + 1, i is what it was when it went through that loop.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Include the output of dotnet --info

The necessity to declare a variable inside your loop is just how C# lambdas work - they bind to a variable, not to the value that was in the variable when the lambda was constructed.

https://github.com/aspnet/Blazor/issues/275#issuecomment-373686979
This is documented here (at the end) https://docs.microsoft.com/en-us/aspnet/core/blazor/components?view=aspnetcore-3.0#event-handling
Other issues:
https://github.com/aspnet/AspNetCore/issues/10138
https://github.com/aspnet/AspNetCore/issues/7134
https://github.com/aspnet/Blazor/issues/1562
https://github.com/aspnet/Blazor/issues/1402
https://github.com/aspnet/Blazor/issues/1422
https://github.com/aspnet/Blazor/issues/764
https://github.com/aspnet/Blazor/issues/447
https://github.com/aspnet/Blazor/issues/275

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.


Smooth scrolling for the Markdown Preview

I would describe the scrolling with markdown previews currently jumpily. Could some digital filter be applied to the scroll behaviour to make it more smooth? Maybe just a simple html-transition for the offset will be sufficient.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Introducing - 'add contact'

Description
A seeker can now send a connection request to an owner in order to start a connection process.

Adding the url needs to be inserted that leads to the 'add_new_contact' view.
Adding the 'add_new_contact' view that handles logic and errors of a seeker trying to add
a new connection with an owner.
Adding tests that test all cases from success to errors trying to use the 'add contact' feature.

Manual Tests
Tried to manually force all errors and received a fitting feedback.
Tried to add a successful contact and received a fitting feedback.
Additional Information
How to use:
While in a seeker profile, referring him to the url "/contacts/add/<apartment_id>" will
add a new pending connection request between that seeker and owner of the apartment.
Will work more nicer after the merge of messages, but not needed.
Issues closed by this PR
fix #113

While in a seeker profile, referring him to the url "/contacts/add/<apartment_id>" will
add a new pending connection request between that seeker and owner of the apartment.

By <apartment_id>, you mean the owner ID right?

While in a seeker profile, referring him to the url "/contacts/add/<apartment_id>" will
add a new pending connection request between that seeker and owner of the apartment.

By <apartment_id>, you mean the owner ID right?

@nadavsu An apartment ID, the PK of the 'Apartment' model, since a connection in made between a seeker and apartment models.


JSON file exported from AE is not working, tried everything

The plugin seems to be exporting corrupted JSON files. I can't get them to play.
If I use another JSONs from the demos, they work perfectly, but once I replace those with the one I exported, it fails to play.
Yes, I'm using the latest player and plugin.
You can see my JSON data here on this working demo > https://jsfiddle.net/16otprco/
If you change the JSON for one of the demos, it works perfectly.
Here's my AE file > https://www.dropbox.com/s/yhjzch7v4ekdgoa/Test.aep?dl=0
And here's my JSON file > https://www.dropbox.com/s/ft0oiuacj449bvn/data.json?dl=0

The issue is with exported fonts. If I outline the font then the JSON file works.

Hi, the extension should be able to export text correctly.
I just tried the .aep and it seems to work fine.
Can you share the .json again? It's returning a 404 page.

Here you go
https://www.dropbox.com/s/ke8t282ln8rc4dq/data.json?dl=0
This same json exported with the font as outlines works perfectly

For some reason the fontStyle is missing.
I have to look into it.

Thanks,
Is there any way I can add that myself to the JSON file to make it work in the meantime?

It's not that easy.
Can you try exporting it with a different font?

Already tried that.
The current JSON is exported using Helvetica. Before I tried others.

Same result?
What version of Bodymovin are you using?
is AE or your OS in a different language than english?

Latest version
AE is CC 2014 in spanish
I'm running macOS High Sierra in spanish

ok, I'll see if that is related

thanks! I'm just trying to export a 2 digit number, so no weird characters either

Hi I might have run into this issue as well, were you able to resolve it @klausabio ?

Closing, reopen if issue is still happening


[BUG] Still can not fetch more in ver 2.5.0 Pagination

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Go to 'search'
Search any keyword that has more than one page
Scroll down to bottom
No new items
Please complete the following information:

Device: iPhone 13
OS: iOS 16.1.1
App Version 2.5.0

Version 2.5.0 on my iPhone 12 with iOS 16.1.1 also meets the bug, and page jump button is still disabled.

Thanks for your feedback.
It seems like E-Hentai updated their layout too.
cc @chihchy need further investigation.

It should be fixed in v2.5.1.
cc @chihchy


installed AspNetCore.AsyncInitialization and created DbInitializer class

resolving issue #19

I am really new to ASP.NET Core so please bear with me 😁

I am really new to ASP.NET Core so please bear with me 😁

No problem, even better! Means besides contributing to a project, you learn some new tech 🙂

Now in the Program.cs

maybe because I inherited IAsyncInitializer interface?

According to the this, you don't need to do it that way, just change the Main to something similar to:
public static async Task Main(string[] args)
{
    var host = CreateWebHostBuilder(args).Build();
    await host.InitAsync();
    host.Run();
}

oops sorry. my bad

lastly

how should i properly register the initializer?

That should be correct.
I think it's the generic constraints that are not well defined in the DbInitializer.
Should probably be like this:
public class DbInitiliazer<T> : IAsyncInitializer where T : DbContext

That did it. Thank you.


fix bug where check box in founder spend funds was hidden

Hi @miladsoft why was this set as hidden? is it by mistake or you planned something else around the checkbox?

before

after

thanks @miladsoft

no still not working


Update tagprefix usage to tag in InitIntegrationTag

Within our tests, we heavily utilize an abstraction called DescribeTestFolder.
This will setup and teardown an "environment" per test that allows us to test various pieces of the test-proxy automation. Within this construct there is a function InitIntegrationTag that is the basis for pushing the "expected" bits that are generated from each integration test.
I partially refactored this when we originally went from branches to tags, but I'm finding that I didn't do a very good job with the update.
I need to clean up the use of TagPrefix instead of Tag when creating a test tag within InitIntegrationTag.  I don't necessarily want to conflate this change with another PR, so filing a separate issue.

Revisit if necessary next time this code changes. Not maintaining an issue for this.


@ binding reformatted strangely on rustfmt from rustc 1.41.0-beta.4

The following line is formatting differently and in an undesirable way with rustfmt from rustc beta (1.41.0-beta.4):
https://github.com/yeslogic/allsorts/blob/c78fb470ca2a575570543918cfbf15422b0377b2/tests/woff2.rs#L236
The diff looks like this:
Diff in /home/travis/build/yeslogic/allsorts/tests/woff2.rs at line 233:
             .iter()
             .map(|glyph| match glyph {
                 GlyfRecord::Parsed(
-                    found @ Glyph {
+                    found
+                    @
+                    Glyph {
                         data: GlyphData::Composite { .. },
                         ..
                     },

I still have this issue with a nested pattern on 1.57:
if let Some(
    mut
    ppart
    @
    PathPart {
        kind: PartKind::End { grid_width },
        ..
    },
) = ppart
{
    // ...
}

should I open a new bug for it?

@calebcartwright Yes, I'm using stable, and good to know. If there is a fix that's about to be published in 1.59, that's good enough for me.


python310Packages.testcontainers: init at 3.5.0

Description of changes

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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 181584 run on x86_64-darwin 1

2 packages built:

python310Packages.testcontainers
python39Packages.testcontainers

Thank you @SuperSandro2000 for reviewing, fixed the missing issues


There is no current event loop in thread 'Thread-1'

Hi, I'm using Zyte API for my Django project, but when I use Zyte, I get There is no current event loop in thread 'xxx' error.
My code:
from zyte_api import ZyteAPI

def omnifollow_product_extract(product_url):
    zyte_api_key = os.environ.get("ZYTE_API_KEY", "")
    client = ZyteAPI(api_key=zyte_api_key)

Could you provide instructions to generate a minimal, reproducible example?

@Gallaecio let me provide an elementary example:
On my Django project:

my_app/utils.py

from zyte_api import ZyteAPI

def omnifollow_product_extract(product_url):
    zyte_api_key = os.environ.get("ZYTE_API_KEY", "")  # or just set a static key
    client = ZyteAPI(api_key=zyte_api_key)

my_app/urls.py

urlpatterns = [
    path("zyte-test/", views.zyte_test),
    ...
]

my_app/views.py

from my_app.utils import omnifollow_product_extract

def zyte_test(request):
    omnifollow_product_extract("")
    return HttpResponse("success")

It's a basic way to use Zyte API? When I go to the view http://my_host/zyte-test/ I got this:

It looks like it's related to AsyncZyteAPI, but I want to use ZyteAPI only for my helper function.

ZyteAPI uses AsyncZyteAPI underneath. Could it be that you are creating ZyteAPI in one thread and then using it from a different thread? It’s possible we did not account for that scenario (and we should).

I have tried reproducing your issue with this code base, but it seems to work. Could you create a PR against that repo with the necessary changes to reproduce your issue?

Oh, right, I used runserver.

@Gallaecio looks like the issue happened on Python 3.8 and Django 2.2.19

@Gallaecio, I re-read the README and found that Python 3.9+ is required. However, I can install it on my old project, which uses Python 3.8. Should we update the Python dependence to the library?

@Gallaecio thanks for your support :100: I will update my project!


[WIP][DO NOT MERGE] highlight box resizing

This looks great. I think it's a good idea to get rid of the min-width on the boxes as that breaks the alignment to other 1/3 columns in the grid.
I think it might work better if the tablet breakpoint has 2 columns, so it goes mobile: full width, tablet: 2 columns, desktop: 3 columns.
We should apply the same rules to the sub topic grid as well.

@alextea Thank you, that's really useful! Going to close this PR for now, but I've written up your suggestions on Trello: https://trello.com/c/votHcdID/34-fix-resizing-of-highlight-boxes-and-sub-topic-grid


DoDo: Remove while(!Serial);  from all examples

This line make many problems on differnt controllers

done


Moved server logs to target/

Having a log file the in root of every project is not very Git-friendly 😄 (sure I added it to the global gitignore, but still). So I moved it to target/. This is also convenient because you can reset logs when running clean in sbt.
I also changed stderr log file, but probably you want to have them together.  Also, what does pc in the name stand for?

Ah yes, that's taken straight from https://github.com/dragos/dragos-vscode-scala/blob/master/ensime-lsp/src/main/scala/org/github/dragos/vscode/Main.scala#L20-L21
I agree moving them to target is a sensible move. About splitting stdout and stderr instead I'm not sure. I think there's a value in having a unique file. WDYT @olafurpg?

OK. I changed it back. What about a better name for the file? I understood that pc stands for Presentation Compiler.

metaserver.log ftw 💯 👍


app created with ionic cloud has a large boottime

I have a problem if I build my application with ionic cloud: In case I build my app with ionic cloud the boot of the application takes quite some time. At the moment the boottime is 15 seconds for my application. I read some other topics about it long boottimes and they suggest to use the --prod option.
I use the following command:
ionic package build android --profile productioncer --release
And I tried the following command:
ionic package build android --profile productioncer --release --prod
But both commands results in the same .APK (same size). How can I decrease the loading time / boottime of my app?

Depending on the Ionic CLI version you are using you first have to build your app locally with --prod (npm run build --prod for example). Then ionic package will upload and use that optimized version to build your app.
Current versions of the CLI build automatically, so this should be taken care of.


Prompt for a new scale or chord upon completion of scale or chord

This app is great! It would be even better if I could toggle an option to suggest another random chord or scale after completing the currently selected one.

That's a pretty good idea, I'll see what I can do!


curl: 8.8.0 -> 8.9.0

https://curl.se/ch/8.9.0.html
https://curl.se/docs/CVE-2024-6197.html
https://curl.se/docs/CVE-2024-6874.html
Fixes: CVE-2024-6197, CVE-2024-6874
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

Built passthru.tests, macos 12 x86_64. Built pkgsMusl.curl.tests.withCheck on nixos x86_64.

Also built curl.tests, pkgsi686Linux.curl.tests.withCheck, pkgsCross.aarch64-multiplatform.curl, pkgsStatic.curl.tests.withCheck on nixos x86_64.


No blocks provisioned if parallelism/blocks = 0

If I set initBlocks=0 and parallelism=0 I don't think any blocks will be provisioned. I tested and the script makes no progress. Perhaps we should catch this case and present an error to users.

This is a bug, I'm working on this.

This is fixed, and will be going into 0.4.1.


[5.1-04-24-2019] IRGen: Don't emit opaque type descriptors twice

rdar://50500620

@swift-ci Please test

Might want to add "[5.1 04-24]" (or something) to the title of this PR to distinguish it from its brethren.

Build failed
Swift Test Linux Platform
Git Sha - 7a8ccb09078af1c4394e7f29d3eab989d576465c

This change is different that what's on master and the 5.1 branch. Why the difference? Also, I see Slava had a comment about a test case. It would be good to add one if that's not too hard.

OK, Arnold updated this to match the revised PR for master, and he's going to follow up with a test case later.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 7a8ccb09078af1c4394e7f29d3eab989d576465c

Build failed
Swift Test OS X Platform
Git Sha - 7a8ccb09078af1c4394e7f29d3eab989d576465c


Route is not resolved when only using query parameter in URL

Hi,
I'm using  "navigo": "^5.3.2".
I have following code:
var router = new Navigo(null, true, '#!');
router.on({ '/home': function (query) {
     console.log('router->on query:', query);
     mainApp.loadCtrl(HomeCtrl, query)
  }
});

Calling http://localhost:3000/#!/home works - route is found.
Calling http://localhost:3000/#!/home?q=test is not working - route is not found.
If I use a param, like in the example on github project page, it's working:
router.on({ '/home/:useless': function (params, query) {
     console.log('router->on query:', query, 'params', params);
     mainApp.loadCtrl(HomeCtrl, query)
  }
});

Calling http://localhost:3000/#!/home/x is working!
Calling http://localhost:3000/#!/home/x?q=test is working!
If I have just a query param without parameterized URLs, the URL is not resolved.
Do you have any idea what I'm doing wrong?
Thanks,
Matthias

Same exact issue over here!

@mr678 @Datamance can you please try 5.3.3 version.

@krasimir works! :-) Thank you so much for providing a fix so fast 👍


Exclude 'WEB-INF' folder and html files of gwt-editors from 'dist' folder

Our kie-tools channels (KIE Sandbox, VS Code Extension ....) have dependency for gwt-editors builds. These gwt-editor builds contains also assets, that are not used by mentioned kie-tools channels.
We should exclude :

WEB-INF folder
html files

from kie-tools channels 'dist' folder.

Fixed here https://github.com/kiegroup/kie-tools/pull/1347


Added the uri of AnimatedCollectionViewLayout

In this file there was the uri of FDTake, so I've modified this file to use the correct uri

Nice catch!! Thanks!


Rollback all locks to prevent from losing the pessimistic lock in flashback

Feature Request
Ref #13303.
Currently, we will delete all locks unconditionally when performing the flashback. Though we will check the minimal resolved TS before a flashback multiple times (https://github.com/pingcap/tidb/pull/37607, https://github.com/tikv/tikv/pull/13412) to prevent breaking any transaction consistency, there is still a case that we should handle when it comes to a pessimistic transaction.
Assume that we have two clients {c1, c2} and a key k1:

c1 begins a pessimistic transaction with ts1.
c1 creates and writes the k1, which will put a lock record in lock_cf.
c2 starts to flashback to version ts0 that is smaller than t1, which will delete the pessimistic lock written in step 2.
c1 commits the transaction successfully.

We should better fail this kind of transaction to prevent breaking the flashback result, a possible method is to roll back the lock rather than deleting it directly, so that the commit will find a conflict and fail eventually.

/cc @HuSharp

/assign

Can you elaborate on why the transaction can commit successfully with the lock deleted

Can you elaborate on why the transaction can commit successfully with the lock deleted

Since TiKV may fail to write pessimistic locks due to pipelined process. If the data is not changed after acquiring the lock, we can still prewrite and commit the key. We can regard it as a fallback to the optimistic transaction.
https://github.com/tikv/tikv/blob/4cce9e7869348c8a51894a047c487783d6190312/src/storage/txn/actions/prewrite.rs#L62-L70

Hi, @sticnarf could you please help add a type label to this issue and merge #13521, I didn't have permission, thx a lot!


Crash during XCode Unit Test run: "Bank manager destroyed with active banks"

My relatively simple unit tests in SongSprout have started crashing out with the latest AudioKit release 5.1.0, and it happens against the develop branch as well. I've tried a few things to isolate the problem, and it appears to be triggered by the call to mixer.connectionTreeDescription (surprisingly enough).
Here's what the output looks like:
Test Suite 'AccompanimentTrackDefinitionTests' started at 2021-05-20 10:31:55.117
Test Case '-[SongSproutTests.AccompanimentTrackDefinitionTests testMakeNodeAndConnectRoute]' started.
2021-05-20 10:31:55.163155-0700 xctest[74766:4718854] [midi] MIDI.swift:init():52:Initializing MIDI (MIDI.swift:init():52)
2021-05-20 10:31:57.243504-0700 xctest[74766:4718854]  ASSERT FAILURE: Bank manager destroyed with active banks
Program ended with exit code: 9

While this error may seem to have something to do with the financial system, I suspect it has more to do with soundbanks of some kind.
Should be easy to reproduce by just running unit tests from this project:
https://github.com/dunesailer/SongSprout

That's not a very good warning message, but for your tests, the main issue is that you're not connecting the mixer. I can add a check to make sure the engine is not null when querying for the connectionTreeDescription, but for your test, I just added
        let engine = AudioEngine()
        engine.output = mixer
        try! engine.start()

in the first test that failed, before the connectionTreeDescription request and the test passed.

Okay, thank you for the tip to solve this. However, it does strike me a bit as unexpected behavior. I would not expect the calling of connectionTreeDescription to fail based on a specific attachment state of the graph. In fact, this used to pass just fine. Is the underlying cause of this related to the fact that I load a soundfont during the creation of the node, which requires some engine resources that it didn't require before?

I don't understand how it could have ever worked without an engine being defined. Could it be you create the engine elsewhere in your code before?

No, the only place I create the engine has always only been inside the Orchestrion class itself, which never gets called  by these unit tests.

I try to write unit tests so they are as self-contained as possible, so I avoided initializing anything that I didn't have to. I actually kind of liked the fact that these used to work as sort of "standalone graphs", even though that's certainly not much of a realistic use case (unless somebody wanted to do something like pre-assemble various graphs and then conditionally hook them up to the output mixer based on some change of condition, maybe?)

So somehow in the past that engine must have been the one providing the connectionTreeDescription. Why isn't it doing so anymore?

I think it has to do with Node now being a protocol. Before it may have kept a reference to the engine internally or something.

That's a reasonable theory. I don't have a better one. :) If you think it's important to get to the bottom of this, I can do some forensic analysis to try to figure it out. If not, I'm comfortable just moving on and chalking it up as "interesting".


added courses

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Added courses from cognitiveclass.ai (free courses on different topics)
Why is this valuable (or not)?
Will give beginners a good overview of various implementations
How do we know it's really free?
It is hosted on cognitiveclass.ai which is a free course website
For book lists, is it a book? For course lists, is it a course? etc.
Courses
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

@eshellman updated the course list in regards to the previous PR, all updated now :D

please resolve conflicts.

@eshellman conflicts resolved

Thanks, and welcome to free-programming-books!


automatically accept Xcode license

This works when SSHing and doesn't even require displaying UI.
I'd also recommend that the call to install_components be replaced with simply open #{xcode_path}, since it doesn't seem to currently be working for me (clicking Install doesn't work when SSHing I think), but opening Xcode automatically prompts for the tools anyway. So it's the same behavior as when it works, but it just works more often :wink:.

Thanks for this! :sparkling_heart:
As for installing components, I'm thinking of removing it entirely for the next version, until we have a reliable way to automate it.

:+1: ! That was simple

As for installing components, I'm thinking of removing it entirely for the next version, until we have a reliable way to automate it.

:+1:

Components installation is now gone in bcfe0719863d6a6f54162800e4a430addcf5c880


CSS styles don't work for autocomplete component when embedded in a shadowRoot

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
We're trying to add the Material UI v5 Autocomplete component to our existing LitElement (Web Component-based app).
We're using  with JSS set to use a custom insertionPoint - our element's shadowRoot. This causes the styles to be properly inserted inside of ShadowDOM, but the autocomplete component also contains some dom elements that seem to be appended to the document's body (outside of our shadowRoot).
Because of this, half of the component is styled when we inject our styles into our shadowRoot, but the other half of the component (the dropdown menu) is not styled.
Expected Behavior 🤔
It'd be nice if there was a clear way to get styles for this component to work inside of a shadowRoot. If the entire element was inside of the shadowRoot (where our React mount point is), then the styles would work.
Alternatively, if there was a way for us to apply the styles for the autocomplete component both  globally and within our shadowRoot, then the component would also be styled. But as is, there seems to be no way to get this component properly styled when it's inside of a shadowRoot.
Steps to Reproduce 🕹
Steps:

Create a Web Component that's rendered somewhere on a page.
Mount React into the shadowRoot of that component.
Render Material UI's  in that React mountPoint anywhere.
Wrap  in a  that has jss set to use a custom insertionPoint of the Web Component's shadowRoot.

Context 🔦
I'm trying to embed Material UI components inside of an existing Web Components-based app, and this issue makes using the autocomplete component infeasible.
Your Environment 🌎

`npx @material-ui/envinfo`
  System:
    OS: macOS 11.2
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
    Memory: 14.04 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
  Managers:
    Homebrew: 2.5.6 - /usr/local/bin/brew
    pip2: 20.2.4 - /usr/local/bin/pip2
    pip3: 18.1 - /usr/local/bin/pip3
    RubyGems: 3.0.3 - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 4.2.1 - /usr/bin/gcc
    Git: <IP_ADDRESS>5. - /usr/local/git/current/bin/git
    Clang: 1<IP_ADDRESS> - /usr/bin/clang
  Servers:
    Apache: 2.4.46 - /usr/sbin/apachectl
  Virtualization:
    Docker: 20.10.2 - /usr/local/bin/docker
  IDEs:
    Nano: 2.0.6 - /usr/bin/nano
    Vim: 8.2 - /usr/bin/vim
    Xcode: /undefined - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Perl: 5.28.2 - /usr/bin/perl
    PHP: 7.3.24 - /usr/bin/php
    Python: 2.7.16 - /usr/bin/python
    Python3: 3.6.8 - /usr/local/bin/python3
    Ruby: 2.6.3 - /usr/bin/ruby
  Databases:
    MySQL: 5.6.47 -<EMAIL_ADDRESS>    SQLite: 3.32.3 - /usr/bin/sqlite3
  Browsers:
    Chrome: 88.0.4324.150 (used this browser)
    Firefox: 85.0
    Safari: 14.0.3

See #17473. It seems that you don't need the isolation in your case. I would recommend not using a shadow root. If you really need to, you can customize the container of the portaled element, or even disable the portal


python310Packages.pyvicare: 2.27.1 -> 2.27.2

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 231014 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.vicare
python310Packages.pyvicare
python310Packages.pyvicare.dist
python311Packages.pyvicare
python311Packages.pyvicare.dist


Push new Release for Web Update

We are currently running into an issue with the web plugin as the currently released version is still depending on web: <1.0.0. This seems to have been updated 2 months ago but not released.
The reason for this conflict is due to firebase plugins now specifying web: ^1.0.0

Pubspec File - https://github.com/firebase/flutterfire/blob/main/packages/firebase_core/firebase_core_web/pubspec.yaml
PR with the update - https://github.com/firebase/flutterfire/pull/13200

@mogol any possibility of this? We are currently at a blocked point with many projects.

@mogol any possibility of this? We are currently at a blocked point with many projects.

You can override web: 1.1.0 for all your deps as for temp solution
dependency_overrides:   device_info_plus: ^10.1.2   flutter_secure_storage_web: ^2.0.0-beta.1   web: ^1.1.0

You can override web: ^1.1.0 for all your deps as for temp solution

It may come to that :/ We typically try to minimize the use of that as much as possible in our projects as it has a sneaky way of getting forgotten about and then never updated.


Update MANIFEST.in

Recursively include all plugin yaml files.
I'm occasionally running into an issue where some plugin yaml files are not bundled together in the nomad build.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.039%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
35713

Relevant Lines:
38385

💛  - Coveralls


Fix memory leak(#699)

Signed-off-by: Alexey Ryazanov<EMAIL_ADDRESS>
Update v2/protocol/http/protocol_retry.go

Already fixed at HEAD


Error: Expected string containing name

Hi everyone, i am trying to execute an action with the new version of the library and here is the error i get. I have trouble understanding what i did wrong.
Error: Expected string containing name
    at SerialBuffer.pushName (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:232:19)
    at Object.serialize (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:795:57)
    at Object.serializeStruct [as serialize] (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:559:28)
    at Object.serializeStruct [as serialize] (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:559:28)
    at Object.serializeStruct [as serialize] (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:559:28)
    at serializeActionData (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:1022:12)
    at Object.serializeAction (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-serialize.js:1032:15)
    at Api.<anonymous> (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-api.js:277:71)
    at step (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-api.js:44:23)
    at Object.next (/home/ubuntu/poc/project/api/implementation/node_modules/eosjs/dist/eosjs-api.js:25:53)

Here is my code :
api.transact({
            actions: [{
                account: 'accountName',
                name: 'additem',
                authorization: [{
                    actor: 'accountName',
                    permission: 'owner',
                }],
                data: argItem, //json object similar to what i use in => cleos push action contractName additem 'argItemjsonstring' which works.
            }]
        }, {
            blocksBehind: 3,
            expireSeconds: 30,
        }).then(result => {
            console.log(JSON.stringify(result));
            res.send("OK");
        }).catch((error) => {
            console.log('\nCaught exception: ' + error);
            next(error);
        });

I imagine it is similar to https://github.com/EOSIO/eosjs/issues/429 but the solution was not posted there.

Like #429, there's not enough information here to diagnose. Show the fully-expanded object you're passing as the first argument to api.transact.

Also the ABI for the contract you're sending an action to.

The bug was fixed! Thank you for your help.

Did you manage to fix this? My transactions are working with the same format as others, for some reason just my 'issue' action is throwing this error. Using the eosio.token contract.
async function issueToken() {
            try {
              let resp = await api.transact({ actions: [{
                    account: paramss.contract,
                    name: 'issue',
                    authorization: [{
                      actor: paramss.sender,
                      permission: 'active',
                    }],
                    data: {
                      to: paramss.receiver,
                      quantity: `${(paramss.amount).toPrecision(5)} ${paramss.symbol}`,
                      memo: '',
                    },
                  }]
                }, {
                  blocksBehind: 3,
                  expireSeconds: 30,
                });
              resp = {...resp, paramss}
              console.log(resp);
              res.send(resp)
            } catch(err) {
              console.log(err)
            }
          }
          issueToken()


Updated ShrinkWrap to 1.2.3

Can one of the admins verify this patch?

this is ok to test

Closing as we're now in 1.2.6. Thanks!


New Logo for Rainloop?

Hi there,
I was wondering whether you need to have a refresh on your branding for Rainloop? Would love to help.
Am focused on working with open source projects: https://ura.design
Would be great to see this happening!

@elioqoshi  your business strategy is to lurk around and spam your advertisements ?

Yes, please edit (remove) your message and close this case.  I wanted to do this for free. If you would have done your research you would have found out that we are focused on doing branding for open source projects. Have you even checked my background before calling me a spammer?
Reconsider your attitude before driving people into reporting. Thank you.

Even if I was a spammer, having that attitude drives contributors away. And then we complain why there are lack of contributors and inclusivity. Great job driving potential contributors away.
I was recently considering to switch to RainLoop as I really liked the UX. If the attitude of the project is however even remotely close to what I have seen here, I really hope someone forks it into a project where one isn't an asshole at the first best opportunity.

You do realise we have done branding, free of charge, for numerous free and open-source projects, right? If not, have a look at that "spam URL" that Elio posted.
Congratulations for driving us away at first glance. Take care and goodbye.

What is this? Do you guy's react to every contributor like this? The guy offers you to help you out with a logo. I don't see why he's spamming because he is offering it for free. I've worked with him great guy in any way, not a spammer!
Also a request to remove / edit the message, so you like censorship?

Woah amazing! I was thinking in setting this up, but this gave me a bad feeling.

Your work experience consists of "Portfolio Gigs", most of the logo's are mis-representations made to look like your did the logos for those various projects and companies. Facts are they do not correlate to what is written on your CV.
If you really wanted to make logo's and graphics for this project, you would of already made them, and then submitted a PR and/or posted them for comment/voting.
Your modus operandi consists of spamming projects mailing lists and repos in order to solicit for work.
Zero tolerance to spammers.

@extremeshok I'm sure he does logo's. He made some logo's for my project and they are better looking than your current one imho.

@elioqoshi @giannisk @brantje @animalillo , if you did your research you should know that nor me nor @extremeshok are in any way the autors of this software.
If you want to selflessly contribute, do a PR or contact the author by e-mail. His e-mail is published on the front page for god-sake.

I never, in my entire life, saw a worst reaction coming from open-source people. If you guys don't need a logo, just say no, thanks and close the case.
Because of bad people, like you, in the open source community, that doesn't know how to deal with other people, which are the core components of the model, that some projects are completely abandoned.
Be nice, BY DEFAULT.

Curious why you see my opinions as spam.
Spam: send the same message indiscriminately to (a large number of Internet users).

@branje only spammer is the person that created the issue.
@douglascamata people like us are needed... we directly fund open source projects, contribute code and releases. We own commercial rainloop licenses, which keeps this project alive.

@extremeshok no, people like you are definitely not needed. If it weren't for a few people like you, OSS projects would have many more contributors, for sure. Today, for example, it's high likely that this project lost one contributor. I wonder how many more it already lost or might lose because of behaviours like this.

@extremeshok ahem, after carefully reading every comment here, I came to the conclusion that this project is not worth devoting our time on and it is a clear example of why some open source projects are failing, because of people like you that do not know how to deal with new possible contributors. You are trying to stay in your comfort zone and don't like innovation and better design for your project? Be my guest, we got more important projects to contribute to instead of wasting time with projects whom communities do not welcome new contributors.

@extremeshok Your contributions don't matter much if you don't know how to behave properly in a community. Am curious what the lead developer thinks of this. I somehow have still hope both of you don't represent the values of the project.
Since you asked, here is the logo, together with the source files. Feel free to do whatever you want with them. Consider them Public Domain:
https://elioqoshi.me/cloud/index.php/s/KzLvRTZFHAkzRcb

You have no idea how destructive you are. You are the reason projects need Code of Conducts.

nice logos

I work as a designer for Mozilla and Tor, trust me, I'm not doing this for my portfolio. I can imagine many other people contributing for different reasons then suggested, but you shouldn't assume my intentions are the same.

@AnXh3L0, extremeshok is NOT the developer or owner of this project. Don't make such a big deal of one or two random people's comments. And don't write off someone else's project because of it.

These comments don't look like personal opinions. And anyway, if you guys didn't have anything to contribute to a healthy discussion about the subject of the PR and are not capable of taking a decision based on it: why the hell you started to speak aggressively?
Having an opinion on everything doesn't mean you should expose it. Sometimes, like today and here, you both could have just kept your toxic opinions to yourselves.
Be responsible and think twice before you type, stop trying to ignore consequences just because it's my personal opinion, so I say whatever I want, herp derp.

If this was a PR I'd agree. But it was an issue and it looks spammy. And I'm not going to click some link to check.

I liked this new proposed logo / identity colors. :+1:
I think in addition to representing better, is more remarkable!
... Just my opinion, as a fan of the project.

My opinion on this, for what it's worth. The OP is a tout for business no matter what 'open source' nonsense is spouted. Open Source != free (cost), especially when it comes to branding.
Looking at their site you can see that they clearly expect to be paid in money, not kind, either directly or via Patreon. Sure, the example amounts are low but it is still money, therefore this is unsolicited advertising.
A genuine contribution would be a PR with the logo they think would look nice. That's the difference between linking to a website which clearly has a 'What is your budget?' field and contributing with actual work, for free.
Receiving donations is perfectly legitimate, we all need to eat (and make a living). However, advertising your services like this is not the way to go about it and is the definition of spam.

Regardless of the source of the redesign or the attitude around soliciting a redesign:
Requesting that a design change comes through a PR drives away very talented designers who aren't familiar with git. Knowing git shouldn't be a requirement for contributing to your project, especially if your skill set doesn't involve coding.
Design is an iterative process, and you can't just "do a PR" and fix it as if it's a bug. Designers take feedback into consideration, work on it, and come back with something new. Their tools aren't all transferable to code and commits.
There are already a lot of hurdles to get designers contributing to open source, something which is a detriment to the entire open source community.
But in the end this seems to be a project that harbors trolls and lets them scare off newcomers and willing contributors. @elioqoshi I honestly wouldn't waste my time.

I definitely see this as Spam.
I am coder and designer as well, and I've worked along with some Open Source projects (like aMSN, and others in the past) and my own Open Source projects (which also, I've have my own business). So, for me to contribute to this kind of projects one should do it directly, not to post your business site... Thats clearly Spam, no matter if your business site is about Open Source or Comercial.

Own serval open source projects too and @elioqoshi did logo's for them, all all of them are awesome.
So imo he is not a spammer, just a great guy who like's to design logo's for free.
Other people would pay 100's if not 1000's or a logo design, so why you can't be thankful?


MVC5 support

MVC5 is now in RC status, maybe it's time to add preliminary support for MVC5? :)

Great question @neographikal !
My first instinctive answer to that is going to be: NOPE. From what I've seen and played around with (so far) it looks like ASP.NET Core 1.0 has a very similar conceptual Authentication story, baked right in. It doesn't look like it's tied explicitly to Sql Server or cringe Membership/ASP.NET Membership, etc.
For example, have a quick look at the ASP.NET Core Security repo and the samples found in that repo, which are doing what SimpleAuthentication was created to do.
In summary: looks like ASP.NET Core 1.0 will replace SimpleAuthentication.
I'm not 100% sure yet, as I've only done some small playing around - but it basically looks like it.


Adding Home, About Us, Pricing Information

They currently don't lead anywhere

Removed with https://github.com/DSC-McMaster-U/Gamified-Learning-Platform/pull/130


[Feature] Loading dlls without LoadLibrary

This feature would be useful to load ue4ss in some configurations, while also being useful to not lock the cpp mod dll after loading.

could not certain features like config load in seperate threads and then join when done

Config load and most of the stuff we do isn't too expensive and we won't see a reasonable benefit from the added complexity. Pattern scanning is the part that takes up the most time, but that's already multithreaded


Installing Tackle on RPI4

Hi SME,
I tried to install Tackle on RPI4 but it shows the following error in the subscription:
bundle unpacking failed. Reason: BackoffLimitExceeded, and Message: Job has reached the specified backoff limit

Tried the steps here, problem remains.
I am using OLM v0.22.0 and Kubernetes v1.24.2
Can Tackle be installed on RPI4?

@chengkuangan Your k8s version and OLM seem reasonable but without more information about other resources in the namespace is hard to say what is happening , specifically state of operator/operands, also full subscription output.

@chengkuangan This may be possible now, but it's untested. We've done multi-arch builds for amd64 and aarch64 for all of the images. Prior to this work (started in February) there would have been no images available that would run properly on an RPI4 cluster.
The bundle image isn't architecture specific, however so I'm not sure what would be happening at that point to cause a problem. If you try again and hit the same issue it would be interesting to know if the catalog source resource has any status indicating a problem, or even the pod to extract the bundle.

@jmontleon I suspected it was no arm64 earlier when I was trying.  I will look into trying this again and will get back. Thank you for notifying me.

@chengkuangan Thanks. The operator is called Konveyor Operator now and we released 0.1.0 of Konveyor Operator yesterday. If you give it a try and have problems let us know and if we can find a way around it we can fix it.

Since we don't have a bot to mark issues as stale and isn't something currently on our roadmap but something that may work. I'm going to close the issue, trusting it will be reopened if it is an actual problem we should look into solving.


Format exception

Julia's logger has a special formatter if a log argument is called exception:
julia> try
         sqrt(-1)
       catch e
         @error "asdfasdf" exception=(e, catch_backtrace())
       end
┌ Error: asdfasdf
│   exception =
│    DomainError with -1.0:
│    sqrt will only return a complex result if called with a complex argument. Try sqrt(Complex(x)).
│    Stacktrace:
│     [1] throw_complex_domainerror(::Symbol, ::Float64) at ./math.jl:33
│     [2] sqrt at ./math.jl:573 [inlined]
│     [3] sqrt(::Int64) at ./math.jl:599
│     [4] top-level scope at REPL[1]:2
│     [5] eval(::Module, ::Any) at ./boot.jl:331
│     [6] eval_user_input(::Any, ::REPL.REPLBackend) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:134
│     [7] repl_backend_loop(::REPL.REPLBackend) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:195
│     [8] start_repl_backend(::REPL.REPLBackend, ::Any) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:180
│     [9] run_repl(::REPL.AbstractREPL, ::Any; backend_on_current_task::Bool) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:292
│     [10] run_repl(::REPL.AbstractREPL, ::Any) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:288
│     [11] (::Base.var"#807#809"{Bool,Bool,Bool,Bool})(::Module) at ./client.jl:399
│     [12] #invokelatest#1 at ./essentials.jl:710 [inlined]
│     [13] invokelatest at ./essentials.jl:709 [inlined]
│     [14] run_main_repl(::Bool, ::Bool, ::Bool, ::Bool, ::Bool) at ./client.jl:383
│     [15] exec_options(::Base.JLOptions) at ./client.jl:313
│     [16] _start() at ./client.jl:506
└ @ Main REPL[1]:4

Running this code in my CI (with the logger set up like in the readme) gives:

Ah, I was hoping that would "just work". PRs are welcome! Or otherwise, I'll eventually have a look at how the stdlib does it and see if I can replicate, but no promises on a timeline.

Ah, I was hoping that would "just work". PRs are welcome! Or otherwise, I'll eventually have a look at how the stdlib does it and see if I can replicate, but no promises on a timeline.

#12

#12


Nothing happens following instruction.

I did all manual steps and getting just blender cube render on F12.
Activating script just print new "bpy.ops.text.run_script()" line in tab under Blender terminal window.
Seems manual missing important steps.

You might need a couple of things --- but the addon might (not) work depends on the latest ControlNet update, but few pointers:

you gotta have ControlNet to be able to be controlled using other script, this is in the setting under Automatic1111
you probably better of to have 3D models or rig that can later translate into: depth, openpose bones, canny, etc
when you hit F12, it will render in Blender, and the after that, it will send the image into Automatic1111, process it using the ControlNet and the model of your choice, and return the new image that's generated using AI.

And also this annoying --api mode https://github.com/coolzilj/Blender-ControlNet/issues/5

I had the same problem.
enabling scripts and putting --api in startup args worked.

enabled "Allow other script to control this extension" in ControlNet settings.
Added --api to webui-user.bat
run script in blender scripting window, hit F12, it just saves a "before" image to selected folder then nothing else happens.
Any help?

I don't know, I had "Allow other script to control this extension" enabled, and run with --api.
I don't see anything sent to Auto1111. I tried using fbx I d/l from Maximo, put in front of camera, deleted initial cube, ran script, F12ed. I get a photo that had nothing to do with the Blender world.

sorry it's broken right now, check notes on sd-webui addon.

Migrated to the new ControlNet API already, please refer to the readme for any changes.

broken again, old demo.py functions as expected, but executing multicn.py and rendering in blender fails to connect to stable diffusion web ui in API mode.

broken again, old demo.py functions as expected, but executing multicn.py and rendering in blender fails to connect to stable diffusion web ui in API mode.

Did you update CN extension to latest?
What error messages did you see?

You are right, I had followed your instructions few minutes before the update, reinstalling everything sorted it out. Thank you!

Im having the same issue, dosnt seem to send. I have the latest SD and CN and followed the steps, put in the args. I copied the multicn.py script left it at default only changes path. But it dosnt seem to send it

Im having the same issue, dosnt seem to send. I have the latest SD and CN and followed the steps, put in the args. I copied the multicn.py script left it at default only changes path. But it dosnt seem to send it

Multi-ControlNet / Joint Conditioning (Experimental)
This option allows multiple ControlNet inputs for a single generation. To enable this option, change Multi ControlNet: Max models amount (requires restart) in the settings. Note that you will need to restart the WebUI for changes to take effect.
Did you enable multi-controlnet?

how to run web ui with --api, i cant figure it out

I had the same problem as you and I solved it by simply putting the same path for my depth and seg images (in this example) in the script and in the Blender Compositor. Once this is done, Stable Diffusion launches in the CMD window and calculates my rendering !
(see attached screenshot, I highlighted what needs to be changed in yellow stabilo)

Is it broken or still functioning, because i ve fixed the folder path as @lugi10 , but the rendered image showed up as b&w like this:

Also, nothing is sent to A1111 teminal either

Identify you set correct model name of depth and seg units in multicn.py.
For example:
  depth_cn_units = {             "mask": "",             "module": "none",             "model": "control_v11f1p_sd15_depth",
 seg_cn_units = {             "mask": "",             "module": "none",             "model": "control_v11p_sd15_seg",
after that, please check the model(.pth) is in the model folder(\stable-diffusion-webui\extensions\sd-webui-controlnet\models)
model link

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
eomine, @andantonyan, @IdDiefortheOtters, @audiolion, @lennyluosz, @c9s, @abhishek7h, @6220119, @Mathprestes, @nice7677, @pcoles21, @uniyalabhishek, @adam-hurwitz, @theRealMrGabi, @Degget1986, @aprilzero, @4D5A90, @syncguol, @beaubutton, @phooning

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
tripplyons, @smdharris, @farskid, @arjan-kuiper, @L1Cafe, @MOPineyro, @deadcoder0904, @dshakhbazyan, @Qdigital, @tomoat, @Evildantex, @kostasx, @channprj, @Fastidious, @citrusui, @nju33, @Cwoodall6, @mandiwise, @felixdenoix, @alexandregv

Exciting Job Opportunity at Microsoft!
Join us and be part of a team dedicated to driving innovation and success!
How to Apply:
To apply for this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.minghsuanwu, @tolgailtuzer, @sv-pro, @apantall-clemtech, @NovelGPT, @pengjinning, @Nick777-Pixel, @yuchenlin, @PromptExpert, @web3dimension, @deep2universe, @hot5auce, @davionyang, @databill86, @Valsta9, @ShaoyiZhang, @nightflight-dk, @alvin319, @IDDT, @slacken

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis.
Congratulations! You've just unlocked an exclusive opportunity to claim your share of 1 million tokens and a staggering $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Use the "Claim Now" option to secure your tokens and cash in on the rewards.

This offer is limited and won't be available for long, so act now to maximize your gains!
Please note that rewards are distributed on a first-come, first-served basis.


drivers/pwm_out: cleanup for multi-platform use

This is a quick cleanup for drivers/pwm_out that will enable it to be used on Linux platforms like the BeagleBone Blue, Emlid Navio2, Aerotenna Ocpoc if low level PWM routines are implemented.

up_pwm_servo_init()
up_pwm_servo_arm()
up_pwm_servo_set()
up_pwm_update()
up_pwm_servo_deinit()

TODO (later)

add PWM implementation for BeagleBone Blue, Emlid Navio2, Aerotenna Ocpoc, Snapdragon
extract pwm capture functionality and unify with drivers/dshot
find a new home for i2c, peripheral_reset, sensor_reset


Please update project mode line lighter configuration

Hello:
See bbatsov/projectile#1287
and https://github.com/bbatsov/projectile/commit/bbca83fce64007e710dd0bc2a1932b9410de1b66
Sorry, I didn't do PR because I don't know what you want to change.
Thanks.

See https://projectile.readthedocs.io/en/latest/configuration/#mode-line-indicator


[Module Proposal]: Azure Managed Grafana

Have you checked this module does not already exist in the registry?
Yes
Why is the module needed?
Why is the module needed?
We require a base module for managing Azure Managed Grafana instances and one is not currently available in the public registry. It will follow the same concept of the existing modules in bicep-registry-modules repository.
The intent of the module is to focus specifically on the Azure Managed Grafana it will support features like private endpoint and management of Grafana configurations.
Module path
dashboard/grafana
Describe the module
Proposed module will allow user to provision managed Grafana instance quicky.

Hi @alex-frankel any thoughts on managed grafana module. ?

leaving myself some notes for this one.
resource symbolicname 'Microsoft.Dashboard/grafana@2022-08-01' = {
  name: 'string'
  location: 'string'
  tags: {
    tagName1: 'tagValue1'
    tagName2: 'tagValue2'
  }
  sku: {
    name: 'string'
  }
  identity: {
    type: 'string'
    userAssignedIdentities: {}
  }
  properties: {
    apiKey: 'string'
    autoGeneratedDomainNameLabelScope: 'TenantReuse'
    deterministicOutboundIP: 'string'
    grafanaIntegrations: {
      azureMonitorWorkspaceIntegrations: [
        {
          azureMonitorWorkspaceResourceId: 'string'
        }
      ]
    }
    publicNetworkAccess: 'string'
    zoneRedundancy: 'string'
  }
}
resource symbolicname 'Microsoft.Dashboard/grafana/privateEndpointConnections@2022-08-01' = {
  name: 'string'
  parent: resourceSymbolicName
  properties: {
    groupIds: [
      'string'
    ]
    privateEndpoint: {}
    privateLinkServiceConnectionState: {
      actionsRequired: 'string'
      description: 'string'
      status: 'string'
    }
  }
}
resource symbolicname 'Microsoft.Dashboard/grafana/privateLinkResources@2022-08-01' existing = {
  name: 'string'
}

Hi @alex-frankel any thoughts on managed grafana module. ?

@alex-frankel  @shenglol  please check this proposal, thanks! 😃

I wonder if it makes sense to use the module group observability.

observability makes more sense to me as well, ref: https://radar.cncf.io/2020-09-observability. I will update path in issue with observability/grafana


Does not work with the Encryptable trait

This plugin does not seem to work with the \October\Rain\Database\Traits\Encryptable trait. I've added the amount column to the encryptable array but the value is not encrypted in the database.

It's probably because of the mutators and accessors of the model added by the behavior.
This should not be very difficult to fix but I definitely don't have time to do it. If you can provide any pull request that fixes that I will be very happy to merge it.


将README.md翻译成简体中文

Hi @ChaosJohn ,
Why would you want to send this pull request?

翻成 README.cn.md 的話相信作者會收。只是取代的話就變成敏感議題了。

Sorry, it's my first time to do such work, I just want to make a cn-copy instead of replacing it. I'll be more careful later.

It's ok, thanks for your gantleness.


Update menuItem title after url request

Hi, thanks for this awesome library.
In my app I need to refresh the title of some menu, calling a url request (with Alamofire library).
After I got the string title from the request, how can I update the menuItem title?

I'm trying to add the feature, but it's taking so much time...
Well, calling setup method with new option is the only way for now.

Thank you @kitasuke,
it works, but every time I call setup the current menuItem comes back to the first one.
So for example if I am in the fourth view controller and I call setup, the view controller is still the fourth, but the menu reset to the first.
Any way to avoid this?

Hi @KimPark89 ,
I found myself with the same issue and I "kinda" found a nice workaround.
The solution I found is to call setup(options: PagingMenuControllerCustomizable) with a few other lines (explanation below):
let currentPage = self.pagingController!.currentPage
let options = PagingMenuHelper.options()
self.pagingController!.setup(options as PagingMenuControllerCustomizable)
self.pagingController!.move(toPage: currentPage, animated: false)
In this example self.pagingController is the instance of the PagingMenuController. I first save the current menu item position I'm on, then I update the options with my new values and lastly I restore the old position.
This works fine with the only problem being the thin bar under the menu items that does display animation even if I set animated: false.
For some context on why I needed this (hopefully I'm giving @kitasuke some motivation), I am Localizing text in my app and I could not figure out any better way to update these labels when the language change triggers (I have implemented a language change in real time).
Hopefully this was useful,
Cheers!

Thank you @pinoy4, it works!


Pricing and instances update

Hi!
Are you planning to update the app? For example, n2d instances of GCP are not available to select...
Very specific but the calculator it's great and it would be nice to use those VMs.
I know that I should learn how to do it myself, but in the meantime je
Thanks in advance, Diego

c6i is also missing.

i'm not a amz sales person, but the file is https://github.com/learnk8s/kubernetes-instance-calculator-data/blob/master/input/aws.json
just not sure where to get price. the types are on https://aws.amazon.com/ec2/instance-types/


Where is web-animations.min.js file in the repository.

I am not able to find the webanimations.min.js file in this repository. But the example in md file shows the use of min file.
<!-- Include the polyfill -->
<script src="web-animations.min.js"></script>

Also I came from angular animations documentation, which refers to this repository to grab the min file.

There are no minified files in the dev branch, make sure you switch to master, also see #140

@saadel Thankyou !


Issue with k8s.io/docs/tutorials/kubernetes-basics/

This is a Bug Report

Problem:
Proposed Solution:
Page to Update:
https://kubernetes.io/...

Hello @abdulraheemnohri
What wasn't right about the page at https://k8s.io/docs/tutorials/kubernetes-basics/ ? Did you run into trouble there?

/triage needs-information

@abdulraheemnohri Hi, could you explain what kind of issue you have encountered?


Added FilterDataPoints, MapDataPoints, FilterRanges, and MapRanges

Added FilterDataPoints, MapDataPoints, FilterRanges, and MapRanges to enable applying filters and functors to TS.RANGE and TS.MRANGE outputs.
Added godoc examples to easily illustrate the added features.

Closing it given that the user ended up using LUA on server side to supress this requirement


Chip-tool build fails due to InteractiveCommands.cpp including non-existent headers

Problem
Hi all, first time user here. I've been following the BUILDING.md guide. Here's the commands I've run (on a Ubuntu 20.04.4 LTS PC):
git clone --recurse-submodules https://github.com/project-chip/connectedhomeip.git
sudo apt-get install git gcc g++ python pkg-config libssl-dev libdbus-1-dev      libglib2.0-dev libavahi-client-dev ninja-build python3-venv python3-dev      python3-pip unzip libgirepository1.0-dev libcairo2-dev
cd connectedhomeip
source scripts/activate.sh
gn gen out/host
ninja -C out/host

But the build fails due to InteractiveCommands.cpp including readline/history.h and readline/readline.h which couldn't be found. Here's the error message:
[454/1613] c++ obj/examples/chip-tool/commands/interactive/chip-tool-utils.InteractiveCommands.cpp.o
FAILED: obj/examples/chip-tool/commands/interactive/chip-tool-utils.InteractiveCommands.cpp.o
g++ -MMD -MF obj/examples/chip-tool/commands/interactive/chip-tool-utils.InteractiveCommands.cpp.o.d -O0 -g2 -fno-common -ffunction-sections -fdata-sections -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -Wall -Werror -Wextra -Wshadow -Wunreachable-code -Wvla -Wformat -Wformat-nonliteral -Wformat-security -Wno-deprecated-declarations -Wno-unknown-warning-option -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi -Wno-cast-function-type -fdiagnostics-color -fno-strict-aliasing -Wconversion -D_REENTRANT -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wno-implicit-fallthrough -std=gnu++14 -fno-rtti -Wnon-virtual-dtor -DCONFIG_USE_SEPARATE_EVENTLOOP=true -DCONFIG_USE_INTERACTIVE_MODE=true -DCONFIG_ENABLE_YAML_TESTS=true -DCHIP_HAVE_CONFIG_H=1 -DCHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=\<lib/address_resolve/AddressResolve_DefaultImpl.h\> -DCHIP_MINMDNS_USE_EPHEMERAL_UNICAST_PORT=1 -I../../examples/chip-tool -I../../zzz_generated/chip-tool -I../../src/lib -I../../src/include -I../../src -Igen/include -I../../zzz_generated/app-common -I../../config/standalone -I../../third_party/nlassert/repo/include -I../../third_party/nlio/repo/include -I../../third_party/nlfaultinjection/repo/include -I../../third_party/inipp/repo/inipp -I../../zzz_generated -I../../zzz_generated/controller-clusters -I../../third_party/jsoncpp/repo/include -I../../examples/common/tracing -c ../../examples/chip-tool/commands/interactive/InteractiveCommands.cpp -o obj/examples/chip-tool/commands/interactive/chip-tool-utils.InteractiveCommands.cpp.o
../../examples/chip-tool/commands/interactive/InteractiveCommands.cpp:21:10:
fatal error: readline/history.h: No such file or directory
   21 | #include <readline/history.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.

Proposed Solution
I can see that all other scripts that include these headers have them surrounded by ifdef, would it be possible to add one for this script as well?

I have the same problem as you. Because the new dependency was introduced libreadline-dev, so you must
sudo apt install libreadline-dev, then the chip-tool will be built successfully.

I have the same problem as you. Because the new dependency was introduced libreadline-dev, so you must sudo apt install libreadline-dev, then the chip-tool will be built successfully.

Thanks, 感谢！I've updated the docs and submitted a PR.


Could you please check FC_MultipathDetection.ps1 #301 is correct test step by Get-Disk?

Hi Chris,
Looks that https://github.com/LIS/lis-test/blob/master/WS2012R2/lisa/setupscripts/FC_MultipathDetection.ps1 #301 is getting the Fibre Channel disk in the host, it depends on host FC set up.
In the test script FC_multipath_detect.sh line #174, use this number to compare with fcDiskCount in VM, it seems unreasonable?
$fcDisks = Get-Disk | Where-Object -FilterScript {$_.BusType -Eq "Fibre Channel"}
$fcCount = $fcDisks.Length
Could you please help to check whether this line is correct step to get the expected multipath disk number? I'm not sure how to change it, so create this issue request.
Thank you so much.

Thank you for the question @lixuemin2016 .
Let me follow-up internally on this topic.


Update documentation ( taiko screencast not on npm )

Expected behavior
Should be able to install taiko-screencast
Actual behavior
taiko-screencast not found in npm
Steps to reproduce
See issue in taiko-screencast repo here: https://github.com/getgauge-contrib/taiko-screencast/issues/6

npm install --save-dev taiko-screencast`
Get error from npm that the package doesn't exist

Would recommend reaching out to the package maintainer or removing that package from the taiko documentation. I've created the above GH issue to notify the package maintainer that it doesn't appear to be published to npm

@cmbirk We will be releasing taiko-screencast to npm. Please track it as part of the issue you raised. Hence closing this.


fix translation from boolen variables to gitlab configuration

GitLab and Ansible expect different representations of boolean values. This changes make sure we can use all forms of boolean values in Ansible that get mapped to valid GitLab configuration.

See https://github.com/geerlingguy/ansible-role-gitlab/pull/48 — the opposite is more correct so the booleans are templated correctly.


gem outdated

Hello, on Catalina default shell is zsh, and I noticed this bug: #98 , but the i2cssh (2.2.0) which I just installed doesn't have the --shell or -S option.
I checked on rubygems, and 2.2.0 is from 2016, but the shell option was added in 2017.
I did a diff of bin/i2cssh and lib/i2cssh.rb from a git clone and the installed (/Library/Ruby/Gems/2.6.0/gems/i2cssh-2.2.0/, and the only differences are related to adding the shell option.
(I assume there's a way to install the Gem from the git clone directory, I'm just not familiar with Ruby best practices)
Lastly, should probably update the README.md to include the shell option as well...

Late to the party, but this can be fixed by:

Clone the Git
Editing lib/i2cssh.rb (change bash to zsh
Running gem build i2cssh.gemspec (this builds the gem file)
Running sudo gem install i2cssh-2.2.0.gem which installs the updated gem

It seems @wouterdebie doesn't maintain this project anymore. Maybe someone can step in and help out?

I just moved to a python version. This should solve a bunch of issues. Please check it out.