As a user I expect values to be emitted in descending order

Feature Request
Description of Problem:
When generating data and only a upper-bound operator (e.g. lessThan, before) is applied, values should be emitted in reverse (descending) order.

See #314 and #590

The following behaviour can be described

lower bound operator
upper bound operator
expected data (in order )

none
lessThan 10
9, 8, 7, ...

greaterThan 1
lessThan 10
2, 3, 4...

greaterThan 1
none
2, 3, 4, ...

none
before 2010-02-10
2010-02-09, 2010-02-08, ...

after 2010-02-07
before 2010-02-10
2010-02-08, 2010-02-09

after 2010-02-07
none
2010-02-08, 2010-02-09, ...

As a user I would expect the data to be emitted as such, as the generator would emit data that is 'closer' to my constraints before this 'farther' from them.
Questions

Should this apply to textual shorterThan operator too?
Should this be configurable

should this be closed

should this be closed

I think it should be kept as a feature, mostly for when interesting and full-sequential data generation is worked on.

Ignored cucumber tests removed from Null.feature:
@ignore #Relates to issue #594 - Reverse order of value generation when only upper-bound operators are provided. Counts up from minimum possible double
Scenario: Not 'null' with a non contradicting 'lessThan' should be successful
Given foo is anything but null
And foo is less than 1
And foo has type "integer"
And the generator can generate at most 2 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
Scenario: Not 'null' with a non contradicting 'lessThanOrEqualTo' should be successful
Given foo is anything but null
And foo has type "integer"
And foo is less than or equal to 1
And the generator can generate at most 2 rows
Then the following data should be generated:
| foo |
| 1   |
| 0   |

The following tests were removed from GreaterThan.feature:
@ignore #594 - Reverse order of value generation when only upper-bound operators are provided
Scenario: not greaterThan run against a non contradicting not greaterThan should be successful (not greaterThan 5 AND not greaterThan 4)
Given foo is anything but greater than 5
And foo is anything but greater than 4
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 3   |
| 2   |
| 1   |
| 0   |
| -1  |
Scenario: not greaterThan run against a non contradicting not greaterThanOrEqualTo should be successful (not greaterThan 5 AND not greaterThanOrEqualTo 4)
Given foo is anything but greater than 5
And foo is anything but greater than or equal to 4
And foo has type "integer"
And foo is anything but null
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: not greaterThan run against a non contradicting lessThan should be successful (not greaterThan 4 AND lessThan 2)
Given foo is anything but greater than 4
And foo is less than 2
And foo has type "integer"
And foo is anything but null
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 1   |
| 0   |
| -1  |
| -2  |
| -3  |
Scenario: not greaterThan run against a non contradicting lessThanOrEqualTo should be successful (not greaterThan 4 AND lessThanOrEqualTo 2)
Given foo is anything but greater than 4
And foo is less than or equal to 2
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 2   |
| 1   |
| 0   |
| -1  |
| -2  |
Scenario: not greaterThan run against a non contradicting granularTo should be successful (not greaterThan 4 AND granularTo 0.1)
Given foo is anything but greater than 4
And foo is granular to 0.1
And foo is anything but null
And foo has type "decimal"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 3.9 |
| 3.8 |
| 3.7 |
| 3.6 |
| 3.5 |

The following tests were removed from the GreaterThanOrEqualTo feature:
Scenario: not greaterThanOrEqualTo run against a non contradicting not greaterThanOrEqualTo should be successful
Given foo is anything but greater than or equal to 5
And foo is anything but greater than or equal to 5
And the generator can generate at most 5 rows
And foo has type "integer"
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |

The following tests were removed from LessThan.feature:
Scenario: Running a 'lessThan' request that specifies an integer should be successful
Given foo is less than 1
And foo is anything but null
And the generator can generate at most 5 rows
And foo has type "integer"
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: Running a 'lessThan' request that specifies an integer with trailing zeros should be successful
Given foo is less than 100
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 99  |
| 98  |
| 97  |
| 96  |
| 95  |
Scenario: Running a 'lessThan' request that specifies a decimal should be successful
Given foo is less than 100.1
And foo is anything but null
And the generator can generate at most 5 rows
And foo has type "decimal"
Then the following data should be generated:
| foo                      |
|<PHONE_NUMBER>9999999999999 |
|<PHONE_NUMBER>9999999999999 |
|<PHONE_NUMBER>9999999999998 |
|<PHONE_NUMBER>9999999999997 |
|<PHONE_NUMBER>9999999999996 |
Scenario: Running a 'lessThan' request that specifies a decimal with trailing zeros should be successful
Given foo is less than 100.0
And foo is anything but null
And the generator can generate at most 5 rows
And foo has type "decimal"
Then the following data should be generated:
| foo |
| 99  |
| 98  |
| 97  |
| 96  |
| 95  |
Scenario: Running a 'lessThan' request that includes a negative value should be successful
Given foo is less than 0
And foo has type "integer"
And foo is anything but null
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| -1  |
| -2  |
| -3  |
| -4  |
| -5  |
Scenario: lessThan run against a non contradicting lessThan should be successful (lessThan 2 AND lessThan 5)
Given foo is less than 2
And foo is less than 5
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 1   |
| 0   |
| -1  |
| -2  |
| -3  |
Scenario: lessThan run against a non contradicting lessThanOrEqualTo should be successful (lessThan 6 AND lessThanOrEqualTo 5)
Given foo is less than 6
And foo is less than or equal to 5
And foo has type "integer"
And foo is anything but null
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 5   |
| 4   |
| 3   |
| 2   |
| 1   |
Scenario: lessThan run against a contradicting lessThanOrEqualTo should only only generate string, datetime and null (lessThan 1 AND lessThanOrEqualTo 1)
Given foo is less than 1
And foo is less than or equal to 1
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting granularTo should be successful (lessThan 2 AND granularTo 1)
Given foo is less than 2
And foo is granular to 1
And foo is anything but null
And foo has type "decimal"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 1   |
| 0   |
| -1  |
| -2  |
| -3  |
Scenario: lessThan run against a non contradicting not granularTo should be successful (lessThan 1 AND not granularTo 1)
Given foo is less than 1
And foo is anything but granular to 1
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo  |
| null |
Scenario: not lessThan run against a non contradicting not granularTo should be successful (not lessThan 5 AND not granularTo 1)
Given foo is anything but less than 5
And foo is anything but granular to 1
And foo has type "decimal"
And the generator can generate at most 5 rows
Then some data should be generated
Scenario: lessThan run against a non contradicting after should be successful (lessThan 1 AND after 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is after 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo         |
| -2147482624 |
| -2147482623 |
| -2147482622 |
| -2147482621 |
| -2147482620 |
Scenario: lessThan run against a non contradicting not after should be successful (lessThan 1 AND not after 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo has type "integer"
And foo is anything but after 2019-01-01T00:00:00.000Z
And foo is anything but null
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting after should be successful (lessThan 1 AND afterOrAt 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is after or at 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting not after should be successful (lessThan 1 AND not afterOrAt 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is anything but after or at 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting after should be successful (lessThan 1 AND before 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is before 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting not after should be successful (lessThan 1 AND not before 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is anything but before 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting after should be successful (lessThan 1 AND beforeOrAt 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is before or at 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThan run against a non contradicting not after should be successful (lessThan 1 AND not beforeOrAt 2019-01-01T00:00:00.00)
Given foo is less than 1
And foo is anything but before or at 2019-01-01T00:00:00.000Z
And foo is anything but null
And foo has type "integer"
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |

The following tests were removed from LessThanOrEqualTo.feature:
Scenario: Running a 'lessThanOrEqualTo' request that includes positive integer should be successful
Given foo is less than or equal to 10
And the generator can generate at most 10 rows
And foo is anything but null
And foo has type "integer"
Then the following data should be generated:
| foo |
| 1   |
| 2   |
| 3   |
| 4   |
| 5   |
| 6   |
| 7   |
| 8   |
| 9   |
| 10  |
Scenario: Running a 'lessThanOrEqualTo' request that includes positive decimal should be successful
Given foo is less than or equal to 10.0
And the generator can generate at most 5 rows
And foo is anything but null
And foo has type "integer"
Then the following data should be generated:
| foo  |
| 10.0 |
| 9.9  |
| 9.8  |
| 9.7  |
| 9.6  |
Scenario: Running a 'lessThanOrEqualTo' request that includes negative integer should be successful
Given foo is less than or equal to -10
And the generator can generate at most 5 rows
And foo is anything but null
And foo has type "integer"
Then the following data should be generated:
| foo |
| -10 |
| -9  |
| -8  |
| -7  |
| -6  |
Scenario: Running a 'lessThanOrEqualTo' request that includes 0 should be successful
Given foo is less than or equal to 0
And the generator can generate at most 5 rows
And foo is anything but null
And foo has type "integer"
Then the following data should be generated:
| foo |
| 0   |
| -1  |
| -2  |
| -3  |
| -4  |
Scenario: lessThanOrEqualTo run against a non contradicting lessThanOrEqualToOrEqualTo should be successful
Given foo is less than or equal to 5
And foo is less than or equal to 5
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 5   |
| 4   |
| 3   |
| 2   |
| 1   |
Scenario: lessThanOrEqualTo run against a non contradicting granularTo should be successful
Given foo is less than or equal to 3
And foo has type "decimal"
And foo is granular to 1
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 3   |
| 2   |
| 1   |
| 0   |
| -1  |
Scenario: lessThanOrEqualTo run against a non contradicting not granularTo should be successful
Given foo is less than or equal to 3
And foo is anything but granular to 0.1
And foo has type "decimal"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 3   |
| 2   |
| 1   |
| 0   |
| -1  |
Scenario: lessThanOrEqualTo run against a non contradicting after should be successful
Given foo is less than or equal to 5
And foo is after 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting not after should be successful
Given foo is less than or equal to 5
And foo is anything but after 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting afterOrAt should be successful
Given foo is less than or equal to 5
And foo is after or at 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting not afterOrAt should be successful
Given foo is less than or equal to 5
And foo is anything but after or at 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting before should be successful
Given foo is less than or equal to 5
And foo is before 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting not before should be successful
Given foo is less than or equal to 5
And foo is anything but before 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting beforeOrAt should be successful
Given foo is less than or equal to 5
And foo is before or at 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |
Scenario: lessThanOrEqualTo run against a non contradicting not beforeOrAt should be successful
Given foo is less than or equal to 5
And foo is anything but before or at 2019-01-01T00:00:00.000Z
And foo has type "integer"
And the generator can generate at most 5 rows
And foo is anything but null
Then the following data should be generated:
| foo |
| 4   |
| 3   |
| 2   |
| 1   |
| 0   |

The following tests were removed from After.feature:
Scenario: 'Not After' with a non-contradicting 'Not After' is successful
Given foo is anything but after 2019-01-01T00:00:00.000Z
And foo is anything but after 2020-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2019-01-01T00:00:00.000Z |
| 2018-12-31T23:59:59.999Z |
| 2018-12-31T23:59:59.998Z |
| 2018-12-31T23:59:59.997Z |
| 2018-12-31T23:59:59.996Z |
Scenario: 'Not After' with a non-contradicting 'Not After Or At' is successful
Given foo is anything but after 2019-01-01T00:00:00.000Z
And  foo is anything but after or at 2020-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2019-01-01T00:00:00.000Z |
| 2018-12-31T23:59:59.999Z |
| 2018-12-31T23:59:59.998Z |
| 2018-12-31T23:59:59.997Z |
| 2018-12-31T23:59:59.996Z |
Scenario: 'Not After' with a non-contradicting 'Before' is successful
Given foo is anything but after 2019-01-01T00:00:00.000Z
And foo is before 2019-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2018-12-31T23:59:59.999Z |
| 2018-12-31T23:59:59.998Z |
| 2018-12-31T23:59:59.997Z |
| 2018-12-31T23:59:59.996Z |
| 2018-12-31T23:59:59.995Z |
Scenario: 'Not After' with a non-contradicting 'Before Or At' is successful
Given foo is anything but after 2019-01-02T00:00:00.000Z
And  foo is before or at 2019-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2019-01-01T00:00:00.000Z |
| 2018-12-31T23:59:59.999Z |
| 2018-12-31T23:59:59.998Z |
| 2018-12-31T23:59:59.997Z |
| 2018-12-31T23:59:59.996Z |

The following tests were removed from Before.feature:
Scenario: Running a 'before' request over a year threshold should be successful
Given foo is before 2019-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2018-12-31T23:59:59.999Z |
| 2018-12-31T23:59:59.998Z |
| 2018-12-31T23:59:59.997Z |
| 2018-12-31T23:59:59.996Z |
| 2018-12-31T23:59:59.995Z |
Scenario: Running a 'before' request over a leap year date should be successful
Given foo is before 2016-03-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| null                     |
| 2016-02-29T23:59:59.999Z |
| 2016-02-29T23:59:59.998Z |
| 2016-02-29T23:59:59.997Z |
| 2016-02-29T23:59:59.996Z |
Scenario: Running a 'before' request that specifies the maximum valid system date should be successful
Given foo is before 9999-12-31T23:59:59.999Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| null                     |
| 9999-12-31T23:59:59.998Z |
| 9999-12-31T23:59:59.997Z |
| 9999-12-31T23:59:59.996Z |
| 9999-12-31T23:59:59.995Z |
Scenario: 'before' run against a non contradicting 'before' should be successful
Given foo is before 2019-01-01T00:00:00.000Z
And foo is before 2018-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2017-12-31T23:59:59.999Z |
| 2017-12-31T23:59:59.998Z |
| 2017-12-31T23:59:59.997Z |
| 2017-12-31T23:59:59.996Z |
| 2017-12-31T23:59:59.995Z |
Scenario: 'before' run against a non contradicting not 'before' should be successful
Given foo is before 2019-01-02T00:00:00.000Z
And foo is anything but before 2019-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| null                     |
| 2019-01-01T23:59:59.999Z |
| 2019-01-01T23:59:59.998Z |
| 2019-01-01T23:59:59.997Z |
| 2019-01-01T23:59:59.996Z |
Scenario: 'before' run against a non contradicting 'beforeOrAt' should be successful
Given foo is before 2019-01-01T00:00:00.000Z
And foo is before or at 2018-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2018-01-01T00:00:00.000Z |
| 2017-12-31T23:59:59.999Z |
| 2017-12-31T23:59:59.998Z |
| 2017-12-31T23:59:59.997Z |
| 2017-12-31T23:59:59.996Z |

The following tests were removed from the BeforeOrAt.feature file:
Scenario: User requires to create a datetime field with date (YYYY-MM-DD) values within a given month that are less than or at a specified date
Given foo is before or at 2018-10-10T00:00:00.000Z
And the generator can generate at most 30 rows
Then the following data should be generated:
| foo                      |
| 2018-10-01T00:00:00.000Z |
| 2018-10-02T00:00:00.000Z |
| 2018-10-03T00:00:00.000Z |
| 2018-10-04T00:00:00.000Z |
| 2018-10-05T00:00:00.000Z |
| 2018-10-06T00:00:00.000Z |
| 2018-10-07T00:00:00.000Z |
| 2018-10-08T00:00:00.000Z |
| 2018-10-09T00:00:00.000Z |
| 2018-10-10T00:00:00.000Z |
Scenario: User requires to create a datetime field with date and time (YYYY-MM-DDTHH:MM:SS) values across a minute boundary that are less than or at specified date and time
Given foo is before or at 2018-10-01T12:01:05.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2018-10-01T12:01:05.000Z |
| 2018-09-01T12:01:02.000Z |
| 2018-07-01T12:01:03.000Z |
| 2018-06-01T12:01:04.000Z |
Scenario: Running beforeOrAt request that includes datetime field with date and time (YYYY-MM-DDTHH:MM:SS) values that has leap year
Given foo is before or at 2024-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                     |
| 2016-10-01T12:01:05.000 |
| 2012-09-01T12:01:02.000 |
| 2024-07-01T12:01:03.000 |
Scenario: Running beforeOrAt request against a non-contradicting beforeOrAt constraint should be successful
Given foo is before or at 2019-01-01T00:00:00.000Z
And foo is before or at 2018-01-01T00:00:00.000Z
And the generator can generate at most 5 rows
Then the following data should be generated:
| foo                      |
| 2018-01-01T00:00:00.000Z |
| 2017-12-31T23:59:59.999Z |
| 2017-12-31T23:59:59.998Z |
| 2017-12-31T23:59:59.997Z |
| 2017-12-31T23:59:59.996Z |


Support #r @" " and #r """ """ strings

Disable response file support for kernel directives.  This ensures that @"" and """ """ are passed through to interactive.
Re-enable the tests for this.

@colombod can we get this merged pls.


Windows Phone 8.1 XAML support

Any plans for Windows Phone 8.1 XAML support?

Would like to bump this issue. 8.1 Phone XAML support is much needed.

Thanks gray will. We are in high need of this in next month.
On Jan 20, 2015 2:37 AM, "graywill"<EMAIL_ADDRESS>wrote:

Would like to bump this issue. 8.1 Phone XAML support is much needed.
—
Reply to this email directly or view it on GitHub
https://github.com/Redth/ZXing.Net.Mobile/issues/111#issuecomment-70560856
.

Thanks for fast action , But make it fast my project is struck  with barcode reader in Windows phone 8.1  issue .

Hi All,
Have anybody found solution on scanning GS1 128 barcode using Zxing or any other API from Windows phone 8.1.
Our golive is not possible without this feature implemented. Any help is highly appreciated!!!
Thanks

Any updates of this issue?

In discussion ...  https://zxingnet.codeplex.com/discussions/566782  ... somebody mentioned VideoEffect lib ... I also tried it ... it is good

For everyone who needs a working solution, here is a sample app using ZXing.NET and Nokia Imaging Toolkit extracted from a project where I have it working: https://github.com/igorkulman/QRReader.WPA81

Hi All,
will the above solutions work for scanning GS 1 128 barcodes?  Any update with zxing library to support this barcode format on windows phone 8.1?

Please track this in #169
This is an enhancement.

Does someone know an alternative bar code scanner which support WIndows phone 8.1 ? I don't find any.

Likely not, as there's no managed API for capturing the preview image buffer contents in 8.1.  There are a couple out there that might work on Nokia phones only for example, but nothing that doesn't make use of vendor specific SDK's that I know of.


Improve visibility of roles being created by iambic setup

Is your feature request related to a problem? Please describe.
During iambic setup, it will attempt to create IambicHubRole and IambicSpokeRole. As a user, I want to preview the permissions granted to these roles.
Describe the solution you'd like
It should link to the definition of permissions granted to IambicHubRole and IambicSpokeRole.
Describe alternatives you've considered
Print to standard out or offer to print to pdf
Additional context
(env) stevenmoy@steven-noqdev-mbp iambic % iambic setup
2023/04/11 16:08:59 [info     ] Setting config metadata...
2023/04/11 16:08:59 [info     ] Plugins loaded successfully...
? To get started with the IAMbic setup wizard, you'll need an AWS account.
This is where IAMbic will deploy its main role. If you have an AWS Organization, that account will be your hub account.
Review to-be-created IAMbic roles at https://iambic.org/reference/aws_hub_and_spoke_roles
Which Account ID should we use to deploy the IAMbic hub role?

https://github.com/noqdev/iambic/pull/318 should tackle this

Close as #318 has been merged


Replace the Tasmota control with Home Assistant integration

~Make the Jellyfin DeviceId consistent across reboots.~ done in release jellyfin-media-player-2022-08-22-1661167363
~This then allows the stock Jellyfin integration to work consistently.~
Figure out creating my own custom "device" in Home Assistant
Somehow send updates to that "device" for volume/mute state, and TV output state.

This can probably be achieved via their ReST api
It'd be great if I could somehow do this with the single Jellyfin "device",
but I don't seem to be able to add my own state attributes there without removing/replacing the rest of them too.

New plan, because I kinda want to continue to support Tasmota TV power control at least (so as to discourage IR)
Instead of putting a hostname in the kernel cmdline, I instead put a webhook URL, and use some standard syntax for the webhook that I can make work the same for both Tasmota & Home Assistant.
Then on a Home Assisted network it'll be pointing to a Home Assistant automation, and on a Tasmota controlled network it'll be pointing straight to the Tasmota device

I'm using MQTT instead of webhhooks for HA support, and in theory it should work exactly the same with a Tasmota device directly using MQTT.
Webhooks didn't really work for HA because they can't be used to send response data back, they are a simple "button" and nothing more.
I intend to continue supporting Tasmota HTTP control (for TV at least) anyway, so that I can drop IR support for controlling the TV, and don't have to set up an MQTT/HA/etc system on a more standalone network.


iOS app crashes for WIKI with images

I have a group with wiki, the wiki has images. When opening the wiki site, the IOS app crashes.

Please use the "report a problem" feature and send us your logs.
To do this: on the hamburger menu (upper left), upper left, Settings, , Help, Report an issue.


[Trivial] Increasing go test run default timeout to avoid intermittent failure of TestVolumeProperties

Increasing go test run default timeout to avoid intermittent failure of TestVolumeProperties
/cc @govint @pdhamdhere

Do we know the root cause for the failures ? If yes - what is the Issue # ? If no - please file an issue and then this patch is LGTM

Do we know the root cause for the failures ? If yes - what is the Issue # ? If no - please file an issue

Thanks @msterin, I will raise an issue first.

ok. Please add the issue # to this PR description and it's good to go

It is already added as part of description. it's #1078

10minutes is already long enough. We should fix testbed issues or minimize running tests.

Makes sense. Testbed cleanup and improvement is done. Closing this PR and issue as wontfix if we see more occurrences then bring back this change for the review.


Add CLI Command to add a genesis miner to GenesisTemplate (with relevant preseal info) and give the miner some balance

https://github.com/filecoin-project/lotus/blob/9b1d2f4c137433c1fe1f5ed44ba2e70105a409f0/cmd/lotus-seed/genesis.go#L29

starting on this


Tensorflow 2.1.0 :  TypeError: new() got an unexpected keyword argument 'serialized_options'

I am facing an error while importing tensorflow-2.1.0 (CPU) with Python 3.6 in Ubuntu 18.
protobuf Version: 3.11.3
Tried many solutions provided in the same Tensorflow GitHub issue pages..But none were useful.
I dont have any NVIDIA, CUDA etc.. (I dont want to install them as i would like to go with CPU)
Following errors appeared.
[Mon Feb 24 11:44:52.926212 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372] mod_wsgi (pid=5520): Exception occurred processing WSGI script '/var/www/testnig/service.wsgi'.
[Mon Feb 24 11:44:52.927298 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372] Traceback (most recent call last):
[Mon Feb 24 11:44:52.927347 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/service.wsgi", line 9, in
[Mon Feb 24 11:44:52.927352 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from service import app as application
[Mon Feb 24 11:44:52.927358 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/service.py", line 11, in
[Mon Feb 24 11:44:52.927362 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     import classify
[Mon Feb 24 11:44:52.927367 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/classify.py", line 3, in
[Mon Feb 24 11:44:52.927370 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     import tensorflow as tf
[Mon Feb 24 11:44:52.927376 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow/init.py", line 98, in
[Mon Feb 24 11:44:52.927379 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from tensorflow_core import *
[Mon Feb 24 11:44:52.927384 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/init.py", line 42, in
[Mon Feb 24 11:44:52.927388 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from . _api.v2 import audio
[Mon Feb 24 11:44:52.927393 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/_api/v2/audio/init.py", line 10, in
[Mon Feb 24 11:44:52.927397 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from tensorflow.python.ops.gen_audio_ops import decode_wav
[Mon Feb 24 11:44:52.927402 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/python/ops/gen_audio_ops.py", line 11, in
[Mon Feb 24 11:44:52.927406 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from tensorflow.python.eager import context as _context
[Mon Feb 24 11:44:52.927411 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/context.py", line 29, in
[Mon Feb 24 11:44:52.927414 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from tensorflow.core.protobuf import config_pb2
[Mon Feb 24 11:44:52.927420 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/core/protobuf/config_pb2.py", line 16, in
[Mon Feb 24 11:44:52.927423 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from tensorflow.core.framework import cost_graph_pb2 as tensorflow_dot_core_dot_framework_dot_cost__graph__pb2
[Mon Feb 24 11:44:52.927436 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/core/framework/cost_graph_pb2.py", line 16, in
[Mon Feb 24 11:44:52.927440 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
[Mon Feb 24 11:44:52.927445 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]   File "/var/www/testnig/venv/lib/python3.6/site-packages/tensorflow_core/core/framework/tensor_shape_pb2.py", line 23, in
[Mon Feb 24 11:44:52.927449 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372]     serialized_pb=_b('\n,tensorflow/core/framework/tensor_shape.proto\x12\ntensorflow\"z\n\x10TensorShapeProto\x12-\n\x03\x64im\x18\x02 \x03(\x0b\x32 .tensorflow.TensorShapeProto.Dim\x12\x14\n\x0cunknown_rank\x18\x03 \x01(\x08\x1a!\n\x03\x44im\x12\x0c\n\x04size\x18\x01 \x01(\x03\x12\x0c\n\x04name\x18\x02 \x01(\tBq\n\x18org.tensorflow.frameworkB\x11TensorShapeProtosP\x01Z=github.com/tensorflow/tensorflow/tensorflow/go/core/framework\xf8\x01\x01\x62\x06proto3')
[Mon Feb 24 11:44:52.927464 2020] [wsgi:error] [pid 5520:tid<PHONE_NUMBER>91808] [remote <IP_ADDRESS>:34372] TypeError: new() got an unexpected keyword argument emphasized text'serialized_options'
Steps to reproduce : (I am using Apache2, Flask & python3 for NSFW detection). However following are the simplest ways to reproduce.

In Ubuntu 18, install python 3.6 and create a Virtualenv. Activate Virtualenv
pip3 install tensorflow
Clone or Download GIT --> github.com/minto5050/NSFW-detection
python3 classify.py test_image.jpg

Please let me know if you need any other information

@votesappteam
please refer to this link related to protobuf, let us know if it helps resolve your issue.

@Saduf2019
I have tried all of the solution you mentioned.
Please understand those were all Tensorflow version less than 2.
None of the solution helped.
Please help.

@votesappteam
I tried replicating the code shared by you and face a different error,please refer to the gist for the same

Hi Sadu,
The original code Github is not compatible with Tensorflow version 2.
Please replace code in classify.py with below:
import os, sys
import tensorflow as tf
#https://github.com/minto5050/NSFW-detection
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'
tf.config.optimizer.set_jit(True)
# change this as you see fit

image_path = img
# Read in the image_data

image_data = tf.io.gfile.GFile(image_path, 'rb').read()
# Loads label file, strips off carriage return

label_lines = [line.rstrip() for line
in tf.io.gfile.GFile("retrained_labels.txt")]
# Unpersists graph from file

with tf.io.gfile.GFile("retrained_graph.pb", 'rb') as f:
graph_def = tf.compat.v1.GraphDef()
graph_def.ParseFromString(f.read())
tf.import_graph_def(graph_def, name='')
with tf.compat.v1.Session() as sess:
# Feed the image_data as input to the graph and get first prediction
softmax_tensor = sess.graph.get_tensor_by_name('final_result:0')
predictions = sess.run(softmax_tensor, \
                           {'DecodeJpeg/contents:0': image_data})

    # Sort to show labels of first prediction in order of confidence
top_k = predictions[0].argsort()[-len(predictions[0]):][::-1]
scoreDict = []
for node_id in top_k:
    human_string = label_lines[node_id]
    score = predictions[0][node_id]
    scoreDict.append(human_string+":"+str(score))
    print('%s (score = %.5f)' % (human_string, score))

@votesappteam
could you please provide us with simple standalone indented code to replicate your issue in our local or share a gist of the error, if possible in colab for us to analyse it.

@votesappteam
could you please update as per above comment

I will respond
On Wed, Mar 18, 2020 at 12:53 PM, Saduf2019<EMAIL_ADDRESS>wrote:

@votesappteam https://github.com/votesappteam
could you please update as per above comment
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/37019#issuecomment-600464239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUTBXQNKO2G6G7SS4ZUIA3RIBZF5ANCNFSM4K2JDJIA
.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

I'm having the same issue with tensorflow version 2.3.1 is there any solution?
Thank you in advance


Options to clear shell, and clear history

15:54:51.274 ~/Projects/tab-rs [0]
⦔ clear
terminals database is inaccessible

Because sometimes you want to clear the shell and or the history.

I think this is a bug related to the $TERM env var.  I'll take a look!

Hey @casonadams.  I've merged some code to main that should fix this (#280).  I couldn't reproduce it though - is any chance you could run scripts/run.sh test270 and see if you can clear your terminal?  (no need to shut down the daemon - and any unique tab name would work)

@austinjones seems to still be happening
12:44:43.026 ~/Projects/tab-rs [test270]
⦔ clear
terminals database is inaccessible
12:44:45.199 ~/Projects/tab-rs [test270]
⦔ echo $TERM
tmux-256color
12:45:25.575 ~/Projects/tab-rs [test270]
⦔

Hey @casonadams ,
I think the issue here is the tmux-256color value - which seems to have problems on OSX w/ terminfo.  See this tmux bug report: https://github.com/tmux/tmux/issues/1257
If you can figure out where it's coming from, xterm-256color should work.  I think all I can do in tab is pass the $TERM var along.

Hey @casonadams.  I just released [v0.5.4] with the $TERM fix.  Did you find anything else while looking at this that might be useful?  One thing I was wondering is if $TERMINFO was different inside/outside the session.

Hey @casonadams.  I just released [v0.5.4] with the $TERM fix.  Did you find anything else while looking at this that might be useful?  One thing I was wondering is if $TERMINFO was different inside/outside the session.

I'm going to close this.  I can't think of any other changes that might fix it.  Let me know if you have more info, though!

I'm going to close this.  I can't think of any other changes that might fix it.  Let me know if you have more info, though!


doctest discovery in packages and subpackages

testmod CLI, which receives a python source file, does not work for subpackages (because it only imports the module itself and cannot handle from . import XXX in-package imports).
Using the python API does not quite work either for public submodules:
>>> import run
>>> from scipy import interpolate
>>> run.testmod(interpolate)
TestResults(failed=0, attempted=0)

For private modules it actually works (modulo gh-6) :
>>> from scipy.interpolate import _bsplines
>>> run.testmod(_bsplines)
TestResults(failed=0, attempted=97)

Maybe the right thing to do is to provide both testmod as is to closely follow the doctest behavior and a refguide-check-like alternative. This alternative can be either a top-level function, or a Finder subclass, this need to be decided.
cross-ref: gh-4 which tracks a low-level test discovery etc.

Current status: mostly done in gh-22. Test-drive and polishing will be done when porting the scipy doctesting from refguide-check to here. So keep this open until then.

Seems to work OK in  gh-33.
The last remaining bit is to verify that all tests are included in the vanilla refguide-check run, are included here too (patch refguide-check to emit the names of objects).

https://github.com/scipy/scipy/pull/16391 confirms the list of objects is identical, so closing.


add basic status code tests for views

Closes #207
So beyond checking the status code. I could look into finding a way to create a assertion comparing the static/openapi.yaml file against the downloaded yaml file. I guess i would have to look into how to access the downloaded yaml file without using a hardcoded path in a context manager? What do you think?

I could look into finding a way to create a assertion comparing the static/openapi.yaml file against the downloaded yaml file.

That sounds good. How would you compare the files? Hash them and then compare the hashes? I'm not actually sure what the options are for file comparison in python...
Do you think that's overkill for the unit test? If it's something that interests you, I don't want to stop you, but I wonder if that gives us a lot more confidence than just checking for the 200 response.
A lighter weight option that might give us slightly more confidence than the 200 response is to just parse the file returned into a yaml.load() type of function. If that function successfully parses it without throwing an error, then we know that it returned a yaml file and we have a fair amount of confidence that it's the same yaml file because exactly where else would valid yaml come from out of that endpoint?

yeah i guess your right there is no other static yaml file to send. I like the idea of using yaml.load() to make sure that the yaml file was returned from that endpoint.

what do you think about also verifying the content type in the headers?
def test_open_api_yaml(module_client):
    response = module_client.get("/openapi.yaml")	    response = module_client.get("/openapi.yaml")
    assert (response.status_code == 200)	    assert (response.status_code == 200)

    stream = response.headers[1][1:]

    assert str(stream) == "('application/octet-stream',)"

I guess that's fine, but remember that the point of a unit test is to have some assurance that as you make changes, you'll find out if you broke anything. I like the yaml.load() idea because if that fails, we know we broke that route. With the content type, maybe it's a good thing if there's a client out there that would break if we returned something other than a stream, but it seems like as long as it's Yaml that gets to them, the content type is less relevant. Can't hurt to leave it in there, but I'd still like to see a test showing that it's valid yaml that is returned from that endpoint


Fixes "git checkout" typo to "git clone"

The git checkout should be git clone.

@mithro Would love a fomu if you have a spare one 😉(don't know if your request to pull request applies for this repo. if not it's all good :) ).

LGTM!

@syed-ahmed Send me an email<EMAIL_ADDRESS>- happy to send you a Fomu.


Recreated forms, refactored CSV, added concepts for BP & Chief complaint

Sync From Bahmni Main. for below changes
Recreated forms, refactored csv, added cocepts for BP

DO NOT MERGE, we need to push the AVNI related changes.


Issue template

Describe the bug
"2. Output of ha --version" is not always available, e.g., after a build with $ go build -o "ha".

Feel free to open up an PR to address the issue.

Actually, ha --version is not available at all.


docx: reinstate converter

Our .docx converter uses Pandoc. It needs to be refactored to our new API and the Pandoc JSON to Stencila JSON conversion reimplemented based on our new schema.

This is currently in progress https://github.com/stencila/convert/pull/56.


allure reports

Add new workflow for Allure reports. In order to work it requires a branch with name "gh-pages"  and GitHub pages configured to use it. There is an example for allure reports in my repository: https://miniteckel.github.io/TestAutomationCourse-python-api-project/1/

Nice! How can I check those reports? @miniTeckel
Could you share any samples?
Thanks

You can see the report in my fork: https://miniteckel.github.io/TestAutomationCourse-python-api-project/1/#suites

But it's your own allure server. Can we use it for our repository?
How we can share those results with anyone?
If someone will clone this repository does he/she need to configure their own allure server?
@miniTeckel

Oh! I see it uses GitHub pages to publish allure reports.

Code is merged. Do I need to change something in the current repository in order to see/get the allure report? @miniTeckel

I got it - https://burhanh.github.io/TestAutomationCourse-python-api-project/1/


Testing Update

tests:
-increased tolerance for random walk displacement Simulation class tests
-added Version class test comparing alpha and rc prerelease names

Pull Request Test Coverage Report for Build 56

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 99.176%

Totals

Change from base Build 53:
0.2%

Covered Lines:
842

Relevant Lines:
849

💛  - Coveralls


[BUG] deploying journey together with senderProfile/sendClassification leaves delivery profile ids empty

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Expected Behavior
No response
Steps To Reproduce

Go to '...'
Click on '....'
Run '...'
See error...

Version
7.5.0
Environment

OS:
Node:
npm:

Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
No response

Duplicate of #1769


Pausible

Crosschain function calls should be pausible This would allow crosschain bridges built on top of the crosschain function call approach to be paused.

GPACT  Crosschain Control contract is pausible. Closing issue.


Removed un-necessary allocation in assign_ops

This PR removes unnecessary allocation on assign_ops.
When converting PrimitiveArray -> MutablePrimitiveArray, we need to check that both the values and validities are unique refs. However, when operating over values and validities independently, we do not need a mutable ref to both at the same time.
A common case where this was hitting was when rhs had a validity and lhs did not. In this case, we first cloned the rhs's validity for lhs, but them tried to get a mut ref to both the validity and the values (to only use the values). This would naturally fail, causing us to have to re-use the lhs.
This PR adds PrimitiveArray::get_mut_values and removes (un-released) functions from PrimitiveArray, since the function get_mut_values is more generic.

However, when operating over values and validities independently, we do not need a mutable ref to both at the same time.

Good observation.


Remove HeatingCoil.res

Hi @rafacanton, this file is used in the current release of pydpf-core, and an error is now raised. Do you think we can revert the deletion until the next release of pydpf-core?

Hi @rafacanton, this file is used in the current release of pydpf-core, and an error is now raised. Do you think we can revert the deletion until the next release of pydpf-core?

Hi @cbellot000, where is it raising? All tests and examples have been modified accordingly in core and post


fix(sdf): Add joi types to Editor

Co-authored-by: Victor Bustamante<EMAIL_ADDRESS>This will ensure that we are showing users correct linting details

bors merge


Simplify market creation page

This simplifies the wording and choices around probability of an event happening as well as duration of the question. It still allows the advanced user to get more specific, however.

I'm using indigo-600 as the background on the toggles as it offers more contrast with the white text so is easier on the eyes. Indigo-500 looks like it's the standard for colored text, however

The academics Sharef & Leon suggested the buttons for quickly choosing a close date, just like you've implemented!
They also wanted 6 months and a year buttons. I think at the least you should add a button for a year!
See: https://www.notion.so/manifoldmarkets/Prediction-markets-on-research-academic-papers-94ba4cfe441247d0873d365d6ed8faf2#f69da9b429304bd89dfb3872f65c13de

Thanks for the review, James! Adding a year button and/or a custom button to the probability row breaks the row into two rows on my phone and looks quite bad. I'm going to graph the distribution of market durations up until now and see if the choices I added make sense and/or if a year button is worth adding. I like removing the custom button for probabilities as I think clustering the liquidity around those non-poles seems like it will result in a better UX for bettors.


better for psycopg2 cursor

psycopg2's execute returns None. I think returning cursor is better for both sqlite3 and psycopg2 ;-)
http://initd.org/psycopg/docs/cursor.html#cursor.execute

Hi,
Thank you for your suggestion, I decided to change the database access a bit, such I didn't need the builder/data_helper.py file after all.


Is this still being maintained?

Hey, love the project, it's very much needed in the slatejs space. I was just wondering if this is still being actively maintained? I've recently updated to jest 28 with jest-environment-jsdom and it completely broke the editor tests. Are there any plans for supporting newer versions of jest?

@mwood23 bump bump -- curious about this too. Anyone else too feel too to ring in, but if not using this, how are people testing against slate/slate-react these days? testing lib userEvents against the <Editable> component?


Conditionally utilize startTransition if it's present

This allows the LexicalTypeaheadMenuPlugin to be utilized in React 17

Not sure what's going on with the playground build in Vercel...

Not sure what's going on with the playground build in Vercel...

Oh, it's a TS issue (implicit any on callback). Vercel just caught it in the build before the integrity CI check finished.
https://github.com/facebook/lexical/runs/7454506945?check_suite_focus=true

Wow this is cool:


replace pypy3.8 with pypy3.10

close/reopen to restart CI

close/reopen: hopefully have correctly convinced stdout to use utf-8 encoding

close/reopen

Close/reopen


NIFI-10630 Fixed Possible Json Ordering Permutations Problem in Tests

Summary
NIFI-10630
Following the problem of flakiness that occurred in test file
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors org.apache.nifi.processors.standard.TestWaitNotifyProtocol
with below three tests
testNotifyAttributes
testNotifyCounters
testNotifyFirst

The test flakiness is due to comparisons between Json Strings and outputs from
cacheEntry.getValue() which is an Object AtomicCacheEntry<String, String, Long>
However, JsonObject does not guarantee entry orders, its object is an unordered set of name/value pairs, and internal permutations may occur in the output as JSON String.
Brief changelog
Since JSON library com.fasterxml.jackson.databind is used in the current project, I import the ObjectMapperand use mapper.readTree(JSON String) when comparing them, thus the equals() method ignores the order and treats them as equal.
Verifying this change
This test avoids nested or different orders of JSON strings that cause flaky errors.
Since I didn't touch any Source code, it should be no impact on the project.
And it passed the local test that the guidelines mentioned.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[ ] JDK 8
[X] JDK 11
[ ] JDK 17

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Hi,
I just saw one of the checks failed due to the time limit. Could you please rerun that or help me check that?
I did not touch the main code and only changes a few lines in the test file with the library used in the project.


Support to make it work with an options array

Hi,
Thanks for this awesome plugin.
Currently it expects an url for search. in My use-case, I have the options in an array in my vue application itself. Can there be support added for accepting an array in input and than suggest from that array.
Thanks.

my request need set headers ，the post／get request  have  a headers options set？

+1 for @jjjachyty - how would I set headers?

Hi All!
Thanks for giving me an issue~
The options props is for you @mimani and....
the onShouldGetData props is made for your need @jjjachyty & @kevcodez
Thanks! :grin: :+1:


[new] Validate IO nodes have resources matching parent signatures

Add a validation check that dataflow graph's input and output nodes have the same resource requirements as the incoming/outgoing wires of the parent.

I'm open to refactoring suggestions, because the code seems quite ugly


Query the EventStore programmatically

In the following code:
var sfhttpClient = ServiceFabricClientFactory.Create(clusterUrl, settings);

var clstrEvents = sfhttpClient.EventsStore.GetClusterEventListAsync(
    "2018-04-03T18:00:00Z",
    "2018-04-04T18:00:00Z")
    .GetAwaiter()
    .GetResult()
    .ToList();

System.Fabric.FabricClient can't access EventsStore and ServiceFabricClientFactory itself can't be accessed (where does it come from?)

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

ID: fabf8df7-756f-2d7a-1d7f-068091d5f4f8
Version Independent ID: 9776fd49-7f2f-8f0c-69be-638fa0d3dd6e
Content: Query for cluster events using the EventStore APIs - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-diagnostics-eventstore-query.md
Service: service-fabric
GitHub Login: @srrengar
Microsoft Alias: srrengar

Thanks for the question. We are currently investigating and will update you shortly.

@mcurko Apologies for delay in response and all the inconvenience caused because of the issue.
Can you please provide detail around your environment you are running on? And the SF version?
Thanks

@mcurko Apologies for delay in response and all the inconvenience caused because of the issue.
Can you please provide detail around your environment you are running on? And the SF version?
Thanks

I'm using the latest NuGet packages. The code doesn't compile, so it's not a matter of the environment, since I haven't gotten to the point where it might run.

I'm using the latest NuGet packages. The code doesn't compile, so it's not a matter of the environment, since I haven't gotten to the point where it might run.

@mcurko The reason I asked was because EventStore is not supported for Linux or Standalone environments and I hope the customer is not using one of those environments.
If you are not, then can you please share the compilation error that you currently see so that we can help investigate the issue.
Thanks

@mcurko The reason I asked was because EventStore is not supported for Linux or Standalone environments and I hope the customer is not using one of those environments.
If you are not, then can you please share the compilation error that you currently see so that we can help investigate the issue.
Thanks

I don't have the code anymore, I reported the problem a month ago...

I don't have the code anymore, I reported the problem a month ago...

@mcurko I do understand your concern but since it was holiday season most of our Product Group folks were oof as well.
If you can arrange code somehow I will request you to share same with me if that is not possible will it be ok to close issue for time being so if you face issue again we can help you out in timely manner.
Thank you for your patience over the matter.
Thanks

@mcurko I do understand your concern but since it was holiday season most of our Product Group folks were oof as well.
If you can arrange code somehow I will request you to share same with me if that is not possible will it be ok to close issue for time being so if you face issue again we can help you out in timely manner.
Thank you for your patience over the matter.
Thanks

@mcurko I do understand your concern but since it was holiday season most of our Product Group folks were oof as well.
If you can arrange code somehow I will request you to share same with me if that is not possible will it be ok to close issue for time being so if you face issue again we can help you out in timely manner.
Thank you for your patience over the matter.
Thanks

@mcurko I do understand your concern but since it was holiday season most of our Product Group folks were oof as well.
If you can arrange code somehow I will request you to share same with me if that is not possible will it be ok to close issue for time being so if you face issue again we can help you out in timely manner.
Thank you for your patience over the matter.
Thanks

@mcurko We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.


Added support for Linux .desktop files

http://standards.freedesktop.org/desktop-entry-spec/latest/

Rebased and added support for Emacs desktop files as suggested.

Rebased and added support for Emacs desktop files as suggested.

Travis noped. I don't have an example. Will keep this to FreeDesktop standard adhering files.

Travis noped. I don't have an example. Will keep this to FreeDesktop standard adhering files.

Thanks for the effort to include Emacs in your PR.  The problem with multiple file extension segments seems fixed now.  Could you please try again?
(Speaking only as an individual; I'm not part of GitHub staff.)

I need an example file. Can you provide one?

Ok, hang on.

Or rather, I made one myself:
http://lars.nocrew.org/tmp/.emacs.desktop

Finally got it to work.

I'm surprised that

I'm surprised that a grammar different fro source.ini is needed. Are the specifications really different?

That is what I tested at first, but the ; is a way to comment out and not a separation char for INI: example

The specifications sharing some syntactic elements may be just coincidental. INI vs .desktop is very much Windows vs Linux.

I see. Thanks for the explanation :+1:

Removed the .emacs.desktop file again. After all it seems to be unused here on GitHub.

And added it again to please the :church: of Emacs.

@Mailaender I was able to find more than 180,000 of them so I think it's a good thing you added .emacs.desktop ;)

Yep, searched the wrong way without the filetype: prefix.

:+1:


feature request : weight of packed items only

Copy-paste from @nutpantz (issue #13 )

Looks great to start. Two thoughts only
it would be nice to see total weight of packed items not total weight of all list items
(Some things in the list don't always get packed)
Total packed item weight in the trips screen.

Added packing weight in detail of trip.

Available in release 0.8.1, consequently closing issue.


Override get_user() in SocialAuthBackend so it supports returning users from a custom user model

Related to this issue https://github.com/omab/django-social-auth/issues/180
This patch fixes the problem where django session/auth middleware would load django.contrib.auth.User models even when a custom user model was specified in SOCIAL_AUTH_USER_MODEL.

Thanks


Implement Function Mock Scoping for Test Framework

Description:
The current implementation of function mocking simply replaces every call to the function with its respective mock function. The scope of this is always the entire module.

An improvement to this implementation would be to have a scoping mechanism which would allow us to restrict the mocking of functions to particular test cases only. Thus, each test case can have its own unique implementation of the mock function which will be useful when testing multiple scenarios

Possible implementation
Scope can be specified by adding a parameter to the annotation called 'scope'. The same mock function can be used by multiple Test files, hence the scope is a string array of possible test cases.
If the scope is not specified, then it is considered as a default case. If the default mock is not specified, then the original function is called.
@test:Mock {
    functionName : "intAdd()",
    scope : ["Test1"]
}
function mockIntAdd_Test1() returns (int) {
    // implementation for Test1 only.
}

Generating a function during compilation allows us to replace the intAdd() calls with the generated function. This generated function would analyze the stack trace to find out which Test file is calling the intAdd() function and call the relevant mock

Implementation spec has since changed hence closing the issue


Create Server / Peripheral package

t.b.d.

under construction

Did anything ever come of this? I was hoping to make use of this functionality but might need another solution if this library doesn't support server mode.

Likewise looking for this functionality but it doesn't look like the ble-server branch has been worked on for two years :(
Any alternative libraries out there?


How to add leadpages to Camaleon

Hi @owen2345,
Can you please let me know how to add Leadpages or other email opt-in landing page builders...I am trying to use contact form, but I feel Leadpages will increase opt-ins greatly.
I would like to offer some give aways to users if they subscribe to my blog, pls let me know how we can do that.

Hi @mazharoddin
I don't understand, could you please give me more details or an example?

Sure, Leadpages are mainly useful for providing some give aways to users like free PDFs or XLs etc.
Basically if they click the 'give away link' they will be prompted with subscribe option, if they subscribe they will allow to download that free PDF, in some cases if they subscribe they will be sent a confirmation mail along with the pdf download link.
What I observed is it really helps in growing email subscribers. pls find below for few images.

If any user clicks on above link will be prompted with subscribe option.

Lead pages allows us to configure these subscribe options various way.

ohhhh I understand, it is easy:

for the admin panel you can show the private file browser with:

$.fn.upload_filemanager({
        formats: $input.data("formats") ? $input.data("formats") : "",
        selected: function (file, response) {
            console.log(file.url.split('?file=')[1].replace(/%2/g, '/'));
        },
        private: true
    });

For the frontend you can create another url to download this file like:

send_file CamaleonCmsLocalUploader::private_file_path(params[:file], current_site)

Regards,

Sure @owen2345, let me try it. Thanks


Make rr.Points3D.indicator possible

so one can do these kinds of things:
rr.log("example/points", [rr.components.Points3D.indicator,
                          rr.components.Position3DBatch(positions)

Same story in Rust.
TODO:

[ ] Python
[ ] Rust

The Rust part of this actually blocks the Rust part of https://github.com/rerun-io/rerun/issues/3383, otherwise things get extremely messy because Archetype doesn't have a num_instances() anymore: it's moved to AsComponents.


Correcting wrong label and its selector

Label used https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/#defining-controller-selectors-and-podtemplate-labels for this example contains slash. But slashes are not allowed for labels so this recommandation is giving error. So correcting that label and its selector.

I'm not sure that's the right fix @rajeshdeshpande02

@rajeshdeshpande02 would you be willing to update this PR based on https://github.com/kubernetes/website/issues/19494#issuecomment-596688442 ?
That corrected section belongs in several places but not the page it's currently part of.
If you want to, you can define a new shortcode with the repeated text and use that (and I can provide some help if you'd like it).

@rajeshdeshpande02 :wave: Please feel free to /reopen this issue when you’re ready to continue.
/close


Matcher for optgroup

Hi! I am digging up issue https://github.com/select2/select2/issues/2007 about matcher for optgroup.
As you can see, the recent updates brought differences in the matcher function declaration.
Has anyone written a custom version of the matcher to match optgroup as well?
Could an alternative matcher be included to the lib? We could add a new option such as the following:
$("#selector").select2({
    [matcher_type: ('opt'|'optgroup')]
});

I'd be happy to hear from you! Cheers,
Quentin

Normally I would push this to the mailing list or Stack Overflow, but I'm pretty sure the change isn't that large.
function matcher (params, data) {
  // Always return the object if there is nothing to compare
  if ($.trim(params.term) === '') {
    return data;
  }

  var original = data.text.toUpperCase();
  var term = params.term.toUpperCase();

  // Check if the text contains the term
  if (original.indexOf(term) > -1) {
    return data;
  }

  // Do a recursive check for options with children
  if (data.children && data.children.length > 0) {
    // Clone the data object if there are children
    // This is required as we modify the object to remove any non-matches
    var match = $.extend(true, {}, data);

    // Check each child of the option
    for (var c = data.children.length - 1; c >= 0; c--) {
      var child = data.children[c];

      var matches = matcher(params, child);

      // If there wasn't a match, remove the object in the array
      if (matches == null) {
        match.children.splice(c, 1);
      }
    }

    // If any children matched, return the new object
    if (match.children.length > 0) {
      return match;
    }

    // If there were no matching children, check just the plain object
    return matcher(params, match);
  }

  // If it doesn't contain the term, don't return anything
  return null;
}

The only change that was needed was moving the term matching to the top, so it wouldn't alter the children before it returned it back.
You can see this live at this jsbin: http://jsbin.com/piyojarara/1/edit?html,js,output

Thank you Kevin this helps a lot!


Add note for users interested in adding data

Also add email to footer.

Added email to footer in #401 . Still need to add note for adding data.


[FR] Support for RFC8375 (home.arpa.)

This is more a question than a feature request. Is it correct that Unbound does not implement anything related to RFC8375? For instance, RFC8375 prescribes that queries for ...home.arpa. must not be forwarded recursively. Does Unbound do that?
If my home network uses home.arpa, should I just treat it as any other domain, as far as Unbound is concerned?

RFC8375 was recently implemented, in commit https://github.com/NLnetLabs/unbound/commit/89510f4a0cb60e0f7d1388e497f1b5feb0464d04.

Grave digging a bit, but just in case it helps someone. After updating Debian 11 -> 12, my unbound package updated 1.13.1 -> 1.17.1, which caused the home.arpa forward zone to break.
forward-zone:
    name: "home.arpa."
    forward-addr: internal.dns.server.ipv4

server:
    domain-insecure: "home.arpa"
    private-domain: "home.arpa"

Adding: local-zone: "home.arpa." nodefault under private-domain fixed my issues.


Why do I receive emails with other adresses in the To field

I get some emails like this:

Why? Shouldn't these be rejected by the mail server? And how can I make the mail server reject them?

The addresses in the To/Cc/(Bcc) headers of a message (in Internet Message Format) can be unrelated to the addresses a message is delivered to (over SMTP, with the MAIL FROM and RCPT TO commands).
If you would send an email to someone, and bcc to another address, than that other address also wouldn't see their address in the message headers. Same for forwarding and mailing lists. So marking a message as junk because your address isn't an addressee in the header isn't necessarily a good idea.
For messages without your address in an addressee header, that could be useful signal for junk filtering. But mox doesn't currently use it as such.
You could look at the x-mox-reason header and see if there's hint why the message isn't rejected.

Oh, I thought a Bcc was like a forward. That makes sense now.
Maybe I can add this as a spam signal. Can you give some pointers?

Heh, as I was looking up and started writing whereabouts a change may be useful, but it looks like it actually is already implemented: https://github.com/mjl-/mox/blob/2bb4f78/smtpserver/analyze.go#L410
Now the question is: is this working properly, and has it been applied to this message? I.e. has the junk filter threshold been lowered? In that case, the contents apparently were very hammy since the message passed the check. Could you see in the logging if there's anything about the analysis of this message? And does the x-mox-reason header on the message say "no-bad-signals"?

If the To/Cc case was hit, it would be logged under Info level. Unless that would result in too much logging, I think would be a good log level for servers. See https://github.com/mjl-/mox/blob/v0.0.10/smtpserver/analyze.go#L416.
I'm also sometimes getting junk messages, and I can't easily see why there are getting through (and I don't always want to dive into server logs). I'm now planning to add some more details to the X-Mox-Reason header. It's much easier to take a quick look. Details like the bayesian filter threshold we arrived at. How many words were used in checking, perhaps scores as well. Will hopefully show a pattern.

I would appreciate that. I also receive these regularly, about once a week, so I will see that as well.


Add 'non-npm package' marker on Type Definitions line.

This allows people to mark their packages as not on npm. This will allow tools like dts-critic to treat these packages differently.
If we decide to ship this change, I'll update Definitely Typed after it merges.
Specifically, the first line can now have two possible headers:
// Type definitions for x

or
// Type definitions for non-npm package x

What's the goal here? Eventually being able to verify that each package is named correctly?

A common thing when reviewing "New Definition" PRs is figuring out if the author named the folder correctly

@RyanCavanaugh is right -- "non-npm package" would give people a pass on making their package match the NPM page.
It could instead give them an error if their name conflicts with an existing NPM package, but several of our existing packages would fail here. I'll have to decide how to approach that after further testing.


Changing HTML entitiy (') to character (')

Localization team has reported source content issue that causes localized version to have broken format compared to en-us version and display wrong content.
The request:
Changing HTML entitiy (') to character (') in titles (metadata and body)

@JiayueHu : Thanks for your contribution! The author, @MightyPen, has been notified to review your proposed change.

Editorial fix confirmed.


Add/remove zh-cn reviewers

The PR proposes some changes to the zh-cn localization team.
Based on contributions during the past few months, we'd like to invite
'Sea-n' to our approvers team and 'Winsonsea' to our reviewers team.
At the same time, we will suspend the membership of some existing
members who are no longer active in the community by commenting out
their IDs so that PRs are no longer assigned to them. We are not
removing those IDs in hope they will join us when their "conditions"
become "Ready".

😄 Thanks a lot, my master, you lead a very good way that is worthy of diving into with so many active members who have different viewpoint to promote me grow and learn new knowledges everyday.
💝 🎁 🤝

Wow, it's my pleasure for being nominated!
We will definitely do my best to reviewing and approving zh localization PRs. 😊

😄 Thanks a lot, my master, you lead a very good way that is worthy of diving into with so many active members who have different viewpoints to enable me grow up and learn new knowledges everyday. 💝 🎁 🤝

I'm not a master, dear friend. I'm just another nerd online passionate on open technologies. I learned a lot from others as well, including you.

/lgtm
/approve


Config to exclude files

It would be nice if we could exclude somes files and folders to the generation.
For example:

  files:
    'scripts/app.js':
      languages:
        '\.js$': languages.JavaScriptLanguage
        '\.coffee$': languages.CoffeeScriptLanguage
        '\.eco$': languages.EcoLanguage
      order:
        before: [
          'vendor/scripts/file.js'
          'vendor/scripts/file2.js'
          'vendor/scripts/file3.js'
        ]
        after: [
          'vendor/scripts/file4.js'
        ]
      not: [
        'vendor/scripts/file5.js'
        'vendor/folder/'
      ]

    'styles/app.css':
      languages:
        '\.css$': languages.CSSLanguage
        '\.styl$': languages.StylusLanguage
      order:
        before: ['vendor/styles/normalize.css']
      not: ['vendor/styles/deprecated.css']

Seems legit. Also could you provide a more real-world use-case, please?

Well, I'm working on a Android/IOS/Web application and I use this architecture:

.
└── brunch # HTML5 Application
    │
    ├── .android  # Android specific Files
    │   └── vendor
    │       ├── scripts
    │       └── styles
    │
    ├── .ios # iOS specific Files
    │   └── vendor
    │       ├── scripts
    │       └── styles
    │
    ├── .web # Web specific Files
    │   └── vendor
    │       ├── scripts
    │       └── styles
    │
    ├── android # Android Application
    │
    ├── ios # iOS Application
    │
    ├── build # Web Application
    │
    ├── app
    │   ├── assets # will be copied to build automatically (see brunch AssetsPlugin)
    │   ├── controllers
    │   ├── helpers
    │   ├── models
    │   ├── routers
    │   ├── styles
    │   ├── templates
    │   └── views
    │       config.coffee
    │       initialize.coffee
    │
    └── vendor

And it would be nice to use :

.
└── brunch # HTML5 Application
    │
    ├── android # Android Application
    │
    ├── ios # iOS Application
    │
    ├── build # Web Application
    │
    ├── app
    │   ├── assets # will be copied to build automatically (see brunch AssetsPlugin)
    │   ├── controllers
    │   ├── helpers
    │   ├── models
    │   ├── routers
    │   ├── styles
    │   ├── templates
    │   └── views
    │       config_android.coffee
    │       config_ios.coffee
    │       config_web.coffee
    │       initialize.coffee
    │
    └── vendor
        ├── common
        │   ├── scripts
        │   └── styles
        ├── android
        │   ├── scripts
        │   └── styles
        ├── ios
        │   ├── scripts
        │   └── styles
        └── web
            ├── scripts
            └── styles

Right now, I use a pre-compiler for Android and IOS for moving the files from .android/.ios to the vendor folder and use brunch watch to build the android/ios version and moving the .web back and brunch watch to have the web application back.
So in complement it would be great if we have something like that:
brunch build -c "my_specific_ios_config_file" -o "ios"
Of course, it would be awesome if we could have the three versions compiled at the same time (with a new configurable outputDir property).

okay, I think something like that would be nice. tagging as "do want"

In 1.0 you can write patterns that will match files so basically this question is resolved.

I would like to re-open this. Having only an "include this" facility may lead to extremely clumsy patterns. Having a "do not include that" facility leads to smaller / cleaner configs and alleviates integrating components (e.g. less-based CSS toolkits) that have internal dependencies not following the _ convention.

https://github.com/brunch/brunch/blob/master/docs/config.md#conventions and negated globs (starting with !) are two additional options for accomplishing that.

Tried conventions.ignored with globs -- did not work (only with REs in conventions.ignored). Negated globs in path did not work out, neither. See an example that works for me in https://github.com/brunch/brunch/issues/720.


Flexbox grid columns not full width at small viewport sizes

Hi,
I noticed that using the flex grid, columns at small sizes don't fill the full width.
See: http://codepen.io/anon/pen/vKxQVx
set the grid to use flexbox and resize the window to small size. Notice how the columns don't fill the width. Shouldn't  the columns have flex-grow: 1; ?
thanks

May I ask why you didn't include your OS and browser versions as requested in the issue template?

Sorry, I forgot :(
OS: mac OS X (latest version)
browser: Chrome

This should be fixed by #20349.


RedisEmbeddingStore: Supporting different index types for metadata in RedisEmbeddingStore

Discussed in https://github.com/langchain4j/langchain4j/discussions/1612

Originally posted by mortensi August 20, 2024
Ingesting data in a RedisEmbeddingStore with metadata creates a TEXT index. This is useless for non-textual metadata (like saying you can't have numeric metadata, exact match TAG indexes, or geographical locations).
"FT.CREATE" "movies_20240820_230935_idx" "ON" "JSON" "PREFIX" "1" "embedding:" "SCHEMA" "$.text" "AS" "text" "TEXT" "WEIGHT" "1.0" "$.vector" "AS" "vector" "VECTOR" "HNSW" "8" "DIM" "1536" "DISTANCE_METRIC" "COSINE" "TYPE" "FLOAT32" "INITIAL_CAP" "5" "$.score" "AS" "score" "TEXT" "WEIGHT" "1.0" "$.date_x" "AS" "date_x" "TEXT" "WEIGHT" "1.0"

Supporting schemas in the same way as LangChain for Python does is nice to have.
index_schema = {
    "tag": [{"name": "genre"},
            {"name": "country"}],
    "text": [{"name": "names"}],
    "numeric": [{"name": "revenue"},
                {"name": "score"},
                {"name": "date_x"}]
}

Redis.from_texts(index_schema=index_schema, ...)
Metadata indexed with the right type of index enable advanced search and RAG use cases.

Sounds good to imporve it.


Add support for duct bank thermal analysis

Duct banks are underground conduits that provide pathways and protection for underground cables.  Heat dissipation in duct banks is a potential issue with electrification. A model for thermal effects on cables is needed for duct banks.

Proposal

Add an object class called duct_bank to powerflow module.
Develop a thermal model for duct banks, including stacked ducts.
Provide a link from underground cable to duct bank so cable losses can be gathered and cable aging can be computed based on thermal effects.


Align class and property descriptions with the new DCAT scope

In order to address https://github.com/SEMICeu/GeoDCAT-AP/issues/36 , revisions have been made by listing, when necessary, the different classes / resource types to which a class / property description refers.
The term "resource" was never used in the narrow sense of dcat:Resource without a proper qualification, and always complemented with the list of relevant resource types - e.g., "a resource documented in a Catalogue (as a Data Service, Dataset, or another Catalogue)".
Additional revisions include editorial fixes, and harmonisation of how classes are referred to (e.g., when the reference points to a class documented in the specification, it is capitalised).
Revised sections (open the link for a preview):

Mandatory classes
Recommended classes
Optional classes
Agent properties:

Recommended properties for agent

Catalogue properties:

Mandatory properties for catalogue
Recommended properties for catalogue
Optional properties for catalogue

Catalogue record properties:

Mandatory properties for catalogue record
Recommended properties for catalogue record
Optional properties for catalogue record

Category properties:

Mandatory properties for category

Category scheme properties:

Mandatory properties for category scheme

Data service properties:

Mandatory properties for data service
Recommended properties for data service
Optional properties for data service

Dataset properties:

Recommended properties for dataset
Optional properties for dataset

Distribution properties:

Mandatory properties for distribution
Optional properties for distribution

Kind properties:

Recommended properties for kind

Location properties:

Recommended properties for location
Optional properties for location

Period of time properties:

Recommended properties for period of time

most is fine: only a typo has been introduce meters -> metres. Should stay meters.

This was meant to use the British English form, consistently with the rest of the document (DCAT2 uses American English instead).

Hi Andrea,
ok, I did not know this was an American/British english spelling issue.
kr,
Bert
Op wo 2 dec. 2020 om 19:35 schreef Andrea Perego<EMAIL_ADDRESS>
most is fine: only a typo has been introduce meters -> metres. Should stay
meters.
This was meant to use the British English form, consistently with the rest
of the document (DCAT2 uses American English instead).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/SEMICeu/GeoDCAT-AP/pull/42#issuecomment-737416138,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPIC3KK7WCRON3LXLCJ4ZTSS2CFLANCNFSM4UFNMEDQ
.

My fault, @bertvannuffelen . I should have explained it in the comments.

@andrea-perego ok to merge it.

Thanks, @bertvannuffelen .


Add a Gitter chat badge to README.md

orchest/orchest now has a Chat Room on Gitter
@yannickperrenet has just created a chat room. You can visit it here: https://gitter.im/orchest/orchest.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Added it!


[Docs] Animated Routes guide outdated

In the example code the import from react-spring should be changed to the code below.
import { Transition, animated } from 'react-spring/renderprops'
On top of that the example code is not working, but I'll have to dig deeper to see why.

The example could be broken because of #1118.

:( but an updated example can be found here https://github.com/nozzle/react-static/issues/1118#issuecomment-492195423

reach-router example using #1181 was listed here: https://github.com/nozzle/react-static/issues/1162#issuecomment-492302334

Closing this issue as a PR was just merged for this.


Where is the latest stable release for production usage?

The  GitHub PSD1 file says the module version is 0.0.1.
https://github.com/gaelcolas/datum/blob/master/datum/datum.psd1
And when I type
Find-Module -Name Datum
PowerShell Gallery answers me that the module version is 0.0.38
but also the description says it is an experimental module…
The README.md says that v1.0.0 is aimed to be released for April 2018, or earlier…
Where can I find the latest stable version for production usage?

Hi,
The version in psd1 is updated when released by the build release for every push to master (or most).
What's in master correspond to the latest version on the gallery, hence 0.0.38.
It's an experiment, and a rather successful one, that is being used in production by several companies.
The main reason for not going 1.0.0 yet is to follow semver, and allow breaking changes without major increment. The quality of the module is also lacking help, tests, and documentation.
That doesn't mean I intend to break it, but the current public interface is not optimal and I may change it. If you follow example of usage, such as what's done in the AutomatedLab DscWorkshop, you should not be affected as I try to be backward compatible.
I should update the readme, thanks. That was the plan, but life happened, and on only released smaller changes.
The version on the gallery is the latest, and as with all free & open source projects, production quality is not guaranteed and subjective to your environment.
It's in use by many, including customers I do not want to annoy too much with breaking changes.
Hope that helps, and you find this module useful.

Thanks for the clarification!


How can I avoid shuffling when writing Clickhouse？

How can I avoid shuffling when writing Clickhouse，Is it supported？

Currently the shuffle is enforced, otherwise may cause large small write requests to ClickHouse server, could you please give more details about your concerns?

Currently the shuffle is enforced, otherwise may cause lots of small write requests to ClickHouse server, could you please give more details about your concerns?

I just change the code as show below and the shuffle was avoided, but I don't know if it will bring other side effects

I guess you think the shuffle cost too much resources in your Spark job, and you prefer to deliver the sort merge efforts to ClickHouse? Anyway, I think it's valuable to make the repartition configurable, would you like to send a PR for that?

thank you for your invitation，but  I want to understand the details of the project architecture first and do some test ,thx :)

@githubgavin I'm sorry there is no project design document now.
The main idea of this connector is how to mapping the Spark DataFrame/RDD partition to ClickHouse shard partition and versa in data exchange process.
Assuming (and sorry if I'm wrong) you have basic knowledge of Spark SQL and ClickHouse Distributed table, I think it's good to start with the DataSource V2 API to learn this connector as the API is intuitive.
If you have any question while reading code, feel free to ping me :)


Add a way to make bounds larger than the actual image pixels

https://www.facebook.com/groups/framerjs/permalink/630438713749870/

Hi guys, Framer or Sketch seems to ignore transparent layers inside the group when exporting. I wanted to include the transparent bounds to have a bigger tap area - like the example below instead
of 192x128, it will only export 27x40. Is there another way to do this?

I had this in sketch-generator:

If you add a "@bounds" layer at the bottom of your layer group, it will be used for dimensions but won't get exported

We could either do something like that, or simply make the exporter export transparent layers as real layers, with opacity set to 0 in Framer. I probably have this filed as an issue already.

I think taking into account transparent layers might be a nice way to do it, but I might be overlooking some edge case.

Imho, this is a nice to have, but not a serious bug at this point.

Pretty sure this is fixed with https://github.com/bomberstudios/sketch-framer/issues/76

Fixed verified


i cant add hdd to my server

hello
when i buy ram and hdd and other parts for the server i cant connect the hdd and server together .. the slot is empty always

Thank you for the report @fisher762 - will have a look and get back to you this week

So I think you probably got as I did an error when building the server, along the lines of an issue with recomputeServerResources
This causes the server config to be corrupted in the DB - so the slot doesn't exist
I've put this fix: https://github.com/nenuadrian/Secret-Republic-Hacking-Browser-Game-V3/commit/9752eaac963e319dca190d4b6793b24ad24fd73d
If you apply same and try it then it should work now


Validation issue with 767845175 (IN)

Please read the "guidelines for contributing" (linked above) and fill in the template below.
Country/region affected (e.g., "US"): IN
Example number(s) affected ("+1<PHONE_NUMBER>"): 767845175
The phone number range(s) to which the issue applies ("+1 555 555-XXXX"):
The type of the number(s) ("fixed-line", "mobile", "short code", etc.):
The cost, if applicable ("toll-free", "premium rate", "shared cost"):
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): IMPORTANT - anything posted here is made public. Read the guidelines first!
link to demo

Thank you for taking the time to improve libphonenumber!
We can't connect to +91 767845175 We support 10 digit long numbers for the prefix 767X while the specified number is 9 digits long. Demo result: https://libphonenumber.appspot.com/phonenumberparser?number=7678451750&country=IN
We are not able to find 9 digit numbers with this prefix online. Closing this as working as intended; if you would like to reopen, please share any working numbers or official evidence you may have. See our
guidelines.


Luisb90/update ngx input autosize

Summary
Worked on updates to ngx-input:

Replaced the default chrome accessibility number spinner with a custom styled one that matches wireframes for numeric ngx-inputs.
Added a minWidth property to ngx-input
Reworked the autosize code, in the previous implementation while the input would grow correctly, it wouldnt size down to smaller inputs (such as small numbers). I've reworked it following the JS method mentioned here: https://css-tricks.com/auto-growing-inputs-textareas/.

Edit
There were a lot of edge cases that werent really covered by the above solution, so i decided to go with a third party library, ngx-autosize-input
Checklist

[x] *Added unit tests
[x] *Added a code reviewer
[x] Added changes to /projects/swimlane/ngx-ui/CHANGELOG.md under HEAD (Unreleased)
[x] Updated the demo page
[x] Included screenshots of visual changes

*required
Old Spinner:

New Spinner:

Autosize:

Are you planning on having design review this PR? I feel like the alignment on the spinners is a bit off.

Are you planning on having design review this PR? I feel like the alignment on the spinners is a bit off.

yup, Mike is gonna look at it in a bit

Given a min="0" property, I can use the tickers to go below 0. The field becomes invalid, but current (and html5) functionality won't allow the value from the tickers (spinner).
Given a max="100" property, I can use the tickers to go above 100.
When a placeholder is present, the descenders get cut off (lowercase g on the demo page)
Tickers are a bit small—should be 10px equivalent. The top ticker has bottom padding, which makes the targets different sizes. If the font size is increased and padding removed, .numeric-spinner aligns middle vertically as it should.

The ticker's right positioning for the filled variant should be consistent with the component's (input's) left padding. Can we make it a 0 right position for the legacy style?

@mcwenger addressed the comments, you're good to pull and check again

@luisb90 @mcwenger Can I suggets adding a little click feedback on the number spinner.  A little on hover color change and some "click" effect?

@Hypercubed Yes, I love the idea—let's chat on it so I can get a design scope.

@Hypercubed Yes, I love the idea—let's chat on it so I can get a design scope.

@mcwenger @Hypercubed pushed commit to add scale on hover to the numeric spinner


chore: fix typo

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@all-contributors add @ansgarm for maintenance


chore: remove unconfigured panels in dashboards

Motivation
Closes https://github.com/ChainSafe/lodestar/issues/5934
Description
Removed unconfigured panels in dashboards

:tada: This PR is included in v1.12.0 :tada:


[release-v1.1] Move up the check if topic is externally managed

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>
move up the check if the topic is external, so we are not bothering w/ Sarama config call (for a non admin user)

/assign @pierDipi
Next:  upstream polishing the actual PR + adding test

/cherry-pick release-v1.2


Q updates

[ ] give Q ability to registerCandidate
[ ] in experience, not using Q for dialog pertaining to MyLife, but standard actor

seems intentional at first glance, as castMember shows up as below in comments

[ ] finalize Q-initial greeting &/or test via url param dyn
[ ] icon instead of help ?

{
  bot: {
    allowedBeings: [ 'core' ],
    allowMultiple: false,
    being: 'bot',
    bot_id: 'asst_dQcj53sHH4c74uqI40Tz2ONB',
    greeting: 'My role in the MyLife play is to be the best darn actor anyone can imagine!',
    id: 'dfe0a7d7-11de-4f5a-ac83-a2fc56f28b22',
    mbr_id: 'mylife|2f5e98b7-4065-4378-8e34-1a9a41c42ab9',
    name: 'bot-actor_mylife|2f5e98b7-4065-4378-8e34-1a9a41c42ab9',
    object_id: '2617f1c5-aa17-48f3-bf7c-294e748b0c68',
    provider: 'openai',
    purpose: 'I am the AI-Actor for the MyLife platform.',
    type: 'actor',
    _rid: 'cFwtAPkoS8qSBQAAAAAAAA==',
    _self: 'dbs/cFwtAA==/colls/cFwtAPkoS8o=/docs/cFwtAPkoS8qSBQAAAAAAAA==/',
    _etag: '"2d002f5a-0000-0100-0000-65e0be000000"',
    _attachments: 'attachments/',
    _ts:<PHONE_NUMBER>
  },
  bot_id: 'dfe0a7d7-11de-4f5a-ac83-a2fc56f28b22',
  icon: 'Q-00',
  id: '88043968-d7ef-4a57-a923-335bc9f92793',
  mbr_id: '113a28c8-b7a0-4ecc-a16c-2f53876bfde6',
  role: 'Q, AI Avatar for MyLife',
  type: 'Q',
  url: 'mylife.png'
}

registerCandidate
following files require update

[ ] mylife-llm-services.mjs: create registerCandidate()
[ ] mylife-agent-factory.mjs:


Redefine neighborhood depth and calibrate low water mark

Issue #1240 stipulated the problem of the asymmetric neighborhoods. This can be partly remedied by applying the following changes:

The low water mark for non-neighborhood bins should be greater or equal to the redundancy parameter (aka neighborhood size).
Set the depth, in such a way to not allow unsaturated bins outside the depth

Old situation example with neighborhood size = 4
8 | 1
7 | 0
6 | 2
5 | 0
--- depth
4 | 1
3 | 4
2 | 4
1 | 4
In this case, there might be an asymmetry, as the peer in bin 4 might believe the peers in my neighborhood belong to his neighborhood. Because we have the low water mark right now at 1, we don't know if there is indeed 1 peer, or if there is symmetry. This confusion is fixed by point 1. If there is asymmetry, then point 2 fixes that we set the depth in such a way to include bin 4.

Because we have the low water mark right now at 1

There's a mixup of wrong terms used here.
Low watermark is set at 2 not 1, and it defines the size of peers to determine the depth. This is clearly articulated in the code:
	nnLowWatermark         = 2 // the number of peers in consecutive deepest bins that constitute as nearest neighbours

I think that as of such the depth calculation should be changed in the following manner - right now it does a sweep from deepest to shallowest to detect the depth candidate, then does a sweep from shallow to deep to detect empty bins and selects whatever is shallower. I think that the second sweep should just be changed to detect whether there are unsaturated bins instead of empty bins, since empty bins qualify as unsaturated bins.


VS Code: Release v1.40.2

Cherry pick https://github.com/sourcegraph/cody/pull/6058 into v1.40.2 patch release
Test plan
N/A

Changelog

oh right thank you!


Active Check box Alignment

Path:  Setup > All Module
Issue : Active Check box alignment is not correct while in edit mode.

Checkbox alignment in record is right in the middle. The only issue here is the filter check box which has a hidden 'reset' text right of it which will be shown upon checking on or off the button.

As discussed with Jilani earlier, it 's fine the have like this.


Implement Viewer Navigation

I used to read manga by tachiyomi app, they implemented several viewer navigation types beside up down volume buttons, I think it is good if you support one of these kinds:
RightAndLeftNavigation
/**

Visualization of default state without any inversion
+---+---+---+
| N | M | P |   P: Move Right
+---+---+---+
| N | M | P |   M: Menu
+---+---+---+
| N | M | P |   N: Move Left
+---+---+---+
*/

KindlishNavigation
/**

Visualization of default state without any inversion
+---+---+---+
| M | M | M |   P: Previous
+---+---+---+
| P | N | N |   M: Menu
+---+---+---+
| P | N | N |   N: Next
+---+---+---+
*/

EdgeNavigation
/**

Visualization of default state without any inversion
+---+---+---+
| N | N | N |   P: Previous
+---+---+---+
| N | M | N |   M: Menu
+---+---+---+
| N | P | N |   N: Next
+---+---+---+
*/

LNavigation
/**

Visualization of default state without any inversion
+---+---+---+
| P | P | P |   P: Previous
+---+---+---+
| P | M | N |   M: Menu
+---+---+---+
| N | N | N |   N: Next
+---+---+---+
*/

Ok, I got. I think one version in the future, I will improve the view page. At that time this feature will be added.


Fixing tests with time.Now

Description
There were a couple things breaking server_test:

A test was using time.Now, which meant that the data it was creating slowly was leaving the window where other test data (performance period data, to be specific) existed to support it. Jan 1 was the cut off, and then the test started failing. I changed the test to use the Test Data Gen constants.
make server_test was failing because there was an order of operations problem in the make target. The test DB was getting created, then destroyed. It should be destroyed, then created.

Fixes the current issue, but when TestYear changes to 2019 it may break again until we fix the rateengine testdata. Will there be a new story to cover this?

Good call @jacquelineIO. Made a story for  the BatTeam here: https://www.pivotaltracker.com/story/show/162932482