show file path suggest besides .js files when working in .js file

Issue Type: Feature Request
when working on a webpack based project, one may want to import .css files or .png files, but vs code doesn't  show those file path suggest
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:09:08.021Z)
OS version: Darwin x64 19.6.0

Duplicate of https://github.com/microsoft/TypeScript/issues/19018


2017-05-30 15:15:00.184 [main] INFO dict.build.FastBuilder - extract words
done: 9000
2017-05-30 15:15:00.191 [main] INFO dict.build.FastBuilder - extract words
done: 10000
2017-05-30 15:15:00.199 [main] INFO dict.build.FastBuilder - extract words
done: 11000
2017-05-30 15:15:00.206 [main] INFO dict.build.FastBuilder - extract words
done: 12000
2017-05-30 15:15:00.213 [main] INFO dict.build.FastBuilder - extract words
done: 13000
2017-05-30 15:15:00.221 [main] INFO dict.build.FastBuilder - extract words
done: 14000
2017-05-30 15:15:00.227 [main] INFO dict.build.FastBuilder - extract words
done: 15000
2017-05-30 15:15:00.233 [main] INFO dict.build.FastBuilder - extract words
done: 16000
2017-05-30 15:15:00.240 [main] INFO dict.build.FastBuilder - extract words
done: 17000
2017-05-30 15:15:00.246 [main] INFO dict.build.FastBuilder - extract words
done: 18000
2017-05-30 15:15:00.252 [main] INFO dict.build.FastBuilder - extract words
done: 19000
2017-05-30 15:15:00.259 [main] INFO dict.build.FastBuilder - extract words
done: 20000
2017-05-30 15:15:00.265 [main] INFO dict.build.FastBuilder - extract words
done: 21000
2017-05-30 15:15:00.272 [main] INFO dict.build.FastBuilder - extract words
done: 22000
2017-05-30 15:15:00.279 [main] INFO dict.build.FastBuilder - extract words
done: 23000
2017-05-30 15:15:00.286 [main] INFO dict.build.FastBuilder - extract words
done: 24000
2017-05-30 15:15:00.292 [main] INFO dict.build.FastBuilder - extract words
done: 25000
2017-05-30 15:15:00.298 [main] INFO dict.build.FastBuilder - extract words
done: 26000
2017-05-30 15:15:00.305 [main] INFO dict.build.FastBuilder - extract words
done: 27000
2017-05-30 15:15:00.311 [main] INFO dict.build.FastBuilder - extract words
done: 28000
2017-05-30 15:15:00.317 [main] INFO dict.build.FastBuilder - extract words
done: 29000
2017-05-30 15:15:00.323 [main] INFO dict.build.FastBuilder - extract words
done: 30000
2017-05-30 15:15:00.329 [main] INFO dict.build.FastBuilder - extract words
done: 31000
2017-05-30 15:15:00.335 [main] INFO dict.build.FastBuilder - extract words
done: 32000
2017-05-30 15:15:00.342 [main] INFO dict.build.FastBuilder - extract words
done: 33000
2017-05-30 15:15:00.348 [main] INFO dict.build.FastBuilder - extract words
done: 34000
2017-05-30 15:15:00.354 [main] INFO dict.build.FastBuilder - extract words
done: 35000
2017-05-30 15:15:00.362 [main] INFO dict.build.FastBuilder - extract words
done: 36000
2017-05-30 15:15:00.368 [main] INFO dict.build.FastBuilder - extract words
done: 37000
2017-05-30 15:15:00.374 [main] INFO dict.build.FastBuilder - extract words
done: 38000
2017-05-30 15:15:00.381 [main] INFO dict.build.FastBuilder - extract words
done: 39000
2017-05-30 15:15:00.387 [main] INFO dict.build.FastBuilder - extract words
done: 40000
2017-05-30 15:15:00.394 [main] INFO dict.build.FastBuilder - extract words
done: 41000
2017-05-30 15:15:00.400 [main] INFO dict.build.FastBuilder - extract words
done: 42000
2017-05-30 15:15:00.407 [main] INFO dict.build.FastBuilder - extract words
done: 43000
2017-05-30 15:15:00.414 [main] INFO dict.build.FastBuilder - extract words
done: 44000
2017-05-30 15:15:00.423 [main] INFO dict.build.FastBuilder - extract words
done: 45000
2017-05-30 15:15:00.430 [main] INFO dict.build.FastBuilder - extract words
done: 46000
2017-05-30 15:15:00.436 [main] INFO dict.build.FastBuilder - extract words
done: 47000
2017-05-30 15:15:00.443 [main] INFO dict.build.FastBuilder - extract words
done: 48000
2017-05-30 15:15:00.450 [main] INFO dict.build.FastBuilder - extract words
done: 49000
2017-05-30 15:15:00.457 [main] INFO dict.build.FastBuilder - extract words
done: 50000
2017-05-30 15:15:00.463 [main] INFO dict.build.FastBuilder - extract words
done: 51000
2017-05-30 15:15:00.470 [main] INFO dict.build.FastBuilder - extract words
done: 52000
2017-05-30 15:15:00.476 [main] INFO dict.build.FastBuilder - extract words
done: 53000
2017-05-30 15:15:00.483 [main] INFO dict.build.FastBuilder - extract words
done: 54000
2017-05-30 15:15:00.490 [main] INFO dict.build.FastBuilder - extract words
done: 55000
2017-05-30 15:15:00.496 [main] INFO dict.build.FastBuilder - extract words
done: 56000
2017-05-30 15:15:00.503 [main] INFO dict.build.FastBuilder - extract words
done: 57000
2017-05-30 15:15:00.510 [main] INFO dict.build.FastBuilder - extract words
done: 58000
2017-05-30 15:15:00.517 [main] INFO dict.build.FastBuilder - extract words
done: 59000
2017-05-30 15:15:00.524 [main] INFO dict.build.FastBuilder - extract words
done: 60000
2017-05-30 15:15:00.530 [main] INFO dict.build.FastBuilder - extract words
done: 61000
2017-05-30 15:15:00.537 [main] INFO dict.build.FastBuilder - extract words
done: 62000
2017-05-30 15:15:00.541 [main] INFO dict.build.FastBuilder - extract words
done: 63000
2017-05-30 15:15:00.545 [main] INFO dict.build.FastBuilder - extract words
done: 64000
2017-05-30 15:15:00.549 [main] INFO dict.build.FastBuilder - extract words
done: 65000
2017-05-30 15:15:00.553 [main] INFO dict.build.FastBuilder - extract words
done: 66000
2017-05-30 15:15:00.557 [main] INFO dict.build.FastBuilder - extract words
done: 67000
2017-05-30 15:15:00.561 [main] INFO dict.build.FastBuilder - extract words
done: 68000
2017-05-30 15:15:00.565 [main] INFO dict.build.FastBuilder - extract words
done: 69000
2017-05-30 15:15:00.569 [main] INFO dict.build.FastBuilder - extract words
done: 70000
2017-05-30 15:15:00.573 [main] INFO dict.build.FastBuilder - extract words
done: 71000
2017-05-30 15:15:00.577 [main] INFO dict.build.FastBuilder - extract words
done: 72000
2017-05-30 15:15:00.581 [main] INFO dict.build.FastBuilder - extract words
done: 73000
2017-05-30 15:15:00.585 [main] INFO dict.build.FastBuilder - extract words
done: 74000
2017-05-30 15:15:00.590 [main] INFO dict.build.FastBuilder - extract words
done: 75000
2017-05-30 15:15:00.594 [main] INFO dict.build.FastBuilder - extract words
done: 76000
2017-05-30 15:15:00.598 [main] INFO dict.build.FastBuilder - extract words
done: 77000
2017-05-30 15:15:00.602 [main] INFO dict.build.FastBuilder - extract words
done: 78000
2017-05-30 15:15:00.606 [main] INFO dict.build.FastBuilder - extract words
done: 79000
2017-05-30 15:15:00.610 [main] INFO dict.build.FastBuilder - extract words
done: 80000
2017-05-30 15:15:00.614 [main] INFO dict.build.FastBuilder - extract words
done: 81000
2017-05-30 15:15:00.618 [main] INFO dict.build.FastBuilder - extract words
done: 82000
2017-05-30 15:15:00.622 [main] INFO dict.build.FastBuilder - extract words
done: 83000
2017-05-30 15:15:00.626 [main] INFO dict.build.FastBuilder - extract words
done: 84000
2017-05-30 15:15:00.630 [main] INFO dict.build.FastBuilder - extract words
done: 85000
2017-05-30 15:15:00.635 [main] INFO dict.build.FastBuilder - extract words
done: 86000
2017-05-30 15:15:00.639 [main] INFO dict.build.FastBuilder - extract words
done: 87000
2017-05-30 15:15:00.643 [main] INFO dict.build.FastBuilder - extract words
done: 88000
2017-05-30 15:15:00.646 [main] INFO dict.build.FastBuilder - extract words
done: 89000
2017-05-30 15:15:00.651 [main] INFO dict.build.FastBuilder - extract words
done: 90000
2017-05-30 15:15:00.654 [main] INFO dict.build.FastBuilder - extract words
done: 91000
2017-05-30 15:15:00.658 [main] INFO dict.build.FastBuilder - extract words
done: 92000
2017-05-30 15:15:00.662 [main] INFO dict.build.FastBuilder - extract words
done: 93000
2017-05-30 15:15:00.666 [main] INFO dict.build.FastBuilder - extract words
done: 94000
2017-05-30 15:15:00.671 [main] INFO dict.build.FastBuilder - extract words
done: 95000
2017-05-30 15:15:00.675 [main] INFO dict.build.FastBuilder - extract words
done: 96000
2017-05-30 15:15:00.678 [main] INFO dict.build.FastBuilder - extract words
done: 97000
2017-05-30 15:15:00.682 [main] INFO dict.build.FastBuilder - extract words
done: 98000
2017-05-30 15:15:00.686 [main] INFO dict.build.FastBuilder - extract words
done: 99000
2017-05-30 15:15:00.690 [main] INFO dict.build.FastBuilder - extract words
done: 100000
2017-05-30 15:15:00.694 [main] INFO dict.build.FastBuilder - extract words
done: 101000
2017-05-30 15:15:00.698 [main] INFO dict.build.FastBuilder - extract words
done: 102000
2017-05-30 15:15:00.702 [main] INFO dict.build.FastBuilder - extract words
done: 103000
2017-05-30 15:15:00.706 [main] INFO dict.build.FastBuilder - extract words
done: 104000
2017-05-30 15:15:00.710 [main] INFO dict.build.FastBuilder - extract words
done: 105000
2017-05-30 15:15:00.716 [main] INFO dict.build.FastBuilder - extract words
done: 106000
2017-05-30 15:15:00.722 [main] INFO dict.build.FastBuilder - extract words
done: 107000
2017-05-30 15:15:00.729 [main] INFO dict.build.FastBuilder - extract words
done: 108000
2017-05-30 15:15:00.734 [main] INFO dict.build.FastBuilder - extract words
done: 109000
2017-05-30 15:15:00.740 [main] INFO dict.build.FastBuilder - extract words
done: 110000
2017-05-30 15:15:00.745 [main] INFO dict.build.FastBuilder - extract words
done: 111000
2017-05-30 15:15:00.750 [main] INFO dict.build.FastBuilder - extract words
done: 112000
2017-05-30 15:15:00.756 [main] INFO dict.build.FastBuilder - extract words
done: 113000
2017-05-30 15:15:00.762 [main] INFO dict.build.FastBuilder - extract words
done: 114000
2017-05-30 15:15:00.767 [main] INFO dict.build.FastBuilder - extract words
done: 115000
2017-05-30 15:15:00.773 [main] INFO dict.build.FastBuilder - extract words
done: 116000
2017-05-30 15:15:00.779 [main] INFO dict.build.FastBuilder - extract words
done: 117000
2017-05-30 15:15:00.784 [main] INFO dict.build.FastBuilder - extract words
done: 118000
2017-05-30 15:15:00.790 [main] INFO dict.build.FastBuilder - extract words
done: 119000
2017-05-30 15:15:00.797 [main] INFO dict.build.FastBuilder - extract words
done: 120000
2017-05-30 15:15:00.803 [main] INFO dict.build.FastBuilder - extract words
done: 121000
2017-05-30 15:15:00.828 [main] INFO dict.build.FastBuilder - extract words
done: 122000
2017-05-30 15:15:00.836 [main] INFO dict.build.FastBuilder - extract words
done: 123000
2017-05-30 15:15:00.842 [main] INFO dict.build.FastBuilder - extract words
done: 124000
2017-05-30 15:15:00.848 [main] INFO dict.build.FastBuilder - extract words
done: 125000
2017-05-30 15:15:00.854 [main] INFO dict.build.FastBuilder - extract words
done: 126000
2017-05-30 15:15:00.860 [main] INFO dict.build.FastBuilder - extract words
done: 127000
2017-05-30 15:15:00.866 [main] INFO dict.build.FastBuilder - extract words
done: 128000
2017-05-30 15:15:00.872 [main] INFO dict.build.FastBuilder - extract words
done: 129000
2017-05-30 15:15:00.878 [main] INFO dict.build.FastBuilder - extract words
done: 130000
2017-05-30 15:15:00.884 [main] INFO dict.build.FastBuilder - extract words
done: 131000
2017-05-30 15:15:00.889 [main] INFO dict.build.FastBuilder - extract words
done: 132000
2017-05-30 15:15:00.895 [main] INFO dict.build.FastBuilder - extract words
done: 133000
2017-05-30 15:15:00.900 [main] INFO dict.build.FastBuilder - extract words
done: 134000
2017-05-30 15:15:00.905 [main] INFO dict.build.FastBuilder - extract words
done: 135000
2017-05-30 15:15:00.912 [main] INFO dict.build.FastBuilder - extract words
done: 136000
2017-05-30 15:15:00.919 [main] INFO dict.build.FastBuilder - extract words
done: 137000
2017-05-30 15:15:00.925 [main] INFO dict.build.FastBuilder - extract words
done: 138000
2017-05-30 15:15:00.931 [main] INFO dict.build.FastBuilder - extract words
done: 139000
2017-05-30 15:15:00.936 [main] INFO dict.build.FastBuilder - extract words
done: 140000
2017-05-30 15:15:00.942 [main] INFO dict.build.FastBuilder - extract words
done: 141000
2017-05-30 15:15:00.949 [main] INFO dict.build.FastBuilder - extract words
done: 142000
2017-05-30 15:15:00.954 [main] INFO dict.build.FastBuilder - extract words
done: 143000
2017-05-30 15:15:00.960 [main] INFO dict.build.FastBuilder - extract words
done: 144000
2017-05-30 15:15:00.966 [main] INFO dict.build.FastBuilder - extract words
done: 145000
2017-05-30 15:15:00.971 [main] INFO dict.build.FastBuilder - extract words
done: 146000
2017-05-30 15:15:00.977 [main] INFO dict.build.FastBuilder - extract words
done: 147000
2017-05-30 15:15:00.982 [main] INFO dict.build.FastBuilder - extract words
done: 148000
2017-05-30 15:15:00.988 [main] INFO dict.build.FastBuilder - extract words
done: 149000
2017-05-30 15:15:00.993 [main] INFO dict.build.FastBuilder - extract words
done: 150000
2017-05-30 15:15:00.998 [main] INFO dict.build.FastBuilder - extract words
done: 151000
2017-05-30 15:15:01.004 [main] INFO dict.build.FastBuilder - extract words
done: 152000
2017-05-30 15:15:01.010 [main] INFO dict.build.FastBuilder - extract words
done: 153000
2017-05-30 15:15:01.016 [main] INFO dict.build.FastBuilder - extract words
done: 154000
2017-05-30 15:15:01.022 [main] INFO dict.build.FastBuilder - extract words
done: 155000
2017-05-30 15:15:01.028 [main] INFO dict.build.FastBuilder - extract words
done: 156000
2017-05-30 15:15:01.033 [main] INFO dict.build.FastBuilder - extract words
done: 157000
2017-05-30 15:15:01.040 [main] INFO dict.build.FastBuilder - extract words
done: 158000
2017-05-30 15:15:01.046 [main] INFO dict.build.FastBuilder - extract words
done: 159000
2017-05-30 15:15:01.051 [main] INFO dict.build.FastBuilder - extract words
done: 160000
2017-05-30 15:15:01.057 [main] INFO dict.build.FastBuilder - extract words
done: 161000
2017-05-30 15:15:01.063 [main] INFO dict.build.FastBuilder - extract words
done: 162000
2017-05-30 15:15:01.070 [main] INFO dict.build.FastBuilder - extract words
done: 163000
2017-05-30 15:15:01.076 [main] INFO dict.build.FastBuilder - extract words
done: 164000
2017-05-30 15:15:01.082 [main] INFO dict.build.FastBuilder - extract words
done: 165000
2017-05-30 15:15:01.089 [main] INFO dict.build.FastBuilder - extract words
done: 166000
2017-05-30 15:15:01.096 [main] INFO dict.build.FastBuilder - extract words
done: 167000
2017-05-30 15:15:01.101 [main] INFO dict.build.FastBuilder - extract words
done: 168000
2017-05-30 15:15:01.106 [main] INFO dict.build.FastBuilder - extract words
done: 169000
2017-05-30 15:15:01.112 [main] INFO dict.build.FastBuilder - extract words
done: 170000
2017-05-30 15:15:01.117 [main] INFO dict.build.FastBuilder - extract words
done: 171000
2017-05-30 15:15:01.123 [main] INFO dict.build.FastBuilder - extract words
done: 172000
2017-05-30 15:15:01.129 [main] INFO dict.build.FastBuilder - extract words
done: 173000
2017-05-30 15:15:01.135 [main] INFO dict.build.FastBuilder - extract words
done: 174000
2017-05-30 15:15:01.138 [main] INFO dict.build.FastBuilder - extract words
done: 175000
2017-05-30 15:15:01.143 [main] INFO dict.build.FastBuilder - extract words
done: 176000
2017-05-30 15:15:01.147 [main] INFO dict.build.FastBuilder - extract words
done: 177000
2017-05-30 15:15:01.151 [main] INFO dict.build.FastBuilder - extract words
done: 178000
2017-05-30 15:15:01.155 [main] INFO dict.build.FastBuilder - extract words
done: 179000
2017-05-30 15:15:01.159 [main] INFO dict.build.FastBuilder - extract words
done: 180000
2017-05-30 15:15:01.163 [main] INFO dict.build.FastBuilder - extract words
done: 181000
2017-05-30 15:15:01.166 [main] INFO dict.build.FastBuilder - extract words
done: 182000
2017-05-30 15:15:01.170 [main] INFO dict.build.FastBuilder - extract words
done: 183000
2017-05-30 15:15:01.174 [main] INFO dict.build.FastBuilder - extract words
done: 184000
2017-05-30 15:15:01.177 [main] INFO dict.build.FastBuilder - extract words
done: 185000
2017-05-30 15:15:01.181 [main] INFO dict.build.FastBuilder - extract words
done: 186000
2017-05-30 15:15:01.184 [main] INFO dict.build.FastBuilder - extract words
done: 187000
2017-05-30 15:15:01.189 [main] INFO dict.build.FastBuilder - extract words
done: 188000
2017-05-30 15:15:01.193 [main] INFO dict.build.FastBuilder - extract words
done: 189000
2017-05-30 15:15:01.196 [main] INFO dict.build.FastBuilder - extract words
done: 190000
2017-05-30 15:15:01.200 [main] INFO dict.build.FastBuilder - extract words
done: 191000
2017-05-30 15:15:01.203 [main] INFO dict.build.FastBuilder - extract words
done: 192000
2017-05-30 15:15:01.207 [main] INFO dict.build.FastBuilder - extract words
done: 193000
2017-05-30 15:15:01.210 [main] INFO dict.build.FastBuilder - extract words
done: 194000
2017-05-30 15:15:01.214 [main] INFO dict.build.FastBuilder - extract words
done: 195000
2017-05-30 15:15:01.218 [main] INFO dict.build.FastBuilder - extract words
done: 196000
2017-05-30 15:15:01.222 [main] INFO dict.build.FastBuilder - extract words
done: 197000
2017-05-30 15:15:01.226 [main] INFO dict.build.FastBuilder - extract words
done: 198000
2017-05-30 15:15:01.229 [main] INFO dict.build.FastBuilder - extract words
done: 199000
2017-05-30 15:15:01.233 [main] INFO dict.build.FastBuilder - extract words
done: 200000
2017-05-30 15:15:01.236 [main] INFO dict.build.FastBuilder - extract words
done: 201000
2017-05-30 15:15:01.240 [main] INFO dict.build.FastBuilder - extract words
done: 202000
2017-05-30 15:15:01.243 [main] INFO dict.build.FastBuilder - extract words
done: 203000
2017-05-30 15:15:01.247 [main] INFO dict.build.FastBuilder - extract words
done: 204000
2017-05-30 15:15:01.252 [main] INFO dict.build.FastBuilder - extract words
done: 205000
2017-05-30 15:15:01.256 [main] INFO dict.build.FastBuilder - extract words
done: 206000
2017-05-30 15:15:01.259 [main] INFO dict.build.FastBuilder - extract words
done: 207000
2017-05-30 15:15:01.263 [main] INFO dict.build.FastBuilder - extract words
done: 208000
2017-05-30 15:15:01.267 [main] INFO dict.build.FastBuilder - extract words
done: 209000
2017-05-30 15:15:01.271 [main] INFO dict.build.FastBuilder - extract words
done: 210000
2017-05-30 15:15:01.274 [main] INFO dict.build.FastBuilder - extract words
done: 211000
2017-05-30 15:15:01.279 [main] INFO dict.build.FastBuilder - extract words
done: 212000
2017-05-30 15:15:01.284 [main] INFO dict.build.FastBuilder - extract words
done: 213000
2017-05-30 15:15:01.288 [main] INFO dict.build.FastBuilder - extract words
done: 214000
2017-05-30 15:15:01.291 [main] INFO dict.build.FastBuilder - extract words
done: 215000
2017-05-30 15:15:01.295 [main] INFO dict.build.FastBuilder - extract words
done: 216000
2017-05-30 15:15:01.299 [main] INFO dict.build.FastBuilder - extract words
done: 217000
2017-05-30 15:15:01.303 [main] INFO dict.build.FastBuilder - extract words
done: 218000
2017-05-30 15:15:01.306 [main] INFO dict.build.FastBuilder - extract words
done: 219000


Filebeat inputs - Support subfields on fields section (relative to ecs support)

Fix code to support ability to set sub fields on fields section. Actually, we can only set key and value.
Actually supported:
fields:
  type: apache_access

Actually not supported:
fields:
  event:
    dataset: apache_access

Maybe we can replace this:
<%- if @fields.length > 0 -%>
  fields:
    <%- @fields.each_pair do |k, v| -%>
    <%= k %>: <%= v %>
    <%- end -%>
  <%- end -%>

by:
<%- if @fields.length > 0 -%>
fields:
  <%- %><%= @fields.to_yaml.lines.drop(1).join.gsub(/^/, '  ') -%>
<%- end -%>

The pull request #236 seems not permit to use pure_array when use create_ressource(filebeat::input, $filebeat_apache), because of it not use field on class filebeat::input::inputs, but field on filebeat::inputs

The pull request #236 seems not permit to use pure_array when use create_ressource(filebeat::input, $filebeat_apache), because of it not use field on class filebeat::input::inputs, but field on filebeat::inputs


Could not load class 'join_state_controller/JointStateController'

Os: Ubuntu 20.04
Ros noetic

Please help me.

I solve by install on Ubuntu 18 use ros melodic.

Sorry for the late reply, and congratulations to you!


Feature/autooptimization

Codecov Report

Merging #18 into master will decrease coverage by 2.16%.
The diff coverage is 86.95%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
- Coverage    97.2%   95.03%   -2.17%
==========================================
  Files           7        8       +1
  Lines         536      645     +109
==========================================
+ Hits          521      613      +92
- Misses         15       32      +17

Impacted Files
Coverage Δ

drf_tweaks/__init__.py
100% <100%> (ø)
:arrow_up:

drf_tweaks/test_utils.py
100% <100%> (ø)
:arrow_up:

drf_tweaks/optimizator.py
77.92% <77.92%> (ø)

drf_tweaks/serializers.py
96.11% <97.36%> (+0.35%)
: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 223e0b8...7bd063e. Read the comment docs.


oops removed rogue print statement

Accidentally left a 'print' statement in merge.py. This PR is just cleaning that up.

Codecov Report

Merging #19 (25e9c2a) into main (ec42ac8) will decrease coverage by 0.69%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
- Coverage   67.87%   67.17%   -0.70%
==========================================
  Files          27       27
  Lines        1130     1109      -21
==========================================
- Hits          767      745      -22
- Misses        363      364       +1

Flag
Coverage Δ

unittests
67.17% <ø> (-0.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

careless/merge/merge.py
71.86% <ø> (+0.13%)
:arrow_up:

careless/models/scaling/nn.py
49.33% <0.00%> (-3.76%)
:arrow_down:

careless/utils/distributions.py
51.16% <0.00%> (-2.69%)
:arrow_down:

careless/models/scaling/image.py
52.77% <0.00%> (-2.49%)
:arrow_down:

careless/models/merging/variational.py
81.25% <0.00%> (-1.94%)
:arrow_down:

Continue to review full report at Codecov.

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


ALQO 6.4 crashes on MAC when locking the wallet

Describe the issue
ALQO 6.4 crashes on MAC (did not check on windows) when locking the wallet
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Launch the 6.4 wallet on MAC (did not check on Windows)
Unlock it via the Icon
Lock it

Expected behavior
The client should not crash
Actual behavior
The client crashes
What version of ALQO are you using?
ALQO 6.4, MAC, official binaries

This will be patched in the ver 6.5 release.


ENH: Reduce warning logs during DICOM import

When ctkDICOMIndexer::addFile was called with non-empty destinationDirectoryName (to indicate that file should be copied) then "Ignoring destinationDirectoryName parameter, just taking it as indication we should copy!" warning message was logged for each file. This flooded the logs and had noticeable performance impact.
Since this warning is for developers, it is not necessary to log it for each file during runtime, but the behavior is documented instead in the header file.

LGTM - thanks!


Infinality: update fontconfig-ultimate, add cairo patches

Motivation for this change
This updates fontconfig-ultimate patches and moves to new presets. Our old preset file was obsolete for some time, and new presets are hardcoded into freetype with Infinality patches. This update accomodates for that, removing our presets and instead allowing user to choose one of the new ones. If user wishes, he or she can override the preset with environment variables.
This also adds cairo infinality patches.
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This branch is for review only; I indend to merge this branch instead, which also includes #16730 and will include #17770 later. It needs combined testing before we can merge.

I have an issue with applying the very large Infinality patches from fontconfig-ultimate to FreeType (not the cairo ones) even when fonts.fontconfig.ultimate.enable is set to false. The three options I think we should have are:

Unmodified (vanilla) FreeType (currently possible if useEncumberedCode is false, though other software than FreeType gets Infinality patches)
FreeType with subpixel rendering enabled (currently not possible without having all the fontconfig-ultimate patches)
fontconfig-ultimate, with patches applied to FreeType and other software (currently the default, also implies subpixel rendering)

Unfortunately, fontconfig-ultimate hasn't been actively maintained lately and is likely to have some trouble with the 2.7 release of FreeType, which adds a new bytecode hinting mode. (Which was added in 2.6.4 and enabled by default, but that was reverted in 2.6.5.)

I think we should leave Infinality support enabled by default for the upcoming 16.09 release given that we would most likely have freetype 2.6.5 there for which there are updated patches (see https://github.com/NixOS/nixpkgs/pull/17770#issuecomment-240982060).
We also may want to add extra flags to other software to disable those patches (they are independent of each other, i.e. Cairo patches can be used without patching freetype) or say allow option 2 if wanted. I'm lazy to do that myself but PRs would be gladly accepted.
For the future freetype update if Infinality's author won't pick it up again we may move to option 2 by default.

I have an issue with applying the very large Infinality patches from fontconfig-ultimate to FreeType (not > the cairo ones) even when fonts.fontconfig.ultimate.enable is set to false.
I'm not sure I understood you correctly there -- why fonts.fontconfig.ultimate.enablewould solve the problem with applying patches?

The issue was that useEncumberedCode was a toggle for Infinality rather than just for subpixel rendering, but that is fixed now that there are separate parameters for both, which essentially makes option 2 possible.
My thought was that ultimately (not for 16.09), the values of the useInfinality and enableInfinality parameters for the packages that have such patches could be changed by fonts.fontconfig.ultimate.enable.

Unfortunately, that cannot be done on NixOS easily because of one of primary properties of Nix: dependencies are strictly specified in all packages, and any change in a dependency causes rebuild of everything downstream. For this suggestion it means that if the user changes those options, it would trigger source rebuild of all GUI-related things (since they all use freetype in the end).
That means that we need to rely on runtime switches instead to control such behaviour, which exist both for subpixel rendering (in XML config files I think) and Infinality (via environment variables).


[FEATURE REQUEST] Firebase Auth - Convert an anonymous account to a permanent account

Is your feature request related to a problem? Please describe.
Currently there is no way to convert an anonymous Firebase account to a permanent account as described here: https://firebase.google.com/docs/auth/web/anonymous-auth#convert-an-anonymous-account-to-a-permanent-account
Describe the solution you'd like
Would like method(s) added to auth.gd to support this workflow.
Describe alternatives you've considered
I have considered some cloud functions that would migrate user data from the original anonymous account into the newly created account but this seems sub-optimal when a more general solution is possible.

Closed by #391.


Separate layers : Preference

What type of PR is this?
/kind cleanup
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Part of #5247
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

Unit Tests finished with errors.
View logs: TXT HTML

Kubernetes Tests finished successfully.
View logs: TXT HTML

OpenShift Tests finished successfully.
View logs: TXT HTML

Kubernetes Tests finished successfully.
View logs: TXT HTML

Unit Tests finished successfully.
View logs: TXT HTML

OpenShift Tests finished successfully.
View logs: TXT HTML

Kubernetes Tests finished successfully.
View logs: TXT HTML

Unit Tests finished with errors.
View logs: TXT HTML

OpenShift Tests finished successfully.
View logs: TXT HTML

Unit Tests finished with errors.
View logs: TXT HTML

OpenShift Tests finished with errors.
View logs: TXT HTML

Kubernetes Tests finished successfully.
View logs: TXT HTML

@feloy I like the interfaces approach you have proposed here. However, I see some discrepancies in the structure of pkg/preference and pkg/application & pkg/project in #5293.

Why are we using implem.go file? It's not present in #5293.
How about using interface.go or types.go to define an interface and have its implementation in preference.go (for this PR) and application.go & project.go for #5293?
Is there some structuring paradigm that you are following here which I should rather be aware of?

My intention is to setup a proper code contributing guideline for new contributors to get started with odo code.

@feloy I like the interfaces approach you have proposed here. However, I see some discrepancies in the structure of pkg/preference and pkg/application & pkg/project in #5293.

Why are we using implem.go file? It's not present in Separate layers - Application + Project #5293.

In application and project, I used kubernetes.go because the implementation is Kubernetes-related, and to make it similar to the url and storage packages.
The preference package is not related to Kubernetes, but to filesystem. I'm not sure which file name to use here.

How about using interface.go or types.go to define an interface and have its implementation in preference.go (for this PR) and application.go & project.go for Separate layers - Application + Project #5293?

It seems the standard is to declare the interface in a file named with the package name, for example in the go stdlib, the FS interface is declared in a fs.go file: https://cs.opensource.google/go/go/+/refs/tags/go1.17.5:src/io/fs/fs.go

What's the purpose of kubernetes.go file in Separate layers - Application + Project #5293? odo has very limited functionality that's specific to OCP. And even those are just another kubernetes resources (Having separate layers #5247 (comment)).
Can we define below type at one place:type kubernetesClient struct {
	client kclient.ClientInterface
}

To implement an interface, we need a type. Incidentally, each implementation (for project, application) has the same underlying structure, but it is not sure it will always be the same. We will probably add more clients to some of these structures (for ex a project.ClientInterface, or a service.ClientInterface, etc)

I genuinely don't know at the time of writing this as to how it can be done. But I have a feeling that defining kubernetesClient under various pkg/* directories will bite us at some point.
Is there some structuring paradigm that you are following here which I should rather be aware of?
My intention is to setup a proper code contributing guideline for new contributors to get started with odo code.

/test v4.9-integration-e2e
  * could not run steps: step [release:latest] failed: release "release-latest" failed: the pod ci-op-1wjwi82z/release-latest was deleted without completing after 29s (failed containers: )

/test unit
  * could not run steps: step unit failed: "unit" test steps failed: "unit" pod "unit-unit-steps" failed: the pod ci-op-7nl9cs8b/unit-unit-steps was deleted without completing after 7m20s (failed containers: )

/approve


Problem with LME .siem-signals-default

Hi,
I am having an issue with the above index.  I think this is related to issue 140 where i deleted all the problematic indices.  the error message is  below... Wil l need to recreate the name index?  If so can you point me in the right direction?
illegal_argument_exception: rollover target [.siem-signals-default] does not point to a write index (400)
{
"name": "Error",
"body": {
"message": "illegal_argument_exception: rollover target [.siem-signals-default] does not point to a write index",
"status_code": 400
},
"message": "Bad Request",
"stack": "Error: Bad Request\n    at fetch_Fetch.fetchResponse (https://Server_IP/46953/bundles/core/core.entry.js:8:57198)\n    at async https://Server_IP/46953/bundles/core/core.entry.js:8:55366\n    at async https://Server_IP/46953/bundles/core/core.entry.js:8:55323"
Thanks
Ed

HI Duncan,
I have now managed to fix this issue, many thanks for all help (once again!).  For those how want to know how to do this in future you need to use the dev tools, identify the lastest index and enter the index name you want change (or create), the alias name the index is assigned to and the value
Put .siem-signals-default-YOUR INDEX NUMBER
{
"aliases" : {
".siem-signals-default" : {
"is_write_index" : true
}
}
}


Conditional Rendering - Merge Registration and Inventory Pages

If user is logged in and has a business, we should show the inventory management page
If  user does not have a registered business (or is not logged in) we should show the business registration page

I created a backend issue to create the necessary code to make this easier.
See: https://github.com/jimventory/Backend/issues/47
@vbroda17

I believe that issue #47 should be included in this PR and that we should remove issue #47.


132 build initial prefect resources

convert original model to prefect
ignore wandb local artifacts
linting
move test data to its own directory
cmds have been moved to prefect pipelines

Changes
Ported original sagemaker logic to prefect, removing some unneeded code.
Comments
Need to come up with better CI/CD in choosing models. This should be doable in wandb model registry, need to look more into it.

It looks like there's an issue with the coverage tool collecting the report and that's blocking the merge.


Implement autotune deployment in openshift environment

Please review the scripts developed for autotune deployment in openshift environment.

Closing this as we have now added this support through PR #427


State message type

Currently the NavSatFix message type uses quaternions for the orientation of the vehicle. Right now we are just passing the heading (no other orientation info for the vehicle).  We also leave all of the covariance variables empty because those aren't used anywhere later in the pipeline, and some of our filters don't generate that data. I see three options for how to go about this:

Write a custom vehicle state message type that doesn't include the unnecessary info. This is the most "data efficient" solution, but we would have to switch message types if we want to add the old info back in in the future.
Translate the heading angle to a quaternion. This generates a lot of unnecessary data (could pass this message with one float, but instead doing it with 4). This is not actually that bad for us, but just not the best practice in general...
Leave it as is, and if we have an application in the future that requires quaternions or can publish the covariances, do so. This still passes the "large" message types though...

I am leaning towards 3), but wanted to write this out somewhere because @AaronYoung5 commented on it. Thoughts? @harryzhang1018 @ishaanamahajan

I personally think 3) should work for now, especially since we have 4 different vehicles. Every vehicle would want different data from the message type depending on what application it is being used for.

Closing bcs ppl didn't reply and I decided we are going with 3.


Define the artistic aspect of the scenarios

The artistic aspect of the scenarios was defined in our game presentation and further elaborated in the "Look and feel" and "Diseño de nivel" sections of our GDD.

GDD: https://docs.google.com/document/d/1iHbk6SjNvEBSYVCmc0KMylksYg6bwNcP/edit#heading=h.iq6is1wkc2sn


Amplify / AppSync with graphql and Cognito - Audit User Actions

** Which Category is your question related to? **
Amplify-cli / Appsync
** What AWS Services are you utilizing? **
api / graphql, hosting, DynamoDB, cognito
** Provide additional details e.g. code snippets **
I asked a similar question here:
https://forums.aws.amazon.com/thread.jspa?threadID=305061&tstart=0
But, i feel like I'm not really getting a great answer specific to my application's setup. I'm using amplify/appsync and trying to figure out a good way to handle this generically. I have a handful of resources that I need to audit.
I am trying to find an effective way to track changes performed using AWS AppSync. By audit or track, what I mean by that is:
I have a need to track what a user does in the system. So at a minimum:
who (username)
what (mutation)
when
where (source IP or other info)
why (this is more than likely gonna be entered by the user)
I'm sure there is more, but if I can get that that would be huge.
The suggestion is to add pipeline resolvers ... but I'm having trouble figuring out how to manage that with my schema.graphql. Some questions:
Do I just add files to my resolvers & stacks?
How do I just add my pipeline and still utilize the standard resolvers?
Is there a way to write a generic pipeline resolver that will handle all mutations in the system?
I have a vague idea of how to implement this (documentation is not clear), but I'm also thinking that this is the wrong tool. It feels like this kind of thing should be audited at a different level.
Any help is greatly appreciated.

+1


add Python 3.9 support

Added Python 3.9 support in GitHub Actions and setup.py. Fix docs (and replace Travis with Github Actions).
Checklist

[x] I have read contributing guidelines
[x] I'm sure that I did not unrelated changes in this pull request
[x] I have created at least one test case for the changes I have made

@eumiro Can you please, fix issues: https://github.com/lk-geimfari/mimesis/runs/1506865642? Thanks!

Fixed the two mypy error messages. However Windows CIs have some issues with pip permissions. Where are they defined?


Add Python type stub.

First pass at adding type annotations.
Closes https://github.com/facebookresearch/visdom/issues/388.

Seems solid to me - did you get a chance to test with pyre?

Not yet, I'll give that a shot.
On Thu, Jun 21, 2018 at 10:13 AM Jack Urbanek<EMAIL_ADDRESS>wrote:

Seems solid to me - did you get a chance to test with pyre?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebookresearch/visdom/pull/396#issuecomment-399118048,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8Sve89gAabbUCK7G6zgOj_fBx5_n6zks5t-6oBgaJpZM4Uv0SR
.

It does work with pyre in my testing, with the caveat that pyre needs to be explicitly told the directory where the stub lives with the search_path option. That won't be necessary once https://github.com/facebook/pyre-check/issues/70 is resolved.

I rebased. I don't think any other changes are needed since #392 didn't change the type information of any Visdom arguments, as far as users are concerned.

Ah fair enough - I recall a time where some of this overlapped with #392 but I suppose that went away with the separate stub file. Thanks!


Example request: Expand object detection predictions to the original image

What is the task?
Object detection
Is this example for a specific model?
Not as far as I can tell. What I am wondering about is how to adapt results from the inference phase of the object detection scenario to be displayable over the original image as opposed to transformed sample. Here's is some code to illustrate
def predict_from_url(image_url):
    # this is just a helper defined previously
    img = image_from_url(image_url)

    infer_tfms = tfms.A.Adapter([*tfms.A.resize_and_pad(384), tfms.A.Normalize()])
    infer_ds = Dataset.from_images([img], infer_tfms)
    infer_dl = faster_rcnn.infer_dl(infer_ds, batch_size=1)

    batch, samples = faster_rcnn.build_infer_batch(infer_ds)
    preds = faster_rcnn.predict(model=model, batch=batch)

    imgs = [sample["img"] for sample in samples]

    # This works as expected for a sample which are transformed original image (resized and padded)
    #  I would like to understand how to transform BBox'es returned in predictions so i can overlay them over the
    #  original image
    show_preds(
        samples=imgs,
        preds=preds,
        class_map=data_class_map,
        denormalize_fn=denormalize_imagenet,
        show=True,
    )

Don't remove
Main issue for examples: #39

I have tried the following so far
# grab bounding boxes returned via inference call
bboxes = [[bbox.xmin, bbox.ymin, bbox.xmax - bbox.xmin, bbox.ymax - bbox.ymin]]

# attempt to set up a reverse compose using height and width of the original image
reverse_transform = tfms.A.Compose(
  [*tfms.A.resize_and_pad([height,width])],
  bbox_params=tfms.A.BboxParams(format='coco', label_fields=['category_ids']),
)

# try reverse transform and include bounding boxes
reversed = reverse_transform(image=sample, bboxes=bboxes, category_ids=category_ids)

Which produces the following result:

This is a sample from inference with what looks like a pretty good bbox

Here is the original image with bbox returned via reverse transform

As you can see, there is a bit of a discrepancy there. I am wondering what is the right way to reverse these transforms.

I think the easiest solution for now, before we integrate this on the API, is to do it manually. You just need to multiply each bbox coordinate with it's corresponding re-scale factor (original_img_size / transformed_img_size), just be sure to get X and Y coordinates correct and be careful with the padding.

ponding re-scal

Hi @lgvaz, do you have any working examples of this?

@tumbleintoyourheart not right now, but I'm sure other people will have in the community. Join the discord server and ask there =)

This currently works thanks to the end2end_detect function.


Error E0046 should be the last one to report

struct Context;

trait ctx{

  fn f1(&self) -> String;

  fn f2(&self) ;

}

impl ctx for Context{

  fn f1(&self) -> String{

     // code here

  }

}

During coding, I always need to run 'cargo build' to check whether it is right, but for the code above, it always report  "error: not all trait items implemented, missing: f2 [E0046]
error: aborting due to previous error",
It is ok that only one or two methods of the trait that need to be implemented,but if the trait has ten methods, I have to implement all of them before I can check whether method f1 is implemented right, without syntax error.
I wish that E0046 be reported as the last one.

This is more fitting for a rust issue, than a rfc.

@Ticki Thanks


i became contribiutor

... by adding a useless comment at the beginning
edit: please accept pull request so i can actually become contribiutor

thats not even how you spell contributor anyways

:skull: :skull:


Added cards for different guides in Introduction page

According to the issue #82 , I have added links to different guides on the Introduction page and removed the unwanted content (Get-Started section) from the Introduction page .
This PR solves a part of #82 .

Small boxes that redirect people to what they care about, similar to https://nextjs.org/docs#join-our-community

I have just some super small recommendations about the wording, but I'm also aware that the text might be too long for the card.

What do you think?

I was trying to be mindful of that and went with one-liners. But we can add the changes if we make every card with same lines. Then it would not look weird.

I was trying to be mindful of that and went with one-liners. But we can add the changes if we make every card with same number of lines. Then it would not look weird.

I tried it locally and I think it looks good. Let me make a commit.


[CocoaPods] Undefined symbols for architecture x86_64 error when compile

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.2
Firebase SDK version: 6.11.0
Installation method: CocoaPods
Firebase Component: Core, Analytics

[REQUIRED] Step 2: Describe the problem
After doing pod install on my project, i encountered this "Undefined symbols for architecture x86_64" error when trying to compiled it using the Simulator.

I already tried to add -Objc at Build Setting > Other Linker Flags, removed derived data, & run project cleanup, but it doesn't solved the error.
Steps to reproduce:

You may clone the sample project from here : https://bitbucket.org/Blurzschyter/projectxyz/src/master/
Uncomment the firebase pod line on podfile.
Run pod install

Thank you in advance ^_^

@Blurzschyter Those missing symbols are not related to Firebase. It looks like a problem related to lightWebiOS.a and VmxCutInterface.
The binary archive ./EXTSDK/libs/libViewRightWebiOS.a does not have a simulator slice:
$ file ./EXTSDK/libs/libViewRightWebiOS.a
./EXTSDK/libs/libViewRightWebiOS.a: Mach-O universal binary with 2 architectures: [arm_v7:current ar archive random library] [arm64]
./EXTSDK/libs/libViewRightWebiOS.a (for architecture armv7):	current ar archive random library
./EXTSDK/libs/libViewRightWebiOS.a (for architecture arm64):	current ar archive random library


Unclear documentation

A few things are vague in this article. If you provided either better descriptions of fields with examples or an actual attached example of the report export you would completely clear this up for folks without easy access to run the report themselves from a tenant.

The screenshot of the view in Admin Center shows a character string, not a friendly username. Is that how the report should look?
The "version" field: does it include the exact Outlook version number (which is important for specific features) or is it just the general platform version (Mac, Windows, iOS, etc)?

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

ID: 535888ea-6011-1467-bf9a-1de66cb8c402
Version Independent ID: d72f6ddc-15a0-5398-251e-92496afdf309
Content: Office 365 Reports in the Admin Center - Email apps usage
Content Source: Office365-Admin/activity-reports/email-apps-usage.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@officedocsbot assign @mypil

@Jason6311 - Thank you for submitting feedback.
I will get this issue over to the O365ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@Jason6311

Report will list the real username. Screenshot is showing the Guid to hide the real username.
Version is just general platform version (Mac, Windows, iOS, etc) and its not outlook version number.

@Jason6311 - From our understanding, the issue has been answered by npsptechusa. If you feel it hasn't been resolved please re-open this issue.
Thank you for engaging with the community here for the docs.

@officedocsbot close


added JavaScript website course from free code camp

Hi, I added javascript course from free code camp in "JavaScript website" section.  Please review it and let me know if I need to do anything. Thanks !

You have also pushed package-lock.json file

There are also conflicts!
NOTE
The contributing guidelines have changed so please make a new PR to dev branch.
Checkout the contributing.md file for more details.
Do not make any PR on the Main branch.


wasm-smith: Implement support for generating GC instructions

Found and fixed a bunch of bugs in the validator, encoder, and the generator itself. Since then, this has been fuzzing for about 18 hours without finding any new bugs.

Okay, CI is green now.

Thanks for taking a look at this!


A round of cleanups

Assorted drive-by cleanups and small refactorings; individual commits describe the specific changes.

The CI failure seems to be https://github.com/rs-ipfs/rust-ipfs/issues/178.

Would removal of those warnings from latest nightly be good enough to include in cleanups? The annotations are at the bottom of the review. Basically just delete the lines #[allow(rust_2018_idioms)], there should be two of these.

Ah, I just thought we didn't mind, since that file was auto-generated; btw, since it is, do we even need to keep it in the repo?

bors r+

Ah, I just thought we didn't mind, since that file was auto-generated; btw, since it is, do we even need to keep it in the repo?

quick-protobuf doesn't (yet) have nice automation for this, so, so far we do need to keep it. It is also nice to be able to view it. It's not like we should need to rebuild the file anytime soon. But when we do, we should change the field names, which I didn't modify the first time around.


Fix bug and tests

Port from #6536.
Leaving isolated channels enabled by default, since the gap for potential bug was very narrow.
Also attempted to better address the test bugs by clearly separating read from write isolated channels.

nit: Can you please update the title to better reflect what this PR does. Currently, its pretty vague :-).


blend sdk binaries restored from nuget

@mauroservienti Is that ok for you?

to me it is good, have you tested that the WPF designer still works when creating a new project using the Interactivity nuget package? I remember I had some issues, at least with VS2013. Can you test it?

Step to reproduce:

[ ] Create new blank WPF project
[ ] Add Expression.Blend.Sdk
[ ] In the window use a behavior from interactivity

@mauroservienti Is that correct?

If I recall correctly yes

ok I check and tell you the results

I've tried on a blank project and it works.
I've tried on the Radical.Samples and every behaviors works.
The designer in both projects works, actually I don't see any error, and all the controls are rendered.
@mauroservienti Could I proceed and merge it?

Go :-)
Sent from my Amazing not anymore Yellow Lumia, typos are guaranteed ;-)

From: Michael<EMAIL_ADDRESS>Sent: ý12/ý01/ý2015 15:18
To<EMAIL_ADDRESS>Cc: Mauro<EMAIL_ADDRESS>Subject: Re: [radical] blend sdk binaries restored from nuget (#119)
I've tried on a blank project and it works.
I've tried on the Radical.Samples and every behaviors works.
The designer in both projects works, actually I don't see any error, and all the controls are rendered.
@mauroservientihttps://github.com/mauroservienti Could I proceed and merge it?
—
Reply to this email directly or view it on GitHubhttps://github.com/RadicalFx/radical/pull/119#issuecomment-69575535.

great, does this mean that we can update the readme.md and the readme files in the NuGet packages removing the dependency on the Blend SDK?
@enosrecanati could you check if the same SDK should be removed from the Universal App support?

great, does this mean that we can update the readme.md and the readme files in the NuGet packages removing the dependency on the Blend SDK?

yes I think we don't need to specify those requirements, because now it's all managed by nuget package restore. We can leave the note on NuBuild extension, even if will be removed when CI #93  process will be ready :smile:

@enosrecanati could you check if the same SDK should be removed from the Universal App support?

The packages are:

Install-Package Expression.Blend.Sdk3 for blend sdk 3 (created by me waiting to be merged in the following one, I've already asked the owner of the other package)
Install-Package Expression.Blend.Sdk for blend sdk 4 & 4.5


Use Case - OSPO scores updates

Context
An essential process related to open-source project management is the scorecard score. This score gives information about the security level of the project and the correctness of the code. The scorecard scores can be used as an indicator or as a KPI for a company's OKR.
We need to add a use case to get the scorecard score of a group of projects from GitHub and update their values in a database on notion.
This use case will imply the creation of a new component or term in the project structure. This new component should abstract the logic to write or update information on a destiny (like notion using an API).
For this issue, we need to:

[ ] Add a fetcher, mapper, and formatter for the scorecard score.
[ ] Add a base class to abstract the update process on destiny. Then, a use case implementation for notion should be defined to cover the use case.

Tackled on https://github.com/kommitters/bas/issues/87


Process Proposal Following Gap Analysis

Following the 19th December 2019 deadline of the milestone there was a gap analysis that happened on an issue as well as on a two W3C Solid Community Group calls in both timezones. The minutes for the 20200102_1600CET and 20200109_1000CET were recorded for reference.
In this pull request, I have started to incorporate the suggestions from the conversations into a process proposal.
I'm still working on including a few more details but will publish the work so far so we can co-create and include any suggestions along the way.

Can we first list problems before discussing solutions?
I.e., what are the things that are not working today?
For lack of problems, we cannot evaluate whether the proposed changes tackle them.
Suggestion: create an issue per problem.

@RubenVerborgh the problems have been discussed in the four CG calls we've had, I don't know if we should reiterate. Personally, my thread pool is quite full, so I would be hesitant to engage more than we've done on the calls.

I don't know if we should reiterate.

Yes.

For lack of problems, we cannot evaluate whether the proposed changes tackle them.

Not asking to discuss or negotiate, just list.

Most work is being done through the github issues, PRs, etc.
Some participants having discussed something in a couple of calls, without bringing (at least summaries of) those discussions here, does not seem to fit with the collaborative community ethos that I believe remains a goal of this work.
I think this is the third, maybe the fourth, significant re-work of the Solid Process in the past year or so. Each round has been a fairly wholesale rip-and-replace of the previous structure, including a restructuring of the github repositories in use.
Sometimes such a wholesale process replacement is warranted, but usually that's after a given process has been tried for a reasonably long window of time -- more than a few months! -- and after a fair number of incremental changes have been applied to fix areas of weakness discovered while working with that version -- which weaknesses are usually nameable, if not describable in detail, especially when they're severe enough to warrant a wholesale process replacement.
I'm hoping for a clear list of the issues which were raised in those calls, and for an equally clear list of which element(s) of this PR address each issue -- as well as which, if any, elements of this PR are distinct from those directed issue fixes.

Can we first list problems before discussing solutions?
I.e., what are the things that are not working today?
For lack of problems, we cannot evaluate whether the proposed changes tackle them.
Suggestion: create an issue per problem.

I have to agree with @RubenVerborgh and @TallTed - it's not clear to me how the large body of changes proposed here map to specific or broad problems. IMO - the only fair way to have reasonable discussion and evaluation of these changes are individual pulls - each of which are focused on addressing a specific / stated problem or need (which ideally would be tied to a reported issue).
My proposal is that we move away from this single pull into smaller individual pulls, each with a stated problem and proposed solution.

Check links in my first message for a list of problems associated with the gap analysis that have been raised in the last few W3C Community Group calls that @kjetilk mentioned.
Important to note that 1 of 44 items were closed in the last milestone. The project board shows that although items were not closed they were advanced to some extent. Activity in the Specification repo opened some months ago has been remarkably low. There have been weekly  W3C Solid Community Group, Editor, and Panellist calls but not all the members listed in the editor and panel roles have been attending these calls.

@RubenVerborgh the problems have been discussed in the four CG calls we've had, I don't know if we should reiterate. Personally, my thread pool is quite full, so I would be hesitant to engage more than we've done on the calls.

@kjetilk I'm not sure it's fair to ask for review but not stipulate the reasoning behind the changes. We spent several months refining the process and getting community consensus on it. The timing of the community calls are such that 50% of them are at 4AM EST / 1AM PST for those in the US, and the ones related to this occurred when many were either still away on a holiday break (myself included), or digging out of things that came up during it. The minutes I have reviewed at https://www.w3.org/community/solid/wiki/Meetings include a lot of topics for discussion but very little in the way of decisions that were reached for each one, or why. From the participants listed these were also very lightly attended meetings.

Important to note that 1 of 44 items were closed in the last milestone. The project board shows that although items were not closed they were advanced to some extent. Activity in the Specification repo opened some months ago has been remarkably low. There have been weekly W3C Solid Community Group, Editor, and Panellist calls but not all the members listed in the editor and panel roles have been attending these calls.

@Mitzi-Laszlo I believe these problems can be extracted from your points there:

Specification work isn't progressing quickly enough
Attendance / engagement is too low on regular calls

Can we get an explanation of how the changes included address these points? Why do we think these changes will make a positive difference, as opposed to creating new swirl? Are there additional points to address? Based on the content of the changes it seems like we're also trying to cover other problems too, so lets identify those.

Activity in the Specification repo opened some months ago has been remarkably low.

I am not sure that this is quite accurate. While it is true that many issues have been opened and only one has been closed, there has been an extensive amount of discussion on the high priority issues (esp. those identified for the Dec 19 milestone). That conversation has been incredibly important; in fact, without those initial conversations, I suspect that it would be much harder for the editors to write specification text (let alone text that would stand up to scrutiny).
While I would certainly like to see formal text materialize in the spec, it would be problematic to write that text prematurely.

Check links in my first message for a list of problems associated with the gap analysis that have been raised in the last few W3C Community Group calls that @kjetilk mentioned.
Important to note that 1 of 44 items were closed in the last milestone. The project board shows that although items were not closed they were advanced to some extent. Activity in the Specification repo opened some months ago has been remarkably low. There have been weekly W3C Solid Community Group, Editor, and Panellist calls but not all the members listed in the editor and panel roles have been attending these calls.

While I appreciate your input, @Mitzi-Laszlo, I can't find the relevance of the above to the changed process text in this PR (similar to @justinwb, it seems).
When asking for issues above, I wanted to know what was wrong with the process, and so far, no such description has showed up in this thread. I have read through all the links provided, but none of them seems to point out a specific aspect of the process that needs changing.
For example, the text above seems to hint at a problem of low activity, but @acoburn disagrees, so maybe it is not a problem. But even if it were, what would be the specific underlying problems with the process (if any)? There is also a mention of low attendance. However, is that a problem of the process? And what is that specific problem? Will the four-strikes-and-you're-out then help?

Summarizing, I really feel we are running blindly here. There is no list of problems to be addressed, no agreement on whether such problems exist or what they are, and no agreement on whether they are real problems.
As such, it's impossible to tell whether this PR makes things better or worse. Assuming the worst case for safety reasons, I strongly recommend to close this PR until we understand the problems. See this as a red pen / green pen thing: we can't possibly fix if we don't know what's wrong.

Ok - let's close this pull request and use the record of the gap analysis ( see issue,  20200102_1600CET minutes and 20200109_1000CET minutes)
following the milestone done by the community for future reference if need be.
Editors @RubenVerborgh @kjetilk @csarven @dmitrizagidulin @justinwb please can you define the next milestone.

I don't see the correspondence between what has been called gap analysis (a list of technical issues that need addressing) and problems with the process (which was put in place to ensure legitimacy of the outcomes). They are completely separate things. The implication would be that somehow the validation process—which is not a planning process—would have a relation to milestones, which is not the case. Retrofitting it to have that role, does not seem meaningful.
As such, I really do not know how to act upon the comment above, other than continuing what we were already doing. I would strongly suggest that we let editors self-manage, or let them execute a planning process that they themselves install.


Testing with new branch: fix-validate as the default branch which has state before commit 10d0561 in k/contributor-tweets

Provide the actual tweet content between the commented colons

Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)Heyy :)

now with char-off-limit

/validate

now within char-limit

/validate

its working


New package: WorkflowXLSX v0.1.0

Registering package: WorkflowXLSX
Repository: https://github.com/christiankral/WorkflowXLSX.jl
Created by: @christiankral
Version: v0.1.0
Commit: 59941d731265a15b68e78bb943df5511951dc53f
Git reference: HEAD
Description: Read and write physical quantities from XLSX files
Release notes:

Initial release

This doesn't look like it's meant for the general registry, just a couple of very specific convenience functions around XLSX.jl?

One could certainly see this as collection of convenience functions only. I agree.
Yet, I devloped this package with a clear work flow in mind for the application in egineering. So this package is not about just reading and writing certian cells from an excel file. Instead the following workflow is enabled for a calculation script in Julia:

An Excel spreadsheet is used to provide all the input parameters (including the physical unit) for a calulation with Julia based on Unitful: so the Excel file is "just" used to organize all the input data
Such an Excel file may look like:

For example, the function call XLSXreadvar(file,"U")  identifies where on sheet the variable U is stored, reads the physical quantity based on the number and unit located in the two cells located to the right of "U".
This way, for example, Ohm's law R = U / I can be applied in Julia based on real physical quanities, not just numbers.
The package WorkflowXLSX then also allows to write back the results to a copy of the Excel file.

The package WorkflowXLSX shall help to avoid calculations in Excel. Instead a calculation script can be created by an engineer with just little programming knowledge.

[noblock] Fair enough - with this more descriptive name I guess it's fine


fix(inline-diff): check for disposed state

Types

[x] 🐛 Bug Fixes

Background or solution
Changelog

/next

/next


session.userData doesn't gets refreshed

Once a session.userData is set,it persists even if I delete the conversation data. I tried "New conversation", "Delete User Data", Refresh Button, Reconnecting to the endpoint URL but nothing worked. Only restarting the emulator seems to do the trick. Also, this is an anomalous behavior and doesn't happen always. Am I missing some trick here?

Hi @PadmanavAgarwal,
The "Delete User Data" menu item doesn't do what it suggests. What it actually does is send an activity to your bot of type deleteUserData. It is up to your bot to handle this message in a way that makes sense to your application. The emulator's UI doesn't make that clear, but we'll improve this in the next release.
Now, when you go to implement a handler for the deleteUserData activity type, you will discover that the code necessary seems more complex than it ought to be. The designers of the Node SDK are aware of this and looking at ways to make it simpler. I'll paste an implementation that works today at the bottom of this message.
The C# SDK has a built-in command called /deleteprofile that will clear UserData and PrivateConversationData. Alas, the Node SDK doesn't have this, but in the code below I've included a Node implementation. The SDK designers are working together to iron out a more consistent story on this and other aspects of the two SDKs.
Here is some code to implement handling of the deleteUserData activity, and also implements a global /deleteprofile command (just for fun :))
// Clears userData and privateConversationData, then ends the conversation
function deleteProfile(session) {
    session.userData = {};
    session.privateConversationData = {};
    session.endConversation("User profile deleted");
}

// Handle activities of type 'deleteUserData'
bot.on('deleteUserData', (message) => {
    // In order to delete any state, we need a session object, so start a dialog
    bot.beginDialog(message.address, '/deleteprofile');
});

// A dialog just for deleting state
bot.dialog('/deleteprofile', function(session) {
    // Ok, now we have a session so we can delete the state
    deleteProfile(session);
});

// Creates a middleware to handle the /deleteprofile command
function deleteProfileMiddleware() {
    return {
        botbuilder: (session, next) => {
            if (/^\/deleteprofile$/i.test(session.message.text)) {
                deleteProfile(session);
            } else {
                next();
            }
        }
    };
}

// Install middleware
bot.use(deleteProfileMiddleware());

Finally, while investigating this issue I discovered a bug in the emulator: It turns out that session.userData state is getting shared between all bots! It should be per-user, per-bot. We'll get new emulator out this week with a fix for this.
Thank you for taking the time to report this!

Thanks for the detailed explanation. The provided fix seems to be working well to refresh user data.
Eagerly awaiting the session.userData state sharing bug fix !

A new emulator build is out with a fix for this (v3.5.25). If this doesn't address the issues you're seeing, please drop a comment here and we'll reopen.

If I don't use some deleteProfile middleware, the session.userData still persists across conversations.
For example, if I set the userData during a conversation like below,
session.userData.name = "Some-Name"
And then, check session.userData.name at the beginning of a "new conversation", it still has that value!
So, the "New conversation" probably refers to a new conversation with the same user (without refreshing the userData) and the custom delete profile middleware is the only way to reset the user data?

I confirm this issue is disturbing for new node bot SDK users

This is the correct behavior for session.userData. It should persist across conversations. You might try using session.privateConversationData instead.

The "new conversation" behavior is ok but the "deleteUserData" emulator button is not. The Emulator UI is misleading about what the expected behavior is.
If I see a button named "deleteUserData" build in the Emulator, I expect this to be a built in feature in the server/framework. Otherwise make it explicit that clicking on the button won't do anything by default unless I implement some code, or just remove the button and rely on users typing commands such as /deleteUserData and implementing ad hoc handlers.

@remydavid, I can see how deleteUserData can also sound like a built-in command. What actually happens is the emulator will send an activity to your bot of type deleteUserData. It is up to your bot to handle this activity type and delete user data in a way that makes sense for your application.

Is there an example of how to handle these activities in NodeJS?

@bondz Sample code to do this in NodeJS appears earlier in this thread. Have you tried it?
https://github.com/Microsoft/BotFramework-Emulator/issues/76#issuecomment-274636337

Oh. Replied via email. Seen it now, thanks.

I am facing the same issue. Any solution?


In channels list only a single channel should have an expanded menu

Description
Now that the channel list displays 3 different lists, each list has an independent expansion tracking. This means that you can have an expanded item for each list. This should change so that each time you expand an item on one of the lists, then any expanded area in the other lists collapses automatically.
Acceptance criteria

Tasks

[ ]

Story Points

We are currently discussing alternatives to the current structure with channels and tokens
@kelsos Please reopen, if you think, that it is still important right now and should be fixed soon.

Let's reevaluate it after the design update if it is still valid. But
closing it now makes sense to me.
On Thu, Oct 24, 2019, 12:50 PM christianbrb<EMAIL_ADDRESS>wrote:

We are currently discussing alternatives to the current structure with
channels and tokens
@kelsos https://github.com/kelsos Please reopen, if you think, that it
is still important right now and should be fixed soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/raiden-network/light-client/issues/212?email_source=notifications&email_token=AARKEJBMSYGRGNQPPLUB2TLQQF4XDA5CNFSM4IGFIWJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECETEDY#issuecomment-545862159,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARKEJCLTUQDROSWVISWAKLQQF4XDANCNFSM4IGFIWJQ
.


Added an Origin Check...

Not sure if this is the best way to accomplish it or not, but
added an Origin check to make sure it matches where you are expecting
your users to be coming from during the handshake.
Thanks for the great work!

Why localhost?


ORM Adapter: Bookshelf

Closing in favor of http://discuss.denalijs.org/t/request-for-addon-bookshelf-orm-adapter/91/1


Add issue template

Close https://github.com/outscale-dev/cluster-api-provider-outscale/issues/7

Close https://github.com/outscale-dev/cluster-api-provider-outscale/issues/7

Take a look at Issue form

Other than that, ok

@outscale-mdr I change the format base on your comment.


Update const.py

Country Turkiye added after it is successfully tested with  myPyllant.tests.generate_test_data

I added it as part of another change!


Add typescript definition related bits

[x] I have followed (at least) the PR section of the contributing guide.

@mgansler What problem are you trying to solve?

@oliviertassinari see related issue #14517

@mgansler Thank you! https://github.com/mui-org/material-ui/issues/14517#issuecomment-463230600

If you don't mind, I would like to repurpose this pull request to reapply #12662. It seems this change was lost: https://packagephobia.now.sh/result?p=%40material-ui%2Ficons%404.0.0-alpha.0.

@oliviertassinari I don't think it got lost, the package.json looks good to me. But I just copied the bits from the core package copy-files script to this one. I removed the line to copy the definitions file to the es/ directory.

@mgansler This should be fixed on next. Could you test with @material-ui/icons@next and report back what issue you have with the type declarations?
I'm not even sure we should publish typings for that one. I'm not sure if this is part of the public API.


Huge button on the page of adding new product

What
Huge button

Steps to reproduce the behavior
Add new product
Smartphone model

Device: iphone
OS: ios15

Fixed in #2028


Add Release CI

Adds CI for auto-releasing tags
Requires elevating rights for GH Actions for this repo before merging

worked here: https://github.com/idea404/zksolc-bin-test/actions/runs/6096088068/job/16540925427
Assumes new versions in all directories are all published at the same time / on the same commit to master/main branch

@idea404 please request a review from the devops team - they are managing our GitHub Actions.

Looks good to me


Print HTTP routes in stable order

When Spin prints:
Available Routes:
  this: http://<IP_ADDRESS>:3000/this
  that: http://<IP_ADDRESS>:3000 (wildcard)
  other: http://<IP_ADDRESS>:3000/other

the order is currently random.  This defeats muscle memory, and requires users to scan the whole list to find the one they're interested in.  (You scoff?  Try it on https://github.com/fermyon/developer/.)
The order should:

At minimum, be stable: not vary from run to run
Ideally, lend itself to searching, e.g. alphabetical, or most general prefix first and alphabetically by URL within that

I have a feeling it used to be stable and the randomness is a regression - I only started noticing this on the docs site recently but I could be wrong!

Looks like this was introduced sometime between Spin 1.0 and 1.1.  1.0 appears to use the order of components in the spin.toml file (which is fine).  1.1 appears to have the random order.

Okay this is the weirdest thing.  It looks like the randomness started when #1321 got merged.  But that's all about the Wasm component model, not anything to do with how we store Spin component metadata and HTTP routes, so seems unlikely!
@dicej I am sorry to bug you with what I worry is a false positive, but can you think of any way in which the CM work could have had this effect?

We're using an IndexMap to store routes which has a stable iteration order (i.e., it always iterates in the order items are added). So it seems like the issue is likely caused by how we're populating those routes. It looks like ultimately this comes down to how triggers are deserialized as part of a LockedApp. It would be interesting to test whether locked apps are being serialized in different ways or if the deserialization is not guaranteed to always result in the same order.

Yes, this was introduced as part of my component work.  The fix is pretty simple:
diff --git a/crates/trigger/src/lib.rs b/crates/trigger/src/lib.rs
index 175d6f9..4023244 100644
--- a/crates/trigger/src/lib.rs
+++ b/crates/trigger/src/lib.rs
@@ -8,6 +8,7 @@ use std::{collections::HashMap, marker::PhantomData, path::PathBuf};

 use anyhow::{anyhow, Context, Result};
 pub use async_trait::async_trait;
+use indexmap::IndexMap;
 use serde::de::DeserializeOwned;

 use spin_app::{App, AppComponent, AppLoader, AppTrigger, Loader, OwnedApp};
@@ -194,7 +195,7 @@ impl<Executor: TriggerExecutor> TriggerAppEngine<Executor> {
                     })?,
                 ))
             })
-            .collect::<Result<HashMap<_, _>>>()?;
+            .collect::<Result<IndexMap<_, _>>>()?;

         let mut component_instance_pres = HashMap::default();
         for component in app.borrowed().components() {

PR coming shortly.

@dicej  Oh, awesome.  Thank you!


How much time do you have ? To make or make + play ?

Some users ask me How much time do they have to make a game or make + play ? Maybe we could just add How much do you have to craft or sthing like this ?

The complicated part of this question is that “how much time it takes” depends on their skills and machines. If they know all machines super well and are super good then it is fast.
Maybe the right way will be to have a “level” option ?
Like : beginner, rookie, average, senior, super-hero
And people can level up as they build more games

On 12 Apr 2018, at 11:32, MaryPek<EMAIL_ADDRESS>wrote:
Some users ask me How much time do they have to make a game or make + play ? Maybe we could just add How much do you have to craft or sthing like this ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/ludobox/ludobox.github.io/issues/16, or mute the thread https://github.com/notifications/unsubscribe-auth/AAtXTqAKKplWtkGOU1Ul1KvQsimy4qLtks5tnx8rgaJpZM4TRcoW.

Ah ok... i don't know maybe just in the text something more specific like How much time do you have to craft a game or something like this ?


Drone authentication

hi
Is there any option for only connecting 1 repository to Drone and don't give access to entire our version control account ?
in team project everyone wants to see Pipeline so they should have my username and password for login to Drone App. and they see all of my repository. otherwise i should create account for my team and its not convenient
Or is there any option to login Drone app with username and password Instead using Github authentication?

I've asked this question on https://discourse.drone.io/


"image" element in the augmentation is required

Currently, you take size of the images with such code:

params.update({'cols': kwargs['image'].shape[1], 'rows': kwargs['image'].shape[0]})

But that is not always correct. What if user wants to have a list of images to augment as this one: {"image1": image1, "image2": image2}

Out of the box this library supports image augmentation only by one (probably with mask). If you want to augment a lot of connected images in absolutely the same way - consider writing your own targets but with same processing function.
In case you want to augment batch of images in different way - just use augmentations in Dataset and fill this Dataset to DataLoader.


Implement IOrganizationServiceAsync2

I'm trying to add DataverseClient to ASP.NET 7 Web API project, when following tutorials I noticed that there are Async operations in ServiceClient, but sadly they are missing in your library.
Take a look at this: https://taerimhan.com/implementing-oauth-2-0-on-behalf-of-flow-for-dataverse-custom-connector/
I noticed that ServiceClient implements an additional interface: https://github.com/microsoft/PowerPlatform-DataverseServiceClient/blob/dd3a3893d135bcb8c023e9d700824f2effd28786/src/GeneralTools/DataverseClient/Client/ServiceClient.cs#L42
any chance it might get implemented?

Yes, I'm working on this now.


Got compilation error

I've tried to use shrinker but got this on compilation:
Configuring library for shrinker-0.1..
Preprocessing library for shrinker-0.1..
Building library for shrinker-0.1..
[1 of 9] Compiling Shrink.Types     ( src/Shrink/Types.hs, dist/build/Shrink/Types.o, dist/build/Shrink/Types.dyn_o )
[2 of 9] Compiling Shrink.ScopeM    ( src/Shrink/ScopeM.hs, dist/build/Shrink/ScopeM.o, dist/build/Shrink/ScopeM.dyn_o )
[3 of 9] Compiling Shrink.Tactics.Util ( src/Shrink/Tactics/Util.hs, dist/build/Shrink/Tactics/Util.o, dist/build/Shrink/Tactics/Util.dyn_o )
[4 of 9] Compiling Shrink.Tactics.Safe ( src/Shrink/Tactics/Safe.hs, dist/build/Shrink/Tactics/Safe.o, dist/build/Shrink/Tactics/Safe.dyn_o )
[5 of 9] Compiling Shrink.Tactics.Tactics ( src/Shrink/Tactics/Tactics.hs, dist/build/Shrink/Tactics/Tactics.o, dist/build/Shrink/Tactics/Tactics.dyn_o )
[6 of 9] Compiling Shrink.Names     ( src/Shrink/Names.hs, dist/build/Shrink/Names.o, dist/build/Shrink/Names.dyn_o )
[7 of 9] Compiling Shrink           ( src/Shrink.hs, dist/build/Shrink.o, dist/build/Shrink.dyn_o )
[8 of 9] Compiling Shrink.PlutusTX  ( src/Shrink/PlutusTX.hs, dist/build/Shrink/PlutusTX.o, dist/build/Shrink/PlutusTX.dyn_o )

src/Shrink/PlutusTX.hs:26:9: error:
    • The constructor ‘SerializedCode’ should have 3 arguments, but has been given 2
    • In the pattern: SerializedCode _ maybePirByteString
      In a case alternative:
          SerializedCode _ maybePirByteString
            -> SerializedCode scriptBc maybePirByteString
      In the expression:
        case comped of
          SerializedCode _ maybePirByteString
            -> SerializedCode scriptBc maybePirByteString
          DeserializedCode _ maybePir -> DeserializedCode prog maybePir
   |
26 |         SerializedCode _ maybePirByteString -> SerializedCode scriptBc maybePirByteString
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cabal: Failed to build shrinker-0.1 (which is required by
test:gero-onchain-test from gero-gov-<IP_ADDRESS>, test:gero-gov-test from
gero-gov-<IP_ADDRESS> and others). See the build log above for details.

Maybe it's caused by plutus version mismatch.
we use on our project plutus: c8c5183f7facd967d48fe07b3b14465b8dd48fe7  (2021-12-27)

Yup that was a plutus version mismatch, sorry about that. it should be fixed in the latest commit 6cd3e on staging.


Update paper.md

Added an acknowledgement for Samantha Deane and the Kelp Forest Foundation (who helped us secure funding from the Moore Foundation)

@johnryantaylor merge?


Add description of rake commands that to PULL_REQUEST_TEMPLATE

I guess it is more kind to first time contributor.

👍


Make OWS Context document implementation compliant to standard and internal class naming consistent

The OGC OWS Context GeoJSON Encoding Standard 1.0 (14-055r2) was finalised and published 2017-04-06.
https://portal.opengeospatial.org/files/?artifact_id=68826
The current implementation in Backend and Webgui (from November 2016) rely on preliminary GeoJson results from Atom encoding mappings from OWS-10 TestBed working groups during the last years, before an official OWC GeoJson encoding was standardised. We are currently not supporting the ATOM encoding.
There are a couple of changes that have to be reflected in our implementation of OwcDocument and how it translates to JSON.  The issues need to be reconciled in the Backend, Webgui and CSW Ingester.

Referenced from: https://github.com/ZGIS/smart-csw-ingester/issues/32

Referenced from: https://github.com/ZGIS/smart-portal-webgui/issues/63

Referenced from: https://github.com/ZGIS/smart-portal-backend/issues/25

[x] Throughout the standard the "OWS Context document" is being referred to constantly, however, the implementing class from the OWS Conceptual Model is named: Class OWC:Context

[x] besides the updated attribute, the context and entry properties also can have a 0..1 date attribute: Date or range of dates relevant to the Context resource (timeIntervalOfInterest)

[x] check that we include the trailing slash in IRI context ids

[x] .features[i].properties.links.via 0..* : This element is optional and references an external resource from which the Context document is derived (e.g. metadata document from which the metadata of the resource is derived).

[x] .features[i].properties.links.alternates 0..* : Reference to a description of the Context resource in alternative format Array of link objects

[x] .features[i].properties.links.previews 0..* : Reference to a quick-look or browse image representing the Context resource Array of link objects. The element length SHOULD be provided

[x] .features[i].properties.links.data 0..* : Reference to the location of the data resource described in the Context resource Array of link objects

[x] 7.1.10 DataType links: The "links" array is not an array anymore. It is an Object that contains different "keys" like "via" or "profile". These are then arrays of objects. The current "rel" of the "OwcLink" is now the "key". So what we need is an OwcLinks class, that basically contains a "map[String, OwcLink]". (this might be a bit tricky to implement see: http://stackoverflow.com/questions/27732552/how-to-parse-json-with-variable-keys-in-scala-play

[x] Links can now also have optional lang and length. Owc document links has profiles and via. The via element is an array of link objects that contains four elements named type, href, title and lang

"links" : {
    "via" : [{
        "href" : "http://www.acme.com/collections/algal.xml",
        "type" : "application/xml ",
        "title" : "Algal XML metadata",
        "lang" : "en"
    }],
...

[x] .properties.links.profiles: The OwcDocument needs to have at least one link in its properties. Should look like

"links" : {
    "profiles": [{
        "href": "http://www.opengis.net/spec/owc-geojson/1.0/req/core",
        "title": "This file is compliant with version 1.0 of OGC Context"
    }],
...

[x] 7.1.8 the "generator" properties element is now an object OWC:Creator/OWC:CreatorApplication:

"generator" : {
 "title": "Web Enterprise Suite",
 "uri": "http://www.somewebside.org/WebEnterpriseSuite"
 },

.properties.display - "display" properties element 0..1 an object of OWC:Creator/OWC:CreatorDisplay:

[x] The list of OWC: Resource Class is mapped to an array of GeoJSON Feature objects (currently an array of our OwcEntry)

[x] the OwcEntry properties don't contain subtitle, but an abstract

[x]  .features[i].properties.active 0..1 : Flag value indicating to the client if the Context resource should be displayed by default (Boolean) Default value is ‘true’

[x] : .features[i].properties.folder

[x] .features[i].properties.offering 0..* : Service or inline content offering for the resource targeted at OGC compliant clients owc:OfferingType - IMPORTANT, Offerings are INSIDE the entry properties, not parallel

[ ] UploadedFileProperties - This should not be an offering but a link in "xz.features[i].properties.links.data[j]". See "<IP_ADDRESS> contentByRef" and it's example.

[ ] The HttpLink Offering is not needed. This GetFile thingy should be done by "xz.features[i].properties.links.data[j]"

[ ] Same goes probably for the "NetCdfOffering"

[x] we don't have styleSet .styles[k] Array of style sets owc:StyleSetType in Offerings

[x] we don't implement Owc:ContentType .contents[k] Array of contents (inline or byRef)
owc:ContentType, also: request .request and result .result are of type owc:ContentType ->  owc:Content elements

[x] If the href attribute is present, the element content SHALL be empty. If  href is not provided, content SHALL be provided
[x] type - .type: MIME type of the Content String type, not empty that contains a MIME media type. One (mandatory)
[x] URL - .href: URL of the Content URL Zero or one (optional)
[x]  a title - .title: Title of the Content String type, not empty Zero or one (optional)
[x] content - .content In-line content for the Content element String type, not empty that can
contain any text encoded media type Zero or one (optional)

[ ] author .properties.authors.name is array of obj {"name": "the name"} -> no OwcAuthors object anymore, no contributors array

[x] [ ] The UUID parameters that we need to save objects in the DB can (and probably should) be written to the JSON. See "<IP_ADDRESS> extension": "Any other element can be added to the JSON object as long as they do not clash with the elements names defined within table 1."

Explicit extensions were named throughout the standard:

<IP_ADDRESS> Extension OWC:Context owc:context.*

<IP_ADDRESS> extension OWC:Resource .features[i].properties.*

<IP_ADDRESS> extension OWC:Offering.*

<IP_ADDRESS> extension OWC:Operation .*

<IP_ADDRESS> extension OWC:Content  .*

<IP_ADDRESS> extension OWC:StyleSet

Released OGC OWS Context GeoJSON Encoding Standard https://bintray.com/allixender/ivy2/smart-owc-geojson/1.0.0


Flickering in version 1.0.7

I'm not entirely sure why line 41 which used to set
position: relative; was removed in release 1.0.7.
This change causes the pages to flicker for me. Could be related to some other css of mine but what exactly was the intention of this change?

I reverted the change in the 1.0.7 release, sorry for the mistake...


reverse-i-search not working in Repl

In the SBT repl CTRL + R searches backwards in the history, for example:

Enter Text

scala> val foo = 22

CTRL + R + f o will find and highlight the line, with this output:

(reverse-i-search)`fo': val foo = 22

RETURN accepts the choice

There's no reason this is missing, just nobody's implemented it yet. However, I am probably not the best person to implement this, as I'm not actually familiar with how this works. If anyone wants to take a crack at it, you can put it in https://github.com/lihaoyi/Ammonite/blob/master/terminal/src/main/scala/ammonite/terminal/ReadlineFilters.scala with the rest of the readline hotkey filters

Switching the frontend to use JlineUnix works as a workaround, but when I do that, what functionality am I missing?

You're missing

Multiline editing
Input-syntax-highlighting
Desktop-style Alt-{left, right} navigation, Shift-selection
Probably a few other things I don't remember off the top of my head

From the code of jline2, how reverse-i-search works seems quite simple. It just searches the most recent command that contains the given string. See https://github.com/jline/jline2/blob/8beae1a471aef17e4c721021ea4be3be918da37f/src/main/java/jline/console/ConsoleReader.java#L2844-L2864 and https://github.com/jline/jline2/blob/8beae1a471aef17e4c721021ea4be3be918da37f/src/main/java/jline/console/ConsoleReader.java#L3890-L3930 .
BTW, notice that there are a bunch of searching commands besides reverse-i-search in readline: http://www.delorie.com/gnu/docs/readline/rlman_15.html
Perhaps we should implement all of them?

Fixed in https://github.com/lihaoyi/Ammonite/pull/335


Consistent default VEGCOVER behavior across modes.

Created new values for veg parameter *_SRC options:

FROM_DEFAULT - primarily intended for VEGCOVER, to indicate setting to 1.0
FROM_VEGHIST - indicates that a veg parameter should take its value from the veg_hist forcing file(s)

VEGCOVER_SRC is now initialized to FROM_DEFAULT.
When VEGCOVER_SRC == FROM_DEFAULT, all vegcover values are set to 1.0.
When any of LAI_SRC, VEGCOVER_SRC, or ALBEDO_SRC == FROM_VEGHIST, their values are taken from the veg_hist forcing file(s).  This is not yet implemented in image mode.
Values of FROM_VEGLIB and FROM_VEGPARAM have the same behavior as before for classic mode (take values from the veg_lib or veg_parameter files, respectively).  For image mode, both of these values indicate to take values from the veg_parameter file, since all veg-related parameters are read from the veg_parameter file in image mode.  This can be modified later if desired.
Additionally, this commit removes all instances of "LAI_FROM_VEGLIB" and "LAI_FROM_VEGPARAM", as these were only present for backwards compatibility.
Similarly, this commit removes the logic in get_global_param() for handling "GLOBAL_LAI", as this also is only present for backwards compatibility.
closes #337

A little more explanation: the purpose of this commit is primarily to allow classic mode to turn off the vegcover feature.  Previously the default was to read vegcover from the veg library, which required the user to put vegcover values in their library.  Now, VIC can once again read a completely traditional set of input files that have no mention of vegcover anywhere.
In addition, this allows the user to more easily turn vegcover on/off and select the source of these values.  Previously, if the user specified veg_hist forcing files in the global parameter file, VIC would use them for LAI, VEGCOVER, and ALBEDO; the only way to turn that behavior off would be to comment out the lines in the global parameter file describing the veg_hist forcing files.  Now, the user only needs to change LAI_SRC, VEGCOVER_SRC, and ALBEDO_SRC to the appropriate "FROM_".  Furthermore, the user can now get different variables from different sources, e.g., LAI_SRC can = FROM_VEGPARAM while VEGCOVER_SRC can = FROM_VEGHIST, etc.

This looks pretty good @tbohn.  I just had a few comments on the handling of global parameter options.

@tbohn - can you pull in the latest develop branch here. The travis tests should pass now.

The image mode build failed, but all it says is that the node doing the compiling didn't return a status after 10 minutes, so we don't know what the error message was...

I re-triggered the build.  I think there is something going wrong with some of the travis nodes tonight because I've had this happen a few times recently.

Hey... it compiled!

Yep - this looks mostly done, after you resolve the merge conflicts, I'll take one last look.
Joe

This is strange.  I see the message about conflicts that must be resolved, but I can't seem to find those conflicts.  On the command line, I did a git pull from origin to bring the merge back to my workspace, but I don't see any merge conflicts there.  I wish the message here on GitHub had a link to a list of those conflicts...  Am I missing something?
Perhaps I should have done the merge on the command line and then, after resolving the conflicts, pushed to origin...

You want to merge in upstream/develop (e.g. UW-Hydro/develop).  Most likely your merge was attempting to reconcile conflicts with origin/develop (e.g. tbohn/develop).  Try git pull upstream develop.

OK, I resolved the conflicts in samples/global.param.sample.classic.txt.

@jhamman this is ready to go as far as I can tell.

Yep.  Looks good to me.  Merging now.

Thanks @jhamman !


Keep Getting "missing dot in first path element" Error Message When Trying To Install a Specific Package

What version of Go are you using (go version)?

$ go version
1.13

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
darwin/amd64

What did you do?

go get google/api/annotations.proto
What did you expect to see?
What did you see instead?
go get google/api/annotations.proto: malformed module path "google/api/annotations.proto": missing dot in first path element

I'm trying to install "google/api/annotations.proto" and keep getting:

go get google/api/annotations.proto: malformed module path "google/api/annotations.proto": missing dot in first path element
.
I installed go in the recommended way.
when I echo $GOROOT I get an empty result though in my "go env" variables it's set to "/usr/local/go":
GO111MODULE=""

GOARCH="amd64"

GOBIN=""

GOCACHE="/Users/amit/Library/Caches/go-build"

GOENV="/Users/amit/Library/Application Support/go/env"

GOEXE=""

GOFLAGS=""

GOHOSTARCH="amd64"

GOHOSTOS="darwin"

GONOPROXY=""

GONOSUMDB=""

GOOS="darwin"

GOPATH="/Users/amit/workspace/"

GOPRIVATE=""

GOPROXY="https://proxy.golang.org,direct"

GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"

GOTMPDIR=""

GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"

GCCGO="gccgo"

AR="ar"

CC="clang"

CXX="clang++"

CGO_ENABLED="1"

GOMOD=""

CGO_CFLAGS="-g -O2"

CGO_CPPFLAGS=""

CGO_CXXFLAGS="-g -O2"

CGO_FFLAGS="-g -O2"

CGO_LDFLAGS="-g -O2"

PKG_CONFIG="pkg-config"


fix: @warn_if_generator_is_not_consumed needs to allow next()

⚠  Relies on https://github.com/modal-labs/synchronicity/pull/94.
Turns out we weren't properly fulfilling the iterator protocol that is provided by a Python generator. So the decorator was changing the interface.
Will remove this gotcha affecting users: https://github.com/modal-labs/modal-examples/pull/267/files#diff-7d760443a54f6d0e66b1d1204a0cc9533d249f658501b557eea183cb76659635R57.

Just published latest main to synchronicity 0.4.2 on pypi

Nice!