Can't start jekyll server locally

I forked the project and github page looks fine. But when i run bundle exec jekyll serve, I got an error like this:
Liquid Exception: SyntaxError: Expected identifier, string or number in /_layouts/Post.html
Traceback (most recent call last):
        96: from D:/Ruby27-x64/bin/jekyll:23:in `<main>'
        95: from D:/Ruby27-x64/bin/jekyll:23:in `load'
        94: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/exe/jekyll:15:in `<top (required)>'
        93: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        92: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        91: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        90: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        89: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        88: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
        87: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `process_with_graceful_fail'
        86: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `each'
        85: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `block in process_with_graceful_fail'
        84: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/commands/build.rb:36:in `process'
        83: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/commands/build.rb:65:in `build'
        82: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:28:in `process_site'
        81: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:76:in `process'
        80: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:201:in `render'
        79: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:507:in `render_docs'
        78: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:507:in `each_value'
        77: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:508:in `block in render_docs'
        76: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:508:in `each'
        75: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:509:in `block (2 levels) in render_docs'
        74: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:523:in `render_regenerated'
        73: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:63:in `run'
        72: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:89:in `render_document'
        71: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:159:in `place_in_layouts'
        70: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:196:in `render_layout'
        69: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:127:in `render_liquid'
        68: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:36:in `render!'
        67: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:70:in `measure_time'
        66: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:37:in `block in render!'
        65: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:63:in `measure_bytes'
        64: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:38:in `block (2 levels) in render!'
        63: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:59:in `measure_counts'
        62: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:39:in `block (3 levels) in render!'
        61: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:220:in `render!'
        60: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:207:in `render'
        59: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:242:in `with_profiling'
        58: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:208:in `block in render'
        57: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
        56: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
        55: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:43:in `render'
        54: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
        53: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `block in render'
        52: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `each'
        51: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:46:in `block (2 levels) in render'
        50: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:91:in `render'
        49: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
        48: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/tags/include.rb:122:in `render'
        47: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
        46: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/tags/include.rb:125:in `block in render'
        45: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:36:in `render!'
        44: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:70:in `measure_time'
        43: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:37:in `block in render!'
        42: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:63:in `measure_bytes'
        41: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:38:in `block (2 levels) in render!'
        40: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:59:in `measure_counts'
        39: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:39:in `block (3 levels) in render!'
        38: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:220:in `render!'
        37: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:207:in `render'
        36: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:242:in `with_profiling'
        35: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:208:in `block in render'
        34: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
        33: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
        32: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:43:in `render'
        31: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
        30: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `block in render'
        29: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `each'
        28: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:46:in `block (2 levels) in render'
        27: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
        26: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
        25: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:79:in `render'
        24: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:150:in `render_segment'
        23: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
        22: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:158:in `block in render_segment'
        21: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:158:in `each'
        20: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:160:in `block (2 levels) in render_segment'
        19: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
        18: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
        17: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:43:in `render'
        16: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
        15: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `block in render'
        14: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `each'
        13: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:46:in `block (2 levels) in render'
        12: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:91:in `render'
        11: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
        10: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/assign.rb:26:in `render'
         9: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:82:in `render'
         8: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:82:in `inject'
         7: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:82:in `each'
         6: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:84:in `block in render'
         5: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:86:in `invoke'
         4: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/strainer.rb:56:in `invoke'
         3: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/filters.rb:19:in `markdownify'
         2: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/converters/markdown.rb:85:in `convert'
         1: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/cache.rb:109:in `getset'
D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/cache.rb:88:in `[]': unhandled exception
        120: from D:/Ruby27-x64/bin/jekyll:23:in `<main>'
        119: from D:/Ruby27-x64/bin/jekyll:23:in `load'
        118: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/exe/jekyll:15:in `<top (required)>'
        117: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        116: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        115: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        114: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        113: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        112: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
        111: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `process_with_graceful_fail'
        110: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `each'
        109: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `block in process_with_graceful_fail'
        108: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/commands/build.rb:36:in `process'
        107: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/commands/build.rb:65:in `build'
        106: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:28:in `process_site'
        105: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:76:in `process'
        104: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:201:in `render'
        103: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:507:in `render_docs'
        102: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:507:in `each_value'
        101: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:508:in `block in render_docs'
        100: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:508:in `each'
         99: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:509:in `block (2 levels) in render_docs'
         98: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:523:in `render_regenerated'
         97: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:63:in `run'
         96: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:89:in `render_document'
         95: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:159:in `place_in_layouts'
         94: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:196:in `render_layout'
         93: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/renderer.rb:127:in `render_liquid'
         92: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:36:in `render!'
         91: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:70:in `measure_time'
         90: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:37:in `block in render!'
         89: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:63:in `measure_bytes'
         88: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:38:in `block (2 levels) in render!'
         87: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:59:in `measure_counts'
         86: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:39:in `block (3 levels) in render!'
         85: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:220:in `render!'
         84: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:207:in `render'
         83: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:242:in `with_profiling'
         82: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:208:in `block in render'
         81: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
         80: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         79: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:43:in `render'
         78: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
         77: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `block in render'
         76: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `each'
         75: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:46:in `block (2 levels) in render'
         74: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:91:in `render'
         73: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         72: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/tags/include.rb:122:in `render'
         71: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
         70: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/tags/include.rb:125:in `block in render'
         69: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:36:in `render!'
         68: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:70:in `measure_time'
         67: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:37:in `block in render!'
         66: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:63:in `measure_bytes'
         65: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:38:in `block (2 levels) in render!'
         64: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:59:in `measure_counts'
         63: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/liquid_renderer/file.rb:39:in `block (3 levels) in render!'
         62: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:220:in `render!'
         61: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:207:in `render'
         60: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:242:in `with_profiling'
         59: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:208:in `block in render'
         58: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
         57: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         56: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:43:in `render'
         55: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
         54: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `block in render'
         53: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `each'
         52: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:46:in `block (2 levels) in render'
         51: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
         50: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         49: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:79:in `render'
         48: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:150:in `render_segment'
         47: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
         46: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:158:in `block in render_segment'
         45: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:158:in `each'
         44: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/for.rb:160:in `block (2 levels) in render_segment'
         43: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:82:in `render'
         42: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         41: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:43:in `render'
         40: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:123:in `stack'
         39: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `block in render'
         38: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:44:in `each'
         37: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/if.rb:46:in `block (2 levels) in render'
         36: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:91:in `render'
         35: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         34: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/tags/assign.rb:26:in `render'
         33: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:82:in `render'
         32: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:82:in `inject'
         31: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:82:in `each'
         30: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/variable.rb:84:in `block in render'
         29: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/context.rb:86:in `invoke'
         28: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/liquid-4.0.3/lib/liquid/strainer.rb:56:in `invoke'
         27: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/filters.rb:19:in `markdownify'
         26: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/converters/markdown.rb:85:in `convert'
         25: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/cache.rb:108:in `getset'
         24: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/cache.rb:111:in `rescue in getset'
         23: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/converters/markdown.rb:86:in `block in convert'
         22: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/jekyll-4.0.1/lib/jekyll/converters/markdown/kramdown_parser.rb:41:in `convert'
         21: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/document.rb:116:in `method_missing'
         20: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/base.rb:107:in `convert'
         19: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:58:in `convert'
         18: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:373:in `convert_root'
         17: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:70:in `inner'
         16: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:70:in `each'
         15: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:71:in `block in inner'
         14: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:93:in `convert_p'
         13: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:70:in `inner'
         12: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:70:in `each'
         11: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:71:in `block in inner'
         10: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/html.rb:352:in `convert_math'
          9: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-2.3.1/lib/kramdown/converter/base.rb:211:in `format_math'
          8: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/kramdown-math-katex-1.0.1/lib/kramdown/converter/math_engine/katex.rb:22:in `call'
          7: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/katex-0.8.0/lib/katex.rb:32:in `render'
          6: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/katex-0.8.0/lib/katex.rb:55:in `katex_context'
          5: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/katex-0.8.0/lib/katex.rb:55:in `synchronize'
          4: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/katex-0.8.0/lib/katex.rb:56:in `block in katex_context'
          3: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/execjs-2.8.1/lib/execjs/runtime.rb:72:in `compile'
          2: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/execjs-2.8.1/lib/execjs/runtime.rb:72:in `new'
          1: from D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/execjs-2.8.1/lib/execjs/external_runtime.rb:14:in `initialize'
D:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/execjs-2.8.1/lib/execjs/external_runtime.rb:39:in `exec': SyntaxError: Expected identifier, string or number (ExecJS::RuntimeError)

It looks like the Liquid version issue.  I am not sure, I will check and update.

I disabled math_engine in _config and it works. Dont know why.

I tried to disable math_engine in _config.yml and it did work. I don't know why either. 😂


How to set the number of epoch when training my model?

I have used
sh experiments/mot17_test.sh
to train my own model. And I can set the batch size. Because of the limitation of GPU performance, I changed it from 32 into 4. But I cannot see where to set the number of epoch. BTW, the notification said the program have to go through 140 epochs. I got the noti by running the command.

In opts.py

Thanks bro


Err: command nnexport not found

Hi, there.
When I try to set the TEACHERS_PET_GITHUB_TOKEN, running source ~./bash_profile, I hit a snag: nnexport: command not found
Could you tell me why? Thanks very much.
Warmly,
Leo

My guess is that you have a type in your ~/.bash_profile...nnexport instead of export. Feel free to reopen if that's not the case!

Below is the content of ~/.bash_profile(token has been changed):
\n\nexport TEACHERS_PET_GITHUB=b80lj3b4276943d2a9d2e10a8247654sjmfe0ec1babjh
So, could you please help me correct it?

What operating system are you running? Mind running the following and pasting the output here?
printf "foo\n\nbar\n"

I think echo doesn't interpret \ns the same on all *-nix operating systems. Anyway, just remove the two \n\n's at the beginning, run source ~/.bash_profile, and you should be good to go.

So it's been guaranteed that an other err I met has nothing to do with this issue now. Thanks.


Add merge helper

Adds orbit/lib/objects#merge helper for merging objects
e.g.
test("`merge` combines two objects", function() {
  var a = { firstNames: 'Bob'},
      b = { lastName: 'Dobbs', 'title': 'Mr.'},
      expected = { title: 'Mr.', firstNames: 'Bob', lastName: 'Dobbs'};
  deepEqual(merge(a, b), expected, 'Object values are not merged');
  deepEqual(a, { firstNames: 'Bob' }, 'Original object mutated');
});

This was based on the version in the schema. We should have checked the implementation to see if it matched up with the behaviour of a generic merge. Will change the behaviour later on today.

Fixed the false case. Thanks for pointing it out.

I'd probably expect merge to keep all keys regardless of their values, @dgeb what do you think?

Yeah, let's just keep all keys regardless of their values. Clearing keys that have undefined values should be done as a second step or perhaps by passing an option to merge.

Ok, simplified to keep all keys.

Thanks @opsb and @walter :+1:


why the "WindowsPerformanceCounter.config" reading every 10 sec?

Hi.
i am checked the "CollectdWin_debug.log"
The following information was in the "CollectdWin_debug.log".
2016-06-23 01:33:58.2302|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:34:08.2323|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:34:18.2364|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:34:28.2385|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:34:38.2406|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:34:48.2426|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:34:58.2447|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:35:08.2488|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration 2016-06-23 01:35:18.2509|INFO|BloombergFLP.CollectdWin.WindowsPerformanceCounterPlugin: WindowsPerformanceCounter reloading configuration
i can't understand the "WindowsPerformanceCounter.config" reading every 10 sec.
i've setting this.

Please help me.

See: https://github.com/bloomberg/collectdwin/pull/17

@pall-valmundsson
sorry. My question was wrong.
i'am setting Interval to WindowsPerformanceCeounter.conf.
it is value 900.
<WindowsPerformanceCounter>   <RefreshInstancesConfiguration Enable="false" Interval="900" />   <Counters>
but reloading WindowsPerformanceCounter every 10 sec.


Idempotent print issue: On shebang in source file

#!/usr/bin/env who
class Foo

The shebang exists as the first child of a file if it is present. On G.CompilationUnit, it is represented as a nullable String, which seems correct since it is not a comment and MUST be declared at the top of the file.
Unfortunately, whitespace is overly complex and would take time to fix and/or understand. I'm assigning this to @kunli2  since he has context to all the whitespace methods. Adding the shebang to the K.CU is simple, but it causes a idempotent print issue since the new line after the shebang is not preserved in the prefix of the class declaration.


Adding VPC config option to readme

Here's the README portion of https://github.com/Miserlou/django-zappa/pull/10

I've added you as a contributor - feel free to add changes you think are good (if they have tests) at will!

OK, thanks!


Bug report task query is throwing parsing error

What happened?
```dataview
TASK

throws:
Dataview: Error:
-- PARSING FAILED --------------------------------------------------

Got the end of the input

Expected:

TABLE or LIST or TASK or CALENDAR

DQL
TASK

JS
No response
Dataview Version
0.5.55
Obsidian Version
1.4.14
OS
Windows

Ay yeah this was some query parsing error. Do you want to try fixing it? It shouldn't be too obtuse but some prior experience in programming would be beneficial.

sure, @AB1908 , will take a stab at it, is there a developer guide on how to setup the repo locally and connect with obsidian application

Yes, it should be in the readme. Let me know if you need assistance.


Update to use diff functionality

FYI https://www.infracost.io/docs/integrations/ uses the screenshots from CI repos, we can copy the updated ones to the docs repo if we want avoid linking them


feat(addon-commerce): add flexible payment system detection

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Closes #2755
Does this PR introduce a breaking change?

[ ] Yes
[x] No

PR Goals

Move all payment system detection logic to one function
Introduce no breaking changes
Keep detection performant & allocation free (by not using strings and array methods, as i first intended in #2755)

What may be done after by PR

Remove functions tuiIsElectron, tuiIsMir, tuiIsVisa, tuiIsMastercard, tuiIsMaestro. I have not touched them, because they are exported

Please add new words to ignore.json


⚠ Account has degraded performance

In e4eb7ad, Account (https://account.wrk.com/health) experienced degraded performance:

HTTP code: 200
Response time: 178 ms

Resolved: Account performance has improved in 3d2b947.


Add days to possession countdown

Add a coundown column which computes the days remaining to possession for each project.

See commit af08114


Rc single context refactor

aferritto created the following on Apr 07:
Closes #91
Cleans up the handling of single context (dociument) vs multi context (e.g. from ir)
TODO:

[x] Fix Tests
[x] Re-run pipeline to test after merging in rc-framework

Original issue: https://github.ibm.com/ai-foundation/PrimeQA/pull/100

On Apr 12, aferritto commented:
Example command:
jbsub -q x86_24h -cores 20+1 -mem 30g -require 'a100_80gb' -proj 'oneqa' -name 'merge-test' \
 /dccstor/aferritt2/miniconda3/envs/oneqa/bin/python examples/mrc/run_mrc.py \
--model_name_or_path xlm-roberta-large \
 --output_dir /dccstor/aferritt3/oneqa/test-model-large-single-context-refactor-merge --fp16 \
 --learning_rate 4e-5 --do_train --do_eval --per_device_train_batch_size 32 --per_device_eval_batch_size 128 \
--gradient_accumulation_steps 2 --warmup_ratio 0.1 --weight_decay 0.1 --save_steps 50000 \
 --overwrite_output_dir --num_train_epochs 1 --evaluation_strategy no

On Apr 11, aferritto commented:
I've tweaked the args a bit: removing ones we are not using currently and adding ones we are.

On Apr 13, aferritto commented:
*** Macro Over 10 Languages, excluding English **
Passage F1:0.725 P:0.759 R:0.696731
\fpr{72.5}{75.9}{69.7}
Minimal F1:0.676 P:0.732 R:0.632926
\fpr{67.6}{73.2}{63.3}
Consistent with https://ibm-research.slack.com/archives/C02R5676R1D/p1649274072992739?thread_ts=1649251564.855669&cid=C02R5676R1D (67.6/72.5)
Merging

PR merged


Add ADR for moving to Trunk Based Development

Changes
Introduce an ADR for moving to Trunk Based Development.
Checklist

[x] Attach this pull request to the appropriate card in Trello.
[x] Update the CHANGELOG.md if needed.

@mec I've created a card at https://trello.com/c/inU274VS/364-migrate-to-trunk-based-development to track this.


Feature Request - LTS version update notifications

Summary of the new feature/enhancement
As a user of the LTS version, I'd like to see the version update notifications for the LTS version only.
When I'm using the latest LTS version, I don't want to be reminded about the latest non-LTS version.
But if there is a newer LTS version, I do want to be reminded.
PowerShell 7.0.5
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/powershell
Type 'help' to get help.

   A new PowerShell stable release is available: v7.1.2
   Upgrade now, or check out the release page at:
     https://aka.ms/PowerShell-Release?tag=v7.1.2

Proposed technical implementation details (optional)
The LTS version should check if it is running the latest LTS version or not, and ignore the non-LTS versions.

You can achieve that by setting the environment variable POWERSHELL_UPDATECHECK. See https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_update_notifications?view=powershell-7.1#long-description for details.

Hi @daxian-dbw, I don't want to say that the link you provided doesn't work, because it does. However, having a single - shared - environment variable is a limitation when people are using multiple PowerShell releases at the same time.
Should I update the original issue and say the different releases should check for updates to their release?
I didn't consider preview releases before, but now I realize that those who are using three different releases, might want to get notified about the matching release.

This just came up again:

#20210


Add dist file to repo and auto build on commit

Connects to #55
change-type: patch

Why checkin in dist?

I'd like to make our build process transparent, and we now have the tooling to ensure the artefacts are built correctly. I think we can easily exclude the stories directory from the dist output.

Hmm, I disagree quite strongly especially now that we have pre-commit hook, it'll make pr's twice as noisy with little benefit, but let's see how it feels and remove later if we like.

@craig-mulligan I'm happy to discuss it further. We could use the travis values skip_cleanup and after_success to build and publish the files on Travis.
Our after_success  entry would look something like this
after_success:
  if ([ "$TRAVIS_BRANCH" == "master" ] || [ ! -z "$TRAVIS_TAG" ]) &&
      [ "$TRAVIS_PULL_REQUEST" == "false" ]; then
    npm run build
  fi

@LucianBuzzo, Yep that'd be rad :) I'd put that script in the main travis script section because if the npm build fails it'll still run the other after_success scripts.


coverage: ensure that "coverage clean" does its job

removed parameters from "coverage run" as they should be read from the .coveragerc file.
"coverage clean" now can see "coverage run" is being executed in parallel mode and can now clean the artifacts properly.
tox:testenv:coverage now runs "coverage clean" after the coverage report generation.
Supersedes #871

We should also find a way to capture the interrupt signal and call the 'coverage clean'.

We should also find a way to capture the interrupt signal and call the 'coverage clean'.

This is done.

Now added the optional '-coverage' to py3 so we're now able to skip coverage related stuff on py3 env run.

So I've made a few significant changes:

Coverage now writes its intermediate files to the tox's temp directory, so no tidying would be necessary (removed the bash interrupt handler thingy)
Moved .coveragerc contents to tox.ini
Renamed tox "coverage" env to "coveragereport"

I think the patch is now much cleaner.

nice cleanups in the final stage! lgtm!


Update examples.hbs

Updated the example handlebars template wording for spelling typos and syntax

Thanks, I can't believe there were mistakes like these in the examples ;)


Set GitHub Workflow permissions to read only

Hi I'm from Google and I'm working with the OpenSSF to improve supply chain security of many open source projects by following OpenSSF Scorecard checks.
I would like to suggest a simple but important supply chain good practice which is to always use minimally scoped permissions because the default of GITHUB_TOKEN is write-all.
This way, even in a case of a compromised workflow, the attacker won't be able to do much.
Let me know if that's ok for me to submit a PR with this change and I'll do it ASAP.

That's ok for you to do 👍


WIP Store Refactor w/o Proto Changes

Putting this PR into a holding pattern. Switching to improving keeper test coverage.


NotADirectoryError while trainling neuralcoref on a new dataset

I am following the documentation to train the neuralcoref system on my own dataset. I have my dataset in CoNLL format and when I run the script python -m neuralcoref.conllparser --path path-to-my-dataset, I have the following error. Any suggestion please?
Traceback (most recent call last):
File "/opt/python/3.6.3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/opt/python/3.6.3/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/neha5486/git/neuralcoref/neuralcoref/conllparser.py", line 702, in
os.makedirs(SAVE_DIR)
File "/opt/python/3.6.3/lib/python3.6/os.py", line 220, in makedirs
mkdir(name, mode)
NotADirectoryError: [Errno 20] Not a directory: '/scratch/Shares/hunter/ontonotes/train.english.v4_gold_conll/numpy/'

Hi @negacy, the path to your dataset is probably wrong.
It should just be the path to the folder containing your data, not to the file itself (the parser will create a directory inside this data folder to host the numpy arrays created after parsing the files)

Right, the problem was with the path. Thanks. Negacy.

Hi @negacy, the path to your dataset is probably wrong.
It should just be the path to the folder containing your data, not to the file itself (the parser will create a directory inside this data folder to host the numpy arrays created after parsing the files)

Thank you soo much, you saved my life :'( @thomwolf


lora-gateway-bridge exception

Is this a bug or a feature request?
It's a bug
What did you expect?
I expected to send "mosquitto_pub -t "gateway/7276ff000b030bcd/command/down -f /tmp/test.json" to it
What happened?
The application crashed
What version are your using?
SNAPSHOT-361697b
How can your issue be reproduced?
The command "mosquitto_pub -t "gateway/7276ff000b030bcd/command/down -f /tmp/test.json" creates the same issue anytime i try. Json contains : {"confirmed" : false, "fport" : 2, "data" :"AQID"}
Could you share your log output?

This is an untagged version. I have looked into the line causing the exception (txInfo is nil), but I don't think this line is present in the latest tagged version.


fix the bug when the page index is bigger than the subview count

If a user is at the last page, and try to scroll all the way to the left, then the app will crash. It is because in the getCurrentDisplayedPage method, the page index can be bigger than the subview count, thus causing crash. Fixed by checking the page number before incrementing it.

Good catch! Thanks for reporting it and also fixing it!
Tom


How can I return a Stream from a chained query?

I come from a NoSQL background so I am very much a SQL noob.  It is possible my design/thought process is totally wrong but maybe somebody can help to point me in the right direction.
I have a Parent table and a Child table.  A Parent can have multiple Children but a Child can only have one Parent. I have my tables defined like so (for example):
class Parents extends Table {
  IntColumn get id => integer().autoIncrement()();
  TextColumn get name => text()();
  BoolColumn get active => boolean()();
}

class Children extends Table {
  IntColumn get id => integer().autoIncrement()();
  TextColumn get name => text()();
  IntColumn get parentId => integer().nullable().customConstraint('NULLABLE REFERENCES parents(id)')();
}

The problem comes when I want to get a Stream<List>.  I need to query for the id of the active parent and then query for the children using that id.  I had no problems doing that to add a new child, but  I can't figure out what I need to do to for the query.
  Future<Parent> get activeParent {
    return (select(parents)
          ..where((c) => c.active)
          ..limit(1))
        .getSingle();
  }

  Future addChild(String name) {
    return transaction(() async {
      var parent = await activeParent;
      await into(notes).insert(ChildrenCompanion(
          name: Value(name), parentId: Value(parent.id)));
    });
  }

  //this obviously does not work and is wrong
  Stream<List<Child>> get currentChildren {
    transaction(() async {
      var parent = await activeParent;
      return (select(children)..where((n) => n.parentId.equals(parent.id))).watch();
    });
  }

I am too much of an SQL noob to know if my approach is totally wrong, or if I just don't know the syntax for what I am trying to do.  Any guidance is very appreciated!

Logically, you'll want to select all children whose parent is active at the moment. In SQL, you could include the parent with a join and then check whether the parent is active or not:
SELECT children.* FROM children
  INNER JOIN parents ON children.parentId = parents.id
WHERE parents.active

In moor, you could write that query like this:
Stream<List<Child>> get currentChildren {
  final query = select(children).join([innerJoin(parents, parents.id.equalsExp(children.id), useColumns: false)]);
  query.where(parents.active);

  return query.map((row) => row.readTable(children)).watch();
}

The useColumns: false tells moor not to include the parent table in the results, since it's only needed for the where clause.

Thanks so much! I thought I needed an inner join, but kept getting stuck on the fact that I didn't need anything from the parents table in the result.  I really appreciate the quick help.


fix: Compute Motoko dependencies in linear (not exponential) time by detecting visited imports

Description
DFX invokes moc --print-deps on each canister source file to discover immediate dependencies on source files, motoko packages and canisters and then requires dfx to do a full transitive closure to discover canister dependencies.
Unfortunately, a series of cumulative imports will lead to exponential behaviour as moc --print-deps is re-invoked on the same file multiple times.
Fixes SDK-749.
How Has This Been Tested?
Manually tested against repro https://github.com/luc-blaeser/dfx-long-building, reducing compile times of a trivial project from an unreasonable 12s to 0.5.s. Dependencies tracing times of >2mins (!) have been observed in the wild. Hopefully this fixes that.
BEFORE:
crusso@vm:~/dfx-long-building$ time dfx -vvvv build
Trace mode enabled. Lots of logs coming up.
Building canisters...
No canister of type 'rust' found. Not trying to run 'cargo audit'.
Running "/home/crusso/.cache/dfinity/versions/0.11.2/moc" "/home/crusso/dfx-long-building/src/test.mo" "-o" "/home/crusso/dfx-long-building/.dfx/local/canisters/test/test.wasm" "-c" "--debug" "--idl" "--stable-types" "--public-metadata" "candid:service" "--actor-idl" "/home/crusso/dfx-long-building/.dfx/local/canisters/idl/" "--actor-alias" "test" "rrkah-fqaaa-aaaaa-aaaaq-cai" "--package" "base" "/home/crusso/.cache/dfinity/versions/0.11.2/base"...

real	0m12.765s
user	0m8.860s
sys	0m4.094s

AFTER
crusso@vm:~/dfx-long-building$ time ../sdk/target/debug/dfx -vvvv build
Trace mode enabled. Lots of logs coming up.
Building canisters...
No canister of type 'rust' found. Not trying to run 'cargo audit'.
Running "/home/crusso/.cache/dfinity/versions/0.12.0-beta.3+rev4.dirty-06a1debc/moc" "/home/crusso/dfx-long-building/src/test.mo" "-o" "/home/crusso/dfx-long-building/.dfx/local/canisters/test/test.wasm" "-c" "--debug" "--idl" "--stable-types" "--public-metadata" "candid:service" "--actor-idl" "/home/crusso/dfx-long-building/.dfx/local/canisters/idl/" "--actor-alias" "test" "rrkah-fqaaa-aaaaa-aaaaq-cai" "--package" "base" "/home/crusso/.cache/dfinity/versions/0.12.0-beta.3+rev4.dirty-06a1debc/base"...
Shrink WASM module size.

real	0m0.533s
user	0m0.494s
sys	0m0.040s

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Checklist:

[x] The title of this PR complies with Conventional Commits.
[x] I have edited the CHANGELOG accordingly.
[x] I have made corresponding changes to the documentation.

@chenyan-dfinity any idea why dfx compiles each moc canister twice? Once it has an ordering, I think it should be enough to just compile each canister once,  in order.

any idea why dfx compiles each moc canister twice?

It used to twice, because we need to produce did file and wasm. Now that moc produces them at the same time, I think it only compiles once?

any idea why dfx compiles each moc canister twice?

It used to be twice, because we need to produce did file and wasm. Now that moc produces them at the same time, I think it only compiles once?

Actually, I think you are right. I was just misreading the long log with -vvvv

This will also have fixed https://dfinity.atlassian.net/browse/SDK-665.  Thanks!


Upgrade to Mapbox GL

Investigate an upgrade to Mapbox GL JS, and if an upgrade seems like a good fit, add in the following Mapbox basemaps:

Streets (style url: mapbox://styles/mapbox/streets-v9)
Satellite (style url: mapbox://styles/mapbox/satellite-v9)
Satellite Streets (style url: mapbox://styles/mapbox/satellite-streets-v9)

Note: Your personal access token is needed to add any of the features above into the map.

Not a bad learning opportunity. If you haven't read this yet, consider it as part of the investigation: http://fuzzytolerance.info/blog/2016/03/16/Leaflet-to-Mapbox-GL/


Error event should include response object

When error is emitted, the res object has already been fulfilled and ended. The error event should include the res object so that it can be included in logs, or otherwise acted upon.

@bahamat  I notice that our response body will just be the error, wrapped in reasonable HTTP semantics):
res.writeHead(400, { 'content-type': 'application/json' })
res.end(JSON.stringify({ error: msg }))

var err = new Error(msg)
// ...

Rather than explicitly emitting res, could downstream projects get by with the assumption that res will always be a "bad request" containing the error message?

I have two questions.

Is this a guarantee that it will never change?
Will something break if it's included? When logging (or whatever) I'd prefer to pass through what the actual error code was rather than making one up on my own.

Is this a guarantee that it will never change?

Insofar as it's covered in the spec (and semantically appropriate). In theory we'd bump version in response to a breaking change in the spec, as well, though there's (unfortunately) no hard guarantee on that.

Will something break if it's included?

I don't think so, as we would only be expanding the interface, but we would want to be sure we weren't inadvertently setting ourselves up for future trouble (e.g., by ensuring that only finalized res objects are being emitted, etc).
If we can get by with the current behavior (or a specific "webhook error" log entry as needed), great; if there are cases where we need direct access to res this is a small enough library that validation shouldn't be a huge issue either. Thoughts?

I looked back through the code I was using for this, and to be quite honest, it was so long ago that I worked on this that I don't really remember exactly what I was going to use it for. I thought I knew, but after some review...it's at least not obvious. In any event, I'm unlikely to go back into my code at any time soon and make use of the res object even if it were there.
I'm ok with closing both the issue and the PR as unnecessary at this time.

Got it, and big thanks for checking back into this!


added shimmer effect in homefragment

Issue Resolved
fixes #169
Screenshots
https://user-images.githubusercontent.com/66007619/222669670-3d450df8-b312-4a27-b866-95d26e6f3274.mp4
Checklist
Please make sure to review the following before submitting your PR:

[x] I have read the contribution guidelines.
[x] I have read the code of conduct.
[x] I have reviewed my submission in detail.

Lgtm, why draft pr though

i just added that to top movie top tv and popular movie, last three are left should i skip them?


Support DNS?

Supoort DNS or only IP ?
i build whit dns and not have conection

yes it supports dns


[5.3] Request add a non form field

Laravel Version: 5.3.29
PHP Version: 7.0 / 7.1.0
Database Driver & Version: mariaDB 10.0.24

Description:
I just change the hosting provider where the app was running without any issue (PHP 5.6) and I noticed that sending a POST request with:
$('form#queryForm').serialize()
"from=express&user_id=wzJ6v357mE23&exam=&last_vaccine=23%2F06%2F2016&last_desp=&appealling=1&dieta=&temp=&pv=&fc=&fr=&mucosas=&mental=&remarks="

the request()->all() has and additional field q
array:15 [
  "from" => "express"
  "user_id" => "wzJ6v357mE23"
  "exam" => ""
  "last_vaccine" => "23/06/2016"
  "last_desp" => ""
  "appealling" => "1"
  "dieta" => ""
  "temp" => ""
  "pv" => ""
  "fc" => ""
  "fr" => ""
  "mucosas" => ""
  "mental" => ""
  "remarks" => ""
  "q" => "/histories/storeExpress/y2X8YpoN7woL"
]

Any clue?

Sorry but please ask questions on the forum, I'm sure someone will help you there. We keep this repo for bug reporting only :)

Thanks for you attention, and sorry I thought  it 'may be' was a bug. Going to forums.

@themsaid I posted the issue on forums without any response, so:
I dig down til Illuminate/Foundation/Http/Kernel.php, in line 129 and event is fired, so the listener:
public function handle($request)
{
    if (auth()->check() && auth()->user()->id == 1) {
        dd([
            'request' => $request->all(),
            'POST' => $_POST
        ]);
    }
}

The dd output:
array:2 [▼
  "request" => array:1 [▼
    "q" => "/users/gB57NM03eoDw/colors"
  ]
  "POST" => []
]

Have compassion on me and give me a clue where to go

@themsaid if I put var_dump($_GET); at the top of public/index.php I got:
array(1) { ["q"]=> string(26) "/users/gB57NM03eoDw/colors" }

So is a php issue, for sure in some config. I'll research this.
Thank you.

Finally a nginx misconfiguration


ModuleNotFoundError: No module named 'descriptastorus'

I installed the environment through environment.yml, and after successful installation, I ran Drug Properties Prediction with an error message as follows:

Traceback (most recent call last):
File "/mnt/sdb1/yinxiaoru/AIDD/project/ADMET/project/DeepPurpose-master/DeepPurpose/utils.py", line 15, in
from descriptastorus.descriptors import rdDescriptors, rdNormalizedDescriptors
ModuleNotFoundError: No module named 'descriptastorus'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "run_admet.py", line 4, in
from DeepPurpose import CompoundPred as models
File "/mnt/sdb1/yinxiaoru/AIDD/project/ADMET/project/DeepPurpose-master/DeepPurpose/CompoundPred.py", line 24, in
from DeepPurpose.utils import
File "/mnt/sdb1/yinxiaoru/AIDD/project/ADMET/project/DeepPurpose-master/DeepPurpose/utils.py", line 17, in
raise ImportError("Please install pip install git+https://github.com/bp-kelley/descriptastorus and pip install pandas-flavor")
ImportError: Please install pip install git+https://github.com/bp-kelley/descriptastorus and pip install pandas-flavor

Prompt for installing descriptastrorus and pandas flavor. An error occurred while installing descriptastrorus, with the following error message:
pip install git+https://github.com/bp-kelley/descriptastorus

Looking in indexes: http://pypi.douban.com/simple/, https://pypi.ngc.nvidia.com
Collecting git+https://github.com/bp-kelley/descriptastorus
Cloning https://github.com/bp-kelley/descriptastorus to /mnt/sdb1/yinxiaoru/.temp_dir/pip-req-build-q1ez9ilq
Running command git clone --filter=blob:none --quiet https://github.com/bp-kelley/descriptastorus /mnt/sdb1/yinxiaoru/.temp_dir/pip-req-build-q1ez9ilq
fatal: unable to access 'https://github.com/bp-kelley/descriptastorus/': Empty reply from server
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'
error: subprocess-exited-with-error
× git clone --filter=blob:none --quiet https://github.com/bp-kelley/descriptastorus /mnt/sdb1/yinxiaoru/.temp_dir/pip-req-build-q1ez9ilq did not run successfully.
│ exit code: 128
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× git clone --filter=blob:none --quiet https://github.com/bp-kelley/descriptastorus /mnt/sdb1/yinxiaoru/.temp_dir/pip-req-build-q1ez9ilq did not run successfully.
│ exit code: 128
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

Have you directly tried pip install git+https://github.com/bp-kelley/descriptastorus.  Otherwise, I think you could try dufferent python env (python 3.10 / python 3.9) to solve this problem.


Stop making sensitive kafka information available for logging

The adapter currently logs the kafka message directly to the console
instead; log metadata such as partition, topic, offset instead
The receive adapter is currently even worse due to the zap logging
done by reflection.  This prints out every struct parameter including
user/password combo.  Drop that and log less sensitive metadata.
Fixes #328
Proposed Changes

Alter receive_adapter to print out a predefined set of field instead of reflecting the entire adapter struct
Change the adapter itself to log metadata only (partition, topic, offset)
Update the README to match the updated output

/ok-to-test

@evankanderson @grantr given that the current IMPL logs sensible data, I'd recommend getting this into 0.5  branch/tag

/lgtm

/lgtm

/retest

/retest

/retest


Rename output_options param dictionary to asset_upload_options

The output_options field in the process definition has caused some confusion. Improved docs will help of course, but it's a rather ambiguous name.  It can be more explicit, these are the options that are passed to the upload_item_assets function in cirrus-lib, so a better name would be asset_upload_options or even just upload_options.
The process lambda can check, update the key, and print a deprecation warning.

Should the payload be "upgraded" to use the new version? Probably, in case you need to rerun a saved payload in the future and the old support has been removed.
upload_options is the preferred name here.


[objc] Fix issues found while working on issue #176

Spinoff of PR #251 [1], which goal is postponed for a bit, to fix issues
found while implementing support for mscorlib types.

mono signatures for interfaces != object;

we should only generate class handles for extension types part of the
current assembly;

if a method is final (sealed) then it's not really virtual

Sadly the original test cases cannot be applied :(
[1] https://github.com/mono/Embeddinator-4000/pull/251

Build and tests passed.


ballons: add memoryTypes to balloon types

Switched from Pattern to XValidation CEL expression for a nice error message.


YuiElementDrag should have an event for when the drag is finished

Currently you can hook into the frame by frame on_position_changed, but it's reasonable to only want to get events on the game side when the drag is over.

Fixed by 04442ab


Prevent duplicated response header insertion

What is this PR for?
Headers are inserted twice in http response message after https://github.com/apache/incubator-zeppelin/pull/831.
it prevents zeppelin-web development mode working (cd zeppelin-web; grunt serve)

This PR provides (dirty) fix for the problem. If anyone knows better way to prevent duplicated header insertion, please let me know.
What type of PR is it?
Bug Fix
Todos

[x] - Prevent duplicated header insertion

What is the Jira issue?
How should this be tested?
Check if dev mode works. ie. 'cd zeppelin-web; grunt serve', browse http://localhost:9000
or
run curl -vv http://localhost:8080/api/security/ticket and see if there're duplicated headers
Screenshots (if appropriate)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM.
is there a way to test/check for this automatically?
is there a way to prevent addCorsHeaders() getting call multiple times?

Closing this PR while #867 is better solution


Make toJSON notation configurable

Add toJSON tests
Make toJSON notation configurable

Thank you for developing big.js. We're using it to handle product prices. With prices the exponential notation is actually longer, for example the price of 0.86 became 86e-2 with big.js 6.0.0. So with using Express, res.json({price: new Big('0.86')}) used to output {price: '0.86'} and now it outputs {price: '86e-2'}.
The additional byte would not be a big deal for us, but when the values are exposed as JSON strings, the requesting end would now need to properly handle the values with exponents, and we unfortunately cannot control that.
In order to support the old normal notation with .toJSON, this PR makes it configurable.
% npm test

><EMAIL_ADDRESS>test ./big.js
> node ./test/runner.js

 Testing big.js

 Testing abs... 486 of 486 tests passed in 4 ms
 Testing cmp, eq, gt, gte, lt, lte... 23943 of 23943 tests passed in 57 ms
 Testing div... 5027 of 5027 tests passed in 509 ms
 Testing minus... 1723 of 1723 tests passed in 20 ms
 Testing mod... 1756 of 1756 tests passed in 87 ms
 Testing plus... 1845 of 1845 tests passed in 22 ms
 Testing pow... 1026 of 1026 tests passed in 124 ms
 Testing prec... 277 of 277 tests passed in 2 ms
 Testing round... 5199 of 5199 tests passed in 31 ms
 Testing sqrt... 1236 of 1236 tests passed in 173 ms
 Testing times... 2087 of 2087 tests passed in 42 ms
 Testing toExponential... 395 of 395 tests passed in 2 ms
 Testing toFixed... 941 of 941 tests passed in 4 ms
 Testing toNumber... 65 of 65 tests passed in 1 ms
 Testing toPrecision... 425 of 425 tests passed in 3 ms
 Testing toString... 1012 of 1012 tests passed in 4 ms
 Testing toJSON... 1948 of 1948 tests passed in 8 ms

 In total, 49391 of 49391 tests passed in 1.142 secs.

Your feedback has shown me that it was a mistake to change toJSON to always return exponential notation.
I considered this PR and instead decided to change toJSON to just be an alias of toString, which is the simplest way of handling the issue.
As with toString, whether or not toJSON returns exponential notation is determined by the values of Big.PE and Big.NE as previously.
Thank you for your efforts.
Fixed in v6.0.2.

Thank you, this solves our original issue well.


Migrate CI actions to latest versions

Codecov Report

Merging #43 (7844fa5) into develop (e41f355) will increase coverage by 2.72%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop      #43      +/-   ##
=============================================
+ Coverage      29.29%   32.01%   +2.72%
  Complexity        30       30
=============================================
  Files             14       14
  Lines            198      228      +30
  Branches          27       27
=============================================
+ Hits              58       73      +15
- Misses           135      150      +15
  Partials           5        5

Impacted Files
Coverage Δ

...irva/src/main/java/com/matbadev/dabirva/Dabirva.kt
87.50% <0.00%> (-0.97%)
:arrow_down:

...om/matbadev/dabirva/RecyclerViewBindingAdapters.kt
100.00% <0.00%> (ø)

...om/matbadev/dabirva/util/RecyclerViewExtensions.kt
100.00% <0.00%> (ø)

...badev/dabirva/decoration/StickyHeaderDecoration.kt
0.00% <0.00%> (ø)

...birva/decoration/VerticalStickyHeaderDecoration.kt
0.00% <0.00%> (ø)

...rva/decoration/HorizontalStickyHeaderDecoration.kt
0.00% <0.00%> (ø)

...ava/com/matbadev/dabirva/DabirvaBindingAdapters.kt
75.00% <0.00%> (+3.57%)
:arrow_up:

...java/com/matbadev/dabirva/DataBindingViewHolder.kt
75.00% <0.00%> (+5.00%)
:arrow_up:

...om/matbadev/dabirva/util/NonNullObservableField.kt
80.00% <0.00%> (+5.00%)
:arrow_up:

...rc/main/java/com/matbadev/dabirva/DabirvaConfig.kt
55.55% <0.00%> (+5.55%)
:arrow_up:

Continue to review full report at Codecov.

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


Input port callback not working

I can't get an input port to fire a callback, and I can't see how this is being supported in the code. Is it supposed to? The equivalent rtmidi code works OK.
This does not work on Windows 10, Linux 24.04, Python 13 or Python 12:
import mido
import time

innames = mido.get_input_names()

def input_callback():
    print("MESSAGE RECEIVED")

port_in = None
for n in innames:
    if n.startswith("USB"):
        port_in = mido.open_input(n, callback=input_callback)

if port_in != None:
    while True:
        time.sleep(1)

It looks like your callback function probably needs to be updated to take a single argument for the message it will receive each time it's called. From the docstring for mido.open_input:
callback=None
    A callback function to be called when a new message arrives.
    The function should take one argument (the message).
    Raises IOError if not supported by the backend.

You could quickly test with something like:
def input_callback(msg):
   print("MESSAGE RECEIVED", msg)

Thanks for your help


Simple task like adding a new module

npm install angular --save-dev
then i just try to add
import angular from 'angular'
I get cannot find module 'angular'
What is the procedure to register angular or any other module so that it is discoverable?

This sounds more like an Angular question, so you might want to follow up with them. But my guess is that, if you're using Angular 1 which doesn't include TypeScript support by default (which Angular 2 does), then you'll need to get hold of some suitable .d.ts files for the Angular 1 libraries.
This looks like a reasonable guide: https://coderwall.com/p/qsrzyq/getting-started-with-typescript-angular

You are right I have to add typings d.ts files and then Visual Studio stopped complaining. I guess Angular2 being better tricked me.


Update entity-operations-update-delete.md

Add Important note about behaviors of update statecode without statuscode

Learn Build status updates of commit d946718:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/developer/data-platform/org-service/entity-operations-update-delete.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@ericregnier
Thanks for your contributions.
This topic has a lot of important notes, so I'm not too keen on adding another.
There is some other clean-up I want to do in this topic, so I won't accept this 'as-is', but I will leave it open until I make the changes.
It is a pretty big gap that should be mentioned. Thanks for raising it.

My pleasure @JimDaly. Maybe we can restructure the important notes and create seperate sections for each "important note" part? The statecode and statusreason behavior is really important and impact can be huge so keen to have this clarified in the docs. Cheers!

@ericregnier
For this, I added a note to some common content we have about the behavior of statecode and statuscode fields.
It will appear in two places where this common content appears:

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/special-update-operation-behavior
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/entity-operations-update-delete#legacy-update-messages


Generating noises on torus-shaped coordinate.

Sorry don't know where else to ask. Can't find the solution in the Wiki and search results of issues with following keywords.

'loop'
'repeat'
'torus'

I want to a function like this issue's title.
Do someone have any idea to settable to any values with as few modifications as possible?
Although limited values(2^N*) can be configured only(, and many noise/fractal/3D functions not work),
I'm trying to implement the function written on forked repo in my repos.

^ : exponent

Please give me some advise or some comments.

I'm struggling to understand what you are referring to, could you link to one of these forked repos?

Thanks for your reply.
Here's the information of repos.
Location: private float SingleSimplex(int seed, FNLfloat x, FNLfloat y)
Commit: mars2nico/FastNoise@e4ae91c
Branch: devel
Repos: mars2nico/FastNoise
Function: OpenSimplex (2D)
Location: private float SingleOpenSimplex2(int seed, FNLfloat x, FNLfloat y, FNLfloat z)
Commit: mars2nico/FastNoise@3aa4d4c
Branch: ( same above )
Repos: ( same above )
Function: OpenSimplex (3D)

I'm coding on C#. So otherwise are not exists.
Using PreviewApp, I confirmed a visual behavior of this library.

If I understand the commit right, it implements the possibility of making periodic noise based on a period of 2^x. Periodic noise was also requested in the original FastNoise library, though the offered implementation had performance implications because it allowed arbitrary integers as periods.
I am very happy to see the overhaul of the lib and would still love to see a periodic/tiling/wrapping/repeating generating function in it.

@a-fent Thanks for your information.
I seem the implement is equals to its function what you wrote, and I understood why not implemented.
I think so(I seem modulo operation has considerable impact of performance).
I try to see the lib and search with keywords contains periodic/tiling/wrapping.

Tileable noise has been discussed before for FastNoise, the conclusion was that it's out of scope for  what FastNoise aims to provide. Adding it to existing noise functions would slow them down for regular noise generation. Adding a separate set of noise functions for it would bloat the total code size and require API changes, since not all noise types can support this type of tileable noise.
https://github.com/Auburn/FastNoise2 does support tileable 2D generation through the use of 4D noise which works on all noise types.

Duplicate of #20

#20

I see. API changes to be necessary to do it...
I'llto consider to use FastNoise2.


VSCode stuck at 'installing' phase while installing plugins.

VSCode Version: 1.6.1
OS Version: Ubuntu 16.10
I simply can't install extensions on VSCode. When I find the desired extension and click Install, the button turns slightly grayish, the text becomes "installing" and its stuck like that forever. It does not freeze or anything, it doesn't install the extension, but I am able to use VSCode fine.
Somehow it did install one extension and I don't think it was visible before restarting it. I opened VSCode to see if it is so again and I saw one of the extensions I was trying to install. The issue could be internet connection as its pretty slow but it used to work fine sometime ago - now it just doesn't. I don't know if you'll be able to reproduce this but whatever.
Steps to Reproduce:

Open a freshly installed VSCode
Go to the extensions thing on the left sidebar
Find your desired extension
Click Install
Get stuck.

Does it happen with everything you try to install? Even simple extensions such as themes?

Yes. every single extension, no matter what it is

Ok it took a good 20 mins to install an extension but it did. Does it really take this long?

No, it shouldn't. It seems you have a really slow internet connection. Where are you located by the way?
cc @modigrv

Ok it took a good 20 mins to install an extension but it did. Does it really take this long?

my internet connection is around 7mb/s (megabit). isn't that enough?

Ok now I sound very dumb but I completely reinstalled vscode (even though the one which didn't work was freshly installed) and... it works fine


Fix entity name in Policies & Conditions lists

Correct & translatable entity name in Policies & Conditions lists
Another nodeid case bug...
Control -> Policies accordion -> Compliance/Control -> any entity type with 0 policies:
Before: »No Compliance Ext Management System Policies are defined.«
After: »No »Provider« »Compliance« Policies are defined.«
Control -> Conditions accordion -> any entity type with 0 conditions:
Before: »No Container Group Conditions are defined.«
After: »No »Pod« Conditions are defined.«
Links [Optional]
Fixes #10540 - yet another manifestation of
https://bugzilla.redhat.com/show_bug.cgi?id=1359909 (master)
https://bugzilla.redhat.com/show_bug.cgi?id=1397248 (euwe)
@miq-bot add-label control, ui, bug, euwe/yes

@himdel, @mzazrivec I feel knowing the meaning and form of @sb[:folder] should not be the view's business, I'd like to refactor this to controller setting @towhat and @mode (at least for these views).
Question: where does translation belong, in controller or view?

@cben I'd rather not introduce new instance variables to be used by views if you can prevent it..
Otherwise, no opinion really :)

@cben I'd rather not introduce new instance variables to be used by views if you can prevent it..

OK, never mind then.
@miq-bot add-label blocker
per https://bugzilla.redhat.com/show_bug.cgi?id=1397248 being blocker+ for 5.7.1

Euwe backport details:
$ git log -1
commit 5b44b15f3b0fbd0f07c77d8d5dbcb5316ba94c32
Author: Milan Zázrivec<EMAIL_ADDRESS>Date:   Fri Nov 25 12:56:37 2016 +0100

    Merge pull request #12802 from cben/no-conditions

    Fix entity name in Policies & Conditions lists
    (cherry picked from commit c3aa75376639edb6dd7a542630d4dad4e7610907)

    https://bugzilla.redhat.com/show_bug.cgi?id=1397248


Chrysler: query FW versions on non-OBD bus

@realfast should be able to get VIN, but do you know if all the ecus respond on bus 0 as well?

Yes all ECUs should respond on bus 0. The only one I would question is the gateway.

Do/would we use the gateway for anything that tells us any information, ie. is it okay to lose it?

Does the gateway tell us anything about the car we care about? ie. is it okay to lose it?

I can’t think of a reason to keep it.


update codes and remove outputs for ndarray

modified a lot, see a preview at http://gluon-test.mxnet.io/P01-C02-ndarray.html

wrongly pushed my changes of linear algebra to this PR. preview at http://gluon-test.mxnet.io/P01-C03-linear-algebra.html


Automated Cost Reporting

Background

TBC
Proposed user journey

TBC
Approach

TBC
Questions / Assumptions

What does the Service Manager need?
Acceptance Criteria

TBC
Reference
How to write good user stories

Unclear user needs.


Why does Zuul Proxy no longer forward to services Eureka shows as DOWN?

My team is working to migrate from Spring Boot 1.5 to 2.1 because 1.5 will be end of life soon. We've been using a Zuul proxy with Eureka service discovery. When moving from 1.5 to 2.1 we noticed that the Zuul proxy no longer forwards requests on to services that are running but show as DOWN in Eureka. In our use case, the service reports DOWN because one of the databases it connects to is unavailable. We still want the request to go to the service, though, to process as much as it can and so that any errors are logged with that service.
I know that when you have multiple instances of a service running and one of them is down it would make sense for Zuul to ignore the DOWN service and instead forward to the UP service. In this case we may have only one service running and still want Zuul to proxy to that service.
From our observation this seems to be a behavior change from Spring Boot 1.5 to 2.1. Is there some way we can configure Zuul to still proxy to the DOWN service if it is the only instance registered with Eureka?
Also, is there any documentation you can recommend about changes in Zuul (or Eureka) from Spring Boot 1.5 to 2.1?

That's not a situation we've encountered before. You'll have to describe your setup and configuration and how to reproduce it.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.

Thank you @spencergibb  for your quick response.
We have a system of multiple microservices that communicate together using Eureka. We then have a Zuul proxy running as the entry point for external requests. The Zuul proxy will get the list of available services from Eureka for it's routes.
We've found that a service will most often report DOWN if it is not able to connect to a database or if the database driver does not have a valid health check. It seems some types of database connections will not allow the service to start up if the username is incorrect. Other types of database connections will allow the service to start and will simply show as DOWN in Eureka. You may know more about this support than I do.
To reproduce this you will need a Eureka server, an app with Eureka client that will show as DOWN, and a Zuul proxy. Start up each service and note that the app shows on the Eureka server but shows as DOWN. Then attempt to make a request to it through the Zuul proxy by using the service name. You should see Zuul report that no instances were found for that service name.

Can you show your zuul configuration?

Here are the parts of our properties file that pertain to Eureka, Zuul, Histrix, or Ribbon:
eureka.client.serviceUrl.defaultZone=[URL]
eureka.instance.nonSecurePortEnabled=false
eureka.instance.securePort=[PORT]
eureka.instance.securePortEnabled=true

hystrix.command.default.execution.timeout.enabled=false

zuul.ribbon.okhttp.enabled=true
zuul.okhttp.enabled=true

ribbon.ConnectTimeout: 4000
ribbon.MaxAutoRetries: 1
ribbon.MaxAutoRetriesNextServer: 2
ribbon.OkToRetryOnAllOperations: true
ribbon.ReadTimeout: 60000
ribbon.isSecured: true

server.port=[PORT]

zuul.retryable: true
zuul.sensitiveHeaders: NoSenstiveHeaders
zuul.sslHostnameValidationEnabled: false


Delete convd_host_weights and update all tests using conv2d

We have ops prepare_conv_weights_for_ttnn and prepare_conv_bias_for_ttnn that will pre-format convolution weights and biases for conv2d (without pushing them to device). In the previous implementation, you would pass the NHWC weights to ttnn.conv2d and ttnn.conv2d would return the formatted weights/bias on device for you to use in subsequent calls. The two aforementioned ops do this beforehand now.
TASKS

ttnn.conv2d is now pybinded to conv2d_host_weights which is the previous conv2d implementation. This needs use conv2d now
All tests that use ttnn.conv2d must use ttnn.prepare_conv_weights_for_ttnn and ttnn.prepare_conv_bias_for_ttnn to format weights/biases beforehand.

Waiting for the merge of this PR. https://github.com/tenstorrent/tt-metal/pull/14566


bug: bug: Radio buttons have broken logical and visual state on iOS9 device

Type: bug
Platform: ios 8 webview
Unpredictable / wrong behaviour of radio buttons / groups on iOS 9.
Build and run Ionic's own http://codepen.io/ionic/pen/saoBG on an iOS 9 device (iPhone). Note that it can only be reproduced on an actual device (and simulator probably).

Your system information:
Cordova CLI: 5.3.1
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.0
Ionic Version: 1.0.1
Ionic CLI Version: 1.6.4
Ionic App Lib Version: 0.3.8
ios-deploy version: 1.7.0
ios-sim version: 4.1.1
OS: Mac OS X Yosemite
Node Version: v0.12.7
Xcode version: Xcode 6.4 Build version 6E35b

Greetings @zarko-tg!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Confirmed, thanks!

Any progress with that issue? It makes nearly all my apps unusable :-(

Working on it now

Seems to be a problem with tilde combinator (~). Using plus (+) fixed the problem.

@zarko-tg could you pull down the nightly builds and give it a test please?

I would but it's weekend here already and I don't have a Mac at home (yet).
Let's see if someone else from the affected can step in in meantime.

I experienced the same issue, seems to be fixed in the nightly builds.

Checkboxes do work again, great! But there is still one thing wrong. Custom icons are not working. I am using icon="ion-ios-checkmark-outline", but it displays ion-checkmark.

@mahnuh alright, I know what that is. Give me a sec

@mahnuh do you mind pulling down the nightly builds again and trying that? Should be good now.

Works like charm! Thanks @mhartington, you are awesome!

I just tried to reproduce this on the iOS Simulator (iOS 9.0 (13A340) with Xcode 7 GM seed) and wasn't able to do so. I tried both on Safari and inside a UIWebView.
I forked the original pen and changed Ionic nightly to 1.1.0 (which still uses ~ for radio buttons): http://codepen.io/gabrielmaldi/pen/ojxveB

I know that you guys already changed ~ to +, but I wanted to know if there would be a problem with my own ~ selectors. Since I couldn't reproduce the issue, I'm assuming that Apple fixed it in some iOS 9 beta release and that now it's safe to use ~? Or maybe it just reproduces on a device and not the simulator (would be really weird)? It would be really helpful if someone could confirm that there is no longer an issue with ~ on the current release of iOS 9 by trying to reproduce the original problem.
Thanks!

@gabrielmaldi I was still able to break it in ios9 GM as well as ios 9.1 beta 1, so I think it's safe to say it is still broken.

@mhartington I'll take a deeper look into it then, thanks!

This issue was closed, but is there a fix? Stuck trying to get this working in an app right now.

Just discovered this in my Ionic app as well. Any updates? Tmp workarounds?

Yes, this has been fixed in the nighty builds. You read more here. http://blog.ionic.io/preparing-for-ios-9/

Awesome, thanks @mhartington, you guys rock!

As a quick fix, the following code did the job for me.
Thanks for a suggestion @Fpds
/**
 * There is a problem with radio buttons on iOS9
 * where Ionic's '~' combinator for radio button styles
 * doesn't work. Changing it into a '+' combinator fixes it.
 * n.b. might be fixed in later builds
 */
.item-radio input {

  &:checked + .item-content {
    background: #f7f7f7;
  }

  &:checked + .radio-icon {
    visibility: visible;
  }
}

@mhartington I am still having issues with radio buttons in iOS 9.1.  I updated to the latest Ionic master, and there was no improvement. A touch on an un-active radio doesn't select it, but a touch on an active radio selects the other un-active radio.  ng-model seems to register correctly though, so it's just the styling.

I'm experiencing the same issue as @jonalling

@TomDoesRUG I was able to use the  to make it work for now if you need a solution.
http://blog.ionic.io/preparing-for-ios-9/

Same issue here, using directive…
<ion-radio class="no-border bg-white" ng-model="$parent.model" ng-value="null" icon="icon-check-circle positive">{{ t.everything }}</ion-radio>
<ion-radio class="bg-white" ng-repeat="option in options | orderBy: 'label'" ng-model="$parent.$parent.model" ng-value="option.value" icon="icon-check-circle positive">{{ option.label }}</ion-radio>

… as with the html directly

	<input type="radio" ng-model="$parent.model" ng-value="null">

{{ t.everything }}

	<input type="radio" ng-model="$parent.$parent.model" ng-value="option.value">

{{ option.label }}

I'm running it inside the modal, works correctly with every plaftorm but fails in iOS 9.1:
when I'm tapping on a item-radio the things remains the same on the view, but if I'm scrolling the new tapped item displays that it's checked… but the old one remains checked as well; if i'm confirming the modal, data is served correctly.
Any help?

@noldotar so this is fixed in the nightly builds, but you can use a external fix until we cut a new release (hoping to do that soon)
https://gist.github.com/mlynch/064d27912b511a63caa3
The main issue here is iOS9's support of the ~ selector, which is used in the radio css. But in the nightly builds/gist, we've changed the markup and css a bit to fix this.
So if you use the nightly builds or apply the gist, you can use
<ion-radio-fix></ion-radio-fix>

As your markup. To make sure it has been applied correctly, you can inspect the element and you should see a radio-content div next to the input.
      '' +
        '<input type="radio" name="radio-group">' +
        '
' +
          '

' +
          '' +
        '
' +
      ''

Also, make sure you are including the directive as a dependency. Please let me know if after review this, you still have issues.

Ok, adding the fixes it works in iOS as well. Thanks a lot! Awesome customer care!!!


Cloudformation example to manage policy due to StringLike issues

What would you like to be added:
Per your documentation here:
{
 "Version": "2012-10-17",
 "Statement": [
  {
   "Effect": "Allow",
   "Principal": {
    "Federated": "arn:aws:iam::111122223333:oidc-provider/oidc.us-west-2.eks.amazonaws.com/624a142e-43fc-4a4e-9a65-0adbfe9d6a85"
   },
   "Action": "sts:AssumeRoleWithWebIdentity",
   "Condition": {
    "__doc_comment": "scope the role to the service account (optional)",
    "StringEquals": {
     "oidc.us-west-2.eks.amazonaws.com/624a142e-43fc-4a4e-9a65-0adbfe9d6a85:sub": "system:serviceaccount:default:my-serviceaccount"
    },
    "__doc_comment": "scope the role to a namespace (optional)",
    "StringLike": {
     "oidc.us-west-2.eks.amazonaws.com/624a142e-43fc-4a4e-9a65-0adbfe9d6a85:sub": "system:serviceaccount:default:*"
    }
   }
  }
 ]
}

Could you also provide a cloudformation example?
The StringEquals attribute in the Condition expects a dynamic value such as:
oidc.eks.${AWS::Region}.amazonaws.com/id/$some_id:sub
This is unusual because normally this is a simple string such as "SAML:aud"
Why is this needed:
I have tried using CF Maps, Parameters, etc. but having a dynamic value for the key seems to be the root issue.
This error:
Template format error: [/Resources/TestRole/Properties/AssumeRolePolicyDocument/Statement/0/Condition/StringEquals] map keys must be strings; received a map instead

Closing the issue with no fix required (at least on this project)

For anyone who might stumble upon this (like myself, before realizing there is a solution)
The AssumeRolePolicyDocument is really of type JSON, so you can supply a (JSON) string, rather than trying to manipulate inline JSON directory. ie. (in yaml) you can:
AssumeRolePolicyDocument: !Sub
        - |
          {
            "Version": "2012-10-17",
            "Statement": [
                {
                    "Effect": "Allow",
                    "Principal": {
                        "Federated": "${IamOidcProviderArn}"
                    },
                    "Action": "sts:AssumeRoleWithWebIdentity",
                    "Condition": {
                        "StringEquals": {
                            "${OidcProviderEndpoint}:sub": "system:serviceaccount:default:my-serviceaccount"
                        }
                    }
                }
            ]
          }
        - {
            "IamOidcProviderArn": "arn:aws:iam::111122223333:oidc-provider/oidc.us-west-2.eks.amazonaws.com/624a142e-43fc-4a4e-9a65-0adbfe9d6a85",
            "OidcProviderEndpoint": "oidc.us-west-2.eks.amazonaws.com/624a142e-43fc-4a4e-9a65-0adbfe9d6a85"
          }

@gjenkins8 thanks for this workaround!

thanks for this workaround @gjenkins8
I have this exact same scenario with a little variation. How can we pass OIDC endpoint as a cfn parameter parameter to this ?
The below obviously wont work
       - {
            "IamOidcProviderArn": "${PROVIDER_ARN}",
            "OidcProviderEndpoint": "${OIDC_ENDPOINT}"
          }

@gjenkins8 thank you so much for adding this workaround.  This saved me an incalculable amount of frustration.

@gjenkins8 live saver here as well! I needed to reference my EKSCluster resource to get the OIDC URLs, here was my final resource:
LoadBalancerControllerRole:
  Type: AWS::IAM::Role
  Properties:
    AssumeRolePolicyDocument: !Sub
      - |
        {
          "Version": "2012-10-17",
          "Statement": [
              {
                  "Effect": "Allow",
                  "Principal": {
                      "Federated": "${IamOidcProviderArn}"
                  },
                  "Action": "sts:AssumeRoleWithWebIdentity",
                  "Condition": {
                      "StringEquals": {
                          "${OidcProviderEndpoint}:sub": "system:serviceaccount:default:aws-load-balancer-controller"
                      }
                  }
              }
          ]
        }
      - IamOidcProviderArn: !Join
          - ''
          - - 'arn:aws:iam::'
            - !Ref AWS::AccountId
            - ':oidc-provider/'
            - !Select [1, !Split ["//", !GetAtt EKSCluster.OpenIdConnectIssuerUrl]]
        OidcProviderEndpoint: !Select [1, !Split ["//", !GetAtt EKSCluster.OpenIdConnectIssuerUrl]]
    Path: "/"
    Policies:
      - PolicyName: LoadBalancerControllerPolicy
        [ --- SNIP --- ]

I was getting the following error while trying to verify if the IAM role was correctly attached to the pod using this troubleshooting guide:
kubectl exec -it awscli -n MY_NAMESPACE -- aws sts get-caller-identity

An error occurred (AccessDenied) when calling the AssumeRoleWithWebIdentity operation: Not authorized to perform sts:AssumeRoleWithWebIdentity
command terminated with exit code 254

And it was because there was a typo in the ARN of the provider. Note that it should be:
arn:aws:iam::your-account-id:oidc-provider/oidc.eks.your-region-code.amazonaws.com/id/EXAMPLE_OIDC_IDENTIFIER and not
arn:aws:iam::your-account-id:oidc-provider/oidc.your-region-code.eks.amazonaws.com/id/EXAMPLE_OIDC_IDENTIFIER
Thanks all for the tips and tricks for making the StringEquals condition to work.


Set custom user agent for S3 store client

Fixes #291
This uses the builtin SetAppInfo from Minio to create "Minio (darwin; amd64) minio-go/4.0.9 Thanos/ (go1.10.1)" user agent string for requests.

@Bplotka yeah, facepalmed myself after I commited....

@Bplotka looks like I broke integration tests by adding my repo fork there, can you rerun https://circleci.com/gh/improbable-eng/thanos/tree/pull%2F294 ?

It seems to be green..

@Bplotka Regarding tests I couldn't find a way to provide a URL for the GCS client without changing code.
WRT to the client itself - maybe it'd be better to rewrite the parts to use the factory method instead? repeating gcsOptions everywhere doesn't seem to good maintenance wise...

Yea, I would use client.NewBucket everywhere and that would solve your problem (:
We can do that in next PR though.

Ok, I'll do that after this is merged.

Thanks!


Add some downstreaming running options

Essentially, the downstram pipeline adds some options, which we would like to offer to the users as well. Thereby, we essentially need  a template for a drop down menu and some clickable button. For both it would be good to have one option already preselected. I can add the "real content" once they are there.
I would suggest that for this the page "Running options" is added in the navigation. This page should then be used to generate "running Profiles" with all of these downstream pipeline options. Basically, it would be good if we could assign these "running profiles" to the single samples on the "My samples" site. The preselected options should be seen as the "normal running profile", which should already be pre-assigned to all samples.

@LArnoldt would you have an example set of running options? And would the different running profiles be shared between all users, or would each user be able to create and save their own personal running profiles?

Example:
Running options for "guppy_model":

dna_r9.4.1_450bps_sup.cfg
dna_r9.4.1_480bps_sup.cfg
...

Each user would be able to create and save their own personal running profiles. This is only about the downstream computational analysis, so it is not too problematic if users choose different configurations.


AnimationSession for curves

Hi, can anybody explain what the point is for an AnimationSession on every single AnimationCurve?
The code is already resource intensive (spawning 64 models uses like > 900 MB):

But if I comment out the AnimationSession in the curve constructor:
var AnimationCurve = function () {
    AnimationCurve.count ++;
    this.name = "curve" + AnimationCurve.count.toString();
    this.type = AnimationCurveType.LINEAR;
    this.keyableType = AnimationKeyableType.NUM;
    this.tension = 0.5;// 0.5 catmul-rom
    this.animTargets = [];// allow multiple targets
    this.duration = 0;
    this.animKeys = [];
    //this.session = new AnimationSession(this);
};

Then the code is using consistently like 100 MB less for the same scene:

I tested multiple models and blending between clips and everything still works. Why does each curve need a session?

I'm sure @thomasbiang can provide some information on this topic... 😄

Hi,
Originally each AnimationCurve has a default session, so that user can play animation on a single curve. For the same reason each AnimationClip also has a default session. If few people are using the API for playing a single curve and it takes up a lot resources, I can remove this default session.

Hi,
Originally each AnimationCurve has a default session, so that user can play animation on a single curve. For the same reason each AnimationClip also has a default session. If few people are using the API for playing a single curve and it takes up a lot resources, I can remove this default session.

Hi, I feel it would make the code easier to understand, since it doesn't need any specialcasing via instanceof then and it removes some redundant code, which is needed to implement Playable. And if somebody just wants to animate one curve, its still easy enough to make a clip for it.
I would vote for removal, but this isn't a democracy here I guess ^^

I made a pull request for this https://github.com/playcanvas/playcanvas-gltf/pull/72


Feature Suggestion: Add Interactive django shell to run django ORM queries

Add Interactive django shell to run django ORM queries and show the output
How it works ?

Approaches:
1
Add another command python manage.py django-ishell to launch the interactive shell.
2
Integrate it into existing django-tui command and have separate screen for it.

Side Note:
I already have a MVP version of the feature, if you confirm I will create a pull request as soon as possible.

@anze3db ?

I'm not exactly sure what you mean by interactive shell. How does it differ from python manage.py shell? If you have the MVP ready, feel free to open a PR (or send a link to your repo), and I'll check it out.
About the approaches: I'm not a big fan of approach 2 because it would add an extra step to the primary workflow of looking up commands, but maybe we could bind something like ctrl+i to get to the interactive shell?

Sure, Here is the pr link.
The main way that it differs from manage.py shell is the ease of use. In here you will be writing queries in an editor like environment.
Quick Demo
https://github.com/anze3db/django-tui/assets/48182832/88a74dee-c759-4d7b-8ff3-d5857c462d4d

@shtayeb thank you for the contribution ❤ ! The interactive shell is available in version 23.9 that was just released!


openrgb: 0.3 -> 0.4

Motivation for this change
https://gitlab.com/CalcProgrammer1/OpenRGB/-/releases/release_0.4
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Hm, to me it looks like https://gitlab.com/CalcProgrammer1/OpenRGB/-/blob/master/OpenRGB.pro tries to embed a date into the build, is that something we want to patch out?

I'm not entirely sure, if it inherits from SOURCE_DATE_EPOCH, then we don't have to worry about anything

It's actually visible in the UI and it looks like my local build time.

No git version information because nix removes .git I guess?

Made an attempt at patching the project file; seeing 1 Jan 1980 now in my build. This is something that might be accepted upstream as well.

No git version information because nix removes .git I guess?

correct, there's a "lib.cleanSource" function which will run on most fetchers and remove potential sources of impurity (.git isn't stable)

Upstream pull request opened at https://gitlab.com/CalcProgrammer1/OpenRGB/-/merge_requests/152

Upstream has accepted my MR, so I've updated the 'patch' commit to reflect that.
Or we can not patch it for now and then the next release should fix it.


Reconfirm Welsh posts

Feature
Ask the candidate to reconfirm their desire to be considered for postings in Wales.
Task list
[ ] Form component
[ ] Review component
[ ] Amend guidance text to "Please update this section to take into account any changes since you submitted your application"

Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC @warrensearle


Screen reader is not announcing the Additional Feedback label name for the edit field.

Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Visually challenged users who rely on screen readers are getting impacted if Screen reader is not announcing the Additional Feedback label name for the edit field.
What browsers and screen readers do this issue affect?
Others
Are there any code-based customization done to Web Chat?
No, I am using Web Chat without any customizations except "styleOptions".
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
Others or unrelated
What is the public URL for the website?
https://airtuserexpdev.azurewebsites.net/Dashboard
How to reproduce the issue?
Step 1: Open the above URL in Edge Browser->SAGE chat window will display->Invoke "Chat in teams" button (open in web).
Step 2: Type “What is the accessibility process”->Invoke “Dislike” button.
Step 3: Verify whether Screen reader is announcing the Additional Feedback label name for the edit field or not.
What do you expect?
Screen reader should announce the Additional Feedback label name for the edit field.
What actually happened?
Screen reader is not announcing the Additional Feedback label name for the edit field.
Observation:
Screen reader is announcing placeholder value in the edit field.
Do you have any screenshots or recordings to repro the issue?

Did you find any DOM elements that might have caused the issue?
No response
MAS reference
https://microsoft.sharepoint.com/:w:/r/sites/accessibility/_layouts/15/Doc.aspx?sourcedoc={3752B546-30D8-44D7-8221-6FC32EEB3AC8}&file=MAS 3.3.2 %25u2013 Labels or Instructions.docx&action=default&mobileredirect=true
WCAG reference
https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response

Bug copied from Accenture team: BUG 11645949

#A11yMAS;#A11ySev3;#MAS1.3.1;#HCL;#Accessibility;#FeatureBotframeworkwebchat-Apr23;

@Kirank915  this looks like Teams issue. Teams doesn't use WebChat for chat