ParseException: Cannot parse statement: Encountered unexpected token: "exists" "EXISTS"

My code:
	@Test
	public void testJSQParser()
	{
		String sql = "alter table if exists public.table2 rename to table3;";
		Validation validation = new Validation(List.of(DatabaseType.POSTGRESQL), sql);
		List<ValidationError> errors = validation.validate();
		Assert.assertTrue(errors.toString(), errors.isEmpty());
	}

Result:
java.lang.AssertionError: [ValidationError [
statement=alter table if exists public.table2 rename to table3;
capability=parsing
errors=[ParseException: Cannot parse statement: Encountered unexpected token: "exists" "EXISTS"
    at line 1, column 16.

Was expecting one of:

    "ADD"
    "ALGORITHM"
    "ALTER"
    "CHANGE"
    "COMMENT"
    "DROP"
    "MODIFY"
    "RENAME"
]
]]

This statement is a valid PostgreSQL syntax.

Possible not supported.
The supported syntax is: http://<IP_ADDRESS>:8080/jsqlformatter/_static/railroad_diagram.xhtml#AlterExpression
PRs are very welcome.

With JSQLParser 4.2 Snapshot from GIT this test case succeeds:
    @Test
    public void testAlterTableRenameTo() throws JSQLParserException {
        assertSqlCanBeParsedAndDeparsed("ALTER TABLE IF EXISTS table_name RENAME TO new_table_name", true);
    }

Please verify and close the case.

java.lang.AssertionError: [ValidationError [
statement=alter table if exists public.table2 rename to table3;
capability=parsing
errors=[ParseException: Cannot parse statement: Encountered unexpected token: "exists" "EXISTS"
at line 1, column 16.

The validation fails on parsing. Maybe the schema specification in the above statement is the problem?
The validation feature is of course expandable when it comes to syntax validation for rdbms. For my purposes it was sufficient so far.
Additions are welcome!

Validation itself is a very cool feature for JSqlParser, but unfortunately the PRs for new syntactic features nearly never adapt the validation framework. Somehow those new features should be mapped the the supporting databases. Is it possible to get the classes that have no corresponding validation part? If I remember right, the validation itself uses a visitor pattern as well, so would it be sufficient to work on empty body methods?

Validation itself is a very cool feature for JSqlParser,

Agreed.

but unfortunately the PRs for new syntactic features nearly never adapt the validation framework.

Guilty, but there are two challenges here:

not everyone is using this Validator. In fact how wonder how many people DO use it.
it is not transparent how to maintain it and there is no documentation about it

Somehow those new features should be mapped the the supporting databases.

Agreed and I have been thinking about that:

In my opinion, the current implementation is very hard to maintain. Also it struggles from the fact, that Default seems to be True as my example show. Default False would be better because people would complain when testing and then we would activate on demand.
Instead I would like to suggest a kind of Spreadsheet with one Feature as per Row and one RDBMS as per Column, where we can flag each Cell with Boolean/False.
Alternatively we could maybe use Annotations like @SupportsMySQL directly at the Java methods, although I do not know how feasible this is. The big advantage was that maintenance would happen during the implementation of a Feature.

In my opinion. the Validation Rules need to be maintained as close to the SQL Grammar as possible and then the Validator Java Code would need to be auto-generated "somehow".

My need was for a framework with which I can validate SQL scripts that are added to my company's code base as part of the version upgrade mechanism (using Flyway). Our product works with Oracle and PostgreSQL DBs. My intention was to have a unit test that does a static analysis on those scripts based on the unique grammar of each DB. That's how I got to JSqlParser. Unfortunately I see that this kind of use of this library is not common, and that is why the code responsible for the validation functionality was not maintained. Should I look for other solutions?

based on the unique grammar of each DB.

The idea of JSQLParser is to manage all possible SQL syntax of various RDBMS in one Grammar definition.

Unfortunately I see that this kind of use of this library is not common

It is not uncommon, I myself would also have taken a slightly different approach, e. g. defining a) a set of RDBMS which shall be supported and then b) find a way to flag each production for compatibility with a specific RDBMS. But that is only my gut feeling, the chosen approach is great for a lot of other objectives.

and that is why the code responsible for the validation functionality was not maintained.

Why not volunteer and just add the Validator Rules for Oracle and Postgresql? Or set a bounty for other developers? The frame work is there already, all it needs is some fine-tuning now.

Should I look for other solutions?

It is always good to know about options, but I myself came quite late for the party and stayed simply because I did not find anything even remotely as good as JSQLParser. Although I found a few short comings it was not too difficult to dive into the code and fill in what I was interested in myself.
Why not give it a try starting with the RENAME oldName TO newname statement and amend the Validator so it will accept Oracle and reject Postgresql.

Using annotations does not guarantee that they are set for new features.

Very true. There is no silver bullet solution.

My need was for a framework with which I can validate SQL scripts that are added to my company's code base as part of the version upgrade mechanism (using Flyway). Our product works with Oracle and PostgreSQL DBs. My intention was to have a unit test that does static analysis on those scripts based on the unique grammar of each DB. That's how I got to JSqlParser. Unfortunately, I see that this kind of use of this library is not common, and that is why the code responsible for the validation functionality was not maintained. Should I look for other solutions?

You should get it right. The validation extension of JSqlParser is very new. So you cannot say it is not maintained. As @manticore-projects and @gitmotte already mentioned, this extension like JSqlParser itself is feature request driven. So the validation extension as well fits the needs so far and didn't need to be extended. But the implementation should grow with JSqlParser and this step is hard to achieve. This step I was referring to.
@manticore-projects: The annotation support is very tempting, but it should (@gitmotte) not be the only way to define validation rules. I am thinking about it and at the moment see no clear way how and where to put those annotations. The common case in JSqlParser is that one AST - class holds behaviour for multiple RDBMS. So the annotations have to somehow hold a predicate expression.
´´´java
@SupportsMySql( if this condition fits or these fields are set with these specific value ranges )
´´´
Without those expressions, the annotations have only a very limited use case. Unfortunately, JavaCC does not support annotations within the grammar file. It's a pity.
My thinking at the moment goes more in the direction to improve the testing framework, if one can name those five methods a framework :), and automatically run a validation after each assertParseAndDeparse without that validation true fallback and check for not recognized expressions (somehow).  @gitmotte Is that last checking step possible? With this, we could assure, that the validation framework at least processes the "new" change. To ensure completeness I see no right way at the moment.

So you cannot say it is not maintained.

To be fair, it was I who used that term first -- referring to fact, that I indeed largely ignore the Validation Framework when I implement new features.

@manticore-projects: The annotation support is very tempting, but it should (@gitmotte) not be the only way to define validation rules.

I brought it up as an example only. In my opinion, the only chance to maintain the Validation Framework reliably is "as close as possible to the feature implementation".

My thinking at the moment goes more in the direction to improve the testing framework,

Could we not use the Annotations within the toString() methods. We compose the SQL syntax there wit all its elements and so are able to flag the compatibility.
Every new feature will be reflected in the toString(). It is the best maintained part aside the Grammar itself.

As far as I know you cannot annotate parts of expressions within java. You can within the toString method only annotate types. The complete list of annotateable things is I think this:

ElementType.ANNOTATION_TYPE
ElementType.CONSTRUCTOR
ElementType.FIELD
ElementType.LOCAL_VARIABLE
ElementType.METHOD
ElementType.PACKAGE
ElementType.PARAMETER
ElementType.TYPE
ElementType.TYPE_PARAMETER
ElementType.TYPE_USE

So how should an annotated toString method look like? Or do you want to annotate the toString method itself?

without that validation true fallback

What kind of true fallback do you mean?
Validation returns a list of ValidationErrors, if there are no errors placed by the ValidationCapability's, the validation is successful.

Every new feature will be reflected in the toString(). It is the best maintained part aside the Grammar itself.

This is by the way not a very good practice using the toString() method for construction of SQL - snippets. I know many model-classes use toString() for this task, but my opinion is there should be no logic within the model, it should be a POJO. Not for nothing was the deparser also designed with the visitor - pattern; unfortunately not consistently.

What kind of true fallback do you mean?

I assume, it refers to the fact that everything returns VALID unless it has been implemented explicitly.  Like the example above which is supposed to fail on Oracle.
Instead, everything should FAIL unless it has been implemented explicitly and supported by a test.

This is by the way not a very good practice using the toString() method for construction of SQL - snippets. I know many model-classes use toString() for this task, but my opinion is there should be no logic within the model, it should be a POJO. Not for nothing was the deparser also designed with the visitor - pattern; unfortunately not consistently.

I am an accountant and have zero clue about software design and programing. Also I do not want to derail this thread even further. At the same time I hope you will appreciate a friendly sparring:

This is by the way not a very good practice using the toString()
my opinion is there should be no logic within the model
it should be a POJO

Please, why exactly? It keeps things closely together at one place, is simple and efficient. It just works well for its particular problem. What are the practical advantages of this additional abstraction layer? Please give me a real life, actual example where it made things easier or more efficient for a programmer or an end-user.

Not for nothing was the deparser also designed with the visitor - pattern

Please, tell me about it.

unfortunately not consistently.

Although I fully agree on this one. We should use either the Deparser Methods or the toString(). The current code duplication is difficult to understand.
@wumpz: No offense or hard feelings please, I am genuinely interested in this objective discussion and will always put my best effort in following the development policy and guidelines.

So how should an annotated toString method look like?
If we can't use Java Annotations inside a method, then maybe we would need to introduce switch-methods

validFor( RDBMS('Oracle', '12') , RDBMS('MSSQL') , RDBMS('Postgres')  )
validFor( RDBMS('Oracle', '11.2') )
The we can place these calls into the toString() method, like in the example for DROP TABLE IF EXISTS tableName :
    @Override
    public String toString() {
        // Explicitly supported by Oracle since 12 and other RDBMS
        validFor( RDBMS("ORACLE", "12"), RDBMS("MSSQL"), RDBMS("POSTGRES") );

        String sql = "DROP " + type + " ";

        if (ifExists) {
            invalidFor( RDBMS("ORACLE", "11.2") ); // Not supported in Oracle 11.2 and previous versions
            sql += "IF EXISTS ";
        }
        sql += name.toString();

        if (parameters != null && !parameters.isEmpty()) {
            invalidFor( RDBMS("MySQL") ); // Not supported in MySQL
            sql += " " + PlainSelect.getStringList(parameters);
        }

        return sql;
    }

To make that work, each Statement and Expression would have to hold a long compatibilityMask which is set by the validFor() and invalidFor() and can be accessed by the Validator framework.
compatibilityMask == 0 means Invalid on every RDBMS (which should never happen of course).
compatibilityMask == Long.MAX_VALUE means, Valid on every RDBMS.
Also, this compatibilityMask can be used in the Tree: Branches would just AND the values of their Nodes.
This might all be a very stupid idea, but I myself would be able to make it work this way. And I see how I would be able to maintain it reliably and continuously in real life: Whenever something changes, you just add/change the validFor and invalidFor calls of the Statement and Expression.

Or do you want to annotate the toString method itself?

That would work only when we introduce many sub-methods for any IF ELSE block.

What kind of true fallback do you mean?

I assume, it refers to the fact that everything returns VALID unless it has been implemented explicitly. Like the example above which is supposed to fail on Oracle.
Instead, everything should FAIL unless it has been implemented explicitly and supported by a test.

This is by the way not a very good practice using the toString() method for construction of SQL - snippets. I know many model-classes use toString() for this task, but my opinion is there should be no logic within the model, it should be a POJO. Not for nothing was the deparser also designed with the visitor - pattern; unfortunately not consistently.

I am an accountant and have zero clue about software design and programing. Also I do not want to derail this thread even further. At the same time I hope you will appreciate a friendly sparring:

This is by the way not a very good practice using the toString()
my opinion is there should be no logic within the model
it should be a POJO

Please, why exactly? It keeps things closely together at one place, is simple and efficient. It just works well for its particular problem. What are the practical advantages of this additional abstraction layer? Please give me a real life, actual example where it made things easier or more efficient for a programmer or an end-user.

Not for nothing was the deparser also designed with the visitor - pattern

Please, tell me about it.

unfortunately not consistently.

Although I fully agree on this one. We should use either the Deparser Methods or the toString(). The current code duplication is difficult to understand.
.

The problem is that you cannot return false as default, because it is a fact that validations are never complete.
The visitor pattern is based on interfaces whose implementation is thus assured. However, if you provide an empty implementation, then nothing will be validated.
Regarding the toString() method - there are enough examples in the Java world where toString() was used across the board (i.e. BigDecimal.toString() became toPlainString() due to version change) and then became an upgrade issue.
Furthermore, toString() is often emitted by loggers, which can lead to performance and privacy issues.
It is simply that in the software architecture different layers are necessary to create a loose coupling that allows other usage.

What kind of true fallback do you mean?

I assume, it refers to the fact that everything returns VALID unless it has been implemented explicitly. Like the example above which is supposed to fail on Oracle.
Instead, everything should FAIL unless it has been implemented explicitly and supported by a test.

This is by the way not a very good practice using the toString() method for construction of SQL - snippets. I know many model-classes use toString() for this task, but my opinion is there should be no logic within the model, it should be a POJO. Not for nothing was the deparser also designed with the visitor - pattern; unfortunately not consistently.

I am an accountant and have zero clue about software design and programing. Also I do not want to derail this thread even further. At the same time I hope you will appreciate a friendly sparring:

This is by the way not a very good practice using the toString()
my opinion is there should be no logic within the model
it should be a POJO

Please, why exactly? It keeps things closely together at one place, is simple and efficient. It just works well for its particular problem. What are the practical advantages of this additional abstraction layer? Please give me a real life, actual example where it made things easier or more efficient for a programmer or an end-user.

Not for nothing was the deparser also designed with the visitor - pattern

Please, tell me about it.

unfortunately not consistently.

Although I fully agree on this one. We should use either the Deparser Methods or the toString(). The current code duplication is difficult to understand.
.

The problem is that you cannot return false as default, because it is a fact that validations are never complete.
The visitor pattern is based on interfaces whose implementation is thus assured. However, if you provide an empty implementation, then nothing will be validated.
Regarding the toString() method - there are enough examples in the Java world where toString() was used across the board (i.e. BigDecimal.toString() became toPlainString() due to version change) and then became an upgrade issue.
Furthermore, toString() is often emitted by loggers, which can lead to performance and privacy issues.
It is simply that in the software architecture different layers are necessary to create a loose coupling that allows other usage.

I have a lot to respond to that but I do not want to make it look like an argument.
Maybe we want to take that offline or move it into discussions? We share a mutual goal after all: implementing a robust, reliable and easily to maintain Validation framework.

@wumpz: No offense or hard feelings please, I am genuinely interested in this objective discussion and will always put my best effort in following the development policy and guidelines.

No offense here. If a discussion brings a project forward then it is a good one. ( @manticore-projects but as we both unfortunately know, there are exceptions due to behavior :/ )  Again I don't see it as a code duplication but a test framework so to say. And my assumption was, that both (toString, deparser) have their merits while developing. Therefore I kept both.

validFor( RDBMS('Oracle', '12') , RDBMS('MSSQL') , RDBMS('Postgres') )

@manticore-projects @gitmotte Since the logic which expression and even subexpression can be executed on which database or even database version, toString will be (over)polluted. I would prefer the logic outside. I assume that's one of the reasons, the validation framework was developed outside the parse objects.

Regarding the toString() method - there are enough examples in the Java world where toString() was used across the board (i.e. BigDecimal.toString() became toPlainString() due to version change) and then became an upgrade issue.
Furthermore, toString() is often emitted by loggers, which can lead to performance and privacy issues.
It is simply that in the software architecture different layers are necessary to create a loose coupling that allows other usage.

@gitmotte Are you simply saying, that using toString for this SQL construction is wrong? I am following your argument. However, I would not go as far as to put this SQL construction logic into a separate class. But I can see the positive effect of renaming toString to for instance toSql. Then everybody knows what to expect.

The problem is that you cannot return false as default, because it is a fact that validations are never complete.

@gitmotte But then how to force the developer to implement a validation or somehow push him smoothly in the right direction?

Not for nothing was the deparser also designed with the visitor - pattern; unfortunately not consistently.

That's in my opinion the same "validation" development problem. How to force somebody to implement the deparsing consistently? However, here we have the advantage that at least new syntactic features enforce interface changes and with that changes in the deparser.

Again I don't see it as a code duplication but a test framework so to say. And my assumption was, that both (toString, deparser) have their merits while developing. Therefore I kept both.

And so be it. Someone needs to be in charge and define the policies.

toString will be (over)polluted.

Yes, maybe. But toString() is the only place where you understand the full logic at one place (e. g. what is a statement actually doing and what are all the possible variants).
When I wrote JSQLFormatter, the toString() was the place to go to, especially for syntax and RDBMS I am not too familiar with. I was actually surprised how little SQL I know :-D
Writing the Validator will have the same challenge: Defining rules for syntax you are not even aware of.

I would prefer the logic outside. I assume that's one of the reasons, the validation framework was developed outside the parse objects.

We have too many "separations" for my taste already, but ok,  it is decided then.

@gitmotte Are you simply saying, that using toString for this SQL construction is wrong? I am following your argument.

The arguments look dogmatic too me. I still do not understand an actual improvement from that Design Patterns for JSQLParser specifically.

But I can see the positive effect of renaming toString to for instance toSql.

Or to StringBuilder appendTo(StringBuilder builder) maybe? :-D
Joke aside: if we do not use toString() for composing the SQL, what shall toSting() return instead? I mean, after all toString() is supposed to give you the content of the Object -- what if not the SQL was that content please?

The problem is that you cannot return false as default, because it is a fact that validations are never complete.

@gitmotte But then how to force the developer to implement a validation or somehow push him smoothly in the right direction?

I strongly agree with @wumpz  here: a false positive is much worse than a false negative. If a Validation fails because it has not been implemented then there is an incentive to report the issue and to amend the Validation. But if the Validation wrongly succeeds, then the information is wrong and potentially harmful. Compare it with a broken traffic light: would you rather see and endless RED or GREEN signal?

That's in my opinion the same "validation" development problem. How to force somebody to implement the deparsing consistently? However, here we have the advantage that at least new syntactic features enforce interface changes and with that changes in the deparser.

Exactly, the Deparser forces me to implement the features or else the Tests will fail or my Test Coverage would decline. Both would be rejected.
We should think about forcing the implementation of the Validation at least for 4 main RDBMS or else this Validation Tool will always fall behind.

@gitmotte Are you simply saying, that using toString for this SQL construction is wrong? I am following your argument. However, I would not go as far as to put this SQL construction logic into a separate class. But I can see the positive effect of renaming toString to for instance toSql. Then everybody knows what to expect.

That would be much clearer, but it doesn't make the abstraction in context to the deparser any better.
Personally, I don't like to rely on the stability of a toString() method. This often only technically expresses the content of an object, but not a formatted version of the content. To give an example, the strict separation of deparser and model (toString() or toSql()) would allow another implementation of a deparser using a special database syntax. I.e. the square brackets for object names at ms sql-server instead of quotes at other RDBMS.

The problem is that you cannot return false as default, because it is a fact that validations are never complete.

@gitmotte But then how to force the developer to implement a validation or somehow push him smoothly in the right direction?

I think this should happen with the interfaces implemented by visitor objects.
I know the visitor pattern is not very easy to understand, but it is wonderful for traversing an object tree.

Not for nothing was the deparser also designed with the visitor - pattern; unfortunately not consistently.

That's in my opinion the same "validation" development problem. How to force somebody to implement the deparsing consistently? However, here we have the advantage that at least new syntactic features enforce interface changes and with that changes in the deparser.

It's the same problem, yes.
However, from my point of view, a customization consists of 4 steps.

Adjustment of the parser
Adaptation of the model (correct setter and getter, speaking names without abbreviations)
Adaptation of the deparser-visitor objects + unit tests
adaptation of validation (addition of feature names and corresponding validation) + unit tests

The enforcement of these 4 steps can only be done by the project manager, who reviews the addition of all parts before a merge and complains about missing adjustments.

The arguments look dogmatic too me. I still do not understand an actual improvement from that Design Patterns for JSQLParser specifically.

But I can see the positive effect of renaming toString to for instance toSql.

Or to StringBuilder appendTo(StringBuilder builder) maybe? :-D
Joke aside: if we do not use toString() for composing the SQL, what shall toSting() return instead? I mean, after all toString() is supposed to give you the content of the Object -- what if not the SQL was that content please?

The output could be jdbc formatted sql with jdbc parameter placeholders. The current deparsers are only one implementation, there are several ways to format SQL, or to format database specific. With or without parameters, with named parameter placeholders or with jdbc-parameter placeholders. Also an implementation of a deparser, which translates into another language would be conceivable (i.e. HQL, JPQL, translate between RDBMS dialects, ...).

The problem is that you cannot return false as default, because it is a fact that validations are never complete.

@gitmotte But then how to force the developer to implement a validation or somehow push him smoothly in the right direction?

I strongly agree with @wumpz here: a false positive is much worse than a false negative. If a Validation fails because it has not been implemented then there is an incentive to report the issue and to amend the Validation. But if the Validation wrongly succeeds, then the information is wrong and potentially harmful. Compare it with a broken traffic light: would you rather see and endless RED or GREEN signal?

A traffic light is even a bit simple compared to a complex validation (which by the way does not only cover database syntax).
Unfortunately, I can't imagine how to check a "missing implementation", except through interfaces, because an implementation of a validation is never complete.

That's in my opinion the same "validation" development problem. How to force somebody to implement the deparsing consistently? However, here we have the advantage that at least new syntactic features enforce interface changes and with that changes in the deparser.

Exactly, the Deparser forces me to implement the features or else the Tests will fail or my Test Coverage would decline. Both would be rejected.

Testing the deparser is also far easier than testing a validation. Although there may be some formatting differences, it is essentially a string comparison without much logical background knowledge.

We should think about forcing the implementation of the Validation at least for 4 main RDBMS or else this Validation Tool will always fall behind.

That would be fine :)

We should think about forcing the implementation of the Validation at least for 4 main RDBMS or else this Validation Tool will always fall behind.

+1

It's about the definition of Feature's and FeatureSetValidation (Version, DatabaseType).
Only new features need an implementation within the Validator-classes. A new RDBMS to be validated only needs the definition of a new FeatureSet.
public enum DatabaseType implements FeatureSetValidation, Version {

    ANSI_SQL("ANSI SQL", SQLVersion.values()),
    // DBMS
    ORACLE(OracleVersion.values()),
    MYSQL(MySqlVersion.values()),
    SQLSERVER(SqlServerVersion.values()),
    MARIADB(MariaDbVersion.values()),
    POSTGRESQL(PostgresqlVersion.values()),
    H2(H2Version.values());

Personally I like the ANSI_SQL type the most, because it helps to write portable SQL, although this is not supported by all databases either.

Since the Validation framework lacks a maintainer, who keeps up with the features and changes of the Parser I would like to recommend to split it off into its own project, maybe under a multi-project structure (similar JSQLFormatter).
I am closing this and recommend to continue under such a new umbrella.

I think it's @wumpz decision if the feature stays part of the library or not.
Every single maintainer is called to complete all features when adding SQL constructs. Like the "deparser", "validation" is also a feature that must be maintained.
A multi-project structure does not support better maintenance of the feature.
The Visitor pattern in general is not very easy to understand or implement. The design of this library dictates in some way to work with the model in this way.
I haven't looked at how your JSQLFormatter works - I assume this also needs a completion when new SQL constructs are added.


[RFC]: Add @stdlib/string/last

Description
This RFC proposes adding support for returning the last (visual) character(s) of a string.
Signature:
last( str[, n][options] )

where n specifies the number of visual characters to return. Default: 1.
E.g.,
last( 'foo bar' );
// returns 'r'

last( '🐶🐮🐷🐰🐸', 2 );
// returns '🐰🐸'

Package: @stdlib/string/last
Alias: last
Related Issues
None.
Questions
No.
Other
See @stdlib/string/first for a similar package.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

Hey @kgryte ,
If this issue is still to be worked on, I would like to work, please assign.

Sure, will work on it then.

@Pushpendra766 To clarify, please first work on @stdlib/string/base/last, and model after the following package: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/string/base/first

This feature request is actually comprised of multiple new packages, and I advised working on one at a time. The easiest and most straightforward is @stdlib/string/base/last. From there, we can move to the others after you've gotten the first successfully merged.

@Pushpendra766 if you're not working on this might i take this up ?

I would like to work on this once related pr(s) are merged

As @Pushpendra766 has not responded or opened a PR implementing this feature, I'll go ahead and assign @adityacodes30 to pick this up once the base packages are merged.

Hey @kgryte ,
Due to some issues with my system I wasn't able to complete my work on it.
And now that my system is back on track again. Can I continue it ?

@Pushpendra766 I'm sorry to hear that you encountered difficulties. Given recent progress, I suggest picking up another good first issue.


chore: release master

:robot: I have created a release beep boop
core: 0.0.13
0.0.13 (2023-03-24)
Bug Fixes

utils: Include all ts files (#1267) (c284159)

Dependencies

The following workspace dependencies were updated

dependencies

@waku/interfaces bumped from 0.0.9 to 0.0.10
@waku/proto bumped from 0.0.3 to 0.0.4
@waku/utils bumped from 0.0.2 to 0.0.3

create: 0.0.9
0.0.9 (2023-03-24)
Bug Fixes

utils: Include all ts files (#1267) (c284159)

Dependencies

The following workspace dependencies were updated

dependencies

@waku/core bumped from 0.0.12 to 0.0.13
@waku/dns-discovery bumped from 0.0.7 to 0.0.8

devDependencies

@waku/interfaces bumped from 0.0.9 to 0.0.10

@waku/dns-discovery: 0.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@waku/enr bumped from 0.0.7 to 0.0.8
@waku/utils bumped from 0.0.2 to 0.0.3

devDependencies

@waku/interfaces bumped from 0.0.9 to 0.0.10

@waku/enr: 0.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@waku/utils bumped from 0.0.2 to 0.0.3

devDependencies

@waku/interfaces bumped from 0.0.9 to 0.0.10

interfaces: 0.0.10
0.0.10 (2023-03-24)
Bug Fixes

utils: Include all ts files (#1267) (c284159)

@waku/message-encryption: 0.0.12
Dependencies

The following workspace dependencies were updated

dependencies

@waku/core bumped from 0.0.12 to 0.0.13
@waku/interfaces bumped from 0.0.9 to 0.0.10
@waku/proto bumped from 0.0.3 to 0.0.4
@waku/utils bumped from 0.0.2 to 0.0.3

@waku/peer-exchange: 0.0.6
Dependencies

The following workspace dependencies were updated

dependencies

@waku/core bumped from 0.0.12 to 0.0.13
@waku/enr bumped from 0.0.7 to 0.0.8
@waku/proto bumped from 0.0.3 to 0.0.4
@waku/utils bumped from * to 0.0.3

devDependencies

@waku/interfaces bumped from 0.0.9 to 0.0.10

proto: 0.0.4
0.0.4 (2023-03-24)
Bug Fixes

utils: Include all ts files (#1267) (c284159)

utils: 0.0.3
0.0.3 (2023-03-24)
Bug Fixes

utils: Include all ts files (#1267) (c284159)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/utils-v0.0.3 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/proto-v0.0.4 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/interfaces-v0.0.10 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/enr-v0.0.8 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/peer-exchange-v0.0.6 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/core-v0.0.13 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/dns-discovery-v0.0.8 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/message-encryption-v0.0.12 :sunflower:

:robot: Release is at https://github.com/waku-org/js-waku/releases/tag/create-v0.0.9 :sunflower:


BUG Prevent password validator min score producing false negatives

Replaces #7995
Fixes min score failing if no tests are set
Fixes min score failing if there are no failing tests
Adds unit tests to cover the above
Fix up bad phpdoc, code style, linting, and upgrade deprecated API usage

OK - I assume this is a bug in 4.0 as well as 4.1, can we target 4.0 whilst it's still a supported version?

Actually 4.0 is safe; We'd refactored PasswordValidator in 4.1, introducing the bug there.

@dhensby Are you                        happy to merge this?

I am, but does it fully address the initial bug?


Fix #199, Fix #195

@xesscorp, @devbisme, this fix more issues and bugs, but I will waiting to merge this, because the last code merged here is already tested and validated.

This request fix #199, fix #195 and fix #201.


Knowledge graph: add pip version of aws cli

We'd previously removed it, assuming that the preinstalled version was enough,
but commands in the provisioning script only work with the pip version. So we're
re-adding it

OK, I'm going to make it upgrade to AWSCLI 2. So ignore this for now.


Add oVirt platform status

Adding platform status for oVirt to include the ip's needed to implement a self sufficient cluster, which doesn't rely on external DNS services to bootstrap etcd, and to have the kubernetes API reachable to all internal components.
I kept the field names exactly the same as 'baremetal' and gave thought to inheriting them. Since the two platforms will have different needs or at least to avoid coupling I decided to just have ovirt platform specific fields rather than just a base Baremetal struct that I would embed.

/cc @coreydaley @ironcladlou @deads2k PTAL

/close
closing without prejudice to due to age.

@deads2k please re-open and review - I rebased it


mysql start failed and cannot login

Cookbook version
[8.0.1]
Chef-client version
[12.12.15]
Platform Details
[CentOS Linux release 7.1.1503 (Core)]
Scenario:
[
I cannot start mysql-default.service using systemctl start mysql-default.service but i can start mysqld using systemctl start mysqld, and i cannot login mysql using the password which is set in default.rb and the temporary password that i find in /var/log/mysql-default/error.log, output is
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
here is my default.rb
mysql_service 'default' do
port '3306'
version '5.7'
initial_root_password 'abc123'
action [:create, :start]
end
mysql_client 'default' do
action :create
end
]
Steps to Reproduce:
[I only change the package_version from 5.7.11 to 5.7.14 in the line 167 of libraries/helpers.rb]
original
return '5.7.11-1.el7' if major_version == '5.7' && el7?
change after
return '5.7.14-1.el7' if major_version == '5.7' && el7?
Expected Result:
[service can start and i can login mysql]
Actual Result:
[
this is the error.log
2016-08-13T21:07:35.709524Z 0 [Warning] InnoDB: New log files created, LSN=45790
2016-08-13T21:07:35.777542Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-08-13T21:07:35.838951Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generat
ing a new UUID: f584c89a-6199-11e6-a467-005056a1618f.
2016-08-13T21:07:35.842953Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2016-08-13T21:07:35.845906Z 1 [Note] A temporary password is generated for root@localhost: :G9o4NXL((V:
2016-08-13T21:07:38.101575Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.14) starting as process 4153 ...
2016-08-13T21:07:38.128016Z 0 [Note] InnoDB: PUNCH HOLE support available
2016-08-13T21:07:38.128042Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-13T21:07:38.128047Z 0 [Note] InnoDB: Uses event mutexes
2016-08-13T21:07:38.128050Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-08-13T21:07:38.128054Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-13T21:07:38.128057Z 0 [Note] InnoDB: Using Linux native AIO
2016-08-13T21:07:38.128287Z 0 [Note] InnoDB: Number of pools: 1
2016-08-13T21:07:38.128406Z 0 [Note] InnoDB: Using CPU crc32 instructions
2016-08-13T21:07:38.129904Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2016-08-13T21:07:38.137577Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-08-13T21:07:38.139593Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of se
tpriority().
2016-08-13T21:07:38.154821Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-13T21:07:38.187585Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2016-08-13T21:07:38.187740Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2016-08-13T21:07:38.230025Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2016-08-13T21:07:38.238414Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2016-08-13T21:07:38.238437Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2016-08-13T21:07:38.239964Z 0 [Note] InnoDB: Waiting for purge to start
2016-08-13T21:07:38.290171Z 0 [Note] InnoDB: 5.7.14 started; log sequence number 2524886
2016-08-13T21:07:38.290689Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql-default/ib_buffer_pool
2016-08-13T21:07:38.292538Z 0 [Note] Plugin 'FEDERATED' is disabled.
2016-08-13T21:07:38.316721Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160813 17:07:38
2016-08-13T21:07:38.334943Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and p
rivate key
2016-08-13T21:07:38.334969Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2016-08-13T21:07:38.336888Z 0 [Note] IPv6 is available.
2016-08-13T21:07:38.336928Z 0 [Note]   - '::' resolves to '::';
2016-08-13T21:07:38.337025Z 0 [Note] Server socket created on IP: '::'.
2016-08-13T21:07:38.443703Z 0 [Note] Event Scheduler: Loaded 0 events
2016-08-13T21:07:38.443909Z 0 [Note] Execution of init_file '/tmp/mysql-default/my.sql' started.
2016-08-13T21:07:38.503305Z 0 [Note] Execution of init_file '/tmp/mysql-default/my.sql' ended.
2016-08-13T21:07:38.503448Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.14'  socket: '/var/run/mysql-default/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
2016-08-13T21:07:38.928891Z 0 [Note] Giving 0 client threads a chance to die gracefully
2016-08-13T21:07:38.928986Z 0 [Note] Shutting down slave threads
2016-08-13T21:07:38.929008Z 0 [Note] Forcefully disconnecting 0 remaining clients
2016-08-13T21:07:38.934730Z 0 [Note] Event Scheduler: Purging the queue. 0 events
2016-08-13T21:07:38.934863Z 0 [Note] Binlog end
2016-08-13T21:07:38.944479Z 0 [Note] Shutting down plugin 'ngram'
2016-08-13T21:07:38.944527Z 0 [Note] Shutting down plugin 'partition'
2016-08-13T21:07:38.944572Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2016-08-13T21:07:38.944580Z 0 [Note] Shutting down plugin 'ARCHIVE'
2016-08-13T21:07:38.944598Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-08-13T21:07:38.944754Z 0 [Note] Shutting down plugin 'MRG_MYISAM
]

We dropped all these hardcodes in 8.1.0 so this shouldn't be an issue any longer.


Question about Prior

Hi, thanks for the code I learned a lot by reading your code especially the reinforcement learning one.
In the code I saw that you use prior during prediction, is there any reason why or any resource I can look at to?
Thanks :)

You are welcome. The prior is usually used for overfitted models in practice. In this case, I used relatively small dataset and did not use augmentation techniques. Therefore, using the prior information helped for this case.

Got it, thanks!!


Error when pressing Record

On Windows 10, selecting Live Recording with default settings and working microphone input bars, pressing Record, generates an error dialog box titled Buzz with content "An error occurred while loading the Whisper model: A connection error occurred. Please retry or check the application logs for more information."
I can't find any application logs for more information.
The PC is stand-alone w/o internet access.

To work Buzz needs to download model files. You need to download them on some PC with internet and then move to the PC without the internet.
See Help -> Preferences -> Models to download and find where the model files should be placed.
Advanced preference for model folder may also be useful to you https://chidiwilliams.github.io/buzz/docs/preferences#advanced-preferences


Debugger Session

Hello,
I see the process opens port 7777 on loopback interface. Connecting via telnet or web browser fails.
Is there a method to access this debugging console? Is it documented anywhere?
Connecting To localhost...Could not open connection to the host 127.0.0., on port 7777: Connect failed

While the game world is playing and there is a running browser within the engine, you may access http://localhost:7777 to access the developer tools

I'm running a PIE session with a active browser session (Fully initialized and texture is rendering). The port is Listening so I assume it is in a good state. However connecting to 7777 via browser or telnet gives a connection refused.
Windows 10
BLUI 3.1
Unreal Engine Version: 4.9.2-0+++depot+UE4-Releases+4.9

Restart the editor and check the log to see if CEF had any issues trying to bind to that port

Restart of editor and started in debug session shows zero errors regarding CEF/Blu. Only worthwhile entries:
LogBlu: Component Initialized
LogBlu: Loading URL: blui://WebUI/CNC/index.html
LogBlu: Load Local File: file:///C:/Users/Paul/Perforce/paultech_windows/WebUI/CNC/index.html
I'll double check everything on my end and see if I recreate on another setup.
Thanks

Able to replicate problem on different computer with similar version information.
Does BLUI have its own log file or method to trigger more verbose logging? Currently very little is logged on any kind of failure.

Most of the logging is done by CEF itself. As BLUI just acts as a wrapper for things.
I can't seem to replicate this issue on any of my dev machines. I can access the developers tools just fine.
You can enable more verbose CEF logging using this line:
BluManager::settings.log_severity = LOGSEVERITY_VERBOSE;


Tell golang about memory limit and allow it to manage the 2 cores itself

Set GOMEMLIMIT to ca 95% of actual limit to allow for a bit of overhead by the system
Same as #299 but based on main

With this GOGC can be adjusted or turned off altogether also, but this will be cheating against any other go app defaults, so probably not a good idea for comparable benchmarks cc @antonputra
GOMEMLIIMT will trigger GC when needed, so GOGC can be turned off now in practice

Thanks @Kavantix for the PR and @sshilko for the feedback. I'll keep it as a reference, and when I have time, I'll try different GC settings.


Update CODEOWNERS

Fix codeowners to correct group name

@Redback-Operations/tutors could you please review?


Question: What makes Aider work so well in comparison to others?

Issue
I'm curious why aider is working so well, for editing files specifically. I understand there is a repo map feature which does seem novel, but what else is going on under the hood? I've tried GptEngineer, Amazon Q, AutoGPT, and open-interpreter, this repo seems to be the most useful and effective by far. I may need to retry these alternatives and make sure I'm using Claude 3.5 Sonnet but the aider workflow does seem more productive.
As a follow-up, I'm curious what could we do to improve it further? Outside of improving the actual LLM model? I noticed this website has some benchmarking rankings: https://www.swebench.com/ so perhaps one of the other repositories is also doing something novel that aider is not.
Version and model info
No response

Thanks for trying aider and filing this issue.
The aider blog has a number of articles that describe some of the things that help aider work well.
https://aider.chat/blog/

I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


User friendly query builder for grafana table panel

Building a cross-metrics table in Warpscript is achievable, but very costly.

What do you call a cross-metrics table?

Hi hbs, I need to build a table with different metrics (price, volume) or combo of metrics (unit price) per column, so x-metrics.

Let's take the discussion on Warp 10's Google Group rather than in this
issue :-)
On Fri, Nov 30, 2018 at 6:46 PM fredduwez<EMAIL_ADDRESS>wrote:

Hi hbs, I need to build a table with different metrics (price, volume) or
combo of metrics (unit price) per column, so x-metrics.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ovh/ovh-warp10-datasource/issues/30#issuecomment-443283122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcXqh0pEJh85KogteBX7YHPW8_qeCV9ks5u0W8OgaJpZM4Y7sZM
.

--
[image: SenX] https://senx.io/
Mathias Herberts
SenX Co-Founder & CTO
+33 6 15 16 19 07 <+33615161907>
55, rue Charles Nungesser
29490 Guipavas - France
http://us.linkedin.com/in/herberts http://twitter.com/herberts
http://github.com/hbs


:bug: Removed mariadb restart check in certRotation test.

What this PR does / why we need it:
Removed mariadb restart check in certRotation test. Because we do not run any tests with mariadb for 1.2 release.

/test-ubuntu-integration-release-1-2
/test-centos-e2e-feature-release-1-2

/manifestlint
/unit

/retest

/test-ubuntu-integration-release-1-2

/lgtm


dropout rate in train and predict

I find that in train_c3d_ucf101.py dropout is 0.5, while in predict_c3d_ucf101.py dropout is 0.6, can you explain why ?  @hx173149

Hi @xudejing
I have try this value from 0.5 to 1.0 in predict process, and it can not make a meaningful difference, so 0.6 maybe just a debugging value

I think during prediction, the dropout rate need to be 1, otherwise the activations are changed for layers applying dropout every time since dropout has a probability. if we use the model as a feature extractor., it is unstable.

你好
是的，如果是拿来做特征提取用1.0确实会比较稳定，但是如果直接是用来做end to end的输出，在我测试的收 0.5-1.0 的效果都差不多。。。。

好的~

看到中文好亲切


zcUtils.lua:532: attempt to concatenate field '?' (a nil value)

Interface\AddOns\Auctionator\zcUtils.lua:532: attempt to concatenate field '?' (a nil value)
VERS:3.2.2 MEM: 1064 KB DB:39 SE:0 SL:2 FSCHUNK: DBVERS:4
REALMS: , Korgath_Alliance (22), Arygos_Alliance (0), Kil'jaeden_Horde (0), Kel'Thuzad_Alliance (39)
STACK: ItemIDStrfromLink > Atr_OnNewAuctionUpdate > Atr_EventHandler > ClickAuctionSellItemButton > Atr_ClickAuctionSellItemButton
ADDONS: , Auctionator, BagBrother, Bagnon, HandyNotes, MasterPlanA, Postal, Recount, Skada, DBM
Reported by http://www.curse.com/users/sweetwineandroses on 8/7/2015
http://www.curse.com/addons/wow/auctionator?comment=5624

This was reported for version 3.2.2; current version 3.2.4.  Closing until re-reported with current version; the line numbers are not aligning with a line that could throw this error.


Fix styles for job history view

Fix stat reporting for failed dependent jobs
Fix duration for stats if job executes "instantly"

@aimeemorgan PR

Forgot to add something else.  Will update after I test


能在windows上复现吗，安装causal-conv1d==1.1.1会报错怎么解决

我的windows上也遇到这个问题

We apologize that we don't reproduce LightM-Unet on Windows temporarily. Could you please provide the error logs for the current issue you are facing? This will help us better pinpoint the problem.

你好我用自己的数据集在在显卡12g，16g内存下，在U-mamba能训练不报cuda oom 错误，但是在LightM-Unet会cuda oom，请问怎么处理？

Hello, I use my own data set under the 16g memory of the graphics card. If I change the batchsize to 2, it will cause cuda oom in LightM-Unet. How to deal with it?
2024-04-25 09:17:44.026392: unpacking dataset...
2024-04-25 09:17:44.497184: unpacking done...
2024-04-25 09:17:44.497184: do_dummy_2d_data_aug: False
2024-04-25 09:17:44.528434: Unable to plot network architecture:
2024-04-25 09:17:44.528434: No module named 'hiddenlayer'

Hello, I use BRaTS2021 dataset under the 16g memory of the graphics card.Have you delt with it? Thanks！


Discovery caching with file_cache is unsupported

Hey everyone, this is a follow-up related to https://github.com/googleapis/google-api-python-client/issues/1490 and https://github.com/googleapis/google-api-python-client/issues/299.
If I understand correctly, discovery_cache.file_cache is broken (since it relies on oauth2client<4.0.0 which is deprecated) and there is no way of using the discovery cache currently (outside of app engine environments), right?
This is far from optimal, especially for a current project of mine, where API client objects are built frequently with different credentials - and I'd definitely prefer to avoid unnecessary discovery requests.
Do you have a plan/ strategy for supporting file_cache again in the future? If not, I'd suggest simply copying the oauth2client.contrib.locked_file module over to this repository. It is self-contained and thus should be fairly easy to maintain. Would that be a workaround you'd consider acceptable?
Cheers, Peter

In version 2.x of this library, a new feature was added to build clients using a cached copy of discovery artifacts.
The new feature is captured in the README (link below)
https://github.com/googleapis/google-api-python-client?tab=readme-ov-file#version-20-release
Discovery documents will no longer be retrieved dynamically when you call discovery.build(). The discovery documents will instead be retrieved from the client library directly.

See the Migration Guide below which includes code samples
https://github.com/googleapis/google-api-python-client/blob/main/UPGRADING.md#200-migration-guide
This solution should work as long as the service and API version appear in the static discovery document directory here: https://github.com/googleapis/google-api-python-client/tree/main/googleapiclient/discovery_cache/documents
Please can you clarify if you require any discovery documents which are not in that directory?

In version 2.x of this library, a new feature was added to build clients using a cached copy of discovery artifacts.
The new feature is captured in the README (link below) https://github.com/googleapis/google-api-python-client?tab=readme-ov-file#version-20-release
Discovery documents will no longer be retrieved dynamically when you call discovery.build(). The discovery documents will instead be retrieved from the client library directly.

See the Migration Guide below which includes code samples https://github.com/googleapis/google-api-python-client/blob/main/UPGRADING.md#200-migration-guide
This solution should work as long as the service and API version appear in the static discovery document directory here: https://github.com/googleapis/google-api-python-client/tree/main/googleapiclient/discovery_cache/documents
Please can you clarify if you require any discovery documents which are not in that directory?

I think @peterkappelt was talking about cache_discovery while you've described static_discovery.
One way to solve this issue on your own is to add a custom implementation of Cache and use it as the cache argument of the googleapiclient.discovery.build function.


FLINK-13302][table-planner] DateTimeUtils.unixDateCeil returns the same value as unixDateFloor does

What is the purpose of the change
Fix a bug in DateTimeUtils.unixDateCeil & keep sync with calcite
Brief change log

Fix unixDateCeil
Fix related unit test cases

Verifying this change
This change is already covered by existing tests
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Travis passed: https://travis-ci.com/flink-ci/flink/builds/119598057
Merging


[SPARK-34487][K8S][TESTS] Use the runtime Hadoop version in K8s IT

What changes were proposed in this pull request?
This PR aims to use the runtime Hadoop version in K8s integration test.
Why are the changes needed?
SPARK-33212 upgrades Hadoop dependency from 3.2.0 to 3.2.2 and we will upgrade to 3.3.x+.
We had better use the runtime Hadoop version instead of having a static string.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the K8s IT.
This is tested locally like the following.
KubernetesSuite:
...
- Launcher client dependencies
- SPARK-33615: Launcher client archives
- SPARK-33748: Launcher python client respecting PYSPARK_PYTHON
- SPARK-33748: Launcher python client respecting spark.pyspark.python and spark.pyspark.driver.python
- Launcher python client dependencies using a zip file
...

Test build #135319 has started for PR 31604 at commit a8ecb70.

Test build #135319 has finished for PR 31604 at commit a8ecb70.

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

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39899/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39899/

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

Thank you, @HyukjinKwon . For 2.7.x, it's difficult because we need to find the corresponding aws-java-sdk.

I landed this test PR to branch-3.1 for K8s GA, too.


SUGGESTION: Recalculate vectors after adding new extensions

Currently, an entity object has a vector representation.
If an extension is added via the c11y endpoint, it would be great if the vector representations are re-calculated if the word(s) of the extension are/is part of the entity.
Maybe there should be an option to disable this.
POST /v1/c11y/extensions

{
  "concept": "Winlogon Helper DLL",
  "definition": "foobar",
  "weight": 1,
  "reindex": false // <== default = true
}

Extention of this request.
Take the following example where two new concepts are added.
POST /v1/c11y/extensions

{
  "concept": "bazbaq",
  "definition": "An example to explain what an foobarqaz is",
  "weight": 1
}

POST /v1/c11y/extensions

{
  "concept": "foobarqaz",
  "definition": "An example to explain this issue and often used in combination with a bazbaq",
  "weight": 1
}

Note how the first addition contains foobarqaz which is an unknown word. However, after adding the second word, it should know this word.
What I would like to propose is:

If a concept contains a word that it previously couldn't index, but now can, should be reindexed.
If a thing or action contains a word that it previously couldn't index, but now can, should be reindexed.

Any thoughts @etiennedi ?

Friendly nudge @etiennedi

@bobvanluijt How would you solve circular dependencies?

@fefi42 How would you solve circular dependencies?

It doesn't (yet) the goal is to start the discussion, especially with the custom DB this becomes interesting to have as a functionality.
Feel free to add suggestions to this issue ;-)


Added extra check in reshape for shapes whose less is less than 2 (#15200 fix)

Link to Github Issue
Problem description:
Due to a tiling check in ReshapeViewOperation::invoke which indexes -2 index of the shape of the tensor, the check fails if the shape rank is 1, this MR just adds an additional check.
What's changed
Added an additional check in ReshapeViewOperation::invoke

Wait sorry I just realized that this will also cause an issue in the new this_is_view check just before. To avoid needing a second PR could you change the this_is_view equation? I will write in a reply the new equation

Wait sorry I just realized that this will also cause an issue in the new this_is_view check just before. To avoid needing a second PR could you change the this_is_view equation? I will write in a reply the new equation

Wait sorry I just realized that this will also cause an issue in the new this_is_view check just before. To avoid needing a second PR could you change the this_is_view equation? I will write in a reply the new equation

First please merge in my changes when I added the view op, then modify my this_is_view check as follows.

Wait sorry I just realized that this will also cause an issue in the new this_is_view check just before. To avoid needing a second PR could you change the this_is_view equation? I will write in a reply the new equation

Wait sorry I just realized that this will also cause an issue in the new this_is_view check just before. To avoid needing a second PR could you change the this_is_view equation? I will write in a reply the new equation

First please merge in my changes when I added the view op, then modify my this_is_view check as follows (with colons rather than commas, sorry for the bad syntax

@jvegaTT I have added the checks as you have wrote. However, I still got the error when trying to reshape 1-dimensional tensors, as it falls down to the PerformView path (the error is: Alignment should have at least 2 dimensions for Tile layout). So I added an additional check to let it falls to the catch-all path convert_tensor_to_rm_reshape_convert_back_to_orig_layout and tested if it works. Let me know if this is ok, thanks!

That's not good. To give you context the OP is about 1000 times faster when this condition is taken. Can you investigate a little bit to see if there is an easy fix? If not we can let this PR through but please raise a github issue and assign me to it to resolve it.


Support all toolbar modes

flexible
waterfall
waterfall with fixed last row

Also update the Content component to match MDC spec in how to specify
that it is being used with a fixed toolbar.
Update toolbar demo to show all the possibilities.

thank you. Merged !


Update index.php

Image path not correct

Hello. Thank you for using and contributing in this tiny project. Could you please explain why should we have to use Yii::$app->homeUrl instead of relative url ? Would be awesome if you provide me some examples when existing approach doesn't work.

relative path show e.g: localhost/img/awesome.png but actually path is localhost/app/frontend/web/img/awesome.png

The template contains 2 nodes. The backend and the frontend. You have to configure your webserver and link 2 different domain names to the backend/web folder and the frontend/web folder. The "web" folders are web-roots of the backend and the frontend parts of the system.


Fix inline record printing in outcome printer

This fixes #1163 and supersedes #2103

@jordwalke rebased on master.


Update dataloader explanation code

Hello! I was using this recently so I thought of updating the docs.
This PR is intended to update the code example provided in the book (#518) to a newer version of the dataloader.
I also copied a bit of the explanation given in https://github.com/graphql/dataloader and created another PR to update the example repository https://github.com/jayy-lmao/rust-graphql-docker/pull/5
Let me know if this is useful or if I need to change anything.

Looks great! Thanks for the PR and the video and the demo repo 🍻

Thanks to you guys for this awesome project. Cheers! :beers:


inputData in Batch missing

The definition of inputData in the batch processing section is missing.  How to load from a CSV would be helpful.

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

ID: 30e7cf89-1a90-7693-db50-11b770c09160
Version Independent ID: 21c26fd2-c6ad-2c2f-166b-03ac0590a1c2
Content: Make predictions with a trained model - ML.NET
Content Source: docs/machine-learning/how-to-guides/machine-learning-model-predictions-ml-net.md
Product: dotnet-ml
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

Hi @bjstigall,
Thank you for the suggestion. For brevity purposes and since the topic of loading data has already been covered in the Load Data how-to, the definition and process of loading this data into an IDataView was deliberately omitted from this sample. I do think it might be confusing and have added a note explaining the source of inputData as part of #12925. I hope that answers your question.


Sidebar change color schema doesn't work

I have free-vue-admin current v 4.1.0
Running in VS code on Windows 11 using Chrome v 99.0.4844.74 (Official Build) (64-bit)
From docs, https://coreui.io/vue/docs/components/sidebar.html, I can clearly see Sidebar property "color-scheme" with possible values "dark or light". By default it's "dark" and works fine. But if I add "color-scheme='light'" it doesn't change the scheme color. Moreover it throughs erros in the console: "Uncaught TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'." "color-scheme='dark'" will through the same error in the console. Only without specifying "color-scheme"  at all, property errors won't be seeing and the theme will be dark which I'd like to change to light.
Could somebody clarify what property and what values should I use to get Sidebar working light scheme???

@vsirghii the light version is available only in PRO version

Thanks @mrholek, sometime later, somewhere from your docs pictures I've got a clue that this might be about PRO/FREE versions difference. Just an idea: if you had in the component descriptions something like color-scheme (PRO), it would eliminate further questions


Path regex isn't working

I'm trying to create an auto group pattern based and a path.
My site looks like this -
https://www.domain.com/tasks/?t=
I've tried using this pattern -
https://*.domain.com/tasks
This is the way it was shown to be used in the patterns page https://developer.chrome.com/docs/extensions/mv3/match_patterns/
But it didn't catch my urls.
I've tried a few other options and none of them worked

Ok, after checking your tests here I found an option that work.
This is the pattern I used that worked - *.www. domain.com/tasks
This type of pattern isn't detailed in the chrom regex pattern matching examples. It might be worth to create a specific page of your own.

Hey Maya, thanks for your feedback. (And sorry for coming back to you so late — seems I had accidentally unwatched my own repo. 😓)

I've tried using this pattern - https://*.domain.com/tasks

This will work for https://domain.com/tasks or https://www.domain.com/tasks, but since you have specified a URL path (/task) in your pattern, it requires the tab's URL to match that exactly, so whatever comes after that (/?t= in your example) causes the non-match.
Using https://*.domain.com/tasks* should work for you here. (You also can omit the HTTPS prefix, just for convenience: *.domain.com/tasks*.)

This is the pattern I used that worked - *.www. domain.com/tasks

I'm not quite sure I exactly understand the pattern you used. That one includes... a space, if I'm taking this correctly? This should definitively never work. Is this the exact pattern you used? (Please consider re-posting it with backticks, I'm suspecting GitHub's markdown renderer to have done funny things to your original pattern...)

This type of pattern isn't detailed in the chrom regex pattern matching examples. It might be worth to create a specific page of your own.

As mentioned above, this kind of pattern is not even supposed to work, so it probably wouldn't be documented anyway. That said, the extension's pattern evaluator does diverge from the match patterns documentation in subtle ways (mostly to enable extra scenarios that match patterns wouldn't allow for), but those should be edge cases not affecting your situation. However, I've already had auto-group-tabs.com registered for a while, and I'm planning to put some extended documentation there — but I'm not sure when I'll have the resources (time, mostly) for doing this and how to prioritize it with other feature requests for the extension.


[AIRFLOW-1571] Add AWS Lambda Hook

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1571

Description

[x] Here are some details about my PR, no UI changes

Details of this PR are in the Jira above.
Tests

[x] My PR adds the following unit tests

test_aws_lambda_hook
This unit test uses moto to mock aws lambda. Firstly, we create a lambda function (assuming this function is already created by aws cloudformation template in production). Secondly, we trigger lambda function using invoke function in the hook. Lastly, we parse the response and assert statements.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2570 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2570      +/-   ##
==========================================
- Coverage   70.91%   70.88%   -0.04%
==========================================
  Files         150      150
  Lines       11595    11595
==========================================
- Hits         8223     8219       -4
- Misses       3372     3376       +4

Impacted Files
Coverage Δ

airflow/jobs.py
77.67% <0%> (-0.37%)
:arrow_down:

Continue to review full report at Codecov.

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

@artwr @criccomini seems like you guys reviewed similar AWS related PR - https://github.com/apache/incubator-airflow/pull/1630
Would be great if you could help review my PR. Any inputs are welcome (this is my first contribution to airflow) :)

Please make sure your commits are merged into one.

@bolkedebruin resolved commits. thanks

Closing this PR - its a duplicate of https://github.com/apache/incubator-airflow/pull/2718


[Feature] make sure all data send before task finish

Description
[Feature] make sure all data send before task finish
Use case
[Feature] make sure all data send before task finish
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

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

no need for this feature anymore


1 Project kickstart with SemVer Explainer

Document SemVer
Best practices for Issues, PR and Tags.

Squashed to have cleaner GitHub History!

I'll rename the commit to match the issue number..

The only commit. https://github.com/yaya2devops/terraform-beginner-bootcamp-2023/commit/e984c0907ede1f5885204e28414b8b52d4054f22
That has no direction to the issue.
For a great reason.
To get your attention on this.


Right sytnax for using user specific sqitch.conf path + verify?

According to documentation, to provide a specific .conf file to sqitch config --file is to be used, but when i do:
sqitch config -f ./path_to_sqitch.config verify errors out with No section given in key: verify for what i guess is wrong way of using config + deploy/verify..status command.
Is this possible to do at all?

-f (or --plan-file) points to the plan file, not the configuration file. If you want to use a specific configuration file, set the appropriate environment variable.


docs: fix typo

Summary
closes #531
Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[x] I have updated the documentation.
[ ] I have added tests to cover my changes.

Thank you .


Updating maps after rework: Chalet, Skyscraper and maybe House

Current status:
Chalet & Skyscraper: images & thumbnail, objectives, ladders, cameras incl. LoS, hatches, drone tunnels and spawn points were updated, labels (and maybe new camera images) are missing
House: New images, nothing else updated yet.

I've finally been able to check out your changes. It looks good, except it looks like the labels are misplaced somehow. It doesn't look like they're just shifted - it looks like they were set for a different zoom or something?

I've finally been able to check out your changes. It looks good, except it looks like the labels are misplaced somehow. It doesn't look like they're just shifted - it looks like they were set for a different zoom or something?

I didn't update the labels yet. They're still at their old position. I just don't have the time currently to finish it, but I will continue working on it in February.
I just wanted to notify you and other contributors that I already updated some things so we won't do the same work twice.

I didn't update the labels yet. They're still at their old position. I just don't have the time currently to finish it, but I will continue working on it in February.
I just wanted to notify you and other contributors that I already updated some things so we won't do the same work twice.

So, I just finished both Chalet and Skyscraper.
Status: The labels are in the correct locations now and the cams will display the correct (new) image now.
What doesn't work: The maps are not in the right location, i. e. when loading them, they are in the lower right corner of the screen by default.
Example:
--------------------------
|                        |
|                        |
|          --------------|
|          |   <MAP >    |
--------------------------

This is not a big problem, as you can move the map, but it is a problem.
I have no idea what could be the reason for this, though ...

So, I just finished both Chalet and Skyscraper.
Status: The labels are in the correct locations now and the cams will display the correct (new) image now.
What doesn't work: The maps are not in the right location, i. e. when loading them, they are in the lower right corner of the screen by default.
Example:
--------------------------
|                        |
|                        |
|          --------------|
|          |   <MAP >    |
--------------------------

This is not a big problem, as you can move the map, but it is a problem.
I have no idea what could be the reason for this, though ...


Error importing the Visibility and Range toolbox

When you try to import the Visibility and Range Tools_10.3.tbx you get a syntax error from some internal script.

Open Python prompt in ArcCatalog/ArcMap/etc.
arcpy.ImportToolbox("Visibility and Range Tools_10.3.tbx',"VandR")

'''

arcpy.ImportToolbox(r'C:\Users<user>\Documents\GitHub\solutions-geoprocessing-toolbox\visibility\toolboxes\Visibility and Range Tools_10.3.tbx',"VandR")
Runtime error
Traceback (most recent call last):
File "", line 1, in
File "c:\program files (x86)\arcgis\desktop10.3\arcpy\arcpy_init_.py", line 124, in ImportToolbox
return import_toolbox(input_file, module_name)
File "c:\program files (x86)\arcgis\desktop10.3\arcpy\arcpy\toolbox_code.py", line 440, in import_toolbox
mymodule = generate_toolbox_module(toolbox, None, False, False, False, module_name, use_alt_alias)
File "c:\program files (x86)\arcgis\desktop10.3\arcpy\arcpy\toolbox_code.py", line 414, in generate_toolbox_module
'exec')
File "C:\Users<user>\Documents\GitHub\solutions-geoprocessing-toolbox\visibility\toolboxes\Visibility and Range Tools_10.3.tbx", line 561
def RadialLineofSight-MultipleTowers(Input_Surface=None, Force_visibility_to_infinity=None, Defensive_Position_Feature_Class=None, Defensive_Position_Description_Field=None, Defensive_Position_Height_Field=None, Output_Workspace=None, Output_Prefix=None):
^
SyntaxError: invalid syntax

'''

Fixed this one in building HLZTouchdownPointsTestCase.py. The toolbox was corrupted and the paths to the script tools were broken. Had to manually rebuild the TBX and copy the doc/properties over.


[dotnet] Update changelogTemplate for GitHub releases

Closes #2372

The following are linked on the README:

https://github.com/dotnet/core/blob/main/release-notes/6.0/6.0.13/6.0.13.md
https://github.com/dotnet/core/blob/main/release-notes/7.0/7.0.2/7.0.2.md

So perhaps https://github.com/dotnet/core/blob/main/release-notes/__RELEASE_CYCLE__/__LATEST__/__LATEST__.md


Serialization / Compose / KSP: NullPointerException during compileKotlinJs in mpp project with AndroidTarget

Describe the bug
Serialization / Compose / KSP: NullPointerException during compileKotlinJs in mpp project with AndroidTarget
Affected platforms
Select one of the platforms below:

Web (K/JS) - Canvas based API
iOS

Versions
android studio 2022.2.1
kotlin 1.8.20
compose-jb 1.4.0
kotlin serialization 1.5.0 plugin 1.8.20
ksp 1.8.20-1.0.10
jdk 17
For details, please refer to: https://youtrack.jetbrains.com/issue/KT-58000

It's probably related to this one #2635

Yes, I made a mistake before. After making the necessary changes, it will be ready
compose {
    //kotlinCompilerPlugin.set("androidx.compose.compiler:compiler:$composeCompilerVersion")//old
    kotlinCompilerPlugin.set("org.jetbrains.compose.compiler:compiler:$composeCompilerVersion")//new
}

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


add some results based on segnet.

Hi, i add results to README.It's time to sleep.

Hi they look great for 40 epochs! MaxPool really makes a huge difference!
I uploaded the images to GitHubs upload service so people don't have to download alle the image data when they clone the repository.
Thanks for helping out and good sleep!


Select dropdown in the form could have an option to  preview the user entered values

Is your feature request related to a problem? Please describe.
In the form editor the select dropdown does not show any default/preview values unlike the radio button for which the values are entered.
Describe the solution you'd like
In the Form editor, the Select dropdown and the radio button are two fields where the values could be labelled and entered. But unlike the radio button on entering the values and labelling them does not have any effect on the Select dropdown as there is no preview available in the editor and we could not see until the form is deployed.
It would be nice if we could display a preview as like the radio button for the select dropdown as well.
Additional context
https://user-images.githubusercontent.com/85225325/132761510-ecb49628-f385-408f-873e-587afed7c6d2.mp4
It would be nice to have an implementation similar to radio button.

Thanks for bringing this one up @GeethaParthasarathy. Moving the issue to the backlog for the moment.


label onclick event doesn't work on iOS 7

When label has for attribute, onclick event doesn't fire.
Without for, works fine. But checkbox doesn't get checked.
<input id="checkbox" type="checkbox">
<label for="checkbox" onclick="console.log('Hi')">label</label>
<script>FastClick.attach(document.body);</script>

FastClick.js version 1.0.2.

@BYODKM
You marked this closed, but the thread does not make clear what is best / recommended solution, thanks.

None of the solutions here is working for me. Doesn't look like a closed issue.

Check for other use of label attribute in JS or CSS. Even changed width of label can cause problems

@genyklemberg Thanks!

@BYODKM why did you close this? Was this fixed?

@OscarGodson Nothing. But you can't fix this. This is a ground rule of JavaScript as @genyklemberg mentioned.

I don't think that's what he pointed out, or if it is, It's not a ground rule of JS. If you remove fastclick and write one-off code I can get this to work pretty easily since that's default browser behavior on touch devices. I just don't know how to integrate into FastClick's code base.

@OscarGodson I think this is because of FastClick's nature, label onclick is a collision course. Sorry, but I have to say "Just don't".

So, what is the best solution?

I wrote about the same issue I had here: http://www.tjcafferkey.me/problems-clicking-input-label-select-ios-safari/
The fix I put in was simply
label > * { pointer-events:none; }

FWIW, there's still an issue in which for example if the <label> has a styling on :hover it will remain styled after the user taps again to uncheck a checkbox:

So the only solution is to have no styling on the <label> on  small screen device and then add it at a certain breakpoint for large screens.
Bummer 😞


Integration/Compatibility with Pieconomy

Suggestion:
Pieconomy's Github
I understand that this plugin isn't released yet but it would be fantastic if the needed additions to the plugin on your side was already in place before Pieconomy's release. It looks like it just needs a stopper in place if inventory space doesn't exist.

This plugin runs a few edge cases you don't expect to see in economy plugins. Player accounts can and will return ResultType.ACCOUNT_NO_SPACE. They can even return that when withdrawing, due to the making of change. They can even return that, but be successful on a larger amount, due to a full inventory but non-full stacks. Server accounts can report a balance, and successfully withdraw a balance, but return ACCOUNT_NO_SPACE if you try to put it back again due to the currency not being allowed on that account. They can also have negative values on any given currency.

However, I still have no idea how Contexts work, or what they even mean, so I ignore them completely.

Can you please elaborate on the what the issue is / what I need to implement? I don't quite understand the issue.

From what Pie says, It's up to whatever plugin does the economy request how to handle a lack of space for money. (copied and pasted from his github for Pieconomy. It looks like a stopper will need to be put in place on the main eco plugin's side if a player does not have the required space for the items his plugin generates.
It looks like his plugin will be sending out a message: "resultType.ACCOUNT_NO_SPACE" if the inventory is full and I assume your (and others) plugin will need to look for that messsage and send an error to the player saying they cannot pay them due to a full inventory or such.

So you are saying that Pieconomy requires a main economy plugin to function? To me this disclaimer is for plugins such as a shop plugin that require an economy plugin to function.

For some crazy reason I was thinking this was a bolt on that would let another plugin manage the currency and it just convert it to items.
Please forgive me for wasting your time with this. I'll close this suggestion..

No worries! I understand why you thought that.


Analyze and rework CPU tests

We have a number of issues reported against CPU test suite, where the final conclusion was that this is test environment issue, not a firwmare issue. This shows low quality of this suite. This issue aims to gather such tickets, and track the progress of improvements in the test environment.
Tickets:

https://github.com/Dasharo/dasharo-issues/issues/343

Regarding getconf -a | grep CACHE returning info with missing data on: NS70MU, NS51MU.
Not displaying the info about cache is not FW issue - rather an OS issue.
Same behavior can be observed on MSI PRO Z690-A DDR4 with Ubuntu

Or NovaCustom NV41PZ with Fedora:
LEVEL1_ICACHE_SIZE                 65536
LEVEL1_ICACHE_ASSOC
LEVEL1_ICACHE_LINESIZE             64
LEVEL1_DCACHE_SIZE                 32768
LEVEL1_DCACHE_ASSOC                8
LEVEL1_DCACHE_LINESIZE             64
LEVEL2_CACHE_SIZE                  2097152
LEVEL2_CACHE_ASSOC                 16
LEVEL2_CACHE_LINESIZE              64
LEVEL3_CACHE_SIZE                  12582912
LEVEL3_CACHE_ASSOC                 8
LEVEL3_CACHE_LINESIZE              64
LEVEL4_CACHE_SIZE
LEVEL4_CACHE_ASSOC
LEVEL4_CACHE_LINESIZE```

However in the case of NovaCustom machine the CPU does not have L4 CACHE at all - this is why no info is displayed.
Tests do not check for L(X) level cache if particular key is set. However test might malfunction if no value (like for example '0') is provided in the output and set cache level amount is checked.

I can add a sanity check for value in the output. Or rework test to use `lscpu` which display cache info like:
![image](https://github.com/user-attachments/assets/523d941e-4829-4b4e-9f11-278482877b62)
or
![image](https://github.com/user-attachments/assets/2663fd14-0532-4c53-8cf5-18d228762585)

Other way is to use util like cpuid:
![image](https://github.com/user-attachments/assets/c477db63-7f80-432c-a361-29c060424c37)
However last method might have issue with reliability as category for non existent cache level is displayed but empty.


Formatter doesn't update styles in connected Server and Channels

If the font is updated when connected, the Server or Channels aren't subsequently updated

https://github.com/matty-r/urChat/issues/76

Fixed with eacaa9c


How to authenticate on pouchdb client with Ionic 2?

Hello,
I'm really new to working with authentication and databases. I was able to follow the readme and the demo fairly well.
I think the answer to my question is somewhere between:
new SuperLogin(config, passport, userDB, couchAuthDB) and the directions below it and the "Client Access Token for Cordova"
I'm working on an offline first Ionic 2 application. I'll be using PouchDB and syncing with Cloudant. I have the "getting started" script on a server.js file on Node. My "Sign Up" form in Ionic does a http.post request to /auth/register. Its so awesome to see the user get added to the sl-users database and see the personal DB get setup.
I need to connect the dots on authenticating a user in pouchdb then syncing the databases.
Any help would be much appreciated. At this setup, I need help with the login() function which I know will need to connect to a pouchdb in a service.
`    var express = require('express');
var http = require('http');
var bodyParser = require('body-parser');
var logger = require('morgan');
var cors = require('cors');
var SuperLogin = require('superlogin');
var app = express();

app.set('port', 3000);
app.use(logger('dev'));
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(cors());

var config = {
  dbServer: {
    protocol: 'http://', /* https:// */
    host: 'localhost:5984', /*'username.cloudant.com',*/
    user: 'user',
    password: 'password', /*'pass'*/
    // cloudant: true,
    userDB: 'sl-users',
    couchAuthDB: '_users'
  },
  mailer: {
    fromEmail<EMAIL_ADDRESS>    options: {
      service: 'Gmail',
        auth: {
          user<EMAIL_ADDRESS>          pass: 'userpass'
        }
    }
  },
  userDBs: {
    defaultDBs: {
      private: ['supertest']
    }
  },
  providers: { local: true }
}

// Initialize SuperLogin
var superlogin = new SuperLogin(config);

// Mount SuperLogin's routes to our app
app.use('/auth', superlogin.router);

http.createServer(app).listen(app.get('port'));

`
Login.ts
`import {Component} from '@angular/core';
import {NavController, MenuController} from 'ionic-angular';
import {DashboardPage} from '../dashboard/dashboard';
import {Http, Headers} from '@angular/http';
@Component({
  templateUrl: 'build/pages/login/login.html',
})
export class LoginPage {

  public newCreds: Object;

  constructor(public http: Http, public nav: NavController, public menu: MenuController) {
    this.menu.enable(false);

    this.newCreds = {
      name: '',
      username: '',
      password: '',
      confirmPassword: ''
    }

  }

  login(){
    this.menu.enable(true);
    this.nav.setRoot(DashboardPage);
  }

  SignUp(newCreds){

    //connects to express server and uses superlogin to create a new user and user database!

    let body = JSON.stringify(newCreds);
    let headers = new Headers();

    headers.append('Content-Type', 'application/json');

    this.http.post('http://localhost:3000/auth/register', body, {headers: headers}).subscribe(data => {
      console.log("success");
    }, error => {
      console.log(JSON.stringify(error.json()));
    });
  }
}`

I haven't yet worked with Angular2 yet, but you can see exactly how to set things up server-side with SuperLogin-Demo. As far as client-side code you may be able to use SuperLogin-Client.
I would definitely welcome the creation of an Angular2 version of NG-Superlogin.

This might help a lot.
http://www.joshmorony.com/part-2-creating-a-multiple-user-app-with-ionic-2-pouchdb-couchdb/

Thanks! I actually reached out to him prior to that and he was able to help me... I'll close this.

Does anyone have a working version of ionic2 -> superlogin using with social authentication? The joshmorony blog above is excellent but it does not cover logging in using social.


Detect shadow clones for git plugin to avoid reading a wrong date range (which first year being wrong)

git rev-parse --is-shallow-repository which will print false (not shallow) or true (shallow):
See #240 for a use case and problem.

I took a quick look at this yesterday, it seems JGit does expose some information that may allow detecting shallow clones without having to shell out to git at all but I didn't get to the point of being able to actually test that
One problem is that if people are using the plugin in their CI environments then they're almost always going to do a shallow clone.  Therefore the plugin will pretty much always fail CI if they are trying to use the new Copyright Existence Years feature (#240) in conjunction with CI.
It may warrant documenting this as an explicit limitation as well as applying any code fixes

I use this in CI all the time, it does require some special handling, mainly just checking out the branch that is being run when this is needed to run.  I know recently some documentation was added due to the release plugin being changed to shallow cloning that simply cannot be gotten around.  But this certainly can work on a shallow clone by checkout out the associated branch along with a fetch to know about the branches beforehand.  So its really shallow plus a bit of foo processing but not deep.  The reason I do this specificially is that I have it automated in case a developer forgets to run the plugin before committing ;)  So it can be done and I agree special needs would need documented as such.

I took a quick look at this yesterday, it seems JGit does expose some information that may allow detecting shallow clones without having to shell out to git at all but I didn't get to the point of being able to actually test that

Huh, I looked and didn't see this, so I did the shell version in #253.  Could you point me to where that was, @rvesse ?
Also, an alternative option to detecting shallow --> fail/skip, is explicitly executing git fetch --unshallow (or a Jgit equivalent) in the cases where either of the file-creation substitution patterns are used.

@dbwiddis In the constructor of GitLookup the code already calls this.repository.getObjectDatabase().newReader().getShallowCommits() which according to the comments there is a workaround for a concurrency bug in JGit.  That actually returns a Set<ObjectId> which could be stored and then later consulted to see whether a given commit is shallow
But like I said I've no idea if that actually works reliably as a way to detect shallow clones

That actually returns a Set<ObjectId> which could be stored and then later consulted to see whether a given commit is shallow

Wow, I had seen that line but ignored it as a "workaround".  In fact that Set<ObjectId> is exactly the contents of .git/shallow, so an empty set means unshallow.  I'll update my PR.

Related: The contents of .git/shallow (and thus the same ObjectId's in the set) are the hashes of the "oldest" commits on each branch.
So if iterating from HEAD (which we do for year of last change) we could stop when we reached that commit.  However, for any single file (other than files involved in that commit) it could be skipped over in iteration.  We could in theory compare timestamps but there is no requirement for commits to be chronological.
And if we iterate from the oldest commit (which we do for creation author/email and year of creation) we wouldn't ever see it anyway.

Typo in issue title shadow vs shallow?


Character deletion/input is flaky

Just had a play around with the demo (https://msafi.github.io/text-mask/), especially with the US phone number with country code demo.
Replication steps:

Enter 2 (input box shows "+1 (2  ) -")
Delete 2 (input box goes back to placeholder)
Enter 1
Use backspace key to remove the 1 (box does not go back to placeholder, the 1 remains
Use the delete key (not backspace), see the input box keep adding 1s until the mask is filled.

Ah, thanks for this bug report @madmatt. There are a couple of issues there that I need to fix.

Fixed in #135 and new versions published to npm.


Revert event wait functions back to immutable

Also adds the new mutable versions as _mut

I don't know why, but the functions were changed so I assumed that somebody needed that functionality...

@torkleyy Sorry for the delay in replying here: the examples don't really build after that change?


While training first TensorFlow neural net model

I build tensorflow for Mac OSX from sources following the Download and Setup guide from tensorflow.org.
$ which python
/usr/local/bin/python
$ pip --version
pip 8.1.2 from /usr/local/lib/python2.7/site-packages (python 2.7)

Created the pip package and installed it with NO GPU support.
$ bazel build -c opt //tensorflow/tools/pip_package:build_pip_package

$ bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

# The name of the .whl file will depend on your platform.
$ sudo pip install /tmp/tensorflow_pkg/tensorflow-0.10.0rc0-py2-none-any.whl

When attempting to Train first neural net model from the root of the source tree:
$ cd tensorflow/models/image/mnist
$ python convolutional.py

Extracting data/train-images-idx3-ubyte.gz
Extracting data/train-labels-idx1-ubyte.gz
Extracting data/t10k-images-idx3-ubyte.gz
Extracting data/t10k-labels-idx1-ubyte.gz

Traceback (most recent call last):
  File "convolutional.py", line 326, in <module>
    tf.app.run()
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/platform/default/_app.py", line 30, in run
    sys.exit(main(sys.argv))
  File "convolutional.py", line 243, in main
    batch = tf.Variable(0, dtype=data_type())

TypeError: __init__() got an unexpected keyword argument 'dtype'

This keyword argument has been available since https://github.com/tensorflow/tensorflow/commit/60dfe8852cfd9565e622e423098bdad746dc3aee, which includes TensorFlow versions 0.8 and later.
Can you try the following at a Python shell and report the results?

import tensorflow as tf; print tf.__version__
help(tf.Variable)

>>> import tensorflow as tf; print tf.__version__
0.7.1

You'll need to upgrade your version of tensorflow to 0.8+, or check out the source code at the 0.7.1 tree, not master.


feat: compatibility with pydantic v2.x.y

What was the problem/requirement? (What/Why)
Pydantic version 2 was released, and contains pydantic v1 as a submodule. This change allows this library to function with both major versions of Pydantic; it will automatically select the v1 submodule if v2 is available in the environment.
What was the solution? (How)
Try to import the v1 module from pydantic v2, and fallback to pydantic v1 if that fails.
What is the impact of this change?
Downstream consumers will be open to use Pydantic V2 at any time without needing to wait for this library to be updated.
How was this change tested?
Using a hatch shell, I ran the test suite with both pydantic v2.3.0 and then again with v1.10.11 installed (via pip install --force).
Was this change documented?
N/A
Is this a breaking change?
No, quite the opposite.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing in favour of an upcoming PR. Pydantic 1.10.17+ contain the pydantic.v1 namespace to make v2 compatibility much easier to do.


Publicly release LAMMPS compiled to WebAssembly

[ ] When done benchmarking, publish the results in a blog post (or other medium)
[ ] Finalize Dayeong's LAMMPS fork on github with clear instructions on how to compile it to webassembly
[ ] Put up a public, proof-of-concept webpage that runs LAMMPS in a browser (doesn't need to have visualization or UI - it could just run a fixed input every time)

This would be awesome.


Update Issue - 63948737

default description
URL tested: http://ci.bsstag.com/welcome
Open URL on Browserstack

Property
Value

Browser
Chrome 38.0

Operating System
Windows XP

Resolution
1024x612

Screenshot Attached
Screenshot URL

Click here to reproduce the issue on Browserstack

Updated Screenshot Attached


Typo in title

Typo in title

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

ID: 8ddde2ac-52eb-ddcf-cb89-bcbda8ab925c
Version Independent ID: a4c41bfe-8a6b-cf05-6875-09e85aa1736e
Content: Find machine information by interal IP API
Content Source: windows/security/threat-protection/windows-defender-atp/find-machine-info-by-ip-windows-defender-advanced-threat-protection.md
Product: w10
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@chbreakthrough, Thank you for pointing it out and have since fixed it.


Please add a changelog and 2.0.0 tag

Hey, thanks for this nice package! I’m in a bit of a crunch though, because I need to update from v1.1.2 to v2.0.0 due to a problem with chunk-manifest-webpack-plugin peer dependencies. Can’t figure out what changed though.
Judging by the semver bump there was a breaking change. What was it?
Two things would help greatly: adding a changelog (you can find some good tips at http://keepachangelog.com/en/1.0.0/) and tagging the commits at which you published the package.
Thanks again!

Good that you reminded me about the changelog, thank you. For now I can let you know here:
What was changed that I forked webpack-chunk-manifest-plugin, so it's now a part of this plugin. I removed the bits from the dependency plugins that were complete overlaps, and made sure the chunk manifest wasn't written to chunks anymore (which was the reason why I never moved to webpack-chunk-manifest-plugin v1.1.2).
The reason for the major bump was because the plugin doesn't support webpack 1 anymore. Which I never had tested if it did in the first place. For consuming the plugin, nothing has changed.

Created a v2.0.0 release:
https://github.com/jouni-kantola/inline-chunk-manifest-html-webpack-plugin/releases/tag/v2.0.0
With that, closing the issue.

Awesome! Thanks so much for the quick action on this. The changelog at https://github.com/jouni-kantola/inline-chunk-manifest-html-webpack-plugin/releases looks lovely and very clear!
Thanks again!