World locked on first login

hi, the plugin looks great, excellent work!
I have a problem... when I log in with a new account and I receive the message "Your Account was generated." You cannot interact with the world, as if it were protected, this is solved by re-entering the server with the message "We loaded your Data, you can now play."
I don't know if this problem is due to natural behavior of the plugin, some interference with another plugin (although I tried removing all of them), or a user permissions problem.
I tried to follow the code, for example in the JoinListener.java class to see if there was something that would block entities but I did not find the problem
The plugin is configured with MongoDb
I am running it on paper 1.20.1

Hello there,
do which version of MySQL-Sync do you use?
~ leo

The same thing happened at our house.
It's not a problem when the server has just started up, but it seems to happen when (no one) has been logged in for a long time.
Re-logging in or moving the server again will cure the problem.
PaperMC 1.21 #40
Velocity #400
MariaDB V15.1
MySQL-Sync 1.4.14

After a number of attempts, we found that it is likely to be due to MySQL timeouts.
Reproduction methods include
You can check this immediately by setting MySQL's wait_timeout to 10 seconds.
Alternatively, restart MySQL and you can check it immediately in-game.

The same thing happened on our server.
It's not a problem when the server has just started up, but it seems to happen when (no one) has been logged in for a long time.
Re-logging in or moving the server again will cure the problem.
In the player's connection log when the phenomenon occurs.
[11:52:34 INFO]: [MySQL-Sync] §aConnected to the MySQL
This is speculation, but it may be related to reconnection after a DB server timeout or something like that.
After a number of attempts, we found that it is likely to be due to MySQL timeouts.
Reproduction methods include
You can check this immediately by setting MySQL's wait_timeout to 10 seconds.
Alternatively, restart MySQL and you can check it immediately in-game.
PaperMC 1.21 #40
Velocity 3.3.0 #400
MariaDB V15.1
MySQL-Sync 1.4.14

Can confirm that this happens all the time, and does confuse a lot of players.

Hello federkone, RuaWing and Hezkore,
thank you for messaging me about this problem. Now that I have more Informations about it, I will look deeper into the problem.
Will update you three as soon, as I have a update.
~ Leo


Back navigation won't work on Android

I've noticed that, on Android:

When moving from a screen to another, not only the back button won't be shown (as reported on #2023), but also the physical back button will put the app in background instead of leading to the previous screen.
When the app is put in foreground again, the initial screen is rendered, instead of previously opened screen.

All of these issues can be reproduced using the Example project.

Sorry, I'm actively looking for Android contributor right now because I'm working on iOS app only.

A workaround for the Android hardware back button closing the app is to use react-native's BackHandler. Would be something like this:
Docs are here: https://facebook.github.io/react-native/releases/0.45/docs/backhandler.html
import React, { Component } from 'react'
import { BackHandler } from 'react-native'
import { Actions } from 'react-native-router-flux'

export default class Page extends Component {
  constructor (props) {
    super(props)
  }

  componentDidMount () {
    BackHandler.addEventListener('hardwareBackPress', () => this.backAndroid()) // Listen for the hardware back button on Android to be pressed
  }

  componentWillUnmount () {
    BackHandler.removeEventListener('hardwareBackPress', () => this.backAndroid()) // Remove listener
  }

  backAndroid () {
    Actions.pop() // Return to previous screen
    return true // Needed so BackHandler knows that you are overriding the default action and that it should not close the app
  }

  // ...other stuff
}

Thanks for the fast reply, @aksonov and @hofuchi! I'm going to take the day to investigate this issue a bit further.
Considering the current scenario, my initial hypothesis is that the scenes aren't being stacked correctly on Android. It would explain why it can't identify where to go when the app is put back in foreground and also won't pop when expected (or show the back button on header).
Do you think that this is a valid approach? 😊

Yea that might help explain some things, console.log(JSON.stringify(Actions.state)) should help determine which scenes are stacked where

Again, thanks for you help, @hofuchi! I'm already working on it. It seems that the initial issue displaying the back button is related to its positioning, as aksonov initially suggested on #2023.
The scenes are being correctly stacked, so the physical back button problem on android is something else. I hope to submit a pull request soon. 😄

Hey guys, I've just submitted a pull request with a fix for the issue #2023. It seems that, even though different from v3, it's expected that the back button action on android is going to be implemented by the user when using react-navigation (at least, this is what I could take out of this thread).
Following what was suggested by hofuchi and here, I'm handling the physical back button with:
import React, { Component } from 'react'
import { BackHandler } from 'react-native'
import { Actions } from 'react-native-router-flux'

class App extends Component {
  constructor (props) {
    super(props);
  }

  componentDidMount () {
    BackHandler.addEventListener('hardwareBackPress', this.onBackPress);
  }

  componentWillUnmount () {
    BackHandler.removeEventListener('hardwareBackPress', this.onBackPress);
  }

  onBackPress () {
    if (Actions.state.index === 0) {
      return false;
    }

    Actions.pop();
    return true;
  }

  // ...
}

@diegocouto We could also add it to v4 ('App' component within src/Router.js), could do you submit PR?

@aksonov Sure, I'm glad to help!

@diegocouto did you check it with Example app?

@quarryman Yep! It should look like this:

@diegocouto  are you on master?

Just did clean install on master and buck button is still not there

@quarryman Example doesn't use master branch but latest beta, are you sure that you are using master?

@aksonov that was the issue.
It works after switching example router dependency to master
Do you think it makes sense to merge this fix into beta branch not to confuse new users trying example app.
It will at least prevent this issue reports from being submitted by those who try example.
@diegocouto thanx for a fix

The Actions.state.index always has the same value. This solution does not work for me.

I solved this way:
<Router backAndroidHandler={this.onBackPress}>
and:
onBackPress = () => {
    if (Actions.state.index === 0) {
      return false
    }
    Actions.pop()
    return true
}

In  "react-native-router-flux" version ( 3.41.0 )
You can use ActionConst.RESET to exit the app from any Component.
import { Router, Scene , ActionConst } from 'react-native-router-flux'
<Router>
    <Scene duration={0} key="main" type={ActionConst.RESET}>
</Router>

backAndroidHandler does not work for me. the function is never called

@ecavalcanti  this solution puts the app in background. any idea about this?

const onBackAndroid = () => {
return Actions.pop();
};

How do you exit app without shutting app down?  I think I have tried all the above combinations.
Anytime I return false from either the router backAndroidHandler or the React Native BackHandler, my app disappears and closes completely.  I do not want this.  My user may be in the middle of uploading or downloading and this kills the process.
When I try to resume, I see the splash screen so I know it is restarting from scratch.
Anytime the app the back handler returns false the app is shut down and closed completyely.
      <router  backAndroidHandler={this.routerBackAndroidHandler} />

  routerBackAndroidHandler = () => {
    const result = Actions.pop();
    console.log('dbg: Actions.pop()', result);

    // returning false will close app completely
    return true;
  }

Using:
		"react": "^16.2.0",
		"react-native": "^0.52.2",
		"react-native-router-flux": "4.0.0-beta.27",

I think this is because of Android behaviour.
On my end : When I exit the app with the backButton because my route stack is empty, the app exits but is not killed. If I come back quickly to the app, I will still be on my latest screen (which for me is a home page (with a type reset)).
If I open a new app or wait a bit, the app will start again from the beginning.

@Blapi A MainActivity.java fix was the only thing that prevented app from terminating.
import android.content.Intent;

public class MainActivity extends ReactActivity {

  // Prevent back button from terminating app
  // https://github.com/react-navigation/react-navigation/issues/1372#issuecomment-299432731
  @Override
  public void invokeDefaultOnBackPressed() {
    moveTaskToBack(true);
  }

Nice info to know, thanks

Firstly my BackHandler works fine, but when i'm on Home screen (consider as one or last screen) the app actually navigating to Sign in page(it's throwing the user out of application)
Below are my files
### AppNavigatorContainer.js
class AppNavigatorContainer extends Component {
addListener = createReduxBoundAddListener("root")
constructor(props) {
super(props)
this.state = {
didReceiveNotificationThatCanBeHandled: false,
notification: null,
didNetworkBecomeUnreachable: false
}
this.onBackPress = this.onBackPress.bind(this)
}
componentWillReceiveProps(nextProps) {
//TODO: Uncomment once VPN problem is fixed
// if (nextProps.isNetworkReachable !== this.props.isNetworkReachable) {
// this.state.didNetworkBecomeUnreachable = !nextProps.isNetworkReachable
// }
}
componentWillMount() {
BackHandler.addEventListener('hardwareBackPress', this.onBackPress)
}
componentWillUnmount() {
BackHandler.removeEventListener('hardwareBackPress', this.onBackPress)
//TODO: Uncomment once VPN problem is fixed
// stopListening()
}
onBackPress() {
console.log(this.props);
const { dispatch, navigationState } = this.props
dispatch(NavigationActions.back());
return true;
}
AppNavigator.js
import React from 'react'
import {
StackNavigator,
addNavigationHelpers
} from 'react-navigation';
import stackConfiguration from './stackConfiguration'
import routeConfiguration from './routeConfiguration'
export const AppNavigator = StackNavigator(
routeConfiguration,
stackConfiguration
);
export default ({
dispatch,
navigationState,
addListener
}) => {
return (
<AppNavigator navigation={addNavigationHelpers({
dispatch,
state: navigationState,
addListener
})} />
)
}

In "react-native-router-flux" version ( 3.41.0 )
You can use ActionConst.RESET to exit the app from any Component.
import { Router, Scene , ActionConst } from 'react-native-router-flux'
<Router>
    <Scene duration={0} key="main" type={ActionConst.RESET}>
</Router>

Hy, I want to know that if I use your way it works through the app?

I solved this way:
<Router backAndroidHandler={this.onBackPress}>
and:
onBackPress = () => {
    if (Actions.state.index === 0) {
      return false
    }
    Actions.pop()
    return true
}

Thanks @ecavalcant IT WORKS FOR ME. IM USING ROUTER FLUX V-4.0.1(STABLE). KEEP IT BRO  GOD BLESS YOU. :)


UI Improvement

Hey, I want to change the "READ MORE" button UI and if I hover the social icon then the hover background is not working. Also, the horizontal scrollbar is not looking good so I remove it.
You can see here,

Please assign it to me under GSSOC'23.

Please assign it to me under GSSOC'23.


README and CI changes

I would like to continue to improve the README and in-code documentation in addition to getting around to updating the Guardian lesson on Elixir School.

I haven't had enough time to look into it but I would really like to figure out a way that we could leverage GH Actions to ship new release to Hex whenever someone updates the version in mix.exs.

Codecov Report

Merging #636 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #636   +/-   ##
=======================================
  Coverage   86.81%   86.81%
=======================================
  Files          22       22
  Lines         455      455
=======================================
  Hits          395      395
  Misses         60       60

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 8c2248a...aa8dbad. Read the comment docs.


Allow :mime_type & :ext to be magic attributes

This is simply to permit *_mime_type and *_ext attributes to be assigned from the magic attributes. Should cause no harm?
And why?
For example some audio players require mime-type to playback the file correctly in all browsers.

this seems to break things (for example the ext method), closing for now

out of interest, what breaks? I didn't think it would

ah the method #ext would clash.

Somehow file file.ext stopped working when I add this.
I am trying to allow users to change the name of a file, but if they forget to add extension things break. Hmm …

And fetching the original name from meta is slow …

the ideal is to use the "name" magic attribute (add a xxx_name column), then the method .ext will come from that

yes that's what I have
but if you change that name and forget to add .pdf, the mime_type etc. is lost as it is inferred from that name …
obviously I could have another attribute (custom_name) and juggle between the two …

So these are 2 separate concerns I think:

magic attributes for _ext and _mime_type which are much helpful in many cases
dealing with updated to the _name attr

yeh seems that way.
re. the second one, magic attributes are really supposed to be read-only (as they're a kind of cache), so maybe the better solution is just use a different column for the user-defined name

How to solve the _ext issue? I am happy to amend my pull-request if you have an idea?
Okay, i think that makes sense for the second one.

the idea I guess is that you don't need an ..._ext column if you're using ..._name as both .name and .ext will come from this cached name

true. and in fact mime_type as well.
ok
thanks mark!

yeh exactly. no probs

@markevans I have one more long-term question I am trying to figure out. Sorry for asking here, but perhaps you might have a suggestion.
Let's say I have an attachment assigned via a standard app, without any specific processors. Is there a clean way how could I 'decorate' the same attachment with different app?
Let's say I would like to use different dragonfly app (for example for pdf processing) to render a thumbnail for a file in general Dragonfly app. How would you recommend to go about this? In most cases I have separate apps that I assign on upload (general file, audio, image, pdf, …), but unfortunately there are exceptions (general file might be a pdf which I would like then to render thumbnail for) …
Thank you in advance.

not sure if this answers your question but there's no harm in registering a specific processor, e.g. pdf_to_thumb, for a general app, and only using it if the file is a pdf, i.e. (somewhere)
asset.pdf_to_thumb! if asset.format == 'pdf'

or whatever.
If you tried to use it on a non-pdf file it would just fail with the appropriate exception

That's the solution I am using now. Was wondering if there's smth cleaner …


[CS2103T-T13-4] CallMeMaybe

CallMeMaybe helps telemarketers to easily catalog the contacts that need to be called/have been called. It is optimized for CLI users so that frequent tasks can be done faster by typing in commands.

Codecov Report

Merging #2 (fab8090) into master (ba53b8c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 ba53b8c...fab8090. Read the comment docs.


Issues Connecting to Instance

I'm having troubles connecting to my Looker instances with gzr. I was successfully able to connect to our trial Looker instance, but our companies instances I keep getting the following error:
ERROR: Connection Failed. Did you specify the --no-ssl option for an ssl secured server?
I include --no-ssl when I try to connect and get the same error. Any suggestions on what the connection problem could be and how to fix it?

We figured out the issue. It was actually an issue with the way our ports were set up so it wasn't able to access the API. Thanks for the help though!


Using CodeID for numerical and multi-categorical data

I was unsure whether to open this as a github issue or not, so please pardon me if it should be put elsewhere.
In our typological database there are two kinds of data we are keeping track of that are not simple categories. The first is numerical data (e.g., maximum number of consonants in coda, number of genders, etc). While I could create a CodeID for each discrete value in our dataset, this seems to me to break the idea of what a number is. I am currently putting the number value directly into the CodeID column in the values table. This seems unsupported, however, or if it is supported I could not find documentation explicitly making sure it was okay.
The second issue is similar: For some of our data, we allow a list or multiset from a discrete list of categories. An example is the set of semantic classes (kin, body parts, animals) for which a possessive construction can be used (this is useful for keeping track of what is in and out of alienability classes). We can list the set of classes in CodeID but it is not clear if it is supported to list multiple CodeIDs in the values table. As of right now, this is what I am doing, and I am separating the CodeIDs with semicolon <;>.
Both of these seem like valid use cases for linguistic data but it is not clear if they are supported by the formalism (if so, can this be documented? and if not, I humbly request their support) nor if they break downstream applications like CLLD.

@davidainman It's absolutely appropriate to post this as issue here! This is the kind of stuff that should be in an FAQ at some point.

Regarding your first question (I'll be using the term names from the ontology rather than the default column names): The codeReference column can be nullable, i.e. you can have values in your dataset, which do not reference a row in CodeTable. For these, you could put the number simply in the value column. You could even specify the datatype for the value column to be integer. But this may not be appropriate for other parameters in your dataset. But since these typed value columns are not specified by CLDF, a generic CLDF consumer would only look at strings in value, and would need to get the type information "out-of-band".
That's a bit of a weak spot in CLDF: Having parameters with different types of values in the same dataset is somewhat difficult - or rather requires a trade-off between full transparency and usability. For full transparency, you'd have to add typed columns to the ValueTable for each type - so the value for parameters with integer values would go into Value_int, or similar, while the value for parameters with dates as values would go into Value_date. A string representation of the values of any type could then go into the standard value column. Maybe some sort of specification of valid values in the ParameterTable would be a good candidate for CLDF 1.2.

Regarding the second question: multi-valued reference properties are supported in CLDF. So if you have a parameter "SemanticClasses", and rows in the CodeTable listing these classes, you could declare the codeReference column multivalued - by specifying a separator property (which seems what you have done?). Alternatively, you could just add multiple rows to ValueTable, each linked to just one code. While this would mean some duplication, it could also be appropriate, e.g. if you have separate sources for each link between construction and a single semantic class.

Here's an example how D-PLACE deals with the problem of parameters with different value types: the ParameterTable specifies a column datatype, which provides "out-of-band" (i.e. non-CLDF-standardized) info how to interpret the values:
https://github.com/D-PLACE/dplace-cldf/blob/bca2e2de714aecc91d25c9b97aeb48ae15433c1d/cldf/StructureDataset-metadata.json#L297-L340)
The CodeTable only lists codes for the parameters specified as "categorical".

I could imagine a solution similar to the D-PLACE example above to be part of the CLDF spec. Maybe a bit more sophisticated, though, e.g. a column
{
    "name": "datatype",
    "datatype": "string",
    "dc:format": "text/json"
}

in the ParameterTable, where the column content would be a CSVW datatype description in JSON, e.g.
{"base": "integer", "minimum": 0, "maximum": 20}

CLDF consumers could then use this datatype spec to read the data properly:
>>> from csvw.metadata import Datatype
>>> import json
>>> dt = Datatype.fromvalue(json.loads('{"base": "integer", "maximum": 20}'))
>>> dt.read("17")
17
>>> dt.read("24")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/robert_forkel/projects/cldf/csvw/src/csvw/metadata.py", line 343, in read
    return self.validate(self.parse(v))
  File "/home/robert_forkel/projects/cldf/csvw/src/csvw/metadata.py", line 339, in validate
    raise ValueError()
ValueError

@Anaphory @chrzyki @LinguList @SimonGreenhill what do you think about the "datatype" column sketched above? Too implicit or ad-hoc or weird (with JSON as column content in CSV)?

Independent of where to store the data type – this still doesn't make it very easy to store and properly handle closed-class and open-class data together, does it?
If I understand you correctly, even with this addition it would still require two different columns for

the codes that are taken from a finite, parameter-dependent set and have their own metadata (eg. the decision tree to code YES vs. NO) in a CodeTable and
the open-class values, such as counts, that may have different data types specified using this suggested scheme.

Side remark: If we take ‘value’ to be the thing reported in some source, it's also not clear how to store data if the source claims a value is “11–13” and the data coder has to make an executive decision to get integers and goes always with the center. Where should the 11–13 go, where the 12?
A data producer would have to fill those columns rigidly, and a data consumer would have to do a lot of case handling depending on which combination of data type, code reference, extracted value, (and raw value) columns are present, and which values they each have – this decision would need to be in the specs, so a data producer can rely on the data being handled consistently.
It could be that this is the best solution, but given the complexity, checking it thoroughly with some examples sounds good.

Well, maybe not "very easy", but as easy as possible - no? But yes, both reading and writing data would require consulting two places:

Writing:

Looking up a ParameterTable's "datatype" column. If it is non-null, use it to encode "value".
Looking up CodeTable for codes associated with the parameter. If there are any, it's a categorical parameter and the row in ValueTable should have a non-null codeReference.

Reading:

If the row in ValueTable has non-null codeReference, just look up the code to get the value.
If the referenced parameter has a "datatype" spec in ParameterTable, use it to decode "value".

A library such as pycldf could make this very transparent, I think.

@Anaphory Regarding the question of reported data vs. data for re-use: I think it's clear from your description and the design goals of CLDF what to do: CLDF wants to make data re-use easier, and apparently the "executive decision" to code a certain value as integer shares that goal (right?). So the integer should go into value, and the "raw" data should go somewhere else - comment, or a non-standard column.

Oh right, I thought we hat a sentence in the specs that #value is the original measurement or the value as given in the source. It's not in there, so of course that would go into a standard column.

Could we conceive a solution where the data type interpretation would be part of the CodeTable instead? I assume that's not compatible with csvw and in particular any clean implementation of foreignKeys, so I think your suggestion is the best one possible, but I'd at least want to consider how badly that would fail.

@Anaphory so how would that look like?

@Anaphory @chrzyki @LinguList @SimonGreenhill what do you think about the "datatype" column sketched above? Too implicit or ad-hoc or weird (with JSON as column content in CSV)?

Irrespective of the other discussions (I'll read through them later!) I don't find it weird or ad-hoc at all, rather, I find the proposal quite consistent and feel it's a 'logical' next step or extension. I like it!

I'm really not sure, that's why I wonder whether we could even conceive such a thing.
The first thing I can think of that goes vaguely in this direction would be similar to virtual columns, but given that we inherit virtual columns from CSVW, I don't think that's a sensible start for this thought experiment.
Browsing through the CSVW specs, I noticed weak linking. With a probably more complicated set of special cases than the ones you suggest (and starting with some specification of how to treat weak linking inside CLDF), we could have a column in the ValueTable that weakly links to the CodeTable in some cases, and to a different table (or just an ontology of numbers, yay :disappointed:) in other cases.

TBH, I find it difficult to compare concrete implementation proposals with thought experiments :)

@Anaphory @davidainman here's how I would imagine typed values to work:
https://github.com/cldf/pycldf/pull/135/files#diff-85bf2019559734a47ac9b8e371220fa7bfe3ed59b5d4401f61f49bdb0a264df7
This really does not require much code, see https://github.com/cldf/pycldf/pull/135/files#diff-03d1c88087d8b8c2f7f2afefe1dce69db8198d8734548999ffcbe3f8f99facf9
In particular, I think it is transparent enough to also work with other toolchains - i.e. outside of pycldf.

I agree with @xrotwang. This seems to be the currently easiest and most straightforward solution.

@PaprikaSteiger is working on this database to create a CLLD web app and this workaround causes a problem with the SQL foreign keys. If integers lack a CodeID, then the CodeID column cannot be declared a foreign key (because there are empty cells). There are two workarounds to this, as we understand it:
(1) We do not declare CodeID as a foreign key (but this breaks the database structure)
(2) We create a fake CodeID for integers that points somewhere saying "Hey, this is an integer, this is not a real value, go look at the values column"
I'm not sure if one of these is better than the other, or if this breaks this integer workaround totally. (Feel free to chime in, @PaprikaSteiger, since you are more familiar with it!)

I don't fully understand. Are we talking about the SQL schema of the clld web app here? If so, that could be entirely separate from the CLDF data model, because loading CLDF data into the app is fully under your control, via the code you write in scripts/initializedb.py.
If we are talking about the CLDF data model - and possibly the SQLite db that can be created from it via cldf createdb, then I could see the problem. Using Code_ID as foreign key for a couple of parameters but not for others wouldn't work. IIRC, the original problem was that you wanted to have typed values for some parameters, right? Maybe my recipe for typed values as used in this test https://github.com/cldf/pycldf/blob/032345fed1b29a8799233d1961f492d7b992a540/tests/test_orm.py#L135-L166 would be a better option then? The idea is that all values are serialized as strings (which fits with Value), but the ParameterTable has enough info to deserialize the value into a typed object.

Yes, we are talking about the SQL schema of the CLLD app (I believe @PaprikaSteiger is using cldf createdb). The original issue is we wanted to have open-ended real number values for some parameters, which CLDF doesn't really support by default. The options were to create a special code ID for every numeral in the database, or this workaround where some parameters had a datatype "integer" which signaled that parameters of this type had no CodeID, but rather a fixed value.
I'm not sure if I fully follow the test_orm code (I have only been peripherally involved in generating the code to port our flat database structure into validated CLDF). If I follow, it does away with the codes table altogether? I'm not sure if this matches totally what CLDF was supposed to encode (i.e., fixed values), but I don't see whether there's a way around a concept like "real numbers" otherwise. It's also not clear to me if this would fix our issues in setting up a clld app.

If it's the SQL of the clld app, then it's presumably created via clld initdb - which is just a wrapper around the code you provide yourselves in yourapp/scripts/initializedb.py. That's what I meant above, that the schema of the clld app is fully under your control, i.e. must not match the CLDF dataset schema exactly.
The CLDF ValueTable specifies Code_ID as optional. So it's completely ok to have some categorical parameters, with valid codes listed in CodeTable and consequently non-empty Code_ID for values in ValueTable - and others with empty Code_ID. For the non-categorical parameters the question arises how to store the typed values, e.g. rational numbers in your case. CLDF doesn't have a clearcut solution for this. You can

just serialize the value as string and put it in ValueTable Value - making sure the documentation of the data makes the data type clear
add a column - e.g. Value_Number with appropriate type to ValueTable
or use the recipe I linked to in pycldf's tests, which is a somewhat a hybrid between the two options above: The datatype column added to ParameterTable is basically machine-readable documentation, with the added benefit of builtin support in pycldf.

Thanks for your elaboration.
I think the problem is not in the yourapp/scripts/initializedb.py but in yourapp/models.py. I derived an OOAValue class from Value and declared the  Code_ID as a foreign key pointing to the primary key of a DomainElement. Did I understand you correctly that I should change it to a normal column and add the ValueTable in datatables.py with a link column to the DomainTable?

Value already has a foreign key to DomainElement, see
https://github.com/clld/clld/blob/ddf56c8b9591d50ef39ccb66a3ae499dade0ab20/src/clld/db/models/value.py#L52-L62
Code_ID (or more correctly, the column with propertyUrl ...#codeReference) will typically used to instantiate such a relation between Value and DomainElement. See
https://github.com/clld/clld/blob/ddf56c8b9591d50ef39ccb66a3ae499dade0ab20/src/clld/project_template/{{cookiecutter.directory_name}}/{{cookiecutter.directory_name}}/scripts/initializedb.py#L140-L147
This will not work if you have not-null values in Code_ID which do not point to anything in CodeTable - e.g. if you put any integers into Code_ID. So in this case, I would indeed load the values of Code_ID into a non-foreignkey column.

We should have a solution to these issues spelt out in the FAQ.


Deploy token

@dkhamsing I managed to create this new awesome repo for live conferences, probably I think I'm missing the GitHub token for ReadmeBot?

Let me take a look later 🙂

fixed


[S3] Configuration of default object lock settings

Is your feature request related to a problem?
Currently, the S3 operator only supports to enable/disable the object lock for new objects but it doesn't allow to customize the object lock configuration (e.g. the default retention or the default retention mode).

Describe the solution you'd like
As a user I would like to be able to customize the default object lock configuration (e.g. set the default retention or the default retention mode) similar to the AWS console:

The Terraform provider: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_object_lock_configuration#default_retention).
The AWS CLI: https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/put-object-lock-configuration.html
I would love to see something similar to this:
objectLock:
  enabled: true
  default:
   retention: 1d // or e.g. 1y
   mode: governance // or compliance

I discussed the topic in Slack and @A-Hilaly suggested that it could be solved by using https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectLockConfiguration.html.
Describe alternatives you've considered
None
Thank you very much! :heart:

I wonder why there is a "Disable" option in the AWS Console since it's pretty clear that once you enable Object Lock, you cannot disable it....

This is doable, but the whole "cannot disable once enabled" thing will need to be custom coded...

/remove-lifecycle stale

/remove-lifecycle rotten


Inventory does not handle empty name/quantity

For inventory/shopping list, I made it such that name is a compulsory input. So if name is not inputted, exception will be shown: Ingredient name can take any values, and should not be blank.
If quantity is not inputted, default quantity 0.0 will be used.

the command I tried was inv add -name apple -qty .
The error message was empty String which is not formatted properly


.NET Date Formatting

This is an issue that has come up a number of times. Given that we are moving to iOS 4.0+ as the deployment target, we should be able to use regular expressions to handle this more easily at the framework level.
http://groups.google.com/group/restkit/browse_frm/thread/8c8e6551d01fbf5d/cf5fb07a65702c64?lnk=gst&q=.net#cf5fb07a65702c64

For future reference: above link is dead, instead please go to https://gist.github.com/exalted/726910


Update install-unifi.sh

New version UniFi 5.10.12

Snappyjava version changed in this controller version - you might want to modify the installer script accordingly.

Snappyjava version changed in this controller version - you might want to modify the installer script accordingly.

All dependent packages are updated by script

My mistake - I checked the code: the script is grabbing the version - whatever that version may be - and replaces it by the right (working) version.


creating smaller release installer for end users

It's unnecessary for end users to download the whole repo

@lone17 You mean the dependency?
The whole repo in zip file is actually not much, just 7.4 MB in zip file

@trducng smaller in terms of the number of files. The whole repo has a lot of files and it looks bloated and unnecessary. Also downloading the entire repo makes upgrading depend on git instead of pip which less desirable. You can check a sample release I'm working on on the releases page https://github.com/Cinnamon/kotaemon/releases


Add compatibility checks

This eases using the module in projects with a lower deployment target.

@rivera-ernesto There are platforms requirements in Package.swift
.iOS(.v13), .macOS(.v10_15), .watchOS(.v6), .tvOS(.v13)

Can you please give more detail about why this is necessary in your case.
Thank you.

Currently it is not possible to import Grid (or any Swift Package) into a project with a lower deployment target.

Compiling for iOS 10.0, but module 'Grid' has a minimum deployment target of iOS 13.0

Workarounds like #if canImport(Grid) do not solve it. The only way is to manually add the source files to the project, but then it won't compile because the used classes and features require iOS 13. This is solved by this PR which adds @available checks to the sources.

This is due to current SPM limitations
https://stackoverflow.com/q/62073570/1049134


CSS not injected on external URL

Submit a feature request or bug report

[x] I've read the guidelines for Contributing to Roots Projects
[ ] This is a feature request
[x] This is a bug report
[x] This request isn't a duplicate of an existing issue
[x] I've read the docs and NPM Debugging Guidelines post and followed them (if applicable)
[x] This is not a personal support request that should be posted on the Roots Discourse forums

What is the current behavior?
Using external URL on another machine (same network), eg <IP_ADDRESS>:3000, CSS is not getting injected.
What is the expected or desired behavior?
CSS should be refresh as it is on local URL, eg localhost:3000.

Bug report

Please provide steps to reproduce, including full log output:

Install fresh Sage theme, activate, start server.
Open one tab with the local URL, another with the external URL given by BrowserSync.
Make a CSS change, save.

CSS is refreshed on the local tab, not on the external one.
Notes:

the BrowserSync notification works.
No error in console.
The local URI does work on the same machine though.
Tried with another Mac, Windows, IE, iPhone... Same issue everywhere.
Changes in JS & Blade templates are injected correctly

Please describe your local environment:
WordPress version: 4.7.3
OS: Mac OS El Capitan (Chrome latest)
NPM/Node version: 7.4.0
Where did the bug happen? Development or remote servers?
Development
Is there a related Discourse thread or were any utilized (please link them)?
Didn't find anything.
Thanks in advance!

just tested this out and was unable to reproduce


blank line render broken

codeBlock:
    const str = `
def func:
  if foo:
    return True

func()
`;

wordList:
[
  ["def", "func:"],
  [tab, "if", "foo:"],
  [tab, tab, "return", "True"],
  [""],
  [""],
  ["func()"],
];

view:

Probably needs a simple adjustment at <Word/>

If we know the line height, we can apply a height style to all lines under CodeWrapper. But the CSS, in general, needs to be updated.

Something like this in index.css would define a consistent line-height:
+#codeWrapper > .WordList {
+  height: 2.5rem;
+}

Note: this patch is referring to the point after the latest style update, commit 42aa421.

yeah I've already made some random tweaks for #12 in terms of the cursor.

btw #12 is pretty hard

maybe just me but without the div outlines the spacing between lines look bit too big


Update MD file on new branch 2017-28-08_19-12-53

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix python ssl after reinstallswift

This is immensely useful and i have validated that the generation of vsaio cert works on a "jammy-m1"


Certificate verification utterly broken

K-9 Mail happily accepts not only self-signed certificates without raising any questions, but also expired certificates. This should definitely be NOT the case, since it renders the whole authentication useless and MitM becomes possible by introducing fake and/or self-signed certificates.
Verifying the validity of certificates is essential to the SSL/TLS system, otherwise it is pretty much useless.

Bug report utterly broken!
Please provide the information asked for in the issue template so we have a chance to investigate: https://raw.githubusercontent.com/k9mail/k-9/master/issue_template.md

Expected behaviour
K-9 Mail should reject to establish a secure (!) connection to servers that provide invalid certificates.
Actual behaviour
K-9 Mail happily accepts invalid certificates, e.g. expired ones. This makes it vulnerable to all sorts of active MitM attacks and renders the whole authentication useless.
Steps to reproduce

Setup server with invalid certificate, e.g. expired one
Connect to it with K-9 Mail. In my case I've used IMAP
See how K-9 mail happily interacts with the server and fetches all mail.

Environment
K-9 Mail version: 5.006
Android version: 5.1.1
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

Works fine for me.

There's an option to ignore the invalidity of SSL certificates. Do you have this set kbabioch?

@philipwhiuk There is not. We removed that option a while ago. If there's a problem with the certificate you should get prompted whether you want to accept the certificate with the dialog shown in my previous comment.

Closing this issue since no instructions on how to reproduce the problem were provided.


deleted items whose parent are not deleted should now be correctly displayed in trash list

Description
For a nested tree, If you deleted an item while its parent is not deleted, then it will not show in the trashed table. So while the count is correct, the table will be missing some items.
The fix for this, would be to display deleted items whose parents are not deleted as first level items without touching their tree-related attributes, this way when it gets restored again, it will be placed in the correct location
Edit:
also when restoring an item whose parent is deleted, it will be set as a first level item

Related Issues

Thank you @haringsrob for these helpful comments, they have all been addressed


Addresss Issue #801 and Add Test

Give this a try and let me know if it resolves the issue.

Thanks @elmq0022 !
Looks like your branch has a conflict with master.  I think a new test was added at the same location as your new test, so we should resolve that by taking both.  Want to rebase and we'll see if the tests pass?  Sorry for the hassle.

That's fine.  I will make another attempt this weekend.
Thanks for your patience add well.
On Nov 5, 2015 8:15 AM, "Richard Frank"<EMAIL_ADDRESS>wrote:

Thanks @elmq0022 https://github.com/elmq0022 !
Looks like your branch has a conflict with master. I think a new test was
added at the same location as your new test, so we should resolve that by
taking both. Want to rebase and we'll see if the tests pass? Sorry for the
hassle.
—
Reply to this email directly or view it on GitHub
https://github.com/quantopian/zipline/pull/818#issuecomment-154069451.

Closed in favor of #819


Package GONE after update new release Verdaccio

I updated to Verdaccio latest version yesterday and my package I uploaded last time are gone to nowhere which I couldn't found. Is this a bug or it happened everytime I update Verdaccio. Someone please help me solve this. Thanks. :)

This may be irrelevant, but have you tried running npm dist-tag ls [<pkg>]? (See documentation) This will list the tags of your NPM package, and the latest versions on each. I recently updated Verdaccio and recall reading about changes regarding how Verdaccio handles tagging. I could see a package seemingly vanishing from the UI perspective depending on how it was tagged.

@jk-jx could you elaborate a bit more? eg: steps, config file, log etc etc

Did you run verdaccio with pm2 cluster mode?

After I installed Verdaccio in my server, I had publish a few package for job purpose. After a few days, I noticed that there's a new update for Verdaccio, so I decided to update. After I updated, all my package I uploaded before had gone. So is that you guys have any solutions to solve this issue?

@jk-jx
We fixed a danger behavior that may cause data loss with: #306, not release yet
If you are experiencing same issue, it's not possible to recover database, at the same time, your npm will auto logout because either database and secret was destroyed. But your packages still store in you disk.

@Meeeeow I know it's not possible to recover. But the problem is, in future if I update my Verdaccio, impossible I need to republish the package again and again what.

@jk-jx This will not happen again in the future release

@Meeeeow actually where did the package all store? because I wanna do some backup for it.

I released v2.4.0 please try again and let us know whether fix your issue

@jk-jx For Linux/Unix, default storage path is ~/.config/verdaccio/storage, for Windows, default storage path is "%appdata%/verdaccio"


Upgrade project for Xcode 10.2, Swift 5

I upgraded the Hashable implementation, while leaving it backwards-compatible.
I deleted all the code for Codable since it's auto-synthesised. Will that make it non-backwards-compatible? 🤔

You're not supposed to persist hashes anyway, just like the documentation clear said:
/// Hash values are not guaranteed to be equal across different executions of your program.
/// Do not save hash values to use during a future execution.
var hashValue: Int { get }

So I'm gonna say this a non-breaking-change.
Thanks, @guykogus!


not happy about it

hi @kenshaw I'd like to express that I am not happy about the fix for the issue reported here:
https://github.com/chromedp/chromedp/issues/75
This issue was reported in june last year, it was followed by a few other people and provided a fix, and there is another merge request page for this. I also provided a testing report base on my particular case about it and showing it has positive results.
You mentioned this might need more tests and you will merge it back, however this has never happened.
In Dec:

you split the codebase to a few individual ones
you closed the merge request (the issue page is still open though)
you did not answer when this will be merged back
you did not announce the plan what to do

I(or other users of the project) could take my patience on the fact that you are busy and let's leave it there for sometime and wait for later and we will probably just use the hack for the time being. However this whole thing is just so not pleasant because:

user has to fork and maintain their own code base and use special way to "overwrite" to hack the go library management. This has to be applied every time if the repo is updated in anyway.
now due to the split of the codebase, this is all broken. The splitting leaves a gap for the other people's patch to be patched again and personally I spent a night and just couldn't easily figure it out what to manually patch by hands due to massive changes.

What I am not happy are:

The process is not agile. Users are expecting adopting fixes/features quicker. Yes, I understand you have limited time for testing and coding etc. Then this comes to second problem:
Can you grant more people the permission and let them contribute to the project? As I can see there are quite a few guys helped patching, testing etc. Can you let them merge the code and responsible for the change they made? or at least allow the trial patch to be in a branch to be verified, so the changes could be carried over to new split code repos.
No communication the plan of changes, like the codebase split
I don't understand why no action on this serious performance issue or plan towards it. I message in the closed merge request and the issue, there seems no reply and no explanation and no plan.

I could appreciate the work you have done and understand time is limited for everybody. And you might not have time to focus on something interest the user but not some more important things to you and your team.
Once again, I wish https://github.com/chromedp/chromedp/issues/75 could be looked at and I am hoping there could be a way for more users to participate in the project and contribute and eventually benefit all.
Excuse and ignore my rumbly noise and focus the issue.
Thanks

@kenshaw trying to reach with your mail but seems the domain name is not resolvable anymore.
I wonder how is going on with the "new" model?
Thanks


fix illegal_parameter alert error due to non-empty key_share extension

The error
hello_tls.protocol.ServerAlertError: (ServerAlertError(...), 'Server error: AlertLevel.FATAL: AlertDescription.illegal_parameter')

has been observed in hello_tls with some servers, e.g.:

AkamaiGHost (adobe.com, amd.com, dhs.gov)
Kestrel (microsoft.com)
nginx (digital.com, duckduckgo.com, freebsd.org, web.archive.org, whitehouse.gov)

It is caused by the key_share extension, which contains a static x25519 entry, independent of the contents of the supported_groups extension. A client hello without x25519 in supported_groups violates RFC8446:

"This vector MAY be empty if the client is requesting a HelloRetryRequest. ... Clients MUST NOT offer any KeyShareEntry values for groups not listed in the client's "supported_groups" extension. Servers MAY check for violations of these rules and abort the handshake with an "illegal_parameter" alert if one is violated."

As noted in the RFC quote, the key_share extension may contain an empty vector. This approach is proposed in the pull request.

Ah, that explains some issues I've seen then. Thanks a lot for picking up on it and providing a fix.


ext_proc: should return 504 on timeout error

When calling ext_proc server and a timeout occurs it is returned 500 to the downstream service.
https://github.com/envoyproxy/envoy/blob/bb4a76ac13d0b8a6851e7db4b1c3a4f2d408f92e/source/extensions/filters/http/ext_proc/ext_proc.cc#L1086
It feels a more appropriated error code would be 504 Gateway Timeout in the same lines httpCall from the Lua filter. I did not see any comments around it when it was introduced in https://github.com/envoyproxy/envoy/pull/15339 so please let me know if I'm missing any context.
I'd be happy to open a PR if agreed.

I have created a draft in case it makes sense. https://github.com/envoyproxy/envoy/pull/34856


jacdac-docs resets micro:bit when flashing

Depending on how you do flashing, the site might interrupt the micro:bit during a flashing process initiated outside of the web browser.
For example, if you drag-and-drop a hex file onto the micro:bit drive with the site connected, it is highly likely that a reset will come from the browser and corrupt the flashing process. This creates a broken user experience, which we want to avoid.
Can we revisit the need for this reset behaviour?

Fixed.


When can we expect code / demo to be released to public?

Same here for the NeuroPrompts research work. Is there an update on the public release of the code/demo?

Thank you for your patience. The code for NeuroPrompts is now available here: https://github.com/IntelLabs/multimodal_cognitive_ai/tree/main/Demos/NeuroPrompts


Change Shape of technology Artifact

How I can change the shape of technology artifacts?
For example, the artifacts shown in the following image

thanks and regards

Hello any comments about this request.
It's really very useful to me, and I'm pretty urgent.
I appreciate any comments you can give me.
Greetings

Hello @DTHerrera , for what I've been able to find it's not possible for users to create new shapes, but only by modifying the code of  PlantUML. Nothing to do about it in this repo which is just a collection of macro definitions.
If you search for "shapes" in their forum you can see people asking for custom shapes since 2015 so I wouldn't keep my hopes up.

Hello thank you very much for your information, it really is bad news, I understand that there must be a core that should not be modified, but you must have an option to extend the functionality as libraries

As this problem lies beyond the scope of this project, I am closing this issue.


add eks:node-manager to allowed_k8s_users list

eks:node-manager  is an Amazon EKS internal service role that performs specific operations for managed node groups and Fargate.
Reference: https://github.com/awsdocs/amazon-eks-user-guide/blob/master/doc_source/logging-monitoring.md
Related falco log
{"output":"10:56:31.181308928: Warning K8s Operation performed by user not in allowed list of users
 (user=eks:node-manager target=aws-auth/configmaps verb=get uri=/api/v1/namespaces/kube-system/configmaps/aws-auth?timeout=19s resp=200)","priority":"Warning","rule":"Disallowed K8s User","time":"2021-01-26T10:56:31.181308928Z", "output_fields":
{"jevt.time":"10:56:31.181308928","ka.response.code":"200","ka.target.name":"aws-auth","ka.target.resource":"configmaps","ka.uri":"/api/v1/namespaces/kube-system/configmaps/aws-auth?timeout=19s","ka.user.name":"eks:node-manager","ka.verb":"get"}}

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

area rules

/area tests

/area proposals

What this PR does / why we need it:
it adds eks:node-manager to allowed_k8s_users list
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@ismailyenigul: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ismailyenigul: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign mstemm after the PR has been reviewed.
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign mstemm after the PR has been reviewed.
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

ee4c4fd add eks:node-manager to allowed_k8s_users list

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

ee4c4fd add eks:node-manager to allowed_k8s_users list

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Welcome @ismailyenigul! It looks like this is your first PR to falcosecurity/falco 🎉

Welcome @ismailyenigul! It looks like this is your first PR to falcosecurity/falco 🎉

Hi @ismailyenigul
Thank you for opening this PR! Anyway, before we can look into it, we need that all commits to be signed-off (you can find more detail here).
Let me know if you need any help.

Hi @ismailyenigul
Thank you for opening this PR! Anyway, before we can look into it, we need that all commits to be signed-off (you can find more detail here).
Let me know if you need any help.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

ee4c4fd add eks:node-manager to allowed_k8s_users list

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

ee4c4fd add eks:node-manager to allowed_k8s_users list

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Kaizhe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [Kaizhe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: f36014e6e48a9cd399a1bd192e012f0614e4b8d4

LGTM label has been added.  Git tree hash: f36014e6e48a9cd399a1bd192e012f0614e4b8d4

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Kaizhe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [Kaizhe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ismailyenigul thank you for your contribution!

@ismailyenigul thank you for your contribution!

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Kaizhe, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [Kaizhe,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[CodeCompletion] Don't run second pass for decls in closures

For instance:
let globalVar = {
    func something(arg: Int) -> Int {
        #^HERE^#
    }
    return something(12)
}()

We want to consider this as a top-level completion, not a function body completion.
rdar://problem/60838686

@swift-ci Please smoke test


add Logger.prettyLogger & Logger.pretty

/snapshot

It would be really nice if this was more customizable

I think we should lean towards a consistent experience over customizability here. In saying that, I think date formatting is an OK option.


[backport] Fix unchain gradient pull

Backport of #6804

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 2131e951b0dc94465f35d27302793eb5985c1b8b, target branch v6) failed with status FAILURE.

LGTM


Dropdown scroll to selected

Is it possible to scroll to the selected item when opening the dropdown? I mean, if one item in the middle of a long list of options (simple HTML select tag) is selected, it gets out of view, one needs to scroll down manually to see. It would be better to have the dropdown scrolled automatically to make it visible.
Or is there an option for this already?

You can using the dropdown show event but the api doesnt exactly give you a method for it. You would have to do the scroll math manually.

Thanks, here's the code I've put together:
$choice.passedElement.addEventListener('showDropdown', function () {
    var $select = this,
        id = $select.value;

    var $option = $select.parentElement.parentElement.querySelector('.choices__list--dropdown [data-value="' + id + '"]');

    if ($option) {
        $option.classList.add('is-active');
        $option.parentElement.scrollTop = $option.offsetTop - $option.parentElement.offsetTop;
    }
}, false);

Unfortunately scrollIntoView() caused jumps in IE and Firefox, otherwise it would do the job as well.

IMO this should be default behavior and not optional.

Here's an alternative solution using the choiceId value and built-in methods for scrolling:
const choices = new Choices(selectElement);

choices.passedElement.element.addEventListener('showDropdown', () => {
    const id = choices.getValue().choiceId
    const option = choices.dropdown.element.querySelector(`[data-id="${id}"]`)

    if (!option) {
        return
    }

    choices.choiceList.scrollToChoice(option, 1)
    choices._highlightChoice(option)
}, false);

Thanks for the solution!
Looks like they updated in their code scrollToChoice to scrollToChildElement

Looks like they updated in their code scrollToChoice to scrollToChildElement

Saved me


Remove border box

How can i remove border box?

Hi Max,
The blue border is a focus field that highlights the current field in your signer flow. The border is surrounding the entire group of checkboxes because you are using the group checkboxes feature, which shows the user that one of the boxes in that particular group is required to be checked. Once you are no longer focused on that panel of checkboxes, the blue border will move to highlight focus on the next field on the document. The placement of the checkboxes on different pages of the form is what is causing the line to extend so far down the page.
If you have any further questions, please email us at<EMAIL_ADDRESS>and we can help you there!


FVT: Multiple SLF4J bindings

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Multiple SLF4J bindings reported in FVTs: (maven)
54414 [INFO] Running org.odpi.openmetadata.accessservices.analyticsmodeling.fvt.execution.AnalyticsModelingOMASSynchronizationIT
54415 SLF4J: Class path contains multiple SLF4J bindings.
54416 SLF4J: Found binding in [jar:file:/home/jonesn/.m2/repository/ch/qos/logback/logback-classic/1.2.10/logback-classic-1.2.10.jar!/org/slf4j/impl/StaticLoggerBin      der.class]
54417 SLF4J: Found binding in [jar:file:/home/jonesn/.m2/repository/org/slf4j/slf4j-simple/1.7.32/slf4j-simple-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
54418 SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

The same overlap is reported in every FVT
Expected Behavior
No duplicate SLF4J bindings to be found
Steps To Reproduce
Build
Environment
- Egeria:
- OS:
- Java:
- Browser (for UI issues):
- Additional connectors and integration:

Any Further Information?
No response

This error occurs because we have 2 SLF4J bindings
a) The server chassis itself, correctly, provides a binding using logback
b) We have a default binding included in test scope only from the top level pom:
<!-- Most dependencies pushed down to keep components minimal -->
<dependencies>
    <!-- Use slf4f-simple anywhere as logging implementation in TEST scope only -->
    <dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-simple</artifactId>
        <version>${slf4j.version}</version>
        <scope>test</scope>
    </dependency>
</dependencies>

This can't be removed, as some tests need it.
Moving it down one level to the implementation directory (rather than explicitly adding to many modules) should be sufficient for now.


Add collections sizes to MsgListDatabases response for Tigris

Description
This PR closes #776.

Readiness checklist

[x] I added tests for new functionality or bugfixes.
[x] I ran task all, and it passed.
[ ] I added/updated comments for both exported and unexported top-level declarations (functions, types, etc).
[ ] I checked comments rendering with task godocs.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Assignee, Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

Add collections sizes to MsgListDatabases response for Tigris

That method should return database sizes, not collection sizes


Implement shutdown

Harvey has no 'shutdown' command, so we should implement it.
This is generally useful, but would also simplify the process to create a Harvey image, since we could combine the 2 consecutive steps where we run GO9PIMG.

(From Ron on slack: this is where we need more acpi support, i.e. another program which will talk to acpi device and tell it what to do. Does not exist yet.)

Again from Ron - see acpi/irq, call the acpi shutdown function

This as done - see acpi/shutdown for a brutal version of shutdown

^


Review Delta State Replicated Data Types abstract

Review Delta State Replicated Data Types (δ-CRDT) abstract and decide if add them to this kit (probably yes) http://arxiv.org/abs/1603.01529
[ ] reviewed
[ ] will add them

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.


Refaster style recipes cannot match types that require transitive dependencies to be loaded

This parser:
JavaTemplate.builder("#{any(com.azure.cosmos.CosmosClientBuilder)}.endpoint(\"boo\").userAgentSuffix(\"test\").buildAsyncClient()")
                .javaParser(JavaParser.fromJavaVersion().classpath("azure-cosmos"))
                .build()

Cannot be used to match a method invocation of CosmosClientBuilder.buildAsyncClient() because the method its parser produces lacks type information. CosmosClientBuilder is defined within the jar "azure-cosmos", but also requires "azure-core" for the java compiler to type attribute it.
This is because JavaParser.fromJavaVersion().classpath() does not look up transitive dependencies of the named artifact, so "azure-core" is absent from the classpath.
This test can be used to reproduce the issue. Changing JavaParser.fromJavaVersion().classpath(JavaParser.fromRuntimeClasspath()) resolves this problem because the full runtime classpath has both "azure-cosmos" and "azure-core".

All my testing used already the JavaParser.fromJavaVersion().classpath(JavaParser.runtimeClasspath()) in the defaults spec.recipe for the generated recipe template. And it never worked - we debugged it few day ago and last week as well - that is how it was setup. Still does not work.

@sambsnyd the test specified here: https://github.com/openrewrite/rewrite/blob/bade688c8c6647f7d4cce1077417f021735ca835/rewrite-java-test/src/test/java/org/openrewrite/java/JavaTemplateMatchTest.java#L164C8-L164C176
is not valid. It does not target any CosmosClientBuilder invocation but specific ".endpoint("boo").userAgentSuffix("test")" - i.e. in client code these additional calls on the builder can come at any order and there are a lot more additional calls that can be there or not. A proper test would use:
"#{builder:any(com.azure.cosmos.CosmosClientBuilder)}.buildAsyncClient()" to match code that may or may not use endpoint or userAgentSuffix on the builder.
And that is still failing for me with latest versions and with avaParser.fromJavaVersion().classpath(JavaParser.runtimeClasspath()) being used for the last 2 weeks.

@sambsnyd
Actually I copied your test in my local and modified it (not looking for specific userAgent, endpoint).... and it works! :)
Looks like the issue was indeed was with setting the classpath - the big difference was that I was doing it in the defaults:
public void defaults(RecipeSpec spec) {         spec.recipe(new ReplaceSyncClientBuilderRecipe()).parser(JavaParser.fromJavaVersion()                         .classpath(JavaParser.runtimeClasspath()));  }
where it works only if I use it like you:
`rewriteRun(
spec -> spec.recipe(toRecipe(() -> new JavaVisitor<>() {
final JavaTemplate template = JavaTemplate.builder("#{any(com.azure.cosmos.CosmosClientBuilder)}.buildAsyncClient()")
.javaParser(JavaParser.fromJavaVersion().classpath(JavaParser.runtimeClasspath()))
.build();
final JavaTemplate replacement = JavaTemplate.builder("null")
.build();
            @Override
            public J visitMethodInvocation(J.MethodInvocation method, ExecutionContext executionContext) {
                JavaTemplate.Matcher matcher = template.matcher(getCursor());
                if(matcher.find()) {
                    return replacement.apply(getCursor(), method.getCoordinates().replace());
                }
                return super.visitMethodInvocation(method, executionContext);
            }
        }))
        .parser(JavaParser.fromJavaVersion().classpath(JavaParser.runtimeClasspath())) .....`


Display zoom level #87

Response to #87:

Apologies it took me a while to get to this, it looks great. Merging.

@orangemug There is no need to apologize. :) One is glad to be of service. :D


bg--transparent class added

See https://github.com/tachyons-css/tachyons/issues/193

Hey @hongkonggong - All Pull Requests for the main repo need to be made into the individual modules, as those get dynamically copied over based on the declared module version in the package.json. I've gone ahead and updated the tachyons-skins repo and then updated the main project. Thanks for pointing out missing this!

Oh my bad, thanks for correcting me on that (and making the update)!

Nah it's not your bad, it's in the contributing guidelines in the readme but it is buried. And it's a different workflow than most other projects so it's pretty weird. Wish it was easier to give 'github credit' when I have to make the patch manually myself.


omegaconf.errors.InterpolationKeyError: Interpolation key 'local.log_dir' not found

Hello, Thanks for your great work!
However, when I run the eval, I meet the error as the title. It seems to be a problem related to the config file. How can I solve the problem？
I have revised the path to run the code.
python eval.py ckpt_path="/path/to/ckpt/name.ckpt"
Meet the fault as below.
  raise InterpolationKeyError(f"Interpolation key '{inter_key}' not found")
omegaconf.errors.InterpolationKeyError: Interpolation key 'local.log_dir' not found
   full_key: hydra.run.dir
   object_type=dict

Hi, if you look in the config you will see that hydra.run.dir is looking for a local.log_dir path. You can either set this or set hydra.run.dir to something else.

Thank you.


DENY Any Windows attempt on restarting

I HATE auto restarts, and active hours here can be 24/7, so could be nice to have option to complete deny windows ability to restart.
afaik this can only be done this way:

Press Windows key + R keyboard shortcut to open the Run command.
Type the following path and click "OK":
%windir%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator
Select the Reboot ) (it does not have an extension)
file right-click it and select "Rename".
Rename the Reboot file to "Reboot.old".
Right-click inside the folder, select "New," and click on "Folder".
Name the New Folder "Reboot".
Now restart your computer.

i really want this tweak inside winutil also ;)
thanks for great app, love it ..

There is no Reboot File? Don't know how to implement this lol

setting anything in windows, will not disable, this is tried. its needed to create a reboot dir inside that %windir%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator

So how can I implement this? I still didn't get the idea.

my idea if i could program, check if @reboot is there, if so rename to @reboot.old, create directory "reboot" if none found create the reboot directory, if disabled, just remove the reboot dir, and rename .old to @reboot if found.


provide a way to customize the output of the emitter

currently all yaml strings are being emitted regardless of whether they are actually needed or not. typically you don't need them in yaml. it would be useful to have a way to customize the behavior or to just opt not to quote things by default.

Yeah, the emitter is not polished yet, I just quote every string to make it safely emit valid YAML document (but may not human friendly).
PR regarding the emitter is welcome.

Thanks @chyh1990. Maybe I'll try to see what I I do myself. You're library has been working great so far

I think we can close this issue since pull request #39 has been merged.

I think that pull helps with what I wanted out of this issue. There are actually many flavors of string quoting styles defined in the yaml spec that would probably be nice to have in this library. Maybe a separate issue to outline those could be opened in favor of this.

Would this also have scope for customizing things other than strings? For example there are situations where using single-line {} or [] constructs for small structures would drastically reduce the size of some of my YAML payloads.

@radix there already is emit_node_compact(), even though this is not public yet. It is currently only used for keys in Yaml::Hash. Perhaps you could come up with a nice API to use this one instead.

Just bumping, would be great to have the option to force adding quotes

Just bumping, would be great to have the option to force adding quotes for strings

bump for that


Read params from ini file

@datarobot/predictions

LGTM

@asvetlov

LGTM, please merge.
I have some ideas on future improvements but the PR is big enough, better to fix the current state.


Add Out of Scope label comment

I'm planning to triage through older enhancements and plan to use labels for auto-comments/closing issues.  Please read the comment and let me know if there are suggestions.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26395

Relevant Lines:
57409

💛  - Coveralls


invalid evidence are tagged as valid during the --val step

@gkos-bio commented on Tue Nov 14 2017
Some invalid evidence strings are marked as valid while they are invalid.
In this example, the pmid reference is missing but the flag "is_valid" is set to true.
{
        "_index": "17.09_gk_validated-data-genomics_england",
        "_type": "genomics_england",
        "_id": "da7cf94e545be45b4f7dc8a7e303ece8",
        "_score": 1,
        "_source": {
          "release_date": "20171114T081802Z",
          "data_source_name": "genomics_england",
          "file_name": "/Users/otvisitor/Documents/data/release9/genomics_england-05-09-2017.json.gz",
          "explanation": {
            "validation_errors": "[] is too short ;  ; Failed validating u'minItems' in schema[u'allOf'][1][u'properties'][u'evidence'][u'allOf'][0][u'properties'][u'provenance_type'][u'properties'][u'literature'][u'properties'][u'references']: ;     {u'items': {u'$ref': u'#/definitions/single_lit_reference', ;                 u'type': u'object'}, ;      u'minItems': 1, ;      u'type': u'array', ;      u'uniqueItems': True} ;  ; On instance[u'evidence'][u'provenance_type'][u'literature'][u'references']: ;     []"
          },
          "target_id": null,
          "json_schema_version": "master",
          "uniq_assoc_fields_hashdig": null,
          "disease_id": null,
          "json_doc_hashdig": "da7cf94e545be45b4f7dc8a7e303ece8",
          "is_valid": true,
          "json_doc_version": 1,
          "line": 40,
          "evidence_string": """
{"access_level": "public", "disease": {"id": "http://www.orpha.net/ORDO/Orphanet_84", "name": "N/A", "source_name": "Fanconi anemia"}, "evidence": {"date_asserted": "2017-09-05T16:37:41.592858", "evidence_codes": ["http://purl.obolibrary.org/obo/ECO_0000205"], "is_associated": true, "provenance_type": {"database": {"dbxref": {"id": "Genomics England PanelApp", "url": "https://bioinfo.extge.co.uk/crowdsourcing/PanelApp/", "version": "v4.1"}, "id": "Genomics England PanelApp", "version": "v4.1"}, "literature": {"references": []}}, "resource_score": {"method": {"description": "Further details in the Genomics England PanelApp.", "url": "https://bioinfo.extge.co.uk/crowdsourcing/PanelApp/EditPanel/"}, "type": "probability", "value": 1}, "urls": [{"nice_name": "Further details in the Genomics England PanelApp", "url": "https://bioinfo.extge.co.uk/crowdsourcing/PanelApp/55a631ae22c1fc6710839b97"}]}, "sourceID": "genomics_england", "target": {"activity": "http://identifiers.org/cttv.activity/predicted_damaging", "id": "http://identifiers.org/ensembl/ENSG00000181544", "target_name": "FANCB", "target_type": "http://identifiers.org/cttv.target/gene_evidence"}, "type": "genetic_literature", "unique_association_fields": {"disease_iri": "http://www.orpha.net/ORDO/Orphanet_84", "original_disease_name": "N/A", "panel_id": "55a631ae22c1fc6710839b97", "panel_name": "Non-Fanconi anaemia", "target_id": "http://identifiers.org/ensembl/ENSG00000181544"}, "validated_against_schema_version": "1.2.7"}

"""
        }
      },

@mkarmona commented on Tue Nov 14 2017
@gkos-bio @ckongEbi this is because the json schema contains that field as optional

@ckongEbi commented on Tue Jul 10 2018
@gkos-bio I suppose we do not have a pmid for GE yet? therefore the field is now optional.

Querying 18.08 this is no  longer an issue, cannot find any evidence where this is the case.
GET 18.08_validated-data-genomics_england/_search
{
  "query": {
    "bool": {
      "must": {
        "match_phrase": {
          "is_valid": true
        }
      },
      "filter": {
        "exists": {
          "field": "explanation.validation_errors"
        }
      }
    }
  }
}


ibugs

Remove redundant namespace per chart
App delete is based on uninstall action

related to: https://github.com/rancher/dashboard/issues/1431


Atempt at auto adding locate to vacuum

Not sure the naming is correct, my vacuum uses voice_find_device

You've forgotten to add the function to issue the locate command...

Try if this commit works for you.


ENH: Added nan_policy to circ functions in stats

Adds nan_policy as an optional keyword argument into the circular stat functions: stats.circmean, stats.circstd, and stats.circvar.  NaN handling for all of these routines happens within stats.morestats._circfuncs_common.
What does this implement/fix?
This makes the circular statistical functions NaN tolerant, using the same method (user specified NaN policy of propagation, omission, or raising an error) as other functions within stats.
Additional information
Here is an example:
import numpy as np
from scipy import stats

stats.circmean([0.1, 2*np.pi+0.2, 6*np.pi+0.3])
stats.circmean([0.1, 2*np.pi+0.2, 6*np.pi+0.3, np.nan], nan_policy='omit')

Both return 0.2

All my comments were addressed and this now looks good to me. @pv's comments also seem addressed, but I don't have the bandwidth to re-review everything in detail right now, so I'll hold off on doing the actual merge (will do so before 1.4.0 if no one else beats me to it).

All looks good, time to merge this. Thanks @aburrell!

Thank you @rgommers, @tylerjereddy, and @pv!  This was a good experience contributing code, and I appreciate the time you all put in to improve my contribution to scipy.

Thanks @aburrell, glad it was a good experience! Will try to get the next PR merged faster:)


While joining two tables if some columns have same name then I am not able to select all column names (Only all unique column names are displaying in the output).

If I am using _fileds and trying to select columns which have the common name then also in the output only one column is displaying. Not getting the option to alias column name.
Example:
Table1 : User(id, name, email, city_id)
Table2:  City(id, name)
query: /api/xjoin?_join=u.user,_lj,c.city&_on1=(u.city_id,eq,c.id)&_fields=u.id,u.name,c.id,c.name
Output:
[{
id: 1,
name : "xxx"
},{
id : 2,
name : "yyy"
}]
Expected Output:
[{
id: 1,
name : "xxx",
id: 1,
name : "city1"
},{
id : 2,
name : "yyy",
id: 2,
name : "city2"
}]

Having multiple keys with same name in an object wouldn't work.
Fixed Output will be in the lines of -
Expected Output:
[{
u_id: 1,
u_name : "xxx",
c_id: 1,
c_name : "city1"
},{
u_id : 2,
u_name : "yyy",
c_id: 2,
c_name : "city2"
}]

where alias for tables getting joined ti.e u and c will be prepended with _

@shivsharma396 Commit 5a9b6f4 has the fix and this will go in next release of npm.
Query:
/api/xjoin?_join=u.user,_lj,c.city&_on1=(u.city_id,eq,c.id)&_fields=u.id,u.name,c.id,c.name

Response:
[{
u_id: 1,
u_name : "xxx",
c_id: 1,
c_name : "city1"
},{
u_id : 2,
u_name : "yyy",
c_id: 2,
c_name : "city2"
}]

With this commit, _fields query param will be mandatory wherein earlier all fields of tables in join were getting selected.

Solution in 0.4.4


Popcorn Convertor and/or Samples

Is there any possibility you could publish the video conversion tool and/or some samples for the Popcorn Media Player app in pico-playground.
This is what README.mb currently says:

This is a movie player for 30fps 320x240 movies with 44100 stereo sound, read in a custom format from SD card... it can even play backwards :-) TODO: add a link to big buck bunny in the right format TODO: add converter

Many thanks

ah yes... i'll upload the bunny movie today, and throw together some sort of instructions for the converter soon.

movie uploaded https://drive.google.com/file/d/1q3szTVccPZ08v_TMDxy9ZgqeOOXXwHCX/view?usp=sharing (also in the README.md which has some very basic instructions)

Thanks for the Bunny example Graham.
It works, but the audio is very broken/stutterly.
Is that expected?

not expected; let me check the latest popcorn binary. (i've never seen audio problems with bunny, but sometimes i have with another movie - in which case pausing/unpausing a couple of times usually fixes it).

sound is good for me; did you get the sound working? I've mostly been using Samsung EVO Selects; though I have used a Sandisk in the past. (can't find it right now).
Certainly my SD testing ^ is not exhaustive, but we're not really pushing them very hard. Definitely worth trying with a different type of card though

oh, having just done this myself, be careful you didn't slow down the video by pressing the left button... the sound will stutter here. (this again is fixed by pause/unpause to set back to normal speed)

sound is good for me; did you get the sound working? I've mostly been using Samsung EVO Selects; though I have used a Sandisk in the past. (can't find it right now).

I've just tried again, and yes pausing/unpausing does resolve the sound issue.
I didn't notice this before, because I had a second source of similar (clicky) noise which I think was down to a USB ground loop

BTW, it does start stuttering again each time you reset. So this must be down to the latency of the first read from the SD Card.

yup... popcorn is by no means fool proof at this point :-)

added converter (non trivial and requires Linux likely)


New public API

Closes #25.
What this PR will do:

Remove the ByHash functions and make all of their sister functions accept hashes instead. Example: Degree(vertex T) and DegreeByHash(vertexHash K) is unified into Degree(vertexHash K).
Change all method names except getters to the form verb + subject. Example: Vertex becomes AddVertex.
Remove functions that don't modify but operate on the graph from the Graph interface and make them standalone functions that accept a Graph instead. Example Graph.DFS() becomes DFS(Graph).
Introduce the new Vertex and Predecessors methods.
Make all functions that could potentially fail return an error.

@geoah This is pretty much finished. You can re-review this PR if you want to, otherwise I'm just going to merge it and release it as version 0.9.0.

@geoah Thanks for your help!

Release v0.9.0
<EMAIL_ADDRESS>


adapt to new crowbar-init api namespace

depends on: https://github.com/crowbar/crowbar-init/pull/43

gating will likely fail due to the missing dependency on https://github.com/crowbar/crowbar-init/pull/43
so I'll merge https://github.com/crowbar/crowbar-init/pull/43 trigger trackupstream and we rerun the gating here.
sorry for the temporary breakage, but there is no other way it seems

I think this broke the susecloud7 deployment because we have there still the old endpoint so we need here an if to use the old URL for M5 and older.

The susecloud gating also failed see: https://ci.suse.de/job/openstack-mkcloud/40523/console


Docs refer to deprecated webpack.optimize.UglifyJsPlugin

https://webpack.js.org/configuration/plugins/#plugins
I don't know if there's other stuff that needs to be updated here, or if maybe the documentation's been updated but it's just not published...

The UglifyJsPlugin itself isn't, but accessing webpack.optimize.UglifyJsPlugin is, because you're supposed to add it as a dependency and pass it to optimization.minimizer

Uhmm, using it as a plugin triggers a warning or something?
I think it works just fine as a plugin.

webpack.optimize.UglifyJsPlugin isn't exposed anymore, one has to explicitly import it since webpack >= v4.0.0
- const UglifyJsPlugin = webpack.optimize.UglifyJsPlugin
+ const UglifyJsPlugin = require('uglifyjs-webpack-plugin')

It ships with webpack and options can be passed to the 'build-in' plugin via config.optimization.minimize removing the need to import it at all in most cases

Please send a PR to this page (https://webpack.js.org/configuration/plugins/#plugins) updating it with your findings.

You just need to remove it from the plugins https://webpack.js.org/configuration/plugins/#plugins page
It is documented here btw: https://webpack.js.org/configuration/optimization/

Also presumably the CommonsChunkPlugin usage should be updated to show requireing it, and likely other stuff is outdated. I don't want to work on this; I've never used the plugins option, and so I hope someone with at least that qualification can pick this up.

@1j01 ok, in that case im picking it up


Create a new pull request by comparing changes across two branches

Bumps engine.io from 6.4.1 to 6.4.2.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: engine.io dependency-type: indirect ...

Description

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[ ] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 95.983%

Files with Coverage Reduction
New Missed Lines
%

js/src/util/focustrap.js
1
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
2017

Relevant Lines:
2068

💛  - Coveralls


[QUESTION] How to get current summoner's name from LoL client

I'm new on this API. Just wondering how to get real-time summoner's name from LoL client when joining a match. Is this possible?
I'm aware that OP.GG does it through their Chrome extension, but not sure how it can be done or we have other options.
I know that a simple way could be by filling your summoner name in a website form and refreshing once you join a match, but I'd like to do it without user intervention.
This package looks very interesting!

Hi, this library does not support the League Client APIs as PHP is not a very good language for working with asynchronous code.
OP.GG uses the League Client Update APIs (https://developer.riotgames.com/docs/lol#league-client)
You can probably get a good answer for your question in the Riot Games API Discord (https://discord.gg/riotapi)


Add IPCC AR6-based dynamic characterization functions

Lifetime and radiative efficiency data is here: https://github.com/chrisroadmap/ar6/blob/main/data_input/ghg_properties/metrics_supplement.csv

d50056a93cc1adf52d28b62f175f37fdbc68de75


how to added backdrop blur please

how to added backdrop blur please

You can try adding it via CSS, but I don't think it's included with the default version of the package.


 It means the player quickly gets bored because of the low difficulty of the game and lack of encouragement and reward.
The ball should speed up a bit by each wave of bricks. Along with starting with a higher velocity.


Pulsing/flickering windows when switching focus left and right back and forth

Hey guys,
I encounter a strange behavior when changing focus in a specific order.
In the Video below, I started with changing focus from right to left. So with ALT-h only, I switched from Wezterm to Arc and so on.
After a while, I changed the direction and changing focus from left to right. So with ALT-L only, I switched from Arc to Wezterm and so on.
And then the weird behavior appears. When changing the focus from Arc (on the left) to Wezterm (on the right) with ALT-L, Arc is pulsing. And when I use ALT-L again to change focus from Wezterm to Arc, Wezterm is changing position for a short time.
I am using the latest Verion of OSX: Sequoia 15.0.1
I already reinstalled Aerospace again, but encounter the same behavior.
https://github.com/user-attachments/assets/3618f0ab-61d4-4e82-94cb-43d47f142c3c
Checklist

[ x] I've searched for duplicates. My search queries were (please don't forget to search in closed issues too):

focus
switch window focus
direction

[ x] I've read the guide https://nikitabobko.github.io/AeroSpace/guide

aerospace CLI client version: 0.14.2-Beta

Interesting! If you didn't attach the video, I'd not believe you :)
Does it happen only with Arc/WezTerm pair?

Haha that's why I attached the video 😅
No, it happens with every combination of applications. (and also with more than 2 windows, and always these on the left side has this behavior)
"Displays have separate Spaces" is on default, so "true" I think - I though this setting is only implrtant if you have multiple screens - but I can test it later when I'm home.

UPDATE:
Still same issue after I disabled "Displays have separate Spaces"

Well, it looks like reinstalling it for the third time fixed the issue somehow...
Solved, I think..


Fix building python bindings on unix systems with both python2 and python3

Pull request type

Please check the type of change your PR introduces:

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

What is the current behavior?
Building ecal with python bindings on a unix system with both python2 and python3 fails. CMake selects python2 instead of python3 when both versions are installed on the same system.
-- Could NOT find Python (missing: Python_INCLUDE_DIRS Development Development.Module Development.Embed) (found version "2.7.18")
-- Python interpreter found: /usr/bin/python2.7
-- Installing Python extensions
-- Could NOT find Python (missing: Python_INCLUDE_DIRS Development Development.Module Development.Embed) (found version "2.7.18")
CMake Error at cmake/helper_functions/ecal_python_functions.cmake:47 (Python_add_library):
  Unknown CMake command "Python_add_library".
Call Stack (most recent call first):
  lang/python/core/CMakeLists.txt:39 (ecal_add_python_module)

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

CMake checks if its a unix system and sets Python_EXECUTABLE to  /usr/bin/python3

if (UNIX)
     set(Python_EXECUTABLE /usr/bin/python3)
endif (UNIX)

Does this introduce a breaking change?

[ ] Yes
[x] No

Hi @CruxDevStuff,
Thanks for contributing!
However, hardcoding a path in the CMakeLists.txt is not the proper way to solve the issue and will lead to many problems. Basically whenever you want to use anything else then what is hardcoded, e.g. different python versions that may be natively installed as /usr/bin/python3.10, /usr/bin/python3.11 or when you use a python venv. We make heavy use of python venvs in our GitHub Action build scripts to generate all those different python wheels.
What you should rather do is provide the path as command line argument to CMake, or set the according environment variable. The CMake command line expects the python path as -DPython_EXECUTABLE=/usr/bin/python3. I think you can also provide the Python3_ROOT_DIR variable for FindPython3: https://cmake.org/cmake/help/latest/module/FindPython3.html
As mentioned earlier, we use python venvs in our GitHub Action CI, which also solves the issue of choosing between python2 / python3, as a venv only holds 1 python version that you specifically chose when creating the venv. You can check how we create those venvs here in our build scripts:
https://github.com/eclipse-ecal/ecal/blob/6b2843ad29597e7de06a6f80e99572006eeb097a/.github/workflows/build-ubuntu-22.yml#L45-L54
Also note the command line parameter that tells cmake to only find a currently activated venv:
https://github.com/eclipse-ecal/ecal/blob/6b2843ad29597e7de06a6f80e99572006eeb097a/.github/workflows/build-ubuntu-22.yml#L96


Users do net get synchronized between the two databases

Currently when the user logs in for the first time, their data is transferred from the applications platform database to the local database of the hub with the hope to improve performance.
The synchronization problems with this approach have proven to outweigh the benefits in performance.
The user system should get changed such that the app uses only the applications platform database for user data.

Working on this issue on the user-db-sync branch. We now check for an updated password when the password check fails and the user is already on the hub


Time Imformation not showing logs

In Time information [pressed LShift+Alt+AltGr+RCtrl+Pause] logs not showing before saving. After saving same thing but module time works. I tested with FreeDOS portable following:
Motherboard: ASRock 970 Extreme 4
CPU: AMD FX-8320 supported MMX
32GB of RAM
GPU: geForce GTX 1080 [works perfectly with Impulse Tracker]
IT EMS: 32MB
IT Driver: Sound Blaster 16 MMX [SBEMU emulation into Intel HDA]

That is by design -- timestamps are only saved when a file is written.