text:
[BUG]  chart.marker / chart.marker_list limited to the same type

Expected Behavior
Support for different markers e.g. shape, color etc. in the same list.
Current Behaviour
It appears chart.marker and chart.marker_list are limited to the same shape, color, text etc., if multiple different types are given in a list it will only draw one of the types and omit the others.
Reproducible Example
[{'time': Timestamp('2023-01-03 14:30:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-03 23:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-03 23:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-04 12:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-04 13:50:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-05 09:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-05 13:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-05 20:50:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-06 09:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-10 00:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-10 14:50:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-10 20:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-12 10:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-12 13:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-12 14:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-18 22:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-19 15:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-19 20:50:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-20 14:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-24 09:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-24 12:50:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-24 15:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-24 20:30:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-25 13:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-30 09:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-30 11:30:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-30 14:30:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-31 14:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-01 13:50:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-02 19:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-02 23:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-03 13:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-06 10:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-06 15:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-06 20:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-07 17:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-07 18:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-08 13:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-08 14:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-09 22:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-10 14:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-10 21:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-13 18:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-13 19:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-14 13:30:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-16 17:10:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-17 11:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-17 11:30:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-17 12:20:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-17 12:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-17 16:00:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-02-17 17:40:00'), 'position': 'above', 'color': 'red', 'shape': 'arrow_down', 'text': 'Bearish'}, {'time': Timestamp('2023-01-03 13:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 09:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 13:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 14:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 18:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 19:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 20:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-04 22:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-05 10:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-10 09:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-10 14:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-10 20:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-11 11:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-11 20:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-12 12:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-12 13:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-13 00:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-17 10:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-18 09:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-19 21:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-20 14:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-20 14:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-20 18:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-23 14:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-23 20:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-24 11:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-24 14:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-24 15:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-24 18:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-24 19:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-24 20:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-25 15:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-25 21:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-25 21:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-26 12:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-26 17:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-26 23:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-27 10:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-27 22:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-28 00:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-30 10:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-30 12:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-31 14:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-31 19:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-01-31 22:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-01 09:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-02 13:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-03 09:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-03 14:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-03 22:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-06 12:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-06 15:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-06 17:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-06 18:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-06 19:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-06 23:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-07 17:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-07 19:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 09:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 11:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 14:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 14:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 16:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 17:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 20:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-08 23:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-09 14:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-09 14:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-09 19:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-13 15:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-13 20:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-14 14:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-15 10:40:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-15 11:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-15 16:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-15 20:30:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-16 11:50:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-16 17:20:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-17 14:10:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-17 17:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}, {'time': Timestamp('2023-02-17 18:00:00'), 'position': 'above', 'color': 'green', 'shape': 'arrow_up', 'text': 'Bullish'}]

Environment
- OS: MacOs
- Library:

Hey @SibbiSibbi,
Unable to reproduce as no MRE was given; the below example works however:
from lightweight_charts import Chart
import pandas as pd

if __name__ == '__main__':
    chart = Chart(debug=True)
    df = pd.read_csv("examples/1_setting_data/ohlcv.csv")

    markers = [ {"time": "2023-01-20", "position": "below", "shape": "circle", "color": "#2196F3", "text": "1"},
            {"time": "2023-01-25", "position": "below", "shape": "arrowUp", "color": "red", "text": "2"},
            {"time": "2023-01-30", "position": "above", "shape": "arrowDown", "color": "green", "text": "3"}
            ]

    chart.set(df)
    chart.marker_list(markers)
    chart.show(block=True)

Louis

Me to have same issue, it plots either buy or sell signal but not both for following marker.
[{'time': '2020-01-27', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2020-02-24', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2020-07-13', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2020-10-15', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2020-12-21', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2021-01-29', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2021-04-29', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2021-07-19', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2021-09-07', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2021-11-26', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2022-01-21', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2022-04-22', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2022-06-08', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2022-08-23', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2022-09-20', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2023-02-01', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2023-05-17', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2023-07-06', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2023-08-03', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2023-10-03', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2023-12-07', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2024-01-31', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2024-03-07', 'position': 'above', 'color': 'red', 'shape': 'arrowDown', 'text': 'Sell'}, {'time': '2020-01-17', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2020-02-05', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2020-05-29', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2020-08-17', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2020-11-09', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2020-12-29', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2021-03-25', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2021-06-04', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2021-08-13', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2021-10-20', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2021-12-16', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2022-03-17', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2022-05-23', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2022-07-19', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2022-09-12', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2022-10-17', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2023-03-27', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2023-06-15', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2023-07-18', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2023-09-14', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2023-11-21', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2023-12-13', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}, {'time': '2024-02-26', 'position': 'below', 'shape': 'arrowUp', 'color': 'green', 'text': 'Buy'}]

On zoom out, I cam see that both buy and sell signals are marked correctly.

But When zoom in, I can see only Buy signals. Sell signal got disappeared.

After sorting the marker list in chronological order based on time, issue seems to be resolved.

thanks @intronix , I faced with the same issue and tryied to figure out where the problem was for a while. @louisnw01 could you please add this to library as a function (to sort markers list)? If you need dataset to check the behavior I could provide it.

authors: SibbiSibbi intronix louisnw01 yaroshoris


text:
Document ranking of results

Document current ranking factors
Document how to influence ranking
Requires #111 to be merged to be correct

Awesome work! Thanks 🥳

source: gharchive/pull-request

authors: Toflar daun

repo: loupe-php/loupe

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 smartsearch is down

In 6bbf4bd, smartsearch (https://smartsearch.kosha.or.kr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: smartsearch is back up in d0f1888.

source: gharchive/issue

repo: loveibora/test


text:
Add missing casts to enums (most likely in DV code only)

@danielmlynek discovered this in https://github.com/lowRISC/ibex/pull/566:
All line where illegal assignment are done is now marked with warning ie:
WARNING VCP2694 "Assignment to enum variable from expression of different type." "/home/danielm/gitlab/ibex/dv/uvm/tests/core_ibex_test_lib.sv" 781  1
This argument will be no longer needed when explicit cast will be used on such illegal assignment ie in file :
/home/danielm/gitlab/ibex/dv/uvm/tests/core_ibex_test_lib.sv, line 201
 operating_mode = core_init_mstatus[12:11];
need to be changed to:
 operating_mode = priv_lvl_e'(core_init_mstatus[12:11]);
@danielmlynek do you know of more cases where such a cast is missing?
@msfschaffner I suppose currently the DV code isn't running through Lint, which should have caught that. Can you think of an easy way to lint that code as well? (Either here, or in OpenTitan.)

Thanks for cleaning this up (and sorry for being late to the party here - I was out the last two weeks). Indeed, we only run RTL through AscentLint at the moment.

@danielmlynek - are you still seeing these issues?

No.
Now all looks ok reagrding this issue.

Great, thanks for confirming @danielmlynek. Closing this then.

authors: danielmlynek imphil msfschaffner udinator

repo: lowRISC/ibex

license_source: bigquery


text:
Fix qrun compile warning

Relate to #622

Hi @rswarbrick ,
Is there anything else that you want to track that needs the timestamps too?

I usually run makefile with default output directory. I just attach the time for default output directory to avoid confuse. It makes sure I can rebuild things properly for different default output directory.
Edit: Aargh, apparently I don't know how to use GitHub PRs yet. This is supposed to be attached to the 2nd commit ("Add time for output report")

I think you can use cherry pick to get my commit?

Right, I've just gone through this PR again. Thanks for spotting the missing void keyword in ibex_mem_intf_slave_seq_lib.sv: we should definitely fix that.
Also, I completely agree with the change to sim.py. Actually, I was going to re-jig that script this morning (making it PEP8 compliant and doing general tidy-ups). So I'll grab that commit and start a "tidy up sim.py" PR based on that. Once it's done, I'll link to the PR here.
The other changes, I'm a little less convinced about: I don't quite understand the XLEN change you're suggesting and I think I disagree with the Makefile change.
If you think the Makefile change is good, could you rebase it onto master and split it into a separate PR? It's not related to Questa compilation warnings, so I think it makes sense to consider separately.

@rswarbrick , I remove 2 commits. Thanks

Oh, sorry, I forgot to link to the sim.py tidyup PR #648. The first patch there is cherry-picked from this PR's original set.

@rswarbrick . It looks good to me.

authors: danghai rswarbrick


text:
[spi_device] Optimize CS pin on at most 1-2 pinmux paths

Description
The current timing constraints for SPI TPM CS try to optimize timing against all muxable IO configurations. This causes timing convergence issues, and we won't be able to support this in the silicon PROD iteration.
Silicon integrations should be constrained to using 1 or 2 pin mapping locations for the TPM CS signal.
@brendose is it ok to define a constraint for this on the integration pinouts? If so, can you provide feedback on which pins to use? It would be ideal if this also falls in the outer ring of the package in case we have to support a single package for multiple use cases.
CC: @msfschaffner, @a-will

We'll also have to update the top-level documentation to capture this.

Let's allocate IOA2 for TPM CS.
@brendose is confirming this with @jesultra.

We are currently using IOA7 for SPI_CSB, can we use that instead of IOA2

We are currently using IOA7 for SPI_CSB, can we use that instead of IOA2

Yes, we can use IOA7 instead. If there are no objections we can close this issue once the SDC file constraints are updated to use this pin.
Thanks everyone!

As Jett said, IOA7 is the pin that ChromeOS planned to use for SPI TPM CS, and if the hardware can support only one pin, that should be it.  If the hardware could support limited mux'ing between two pins, then we would want to be able to select either IOA7 or IOA2. The latter would help in a hypothetical future scenario, in which the OT chip would simultaneously support I2C (on IOA7/8) and SPI TPM.

authors: jesultra jettr moidx

repo: lowRISC/opentitan


text:
[docs] Preview builds broken with "Error: too many open files"

I'm currently unable to build documentation on my machine, it errors out with
./util/build_docs.py --preview

...

Built in 512 ms
Watching for changes in /home/philipp/src/opentitan/{.github,build,ci,doc,hw,resources,site,sw,test,test2,util}
Error: too many open files
Error building site

This is most likely due to hugo picking up too many temporary build files in my working directory. We do set ignores in config.toml, however, they look quite fishy: the items should be regex matches, but we do use glob-style matches at times. It's also not quite clear what the base directory for those matches is, and if the file watcher (which seems to prevent the preview from working) is using those. Hugo documentation is not overly useful, and there a quick googling did make me find a couple of issues and PRs, but no answer.

Is it possible your default soft-limit is set low on your machine?  Try ulimit -Sn (soft limit) and/or ulimit -Hn to check - if it's only 1k it might actually need to be raised.  If it's 4k or higher, your suspicions are probably correct about the globbing issues.

I think adding more rules to the ignores will not help as Hugo will probably need to check for all files and will apply the ignore filter after that. But this might not be true since it complains about open files.
Could you try the following to check if that might help?
diff --git a/util/build_docs.py b/util/build_docs.py
index bb2038b9..64d34ee2 100755
--- a/util/build_docs.py
+++ b/util/build_docs.py
@@ -293,6 +293,8 @@ def invoke_hugo(preview, hugo_bin_path):
     ]
     if preview:
         args += ["server"]
+        args += ["--watch=false"]
     subprocess.run(args, check=True, cwd=str(SRCTREE_TOP))

The best would be to restrict '--contentDir' to apply only to a limited subset, but I did not see how that would be possible.

OK, I finally got to the bottom of this. Increasing ulimit was something I did before, but generally wasn't sufficient.
Turns out, (my configuration of) VS Code is rather excessively watching files, exceeding the limits. Closing VS Code solves the problem. I probably need to spend a bit more time excluding build output directories there.

authors: cdgori imphil towoe


text:
Addressing issue for PROG_FIFO and RD_FIFO

Hello in the flash_ctrl_reg_top.sv#L91 the addressing being used to route the response of host request for the prog_fifo and the rd_fifo are different from the assigned address map. Am I getting something wrong?

ah in reg_top it's decimal, but in the address map it's hex.


text:
[entropy_src/dv] Scoreboarding of REPCNT & REPCNTS

This commit fixes many subtle in scoreboard accuracies regarding the
behavior of the REPCNT and REPCNTS tests.
Moreover in order to bring the entropy_src_rng test to 100% passing
these changes assume the fixes proposed in issue #14078 and implemented
in PR #14083.
Additionally this PR addresses a scoreboarding issue wherein HT alerts
will not fire if the DUT main SM has been forced into an error state
(notably due to a local escalation, which is the only SM error that
the scoreboard can predict).
Signed-off-by: Martin Lueker-Boden martin.lueker-boden@wdc.com

Hi @weicaiyang,
I made some incremental changes to the scoreboarding after deciding to drop the RTL changes proposed in #14083.   Would you mind re-reviewing this?  If you like you can take a look at just the second commit (2f085d7362374bd489d9c4530f26ad08a0eeba8a).  I'll squash them when everything is done.


text:
[ci] Move SW Build and Test job to ci-public

The public Azure Pipelines ubuntu-20.04 pool is slightly overtaxed, causing the ci-public pool to be underutilized over the past few days. We can move the SW Build and Test step (which normally takes about 30-40 min on Azure-hosted runners) to the ci-public machine. This job would also benefit from the increased parallelization.
Signed-off-by: Miles Dai milesdai@google.com

Alternatively, we could move the airgapped environment test to the ci-public machine. I'm just not entirely sure right now if the network namespacing used in there will affect the ci-public containers.


text:
[rom_ctrl] Switch to overridable memory mechanism

This is a carryover commit from integrated_dev.
It will make parameterization of the ROM_CTRL via the top_earlgrey.hjson much more straightforward using the same mechanism used for SRAM_CTRL.
It will also allow us to have multiple ROM_CTRL instances in a design, just like we do in Darjeeling.
I will take another look at whether D2S/V2S is still fulfilled after this lands.
It also looks like we still need to bump the design stages in the Hjson, even though the signoff issues have already been closed.

Unfortunately we can't override window sizes at the top-level, which would be necessary in order to instantiate two different ROM_CTRL parameterizations.
To that end, this patch switches to the same topgen override mechanism that the SRAM_CTRL uses. That however means that we have to remove the window and second reg_top, which in turn affects how the DV environment is constructed.
Most edits there have basically been carried over from the SRAM_CTRL testbench.
This patch also adds simulation configurations for the relevant ROM sizes.

Unfortunately we can't override window sizes at the top-level, which would be necessary in order to instantiate two different ROM_CTRL parameterizations.

Out of curiosity, is this going to make sense as an ipgen type someday? It kind of feels like we're avoiding our infrastructure, but I can't claim familiarity with the decisions that led to SRAM_CTRL's mechanism. :)

Unfortunately we can't override window sizes at the top-level, which would be necessary in order to instantiate two different ROM_CTRL parameterizations.

Out of curiosity, is this going to make sense as an ipgen type someday? It kind of feels like we're avoiding our infrastructure, but I can't claim familiarity with the decisions that led to SRAM_CTRL's mechanism. :)

I believe that mechanism was implemented at a time where Ipgen wasn't a thing yet and we did not want to have yet another templated IP that uses some custom script for generation ;).
Converting to Ipgen could make sense, although maybe we need some sort of intermediate mechanism where overriding Hjson parameters is enough (i.e., no templating is needed since the SV parameters offer enough flexibility).

The CI (Verilated English Breakfast (Execute)) failure is unrelated and currently known broken.
It should not gate this PR from getting merged.

authors: a-will msfschaffner


text:
[chip-test/sival] Optimize csrng_edn_concurrency test and run more seeds in nightlies

This PR contains three more commits to optimize the csrng_edn_concurrency test to focus on the CSRNG and EDN interaction (and reducing wait times for ENTROPY_SRC during the test loop) and it increases the number of seeds we run in the nightlies as proposed #22753 .

The FPGA tests all fail but it looks like an infrastructure issue. This PR touches a file only relevant for one specific test which isn't run in CI. But the test is run in the nightlies and I am merging this now such that the next nightly regression runs the modified test with more seeds. We need this for M4.


text:
[ci] Add Task To Build Docker Containers

We currently do no checking or automated updating of the Dockerfiles
committed to the repository. This makes a step along that path, with a
task that will at least attempt to build the three containers.
In the future, we may turn on some kind of automated updating for
commits to the master branch, but that's a lot more dangerous than this.

@imphil I think we want to push the images to our own locations (both images are canonically on google cloud's container image hosting right now) - I don't know how docker hub works, but I thought this a simpler thing to start with.


text:
[i2c, dv] Support on-the-fly reset, add error_intr, and fix fifo_overflow

This PR includes
- Update i2c_agent to assert error interrupts (e.g. sda_interference, scl_inteference, and sda_unstable)
- Install on-the-fly reset for i2c_agent and scoreboard to allow dut and dv are reset then re-started when the error interrupts are triggered
- Add error_intr test
- Disable checking request match in tl_host_driveri (tl_agent) when reset is in progress
- Fix i2c_fifo_overflow test to address PR #3422

I submit the patch for tl_host_driver with this PR after a discussion with @weicaiyang for the bug. Since the change is tiny so I and @weicaiyang agreed to include the change for tl_host_driver with this PR which mainly focused on i2c instead of splitting.

I fixed fifo_overflow to adopt PR #3422

@weicaiyang I force-pushed the commit efeacfe to address your comment. Please do review, thank!

@rasmus-madsen any further comments?

@rasmus-madsen any further comments?

nope LGTM


text:
[lc_ctrl] Remove RD access to isolated partition in DEV

This addresses a security concern in #7197.
Signed-off-by: Michael Schaffner msf@opentitan.org

We can also remove the write access, but I don't think that is needed.

Sure - just thought I'd put the change already out such that we can get it reviewed.


text:
Feat: current time indicator

Feat: Add marker to current time slot

fix for #53
also fixes #47

@lozzd this will conflict with my other pull request but both are compatible

also fix for #44 and #9

repo: lozzd/octopus-energy-rates-card


text:
feature selection

Hi~  Is there any specific reason for choosing the specific order of feature selection? The first time, we ANOVA and then MRMR?

Hi! The reasoning is that since the first phase of the feature extraction and selection can be performed in a distributed manner on different nodes, we need a selection method that ranks the utility of each feature "independently",  so that we get an initial collection of the most useful features globally (across nodes). Afterwards, when this first set of features is gathered to the main node, we use MRMR to reduce redundancy, since it can compare the utility and correlation of the features. That being said, you could experiment with different feature ranking methods and potentially get some interesting results!

Thanks for your repley. If you only use one CPU to run your code (that is, only a single node), does that mean that ANOVA has no particular advantage over other feature selection method. If I understand you correctly, nodes are not channels but computing devices.

Hi,
That's correct, if you have all the generated features of the first phase on a single node, you could modify the code appropriately to use other selection methods (that even take into account the other features, such as MRMR). Yes, with nodes I am referring to computational devices, such as computers on a local network. Let me know if this is clear!

Your answer is very clear, thank you very much for your patience.

repo: lpphd/lightwaves


text:
Sonar settings

Incorporate them to GitHub (preferable) to track changes and have online storage

Maybe this will be not needed with #240

Due to #361 - not needed

repo: lrozenblyum/chess


text:
[Feature Request] Compatiable With Another Addon

Any chance you can make the animated Twitch emotes work as well? The static ones work but the animated ones only move by 1 frame when you scroll up or down.
Twitch Emotes v2

I'll look into how it works later, so I can't guarantee anything atm. Rn I'm busy with my other addons >_>

I'm not sure when I fixed that, but it's been working for quite a while :D


text:
Programming exercise titles must be unique and cannot be renamed properly

Describe the bug
Importing a programming exercise in a course with the same title into the same course fails with an internal server error (but still create the exercise in Artemis, but without repos/CI). Moreover, renaming the title of the exercise you want to import will not change that, the old title stays locked as long as the programming exercise exists.
This process is e.g. (currently) necessary to move an exercise from the course to an exam.
I guess this is due to the way projects are handled in BitBucket/Bamboo.
Solution
Either the title ca be whatever the user wants (preferred, the short name should be providing uniqueness) or renaming will cause the old name to be available again.
Workaround
Import the exercise with different name, delete the old one, import the exercise with the old name.

At least the point "Importing a programming exercise in a course with the same title into the same course fails with an internal server error (but still create the exercise in Artemis, but without repos/CI)" was fixed already with additional validation checks.
The other parts are a bit more difficult to fix, because Artemis would need to rename the project in Bitbucket and Bamboo which is currently not supported, but might be possible.

authors: MaisiKoleni krusche


text:
Exam mode: Rejecting complaints leads to wrong points displayed to student

Describe the bug
After an exam was conducted, the complaint period was started, and a complaint was filed by a student. The complaint was rejected by an instructor within the complaint period.
For the affected exercise, the student now sees "No graded result" for the exercise, as can be seen in the following scrennshot:

Also, in the table that summarizes the points for their exam exercises  (see screenshot below), the students sees 0 points for the affected exercise, even though the actual points for the exercise are not zero.

On the instructor side, the points for the exercise are displayed correctly, but marked as preliminary:

To Reproduce

Conduct exam
Grade exams
Publish results and start complaint period
Complain as a student about one exercise assessment
Reject complaint as an instructor
As a student, view your exam overview and the exercise you complained for.
Observe described behavior

Expected behavior
The student should see the changed grading of the exercise in both the exercise view and the exam overview.
Screenshots
No response
What browsers are you seeing the problem on?
Firefox
Additional context
The complaint period was (is) still running when the complaint was rejected and the spurious points and grading status were displayed. The exercise in question was a programming exercise.
It is not clear whether this issue affects the display of accepted complaints and whether it affects the display of points after the end of the complaint period.
Relevant log output
No response

Additional context: We have gotten word from an affected student that this also affects the grade as shown to the students. The new grade is calculated as if they received no points for the exercise in question.

Thanks for reporting! We will fix it asap!

I tried looking into it, but I can’t reproduce it. I tried it four times locally and on TS3.

Created an exam with a default bubble sort programming exercise (semi-automatic assessment mode)
Participated and submitted
Assessed the exercise, gave it mediocre points
Complained as a student during the student review time window
Rejected the complaint during the student time window

For the student, it shows that the complaint has been rejected. “Your points” remained at what I set it during assessment.
@jerhard, could you share more details about the configuration of your exam and exercise? Are there any missing steps? Ideally, we would be able to recreate the exam and exercise with the exact settings you're using so we can try again to repro that issue.

OK, i had time to look into the issue a bit:
The problem exists because we planned to do second corrections, but ran out of time for the corrections and had to skip second corrections for some exercises.
To reproduce the issue as we had you need to enable second corrections but not do the second correction round, then create a complaint and reject it.
Some more digging reveals that the issue has actually nothing to do with complaints but rather happens when there is an assessment lock for that submission and thus the latest result is still pending.
Thus the result disappears for the student when visiting the assessment page to look at the complaint and not when rejecting it.
The whole issue can be fixed by canceling the assessment lock or just doing the the second correction.
In conclusion the whole thing is likely mostly by design/user error and i am not sure what can really be done about it other than maybe just adding a skip second correction button that creates dummy second correction results to avoid taking the assessment lock when viewing complaints.

If second corrections are enabled, this issue also affects programming exercises that are graded only automatically.
In other words: If you have an exam where second corrections are enabled, and where the progamming exercises are graded automatically, and the students complain about the programming exercise, and the complaint is rejected, Artemis will show 0% to the students for that exercise.
This behavior should be changed such that the last grading is shown, also if the complaint is rejected.

authors: bassner bottbenj jerhard krusche michael-schwarz


text:
Development:  Increase contributor-model client test coverage

Checklist

[X] I chose a title conforming to the naming conventions for pull requests.

Client

[X] I followed the coding and design guidelines.

Description

Added a client test to improve the test coverage of contributor-model.ts.
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Test Coverage

contributor-model.ts 100% | 0%  --> 100% | 100%

I left 2 comments in the code.
But to be honest: Do we really want to keep this test? This is not testing any functionality or business logic.
Instead, to add coverage to this model, I'd suggest to extend about-us.component.spec.ts to actually render one or two contributors into HTML using this model, and then assert that it's actually on the page, e.g. by looking for their full name.

Thank you for your suggestion. I will look into it.

I agree with @coaxial1 about extending about-us.component.spec.ts for this model. An alternative might be converting the AboutUsModel and ContributorModel classes to interfaces if they are not instantiated at all, but since they have -Model suffix I am not sure this approach would be better.

I agree with @coaxial1 about extending about-us.component.spec.ts for this model. An alternative might be converting the AboutUsModel and ContributorModel classes to interfaces if they are not instantiated at all, but since they have -Model suffix I am not sure this approach would be better.

@akesfeden I updated the code according to the suggestions. Can you take another look?

authors: akesfeden canberkanar


text:
Iris: Add optional client context to message sending

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Motivation and Context
In many Iris features, Iris is designed to be aware of the user's context to provide more personalized and relevant assistance. However, the current system assumes that all necessary contextual information will be available server-side when the user sends a message. Sometimes however, the context on the user's screen has not been persisted to the server (yet) and only resides on the client - for example, unsaved form data. Therefore, it is useful if we have the option to send some extra context from the client when the user sends a message to Iris.
Description

We are now accepting a JsonNode context object in the IrisMessageResource through the Iris services and into the requestMessageFromIris() method to be used in the request.
The Iris button and Iris chatbot widget have been modified with an optional input parameter that allows you to set what context to collect from the UI every time the user sends a message to Iris. The sendMessage() and resendMessage() methods in the http services now additionally send this context to the server.

Steps for Testing

Prerequisites:

1 Editor
1 Programming Exercise with Iris enabled

Make sure that sending and receiving messages in the chat window still works

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Summary by CodeRabbit

New Features

Enhanced messaging functionality to include contextual information when sending or resending messages.
Introduced a new data transfer object for Iris messages to encapsulate message content and context.

Enhancements

Updated chatbot components to allow passing context information during message transmission.
Improved clarity of comments in code editor service for better understanding of functionality.

Refactor

Modified method signatures to support new context parameter in various services and components.

Reviewed CodeRabbit suggestions, all were non-issues

Thanks to @krusche for the suggestion to improve security by using a DTO hierarchy instead of JsonNode. I've also introduced an example usage of this feature in the Code Editor, where the unsaved problem statement on the client is sent to the server every time the user sends a message to Iris.

This PR is open too long, therefore we close it. Feel free to reopen it when the actual implementation is finished and needed

authors: MichaelOwenDyer krusche


text:
Adaptive learning: Add competency management operations for prerequisites

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I strictly followed the server coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Client

[x] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[x] I strictly followed the client coding and design guidelines.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[x] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Motivation and Context

Prerequisites should offer the same options as competencies, e.g. importing them from another course.
Description

Implement all operations for prerequisites that are on the competency management page and all related pages. These are:

Importing all from a course (and optionally the relations between them)
Importing a selection from all other courses
Importing standardised competencies
Create Prerequisites and link lecture units to them
Edit Prerequisites and link lecture units to them

This PR does not fix all issues that are related to competencies and their current implementation. E.g. Artemis did not check if imported competencies and existing competencies have the same title, so this is now also not checked for prerequisites.
But this PR makes it easier to fix this in the future by offering common methods for competencies and prerequisites.
Additionally there is now a button to import competencies and relations (and optionally the relations between them) of another course with a single operation.
Steps for Testing

Prerequisites:

1 Instructor
1 course with lecture units to link to prerequisites
1 other course with competencies and prerequisites to import

Log in to Artemis
Navigate to Course Administration
Test the different operations listed above

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[x] Server Code Review 1
[ ] Server Code Review 2
[x] Client Code Review 1
[ ] Client Code Review 2

Manual Tests

[x] Test 1
[ ] Test 2

Test Coverage

Client

Class/File
Line Coverage
Confirmation (assert/expect)

competency-management.component.ts
92.92%
✅

import-all-competencies.component.ts
94.73%
✅

competency.service.ts
100%
✅

course-competency.service.ts
81.53%
✅

create-competency.component.ts
96.77%
✅

create-course-competency.component.ts
100%
✅

create-prerequisite.component.ts
96.77%
✅

edit-course-competency.component.ts
100%
✅

edit-prerequisite.component.ts
95.45%
✅

competency-form.component.ts
86.36%
✅

course-competency-form.component.ts
94.54%
✅

prerequisite-form.component.ts
86.36%
✅

generate-competencies.component.ts
97.22%
✅

course-import-standardized-competencies.component.ts
100%
✅

course-import-standardized-course-competencies.component.ts
95.34%
✅

course-import-standardized-prerequisites.component.ts
100%
✅

import-prerequisites.component.ts
94.11%
✅

prerequisite.service.ts
100%
✅

competency-node-details.component.ts
95.23%
✅

course-competencies-details.component.ts
77.01%
✅

course-competencies.component.ts
94.91%
✅

course-prerequisites-modal.component.ts
94.73%
✅

standardized-competency-detail.component.ts
100%
✅

standardized-competency-filter.component.ts
100%
✅

Server

Class/File
Line Coverage
Confirmation (assert/expect)

PrerequisiteRepository.java
100%
✅

CompetencyRelationService.java
99%
✅

CompetencyService.java
100%
✅

CourseCompetencyService.java
88%
✅

PrerequisiteService.java
100%
✅

CompetencyResource.java
95%
✅

CourseCompetencyResource.java
84%
✅

PrerequisiteResource.java
95%
✅

Screenshots

Imporved competency management page:

Followed the testing steps, here is what I have noticed while testing on ts1:

On ts1 I cannot import standardized competencies - could you add some information how these can be defined if not selection option is available?

E.g. ts3 should have standardised competencies.

The filter looks a little broken, could you also use a filter icon beside Filter competencies?

I did not change the UI of the competencies and only reused it for prerequisites.

would it be a reasonable calculation effort to define whether the option Import all Prerequisites from another course is a useful for the displayed courses? (e.g. do not display a course if no prerequisites are defined and we want to import all prerequisites from another course)
right now this yields the following message

I only adapted the logic to work for competencies and prerequisites and did not write it from scratch. So I won't change it in this PR. Since you can only see the courses where you are editor/instructor, it should be ok to display all courses.

Followed the testing steps, here is what I have noticed while testing on ts1:

On ts1 I cannot import standardized competencies - could you add some information how these can be defined if not selection option is available?

E.g. ts3 should have standardised competencies.

The filter looks a little broken, could you also use a filter icon beside Filter competencies?

I did not change the UI of the competencies and only reused it for prerequisites.

would it be a reasonable calculation effort to define whether the option Import all Prerequisites from another course is a useful for the displayed courses? (e.g. do not display a course if no prerequisites are defined and we want to import all prerequisites from another course)

right now this yields the following message

I only adapted the logic to work for competencies and prerequisites and did not write it from scratch. So I won't change it in this PR. Since you can only see the courses where you are editor/instructor, it should be ok to display all courses.

Yeah, the things I mentioned are suggestions for future PRs

authors: JohannesStoehr florian-glombik


text:
Improve consistency of exercise status messages

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I added multiple integration tests (Spring) related to the features
[x] Server: I added @PreAuthorize and check the course groups for all new REST Calls (security)
[x] Server: I implemented the changes with a good performance and prevented too many database calls
[x] Server: I documented the Java code using JavaDoc style.
[x] Client: I added multiple integration tests (Jest) related to the features
[x] Client: I added authorities to all new routes and check the course groups for displaying navigation elements (links, buttons)
[x] Client: I documented the TypeScript code using JSDoc style.
[x] Client: I added multiple screenshots/screencasts of my UI changes
[x] Client: I translated all the newly inserted strings into German and English

Motivation and Context
Two bugs of the exercise status messages evaluation are fixed by these changes. These bugs have been caused by insufficient passing of the data necessary for the evaluation.
Description
Bug I: Exercise details page erroneously shows No graded result
For some exercise No graded result was displayed in the detail view, although these exercises had a result.
The solution was to add the exercise as property to the studentParticipation that is passed as an input to the upgrading-result.component. From there it is passed to the result.component where the actual status evaluation takes place.
Affected files: course-exercise-details.component.ts
Bug II: Inconsistent messages on the tutor dashboard
Wrong messages were displayed on the tutor dashboard, although they were displayed correctly on other pages. The submission was marked as too late, although it was submitted before the deadline. The evaluation of the exercise status failed because the submissions were missing in the participation object passed by the tutor-exercise-dashboard.component to the result.component.
The solution was to nest the corresponding submission into the participation object that is passed to the result.component. This solution is arguable since the submission is somehow nested in itself. The alternative, however, would be an additional @Input for the result.component, which would make the code much more verbose.
Affected files: tutor-exercise-dashboard.component.ts
Steps for Testing
For Bug I

Log in to Artemis
Navigate to the course exercise dashboard
Inspect an exercise with a result
Make sure that the status message indicates that the exercise has a result

For Bug II

Log in to Artemis
Navigate to the course exercise dashboard
Inspect an exercise that was submitted in time with a result (you should see the score)
Then go to the tutor dashboard for that exercise
Inspect the same exercise and make sure that the status message is the same

Screenshots

@krusche Before I enter evaluateTemplateStatusForModelingTextFileUploadExercises() I check for this.participation && getExercise(this.participation) in the surrounding if condition. Therefore the fallback case will never be executed.
evaluateTemplateStatusForQuizProgrammingExercises() implements (nearly) the same logic as the removed fallback case. I added the comment // This branch also handles edge/error cases implicitly: missing participation or missing exercise in participation. to make this clear.

Ok, I can see this now. However, I really don't like the code and the control flow here. Why do we even have these methods if they are only invoked once?
Why does evaluateTemplateStatusForQuizProgrammingExercises also handle the case that this.participation is undefined or null?
I would suggest to change the control flow like this

if (this.participation) { ... handle this case and return ... }

if (getExercise(this.participation)) { ... handle this case and return ... }

if (isModelingOrTextOrFileUpload(this.participation)) { ... handle this case and return ... }

if (isProgrammingOrQuiz(this.participation)) { ... handle this case and return ... }

this would be much easier to understand!

In the review for my last pull request, I was recommended to avoid nesting of if-statements as much as possible. So I used the methods to avoid nesting. Especially because of the handling of the edge/default cases I like your variant more. I'll adjust that.

I added another small bugfix to this PR (see description Bug III). In terms of bugfixes this PR is finished now for me. It tested everything again on the test server. Would be nice if my review team (@HanyaElhashemy , @Minh13, Beatris) could review it ;-)


text:
@!scope class behaviour not following docs example for "set of methods" scope

Docs here states that this should mark method1 & method2 as class methods:
# @!scope class

# Documentation for method1
def method1; end

# Documentation for method2
def method2; end

In my experience, this doesn't work and @!scope class must be repeated on all methods definitions
Steps to reproduce
Repro:
class Test
  def test_instance; end

  # @!scope class

  # method1 doc
  def method1; end

  # method2 doc
  def method2; end
end

class Test2
  def test_instance; end

  # @!scope class

  def method1; end

  def method2; end
end

class Test3
  def test_instance; end

  # method1 doc
  # @!scope class
  def method1; end

  # method2 doc
  # @!scope class
  def method2; end
end

Actual Output

Expected Output
I would expect Test & Test2 to behave the same, with Test2 methods having no doc.
I would expect Test & Test2 to have method1 & method2 as class methods.
I would expect Test & Test3 to have the same doc.
Environment details:

OS: Fedora 34
Ruby version (ruby -v): ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux]
YARD version (yard -v): yard 0.9.26

I have read the Contributing Guide.

Thanks for the report! This is fixed in the above commit and will be in the next release.

authors: lsegal qortex

repo: lsegal/yard

license: mit


text:
Move param name before type in README.md

Description
Move param name before type in first code sample to make it more readable.
Completed Tasks

[x] I have read the Contributing Guide.
[x] The pull request is complete (implemented / written).
[x] Git commits have been cleaned up (squash WIP / revert commits).
[x] I wrote tests and ran bundle exec rake locally (if code is attached to PR).

Coverage remained the same at 52.069% when pulling a0cf8a5f94c59fec611ea952a728de5db8e5fd35 on alexeymetelev:master into 1d312db99b80bd803a180c8954c22bfed58bdcbf on lsegal:master.

Thanks!

authors: alexeymetelev coveralls lsegal


text:
Documentation is hard to use

I used to be able to search the usage of functions easily since they were all on the same page. After the docs have bee divided into multiple pages, I find it's rather inconvenient when finding usage for a specify function.
I propose that this repo should revert back to the old way of organization for documentations.

Understood and sorry it pains you. Would you mind filing a pull request unifying the docs but keeping a table of contents?

You should rewrite the docs into an emacs org-mode file (it allows export to texinfo, man format, and html/pdf, and markdown - gives you a TOC for free too).
Maybe I'll set this up for you sometime

I have an unified version of the docs with a doctoc-generated TOC. I you want I can make a pull request.

Sounds good, go ahead!

authors: ahungry cuongthamhl lstrojny soutoner

repo: lstrojny/functional-php


text:
🛑 SoHard Cloud is down

In cf9bd5d, SoHard Cloud (http://cloud.lsy223622.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SoHard Cloud is back up in 1cc306d after 8 minutes.


text:
🛑 Mirror-爬 is down

In 0f2a858, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1046 ms

Resolved: Mirror-鱼露 is back up in a4c8eaf.


text:
🛑 Mirror-爬 is down

In 7302ed0, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 833 ms

Resolved: Mirror-鱼露 is back up in c9877be.


text:
🛑 Mirror-爬 is down

In c7fcd4c, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1877 ms

Resolved: Mirror-鱼露 is back up in ea6f1f7.


text:
🛑 Mirror-爬 is down

In 3ad7624, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 799 ms

Resolved: Mirror-鱼露 is back up in f550797.


text:
🛑 Mirror-没有女朋友跨年的群傻逼 is down

In 5e3e2ba, Mirror-没有女朋友跨年的群傻逼 (https://x.ksfu.top/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mirror-木生 is back up in dd12ec6.


text:
🛑 Mirror-爬 is down

In c583284, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 989 ms

Resolved: Mirror-鱼露 is back up in e52a114.


text:
🛑 Mirror-爬 is down

In ab482bd, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 675 ms

Resolved: Mirror-鱼露 is back up in 4ce3465.


text:
Export to TensorRT

A few questions about exporting FastFlowNet to TensorRT for inference on the Xavier TX2.

Which version of TensorRT was used to test FastFlowNet on the Xavier TX2?
Which toolkit or opensource project did you use to export FastFlowNet from pytorch to TensorRT? Did you use torch2trt?

I use TensorRT 6.0 to test FastFlowNet on the Jeston TX2.
I write CUDA kernel and TensorRT plugin of Center Dense Dilated Correlation layer and Warping layer, then I use CMake to compile them into dynamic link library (libplugin.so). Next, I implement FastFlowNet with TensorRT without using torch2trt, and load the Center Dense Dilated Correlation layer and Warping layer from above compiled dynamic link library, and add them to the network as custom plugin layers. Finally, I load the PyTorch pretrained parameters to the TensorRT model.

I use TensorRT 6.0 to test FastFlowNet on the Jeston TX2. I write CUDA kernel and TensorRT plugin of Center Dense Dilated Correlation layer and Warping layer, then I use CMake to compile them into dynamic link library (libplugin.so). Next, I implement FastFlowNet with TensorRT without using torch2trt, and load the Center Dense Dilated Correlation layer and Warping layer from above compiled dynamic link library, and add them to the network as custom plugin layers. Finally, I load the PyTorch pretrained parameters to the TensorRT model.

感谢您的开源工作！我是一个深度学习的新手，我想请教一下，在您的模型中使用了cuda编程，那么是不是没法将这个模型直接转化成onnx模型了呢？我的gpu不是3060Ti，想要部署这个模型的tensorrt，是不是只能按照您的方法自己重写tensorrt模型？不同cuda型号需要对tensorrt模型有很大改动吗？

authors: Cai-RS anenbergb ltkong218


text:
🛑 Národný ústav certifikovaných meraní vzdelávania is down

In e67f0ef, Národný ústav certifikovaných meraní vzdelávania (https://www.nucem.sk/) was down:

HTTP code: 502
Response time: 946 ms

Resolved: Národný ústav certifikovaných meraní vzdelávania is back up in 91eb12b.

repo: lubosm/minedusk-uptime


text:
🛑 Školský šport is down

In 4979fb3, Školský šport (https://skolskysport.sk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Školský šport is back up in e952090.


text:
🛑 Školský šport is down

In 0b15d50, Školský šport (https://skolskysport.sk/) was down:

HTTP code: 403
Response time: 1025 ms

Resolved: Školský šport is back up in 75682b0.


text:
Update README

describe usage with external test-runners (as followup for #29)
describe builtin generators (I believe it would be useful to have these descriptions in README. Yes, I know about documentation generated by ldoc.)

Left some minor suggestions, looks good for the rest.

Thanks for suggestions! Everything committed, squashed (also I have added Co-authored-by to mark you as co-author) and force-pushed.
Seems change with descriptions for generators requires review too - I'm stuck with description for some of them.

Unfortunately CI is broken, sorry for that.
I'll fix it in a separate commit in the same PR (if you have no objections).
right now it can start, but

Lua == 5.1 failed due to segmentation fault in busted (https://github.com/luc-tielen/lua-quickcheck/pull/30/checks?check_run_id=2333602586)
LuaJIT jobs failed to upload code coverage data:

Uploading ...
Upload error: Couldn't find a repository matching this job.
Raw data:	Couldn't find a repository matching this job.
--------------------
Upload error: Couldn't find a repository matching this job.
Raw data:	Couldn't find a repository matching this job.
--------------------

@ligurio Yeah, it never is that easy to switch over CI.. I'd look into the segfault first. If we can't fix that; we might have to go back to old way of CI? :thinking:

Yeah, it never is that easy to switch over CI.. I'd look into the segfault first. If we can't fix that; we might have to go back to old way of CI?

I suspect the root cause is not in CI itself but in actions described by me. CI workflow runs on Ubuntu 20.04, I have the same OS on my laptop and everything works fine there. I'll try to investigate problem more and try to fix it.

I have found a ticket about random luajit segfaults on running busted and also related conversation in luajit mailing list.
Someone suggested a solution with small Lua snippet. I have applied it to lua-quickcheck and now CI is red but due to failed steps with upload code coverage data to coveralls service. I suspect lua-coveralls requires environment variable with coveralls token (see https://github.com/moteus/luacov-coveralls).
For me this solution looks like a dirty hack.

@ligurio maybe we should split this PR into multiple parts? Just README docs in this 1, fixing CI in another? CI is broken anyway, so I will merge in when docs are updated.

Agree. I have failed to fix CI quickly so it's better to split PRs. I'll do.

@luc-tielen done

authors: ligurio luc-tielen

repo: luc-tielen/lua-quickcheck


text:
Explore validation with JSON Schema

This is more of a POC to see if we can easily add validation by extending resource attributes and leveraging JSON Schema to do the heavy lifting. What do you think?

It looks good. If I'm reading it correctly with this validation step this library can validate the params itself without any other library doing the job.

Yes, that's the idea. This is just a POC:

The resource definition can be expanded to support more features from json schema.
We could work out a way to collect everything and generate a reasonable OpenAPI specification.
We can also experiment with different libraries to see what fits best.

authors: lucacorti treere


text:
quic-go 0.10.2 client could not connect quic-go 0.12.0 server

my client app using quic-go0.10.2, now i wanna upgrade my server app to quic-go 0.12.0, unluckly it seems to not compatible.
Is that really not compatible?

That's correct, they use different QUIC version numbers.

authors: haodongh marten-seemann

repo: lucas-clemente/quic-go


text:
Receiving Data Error

The thread that receive data send it to the game_view and it uses "window.finalize()". But the code at create_game.py is waiting a button to be clicked ... then window.finalize() can't be used because the button is waiting to be clicked.

Ok, I created a button "update" to update the data received from other people.


text:
Bottomsheet doesn't lock orientation when app has only portrait mode.

Describe the bug
The bottomsheet changes orientation when phone is on horizontal position even if the app support only portrait mode.
Minimal reproduce-able code
`
import MapKit
import SwiftUI
import BottomSheet
struct ContentView: View {
@State var bottomSheetPosition: BottomSheetPosition = .relative(0.60) //1
var body: some View {

    Map() //2
        .bottomSheet(
            bottomSheetPosition: $bottomSheetPosition,
            switchablePositions: [],
            content: {
                Text("test")
            }
        ) //3
}

}
`
Expected behavior
The bottomsheet should lock orientation as well, it shouldn't be shrinking as shown in the clip below.
https://github.com/user-attachments/assets/c1bdeb9e-94ed-406f-b226-f4983877cd30
Screenshots
If applicable, add screenshots to help explain your problem.

Target version

Environment: iOS 17.2
Version: Bottomsheet v3.1.1

Additional context
Add any other context about the problem here.

Try adding this property: .sheetWidth(.relative(1))

it works, thanks

authors: SteeveFong mikejonas

repo: lucaszischka/BottomSheet


text:
Saw you changed ResNet to ConvNext

I recently was thinking of doing the same but was wondering if you have tried it and seen any actual benefit?
I am currently using the UNet architecture from OpenAI improved/guided diffusion as well
Thanks

@Mut1nyJD it seems to work! im just tired of batchnorm or groupnorms - layernorms all the way from now on :D

@lucidrains Thanks for your honest answer. I see friends do not let friends use Batchnorm ;)
Just wondering if you saw any improvements in image quality, convergence or sampling time

repo: lucidrains/denoising-diffusion-pytorch


text:
Warning: Mixed memory format inputs detected while calling the operator.

I have added lambda layers to every block of Resnet, but the following warning will appear. Will it affect the result?
Warning: Mixed memory format inputs detected while calling the operator. The operator will output channels_last tensor even if some of the inputs are not in channels_last format. (function operator())

Could you try with a dim_u greater than 1 and see if that error goes away?

class BasicBlock(nn.Module):        # resnet18, resnet34
    expansion = 1

    def __init__(self, c1, c2, stride=1, downsample=None):
        super(BasicBlock, self).__init__()
        self.conv1 = conv3x3(c1, c2, stride)
        self.bn1 = nn.BatchNorm2d(c2)
        self.relu = nn.ReLU(inplace=True)
        self.conv2 = conv3x3(c2, c2)
        self.bn2 = nn.BatchNorm2d(c2)
        self.downsample = downsample
        self.stride = stride

        # lambda layers
        self.lambda_layers = LambdaLayer(
            dim = c2,
            dim_out= c2,
            r = 23,
            dim_k = 16,
            heads = 4,
            dim_u = 4
        )

    def forward(self, x):
        identity = x

        out = self.conv1(x)
        out = self.bn1(out)
        out = self.relu(out)

        out = self.conv2(out)
        out = self.bn2(out)

        if self.downsample is not None:
            identity = self.downsample(x)

        # lambda layers
        out = self.lambda_layers(out)

        out += identity
        out = self.relu(out)
        return out

yes, dim_u = 4.
at the same time, I don’t know if I changed it right.

@Pluto1314 ok, should be fixed in the latest! https://github.com/lucidrains/lambda-networks/commit/b6c88742d65479246a7a71cdd0ddf501e3d36d50

Thanks, everything is working now!

repo: lucidrains/lambda-networks


text:
🛑 Cam-85 is down

In 33f7bfd, Cam-85 (http://lucien.kerl.io:85) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cam-85 is back up in e649bff.

repo: lucienkerl/status


text:
Default Group

When People Join They are not given the default group for some reason

https://github.com/lucko/LuckPerms/wiki/Default-Groups

no info about it lol

what?
The page explains how LP handles default groups and what some possible solutions are...
Also, instead of just saying "When People Join They are not given the default group for some reason" or "no info about it lol" maybe try to actually provide some useful information?

I am also having the same issue, I am setting up a new server and using my test account to test how new players would interact with the server. Joining the server "for the first time" does not seem to put my account into the default group and also does not create a user file in the storage. I am not seeing anything in https://github.com/lucko/LuckPerms/wiki/Default-Groups that is helping me understand this issue. Using version 4.4.30 on bukkit.

The default groups page already explains that LP doesn't store the player when they don't have any permissions or groups assigned. So that is intentional behaviour.
Do the players have permissions you set in the default group?
If yes, then they have the default group assigned.

I did see that part. My intention is to start new players into the default group so they can have basic permissions. There is a lot of info to cover and I have been lost on that part. For now, it does not seem like new to server players have any permissions from the default group I have set. I used the migration command successfully just prior to testing.

I think I figured it out. This is part of the default permissions I got after the migration command. I see some perms have a value under them "value: true" or "value: false". The perms that are missing the value true or false wont work?

zarena.voter:
value: true
world: parkour
ecocreature.gain.*
ecocreature.reward.*
modifyworld.*
multiverse.access.*
phatloots.loot.*
serversigns.use.*
towny.wild.*
worldguard.region.teleport.member.*
backfromthedead.backpack
backfromthedead.spawn
bssentials.command.delhome
bssentials.command.disnick
bssentials.command.home
bssentials.command.nick
bssentials.command.pm
bssentials.command.sethome
bssentials.command.spawn
bssentials.command.viewnick
bssentials.command.warp
bukkit.command.plugins:
value: false
chatex.allowchat
chatex.chat.bold
chatex.chat.color
chatex.chat.italic
coloredtags.hero:
value: false
coloredtags.hr:
value: false
coloredtags.immortal:
value: false
coloredtags.initiate:
value: false
coloredtags.legend:
value: false
coloredtags.nomad
coloredtags.owner:
value: false
coloredtags.vip:
value: false

If the value is undefined then it is assumed to be true.
Could you just post a link to your editor? /LP editor

Please keep in mind that migrating from other perm plugins won't change the default group.
The default group is always called "default" and you have to use one of the methods explained on the Default Group page to change that.
My recommendation is to let default inherit the group, that previously was your default one.
Also, it doesn't matter if value: true is set... When it doesn't do LP assumes you're granting the permissions.

Here is a screenshot of my FTP editor and the link for the LP editor groups
https://luckperms.github.io/editor/#XefH28ZFUF

We don't encourage people to manually edit files as a small typo can mess up your entire system.

I have not edited the file yet. that was the result of the migration

You have a lot of permissions with world contexts, make sure you are in the correct world while debugging the permissions. You can also use the verbose mode to see whether the permission checks are being passed or not.

The permissions in question are in the global context, a lot of the perms are dead from my old 2015 server HA! I added a few new ones from BSSENTIALS, and added them to the PEX file before the migration, and they  are near the bottom of the list. At the same time, before I wiped the player file, I was in the group "initiate" and I had the "INITIATE" prefix in chat, but couldnt use basic perms. I deleted the player file, and prefix for default should be "NOMAD" but there is no prefix, and still not able to use basic commands such as /spawn

Just reply here or join the discord

I have it figured out. Deleted the dead perms. Realized some plugin perms are not working because they are either broken or some other issue, like "colored tags" perms are not working due to it being an outdated plugin so I used the prefix perms successfully, which shown me my test account is in the default group displaying the prefix tag I made. spawn is not working because I believe Bssentials permission for spawn is not working. I have it from here. Thank you Turbo and Andre.

repo: lucko/LuckPerms


text:
May need to update example command_who_am_i.py

The problem
in command_who_am_i.py
res = s.get_self()
username = res.username  # this will raise a key error
print res.keys()

# [u'first_name',
#  u'print_name',
#  u'peer_type',
#  u'when',
#  u'phone',
#  u'last_name',
#  u'flags',
#  u'peer_id',
#  u'id']

I don't know the inner working of pytg and tg, but I suspect Telegram changed the response slightly and username is no longer used. It may be worth updating the examples. I may get around to a pull request with the changes.
Your environment
OS: Ubuntu 14.04
Python: 2.7
pytg: 0.4.10

Does the account of you bot has a @username?

Oh okay. I was checking out a user, not a bot. They may have been the problem.

I assume this is resolved?

Yes
On Jan 9, 2017 11:14 AM, "Luckydonald" notifications@github.com wrote:

I assume this is resolved?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luckydonald/pytg/issues/100#issuecomment-271327982,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGzR1RAs1DdI-0pQrpH_ShWawIqcZcLks5rQlzygaJpZM4K0WQt
.

authors: Shatnerz luckydonald

repo: luckydonald/pytg


text:
Import host information as environment

Would it be possible to create an environment and set the host from the swagger.json as variable into the requests? This would allow to import swagger files and run against different servers (dev,stage,prod) without changing every request

@hoegertn i have created a branch that has this functionality.
https://github.com/luckymarmot/Paw-SwaggerImporter/tree/setHostAsEnv
It would be nice to have a ui for an importer, but for know i hope this helps.
To install you will need:
git, npm (v2.11.3) aka node (v0.12.7)
then checkout setHostAsEnv branch.
npm install
npm install -g cake
npm install -g coffee-script
npm install mkdirp ncp
cake build
cake install

This will install into your Paw.app
Let me know if this helps.

Great. I will check this today.

com.luckymarmot.PawExtensions.SwaggerImporter.zip
Uploaded using ZenHub.io
I have added the compiled plugin: you need to unzip it and add it to: you extensions folder. (to find this open preferences from Paw and click extensions tab)

click "open extensions Directory": replace the existing swagger importer with the folder within this zip file.

Hi,
import works like charm. Some points to improve it even further:

There is a typo in the name of the domain "hostEvnDomain"
Maybe it is possible to use the "title" of the group as env domain name
Please add the scheme to the variable "://" to allow to change this globally to.

My main use case is to test against http://localhost and https production

authors: hishnash hoegertn

repo: luckymarmot/Paw-SwaggerImporter


text:
Git 협업 관련 글 작성

협업 초기 git 관련글을 작성할 예정입니다.


text:
[Write Me] How to Submit My Game

This section at the bottom of the hosting guide needs filling in.

Should be based of this, or subsequent versions of this video
I'm putting the final touches on this, but here is how you join the event (create a game) and make blog posts. #LDJAM pic.twitter.com/jWVgY7eqDk— Mike Kasprzak🆚#LD38 (@mikekasprzak) April 21, 2017

I'm uploading a youtube version, but yeah.

authors: povrazor zwrawr

repo: ludumdare/ludumdare


text:
AttributeError: 'module' object has no attribute 'text_format'

self.solver_param = caffe_pb2.SolverParameter()
with open(solver_prototxt, 'rt') as f:
pb2.text_format.Merge(f.read(), self.solver_param)
程序编译到这一步出错，报AttributeError: 'module' object has no attribute 'text_format'错误，请问是什么原因啊？？？

you can try changing pb2.text_format.Merge(f.read(), self.solver_param) to tf.Merge(f.read(), self.solver_param) and add import google.protobuf.text_format as tf at the top.

repo: luhaofang/tripletloss


text:
Escolher ferramenta de IaC

Depende de https://github.com/luizaalves/smu20222/issues/13 e https://github.com/luizaalves/smu20222/issues/14.

Adotado AWS CloudFormation como ferramenta da disciplina.


text:
Issue with search functionality

I just discovered that for any reason there is an issue with the search function.
If I search for "spinat" (the German word for spinach btw :p) or to be precise even start entering "spi", then it does not update the suggestions at all.. nevertheless if I hit return it opens the most recent note containing the search query.
Performing the same search request in Evernote leads 5 notes containing this word.. I have no idea if there are other letter combinations causing the same problem.

My best guess it that processing of the search results fail and then, the return results list is empty. This manifest in "nothing" happens.
I'll add some debugging information to the processing which might shade some light on this issue; probably at the weekend.

@agentcross Hi can you checkout the last commit I made and try to run some of the queries that yield the problem? The action should report errors to the console. It would be very helpful, if you could send me those errors for further investigations.

Sure, see below. Or how would you like me to send the errors?
process launchbar:
Evernote_Test (net.pustina.LaunchBar.action.evernote_Test): Unhandled Exception in script "suggestions.js": SyntaxError: Unexpected identifier 's'. Expected '}' to end an object literal. {     column = 17;     line = 12; }
process logger:
Evernote LbAction failed because „item 4 of {note id "x-coredata://8595DE0B-FE6C-4F08-8659-AE2DB32B1DF6/ENNote/p21" of notebook "01 Rezepte" of application "Evernote", note id "x-coredata://8595DE0B-FE6C-4F08-8659-AE2DB32B1DF6/ENNote/p25" of notebook "01 Rezepte" of application "Evernote", note id "x-coredata://8595DE0B-FE6C-4F08-8659-AE2DB32B1DF6/ENNote/p134" of notebook "01 Rezepte" of application "Evernote"}“ kann nicht gelesen werden.
"kann nicht gelesen werden." means " cannot be read." Don't know why it changes to German.
Hope it helps, if you need anything else just let me know.

Perfect. What I now need is for you to send me the a screen shot of the note's retails -- if open the specific note and klick on the button represented by an i with a circle around it.

Here you go.

There you go. The ' in Oma's Spinat cannot currently be parsed -- cf. https://github.com/lukaspustina/Evernote.lbaction#known-limitations. Unfortunately, I don't see a way how to solve this for now.
Since I'm working on your "Saved Search" feature, I will completely refactor the code -- cf. #4. Maybe I'll find another way how to deal with notes containing ' in their title.
For now, you need to remove the ' from the note and your search will work as expected. And you don't use the ' in German's Genetiv as you do in English anyway :)

Haha, nice German knowledge !
Thanks for investigating the bug. I did read the limitations but just thought that only this one note will be affected

In German you say "To have tomatos on the eyes" when you mean that you have been blind for a thing. Well, I had large tomatos on mine. The issue is fixed and the limitation is gone.

@agentcross Can you check, if the last commit fixes your "spinach problem"?

Yep, is solved !

authors: agentcross lukaspustina


text:
Verizon iPhone Compatibility

Hey Luke,
I'm noticing an issue with connecting to a pusher channel on the Verizon iPhone 4/4S with my iOS app using your previous version of libPusher.  Connecting to a pusher channel works if the Verizon iPhone is on WIFI which leads me to believe that it has something to do with Verizon's network.   Do you have any suggestions on what might be the problem?
Thanks.
Adam

Hi Adam
I've had numerous reports of problems with Pusher over a 3G connection due to transparent proxying on the network end. The fix for this is to use a secure HTTPS connection.
If you are using the old version of libPusher (prior to the recent big refactor) I'd highly recommend taking the time to upgrade to the new version which contains numerous fixes and improvements as well as SSL support.

Thanks Luke!
After I update with the new libPusher I'll let you know if that solves the problem.

Closing as a dupe of #4. Please re-open if you are still having issues. You may want to grab the latest build.

authors: adamkidbombay lukeredpath

repo: lukeredpath/libPusher


text:
How about manage multiple ssh keys?

Suppose I have multiple ssh keys under my ~/.ssh folder, pshazz will help to manage the id_rsa by default, but what about others? Manually add them by using ssh-add?
Is there a best practice of using pshazz to manage multiple ssh keys?

I haven't tried it, but does this answer help?

Yes, this works. Actually I always use ssh config on Linux/Mac, but forgot to copy this to windows. Thanks for reminding me, closed.

authors: lukesampson nightire

repo: lukesampson/pshazz

license: unlicense


text:
bulk-rename-utility@3.3.1.0: hash check failed

Another one to revise

Duplicate of #3079

authors: ither rasa

repo: lukesampson/scoop-extras

license: Unlicense


text:
Piriform Apps: Change URLs, add persist, modify checkver

I'm not sure if this will fix Piriform apps' hash errors...

Change URLs to ccleaner.com
Modify checkver and download URLs and download filenames (change to filename returned by URL)
Add persist (and switch off autoupdate)

Change download file name to dl.zip.


text:
Equation of line from two points

Example Problem:
Find the equation of the line between points (0,1) and (2,5) in slope-intercept form.
Example Solution:
y=2x+1
Further explanation (optional):
Coordinates should be between positive and negative 20

I would like to contribute to the solution to this problem.

Can i work on this too?

I would like to contribute under hacktober fest. Plz assign this to me.

can you assign to me @lukew3 @

Which form does the equation of the line need to be in? Or can that be alterable? If so, in what form do you want to input the form?

Which form does the equation of the line need to be in? Or can that be alterable? If so, in what form do you want to input the form?

I think that it would make sense for the solution to always be in slope intercept form, y = mx + b.


text:
Re-organise sidebar of Learn section

Are the - just strings? and supposed to be an indent? If so, should we not keep them as drop downs?

Are the - just strings? and supposed to be an indent? If so, should we not keep them as drop downs?

I could try, but I think it really create a big nesting. Let me check

PR moved to draft as several things are broken. Including code syntax highlighting

Reverted the change for renaming from Learn to Tutorial, as this is a big change for the SEO, etc... and we should discuss this together first in team.
@rowkee for this:

Are the - just strings? and supposed to be an indent? If so, should we not keep them as drop downs?

Agree I remove the "bullet" list - and moved the re-org of the internal items with dropdowns in #1004 🫡

repo: lukso-network/docs


text:
VRouterScopeNotFoundException when hot reloading

Hey, I'm getting the below exception when hot reloading. Everything keeps working but when I enable VSCode to display every exception it's shown.

Are you using VRouter or VRouterDelegate?

Also on which platform?

Also could I have the full stackTrace?

I'm using VRouter. The platform was windows but the same happens in Android.
CallStack
VRouterScope.of (c:\Users\evandromb\AppData\Local\Pub\Cache\hosted\pub.dartlang.org\vrouter-1.1.4+6\lib\src\core\vrouter_scope.dart:43)
_VRouterScopeState.build (c:\Users\evandromb\AppData\Local\Pub\Cache\hosted\pub.dartlang.org\vrouter-1.1.4+6\lib\src\core\vrouter_scope.dart:60)
StatefulElement.build (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4691)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4574)
StatefulElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4746)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatefulElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4778)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
StatefulElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4746)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatefulElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4778)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatelessElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4655)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
SingleChildRenderObjectElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:6090)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
SingleChildRenderObjectElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:6090)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
StatefulElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4746)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatefulElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4778)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatelessElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4655)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
_InheritedProviderScopeElement.performRebuild (c:\Users\evandromb\AppData\Local\Pub\Cache\hosted\pub.dartlang.org\provider-5.0.0\lib\src\inherited_provider.dart:456)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
ProxyElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4922)
_InheritedProviderScopeElement.update (c:\Users\evandromb\AppData\Local\Pub\Cache\hosted\pub.dartlang.org\provider-5.0.0\lib\src\inherited_provider.dart:477)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatelessElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4655)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
StatelessElement.update (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4655)
Element.updateChild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:3350)
ComponentElement.performRebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4599)
Element.rebuild (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:4267)
BuildOwner.buildScope (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\framework.dart:2582)
WidgetsBinding.drawFrame (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\widgets\binding.dart:875)
RendererBinding._handlePersistentFrameCallback (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\rendering\binding.dart:328)
SchedulerBinding._invokeFrameCallback (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\scheduler\binding.dart:1144)
SchedulerBinding.handleDrawFrame (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\scheduler\binding.dart:1082)
SchedulerBinding.scheduleWarmUpFrame.<anonymous closure> (c:\Users\evandromb\fvm\versions\stable\packages\flutter\lib\src\scheduler\binding.dart:865)
Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:18)
_Timer._runTimers (dart:isolate-patch/timer_impl.dart:395)
_Timer._handleMessage (dart:isolate-patch/timer_impl.dart:426)
_RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:184)

Mmm, I'm not sure how VSCode exceptions work but the thing is that having this exception is expected at the line of the error.
Actually this exception is called and expected. Not having this exception is an issue ^^
Anyway it might seems counter intuitive but it's just a check to be sure that you don't setup multiple VRouterScopes.
I would be glad to know if you think this is normal that you saw this error concidering that it was handled within a try catch bloc.
Appart from that I would say having this issue is normal and actually a good thing 😉

Well, I think it's fine since it doesn't stop the app from running either freeze it. My main concern was just due to the error message telling me that it might be a bug.
Again thanks for such great support!

I'm getting this too.  Is there a work around?  Hard to debug with exceptions on with this constantly crashing.

@sgehrman are you using VRouter or VRouterDelegate ?

authors: evandrmb lulupointu sgehrman

repo: lulupointu/vrouter