Felix exception  doing resynch

Hits the exception below periodically. I hav two nodes calico-rh01 is combined control and compute, calico-rh02. rh02 does not have this log, rh01 does.
2015-06-05 10:41:09,070 [ERROR][1098/3] calico.felix.fetcd 321: Unknown etcd error 'Unable to decode server response: timed out'; doing resync.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/calico/felix/fetcd.py", line 282, in _wait_for_etcd_event
check_cluster_uuid=True)
File "/usr/lib/python2.7/site-packages/python_etcd-0.3.3_calico_2-py2.7.egg/etcd/client.py", line 357, in read
return self._result_from_response(response)
File "/usr/lib/python2.7/site-packages/python_etcd-0.3.3_calico_2-py2.7.egg/etcd/client.py", line 541, in _result_from_response
'Unable to decode server response: %s' % e)
EtcdException: Unable to decode server response: timed out
Followed by:
2015-06-05 10:41:09,071 [INFO][1098/3] calico.felix.fetcd 173: (Re)connecting to etcd. Old etcd cluster ID was e0c067710be719f2.
2015-06-05 10:41:09,072 [INFO][1098/3] calico.felix.fetcd 205: Polling aborted, doing resync.
2015-06-05 10:41:09,072 [INFO][1098/3] calico.felix.fetcd 190: Reconnecting and loading snapshot from etcd...
2015-06-05 10:41:09,072 [INFO][1098/3] calico.felix.fetcd 175: (Re)connecting to etcd. No previous cluster ID.
2015-06-05 10:41:09,072 [INFO][1098/3] calico.felix.fetcd 137: Waiting for etcd to be ready...
2015-06-05 10:41:09,072 [INFO][1098/3] urllib3.connectionpool 257: Starting new HTTP connection (1): localhost
2015-06-05 10:41:09,078 [INFO][1098/3] calico.felix.fetcd 155: etcd is ready.
2015-06-05 10:41:09,081 [INFO][1098/3] calico.felix.fetcd 215: Loaded snapshot from etcd cluster e0c067710be719f2, parsing it...
2015-06-05 10:41:09,083 [INFO][1098/3] calico.felix.fetcd 252: Snapshot parsed, passing to update splitter
2015-06-05 10:41:09,084 [INFO][1098/7] calico.felix.splitter 61: Applying snapshot. STAGE 1a: rules.
2015-06-05 10:41:09,084 [INFO][1098/7] calico.felix.splitter 64: Applying snapshot. STAGE 1b: tags.
2015-06-05 10:41:09,084 [INFO][1098/7] calico.felix.splitter 71: Applying snapshot. STAGE 2: endpoints->endpoint mgr.
2015-06-05 10:41:09,085 [INFO][1098/7] calico.felix.splitter 77: Applying snapshot. DONE. 5 rules, 5 tags, 4 endpoints
2015-06-05 10:41:09,085 [INFO][1098/7] calico.felix.splitter 85: No cleanup scheduled, scheduling one.
2015-06-05 10:41:09,085 [INFO][1098/8] calico.felix.profilerules 63: Rules manager applying snapshot; 5 rules
2015-06-05 10:41:09,085 [INFO][1098/8] calico.felix.profilerules 75: Rules for profile 6348aba3-e010-4a3a-b5fb-53930e29b2b4 updated.
2015-06-05 10:41:09,085 [INFO][1098/8] calico.felix.profilerules 75: Rules for profile 109c0510-1a5c-4b4a-90c8-b827acc250eb updated.
2015-06-05 10:41:09,085 [INFO][1098/8] calico.felix.profilerules 75: Rules for profile 6945f875-a515-4e2c-85c4-9b915a803976 updated.

Triggering the resync looks like another instance of https://github.com/Metaswitch/python-etcd/issues/6.  That timeout should be passed up to our code but it's getting caught and wrapped so our code resorts to a full resync.
OTOH, should we be hitting a timeout here?  Was there anything going on that might have caused the timeout from etcd?

I don't think there was a reason for the timeout. This node was controll + compute, so plugin was writing, and felix reading. The other (compute only) node didn't see any issues.

@DaveLangridge does that mean that you were directly connected to the etcd master, rather than a proxy?

No etcd restarts or anything?  I can repro that by hitting etcd with a SIGKILL, but only when I'm directly-connected.

Yes. Plugin and felix both on calico-rh01 directly connected to ectd master.

@DaveLangridge what's the impact of this now we've fixed the python-etcd bug?  I'd expect a log saying there was a timeout but it shouldn't resync.

Its now just logging the following every 90s:
2015-03-03 11:13:42,968 [INFO][30133/3] calico.felix.fetcd 199: (Re)connecting to etcd. Old etcd cluster ID was afacd66dd456fea3.
2015-03-03 11:13:42,968 [INFO][30133/3] urllib3.connectionpool 257: Starting new HTTP connection (1): localhost
No exception, so closing.


Flow 0.60[.1] breaks IDEs (at least Atom and WebStorm)

Atom works with 0.59 but not with 0.60:
https://stackoverflow.com/questions/47599966/cant-get-flow-working-with-atom
WebStorm works with 0.59 but not with 0.60:
https://youtrack.jetbrains.com/issue/WEB-30020

It seems it's already fixed. Hope they release flow-bin soon. cc @calebmer

@lll000111  are you able to get flow working webstorm for 60.1? I am getting "Error: process terminated" in Web Storm. I was getting same error as you for 60.0

@lvdang I was suspicious of that tiny patch (I looked at the change in 0.60.1) and it indeed does not address this issue.

v060.1 and IntelliJ IDEA 2017.3 (Ultimate Edition) Build #IU-173.3727.127
seeing the same problem,.

Downgrade not work for me, WebStorm 2017.3 Build #WS-173.3727.108

RubyMine Build #RM-173.3727.132. I tried Flow 60, 59 and 55, none worked.

@Meeeeow @evrimfeyyaz Pls. define "does not work". This does not look like this particular problem I reported right here, which only occurred from 0.60. Check the linked error descriptions.

@lll000111 Updated, but useless, i can't reproduce it in command line, looks like a bug of JetBrains IDE itself

@Meeeeow Consider adding to the linked WebStorm ticket. Check if there is anything in the log (Help => Show Log in Explorer => ìdea.log`).

@lll000111 My bad, it's looks like another bug of WebStorm. it can't understand OCaml regular expressions in .flowconfig?
.*/node_modules/.*

@Meeeeow I'm not sure WebStorm reads .flowconfig. I don't think it does.

Both 0.60.0 and 0.60.1 are broken in Atom and WebStorm for me as well. 0.59.0 works fine.

I wonder if Facebook/Flow developers are aware of this issue. If they are using IJ or WebStorm with v60.0 and v60.1, the Flow developers should also see this issue.

Atom works for me. With Nuclide.

https://youtrack.jetbrains.com/issue/WEB-30020

@lvdang

your URL is broken (the text is okay, the underlying link is not)
that link already is at the very top in my very first post

thanks for clarification

I can also confirm that this breaks with 0.60.0 and 0.60.1 with latest WebStorm version 2017.3:
WebStorm 2017.3
Build #WS-173.3727.108, built on November 25, 2017
JRE: 1.8.0_152-release-1024-b6 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.1

FYI: The state of the WebStorm ticket has been changed to "fixed" (there is no new version available yet, obviously, probably in an upcoming EAP and then a patch for 2017.3).

I updated v61.0 still getting: Error:Timeout on starting language service process
with latest WebStorm. Hopefully WebStorm has patch to fix this issue.

WebStorm has released an update https://confluence.jetbrains.com/display/WI/WebStorm+173.3942.31+Release+Notes
Works for me with Flow 0.60.1

I'm closing this issue because it's been working with the last few Webstorm releases (incl. EAPs). the remaining issue #5583 is Flow crashing regularly (on Windows systems at least) which the IDE can do nothing about.

I chose a different node version in the ESLint settings panel of WebStorm and now it works fine again.


Disable method is not working for extensions

I tried to use the disable method on an extension but cannot get it to work. It just disables all logging. Could you please provide an example? Thanks!
import { logger, consoleTransport } from "react-native-logs";

const config = {
  transport: consoleTransport,
  enabledExtensions: ['ROOT','HOME']
};

var log = logger.createLogger(config);
var rootLog = log.extend('ROOT');
var homeLog = log.extend('HOME');

log.disable('HOME');
log.disable(homeLog);

rootLog.info('Magenta Extension and bright blue message');
homeLog.error('Green Extension and bright red message');

Sorry, I'll fix this in the next few days

Fixed in ver 4.0.1, see the example in the README.


Deleting redundant folders and files

https://github.com/msenin94/mk-post-deployment-checks/issues/40

@msenin94 Need your review. Please)


update ko.json

ko translation update please

Found at 225
225    "focusOnFile": "Focus on file search inptut",
input? inptut?

Should be input -- I'll fix now

thanks!

Thank you for the translation and for catching the misspelling 😅 fixed with https://github.com/whyboris/Video-Hub-App/commit/d4ed3040b2b444c7595486a5ba694dfbd7015092
I fixed it in all the files, but I suspect I should re-translate this line in all other languages at some point later 😅


Move domain handling logic to common package

Coverage decreased (-0.5%) to 67.921% when pulling a17d83213967f4f78c842cd3e6b1c7b2fa9f0035 on domain-moving into d29385fb421de820d89e4f630f071990f106733b on master.


Add backend healthcheck functionality

Creates route that will be called by load balancers, skips backends that don't have a check function. Includes the first implementation of a check for sproxyd for each backend option.
Depends on sproxydclient PR https://github.com/scality/sproxydclient/pull/92

@ironman-machine do it, jarvis

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6139 for CI status.

@ironman-machine again plz

Hello @dora-korpar
Sorry, but this PR cannot be merged in this state, please rebase it on the master branch

Hello @dora-korpar
Sorry, but this PR cannot be merged in this state, please rebase it on the master branch

@ironman-machine attack

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6159 for CI status.

@ironman-machine one mo time

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6163 for CI status.

There was a problem with the http request path being passed to sproxydclient, which was fixed in https://github.com/scality/sproxydclient/pull/93

@ironman-machine blast off

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6211 for CI status.

@ironman-machine holy moly let's go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6223 for CI status.

@ironman-machine work it

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6231 for CI status.

@ironman-machine seriously

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6259 for CI status.

CI was hanging because of bug fixed here: https://github.com/scality/Federation/pull/720

@ironman-machine now that the problem has been fixed

Hello @rahulreddy
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6263 for CI status.

@ironman-machine gogogogo

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6264 for CI status.

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/deep-healthcheck", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6265 for CI status.


Draft: support apple metal framework to compute graph

Library setting

Add new metal setting in CMakeLists. (follow the CMakeLists.txt in llama.cpp)

Update Functions for metal support.

Set initial metal context in load model weight (maybe initial at rwkv.cpp)
Add buffer data from the context built from original graph in rwkv_graph
Add new compute_graph for metal in rwkv_eval
Update operations for metal can use in rwkv_operators. (because many ggml_op cannot compute in metal, and I found the max function cannot be re-write from other ggml-functions for metal backend can be supported.)

#134

Hi @fann1993814, thanks for implementing this!
I've tested this with model: RWKV-5-World 7B (RWKV-5-World-7B-v2-OnlyForTest_49%_trained-20231114-ctx4096-Q4_0)
I've converted it to ggml FP16 (FP32 too) and then quantized to Q4_0.
Apple M2 16GB (8 cores)
I'm getting the following error:
rwkv.cpp % python python/chat_with_bot.py RWKV-5-World-7B-v2-OnlyForTest_49%_trained-20231114-ctx4096-Q4_0.bin

System info: AVX=0 AVX2=0 AVX512=0 FMA=0 NEON=1 ARM_FMA=1 F16C=0 FP16_VA=1 WASM_SIMD=0 BLAS=1 SSE3=0 VSX=0
Loading RWKV model
ggml_metal_init: allocating
ggml_metal_init: found device: Apple M2
ggml_metal_init: picking default device: Apple M2
ggml_metal_init: loading '/rwkv.cpp/ggml-metal.metal'
ggml_metal_init: loaded kernel_add                            0x15732b230 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_add_row                        0x16083e7f0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul                            0x16083e9e0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_row                        0x16083ebd0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_scale                          0x16083edc0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_silu                           0x16083efb0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_relu                           0x16083f1a0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_gelu                           0x16083f390 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_soft_max                       0x16083f580 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_soft_max_4                     0x16083fb80 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_diag_mask_inf                  0x160840160 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_diag_mask_inf_8                0x1608408b0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_f32                   0x160840ee0 | th_max =  896 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_f16                   0x160841510 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q4_0                  0x160841b40 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q4_1                  0x160842170 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q8_0                  0x1608427a0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q2_K                  0x160842dd0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q3_K                  0x160843400 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q4_K                  0x160843ba0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q5_K                  0x1608441d0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_get_rows_q6_K                  0x160844800 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_rms_norm                       0x160844e40 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_norm                           0x157209fb0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_f32_f32                0x157235030 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_f16_f32                0x160845500 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_f16_f32_1row           0x160845e00 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_f16_f32_l4             0x1608467e0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q4_0_f32               0x157f66db0 | th_max =  896 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q4_1_f32               0x157f675f0 | th_max =  896 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q8_0_f32               0x157f67e20 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q2_K_f32               0x160846da0 | th_max =  640 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q3_K_f32               0x160847360 | th_max =  576 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q4_K_f32               0x160847a40 | th_max =  576 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q5_K_f32               0x160848120 | th_max =  640 | th_width =   32
ggml_metal_init: loaded kernel_mul_mat_q6_K_f32               0x160848800 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_f32_f32                 0x160848f90 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_f16_f32                 0x160849720 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q4_0_f32                0x160849eb0 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q8_0_f32                0x16084a640 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q4_1_f32                0x16084add0 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q2_K_f32                0x16084b560 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q3_K_f32                0x16084bcf0 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q4_K_f32                0x16084c480 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q5_K_f32                0x16084cc10 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_mul_mm_q6_K_f32                0x16084d3a0 | th_max =  768 | th_width =   32
ggml_metal_init: loaded kernel_rope                           0x16084d990 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_alibi_f32                      0x16084e4e0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_cpy_f32_f16                    0x16084ecf0 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_cpy_f32_f32                    0x16084f500 | th_max = 1024 | th_width =   32
ggml_metal_init: loaded kernel_cpy_f16_f16                    0x16084fd10 | th_max = 1024 | th_width =   32
ggml_metal_init: hasUnifiedMemory              = true
ggml_metal_init: recommendedMaxWorkingSetSize  = 10922.67 MB
ggml_metal_init: maxTransferRate               = built-in GPU
ggml_metal_add_buffer: allocated 'weight_data     ' buffer, size =  4805.00 MB, ( 4805.50 / 10922.67)
ggml_metal_add_buffer: allocated 'serial_computer_buffer' buffer, size =   273.22 MB, ( 5078.72 / 10922.67)
Loading World v20230424 tokenizer
Processing 178 prompt tokens, may take a while
ggml_metal_add_buffer: allocated 'sequential_computer_buffer' buffer, size =  2896.44 MB, ( 7975.16 / 10922.67)
ggml_metal_graph_compute_block_invoke: node   2, op =   REPEAT not implemented
GGML_ASSERT: /rwkv.cpp/ggml/src/ggml-metal.m:1265: false
ggml_metal_graph_compute_block_invoke: node 2285, op = MAP_CUSTOM1 not implemented
GGML_ASSERT: /rwkv.cpp/ggml/src/ggml-metal.m:1265: false
ggml_metal_graph_compute_block_invoke: node 4571, op = MAP_CUSTOM1 not implemented
GGML_ASSERT: /rwkv.cpp/ggml/src/ggml-metal.m:1265: false
ggml_metal_graph_compute_block_invoke: node 6855, op = MAP_CUSTOM1 not implemented
GGML_ASSERT: /rwkv.cpp/ggml/src/ggml-metal.m:1265: false
zsh: abort      python python/chat_with_bot.py

Any idea?

@fann1993814

Hi @fdagostino , this pr is not ready.
because I don't know how to implement the some operations into metal.
Operation is just like tensors compute ADD or SUB...
Some of Operation are too difficult to implement (REPEAT, or SER, also include RWKV_v5_wkv...)
Maybe can need ask @saharNooby how to implement...?

Can't ggml just not use Metal for simple operations like ADD, SUB, etc. -- the same way it is for GPU offloading?
I'm afraid I would not be able neither implement, nor help with implementing operations for Metal -- among other reasons, I don't have a Mac.
The situation may change with the next ggml update in rwkv.cpp, but this is unlikely.

Hi @saharNooby
Can't ggml just not use Metal for simple operations like ADD, SUB, etc. -- the same way it is for GPU offloading?

Metal need to be implemented kernel functions, you can see those functions in src/ggml/ggml-metal.metal
It's different with cuda (cublas), because it only focus on BLAS computing. (Maybe Matrixs gems,...,..)
Metal is not just BLAS, It support all the operations for General-Purpose computing.
A graph need to be translate ggml-operations to metal-related operations.
Otherwise, metal runtime cannot understand how to do.
Implement kernel functions is  simply like SUB/DIV/SQT or some custom operation SIGMOID/OneMinusX.
However, REPEAT/SET/WKV_for_v5 are difficult to me.
I hope I do not modify ggml, but I have no idea to deal with this problem.
New sgml support CoreML, maybe use it without thinking how to make work-around with metal.
The situation may change with the next ggml update in rwkv.cpp, but this is unlikely.

I know your concern, so I stop it in this moment.
It need to be consider a long term progress.


[FLINK-29301] Publish flink-ci-tools

Publish the java-ci-tools (after renaming them to flink-ci-tools) so that external connectors can also use it for license checks etc.
Additionally fixes a few issues about resources and modules skipping deployments to make it usable outside the Flink repo / CI.

Overall the code in licensecheck/NoticeFileChecker.java is complex enough that I'm wondering how we know for sure that it works. Are there tests somewhere?

We don't really have tests for NoticeChecker, however one can infer the correctness from the logging output on CI: https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=41020&view=logs&j=52b61abe-a3cc-5bde-cc35-1bbe89bb7df5&t=54421a62-0c80-5aad-3319-094ff69180bb
If the parsing of modules from the build output is broken then this line shows it:
...Extracted 157 modules that were deployed of which 48 bundle dependencies with a total of 779 dependencies
For finding the NOTICE files we got:
... Found 44 NOTICE files to check
If the parsing of dependencies from the build output is broken, then we get warnings for all modules.
If the parsing of dependencies from NOTICE is broken, then we get errors for all modules.
Finally, if the comparison of the dependencies between NOTICE/build-output is broken then either everything fails or no warnings are logged.


BotConnector code block formatting issue

I'm using BotConnector with Slack and I'm running into some formatting issues specifically with code blocks. I append and prepend the code block with the triple backticks as I'm supposed to for Slack, but this results in weird behaviour. Often times, it messes up the indentation and the newlines. Sometimes it does not give me the message in a code block at all.
Here's an example:
The raw text sent looks like this:

Result in Slack (BotConnector):

I switched from BotConnector to the native BotKit library for Slack and it gives proper formatting (still using BotBuilder though).

Could be an issue with BotConnector adding additional encoding.

Looks like a bug.  We'll investigate

Anthony, can't repro.  One thing to remember is to use a double "\n" for a new line.
This:
"#code comment\n\nFor element in sequence:\n\n#code to perform\n\n# Loop behavior\n\nFor each\n\n# Code to execute\n\n"
Results in:


feat: Login email skeleton design

https://app.asana.com/0/1206415573081293/1206415573081355/f

Good

Hello there how are you


Add leave page confirmation dialog to language edit form

This addresses issue #391 to add a confirmation dialog box before navigating away from the language edit form.
It seemed pretty straight-forward so I threw this together. It just adds a "dirty" check like mentioned in the issue and forces a confirmation on the beforeunload event if any of the form fields have been changed.
Notably, I had to disable the popup for the save button as well as the delete button so it can use it's own (less generic) confirmation dialogue.
It passed all current tests, but I haven't added any new ones yet. Are there any particular smoke/acceptance tests you'd like me to add @jzohrab?

Hi @cblanken - thanks very much!  Re extra testing, let's go with this as-is, since it's so small.  Hopefully that doesn't come back and create problems later :-)  As long as the existing tests pass, we're good to go.

Launched in 3.5.0. :tada:


Module system

Add as special forms a way to provide and require files from a script
For example:
;; sort.scm
(provide sort)
(define (sort lst) ...)

(require "sort.scm")
(sort (list 6 3 5 4 1 2)) ;; '(1 2 3 4 5 6)

Only functions provided by one file should be available in a file that requires them.

You should read this: https://www.cs.utah.edu/plt/publications/macromod.pdf. (I’m thrilled with what you’re doing here!)

Thanks! My first attempt at modules actually failed for some of the reasons described here (macro expansion was not playing nicely!). I'll take a look at this and hopefully it can help fix those problems


[PIX-LINK A10] PIXA-123456-GYFDP protocol reversing

Documenting my findings here for a camera that is likely a derivative of pppp in case a dissector can be made.
Device: Aliexpress camera https://www.aliexpress.com/item/1005006054720973.html (PIX-LINK A10)

has a BK7252 (verified inside, pictures pending).
apk can be downloaded from: https://qr01.cn/E3BMyh
apk name is "shix.pixlink.camera".
apk contains libobject_jni.so which appears to be similar to libpppp, since it contains functions such as cs2p2p_PPPP_Initialize and cs2p2p__P2P_Proprietary_Decrypt("SSD@cs2-network.",...) which appears on the internet at least here and here.
PPPP_SIMPLE_SHUFFLE table is the same in the apk's .so as here.
Default camera password is SHIX_DEFUALT_PWD = "6666" (DEFUALT is not a typo)
did is of format PIXA123456GYFDP (only numbers changed)

Tested on non-direct mode (aka connected to WiFi AP):

Traffic is different to pppp-dissector's: every packet starts with 0x9f instead of 0x2c (both directions). Opcodes do not match if the magic packet alone is changed.
The device keeps on broadcasting a UDP packet IP <IP_ADDRESS>.11007 > <IP_ADDRESS>.0: UDP, length 48 with payload starting with 0x9f 0x83 0x24 0x22 .... (payload does not change between broadcastings).
Simulating offline mode by blocking phone and the device prevents connecting to the device. (Speculation: maybe DNS also needs to be blocked, will keep on testing.)

Intercepted with jnitrace and frida-gadget. Phone is sending json messages to the .so for some commands (might be towards cloud, still learning jnitrace):
{"pro":"set_cypush","cmd":1,"user":"admin","pwd":"1234","pushIp":"<IP_ADDRESS>","pushPort":9093,"pushInterval":180,"cyAdmin":"admin","cyPwd":"admin123","isPushPic":1,"isPushVideo":1}
{"pro":"set_datetime","cmd":126,"user":"admin","pwd":"1234","time":1699723191,"tz":-7200}
{"pro":"get_parms","cmd":101,"user":"admin","pwd":"1234"}

Called functions according to jnitrace: PPPPMsgNotify, CallBack_H264Data, SearchResult. Likely similar SDK.
getServer() (StartPPPP?) has likely decryption key at least for some traffic:
if(strcmp("PIXA", vendorstring_or_something))
  {
    return "EIHGFNBBKAIEGEJLELHBFEELGDNNGBMIHFFMAPDMAAJEKEKPDLAJDPPKGALBIBLAAENOKNDAOFNFBICNIF:SHIX";
  }

Keys also exist for XIAODOU and MANY others.

Interesting. :) This sounds very similar to the app my camera ("vi365") is using. The APK contains a libobject_jni.so which matches your description. The string "shix" (or "SHIX") is all over the place.
The json commands you are seeing are sent using DRW packets on channel 0. I'm currently working on documenting the set of commands available on my camera, but your examples matches 100% my camera.
That your packets start with 0x9f means the encryption is different. Before decryption, my packets all begin with 2c.
The broadcast packet which you say is 0x9f 0x83 0x24 0x22 is for me 0x2c 0xba 0x5f 0x5d. After decryption, it becomes 0xf1 0x30 0x00 0x00.

I honestly have not spent much time on the decryption; I found the algorithm + tables in a javascript linked from a Home Assistant forum, and it Just Worked. But if you found the same table as the keytable array in the dissector, then maybe it is the four byte dec_key that is incorrect?

I have not been able to find the four byte key in the dissector indeed. Will continue investigating later.
Trying to decompile the broadcast packet with the "v4 encryption" (correct<EMAIL_ADDRESS>string which might be the key but with extra steps) gives "\xdf\xd1\xf4\x0e" which does not correspond at least to your decrypted example.
Reading the ha thread more I tested shix.cy.camera and it also works and the app appears more polished, also asking for WeChat cloud payments. "Check FwVer" only has a slider and appears to not do anything (did not check logcat or network traffic yet), bummer.
Forgot to add that the camera is called "CYCAM_VM191p_v85_0729" in both apps and that string appears to come from inside the camera. The camera has JTAG test points and the usb port cannot be used for UART as the data pins appeared to not go into the PCB, will recheck when I open it again.

More findings to prevent others from straying to wrong paths: The EIHGFNB... string is just an encoded string for server IPs for each vendor (apparently decoded by PPPP_DecodeString).
This online decoder has the same EIHGFNB...SHIX string as my PIXA.

The "v4 encryption" link was enlightening. It gives an algoritm how the dec_key (they call it seed; a much better name; I'll update my dissector to use it) is calculated from the string "camera". I can see the<EMAIL_ADDRESS>being used as the seed string in the APK, but I think this is only when encrypting for when doing P2P calls, not for device/controller communications.
You can try setting dec_key = { 0x97, 0x69, 0xd6, 0x5b } (that's the dec_key/seed for<EMAIL_ADDRESS>in the lua and see if you get any sane values out.

I think I got it! I believe your camera has "SHIX" as the seed string. If that is correct, then you should use dec_key = { 0x3c, 0xc4, 0x68, 0x0a } in the lua script. Try it, and see if you can get decrypted packages beginning with 0x1f.

Thank you! With that the broadcast becomes
PPPP Packet (encrypted)
    Decrypted Packet: f112002c....
PPPP Packet (MSG_DEV_LGN_CRC)
    Magic Byte: 0xf1
    Opcode: 0x12 (MSG_DEV_LGN_CRC) <- ???
    Payload Length: 44 <- CORRECT!!!
    Payload: 9097...
PPPP Payload

...this opcode leads to another presentation I'll have to digest another weekend.
In the code cs2p2p_gP2PKeyString (set in PPPP_Initialize()) indeed appears to be derived from the EIHGFNB...:SHIX value, which appears to be SHIX.

There is a huge getServer() function that returns ":" for all possible prefixes. I'm trying to extract those values into something usable.
The opcode MSG_DEV_LGN_CRC has something to do with how the device sets up P2P communication over the Internet. I'm guessing it is being sent to an external server. I highly recommend you block UDP port 32100 for outgoing traffic to avoid this. (And/or block the entire device from accessing Internet at all...)

Indeed I had a MSG_DEV_LGN_CRC instead of MSG_HELLO which I now got after restarting the camera.
I blocked the device from internet except for DNS but it is still sending the CRC messages and a hello ever 10 seconds even after mode button "reset" and wifi ap reconnect.
It can be made connect to the wifi again but it will not be connectable by the app, I'll try blocking the phone also. I'll check the pure p2p mode next if for example the A9_PPPP example would work with this camera.
Just to confirm:
PPPP Packet (MSG_HELLO)
    Magic Byte: 0xf1
    Opcode: 0x00 (MSG_HELLO)
    Payload Length: 0

You might have some success with A9_PPPP but you need to update the four seed key bytes.
For me, I had a lot of success by factory resetting the camera to force it to AP mode, and then letting my phone connect to the AP with the app, and setting my laptop in monitor mode and sniffing the AP SSID. This way it stayed off internet, but I could do basically everything (except sending push notifications on motion detected which are done by the camera to an external http server).

(The nice thing is though that the controller tells the camera which ip and port to send the push notifications to, so I'm basically planning to tell it to send it to my Home Assistant server on a port I chose, and use that to get motion detection from the camera, without having to go on the external internet).

More testings: VI365 does not find the device in AP mode at all, so only CY365 works.
Monitor mode says that all packets are identified (and the messages look sane: MSG_HELLO, MSG_DRW followed by MSG_DRW_ACK, etc) so this ticket can likely be closed :)
Commands are decoded nicely from the monitor traffic also:
PPPP Command Channel
    Command Block
        Command Flags: 0x060aa080
        Command Length: 181
        Command: {"pro":"set_cypush","cmd":1,"user":"admin","pwd":"6666","pushIp":"<IP_ADDRESS>","pushPort":80,"pushInterval":180,"cyAdmin":"admin","cyPwd":"admin123","isPushPic":1,"isPushVideo":0}
    Command Block
        Command Flags: 0x060aa080
        Command Length: 89
        Command: {"pro":"set_datetime","cmd":126,"user":"admin","pwd":"6666","time":1699822878,"tz":-7200}
PPPP Command Channel
    Command Block
        Command Flags: 0x060aa080
        Command Length: 293
        Command:{
	"cmd":	101,
	"result":	0,
	"time":<PHONE_NUMBER>,
	"stream":	0,
	"icut":	0,
	"power":	100,
	"charging":	1,
	"sysver":	"CYCAM_VM101P_v85_0729",
	"server_ver":	"",
	"upgrade":	0,
	"rotmir":	4,
	"lamp":	1,
	"isShowIcutAuto":	1,
	"bright":	4,
	"contrast":	2,
	"rate_bit":	26,
	"sensor":	"HI0704"
}

Interestingly the HI0704 sensor ID does not appear in github or on the internet.
Also indeed no UART on this one, damn:

What kind of controls do your app offer you? For my camera, I can change pan, tilt, IR-mode on/off and flashlight on/off. I can look at video and listen to audio (although I'm just getting static, don't know if that is a software problem, a defect unit, or just that the sellers lied about the hardware capabilities), and finally I can send output to a speaker on the camera.
If you have anything like this, I'd be interested in seeing the corresponding cmd messages and their replies for activating these functions.

(Btw, the VI365 app is likely hard-coded with the "camera" PSK, so I'm guessing it will not even send a proper discovery packet for your camera.)

Appears that it is just mjpeg. For better or worse A9_PPPP works with the following changes, will make a basic PR there eventually unless someone else is faster:
node run.js -t <IP_ADDRESS> -b <IP_ADDRESS>

  sendBroadcast() {
    const message = Buffer.from('9fa1eeb9', 'hex')
/*PPPP Packet (encrypted)
    Decrypted Packet: f1300000
PPPP Packet (MSG_LAN_SEARCH)
    Magic Byte: 0xf1
    Opcode: 0x30 (MSG_LAN_SEARCH)
    Payload Length: 0
*/

const key = [0x3c, 0xc4, 0x68, 0x0a]

Commands: No flashlight, irmode led toggle works (it appears to be 940nm instead of 850nm so I can't see for example HTC lighthouse light emissions with it, clever design to not really need ir-cut it seems), I can flip stream but no pan/tilt, can change definition (likely still not h264, latency is too low and cannot see h264 artifacts). I will try your PR soon(ish).

Can you capture and post here the json commands and responses sent when you execute this functionality on the app?

Confirmed sendCMDIr() working both directions but need to spam it greatly.
For both requests I get a reply:

{
        "cmd":  102,
        "result":       0
}

So "just" need to implement a retry system since the UDP packet loss can be great.
Also the stream stops until I restart run.js so something else is still missing also in retry logic.

I gave up a bit on my camera and am considering buying a new, better, so I kind of lost interest a bit. :-(
But yes, agree, the packet loss is huge. For me, a "make it or break it" thing was the motor control. Idiotically enough, it is implemented not as "tilt camera X degrees up", but as "start motor upwards motion" and "stop motor upwards motion". Works great when you have intermittent packet losses. NOT! :-( So getting the camera in position is like a huge patience challence game, taking minutes. And if the power is cut, the camera goes back into the "reset" centered position. After the second unplanned blackout at our house this week, I haven't cared to put it back in position.
Also, as you say, the stream stops after a while. It seem to be close to exactly 5 minutes for me. I'm guessing you need to spam some kind of "keep alive, please" packets from the controller to the device, and that the camera shuts down if it has not received these for a while. Or, in worst case, it is just that too many RWD_ACK packets are lost, and we need to be even more aggressive in spamming those.

My long-term plan was to reimplement this in python, since my ultimate goal is a Home Assistant integration. However, I started in the other end, by seeing how I can even write a HA integration, and I did not even get to the part where I could get the configuration to work before I got scared away by the complexity. :(
I do think that the way forward, if this is to be ever properly supported, is to build this properly layered, with a low-level transport layer, which deals with opening connections, keeping them alive, ack:ing and resending packets, and a high-level application layer, that sends commands and interpretes the video and audio stream. The current code in A9PPPP is just mixing all that together.
I started doing some cleanup like that in my fork (https://github.com/magicus/pppp/) but I quickly realized that to get this done properly, a lot of work is needed, and I don't want to do that in javascript if the end goal is a python library.

And the final disappointment for me was that I actually ordered a second $5 camera to have another reference point in reverse engineering and testing, but it turned out to have a wildly different protocol. It seems to be the "naxclow" protocol, so I guess https://github.com/intx82/a9-v720 would work, even though I have not tested it. But since I ordered it not really to use it as a camera, but to have it as a second testing device, it was a bit of a bummer...


[Event Request] table 37 "Sales Line" - OnBeforeValidateQuantityBase

Can you add event OnBeforeValidateQuantityBase?
field(5415; "Quantity (Base)"; Decimal)
        {
            Caption = 'Quantity (Base)';
            DecimalPlaces = 0 : 5;

            trigger OnValidate()
            // >>>>>>>>>>>>>>
            var
                IsHandled: boolean;
            // <<<<<<<<<<<<<<
            begin
                // >>>>>>>>>>>>>>
                IsHandled := false;
                OnBeforeValidateQuantityBase(Rec, xRec, CurrFieldNo, IsHandled);
                if IsHandled then
                    exit;
                // <<<<<<<<<<<<<<
                TestJobPlanningLine();
                TestField("Qty. per Unit of Measure", 1);

    [IntegrationEvent(false, false)]
    local procedure OnBeforeValidateQuantityBase(var SalesLine: Record "Sales Line"; xSalesLine: Record "Sales Line"; CallingFieldNo: Integer; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Parameter values of type int should also work with type float

When calling LoadGPTEnabled, I have a situation where I'm passing 2 into a parameter of type float and it errors out when validating the type.

Perhaps an extra flag like coerce_type or something.

The first fix that comes to mind is (in type_schema.py:142):
class ValueTypeSchema(TypeSchema):
    # ...

    def validate(self, value) -> bool:
        try:
            self.type(value)
            return True # Return true if the value can be converted to the type
        except ValueError:
            return False

But this might be too permissive. For example, I think every value can be converted to boolean.
Otherwise we could have a special case for float and int:
def validate(self, value) -> bool:
    return (self.type is float and type(value) is int) or self.type == type(value)

But this might not work in other cases, if there are any. It depends on Python rules for implicit conversion. Reading online I did not find any other cases of implicit cast, so the special check might not be that bad.

Allowing implicit conversion from int to float looks good to me.


Support standalone deployment of the network hub and tiers 0, 1, 2

Benefit/Result/Outcome
So that an IT admin can assemble an automated deployment using modules from Mission Landing Zone as part of a larger deployment, and deploy updates with configuration and template changes.
Description
We want to know what work is required to support a standalone deployment of the network hub and each tier.

Can they be deployed and updated separately and still support the simple single command deployment we have today?
If we separate the tiers, what types of changes are idempotent and what ones are not?
Are there other ways we should de-compose the deployment into smaller parts to better support idempotency?

The eventual goal is to provide better support to our customers for a NoOps/GitOps automated deployment system in which changes to individual configuration files or Bicep templates trigger incremental changes to the deployed infrastructure. The specific goal of this spike is to explore which parts of MLZ can be decomposed into smaller parts while keeping the possibility to perform a single deployment.
Suggested approach:

Focus on testing separation of the network hub and tier 0 as standalone deployments, while keeping our ability to deploy everything together with the existing parameters in mlz.bicep.
Test idempotency for the hub and tier 0. What types of changes are not idempotent? Can we predict which changes will trigger an update vs. a destroy/create action.
Try other ways of decomposing the deployment into smaller parts.

NOTE: This spike does not apply to the MLZ Terraform code.

Work on this spike is limited to: 24 hours
Outcomes
The spike will result in one or more of the following outcomes:

A proof-of-concept deployment of the network hub and another tier that can be deployed separately, and can also be deployed as a single deployment (as it is today).
Suggestions on additional ways we can break up our single deployment into multiple, while maintaining the ability to deploy in a single deployment.
Does deploying an update result in network downtime? Are there ways to mitigate downtime?
Understanding of what types of changes trigger updates vs. destroy/create (idempotency).
Definition of the future work required to fully implement the recommendations from this spike.

Something else to consider is network downtime. What kind of changes will bring resources down for even moments?

Something else to consider is network downtime. What kind of changes will bring resources down for even moments?

Thanks! I added an outcome for this.

One approach might be to separate the resource group deployments into distinct modules in the src/bicep/modules/ folder and reference them in the mlz.bicep file
From there we can provide example deployments using the tier-n.bicep file directly using an inheritance pattern in a way that makes it possible to deploy unintentionally deleted resources in a standard MLZ deployment.
Further discussion might be warranted here. This could provide pseudo idempotency if such an approach was taken to re-populate a tier-n resource.
This wouldn't completely answer to issue #695 however.

This is not the first time idempotency was brought up; looks like these concepts were closed with no action previously:
https://github.com/Azure/missionlz/issues/419

Should idempotency be enabled as well as per
Can very likely be implemented in bicep using conditional resource deployment; ie:
@allowed([
  'new'
  'existing'
])
param newOrExisting string = 'new'

resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' = if (newOrExisting == 'new') {
  name: storageAccountName```
https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/conditional-resource-deployment#new-or-existing-resource

Due to the dependencies between each tier and the required deployment order, this is not feasible unless all the required resources are moved to the HUB. For example, we enable diagnostic settings on several resources within each tier. If the log analytics workspace doesn't exist in the OPS tier first, then we can't completely deploy the HUB. However, we can't deploy the OPS tier first because we need the private DNS zones and private link scope deployed first in the HUB.


Deduplicate when converting metadata

The initial proof of concept of tmt test convert does not check whether an attribute is already defined higher in the fmf tree hierarchy. This would be good to prevent unnecessary data duplication.

check which attributes are already present in the current metadata branch
remove duplicates from the dictionary of gathered data
store the rest into main.fmf

The implementation could be quite easy:
parent = tree.find('/parent/directory')
if parent.get('contact') == imported_contact:
    do not store into main.fmf

What do you think?

'contact' is specifically singled out or should all attributes be checked?

(closed by accident)

I believe the same should apply to all attributes.

Any progress here? Are you blocked on something?

Mostly on time but also I have trouble understanding how to work with the fmf paths.


reading parquet returns EOF

When reading parquet objects we sometimes reach the proper end of the object but the caller (parquet reader) treat it as an error and throws an EOF exception.  The problem seems to lie with how we indicate to the caller that we reached the end.
This is the exception and call stack that I see:
16/08/02 19:06:14 TRACE SwiftInputStreamWrapper: No more data to read
16/08/02 19:06:14 ERROR Executor: Exception in task 0.0 in stage 9.0 (TID 51)
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:197)
at java.io.DataInputStream.readFully(DataInputStream.java:169)
at org.apache.parquet.hadoop.ParquetFileReader$ConsecutiveChunkList.readAll(ParquetFileReader.java:756)
at org.apache.parquet.hadoop.ParquetFileReader.readNextRowGroup(ParquetFileReader.java:494)
at org.apache.spark.sql.execution.datasources.parquet.UnsafeRowParquetRecordReader.checkEndOfRowGroup(UnsafeRowParquetRecordReader.java:604)
at org.apache.spark.sql.execution.datasources.parquet.UnsafeRowParquetRecordReader.loadBatch(UnsafeRowParquetRecordReader.java:218)
at org.apache.spark.sql.execution.datasources.parquet.UnsafeRowParquetRecordReader.nextKeyValue(UnsafeRowParquetRecordReader.java:196)
at org.apache.spark.rdd.SqlNewHadoopRDD$$anon$1.hasNext(SqlNewHadoopRDD.scala:194)
at scala.collection.Iterator$$anon$14.hasNext(Iterator.scala:388)
at org.apache.spark.sql.execution.joins.HashJoin$$anon$1.hasNext(HashJoin.scala:77)
at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:327)
at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:327)
at org.apache.spark.shuffle.sort.BypassMergeSortShuffleWriter.write(BypassMergeSortShuffleWriter.java:126)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:73)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:41)
at org.apache.spark.scheduler.Task.run(Task.scala:89)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Effi Ofer

resolved in https://github.com/SparkTC/stocator/pull/58


Monkey patch mention_name to prepend '@' for Hipchat

Hipchat uses '@' in mention names, so automatically append that when the hipchat adapter is loaded.

This shouldn't be necessary because Lita::Adapter#mention_format is implemented by lita-hipchat. Where are you seeing mention names appear without the @ symbol?

I'm doing this and it was coming through without the '@'. Using latest lita and lita-hipchat.
  def sorry(response, msg)
    response.reply("Sorry, #{response.user.mention_name}. #{msg}")
  end

You can use Lita::Robot#mention_format manually to achieve this now!


RX72N-EK Ether GCC: Failed to build aws_demos

It seems that e2studio cannot find the inclusion files of rx-elf-gcc.
Extracting support files...
16:08:44 **** Build of configuration HardwareDebug for project aws_demos ****
make -j8 all
rx-elf-gcc: error: for: No such file or directory
rx-elf-gcc: error: Renesas: No such file or directory
rx-elf-gcc: error: RX: No such file or directory
rx-elf-gcc: error: <IP_ADDRESS>004-GNURX-ELF\rx-elf\rx-elf\/include: No such file or directory
rx-elf-gcc: error: for: No such file or directory
rx-elf-gcc: error: Renesas: No such file or directory
rx-elf-gcc: error: RX: No such file or directory
rx-elf-gcc: error: <IP_ADDRESS>004-GNURX-ELF\rx-elf\rx-elf\/include: No such file or directory
make: *** [vendors/renesas/rx_driver_package/v125/r_sci_rx/src/targets/rx72n/r_sci_rx72n.o] Error 1
'rx-elf-gcc -O0 -ffunction-sections -fdata-sections -fdiagnostics-parseable-fixits -Wstack-usage=100 -g2 -m64bit-doubles -mcpu=rx72t -misa=v3 -mlittle-endian-data -mdfpu -std=gnu99 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../freertos_kernel/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common/compiler_support/gnuc -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common/network_support/onchip_rx_ether -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_bsp -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_bsp/board/generic_rx72n -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_ether_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_1 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_3 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_4 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/targets -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_byteq -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_byteq/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_sci_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_sci_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx/src/targets/rx72n -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/r_config -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/general -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/r_pincfg -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../freertos_kernel/portable/GCC/RX700v3_DPFPU -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/config_files -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/network_manager -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/common/include/private -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/common/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/freertos/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/include/platform -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/secure_sockets/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/freertos_plus_tcp/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/freertos_plus_tcp/portable/Compiler/GCC/ -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/tls/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/crypto/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/pkcs11/corePKCS11/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/utils/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/logging/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/dev_mode_key_provisioning/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/aws/defender/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/mqtt/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/coreMQTT/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/coreMQTT/source/interface -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/backoff_algorithm/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/common/pkcs11_helpers -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstracti'rx-elf-gcc -O0 -ffunction-sections -fdata-sections -fdiagnostics-parseable-fixits -Wstack-usage=100 -g2 -m64bit-doubles -mcpu=rx72t -misa=v3 -mlittle-endian-data -mdfpu -std=gnu99 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../freertos_kernel/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common/compiler_support/gnuc -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common/network_support/onchip_rx_ether -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_bsp -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_bsp/board/generic_rx72n -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_ether_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_1 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_3 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_4 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/targets -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_byteq -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_byteq/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_sci_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_sci_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx/src/targets/rx72n -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/r_config -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/general -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/r_pincfg -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../freertos_kernel/portable/GCC/RX700v3_DPFPU -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/config_files -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/network_manager -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/common/include/private -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/common/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/freertos/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/include/platform -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/secure_sockets/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/freertos_plus_tcp/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/freertos_plus_tcp/portable/Compiler/GCC/ -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/tls/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/crypto/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/pkcs11/corePKCS11/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/utils/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/logging/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/dev_mode_key_provisioning/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/aws/defender/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/mqtt/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/coreMQTT/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/coreMQTT/source/interface -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/backoff_algorithm/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/common/pkcs11_helpers -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractivendors/renesas/rx_driver_package/v125/r_sci_rx/src/targets/rx72n/subdir.mk:21: recipe for target 'vendors/renesas/rx_driver_package/v125/r_sci_rx/src/targets/rx72n/r_sci_rx72n.o' failed
make: *** Waiting for unfinished jobs....
vendors/renesas/rx_driver_package/v125/r_sci_rx/src/targets/rx72n/subdir.mk:26: recipe for target 'vendors/renesas/rx_driver_package/v125/r_sci_rx/src/targets/rx72n/r_sci_rx72n_data.o' failed
make: *** [vendors/renesas/rx_driver_package/v125/r_sci_rx/src/targets/rx72n/r_sci_rx72n_data.o] Error 1
rx-elf-gcc: error: for: No such file or directory
rx-elf-gcc: error: Renesas: No such file or directory
rx-elf-gcc: error: RX: No such file or directory
rx-elf-gcc: error: <IP_ADDRESS>004-GNURX-ELF\rx-elf\rx-elf\/include: No such file or directory
make: *** [vendors/renesas/rx_driver_package/v125/r_sci_rx/src/r_sci_rx.o] Error 1
'rx-elf-gcc -O0 -ffunction-sections -fdata-sections -fdiagnostics-parseable-fixits -Wstack-usage=100 -g2 -m64bit-doubles -mcpu=rx72t -misa=v3 -mlittle-endian-data -mdfpu -std=gnu99 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../freertos_kernel/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common/compiler_support/gnuc -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/amazon_freertos_common/network_support/onchip_rx_ether -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_bsp -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_bsp/board/generic_rx72n -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_ether_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_1 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_3 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/flash_type_4 -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_flash_rx/src/targets -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_byteq -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_byteq/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_sci_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_sci_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx/src -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/rx_driver_package/v125/r_s12ad_rx/src/targets/rx72n -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/r_config -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/general -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/src/smc_gen/r_pincfg -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../freertos_kernel/portable/GCC/RX700v3_DPFPU -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../vendors/renesas/boards/rx72n-envision-kit-gcc/aws_demos/config_files -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/network_manager -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/common/include/private -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/common/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/freertos/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/platform/include/platform -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/secure_sockets/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/freertos_plus_tcp/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/freertos_plus_tcp/portable/Compiler/GCC/ -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/tls/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/crypto/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/pkcs11/corePKCS11/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/freertos_plus/standard/utils/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/logging/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/dev_mode_key_provisioning/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/aws/defender/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/c_sdk/standard/mqtt/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/coreMQTT/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/coreMQTT/source/interface -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractions/backoff_algorithm/source/include -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../demos/common/pkcs11_helpers -IC:/Users/thain/ws_afr/amazon-freertos/projects/renesas/rx72n-envision-kit/e2studio-gcc/aws_demos/../../../../../libraries/abstractivendors/renesas/rx_driver_package/v125/r_sci_rx/src/subdir.mk:18: recipe for target 'vendors/renesas/rx_driver_package/v125/r_sci_rx/src/r_sci_rx.o' failed
"make -j8 all" terminated with exit code 2. Build might be incomplete.

16:08:46 Build Failed. 5 errors, 0 warnings. (took 1s.990ms)

In the Includes section, it is suspected that this inclusion is incorrect.
${TCINSTALL}/include

This inclusion should be enclosed in quotes.
"${TCINSTALL}/include"

Or this inclusion should be removed?

fixed by removing the "${TCINSTALL}/include". This is not needed. The space in the installation path will causes the gcc compilation error


Fix auto merge conflict 9043 [skip ci]

fix auto-merge conflict at #9043
NOTE: this must be merged as create a merge commit

build


Research various implementation techniques

Real Alex: JavaScript (standalone first, then node)
Fake Alex: Alternatives in Python
Stephen: NetworkX/iGraph, other libraries
Dan: Ruby options
Noah: GeoPandas?

We've settled on ArcGIS with JavaScript for now.


Fix escaped backtick highlighting in string literal (#324)

should fix #324:
let regex = `\``

let foo = 10

Should I first create a PR in rescript-lang/rescript-sublime?

Thanks!


migrate Gauge to analyser

What it says on the tin.  And I didn't even change logic this time!  Should be a 1:1 migration, only PLD Oath Gauge and WAR Beast Gauge are currently consuming core Gauge, from what I could find.

I'm happy with this in the current state, but considering it's gauge, may be worth ack taking a look too.

thankeethankee


How to install on Fedora?

The python-yaml package isn't in dnf, and I'm not sure which package I can substitute.

you are looking for the python3-pyyaml package


Issues with TLS certificates using Opera Mini

I was trying to access the Caddy blog under HTTPS (https://caddyserver.com/blog/) using Opera Mini, but I got the following error message:
You tried to access the address
https://caddyserver.com/blog/caddy-0_8-released , which is currently unavailable. Please make sure that the web address (URL) is correctly spelled and punctuated, then try reloading the page.
Secure connection: fatal error (1066)
https://caddyserver.com/blog/caddy-0_8-released
Unable to verify the website's identity (OCSP error).
The response from the online certificate validation (OCSP) server was too old.
```

I guess it's using the Let's Encrypt functionality to serve the blog, that's why I think it could be an issue.

@ragrum So actually, this might be a problem with Opera Mini implementing OCSP incorrectly. See http://www.opera.com/blogs/security/2014/10/security-changes-opera-25-poodle-attacks/#comment-1644749998 (or any other similar Google search results). Basically, upon a browser getting an expired OCSP value, they should request a new one themselves. But maybe Opera Mini is not doing that?
Anyway, I'm still improving the OCSP stapling in Caddy for 0.8.1 to fetch a new OCSP response at NextUpdate rather than only when the status changes. This will still leave a brief window where OCSP status is old, but in those few occasions the browser should request a new one on their own.

@mholt I see, thanks for sharing that link, and looking into the issue, I'll keep and eye on the Caddy blog after Caddy 0.8.1 is released, and see if the problem continue.
For what it's worth:
Browser: Opera Mini 13.0.2036.98649
OS: Android 5.1
Device: Moto G (1st gen)

This is fixed locally; changes will be available on master as soon as I push.


Release Google.Maps.RouteOptimization.V1 version 1.1.0

Changes in this release:
New features

Minor fields and documentation update (commit f327149)
A new message RouteModifiers is added (commit f327149)
A new field route_modifiers is added to message .google.maps.routeoptimization.v1.Vehicle (commit f327149)
A new field cost_per_kilometer_below_soft_max is added to message .google.maps.routeoptimization.v1.DistanceLimit (commit f327149)

Documentation improvements

A comment for method BatchOptimizeTours in service RouteOptimization is changed (commit f327149)
A comment for enum value DEFAULT_SOLVE in enum SolvingMode is changed (commit f327149)
A comment for field validation_errors in message .google.maps.routeoptimization.v1.OptimizeToursResponse is changed (commit f327149)
A comment for message TimeWindow is changed (commit f327149)
A comment for enum value CODE_UNSPECIFIED in enum Code is changed (commit f327149)
A comment for field reasons in message .google.maps.routeoptimization.v1.SkippedShipment is changed (commit f327149)
A comment for enum value RELAX_VISIT_TIMES_AND_SEQUENCE_AFTER_THRESHOLD in enum Level is changed (commit f327149)
A comment for message OptimizeToursValidationError is changed (commit f327149)
A comment for field code in message .google.maps.routeoptimization.v1.OptimizeToursValidationError is changed (commit f327149)

Created release for Google.Maps.RouteOptimization.V1-1.1.0


Default params with plain use Params.Schema

Hello, here is my issue:
defmodule MyParams do
  use Params.Schema

  schema do
    field :count, :integer, default: 1
  end
end

changeset = MyParams.from(%{})
assert %{count: 1} = Params.to_map(changeset) # but it is %{}

Hm, this is a bug, I guess we need a new test for it the latest PR to work on default vales was #10

oh btw @lasseebert, any idea about this issue?

This is definitely a bug. I will have a look when time allows ;)


RFP - proxallium

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://proxallium.dtw.tools
Direct download URL for the software / installer : https://github.com/DcodingTheWeb/ProxAllium/releases/download/v0.4.2/ProxAllium-v<IP_ADDRESS>z
Software summary / short description: ProxAllium is a GUI front-end for Tor, it can be used to circumvent censorship and allow freely browsing the internet.

Please assign this to me. I'll take on maintaining this package for Damon.
Daman, ill include the files direct in the chocolatey package. I can also include a start menu entry as well. My updating script will pull from github releases and update whenever the "latest" version tag differs.
I'll use the release text on github as the release notes. Also let me know how you want it tagged  on community repository and what you want it to say on the description text so I can get it the way you want.

@Cossey Thank you so much for adopting this package! :grin:

Also let me know how you want it tagged on community repository and what you want it to say on the description text so I can get it the way you want.

These are the tags on the top of my head: privacy, security, anonymity, tor, proxy, vpn, portable etc.
As for the description I think we can keep it simple:

ProxAllium is a GUI frontend to Tor, you can use it to easily create a proxy and use with it programs (like browsers, mail clients, chat clients etc.) to circumvent censorship and also to encrypt your connection.

Let me know if you need more info, cheers!

That is fine for now. I'll include files direct in the package instead of shimming them from GitHub.
Is just the current version fine to have on the community repository or do you need some older versions too?
Please give me up to a week to build an updating script, do testing and get the package(s) submitted.

Is just the current version fine to have on the community repository or do you need some older versions too?

The current is fine, no need to have older versions with less features in the repository. They also used to come with Tor pre-packaged, which means they would be exposed to security risks if there are any in the old versions of Tor. The latest version doesn't package Tor so it's for the best.

Please give me up to a week to build an updating script, do testing and get the package(s) submitted.

Of course, please feel free to take your time, I am grateful for your effort and enthusiasm :smile:

Okay, the package is nearly ready to be pushed, but should it dependencies the tor package (It will install the tor package when installed)? If so which tor package should it install? (https://community.chocolatey.org/packages?q=tor).

If there are several different dependencies a package can work with it's usually better not taking a direct dependency on any of them but instead highlight what is required in the package description and let the user decide which dependent package to install.

@Cossey ProxAllium doesn't have a hard dependency, it can use any version of Tor. On the first start it prompts the user to go through the setup guide, which lets them choose a folder containing Tor, or a folder containing the Tor Browser (which includes Tor).
The choice is normally left up to the user, what I recommend to users is to install Tor browser so that Tor is kept updated whenever TB is updated.
But since the user in this case would be using chocolatey, I am not sure what the best way of doing things is. How easy is it for the user to locate tor.exe if it is added as a dependency?
Perhaps I can even add a feature to auto-detect the appropriate version of Tor if installed via chocolatey.
For now I think we should take @pauby's advice and mention that the user can install Tor or Tor Browser in the description and let them make the choice.

Okay, it is submitted and there is a mention of the requirement of Tor.
https://community.chocolatey.org/packages/proxallium/0.4.2

@Cossey Cool!
I have two comments:

The website has been migrated to a new domain: https://proxallium.dtw.tools (the old one still works and redirects to the new one)
The description says "requires" packages, but it doesn't really require them if the user already has Tor (Browser) installed outside of chocolatey, I'd phrase it something like this: "Requires Tor to function, you can get it from the tor or tor-browser bundle packages."

Okay I have made changes to those two points, but before I push again, is there a new url for https://download.tuxfamily.org/proxallium/icons/128.png that I should be using? (This is the icon that displays on the chocolatey community repository).

Thanks, you can use the 256 pixel version of the icon for more resolution: https://download.tuxfamily.org/proxallium/icons/256.png
The download repository is still hosted at TuxFamily.

Done.

Waiting on moderator to approve. Unfortunately it has been flagged by VirusTotal as malicious by 8 vendors which will require moderator approval regardless. I noticed that you've posted on the virustotal page about that @TheDcoder . If you have not already, might I suggest you contact some of these vendors to report a false positive? That way this will improve your score on VirusTotal as well as not flag your software on those users devices.
I've done this before with one of my installers that was flagged by my partners endpoint protection software for her work. I submitted a report and it was a turnaround of 3 days if I recall (don't remember the software that was being used).
This is a pretty good list provided by VirusTotal which list contact details for reporting false positives:
https://github.com/yaronelh/False-Positive-Center
Here are some links to the vendors that have reported the exe as Malicious
https://www.secureage.com/article-report-false-positive
https://www.maxsecureantivirus.com/maxis/submit_aFalse_Positive.htm
https://service.mcafee.com/?locale=en-IN&articleId=TS102751&fromSearch=true&page=shell&shell=article-view
https://support.quickheal.com/v4/index.php?/Knowledgebase/Article/View/137/0/how-to-submit-a-false-positive
Even if you can get at least 4 of those vendors to approve as false positive this would drastically improve your score on VirusTotal.

@Cossey Thank you for the information. I did send emails to AV vendors a while back and some of them responded positively, but most of them just ignored me. I think the turnaround time for me was longer than 3 days, and it didn't eliminate all false positives.
The reason for such a high positivity rate is due to how AutoIt (the programming language in which ProxAllium is written) is used, as it is easy to learn and use, a certain portion of malicious users have written viruses in it, and since the compiled programs are nothing more than the AutoIt interpreter and the code, the signature for a virus matches with many other totally different AutoIt programs, more info can be obtained from this forum post: https://www.autoitscript.com/forum/topic/34658-are-my-autoit-exes-really-infected/
Never the less, I am going to release an update to ProxAllium soon, so I will contact the vendors again at that time to get it "whitelisted". I hope it can be approved by manual review until then.

That's really unfortunate how some have not responded.
Any updates you make and release will be automatically picked up and deployed out to the community repo. It checks approximately every 4 hours (DELAY=240) via the GitHub API.
However please do open an issue at https://github.com/Cossey/choco and give me a heads up if you plan on doing something like drastically change the folder structure or executable file names etc in any future releases etc as I may have to upgrade the script.

Package has been approved. RFP completed.

Awesome! @Cossey Thanks for picking it up :)

Package approved:
https://community.chocolatey.org/packages/proxallium/0.4.2


Improve test cases for socket server of cookbook.

Includes MockServerTestCase and its subclasses: MockTCPServerTestCase and MockUDPServerTestCase.


Please consider making a new release

Dear maintainers of vim-airline
The last release of vim-airline occurred in March 2016, and there has been many commits since then. Please consider making a new release that include these.
I maintain the vim-airline package in Debian, and wouldn't want to take the burden of cherry picking commits or confusing users with a snapshot release.
thanks!
-Jonathan

okay, will do. Hopefully I have some time to fix remaining issues within the next month. @bling are you able to do the required changes (mainly upload it to vim.org page)?

sure thing, just ping me when you're ready.


[Teams] Hackathon feedback

Fixes:
https://github.com/microsoft/botbuilder-dotnet/issues/2737
and
https://github.com/microsoft/botbuilder-dotnet/issues/2718
•	Remove the tenant filtering middleware from the product, and add to samples
-Removed TeamsTenantFilteringMiddleware from the product and added it to Roster bot as an example.
•	Bot message preview edit/send return value should be bad request if malformed
-now returning BadRequest
•	File consent should be bad request if malformed
-now returning BadRequest
•	OnTeamsMessagingExtensionFetchTaskAsync should take a MessagingExtensionAction and not MessagingExtensionQuery
-Changed parameter type
•	In TeamACtivityHandler we should check whether there is an InvokeResponse activity on the turnstate and if there is don’t overwrite it.
- added check of TurnState for existing InvokeResponse
•	OnSigninVerifyStateAsync should be void (create invoke response internally, if not present in turnstate)
- Changed return type to void, added test
•	Change TeamsActivityHandler's task/fetch and task/submit return types to TaskModuleResponse

Pull Request Test Coverage Report for Build 83522

0 of 0   changed or added relevant lines in 0 files are covered.
19 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.05%) to 78.823%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs
1
75.14%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/OAuthPrompt.cs
1
57.23%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs
2
50.0%

/libraries/Microsoft.Bot.Builder/MemoryTranscriptStore.cs
2
86.09%

/libraries/Microsoft.Bot.Builder/Teams/TeamsActivityHandler.cs
13
82.47%

Totals

Change from base Build 83506:
0.05%

Covered Lines:
5423

Relevant Lines:
6880

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


Change of inconsistencies_found.csv file column name

For improving the readability, please substitute the name of the column in the inconsistencies_found_N.csv file as follows:

before: inconsistent_class_stereotype
after: input_class_classification

Also, make the adjustments in the related variables names if necessary.

@mozzherina, please solve this issue before the re-generation of the dataset.

@pedropaulofb Is it still actual? In the documentation it is still the same

Yes, it is actual. Thanks for noticing and pointing me out that. I have already fixed that in the documentation.

Done


Update workflows from templates

Updating from templates.

Closing to let the workflow re-open if necessary.