Subclass method is not allowed (TS2425) if the parent class has a property of type any with the same name

TypeScript appears to treat class methods as something fundamentally different from a class prototype property of type function. This is not in agreement with the standard semantics of ES6.

TypeScript Version:  all versions, as far as I have been able to test.

Search Terms: method member property any parent class subclass
Code
class Super {
    prop: any;
}

class Derived extends Super {
    prop() {}
}

Expected behavior: should compile without a problem. Note that by the ES6 standard, the above definition of Derived is equivalent to the following, which TypeScript compiles without a problem:
class Derived extends Super {}

Derived.prototype.prop = function(){};

Actual behavior:
Error TS2425: Class 'Super' defines instance member property 'prop', but extended class 'Derived' defines it as instance member function.

Playground Link: https://www.typescriptlang.org/play/#src=class Super {
    prop%3A any%3B
}

class Derived extends Super {
    prop() {}
}

Related Issues: I didn't find similar issues, although I started by looking for issues requesting for the ability to disable particular errors (TS2425 in this case). There are several (closed) issues in which such an ability is requested or suggested, but I believe the proper solution would be to bring TypeScript in agreement with ES6. After all, it claims to be a superset!

The problem here is that prop(){} defined as method is placed on the prototype. prop: any as property is written directly to the instance (if it had an initializer) and thus overrides the prototype method.
Consider the following slightly modified version of your code:
class Super {
    prop: any = undefined;
}

class Derived extends Super {
    prop() {}
}

new Derived().prop(); // runtime error: undefined is not a function

You can still use a function to initialize prop in Derived:
class Super {
    prop: any = undefined;
}

class Derived extends Super {
    prop = () => {}
}

new Derived().prop(); // works as expected

Thanks @ajafff, I didn't think of that. The reason I'm running into this is not resolved yet, though. A common pattern in the JavaScript world is to allow an object property to either be of type A or a bound method of type () => A. Underscore's and Lodash's _.result is specifically meant to cater to this scenario. However, there seems to be no way in TypeScript to express such a typing:
// first attempt

class Super {
    prop: any;
}

class Derived extends Super {
    prop() {}
}

// problem as above

// second attempt

class Super {
    prop() { return {}; };
}

class Derived extends Super {
    prop = {};
}

// Property 'prop' in type 'Derived' is not assignable to the same property in base type 'Super'.
//    Type '{}' is not assingable to type '() => {}'.
//      Type '{}' provides no match for the signature '(): {}'.

There may be a way I'm not aware of (I hope there is), but otherwise, I'd argue TypeScript is missing something.

What is Super doing here? Do you mean to have an interface instead?

My specific situation is as follows:
// a library not originally written in TypeScript

class Super {
    prop() {  // meant to be overriden either with {} or () => {}
        return {};
    }
}

// somebody else's @types/library/index.d.ts

declare class Super {
    prop(): {};  // doesn't cover all cases
    prop: any;   // doesn't cover all cases either
}

// my code

class Derived extends Super {
    // If I want to override prop in a way not supported by the typings, I have a problem.
}

But it also applies if the library were written in TypeScript in the first place.

After all, it claims to be a superset!

This does not mean "all syntactically-legal ES6 code must not have type errors"; see https://stackoverflow.com/questions/41750390/what-does-all-legal-javascript-is-legal-typescript-mean
This has come up in the past but the specific scenario of "this method may be overriden by a property of a different type" hasn't come up often enough to warrant a solution

This does not mean "all syntactically-legal ES6 code must not have type errors"; see https://stackoverflow.com/questions/41750390/what-does-all-legal-javascript-is-legal-typescript-mean

Fair point. I started this ticket with different assumptions, so the opening post and the title probably don't accurately reflect anymore what this issue is really about.
I'm not meaning to imply that TypeScript should just accept the example code I presented. Rather, the problem is that there seems to be no alternative. Semantically, it is a valid and even meaningful construction in JavaScript to override a base class method with a subclass non-function prototype property or vice versa. This is especially the case if the return type of the method is the same as the type of the non-function. To me, this seems like a scenario that could be type-checked, but again, there seems no way to do this in TypeScript.
If it hasn't come up often, then apparently not many Backbone users work with TypeScript. In Backbone, _.result is used all over the place. You may be able to gain some ground there!

Got the same when using :
class Super{
  test = function (){}
}

class Delivered extends Super {
  test() {}
}

For completeness (and people seeking help with TS2425 errors), you can always use type merging to "tell" TS that the member shall be seen as method.
The examples above for instance can be solved like this:
interface Super {
    test?(): void;
}

class Super{
  test = function (){} // test may also be undefined, it's optional on the interface
}

class Delivered extends Super {
  test() {}
}

Unfortunately, that doesn't work well:
interface Super {
    test?: boolean | (() => boolean) // ERROR, All declarations of 'test' must have identical modifiers. (2687)
}

class Super{
  protected test // ERROR, All declarations of 'test' must have identical modifiers. (2687)
}

class Delivered extends Super { // ERROR, Property 'test' is protected in type 'Delivered' but public in type 'Super'. (2415)
  protected test = true
}

playground
This is a pattern I've seen in base classes before.
For example, here is a more representative example of what a base class would want to do:
import * as React from 'react' // this is only for JSX types, but we're not using React in the following example...

type Template = Element | (() => Element)

interface Super {
	template?: Template
}

class Super extends HTMLElement {
	// Subclasses can optionally provide this, writing JSX to create a DOM tree.
	// BUT! Not all elements need to have their own Shadow DOM tree, so they don't have to define this.
	protected template

	connectedCallback() {
		const tmpl = this.template
		if (tmpl) this.render(typeof tmpl === 'function' ? tmpl : () => tmpl, this)
	}

	private render(template: () => Element, ctx: this) {
		this.attachShadow({ mode: 'open' })
		this.shadowRoot!.append(template.call(this))
	}
}

// This element has a simple static Shadow DOM, written with concise syntax.
class SomeElement extends Super {
	protected template = div(
This should work.
)
}

customElements.define('some-element', SomeElement)

// This element needs no inner Shadow DOM.
class OtherElement extends Super {
	connectedCallback() {
		super.connectedCallback()
		// ...does something special, without needing a `template`...
	}
}

customElements.define('other-element', OtherElement)

// This element make a local reactive variable (state) to render in its DOM.
class AnotherElement extends Super {
	count = reactiveVar(0)

	protected template() { // <------- ERROR 2425 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
		setInterval(() => this.count.set(this.count.get() + 1), 1000)

		return div(
This should work too. The count is {this.count.get()}
) // updates the DOM every second.
	}
}

customElements.define('another-element', AnotherElement)

declare function reactiveVar<T>(initialValue: T): { get(): T; set(val: T): T }

// This is simple a no-op identity function, to type cast JSX.Element to a DOM type. Hopefully
declare function div(j: JSX.Element): HTMLDivElement

Now strip all the type from that example, and you'll see that it is valid and well-functioning JavaScript.

Some people mention that we can just use an arrow function, like
class Derived extends Super {
    prop = () => {}
}

but this is not ideal because

it is wasteful to create one new function per instance, instead of sharing a single prototype function.
it does not work with inheritance (we can not use super in an arrow function to call the same function of a super class).

@RyanCavanaugh Can we perhaps have a way to allow this, under the condition that the super class does not have an initializer? It seems that a super class having an initializer is the foot gun that the restriction is trying to prevent.
So, what if
class Super {
    prop?: boolean | (() => boolean)
}

class Derived extends Super {
    prop = true
}

class Derived2 extends Super {
    prop() { return true }
}

is ok with no type error, and
class Super {
    prop?: boolean | (() => boolean) = false
}

class Derived extends Super {
    prop = true
}

class Derived2 extends Super {
    prop() { return true }
}

has a type error that says something like "The Super base class prop property has an initializer, therefore the the subclass Derived2 can not override prop with a prototype method."
I think allowing this under certain conditions would be great!

I have an example here
type Constructor<T> = new (...args: any[]) => T

interface Mergeable {
  merge: (
    obj: any,
    omit: string[]
  ) => void;
}

function Orderable<T extends Constructor<Mergeable>>(Class: T) {
  return class OrderableClass extends Class {
    merge(obj, omit: string[] = []) { // Error here
      return super.merge(obj, [...omit, 'before', 'after'])
    }
  }
}

Class 'Mergeable' defines instance member property 'merge', but extended class 'OrderableClass' defines it as instance member function.(TS2425)
I know the difference between class prototype function and class property. But in as in https://github.com/microsoft/TypeScript/pull/18654 says they should behave different in strict mode.

I came across this error when I wanted subclasses to be able to signal that the method does not exist by setting it to null.
What I want to be able to do
interface A {
  // if a subclass wants they can set this method to null
  foo: null | (() => number); // property foo was also declared here
}

class A {
  foo(): number { return 1; } // duplicate property
}

class B extends A {}

B.prototype.foo = null;

I can however change the definition for class A to:
class A {}
A.prototype.foo = () => 1;
// no problem - just as the first comment in this issue found

But since this is valid typescript I would have assumed the first version was also valid...
I can see how it's not. I guess it's because prototype is itself an instance of type A and so assigning foo to be a function is like defining an instance member property. Typescript considers it different to defining an instance member function inside the class body, even though it all ends up on the prototype anyway.
It would be nice if my original code worked, I don't mind the workaround but I don't love it.
Note the opposite is also problematic
interface A {
  // if a subclass wants they can set this method to null
  foo: null | (() => number); // property foo was also declared here
}

class A {}
A.prototype.foo = null;

class B extends A {
    foo(): number { return 1; }
    // class A defines an instance member property but extended class B defines it as an instance member function
}
// B.prototype.foo = () => 1 // no problems

(I also want to avoid defining functions that end up on the instance and would prefer to keep them on the prototype).

I don't know who came up with this first, but TS and ESnext basically share the same critical mistake to consider a "class field"
class A {
    prop = 'abc';
}

equivalent to a constructor initializer
function A() {
    this.prop = 'abc';
}

instead of a default property on the prototype.
function A() {}
A.prototype.prop = 'abc';

Besides the fact that this is inconsistent with member functions (which are set on the prototype), this causes all kinds of nasty problems. For example, you can't override a parent "class field" by setting a derived class prototype property.
class Base {
    prop = 'abc';
}

class Derived {}
Derived.prototype.prop = 'def';

const d = new Derived();
d.prop; // 'abc'

If "class fields" were prototype properties instead, there wouldn't be any problem of this kind (below, I'm avoiding class field syntax in order to avoid confusion).
class Base {}
Base.prototype.prop = 'abc';

class Derived1 {}
Derived1.prototype.prop = 'def';

class Derived2() {
    constructor() {
        this.prop = 'ghi';
    }
}

(new Derived1()).prop; // 'def'
(new Derived2()).prop; // 'ghi'

I think that the current issue ticket is a symptom of this problem being reflected in the TS type system.
At first I thought that adding type checking to JS was a neat idea, but every time I ran into a problem like this (i.e., the TS type system being too incomplete to accurately reflect what's going on in JS), I became more convinced that a dynamically typed language simply isn't meant to have static type checking. Either you create a language that is actually statically typed and you can do all the type checking you want (cf. C++), or you create a dynamically typed language, enjoy the added flexibility and accept that you can only do runtime checks. Not to mention the lack of accurate typings for third-party libraries. Type checking isn't going very well in Python, either.
I'm switching back to CoffeeScript, which has sane "class fields". This is an important reason for me to switch back, perhaps even the most important.

I don't know who came up with this first, but TS and ESnext basically share the same critical mistake to consider a "class field"
class A {
    prop = 'abc';
}

equivalent to a constructor initializer
function A() {
    this.prop = 'abc';
}

instead of a default property on the prototype.
function A() {}
A.prototype.prop = 'abc';

I would argue that if you need a value to be the shared between every instance you should not allow yourself to use it with the same syntax that you'd access a member variable, because it may get confusing.
You can use the specifier static if you want to add a member to the constructor itself.

Besides the fact that this is inconsistent with member functions (which are set on the prototype), this causes all kinds of nasty problems. For example, you can't override a parent "class field" by setting a derived class prototype property.
class Base {
    prop = 'abc';
}

class Derived {}
Derived.prototype.prop = 'def';

const d = new Derived();
d.prop; // 'abc'

Member functions are what prototypes are for, so that you can have a member invocation syntax on your function while implicitly passing the this  argument. There is a clear difference in syntax in the way you declare a member and a property in Typescript/ES class, so a different behavior may be expected. If you want a function as a property you have the prop = function() { } syntax that you can use

If "class fields" were prototype properties instead, there wouldn't be any problem of this kind (below, I'm avoiding class field syntax in order to avoid confusion).
class Base {}
Base.prototype.prop = 'abc';

class Derived1 {}
Derived1.prototype.prop = 'def';

class Derived2() {
    constructor() {
        this.prop = 'ghi';
    }
}

(new Derived1()).prop; // 'def'
(new Derived2()).prop; // 'ghi'

I think that the current issue ticket is a symptom of this problem being reflected in the TS type system.
At first I thought that adding type checking to JS was a neat idea, but every time I ran into a problem like this (i.e., the TS type system being too incomplete to accurately reflect what's going on in JS), I became more convinced that a dynamically typed language simply isn't meant to have static type checking. Either you create a language that is actually statically typed and you can do all the type checking you want (cf. C++), or you create a dynamically typed language, enjoy the added flexibility and accept that you can only do runtime checks. Not to mention the lack of accurate typings for third-party libraries. Type checking isn't going very well in Python, either.

This rant of yours is a bit unfair. TS type system is one of the most expressive (and complex) type system around, and can express most of the shenanigans that people have done so far with Javascript, because it has been designed with the intention to retroactively add typings to existing libraries. Even this particular case is an example of Typescript semantic actually expressing correctly what happens with ES classes (to be fair ES classes were inspired and modelled after Typescript classes so there is some blame in Typescript if they don't appeal to your liking).
As for "there is no use in do statical type check in a dynamic language" I'd argue that there is instead, and it's static analysis which can help reducing bugs: although Javascript is a dynamic language I'd argue that 99% of Javascript code should not use dynamic features and should be statically typable, in order to be "safer".
As for those awesome Javascript tricks that you can do since it is actually a dynamic language, they shouldn't cover more than 1% of all the Javascript code. And typescript provides you with escape hatches from the "safe" static types like the any type, so that you can write that 1% of magic dynamic code, add a warning for reviewers that they need to pay special attention to that part, then go back to the safety and happiness of a statically typed language.

I'm switching back to CoffeeScript, which has sane "class fields". This is an important reason for me to switch back, perhaps even the most important.

If adding non-function properties to a prototype is something that happens often in your ordinary workload it is a good idea to use a language that allows for that to be expressed easily. I have no experience with CoffeeScript, so I can't advise for or against it.

Hey @pqnet, thank you for taking the time to respond to my post.

I would argue that if you need a value to be the shared between every instance you should not allow yourself to use it with the same syntax that you'd access a member variable, because it may get confusing. You can use the specifier static if you want to add a member to the constructor itself.

I might agree with this way of thinking for a static language like C++ or C#, but not for a dynamic language like JavaScript or Python. In dynamic languages, there is no danger in "confusion" because properties on the prototype (or "attributes" on the class in Python) are intended as a transparent fallback value. Alternatively, you could say that programmers are encouraged to "confuse" between instance and prototype properties; the language feature was introduced specifically to facilitate this.
The very idea is that you do not need to distinguish between an instance property and a prototype property. Reading the property on the instance, you do not need to be aware of the difference. Writing the property on the instance, you do not need to worry, because the property on the prototype will never be affected.

Member functions are what prototypes are for, so that you can have a member invocation syntax on your function while implicitly passing the this argument.

You write this as if meaning to imply that non-function members are not "what prototypes are for". I beg to differ; I think the creators of JavaScript added the option to define non-function prototype properties because they wanted them to be used. Indeed, they are almost universally used in JavaScript projects, and I think the use is valid in a large majority of cases.
It seems that the aim of the TS project is to instill an opinion on what language features of JS should and shouldn't be used. Is it an official standpoint that prototypes should have only function members? In any case, while I see the added value of type checking, I never asked for a language that changes the semantics of JavaScript.

There is a clear difference in syntax in the way you declare a member and a property in Typescript/ES class, so a different behavior may be expected.

If you mean that the assignment notation for class fields is consistent with its semantics, then I somewhat agree. In C++ (and I guess C# and Java as well), the same notation is used to set a default value for an instance property, too:
class Example {
    int property = 0;
};

However, these languages have no equivalent of prototype properties, so there is no other plausible meaning for the notation, unlike in JavaScript.
In JavaScript, if class fields had the semantic of setting prototype properties, perhaps we would expect a colon notation instead, analogous to object literal notation:
class Example {
    property: 0;
}

However, that notation is obviously unavailable for TypeScript, as it conflicts with type annotation syntax.
What really gripes me, is that a notation was invented for something that already had a convenient notation:
class Example {
    constructor() {
        this.property = 0;
    }
}

Thus leaving no obvious candidate for something that did not have a convenient notation yet:
class Example {}

Example.prototype.property = 0;

Contrast this with CoffeeScript, which has both colon notation and assignment notation inside class bodies, using both notations in consistent ways that add real value. Colon notation is used both for function and non-function prototype properties:
class Example
    property: 0
    method: -> return this.property

If you want to set an instance property in the constructor, you can, just like in JavaScript:
class Example
    constructor: ->
        this.property = 0

Assignment notation at class body scope is used for a purpose that does not exist in languages like C++, i.e., to store variables that can be used in logic that runs at class definition during runtime (in C++ you can run logic during class definition, too, but it happens during compile time and it requires different notation). Here is a slightly advanced example of how that may be used for metaprogramming purposes:
import { encoding } from './config.coffee'

class Example
    utf8method = -> ### imagine lots of code ###
    utf16method = -> ### lots of different code ###
    method: if encoding is 'utf8' then utf8method else utf16method

At first I thought that adding type checking to JS was a neat idea, but every time I ran into a problem like this (i.e., the TS type system being too incomplete to accurately reflect what's going on in JS), I became more convinced that a dynamically typed language simply isn't meant to have static type checking. Either you create a language that is actually statically typed and you can do all the type checking you want (cf. C++), or you create a dynamically typed language, enjoy the added flexibility and accept that you can only do runtime checks. Not to mention the lack of accurate typings for third-party libraries. Type checking isn't going very well in Python, either.

This rant of yours is a bit unfair.

I think I'm just stating a tradeoff. Surely you agree there is a tradeoff between static and dynamic typing? I just think that TypeScript is making a compromise, which ends up not working very well.

TS type system is one of the most expressive (and complex) type system around,

I will agree with that,

and can express most of the shenanigans that people have done so far with Javascript,

but I would like to nuance this. I think that 90% of normal JavaScript can be straightforwardly typed using TS annotations. Another 9% can be typed, but requires complex annotations or advanced techniques, which tend to be highly intimidating for beginners. The remaining 1% cannot be typed at all. Given the size of modern JavaScript projects, we end up hitting the undesirable 10% all the time.

because it has been designed with the intention to retroactively add typings to existing libraries.

This is how TS sometimes advertises itself, but it is not the whole story. From the way maintainers and proponents (including you) defend the ways in which TS departs from regular JS semantics, it is clear that another intention is to enforce a particular opinion about how JS should be used. Remarks like "that something is allowed does not mean you should do it" and your "prototypes are meant for member functions". The opinion of the TS compiler, and it proponents, appears to be that JavaScript code should be written like C# code, even though C# is static and class-based while JavaScript is dynamic and prototype-based.

Even this particular case is an example of Typescript semantic actually expressing correctly what happens with ES classes (to be fair ES classes were inspired and modelled after Typescript classes so there is some blame in Typescript if they don't appeal to your liking).

Exactly. I think it is madness that ES went along with it.

As for "there is no use in do statical type check in a dynamic language"

Note that this is not what I wrote. I think there is a use in principle, but it's simply not possible to do it in a way that is comprehensive, correct and convenient at the same time.

I'd argue that there is instead, and it's static analysis which can help reducing bugs: although Javascript is a dynamic language I'd argue that 99% of Javascript code should not use dynamic features and should be statically typable, in order to be "safer". As for those awesome Javascript tricks that you can do since it is actually a dynamic language, they shouldn't cover more than 1% of all the Javascript code.

Here you are making claims about what should and should not be done in JavaScript, confirming what I wrote above.
Dynamic typing makes the programming language more powerful. Expressive power makes programmers more productive. I'm in favour of consistency and I'm open to discussions about situations in which dynamic construct are better avoided, but I don't think a compiler for a dynamic programming language should be ruling out entire domains of dynamic semantics. The syntax of the language itself (i.e., ES) even less so!

And typescript provides you with escape hatches from the "safe" static types like the any type, so that you can write that 1% of magic dynamic code, add a warning for reviewers that they need to pay special attention to that part, then go back to the safety and happiness of a statically typed language.

I agree the escape hatch is there, but you need it a lot in order to avoid all the problems with TS. Even static types are often problematic.

If adding non-function properties to a prototype is something that happens often in your ordinary workload it is a good idea to use a language that allows for that to be expressed easily.

Right.

@RyanCavanaugh
Interface implementation is public, mostly we would want protected members, take a look at following.
   class BaseClass {

        protected init: (... args: any[]) => any;

        constructor() {
             // child classes can initialize members
             // before executing further statements...
             this.init?.(... arguments);
        }
   }

class DerivedInstanceProperty {
	protected init = () => {
		this.a = "1";
		this.b = "2";
	}
}

class DerivedMethod {
        // @ts-ignore
	protected init() {
		this.a = "1";
		this.b = "2";
	}
}

This code ensures that init does not popup on intellisense.
Performance
https://jsfiddle.net/qkcatm81/
Instance Member is 60% slower compared to Prototype Method. So argument of using instance member goes against performance.
Current workaround for using // @ts-ignore is an extra step, which might hide an important error by hiding wrongly typed parameteres or any other error.

@ackava it seems like you're looking for
      declare protected init: (... args: any[]) => any;

Dirty Workaround

class Super {
    prop() {
    }
}

// this will remove `prop` from existence
// howerver derived class can still override it
// without typescript warning
delete Super.prototype.prop;

class Derived extends Super {
    prop() {}
}

 class MyMaths {
 }

  class Maths {
  }

 /** Define for a custom add function
   * @function
   * @param {number} a
   * @param {number} b
   * @returns {number} */
  Maths .prototype.add=undefined;

In case this is useful for anyone else, this work-around gives me error free "ts-checking" with vanilla javascript.
The core need is to allow a derived class to optionally define a function.
I use this pattern frequently as part of an opt-in event/callback system pushing the details of event registration/de-registration into the base class.
class Motor extends Events {
  onSunrise(a) {
    turnOnMotor();
  }
}

class Events {
   constructor() {
     if( this.onSunrise ) addSunriseListener(this.onSunrise.bind(this));
   }
  dispose() {
     if( this.onSunrise ) delSunriseListener();
  }
}

/** Define to receive a callback
 * @function
 * @param {Date} time time of sunrise
 */
 Events.prototype.onSunrise=undefined;


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:18: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:24: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:44: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:44: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:44: missing_description: The recipe is missing a description
ERROR: /tmp/abs_c54zl4ob10/clone/recipe/meta.yaml:44: missing_dev_url: The recipe is missing a dev_url
Errors were found


MM-T400 Create account from login page link using email-password

Summary
This test ensures that signing up with email verification set to true works.
Test case: https://automation-test-cases.vercel.app/test/MM-T400

/update-branch


Favicon and branding

Incorporate new favicons
images are here - https://drive.google.com/drive/folders/1-JRJAHIBLL2sPwRmeS5AZJ2BN48fvfa5?usp=sharing

Size
Name
Purpose

32×32
favicon-32.png
Standard for most desktop browsers

128×128
favicon-128.png
Chrome Web Store icon & Small Windows 8 Star Screen Icon*

152×152
favicon-152.png
iPad touch icon (Change for iOS 7: up from 144×144)

167×167
favicon-167.png
iPad Retina touch icon (change for iOS 10: up from 152×152, not in action. iOS 10 will use 152×152)

180×180
favicon-180.png
iPhone Retina

192×192
favicon-192.png
Google Developer Web App Manifest Recommendation

196×196
favicon-196.png
Chrome for Android home screen icon

this is from https://www.emergeinteractive.com/insights/detail/The-Essentials-of-FavIcons/ (features a Photoshop Action you can use to generate these images)

Supplement that article with the information from https://stackoverflow.com/a/48969053 and https://stackoverflow.com/a/49460333
Include Twitter card and Facebook OG tags

Notes for ICO format favicon - https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/samples/gg491740(v=vs.85)?redirectedfrom=MSDN#site-icons-in-internet-explorer-9


Odd versioning with linux and mac package

Expected behavior
0.10.5 Release installs version 0.10.5
Actual behavior
When installed on a mac, the app reports version 0.10.4 and Ubuntu 0.10.5 "deb" (actually a zip) contains a 0.10.4 installer deb.

@DuckThom there was some missed version updates. A new release will be made early next week, which should amend those mistakes.
Thanks for the issue.


Docs: refine new quick start for producing and consuming messages in CLI

Notes for reviewers:

An HTML preview of the quick start content is available for review here.
I also did a preview build of the quick start to verify that it appears and behaves as expected in the console. All good there.

Hey! the link for the HTML preview is a dead link

Hey! the link for the HTML preview is a dead link

It just worked fine for me! Are you connected to VPN?

@bhardesty I had reason to get this PR merged, even with your review still open. Please review in your own time, and I'll address any feedback in a follow-up PR.


Projects owned by team are not unique

/v1/projects returns projects like:
{
  id: '1a24',
  type: 'project',
  externalIdType: 'project:github_team',
  externalId: 'dev'
}

Using a team as the owner of a project doesn't work right, because their names are only unique within an organization, not across them.  (e.g. both rancherio and rancherlabs have a team named "dev").
Need to store, accept and return team id (or org name + team name) instead.

@vincent99  and I decided to use teamIds instead of orgName + "/" + teamName. That way the Id is the consistent mode of representing github teams while communicating with cattle.
The input to cattle will be teamId and the output on creation and on listing will be teamId


remove dead link

Thanks for the pull request. Could you please replace the broken link by this one: http://www.json.org/ ?


encode and decode for "16k sample"

I need to use the model for encoding 16k WAV files. Only i need to resample the speech to 16k before encoding, and save the 16k WAV file after decoding the speech token?

I need to use the model for encoding 16k WAV files. Only i need to resample the speech to 16k before encoding, and save the 16k WAV file after decoding the speech token?

The input and output for the WavTokenizer are audio files sampled at 24 kHz. If your input audio is sampled at 16 kHz, it must be resampled to 24 kHz before being processed by the WavTokenizer. Similarly, if a 16 kHz output is required, simply resample the 24 kHz output audio back to 16 kHz.


Map Layout Creation

Description
Task: Map Layout Creation.
Feature: Map Design / Colour Palette
The concept design of the restaurant map and cooking station layout
#Dependencies

[ ] Map Asset Generation

Milestones

[ ] Rough design completed (Aug 18)

Completion Deadline: Aug. 20
Documentation

Main description of feature

Member

Alex (@amacn13) Alex Macnamara
Yarn(@danhdinh98)

Rough design completed and compared options. All documented here https://github.com/UQcsse3200/2024-studio-3/wiki/Map-Design


Meta: Release via dispatch

Fixes https://github.com/fregante/daily-version-action/issues/15
Considering that:

Updating a major tag (like v2) requires the tag deletion and recreation: https://github.com/fregante/daily-version-action/issues/15
There's no way to create a tag without a release on GitHub.com
release-with-changelog will fail if a Release exists: https://github.com/notlmn/release-with-changelog/issues/2#issuecomment-692248910

I moved the auto-changelog workflow to the workflow_dispatch method.

The range link was wrong as expected (v1..v1.2.1 instead of v1.2.0..v1.2.1), but in my private tests it seemed correct, so it probably depends on the order of tags. It can be disabled later if it actually doesn't work.

This is why I removed running this action on itself, because we'd be constantly re-pushing tags.

Also we should change range from v1..v2 to v1...v2 (notice the extra dot), which also displays the list of commits, the former one doesn't, which only shows diff.

Indeed that’s what’s happening. I was thinking we could just change the order of tags, but that doesn’t solve it. I’ll open another PR
Regarding the triple dot, I don’t think that changes the output log, it just changes the way diffs are computed (in some cases). GitHub only uses double dots

Regarding the triple dot, I don’t think that changes the output log, it just changes the way diffs are computed (in some cases). GitHub only uses double dots

/compare/v2...v3 (3 dots)
/compare/v2..v3 (2 dots)

Ah yeah, I confused the 2. Let’s use the 3 dot


break_contigs error 1

Greetings of the season.
Here is the history of my installation process.
conda create -n SALSA python=2.7 #Create the SALSA environment and install python 2.7

source activate SALSA  #Activate the SALSA environment

conda install boost networkx==1.11 #Install boost and networkx v1.1

cd SALSA-master #move to the SALSA-master folder

make  #compile the code

I got this message
g++ -O3 -Wall -Wextra -std=c++11 -o break_contigs break_contigs.cpp
cc1plus: error: unrecognized command line option "-std=c++11"
make: *** [Makefile:9: break_contigs] Error 1

Due to this line
 cc1plus: error: unrecognized command line option "-std=c++11",
I checked the version of my g++ by typing
g++ --version.
I got the message
g++ (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I updated the compiler by typing:
conda install -c anaconda gcc_linux-64==5.4.0

I compiled again but I got the same message
g++ -O3 -Wall -Wextra -std=c++11 -o break_contigs break_contigs.cpp
cc1plus: error: unrecognized command line option "-std=c++11"
make: *** [Makefile:9: break_contigs] Error 1

However, I checked the program by running:
python run_pipeline.py -h

And I got the message:
usage: run_pipeline.py [-h] -a ASSEMBLY -l LENGTH -b BED [-o OUTPUT]
                       [-c CUTOFF] [-g GFA] [-u UNITIGS] [-e ENZYME]
                       [-i ITER] [-x DUP] [-s EXP] [-m CLEAN]

SALSA Iterative Pipeline

optional arguments:
  -h, --help            show this help message and exit
  -a ASSEMBLY, --assembly ASSEMBLY
                        Path to initial assembly, headers must not contain ':'
  -l LENGTH, --length LENGTH
                        Length of contigs at start
  -b BED, --bed BED     Bed file of alignments sorted by read names
  -o OUTPUT, --output OUTPUT
                        Output directory to put results
  -c CUTOFF, --cutoff CUTOFF
                        Minimum contig length to scaffold, default=1000
  -g GFA, --gfa GFA     GFA file for assembly
  -e ENZYME, --enzyme ENZYME
                        Restriction Enzyme used for experiment
  -i ITER, --iter ITER  Number of iterations to run, default = 3
  -x DUP, --dup DUP     File containing duplicated contig information
  -s EXP, --exp EXP     Expected Genome size of the assembled genome
  -m CLEAN, --clean CLEAN
                        Set this option to "yes" if you want to find
                        misassemblies in input assembly

How can I fix this issue
make: *** [Makefile:9: break_contigs] Error 1 ?

Which version compiler is required?
Sincerely Yours.

What's your gcc version? We recommend using the latest gcc version for compilation.


Examples not working

I try the examples on the readme, but only the first one is working.
The Card with section and the action card example generates '/skrepr/teams-connector/src/Exception/InvalidServerResponse.php' execption.
I use everything as seen on the readme, with guzzle client, and a working endpont (as mentioned the first example works, I got the card in teams)

I see some issues for when you just copy/paste the examples (I will fix those examples asap), but I didn't got the InvalidServerResponse exception, can you give me more information?
Which PHP version did you use and can you give me the complete exception as you got it?


fix bug with mempool explorer url

It closes #384
@tiero please review

It should be
  electrsURL: 'https://liquid.network/testnet',
  esploraURL: 'https://liquid.network/liquidtestnet/api',

to be consistent with the other providers (esplora = 'api')
changed by 7437a6a


Using auth in receivers

Hi everybody!
I'm just wondering, can i provide auth credentials in receivers config to use then with webhook? something similar to header in curl. My target url requires auth (ID and token, like curl -H "Authentication: ID TOKEN"), but i can't use them in link.

Are you looking for this: https://prometheus.io/docs/alerting/configuration/#http_config ?

Hi, @mxinden. Thank you for reply.
is
basic_auth:
  username: ID_here
  password: TOKEN_here

the same as curl -H "Authentication: ID TOKEN"?
Thank you.

@krakazyabra this change wouldn't be limited to AlertManager and it has been discussed before: see https://github.com/prometheus/common/issues/140. The conclusion has been that we don't want to support arbitrary authentication schemes.

The conclusion has been that we don't want to support arbitrary authentication schemes.

Why? I'm trying to hook up alertmanager with splunk and since Splunk is demanding Splunk to be placed in Authorization header - I can't use alertmanager.

I think that it is exactly the reason. There are thousands of products out there, we can't support non standard authentication schemes for all of them. In the case of splunk from what I understand they invented a completely new scheme?

@roidelapluie
I don't know what is underneath in each auth scheme, but in case of splunk you just need to put:
Authorization: Splunk TOKEN
And from my perspective changing Bearer to Splunk in header is just a matter of couple lines of code :)

@ikarlashov we are having the same issues here to integrate with Splunk, did you find any workaround for this?

I think that it is exactly the reason. There are thousands of products out there, we can't support non standard authentication schemes for all of them. In the case of splunk from what I understand they invented a completely new scheme?

This seems to more or less be the justification every time something like this comes up, but the majority of these I've seen seem to boil down to "let me set arbitrary headers in http_config" which seems like a very small change to allow alertmanager to talk to almost anything. Heck, you could scrap the entire bearer_token and basic_auth sections without any loss of functionality if you just supported setting arbitrary headers.
The current state means that you basically always end up writing a custom authentication server to translate from what alertmanager will provide to whatever format the thing you're talking to supports. Which is really not great and creates ample opportunity to create new security problems for yourself.
Am I missing some reason to be so opinionated about specifying bearer token/basic auth credentials rather than just making all headers (including the Authorization header) configurable?

This is supporter in alertmanager 0.22, currently in release candidate.
e.g.:
authorization:
  credentials: password
  type: Splunk


Get rid of get_or_create_resource in example script

Is your proposal related to a problem?
The use of a function that gets a resource OR creates it and gets it is a bad practice. If the user is requesting a resource and it does not exists, a 404 error should be returned to the user instead of assuming that he/she wants the resource to be created.
Describe the solution you'd like
Get rid of the function get_or_create_resource  in the example script.

I personally think it would be bad practice if the function was labelled as create or get, but it's pretty clear here that the function will create a resource if it doesn't exist, and get it if it does.
That being said, this was done because you may not want to have to add in the try catch yourself if the creation of the 300th patient failed and you have to rerun your creation script.  It's no different then having all the try catches that you had in the first place, it just makes the code more condensed.

I looked at the script I wrote originally and you're right, what you are doing is just making the script more condensed. Generally speaking, running the script twice in a row should lead to the same dataset state in the data node. One way to achieve this is to start the script with DELETING the dataset (we know its resource name), then create the dataset, create the fhir store, etc. with no need to check that these resources already exist because we make sure to remove the dataset first thing in the script. With this new approach, running the script twice (if it completes successfully) grantees that the state of the dataset in the data node is the same.


Connect failed: AMQJS0007E Socket error:undefined" with HiveMQ client

Problem/Motivation
Receive "Connect failed: AMQJS0007E Socket error:undefined" error when trying to connect to Community Add on MQTT broker through built-in HiveMQ client from all browsers (tried Chrome, Opera and Edge).
Issues #24, #6 and #12 are about the same error message, but neither was actually resolved. One submitter stopped using Hassio, and this addon, while the other managed to connect finally "without changing anything". Both issues are closed.
Expected behavior
HiveMQ client connection to add on broker.
Actual behavior
Connection fails with error message as above.
Steps to reproduce
Fresh install of add on. MQTT broker works and I can see devices connecting to it in logs. Hassio integration set up via configuraton and HA configuration.yaml.
Attempted to use the mosquito addon before this and also had issues attempting to connect to the MQTT broker from home assistant (i uninstalled the mosquito addon before swapping to this addon).
Error in WEB UI

MQTT Server & Web client configuration

System info

System log (when attempting to connect)

Addon log
Log
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
Hass.io Add-on: MQTT Server & Web client
Mosquitto MQTT Server bundled with Hivemq's web client
Add-on version: 1.1.0
You are running the latest version of this add-on.
System: HassOS 2.12  (amd64 / intel-nuc)
Home Assistant version: 0.97.2
Supervisor version: 181
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] hivemq.sh: executing...
patching file /app/index.html
[cont-init.d] hivemq.sh: exited 0.
[cont-init.d] mosquitto.sh: executing...
[15:17:20] INFO: Adding configuration for MQTT Server...
[15:17:27] INFO: Setting up user (!secret)
[15:17:31] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[15:17:37] INFO: Starting mosquitto MQTT Server...
1566245857: mosquitto version 1.6.2 starting
1566245857: Config loaded from /opt/mosquitto.conf.
1566245857: Opening ipv4 listen socket on port 1883.
1566245857: Opening ipv6 listen socket on port 1883.
1566245857: Opening websockets listen socket on port 1884.
1566245857: Opening ipv4 listen socket on port 4883.
1566245857: Opening ipv6 listen socket on port 4883.
1566245857: Opening websockets listen socket on port 4884.
[15:17:38] INFO: Starting NGINX for the MQTT client...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
Configuration.yaml
Proposed changes
No idea how to fix this isssue.
 GitHubopenresty/luajit2OpenResty's Branch of LuaJIT 2. Contribute to openresty/luajit2 development by creating an account on GitHub.
OpenResty - Download

From my understanding its a Websockets connection from your browser, is 4884 accessible?

Not sure how to test for this.
I am new to the home assistant community and I tried searching "how to access ports via websockets" and I got a bit overwelmed.
Im clearly lacking knowledge on the underlying mechanism of how the MQTT client communicates with HASSIO.
Is there a resource i can read to become more familar with testing ports accessiblity with websockets?
I also forgot to add my HA configuration
mqtt:
broker: a0d7b954-mqtt
username: !secret mqtt_user
password: !secret mqtt_pass
client_id: hassio-mqtt-client

No problem, the reason for my comment was that I noticed you are accessing via your duckdns domain.  Is that resolving to your external address? or did you make if resolve to your internal address?
If it is external did you configure access via port-forwarding?  If connect to IP address on 1884 does the web ui work (you may need to disable SSL)?
Just to add, accessing from the webui and from HA are different things are you actually seeing errors in the HA log itself when connecting.

Looks like you made you way to Discord which is probably the best place to help troubleshoot.
Will close this out.

I am having the very same issue. did you find a solution?


decorators that are instances of classes have methods stripped when access through context

import { Elysia } from "elysia";

class Test {
  readonly name = "test";
  public foo() {
    return this.name;
  }
}

const test = new Test();

console.log(test);

export const ctx = new Elysia().decorate("test", test);

const app = new Elysia()
  .use(ctx)
  .get("/", ({ test }) => {
    console.log(test);
    console.log(test.foo());
  })
  .listen(3002);

console.log(`app is listening on ${app.server?.hostname}:${app.server?.port}`);

app.handle(new Request("http://localhost:3002/"));

$ bun run --hot src/main.ts
[0.02ms] ".env"
{
  name: "test",
  foo: [Function: foo]
}
app is listening on localhost:3002
{
  name: "test"
}
TypeError: test.foo is not a function. (In 'test.foo()', 'test.foo' is undefined)

very very strange behavior, and only happens with classes
if you replace
const test = new Test();

with
const test = {
  name: "test",
  foo() {
    return this.name;
  },
};

everything works fine
$ bun run --hot src/main.ts
[0.03ms] ".env"
{
  name: "test",
  foo: [Function: foo]
}
app is listening on localhost:3002
{
  name: "test",
  foo: [Function: foo]
}
test

This issue stems from Mergician, if you call .use, it tries to merge your decorators but somehow fails. This probably can be alleviated, but I'd like to create an issue at  Mergician

https://github.com/jhildenbiddle/mergician/issues/4

Should be fixed in #103.
Let me know if the problem stills persists


Share source processing result within a build and cache macro includes based on the discovered macros

Context
See https://github.com/gradle/gradle-native/issues/302.
Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

As a first step, I tried hashing the include directives using Serializer feeding inside HashingOutputStream via KryoBackedEncoder. That made the performance even worst, ~10-15x slower.
Here is a flame graph with PR https://github.com/gradle/gradle/pull/4616 applied. What this change tries to do is limit the number of DefaultIncrementalCompileSourceProcessor.visitFile call for file processing that contains macro includes. However, looking at a profiler runs, DefaultSourceIncludesResolver.resolveMacro is still in the top of the method profiling:

An entry point to DefaultSourceIncludesResolver.resolveMacro is DefaultSourceIncludesResolver.resolveInclude. Caching at that level is quite similar to what I'm trying to do here. However, maybe we can do something cheaper and more effective than caching to avoid doing the work again.

This change seems to be harder to achieve correctly. So I'm going to close this PR in favor of https://github.com/gradle/gradle/pull/4677. We can revisit the idea behind this change once we get more data points with regards to performance measure in real projects.


Unable to proceed with installation under proxy due to SSL error on Ubuntu

I am trying to install rust and related tools using the script curl https://sh.rustup.rs -sSf | sh. However, I get the error :
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256' to '/home/nascarsayan/.rustup/tmp/vnx5fmfc21kuqttu_file'
info: caused by: error during download
info: caused by: [35] SSL connect error (error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol)

Other installation methods including building from source don't work and give the same error.

Similar problem here:
Submodules updated in 68.38 seconds
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

spurious failure, trying again
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

spurious failure, trying again
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

spurious failure, trying again
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

spurious failure, trying again
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
failed to run: curl -s -y 30 -Y 10 --connect-timeout 30 --retry 3 -Sf -o /scratch/87971386.tmpdir/tmpRwGdZx.sha256 https://static.rust-lang.org/dist/2019-01-17/rust-std-1.32.0-x86_64-unknown-linux-gnu.tar.gz.sha256
Build completed unsuccessfully in 0:01:08
make: *** [Makefile:18: all] Error 1


Go to definition is missing references as of TypeScript 4.7.4

Bug Report
🔎 Search Terms
"go to definition" javascript
🕗 Version & Regression Information

This changed between versions 4.6.4 and 4.7.4

⏯ Playground Links

4.6.4
4.7.4
TypeScript equivalent

💻 Code
class Test {
	constructor() {
		// Right click and choose 'Go to Definition'
		//    |
		//    V
		this.foo = null;
	}

	setFoo() {
		this.foo = "not null";
	}

	usesFoo() {
		if (this.foo) {
			const lower = this.foo.toLocaleLowerCase();
			console.log(lower);
		}
	}
}

🙁 Actual behavior
Only the first two references are shown
🙂 Expected behavior
All references are shown, including those in usesFoo(). This was the behaviour in 4.6.4, and is currently still the behaviour when using the TypeScript equivalent of this code.

Hmm I reckon this might actually be intentional in a way. After all the TypeScript equivalent works exactly the same, using 'Go to Definition' on one of the references goes to the only definition available, which is the one on line 5.
The only difference is then, that in JavaScript there are two definitions. One where it is set to null and another where it is set to "not null".
You can see the behaviour is in fact the same by adding a second definition to the TypeScript version: playground. It shows an error because there are now two foo definitions, but 'Go to Definition' functionality still works and you can see the behaviour is exactly the same as what is happening in JavaScript.
So I suppose there are two possible expected behaviors that would fix this:

Using 'Go to Definition' on something that is already a definition, causes all references to get shown, both references and definitions.
When 'Go to Definition' is used on something with multiple available definitions, only a single definition would get listed. In the case of TypeScript this would be whichever doesn't have a 'Duplicate identifier' error, and in the case of JavaScript this would be the one that is inside a constructor(). Though I'm not sure what should happen if in JavaScript the constructor doesn't contain a definition at all.

There are two different verbs available here:

Go to Definition
Find All References

Go to definition attempts to go to "the" definition, but will show multiple results if multiple are present. In a JS file, every assignment to a this. property is considered a definition, so you see both assignments but not the use site. The fixed bug was that we were showing a non-definition result in a use site.

Or to put it another way, the invariant we chose to preserve is that adding an additional "declaration" will not hide an existing declaration from the Go To Definition results

Yeah that makes sense, I think what confused me is that VSCode has a setting for a fallback method when the result is the current location.
Ideally I'd want to get a list of all references and all definitions. But I think that would be easier to achieve by making a change to VSCode rather than to TypeScript.


Sort results from ec-cli

This is a very simple sorting implementation on ec-cli's result outputs.
From what I can tell, a lot of the reason result ordering wasn't deterministic in the first place is down to the ordering of evaluators not being deterministic. You can see how the current code prepares input to Evaluate() here: https://github.com/hacbs-contract/ec-cli/blob/main/internal/image/validate.go#L101
This doesn't seem to be an issue internally (at least as far as I can tell), so I went with the approach of sorting the merged lists of successes, warnings, and violations. Note that the sort method is different for violations, since the msg field is often more descriptive than the metadata.code field. However, the opposite is true for successes.
This is my first Go pull request ever, so I'm sure there's a better way to do this. Feedback is welcome!
Ref: https://issues.redhat.com/browse/HACBS-1771
cc @zregvart @simonbaird @lcarva and anyone else interested :smile:

The acceptance failure seems bogus, but the unit test failures are useful. Do you get same failures with make test locally?

Not sure if there's a good way to extract the comparison logic. Can a go function return a function?
I'm imagining something like this:
    sort.Slice(violations, sorterFunc(violations))

@simonbaird I don't know if that's even necessary - all three slices (successes, warnings, and violations) should behave the same if passed to a separate sort function, and we can just pass that function into sort.Slice().

@simonbaird How does it look now?

Better get the tests passing, it might encourage more reviewers. :smile:

To all following, I've refactored the sort function so it makes more sense and updated tests to work with the new sorting. I can also look into a new test to ensure everything is sorted, but that will take more time.

I'm not sure what the deal is with Pipelines as Code CI / task-verify-ec-on-pull-request. Anyone know if we're expecting that to pass?

I found this:
Pipeline tekton-ci/tekton-bundle-builder can't be Run; it contains Tasks that don't exist: Couldn't retrieve Task "sanity-label-check": GET https://quay.io/v2/auth?scope=repository%3Aredhat-appstudio-tekton-catalog%2Ftask-sanity-label-check%3Apull&service=quay.io: unexpected status code 502 Bad Gateway:


[SPARK-17676][CORE] FsHistoryProvider should ignore hidden files

What changes were proposed in this pull request?
FsHistoryProvider was writing a hidden file (to check the fs's clock).
Even though it deleted the file immediately, sometimes another thread
would try to scan the files on the fs in-between, and then there would
be an error msg logged which was very misleading for the end-user.
(The logged error was harmless, though.)
How was this patch tested?
I added one unit test, but to be clear, that test was passing before.  The actual change in behavior in that test is just logging (after the change, there is no more logged error), which I just manually verified.

Test build #65942 has started for PR 15250 at commit b125f2f.

Test build #65942 has finished for PR 15250 at commit b125f2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65942/
Test PASSed.

Test build #65997 has started for PR 15250 at commit 9c9012e.

@vanzin woudl appreciate it if you can take a look at this -- related to the change you reviewed back here https://github.com/apache/spark/pull/5886#issuecomment-99941529

Test build #65997 has finished for PR 15250 at commit 9c9012e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65997/
Test PASSed.

Looks ok but I think the test could be changed to actually ensure the change is working.

Test build #66121 has started for PR 15250 at commit 2d37bd3.

Test build #66121 has finished for PR 15250 at commit 2d37bd3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM, merging to master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66121/
Test PASSed.

Merged build finished. Test PASSed.


Mouse acceleration

I downloaded this mod and started using it but something felt slightly off and after some testing I figured out that it was something with the mouse in game. I tried to launch Minecraft without the mod and it was all good so I think the mod works as a mouse accelerator

I did some testing, and I have not been able to reproduce this bug. Are you absolutely certain it is this mod that is causing the issue? What version of Minecraft and Forge are you using? Does the mouse get sped up only in GUIs or in the actual game? What other mods are you using? Is there anything else I should know that would help me reproduce this bug?

I did some testing, and I have not been able to reproduce this bug. Are you absolutely certain it is this mod that is causing the issue? What version of Minecraft and Forge are you using? Does the mouse get sped up only in GUIs or in the actual game? What other mods are you using? Is there anything else I should know that would help me reproduce this bug?

I was wrong I think it might have been another mod. Sorry for the inconvenience

I was wrong I think it might have been another mod. Sorry for the inconvenience


Remove automatic hub creation from here

That should be done by hubploy

Makes sense. Let hubploy do everything JupyterHub for now, make sure you still have a working helm provider.

Thanks, @salvis2 :)


How to run in Rust

When I clone the directory and run "cargo run"
it gives me a "a bin target must be available for cargo run"
what can I do?

It's a library, you need add it as a dependency in your project's Cargo.toml.  see this

I'm interested in Implement your library and fork it into a full RISK-V C compiler as my Rust learning project.
Can you give me some clues where to start from?

Actually it's a copy of this for C language. Here's the article about the original project.

Actually this project is a copy of this for C language. Here's the post about the original project.
For RISC-V porting, I have no experience about it. But this project doesn't use OS/Arch-specific features so I think it's easy to port.

Thanks a lot, I appreciate it.
Cheers mate!


Is Armor Master (Light Armor Master) working?

Sorry, this wasnt a bug at all, answered my own question. Please delete :)

This looks like a bug but not sure if it is from the mod. Your max dex mod
is stuck a +3 so i am guessing there is some ghost armor on your character
somehow. I know I saw this in beta but i thought it had been resolved.
On Sat, Sep 11, 2021, 11:01 Sikosh1999 @.***> wrote:

Closed #41 https://github.com/Vek17/WrathMods-TabletopTweaks/issues/41.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Vek17/WrathMods-TabletopTweaks/issues/41#event-5287786265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWSQPFPV54BVB5QV3ZCU33UBOKOHANCNFSM5D3FX67A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

It's not a bug. Chainmail is Medium Armor. He's not wearing a Chain Shirt, but Chainmail.
Mithril doesn't change the type of armor, it just makes it act like 1 type lighter for the purposes of armor penalties.

Mithril makes it count as light for all purposes except proficiency, even so they are getting +3 from dex instead of +4 even then. Though that could be encumberece.

It doesn't for things that specifically target a type of armor. If it says "expert in light armor" (I can't remember, and the screenshots were deleted) then a chain shirt works. Chainmail, even mithril, doesn't.

It was encumbrance in this case, thanks everyone!


Jitter and getting stuck when colliding with flat wall and angled surface

When running against a gap that is barely not large enough for the collision shape the CharacterBody3D will jitter and jumping is affected.
Cylinder Shape: The CharacterBody3D will jitter and is_on_floor() will flip between true and false. Jumping is nearly impossible since you do not get the right amount of height from a jump.
Capsule Shape: The CharacterBody3D will jitter and is_on_floor() will flip between true and false. Jumping is nearly impossible since you do not get the right amount of height from a jump.
Box Shape: The CharacterBody3D will jitter but is_on_floor() is right. Jumping is nearly impossible since you do not get the right amount of height from a jump.
The jumping bug does still happens when the gap is much smaller than the width of the collision shape.
Setting the amount of max_slides to a value much higher ( I use ~20) than default will fix the jumping issue, but the jitter issue and is_on_floor() issue is still present. This happens with 60 physics ticks per second and 100 physics ticks per second with no change. These scenarios occur with default jolt settings on 0.9.0 and 0.8.0. Not entirely sure if this is a known issue or not. Since it affects the most common collision shape I thought it would be worth making this issue anyways.
MRP is included.  The .godot and addons folder are not present in the MRP so godot-jolt needs to be installed.
Setting the max amount of slides is commented out in the _ready() function. is_on_floor() is printed at the beginning of every physics tick in the console. All that is needed to change collision shapes is to change CShape in player.tscn (The default sizes of the named collision shapes are what should be used).
MRP-Jittering.zip

Thank you for reporting this, and for providing the minimal repro.

Jumping is nearly impossible since you do not get the right amount of height from a jump.

Assuming I'm actually performing the repro correctly, this particular thing seems to happen with Godot Physics as well, where jumping will be severely hindered when you push yourself into one of these corners. Bumping up max_slides to a higher value does indeed fix this, as you point out.
As for the jittering and flip-flopping of is_on_floor, I'll have to do some more in-depth debugging to see why/where this diverges from Godot Physics. I would've bet money on it being a regression caused by #559, similar to #626, since that seems to have messed with some floor stuff internally within move_and_slide, but that does not appear to be the case.


Command not found

Installed the extension and nothing works.
I keep getting command 'magit.status' not founderror. And similar ones for other commands as well.

What version?
Platform?

I'm getting the same error.
Environment: Ubuntu on WSL2 on Windows 10, with vscode using Remote-WSL connection.
 This seems related to the file name case sensitive issue fixed in version 0.0.5

Tried Uninstall + Restart + Install + Restart: same error.
Is there some other way to "completely remove" the extension?

To clear the VS Code extension cache folder:

    Open the folder in C:\Users\<username>\. vscode\extensions.
    Delete all files in the folder.

To clear the VS Code extension cache folder:

    Delete the folder in ~/.vscode/extensions/kahole.magit-0.0.5

Just delete magit extension folder in there, and restart and re-install. Should be good then, I think.

Tried this. Still same error.
Another data point: I've clean-installed magit both in WSL environment and in Windows environment.
It works when I open a project in the windows environment.
But, it gives the above mentioned error when I try inside the WSL environment.

If I manually change these 4 lines to use HunkView instead of hunkView, then it works:
./out/views/changes/changeView.js:const hunkView_1 = require("./HunkView");
./out/commands/visitAtPointCommands.js:const hunkView_1 = require("../views/changes/HunkView");
./out/commands/stagingCommands.js:const hunkView_1 = require("../views/changes/HunkView");
./out/commands/discardCommands.js:const hunkView_1 = require("../views/changes/HunkView");

Maybe because WSL is linux, which is case sensitive?

Yep, did a clean build on my side, trying to get rid of every last capital H. grepped for them and dint find any
lets see how it goes, v.0.0.6


Syntax Error in Migration Script

Hi,
I'm trying to update the plugin from version 2.10.1 to 2.11.0 and when Craft tries to run migrations it trips the following error:
Exception 'ParseError' with message 'syntax error, unexpected '|', expecting ';' or '{''
in /storage/XXXXXX/www/staging_html/vendor/born05/craft-twofactorauthentication/src/Plugin.php:132
Can you help me resolve?
Thanks!
Brian

Hi I'm having the same issue trying to update from version 2.10.1 to 2.11.0.
Craft CMS 3.8.9
Status: error
Response: {"name":"Exception","message":"syntax error, unexpected '|', expecting ';' or '{'","code":0,"error":"syntax error, unexpected '|', expecting ';' or '{'","exception":"ParseError","file":"/var/www/html/vendor/born05/craft-twofactorauthentication/src/Plugin.php","line":132,"trace":[{"file":"/var/www/html/vendor/composer/ClassLoader.php","line":428,"function":"Composer\Autoload\includeFile"},{"function":"loadClass","class":"Composer\Autoload\ClassLoader","type":"->"},{"function":"spl_autoload_call"},{"file":"/var/www/html/vendor/craftcms/cms/src/services/Plugins.php","line":917,"function":"is_subclass_of"},{"file":"/var/www/html/vendor/craftcms/cms/src/services/Plugins.php","line":232,"function":"createPlugin","class":"craft\services\Plugins","type":"->"},{"file":"/var/www/html/vendor/craftcms/cms/src/base/ApplicationTrait.php","line":1520,"function":"loadPlugins","class":"craft\services\Plugins","type":"->"},{"file":"/var/www/html/vendor/craftcms/cms/src/web/Application.php","line":99,"function":"_postInit","class":"craft\web\Application","type":"->"},{"file":"/var/www/html/vendor/yiisoft/yii2/base/BaseObject.php","line":109,"function":"init","class":"craft\web\Application","type":"->"},{"file":"/var/www/html/vendor/yiisoft/yii2/base/Application.php","line":204,"function":"__construct","class":"yii\base\BaseObject","type":"->"},{"function":"__construct","class":"yii\base\Application","type":"->"},{"file":"/var/www/html/vendor/yiisoft/yii2/di/Container.php","line":419,"function":"newInstanceArgs","class":"ReflectionClass","type":"->"},{"file":"/var/www/html/vendor/yiisoft/yii2/di/Container.php","line":170,"function":"build","class":"yii\di\Container","type":"->"},{"file":"/var/www/html/vendor/yiisoft/yii2/BaseYii.php","line":365,"function":"get","class":"yii\di\Container","type":"->"},{"file":"/var/www/html/vendor/craftcms/cms/src/Craft.php","line":61,"function":"createObject","class":"yii\BaseYii","type":"::"},{"file":"/var/www/html/vendor/craftcms/cms/bootstrap/bootstrap.php","line":247,"function":"createObject","class":"Craft","type":"::"},{"file":"/var/www/html/vendor/craftcms/cms/bootstrap/web.php","line":51,"function":"require"},{"file":"/var/www/html/web/index.php","line":11,"function":"require"}]}

Which php version are you using? I think i accidentally added php 8.x syntax, which should just be in the Craft CMS 4 version of the plugin.

Is this solved with version 2.11.1 of the plugin?

Which php version are you using? I think i accidentally added php 8.x syntax, which should just be in the Craft CMS 4 version of the plugin.

I’m using PHP version
8.1.17

I'm running php 7.4.3, Craft 3.8.7

@mattias78 @brianrivet-tilt  Does version 2.11.1 solve the errors?


Evaluate support of Pydantic-v2 generated JSON Schemas

When testing the schemas in https://github.com/fractal-analytics-platform/fractal-tasks-core/pull/737, we should be aware of how Pydantic V2 changes handling of Optional attributes (which includes the use of anyOf, and the fact that it seems that attributes are always included). The new behavior is sometimes confusing, see:

https://github.com/pydantic/pydantic/issues/7161
https://github.com/pydantic/pydantic/issues/8394

It's likely that this produces issues in the form generator.
By taking the example in https://github.com/pydantic/pydantic/issues/7161#issue-1854576770, we end up with this JSON Schema:
{
  "properties": {
    "field": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Field"
    }
  },
  "title": "Model",
  "type": "object"
}

If we try it out in https://rjsf-team.github.io/react-jsonschema-form/, we find this behavior:

which IMO is a suboptimal UX, because it forces a two-steps process: first I need to decide whether to include the argument, and then I can decide whether/how to fill it.

TLDR We'll need to keep an eye on this, when experimenting with schema-based form generators.

This issue was a FYI, but the plan is rather to make sure that fractal-tasks-core produces appropriate JSON Schemas (that is, without the additional anyOf pattern for nullable field) even with Pydantic v2.
Closing.


Add the ability to track Groovy model objects via a specification.

Not yet wired up yet into any view.

This is some really rough code, but I want to facilitate future experimentation. It's only wired to tests ATM


jailbreak ASR label for 5 models per prompts+questions?

Can you provide jailbreak ASR labels on the five models per prompts+questions per attempt?
Thank you for your effort in this research!
It helps a lot and promotes the development of the safety of LLMs.

Hi,
Glad to hear from you!
I am sorry that we cannot provide the jailbreak ASR on the models per prompts and questions at this time. We plan to release this information after our paper is accepted for publication.
Thank you for your understanding and support!
Best,
Vera


add asmitsirohi

I have added my name, along with GitHub profile link.

Thanks for your contribution 🚀 and thanks for reviewing @CodingSpecies


CreateSnapshotRequest: DryRun parameter definition incorrect

The services-2.json for ec2's CreateSnapshotRequest has locationName set to dryRun which results in AWS rejecting the request:
<?xml version="1.0" encoding="UTF-8"?> <Response><Errors><Error>UnknownParameter<Message>The parameter dryRun is not recognized</Message></Error></Errors><RequestID>...</RequestID></Response>
The correct case is DryRun which AWS accepts:
<?xml version="1.0" encoding="UTF-8"?> <Response><Errors><Error>DryRunOperation<Message>Request would have succeeded, but DryRun flag is set.</Message></Error></Errors><RequestID>...</RequestID></Response>

The model is correct, but there are some differences in the ec2 protocol over the very similar query protocol. One of those differences is that for input the first letter in locationName is capitalized.
You can see how we handle those differences in our serializer (here).


Reduce use of reflection

I removed reflection calls where they are not needed.

Thank you Markus for your contribution


SWN: Add misc attribute mod field

Need to have a misc bonus field that adds on to attributes mods. These bonuses or penalties could be gained through various means not necessarily documented in the RAW.

#2352 should happen first.


[FEATURE] Automatic publishing to package managers

Describe your Feature
This issue is about the addition of CI scripts that would automate publishing to supported platforms on release (wally, npm, pesde, etc). While we already have a wally CI script for this, we do not have such a script for npm or pesde.
Implementation
This would be implemented using the release CI script.
Alternatives
Publishing manually. This is relatively infeasible at scale for fairly obvious reasons.
Considerations
Successful implementation of this issue would resolve the problem of having to manually publish to all providers for the package.
Tasks
The following tasks need to be done for this issue to be complete:
@Ukendio specific:

[ ] Expose an NPM_AUTH_TOKEN secret for the runner to use in accordance with this

Non-specific:

[ ] (Pesde) add manifest info
[ ] (Pesde) implement CI script
[ ] (npm) implement CI script

Steps to get the pesde token on Windows:

Install pesde
pesde auth login
Then due to Windows not allowing users to get tokens from the credential manager, you need to create a rust app to get the token.
cargo create get-pesde-token
cd get-pesde-token
cargo add keyring -F windows-native

use keyring::{Entry, Result};

fn main() -> Result<()> {
    let entry = Entry::new("tokens", "pesde")?;
    let password = entry.get_password()?;
    println!("Password: {}", password);
    Ok(())
}

cargo run
Make sure to copy the entire token including Bearer.


Typo in math in epsilon-traveled posterior

Incorrect:
    \\sum_{i=0}^{n-k} \\binom{n-k}{i} (-1)^i p^\\frac{α + δ (k + i) - 1}{δ ε} (1-p^{1/(δε)})^{β - 1}

Correct:
    \\sum_{i=0}^{n-k} \\binom{n-k}{i} (-1)^i p^(\\frac{α + δ (k + i)}{δ ε} - 1) (1-p^{1/(δε)})^{β - 1}

Also typo in Likelihood


Notebook Rendering: HTML tables & KaTeX

The impact on page load time is small:

An extra 85kb on the first load of a code page - which is mostly webfonts for KaTeX from a cdn.
Then it's cached and there's no additional impact.
KaTeX is pretty performant so it doesn't take that long to render.

This isn't quite ready to merge yet.

</tbody> is showing up for some reason
KaTeX fonts use relative URLs when they are getting the fonts - which works fine in dev but not in production when bundle everything up.

I hade a similar problem when bundling font-awesome. I tried bundling the fonts too somehow but webassets does not support binary files

Things should work now. I'm not super happy about having to resort to using vw for the max-width of an output - but it works.

Any comments? This is mostly just some minor CSS tweaks and pulling in some libraries (though it didn't feel like that)
Probably going to merge this sometime tomorrow if not.


Switch to built-in SWIFT_PACKAGE flag

I think this isn't needed, but the CocoaPods and Carthage builds will be the ultimate determiner.

⛵


Instructions Need to be Updated

The instructions for adding a data source to a gateway don't look anything like what I see on Power BI service.  When I log in, I click on the cog and choose Manage Gateways.  In your instructions, you say to choose the new at the top of the ribbon.  However, I just see a list of gateways with no way of choosing one and no new button to select.

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

ID: 92e0c038-1195-d758-ccf4-903b689139ca
Version Independent ID: 181904c0-1ec5-0a1d-4cbf-a5a639bbdfeb
Content: Add or remove a gateway data source - Power BI
Content Source: powerbi-docs/connect-data/service-gateway-data-sources.md
Service: powerbi
Sub-service: powerbi-gateways
GitHub Login: @arthiriyer
Microsoft Alias: arthii

Thanks for your comment, @SueStankus. This issue has been assigned to the doc author for review.

We've updated the article since you submitted this feedback. Thanks.


Hue Dimmer switch events

Because homebridge-hue polls the Hue bridge, it cannot detect reliably all buttonevents.  E.g. when a button is pressed and released between to heartbeats, homebridge-hue only sees the release buttonevent; but when the button is pressed just before a heartbeat and released just after, homebridge-hue sees both events.  To cope with this, homebridge-hue currently only changes the Output State of the Stateful Programmable Switch service corresponding to a Hue Dimmer switch, when a dimmer button is released.
This causes the HomeKit change to happen late, especially when a button is pressed, held for several seconds and then released.  Homebridge-hue should change the Output State as soon as it detects the first event in a press/hold/release series, and not change the state for the next events in the same series.

Implemented in v0.1.8.


Expand logging configuration to include the file name and data word format

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
All users to configure a file name (including an optional timestamp), as well as the format of the logged data word.
Define unit tests around custom Linux path manipulation.
Why should this Pull Request be merged?
We want users to be able to customize the log file name in a similar way to the Embedded Data Logger.
What testing has been done?
Hand testing of deployed functionality. Added unit tests for path manipulation.

I do not currently have any system tests that exercise this functionality, but intend to add them (either in this PR or a subsequent one). @buckd please let me know if you want the tests submitted as part of this PR.

I do not currently have any system tests that exercise this functionality, but intend to add them (either in this PR or a subsequent one). @buckd please let me know if you want the tests submitted as part of this PR.

A separate PR is fine.

I'm going to leave the format string handling as-is for now, but I do think something like this (which would allow a sufficiently motivated user to specify a custom format string entirely) is worth considering for other protocols. ARINC-429's 32-bit format doesn't leave too much flexibility in how the values are represented, so I don't think it's worthwhile in this case.


Delete this repository

A while back I started using https://github.com/bincrafters/conan-caf as the primary repository for the CAF Conan recipe.  Bincrafters is a collective of developers writing Conan package recipes for the major C/C++ libraries.  The Bincrafters CAF recipe has been accepted into the premier Conan package repository called Conan Center (search for caf), and we Bincrafters keep it up to date with new releases of CAF.
Because it has diverged so much I propose to delete this repository and add a reference to conan-caf on the main actor-framework README.md.

Thanks for the heads-up! I think I'll gladly remove this repository.

add a reference to conan-caf on the main actor-framework README.md.

Would you mind making a PR to the readme with the necessary conan steps? :)

I submitted the PR


Nitpicking the docs

Having a read of some of the docs, a few things caught my attention:
-For installing maybe a onliner would be good, say
"pip install git+https://github.com/xgcm/xmitgcm.git"

The default test dataset has no "ds.WVEl.dims"
addtiional
-print(ds_llc['S']dims) -> print(ds_llc['S'].dims)

Thanks for finding these typos! (The docs were mostly written when I was very sleepy..)
It would be great if you could make a pull request yourself to fix them. To do this, you can follow the directions in the docs, or, since these are small changes, you can directly edit the code in github.
https://github.com/xgcm/xmitgcm/blob/master/doc/installation.rst
(click on the pencil)
This will automatically create a pull request.

Hi @maikejulie, just checking in with this issue. Do you need any help getting a pull request started?

Hei! Thanks for checking in :) I was away for the weekend, so not had time yet! I think I should be fine, but will get back to you if I get confused!

@maikejulie, I would like to either close this issue or else resolve it. Do you plan to make an update to the docs?


Duplicate attributes in express entity customize search for default column

I have added two text attributes to an express entity object.
The customize search page (index.php/dashboard/system/express/entities/customize_search/:id) shows the columns correctly when I want to reorder the columns. But when I try to select the default sorting column, it shows the attributes twice.
Sorry for the Finnish screenshots. First screenshot is from default column and second one is from the column order.

Core Version - 8.3.2
Version Installed - 8.3.2
Database Version -<PHONE_NUMBER>3656

# concrete5 Packages
Afixia: Login Redirect (0.9.2), Login Block (0.9.3)

# concrete5 Overrides
themes/extranet/home.php, themes/extranet/page_forbidden.php, themes/extranet/page_theme.php, themes/extranet/right_sidebar.php, themes/extranet/full.php, themes/extranet/images, themes/extranet/left_sidebar.php, themes/extranet/default.php, themes/extranet/view.php, themes/extranet/page_not_found.php, themes/extranet/elements/header_calendar.php, themes/extranet/elements/header_top_bak.php, themes/extranet/elements/header_top.php, themes/extranet/elements/footer.php, themes/extranet/elements/header.php, themes/extranet/elements/footer_bottom.php, themes/extranet/elements, themes/extranet/description.txt, themes/extranet/css/styles.xml, themes/extranet/css/mixins/mixins.less, themes/extranet/css/mixins, themes/extranet/css/main.less, themes/extranet/css/components/forms.less, themes/extranet/css/components/footer.less, themes/extranet/css/components/header.less, themes/extranet/css/components/navigation.less, themes/extranet/css/components/blocks.less, themes/extranet/css/components, themes/extranet/css/bootstrap-3.2.0/button-groups.less, themes/extranet/css/bootstrap-3.2.0/code.less, themes/extranet/css/bootstrap-3.2.0/variables.less, themes/extranet/css/bootstrap-3.2.0/navs.less, themes/extranet/css/bootstrap-3.2.0/forms.less, themes/extranet/css/bootstrap-3.2.0/breadcrumbs.less, themes/extranet/css/bootstrap-3.2.0/mixins.less, themes/extranet/css/bootstrap-3.2.0/close.less, themes/extranet/css/bootstrap-3.2.0/labels.less, themes/extranet/css/bootstrap-3.2.0/mixins/center-block.less, themes/extranet/css/bootstrap-3.2.0/mixins/grid-framework.less, themes/extranet/css/bootstrap-3.2.0/mixins/image.less, themes/extranet/css/bootstrap-3.2.0/mixins/forms.less, themes/extranet/css/bootstrap-3.2.0/mixins/progress-bar.less, themes/extranet/css/bootstrap-3.2.0/mixins/labels.less, themes/extranet/css/bootstrap-3.2.0/mixins/tab-focus.less, themes/extranet/css/bootstrap-3.2.0/mixins/background-variant.less, themes/extranet/css/bootstrap-3.2.0/mixins/resize.less, themes/extranet/css/bootstrap-3.2.0/mixins/hide-text.less, themes/extranet/css/bootstrap-3.2.0/mixins/gradients.less, themes/extranet/css/bootstrap-3.2.0/mixins/size.less, themes/extranet/css/bootstrap-3.2.0/mixins/pagination.less, themes/extranet/css/bootstrap-3.2.0/mixins/text-emphasis.less, themes/extranet/css/bootstrap-3.2.0/mixins/nav-vertical-align.less, themes/extranet/css/bootstrap-3.2.0/mixins/nav-divider.less, themes/extranet/css/bootstrap-3.2.0/mixins/opacity.less, themes/extranet/css/bootstrap-3.2.0/mixins/table-row.less, themes/extranet/css/bootstrap-3.2.0/mixins/list-group.less, themes/extranet/css/bootstrap-3.2.0/mixins/responsive-visibility.less, themes/extranet/css/bootstrap-3.2.0/mixins/grid.less, themes/extranet/css/bootstrap-3.2.0/mixins/vendor-prefixes.less, themes/extranet/css/bootstrap-3.2.0/mixins/clearfix.less, themes/extranet/css/bootstrap-3.2.0/mixins/border-radius.less, themes/extranet/css/bootstrap-3.2.0/mixins/panels.less, themes/extranet/css/bootstrap-3.2.0/mixins/buttons.less, themes/extranet/css/bootstrap-3.2.0/mixins/text-overflow.less, themes/extranet/css/bootstrap-3.2.0/mixins/alerts.less, themes/extranet/css/bootstrap-3.2.0/mixins/reset-filter.less, themes/extranet/css/bootstrap-3.2.0/mixins, themes/extranet/css/bootstrap-3.2.0/scaffolding.less, themes/extranet/css/bootstrap-3.2.0/utilities.less, themes/extranet/css/bootstrap-3.2.0/tables.less, themes/extranet/css/bootstrap-3.2.0/normalize.less, themes/extranet/css/bootstrap-3.2.0/thumbnails.less, themes/extranet/css/bootstrap-3.2.0/component-animations.less, themes/extranet/css/bootstrap-3.2.0/navbar.less, themes/extranet/css/bootstrap-3.2.0/pagination.less, themes/extranet/css/bootstrap-3.2.0/jumbotron.less, themes/extranet/css/bootstrap-3.2.0/input-groups.less, themes/extranet/css/bootstrap-3.2.0/tooltip.less, themes/extranet/css/bootstrap-3.2.0/glyphicons.less, themes/extranet/css/bootstrap-3.2.0/wells.less, themes/extranet/css/bootstrap-3.2.0/responsive-embed.less, themes/extranet/css/bootstrap-3.2.0/list-group.less, themes/extranet/css/bootstrap-3.2.0/badges.less, themes/extranet/css/bootstrap-3.2.0/grid.less, themes/extranet/css/bootstrap-3.2.0/carousel.less, themes/extranet/css/bootstrap-3.2.0/modals.less, themes/extranet/css/bootstrap-3.2.0/media.less, themes/extranet/css/bootstrap-3.2.0/dropdowns.less, themes/extranet/css/bootstrap-3.2.0/panels.less, themes/extranet/css/bootstrap-3.2.0/buttons.less, themes/extranet/css/bootstrap-3.2.0/progress-bars.less, themes/extranet/css/bootstrap-3.2.0/bootstrap.less, themes/extranet/css/bootstrap-3.2.0/pager.less, themes/extranet/css/bootstrap-3.2.0/print.less, themes/extranet/css/bootstrap-3.2.0/alerts.less, themes/extranet/css/bootstrap-3.2.0/type.less, themes/extranet/css/bootstrap-3.2.0/popovers.less, themes/extranet/css/bootstrap-3.2.0/theme.less, themes/extranet/css/bootstrap-3.2.0/responsive-utilities.less, themes/extranet/css/bootstrap-3.2.0, themes/extranet/css/base/typography.less, themes/extranet/css/base/body.less, themes/extranet/css/base, themes/extranet/css/variables/errors.less, themes/extranet/css/variables/colors.less, themes/extranet/css/variables/typography.less, themes/extranet/css/variables/gutters.less, themes/extranet/css/variables/dimensions.less, themes/extranet/css/variables, themes/extranet/css/bootstrap-modified.css, themes/extranet/css, themes/extranet/js/main.js, themes/extranet/js, themes/extranet

# concrete5 Cache Settings
Block Cache - Off
Overrides Cache - Off
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).

# Server Software
Apache

# Server API
litespeed

# PHP Version
5.6.35

# PHP Extensions
bcmath, bz2, calendar, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, ionCube Loader, json, libxml, litespeed, mbstring, mcrypt, mhash, mysql, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_sqlite, Phar, posix, readline, Reflection, session, shmop, SimpleXML, soap, sockets, SPL, sqlite3, standard, timezonedb, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend Guard Loader, Zend OPcache, zip, zlib

# PHP Settings
max_execution_time - 30
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - -1
max_input_vars - 1000
memory_limit - 128M
post_max_size - 8M
sql.safe_mode - Off
upload_max_filesize - 2M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 7200
soap.wsdl_cache_limit - 5
opcache.max_accelerated_files - 2000
opcache.max_file_size - 0
opcache.max_wasted_percentage - 5
zend_optimizerplus.max_accelerated_files - 2000
zend_optimizerplus.max_file_size - 0
zend_optimizerplus.max_wasted_percentage - 5```

I think that #7895 fixed this issue.
@Hypocrite are you still experiencing this issue with concrete5 8.5.2?


Connect to a node automatically

To connect with the wallet, the user shouldn't need to enter a pool manually to connect.
I think the program should check all the available pools/nodes and connect to the one available with less ping or something.

https://github.com/XDagger/xdag/pull/239


trouble installing with conda

I am trying to install IgDiscover with conda according to the IgDiscover documentation, and have tried several versions of both conda and python, but the environment always fails to solve. Is IgDiscover still supported by conda? Is there a trick to solving the installation?
Thanks,
John

Can you be more specific? Which exact command(s) are you using and which error messages do you get?

This repository is outdated and is going to be archived. Please see the new repository at https://gitlab.com/gkhlab/igdiscover22/ or the homepage at https://www.igdiscover.se/ for the most recent and maintained IgDiscover version.


⚠ TROJAN 🇺🇸 United States USF 1 has degraded performance

In 045cb0a, TROJAN 🇺🇸 United States USF 1 (https://ust-1.optnl.com/) experienced degraded performance:

HTTP code: 200
Response time: 21579 ms

Resolved: TROJAN 🇺🇸 United States USF 1 performance has improved in d3c4ad1.


Camera doesn't start immediately after view is selected

Solved by commit https://github.com/scraptechguy/Cryp2p-ios/commit/2fc63b661bc518302c1618261215032b2a5c5528 Fix camera bug


Partially localized messages when installing

When I installed Bash on Windows, the output was:
-- Beta feature --
This will install Ubuntu on Windows, distributed by Canonical
and licensed under its terms available here:
https://aka.ms/uowterms

Type "y" to continue: y
Downloading from the Windows Store... 100%
Extracting filesystem, this will take a few minutes...
Please create a default UNIX user account. The username does not need to match your Windows username.
For more information visit: https://aka.ms/wslusers
Enter new UNIX username: svick
Zadejte nové UNIX heslo:
Opakujte nové UNIX heslo:
passwd: password updated successfully
Installation successful!
The environment will start momentarily...
Documentation is available at:  https://aka.ms/wsldocs

Notice that all text is in English (including "Enter new UNIX username"), except for the password prompts, which are in Czech ("Zadejte nové UNIX heslo" translates to "Enter new UNIX password").
I would expect the installation to be either fully in English, or fully in Czech, not a mix of the two.
My Windows version is 1607 (OS Build 14393.51) according to winver.
I realize this could be caused by the underlying Ubuntu commands (passwd?), but I thought it's worth pointing out anyway.

Hi @svick. Could you share what locale settings you're running on your PC?

Display Language is English (United States), Input Language is Czech (Czech Republic). Inside bash, locale outputs:
LANG=cs_CZ.UTF-8
LANGUAGE=
LC_CTYPE="cs_CZ.UTF-8"
LC_NUMERIC="cs_CZ.UTF-8"
LC_TIME="cs_CZ.UTF-8"
LC_COLLATE="cs_CZ.UTF-8"
LC_MONETARY="cs_CZ.UTF-8"
LC_MESSAGES="cs_CZ.UTF-8"
LC_PAPER="cs_CZ.UTF-8"
LC_NAME="cs_CZ.UTF-8"
LC_ADDRESS="cs_CZ.UTF-8"
LC_TELEPHONE="cs_CZ.UTF-8"
LC_MEASUREMENT="cs_CZ.UTF-8"
LC_IDENTIFICATION="cs_CZ.UTF-8"
LC_ALL=

The legasy install experience (lxrun) is deprecated.