text:
Error 450 while sending emails(Docker)

While i was configured Mailrise, i tried testing my notification setup by testing with multiple programs that send email. It seems that it receive the error 450 from the client and the log in docker shows.  I am sending emails to alerts@mailrise.xyz to the correct host.
 WARNING:apprise:Failed to load Apprise configuration from memory://

Using yoryan/mailrise:latest docker image on an amd64 machine, and latest dockerr release, debian buster
here is my mailrise.conf
configs:
  alerts:
    urls:
     discord://(REDACTED)/(REDACTED)

and here's the verbose logs
[2021-08-23 15:40:12] INFO:mailrise.skeleton:Loaded configuration with 1 recipient(s),
[2021-08-23 15:40:12] INFO:mail.log:Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin),
[2021-08-23 15:40:12] INFO:mail.log:Peer: ('::1', 40312, 0, 0),
[2021-08-23 15:40:12] INFO:mail.log:('::1', 40312, 0, 0) handling connection,
[2021-08-23 15:40:12] INFO:mail.log:('::1', 40312, 0, 0) EOF received,
[2021-08-23 15:40:12] INFO:mail.log:('::1', 40312, 0, 0) Connection lost during _handle_client(),
[2021-08-23 15:40:12] INFO:mail.log:('::1', 40312, 0, 0) connection lost,
[2021-08-23 15:40:13] INFO:mail.log:Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin),
[2021-08-23 15:40:13] INFO:mail.log:Peer: ('REDACTED IP', 38840),
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) handling connection,
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) >> b'EHLO [127.0.0.1]',
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) >> b'MAIL FROM:<alerts@mailrise.xyz>',
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) sender: alerts@mailrise.xyz,
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) >> b'RCPT TO:<alerts@mailrise.xyz>',
[2021-08-23 15:40:13] INFO:mailrise.skeleton:Accepted recipient: alerts@mailrise.xyz,
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) recip: alerts@mailrise.xyz,
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) >> b'DATA',
[2021-08-23 15:40:13] INFO:mailrise.skeleton:Accepted email, subject: My Smtp Alert (1) Testing,
[2021-08-23 15:40:13] WARNING:apprise:Failed to load Apprise configuration from memory://,
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) EOF received,
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) Connection lost during _handle_client(),
[2021-08-23 15:40:13] INFO:mail.log:('REDACTED IP', 38840) connection lost,

You need a dash before your Discord URL, because urls must be a list:
configs:
  alerts:
    urls:
     - discord://(REDACTED)/(REDACTED)

As you can see, it's a pretty easy mistake to make. 😁

I spent 6 hours troubleshooting this and didn't realize.
I'm embarrassed 😂

authors: SemperEnim YoRyan

repo: YoRyan/mailrise


text:
No way to unbind event handler functions

I don't see any way to unbind event handler functions.
I need an equivalent of tree.release() that only removes the event handlers but doesn't wipe out all the tree data.

Hello @jmullo. Both the tree and the cursors are extending the emmett library event emitter. They therefore both have an off method you can use to unbind single handlers.

Ahh, thanks. I suggest adding that to the documentation :)

Actually this already is in the documentation :smile:. But I admit I should put it first.

source: gharchive/issue

authors: Yomguithereal jmullo

repo: Yomguithereal/baobab

license: MIT

license_type: permissive

license_source: github-api


text:
Print backtrace on abort/assert

Feature Description
Currently it only prints the line where the assert was hit - it might help for some bug reports if it also prints more information about the context.

libunwind can be adapted do this in debug build of Yosys; however since Yosys is a command-by-command interpreter this is sufficient isn't it ? Unlike having function calls etc. its a straight line interpreter and it just fails on most recent command so I don't see a major need for it yet.

rough cut implementation to print a stack of commands executed to point of failure https://github.com/YosysHQ/yosys/pull/3757

Updated to actually print the stack trace; see commit detail

@nakengelhardt @whitequark - any idea on the PR ?

authors: arcturusannamalai nakengelhardt

repo: YosysHQ/yosys

license: isc

license_source: bigquery


text:
Tweaked the representation of nets and buffers in the Show command graph.

Two tweaks to the generated graph.

Nets changed from a diamond shapes to plain text with the net name. This provides the visual load of the nets while preserving their names.

Buffers changed from a period shape to a plain text with the label "[BUF]", providing hint what they are while keeping the visual load low

Before

After

Dot files
Archive.zip

Personally, I find it unconvincing that the new representation is any better (or any worse) than the old one. Both have issues in slightly different ways.

2. Buffers changed from a period shape to a plain text with the label "[BUF]", providing hint what they are while keeping the visual load low

This makes buffers more visible, why? I suspect this is because it looks better when used with -colors, but it makes the output more cluttered. Just recently we removed an explicit BUF label, and this would change it back.

@povik, the rationale behind the "[BUF]" is to provide to readers an indication what that node mean.  Below are the three version of the buffer. The "[BUF]" one provide a balance between providing the information while keep low clutter.

is to provide to readers an indication what that node mean

Yosys developers already know what the node means though.

@whitequark, yes, it targets new readers, eliminating the question "what does this dot mean?", without much burden on readers that already know.

This yosys application suggests that the diagram is also targeting users and learners. I hope that is still the case.

The reason I changed the "BUF" nodes to a dot was that there were a lot of issues filed by confused users that asked how to make yosys remove the buffers (that didn't really exist in the netlist, but were just a visual representation for two connected wires) and I got tired of answering them. I haven't seen any new questions like that filed since the change, so I feel quite confident in saying that the dot shape is less confusing to users.

Thanks @nakengelhardt.  I will restore the 'point' shape and will submit a new clean PR.

For the plaintext I guess it can be an option, I personally dislike the wide space between the place where the arrow points and the actual text, especially for short wire names, but I can see that it's a taste question. The default should remain the diamond but I would be ok with a generic option to override it, something like show -wireshape foo.

Sounds good. Thanks.
On Thu, Feb 29, 2024 at 10:14 AM N. Engelhardt @.***>
wrote:

For the plaintext I guess it can be an option, I personally dislike the
wide space between the place where the arrow points and the actual text,
especially for short wire names, but I can see that it's a taste question.
The default should remain the diamond but I would be ok with a generic
option to override it, something like show -wireshape foo.
—
Reply to this email directly, view it on GitHub
https://github.com/YosysHQ/yosys/pull/4247#issuecomment-1971693738, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQVMQOV6BREUCJBKNL2TWDYV5XZVAVCNFSM6AAAAABD7Q37QSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRGY4TGNZTHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi @nakengelhardt, I have the -wireshape code working, but before I send a PR, I would like to ask you one more question.
You mentioned that you dislike the space in the plaintext nodes and I found a way to eliminate it (see below). Would you consider  having this is the new default (and only) behavior, resulting with simpler code, or should I go ahead with the --wireshape PR?
Original/default:

With -wireshape=plaintext:

BTW, https://edotor.net/ is a great site to experiment with .dot files.

Opening for the ongoing discussion.

source: gharchive/pull-request

authors: nakengelhardt povik whitequark zapta


text:
🛑 UPC is down

In 9426cd4, UPC (https://www.upc.edu.cn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UPC is back up in 4522ee6 after 6 minutes.

repo: Yourrrrlove/upptime


text:
🛑 UPCME is down

In 27bf56a, UPCME (http://medwww.upc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UPCME is back up in acd8ea3 after 16 minutes.


text:
Dev

merge my pr

No pr..

repo: YuriyGuts/snake-ai-reinforcement


text:
いいところ診断の結果に優しさを追加したい

以下の結果を追加したい
'{userName}のいいところは優しさです。あなたの優しい雰囲気や立ち振る舞いに多くの人が癒やされています。'

これから対応する

3e67976で対応されました

repo: Yusuke-dwyane/assessment


text:
can you offer training file

How to organize data

Hi,
Please see #6 about the the training dataset.
Otherwise if you want to use your own data, it has to follow the PASCAL VOC format.
Best,
Yuval

not training data。train_and_test.prototxt File

you only offered  test.prototxt file. and  your work is  cool.

such as loss layer？

Caffe training file？

You can find the training files here:
https://github.com/shelhamer/fcn.berkeleyvision.org/tree/master/voc-fcn8s-atonce

authors: YuvalNirkin sunjunlishi


text:
Option to copy the unencrypted msgstore.db to the Internal root (/storage/emulated/0/) at the end of the script

This would be a really cool feature to work in conjunction with https://github.com/jukefoxer/Signal-Android

To clarify, I mean on the phone.

To clarify, I mean on the phone.

To clarify, I mean on the phone.

yes I understood that.

To clarify, I mean on the phone.

yes I understood that.

TODO : What if user does not connect device during view_extract.py

authors: YuvrajRaghuvanshiS rschuppan


text:
Con't use “crx”

“If you need to use a disabled extension, you can contact the extension’s developer and ask them to upload their extension to the Chrome Web Store. This will allow you, and other people who use Chrome, to install that extension from the Chrome Web Store, or if you already have it installed, to manually re-enable it from your list of extensions.”
The info is provided by Chrome

@Yueshi9 Chrome 目前不支持非谷歌官方商店的扩展程序了。
可行的更新后的方案为加载解压缩的文件夹，具体可查看最新 release。

THX


text:
🛑 Official Website is down

In c630916, Official Website (https://www.zeenkey.com) was down:

HTTP code: 500
Response time: 186 ms

Resolved: Official Website is back up in 445a8a3.

repo: ZEENKEY/statuspage


text:
🛑 ZEENKEY Merch (Official Store) is down

In 813f25f, ZEENKEY Merch (Official Store) (https://shop.zeenkey.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ZEENKEY Merch (Official Store) is back up in 641f064.


text:
🛑 Server 1 is down

In 6eff403, Server 1 (https://www.zeenkey.com) was down:

HTTP code: 500
Response time: 88 ms

Resolved: Server 1 is back up in 22ddd2c.


text:
🛑 Server 1 is down

In 0fba1f6, Server 1 (https://www.zeenkey.com) was down:

HTTP code: 500
Response time: 175 ms

Resolved: Server 1 is back up in 7487b39.


text:
MISS of average mask

Hi, thanks for your brilliant work.
I try to re-run your project, but i can't found the code for calculating the average segmentation mask as well as the usage of m_t.py in irn project, did i missed any information?

@DepueeDome  Thank you for your attention. This part of the script code needs to be prepared by yourself.

@DepueeDome Thank you for your attention. This part of the script code needs to be prepared by yourself.

Thanks for your reply! may i verify some parameters in m_t.py  with you here?
1.According to your paper, Eq. 3, X_m denotes the segmentation mask (hw) and c_i is (hw*1),
therefore, should both the embedding_size and the representation_size change to 1 in m_t.py?

@DepueeDome Thank you for your attention. This part of the script code needs to be prepared by yourself.

Thanks for your reply! may i verify some parameters in m_t.py  with you here?
1.According to your paper, Eq. 3, X_m denotes the segmentation mask (hw) and c_i is (hw*1),
therefore, should both the embedding_size and the representation_size change to 1 in m_t.py?

@DepueeDome Both segmentation mask and c_i denote hw1, and the embedding size (W_1 and W_2) is nhw.

@DepueeDome Both segmentation mask and c_i denote hw_1, and the embedding size (W_1 and W_2) is n_hw.

So the output of M_t is (hw1), where h and w determine by the feature map M_t concatenate to, and i right?

@DepueeDome  Yes, you are right.

@DepueeDome Yes, you are right.

Thanks a lot!

@DepueeDome Both segmentation mask and c_i denote hw1, and the embedding size (W_1 and W_2) is nhw.

@ZHANGDONG-NJUST Could you please elaborate a little further on this.
If I understand correctly, both X_m and c_i are of dim hw x 1 and W_1 and W_2 are n x hw. Then, the term inside the softmax (in Eq (3)) would have a dimension of 1 x 1. What exactly is the dimension of alpha_i? Is the term inside the softmax being computed for all n segmentation masks and then the softmax is applied over these n scores?
Thanks!

@pkmandke   1. alpha_i is a scalar, so it has a dimension of 1 x 1; 2. softmax is only applied over n scores.

authors: DepueeDome ZHANGDONG-NJUST pkmandke

repo: ZHANGDONG-NJUST/CONTA


text:
transform coordinate system

transform coordinate from 84 into baidu system

加了一个转换，把坐标从标准转换成百度的系统

license: WTFPL


text:
IndexNSG::InterInsert lock issue

https://github.com/ZJULearning/nsg/blob/eceb09e2754d978b4c8b07e3248018987feb597a/src/index_nsg.cpp#L308C7-L308C7
这里会用一个锁来读取 des_pool，之后又会加个锁写入 des_pool，假如处理另一个节点的函数在读、写操作中间读了，又在本线程写后写了数据，那么本线程的工作不就等于没干？
当然，这里这样处理可能是没问题的，在 des_pool 空间未满时，写操作分别在末尾添加数据是没有问题的，在 des_pool 空间已满时，究竟怎么更新数据（把入边反转一下也加入出边？），也许并没有区别？

全程加锁会有些延长执行时间，读写分开加锁会快一些，这么做的一个假设是当图比较稀疏的时候，锁冲突概率比较低，你说这种互相干扰的情况发生的概率也比较低，可以忽略。

repo: ZJULearning/nsg


text:
fix: add coreuils build dependency

Fixes #9.

This fix exposes more build issues which will need to be addressed before it is committed.
#10 Multiple test suites report separate results and zopen_check_results doesn't process the output correctly
#12 Possible loop in multiple tests

Fixes #12 - some issues fixed, some temporarily worked around. See the details in the issue.
Fixes #10 - zopen_check_results updated.

@IgorTodorovskiIBM @MikeFultonDev
This is now ready for review is either of you can spare a bit of time.
I don't have authority to assign reviewers.

@IgorTodorovskiIBM Thanks for the review.
If you're happy, could you merge this as I don't have write access?

repo: ZOSOpenTools/findutilsport


text:
Cannot apply JSON operations (e.g. pretty formatting) to unsaved editor

I'm often dealing with minimized JSON and XML embedded in log files. To ease reading I will copy the block of JSON or XML to a new document in an editor and use the editor's tools (potentially via a plugin) to reformat the content so it's easier to read (and potentially to take advantage of context collapsing if the editor offers that for structured content).
It seems I'm unable to do that in VSCode when using this plugin. I create a new editor window, paste a bunch of JSON into it, and click the JSON icon in the left sidebar, and get a "Please open the JSON file" notice rather than JSON options.
Please allow the extension to work with an unsaved editor tab that contains JSON.
Thanks!

https://github.com/mohsen1/vscode-prettify-json

authors: bandlerr jhardin-accumula

repo: ZainChen/vscode-json


text:
feat(state): add a query function for transparent address balances

Motivation
This PR adds a state query function for the get_address_balance RPC in ticket #3157.
We still need to add a state request and a RPC method.
Specifications
RPC:

https://zcash.github.io/rpc/getaddressbalance.html

But only the arguments and fields in ticket #3157.
Designs
There are a few tricky parts of this PR:

making sure the balances from finalized state are consistent with each other
combining the finalized and non-finalized balances

We could try to hold a database read snapshot, but that could cause locking issues. Instead, I just retry a few times if the balance might have changed. (If the query fails for this reason, Zebra is still syncing, and the results would probably be wrong anyway.)
Solution

Add a query function for address balances

Add a query method for non-finalized address balance changes
Add a query method for finalized state address balances

Retry interrupted finalized balance queries
Pop chain root blocks until it matches the finalized tip

Related changes:

Make address index types consistent
Simplify non-finalized address index updates

Update snapshots for address index queries

Simplify non-finalized UTXO query

Review
I think @jvff is writing the RPC side of this query.
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work
Do the state queries for the other address RPCs.

Full validation sync failed due to #3991, but we stopped requiring that check due to #4114:
https://github.com/ZcashFoundation/zebra/runs/6017141629?check_suite_focus=true#step:9:1635

@mergifyio update

Mergify hung on "evaluating rules" for 90 minutes:
https://github.com/ZcashFoundation/zebra/pull/4097/checks?check_run_id=6016785912

@mergifyio refresh

Full validation sync failed due to #3991:
https://github.com/ZcashFoundation/zebra/runs/6018158375?check_suite_focus=true#step:9:7199
I'll re-run the job.

Now it's failing with #4114, sigh

repo: ZcashFoundation/zebra


text:
🛑 multilevel-catalog-new-games-paywall (prod) is down

In dfafccf, multilevel-catalog-new-games-paywall (prod) (https://prod.zebr-a.com/squidex/cache/58507d07-0d32-4815-8264-75fa327363d2) was down:

HTTP code: 502
Response time: 100 ms

Resolved: multilevel-catalog-new-games-paywall (prod) is back up in 229741f.

repo: Zebrainy/upptime


text:
🛑 Dev Yandex service health auth check is down

In c336384, Dev Yandex service health auth check (https://dev.zebr-a.com/yandex/health/authCheck) was down:

HTTP code: 400
Response time: 428 ms

Resolved: Dev Yandex service health auth check is back up in 83201ae.


text:
🛑 Latest versions (prod-squidex) is down

In b6ab674, Latest versions (prod-squidex) (https://prod.zebr-a.com/squidex/cache/6402afa4-b358-4d06-875d-d3fc1f3f78cd) was down:

HTTP code: 502
Response time: 128 ms

Resolved: Latest versions (prod-squidex) is back up in 755e9ad.


text:
Add endpoints for guild events

Docs
Instructions

This will need to be done in dippy/core/api/endpoints/guild_events.py
Fields in the docs that have a type with a question mark should be optional (ex. ?integer should be Optional[int])

Tasks

[ ] List scheduled events for guild
[ ] Create guild scheduled event
[ ] Get guild scheduled event
[ ] Modify guild scheduled event
[ ] Delete guild scheduled event
[ ] Get guild scheduled event users

Be sure to commit each new endpoint separately

hi! i'd like to be assigned to this issue
also noticed a thing, in list scheduled events for guild there is nothing said about with_user_count being required and/or default.. what should i put in QueryArgField()?

authors: ZechCodes eggveloper


text:
NotSupportedError: ReadableStream uploading is not supported

NotSupportedError: ReadableStream uploading is not supported
This error occurs in Safari on iOS and macOS, but everything works fine on other platforms.

According to MDN this feature is unavailable on Safari browser, sadly there are no fix for that, all I can do is to add note to documentation:
https://developer.mozilla.org/en-US/docs/Web/API/Request#:~:text=Send ReadableStream in request body

license: ISC


text:
Is/version pin torchsparse again

We found that, for some reason not fully understood, on 2023-10-04 we began to have torch-dependency issues on some of our machines, where torchsparse was attempting to pull a different version of pytorch than the one we have version-pinned in RadarProcessor.
These changes represent a quick fix to explicitly version pin the package again.

Note: this PR was pushed through by me alone, for the sake of moving quickly.  Changes made on this repo are well-isolated from RadarProcessor, and several developer PRs were blocked by the problem, so I thought haste was justified.

repo: ZendarInc/torchsparse


text:
Cooky policy pagina en actie cookies weigeren

Describe the bug

A cooky policy is required linked from the cooky pop-up which links to https://holontool.nl/cookie-policy/
Make sure that when clicked on 'weigeren' cookies are switched off

To Reproduce
Steps to reproduce the behavior:

Go to holontool.nl in private tab
Check cooky policy

Expected behavior
A working cooky policy page and cookies switch off when denying cookies
Actual behavior
Not sure if all cookies switch of, no cookie page

Aangepast dat tracking via Microsoft Application Insights alleen aan staat als de banner geaccepteerd is.
Google Analytics verwijderd.

Ik heb de link verwijderd en gewoon in de melding gezet dat Azure Application Insights ingeschakeld wordt bij accepteren.
Ik weet niet wat ik er verder bij moet zetten, zijn allemaal nogal open deuren.

authors: Erikvv naudloomans

repo: Zenmo/Holon-webapp


text:
卡片模式下关闭按钮错误

卡片模式下点击关闭按钮会打开信息窗口，

卡片模式下的连接类别能不能像表格模式一样支持升序/降序排列吗

关闭修了 不过发版工具被我玩砸了一会修好了再发fix

支持升序/降序排列

这个会考虑在未来的几个版本支持

加上了

repo: Zephyruso/zashboard


text:
Update Workflows

Ello, here is a done pipeline for the main zig tooling/library. It still needs the website stuff (will be working on that next).
How things work and names and everything can be changed. I just wanted to get this out here for people to start looking at.
Implemented functionality:

[x] Build microzig on PR to main & Push to main. Both have file triggers to only run if a part of Microzig that would affect the build is changed (a).
[x] Upon push to main (and successful build), create a PR to zig-master with the changes.

[x] Create new branch (b)
[x] Create new dummy commit in branch (this is to make it so that the master test will be done against a different commit. (c)
[x] Create PR against zig-master (d)
[x] CI to build microzig against zig master upon PR to zig-master

[x] Using same publish method, publish changes upon tag creation (e)

[x] Create GitHub draft release for commit (f)

CI Update TODO:

[x] Website Publish

[x] Build & Test
[x] Staging area with viewable staged sites.
[x] Deploy on PR to main

[ ] Run tests after building (Need more details on what is needed for testing)
[ ] Add download URLs to draft releases
[ ] Additionally publish regz and uf2 separately from the main microzig location.
[x] Update build.zig.zon version based on tag prior to publishing.
[ ] Add binaries to draft releases (maybe)

Microzig Repo TODO:

[ ] Create zig-master branch
[ ] Add PR_CREATE_PAT PR_CREATE_TOKEN (name changed to be more accurate to what it is. see) secret for actions. This is to allow automated PR creation. The Fine-grained PAT tested with has: "Read access to metadata", and "Read and Write access to pull requests" as permissions for my fork of the microzig repository.
[ ] Add DEPLOY_ROOT_DATA_PATH secret for actions. This specifies the root of the data directory when publishing to a static file site (My environment needed a different value than the old workflow, so I added it as a secret that can be configured).

Remarks

(a): Runs if a change was made to any of:

.github/**
build.zig*
tools/**
core/**
bsp/**
examples/**

(b): The branch is created off of main in the format of: master-patch/{sha}. Example: master-patch/1895868a2cf6783cd9be4653b0f99503d4c36f03. This was chosen because it prevents duplication of branch names allowing multiple patches to be open at any given time.

Cons: The major con of this is that if not maintained actively, the list of open branches can balloon (This is also a downside of (d))

(c): Github stores CI results against the sha. This means that if you directly run the master test against the same commit on main, it failing will turn main red. That is something I wanted to ensure did not happen. Creates an empty commit with the following details:

author: ZEG Github Action <>
message: chore: commit for zig master build ci

(d): Creates a PR from the master-patch/* branch to zig-master with the below details. See (b) for the main con.

title: Testing commit {sha} with zig master
body: Created by Github action
Example: https://github.com/EliSauder/microzig/pull/47

(e): For the time being the tags expected are in either of the below formats. I am imaging for the website, that it just behaves like trunk based development without versions. These would only be for microzig and all of its tools (i.e. everything gets versioned together)

v*.*.*
v*.*.*-* (beta, alpha, rc, etc.)

(f): To cap off the whole process, upon a successful build and deploy, a draft release is created in GitHub for the tag that triggered the release. Draft is automatically marked as prerelease if the version contains: beta, alpha or rc

Realized I forgot to mention it in the main PR message. This currently also includes some cleanup effort. I've removed a lot of the LICENSE files except from the root of the project and from each of the tools. I also removed old workflows, unused files, etc.

Update: I removed the dependency of having a separate PAT. GITHUB_TOKEN has permission configurations available.
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token

Update: I removed the dependency of having a separate PAT. GITHUB_TOKEN has permission configurations available. https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token

After doing some more testing I re-realized why I did the PAT method over continuing with the GITHUB_TOKEN. The reason is that with using GITHUB_TOKEN, it will not trigger workflows (i.e. the zig-master build workflow). Here is the section in the documentation about it. https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow#triggering-a-workflow-from-a-workflow
GitHub Docs
Triggering a workflow - GitHub Docs
Image
Here is the specific paragraph that is relavent to enabling this ability:

If you do want to trigger a workflow from within a workflow run, you can use a GitHub App installation access token or a personal access token instead of GITHUB_TOKEN to trigger events that require a token.

Zon version overriding added. This can be removed if desired, however, based on my idea on what the publish should do, everything in the repo should be versioned together. As such, the publish workflow will now overwrite the version specified in all of the zon files with the tag that is provided.
Notes: This overwrite will only occur if the version is a semver or a semver prefixed by v.
Example generation with a tag: v0.12.2.-beta25.

Update:
Features added:

Boxzer output is now flattened in the release.

Any given release has the folder path zig-{{zig version}}/{{artifact}}-{{artifact_version}}/ e.g. zig-0.13.0/microzig-0.1.0/
The folder structure within this folder matches the image below
An example can be viewed here: https://microzig.funtimes.meme/zig-0.13.0/microzig-0.12.2-beta44/ (if the link doesn't work, please see the microzig releases for an example as I may have removed my test environment).

Microzig repository variables/secrets needed:

Variables

MZ_TARGET_ZIG_VERSION - The primary version to build/publish for microzig/regz/uf2/etc.
WS_TARGET_ZIG_VERSION - The version to build/publish the website with.

Secrets

DEPLOY_MZ_HOST - When publishing microzig, host address to publish to.
DEPLOY_MZ_PORT - When publishing microzig, port on the host to use.
DEPLOY_MZ_PRIVATE_KEY - When publishing microzig, private key to connect with.
DEPLOY_MZ_ROOT_DATA_PATH - When publishing microzig, location of directory to store data to within the host.
DEPLOY_MZ_USER - When publishing microzig, user to connect with.
DEPLOY_WS_HOST - When publishing website, host to publish to.
DEPLOY_WS_PORT - When publishing website, port to publish to.
DEPLOY_WS_PRIVATE_KEY - When publishing website, private key to connect with.
DEPLOY_WS_ROOT_DATA_PATH - When publishing website, location of directory to store data to within the host.
DEPLOY_WS_USER - When publishing website, user to connect with.
DOWNLOAD_URL - When publishing microzig, download url to use with boxzer.
PR_CREATE_TOKEN - Token that is used when creating the PR against the zig-master branch. This token is needed to ensure that the PR can trigger workflows itself.

Other:

Creation of the zig-master branch.

I additionally added some of the commits from #229 to enable the website to build so I could validate that it worked.

Alternatively, can we cretae something like a "config file" where all variables for the workflows will be defined, and we can make the secret deduplication there?

Wouldn't that be insecure? Storing private keys in a text file doesn't seem wise. Though, if we made the content of the text file the value of the secret we could do that.
Though, I'm not sure what the benefit over just having the secrets would be.

Alternatively, can we cretae something like a "config file" where all variables for the workflows will be defined, and we can make the secret deduplication there?

Wouldn't that be insecure? Storing private keys in a text file doesn't seem wise. Though, if we made the content of the text file the value of the secret we could do that. Though, I'm not sure what the benefit over just having the secrets would be.

This wasn't meant as a physical file but more as a "github ci file" which can be included or similar, so we don't have to spread the actual secrets across all files.
But in the end, it would also just increase complexity for little benefit

Alternatively, can we cretae something like a "config file" where all variables for the workflows will be defined, and we can make the secret deduplication there?

Wouldn't that be insecure? Storing private keys in a text file doesn't seem wise. Though, if we made the content of the text file the value of the secret we could do that. Though, I'm not sure what the benefit over just having the secrets would be.

This wasn't meant as a physical file but more as a "github ci file" which can be included or similar, so we don't have to spread the actual secrets across all files.
But in the end, it would also just increase complexity for little benefit

We could turn it into a job/workflow that job would then have outputs which could be used by subsequent jobs. However, we run into the same issue of storing information that should be secret within an actual file that is publicly viewable.

Updated it with a simplified CI.

Remove boxzer flattening and that will end up changed on the repository level.
Simplify publish workflows (merged website publishing into one file)
Remove the build automation against zig master.
Reverted secrets to be microzig/website agnostic (DEPLOY_MZ_HOST & DEPLOY_WS_HOST -> DEPLOY_HOST)

Current list of required repository/org secrets should match the old list with a couple additions:

DEPLOY_HOST
DEPLOY_PORT
DEPLOY_PRIVATE_KEY
DEPLOY_ROOT_DATA_PATH
BOXZER_DOWNLOADS_URL

Current list of required repository/org variables:

MZ_TARGET_ZIG_VERSION
WS_TARGET_ZIG_VERSION

I'm going to close this and create a new PR since it'll be different with the new setup.

authors: EliSauder ikskuh

repo: ZigEmbeddedGroup/microzig

license: Zlib


text:
🛑 blog.zinglix.xyz is down

In 9acd9e2, blog.zinglix.xyz (https://blog.zinglix.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: blog.zinglix.xyz is back up in 4bfb635.

repo: ZingLix/blog-mirror-uptime


text:
🛑 blog.zinglix.xyz is down

In 4e6b5a5, blog.zinglix.xyz (https://blog.zinglix.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: blog.zinglix.xyz is back up in 67543c9.


text:
Allow suffix string value

Great library!  Just looking for one additional bit of functionality.
I have UX requirements to display both a custom symbol as well as a string suffix on prices under certain scenarios.  The main example of this is to distinguish between currencies sharing the same symbol, such as USD/CAD/AUD.  Allowing the specification of an optional suffix string would support displays such as:
$100.00 USD
$100.00 CAD
$100.00 AUD

I have a PR I will submit that will support this if suffixSymbol is passed as a string instead of a boolean.

That all makes sense, thanks for the PR!

repo: Zmetser/angular-currency-filter

license: mit


text:
🛑 Invoice - LTI Lite (Canvas) is down

In 8782fee, Invoice - LTI Lite (Canvas) (https://zql.zollege.com/lti/invoice?email=r.watkins@zollege.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Invoice - LTI Lite (Canvas) is back up in 60ed9d6.

repo: Zollege/status


text:
🛑 Evansville Dental Assistant School is down

In 0178735, Evansville Dental Assistant School (https://evansvilledentalassistantschool.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Evansville Dental Assistant School is back up in a986e94.


text:
Claiming Brewing Stand

Hello,
I have a problem with the brewing stand, when a player claim a brewing stand and destroy it, the place of this brewing stand stay claim for the player.
But this system with furnaces work fine.

Try update to the latest version.

I just test that issue on 4.7.2

Does the player have Builder's job? In the jobConfig.yml file, is there a block type in the Place method that is Brewing_Stand?

Nothing of that, I don't use the Builder's job

I'll test it and, if that's what it is, we'll try to fix it. If it works properly, it may take time.

authors: Momonche montlikadani

repo: Zrips/Jobs


text:
invalid type definitions in media_player.ts

lib/entities/media_player.ts
- attributes has invalid type definition!
https://github.com/ZsakaiBalint/integration-node-library/blob/7a95faa91efef5630752f560ecd552b762b53e8c/lib/entities/media_player.ts#L205
Entity attributes are not a string -> string map / record. Only the key is a string and the value can be number, string, boolean, array, …
See also constructor documentation in .js file with a link to the documentation.
- This should have been caught in the test/media_player.test.ts unit test:
https://github.com/ZsakaiBalint/integration-node-library/commit/005fd91ccdaa1c666855e00c87181fa68728b322#diff-7e75fcd83b8107ea8ac224f1397ffb951709cea32d8e1c8c892ce0b9da66281cR49
- shuffle was defined as boolean, but was changed into a string!
- volume was defined as a number, but was changed into a string!
- In climate.ts, cover.ts, light.ts, remote.ts, sensor.ts, switch.ts this was done correctly with
"attributes?: Map<string, any> | Record<string, any>;"

I updated the types:
attributes?: Partial<Record<ATTRIBUTES, STATES | number | boolean | string[] | string>>;

repo: ZsakaiBalint/integration-node-library


text:
Feature branch

Odin Projects

Hi @ZuhRa-HashiMi  🙋♀,

Excellent work! 💯 You have done a great job implementing all the project requirements. 🥳 Your feature is complete! Congratulations!!!🎊
Comment:
Below I provided some ‼ Important Comments you need to follow in your future projects in order to get the approval for that.

Highlights 🌞
✔ Created a professional Repo (You created a repository with your project name)
✔ Correct use of Gitflow (You created the development branch and made it as your default branch, then created and committed your work on your feature branch)
✔ Commit messages are meaningful
✔ Setup the linters correctly (You added the correct linters config into your project according to the language you used on your code)
✔ No linter errors (All linters checks have been passed 🟢)
✔ You have followed the Odin project task and committed using command line
✔ Created the pull-request (From your feature branch to the development branch you created a pull-request and submitted the pull request link for review)
❌ Good PR description (You added a meaningful description to you PR about your work and the features you added on this pull request)
Status: Approved✅

Cheers 🥂 and Happy coding!!! 👯 Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me @ahzamir in your question so I can receive the notification.
You have to implement all requirements and comments provided by the code reviewer in order to receive the final approval on your project

authors: ZuhRa-HashiMi ahzamir


text:
Parse dataset on backed

Parsing on frontend will cause the browser to freeze, if the file is too big. File should be uploaded to backend and parsed there.
Maybe experiment with streams and only parse/send the first line.

Still parsing on frontend, but using streams instead.

repo: a-blaho/semanti-core


text:
🛑 RAIDA#17 Singapore is down

In fc17415, RAIDA#17 Singapore ($RAIDA_17) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RAIDA#17 Singapore is back up in 7d14a6d.

repo: a-lang/raida-uptime


text:
Can gaps be filled with just extension reads?

Hello,
Can Dentist be configured to fill gaps with just extension reads (the purple and orange ones in fig) ?  (e.g. by setting "min-spanning-reads" to 0)
 (From the DENTIST paper supplementary figure 1)
Thanks,
Tim

Hi Tim,
I am a little uncertain about your intentions. What are you trying to achieve?
Generally, you can enable partial gap closing – using the extending reads – by setting only: both. However, I strongly discourage this because the generated sequences are very prone to all sorts of errors. In case of a pure extension, min-reads-per-pile-up will determine the minimum number of extending reads required. This should not be any lower than the default 3. To reduce useless modifications, you may increase min-extension-length (default 100bp). See the list of CLI options for help on individual options.
In the default setting only: spanning only gaps that have support by spanning reads will be closed and all incident spanning and extending reads will be used to build a consensus. Is this what you were concerned with?
I just realized that the only option is rather poorly documented. You can find the valid values in the API docs.

Hi Arne,
Thanks for providing the relevant parameters.  I am trying to fill gaps that might be longer than a typical pacbio read, and the assembly in question is assembled from long reads.   To help minimise inaccuracies, I am running DENTIST with very specific inputs: only one gap and enriched reads for that gap.   Information about that specific gap is provided from the long-read assembly graph, from which the adjacent contigs, approximate gap size (based on coverage), and repeating unit is known.
However, when I tried to test run DENTIST for just one artificial gap that is 50kbp long under only: both or only: extending, an error occurs (error files attached).
Thanks,
Tim
purged-output.log
dentist_run.e77671310.txt

Thanks for looking into it and responding, @a-ludi .  Disabling purging did the trick.

Glad I could help. I consider this issue done for now.

authors: a-ludi lautimothy

repo: a-ludi/dentist


text:
🛑 West Broward Massage is down

In 54810ba, West Broward Massage (https://westbrowardtherapeuticmassage.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: West Broward Massage is back up in 726b733 after 6 minutes.


text:
🛑 WSINGRESOS - RECIBOPAGO is down

In 35e9f15, WSINGRESOS - RECIBOPAGO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsRecibosPagosWeb.r) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WSINGRESOS - RECIBOPAGO is back up in 3b7f163.

repo: aafyyuc/upptime


text:
🛑 KIOSKOS - HOME is down

In 2749763, KIOSKOS - HOME (https://recaudacion.yucatan.gob.mx) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KIOSKOS - HOME is back up in cabede6.


text:
Filtering sometimes doesn't work

On macOS 11.5.2, unshaky 0.7.0.
Currently I have 55ms for global setting and 130ms for Space.
For some reason, the chattering doesn't get filtered for unknown reason. Here's a couple of samples:
1631548154.279290 Key( 40| 49|         Space|         0|130) E(10)
1631548154.396071 Key( 40| 49|         Space|         0|130) E(11)
1631548154.401034 Key( 40| 49|         Space|         0|130) E(10)
1631548154.404899 Key( 40| 49|         Space|         0|130) E(11)

The delta from keyup to keydown was only ~5ms, yet still registered.
1631548383.173862 Key( 40| 49|         Space|         0|130) E(10)
1631548383.231955 Key( 40| 14|             E|         0| 55) E(11)
1631548383.274003 Key( 40| 49|         Space|         0|130) E(11)
1631548383.278947 Key( 40| 49|         Space|         0|130) E(10)
1631548383.279698 Key( 40| 49|         Space|         0|130) E(11)

The delta here was about 4.9ms, and registered.
Working log:
1631548512.333682 Key( 40| 49|         Space|         0|130) E(11)
1631548512.342858 Key( 40| 49|         Space|         0|130) E(10) DISMISSED
1631548512.342986 Key( 40| 49|         Space|         0|130) E(11) DISMISSED

Worked fine in this case, ~9ms delta.
Is there any known issue ?

@sky417 this is pretty strange. From the log, my guess is it is somehow triggers the special logic:
I cannot remember too much details. Will try to re-visit this when I have time
https://github.com/aahung/Unshaky/blob/feac0093d0d823c183a6b83800a399a633b448cf/Unshaky/ShakyPressPreventer.m#L182-L196
https://github.com/aahung/Unshaky/blob/feac0093d0d823c183a6b83800a399a633b448cf/Unshaky/ShakyPressPreventer.m#L220

repo: aahung/Unshaky


text:
Spanish translation

Language
Spanish.
Can you help with the translation?
(Yes/No)
Yes.

@jadraker thanks for your interest. Which of the below should I choose?

Spanish (es)
Spanish (Latin America) (es-419)

Hi,
Spanish Latin America es-419.

Hi @jadraker  thanks for your interest. A branch named "lang/es-149" has been created and you can see 4 string files in es-149.lproj
For each file you will see several "some identifier here" = "some text in English here"; and only "some text in English here" part need translation. Besides, /* ... */ are comments and they don't need translation.
Thanks!

Hi @aahung,
Please tell me if I translated the first file as it should: https://github.com/aahung/Unshaky/compare/lang/es-419...jadraker:patch-1.
Thank you and congratulations for this software. I hope 2019 and future Mac implement a butterfly or another more reliable keyboard. I've had two MBP 2018 with same problems.

Translation seems good, just need it to the line below. For example, line 3 instead of line 2. Line 2 is actually just comment and you can leave it there.
So annoying you have two Mac being affected ...

Hi @aahung,
The 4 files you requested were translated into Spanish LA.
Please tell me if it's okay (I translated the 4 files again correcting the problem with the comments).
What are the following steps to see this translation go live? :)
Thank you.

Thanks! Did you create a pull request?
I will test it a bit to ensure the UI looks good, and it will go live in the next version.

@jadraker I already merged your translation, there is nothing left for you to do. Thank you!

authors: aahung jadraker


text:
test(lint): Add lint step to molecule.yml

This lint step enables tests to fail locally before submitting code to
the remote repo where github actions will fail because of linting errors.
On the local machine yamllint as well as ansible-lint need to be installed. Like so:
python3 -m pip install molecule[lint,] ansible-lint

Hello @stevenengland! Adding linter to molecule is unnecessary. YAML Linter and Ansible Linter are added to Github Actions as separate steps. Adding linker to molecule is extending running time, while having 4 test cases as we do, it's extending it in every Molecule run.
The best idea is to install and run ansible-lint on local machine or just use Github Actions version.
I've also have a good tip, when you push to your branch and you are trying to make PR, you have this branch available on your profile in your fork and Ansible lint is run as Action anyway but only in your workspace: https://github.com/stevenengland/ansible_nextcloud/actions , so you can use it from there before adding PR :)

Hi @wiktor2200, thank you for your explaination. The way you write it, I now understand the caveat very well. That makes the solution I wanted to introduce less than ideal. Since I'm stuck with the idea that the local test pipeline doesn't automatically include linting for everyone contributing, I'm wondering if an alternative would be useful that only takes effect for local tests (when running molecule lint/test) but doesn't run when the code is checked in online, where the Github Actions check linting. You think that this is possible? E.g. by checking certain Github environment variables for presence and if they are not then run the linter locally. I will have a look into this and then you can vote for or against that solution :)

Hi @wiktor2200, thank you for your explaination. The way you write it, I now understand the caveat very well. That makes the solution I wanted to introduce less than ideal. Since I'm stuck with the idea that the local test pipeline doesn't automatically include linting for everyone contributing, I'm wondering if an alternative would be useful that only takes effect for local tests (when running molecule lint/test) but doesn't run when the code is checked in online, where the Github Actions check linting. You think that this is possible? E.g. by checking certain Github environment variables for presence and if they are not then run the linter locally. I will have a look into this and then you can vote for or against that solution :)
Update: When I have a look to other repos where workflows fail, it is often the linting :-D Maybe because of forgotten or differently configured local linting ;)

@stevenengland good point.. The way to do it locally is through pre-commit.

Wow, what a powerful tool. I really like the idea of the pre-commit project. I will test it. Just for further reference and to teach myself I finished the idea of using a environment variable approach to distinguish between local and remote tests.
What do you say: Shall I instead refactor the code to use a pre-commit config or shall the complete PR/idea of local forced linting be rejected?

Actually, if you add pre-commit config you will be achieving both, since when you have it, you cannot commit if linting does not pass. Basically you just need to copy paste this file to the root and add to our contributing documentation that you need to run: pre-commit install to work with this project.

pre-commit is extremely useful tool, especially in very complex environments with multiple testing schemas or lots of dependencies (such as in js/ts/py projects) or when CI run lasts long time.
But in my opinion using pre-commit is an overkill here. It's additional step before contributing and it requires some dependencies to be installed. I usually commit from multiple devices which has different configurations or sometimes when small changes are needed even from browser via Github Editor. So now I only need my Github account or SSH/GPG keys to contribute and it can be done from anywhere with clean terminal, pre-commit limits that.
@aalaesar WDYT about it?

pre-commit is extremely useful tool, especially in very complex environments with multiple testing schemas or lots of dependencies (such as in js/ts/py projects) or when CI run lasts long time.
But in my opinion using pre-commit is an overkill here. It's additional step before contributing and it requires some dependencies to be installed. I usually commit from multiple devices which has different configurations or sometimes when small changes are needed even from browser via Github Editor. So now I only need my Github account or SSH/GPG keys to contribute and it can be done from anywhere with clean terminal, pre-commit limits that.
@aalaesar WDYT about it?

Also a very interesting opinion. Thanks for sharing. From my point of view I am unsure. I made the refactoring, now you can decide what is the best solution :)

@wiktor2200 actually this is not the case. pre-commit is only enforced when you do a pre-commit install, it will not limit you from doing any changes from Github directly actually. I have pre-commit in all my projects also, it is really helpful I would say. No downsides except Dependabot does not update versions on pre-commit config.

authors: staticdev stevenengland wiktor2200


text:
OpenBSD build fails

OpenBSD doesn't have the constants AI_ALL and AI_V4MAPPED, so building on that platform fails. I'm happy to submit a pull request, if you can suggest how you'd like it fixed. I was able to build by removing all references to those constants, but I assume that's not what you want.

Here are the C compiler errors
generate_types_step_2.c:796:39: error: use of undeclared identifier 'AI_ALL'
     enum { check_AI_ALL_const = (int)AI_ALL };
                                      ^
generate_types_step_2.c:797:15: error: use of undeclared identifier 'AI_ALL'
     int v = (AI_ALL);
              ^
generate_types_step_2.c:803:44: error: use of undeclared identifier 'AI_V4MAPPED'
     enum { check_AI_V4MAPPED_const = (int)AI_V4MAPPED };
                                           ^
generate_types_step_2.c:804:15: error: use of undeclared identifier 'AI_V4MAPPED'
     int v = (AI_V4MAPPED);
              ^
4 errors generated.

Here is the build output
#=== ERROR while compiling luv.0.5.11 =========================================#
# context     2.1.4 | openbsd/x86_64 | ocaml-base-compiler.5.0.0 | https://opam.ocaml.org#28feb0dc
# path        ~/.opam/5.0.0/.opam-switch/build/luv.0.5.11
# command     ~/.opam/5.0.0/bin/dune build -p luv -j 4
# exit-code   1
# env-file    ~/.opam/log/luv-39113-378b44.env
# output-file ~/.opam/log/luv-39113-378b44.out
### output ###
# generate_types_step_2.c:804:15: error: use of undeclared identifier 'AI_V4MAPPED'
# [...]
# 4 errors generated.
# File "_build/.dune/default/src/c/dune", line 45, characters 0-813:
# 45 | (rule
# 46 |  (targets libuv.a dlluv%{ext_dll})
# 47 |  (deps (source_tree vendor))
# ....
# 62 |    "cp vendor/libuv/libuv.so.1.0.0 dlluv.so || \
# 63 |     cp vendor/libuv/libuv.1.dylib dlluv.so || \
# 64 |     cp vendor/bin/libuv-1.dll dlluv.dll")))))
# (cd _build/default/src/c && /usr/local/bin/bash -e -u -o pipefail -c 'cp vendor/libuv/libuv.
so.1.0.0 dlluv.so || cp vendor/libuv/libuv.1.dylib dlluv.so || cp vendor/bin/libuv-1.dll dlluv
.dll') &> /dev/null
# Command exited with code 1.

I've attached the output file luv-39113-378b44.out

generate_types_start.c includes helpers.h into the file it generates:
https://github.com/aantron/luv/blob/fbb87daff2b61aee747c56224b193d554345302c/src/c/generate_types_start.ml#L6-L15
It might be sufficient to just add some #ifndefs, guarded by a macro test for OpenBSD, to the beginning of this file, as already done for some constants on Windows:
https://github.com/aantron/luv/blob/fbb87daff2b61aee747c56224b193d554345302c/src/c/helpers.h#L22-L36
We would then probably want to just document that AI_ALL and AI_V4MAPPED are meaningless on OpenBSD.
Would you still be willing to open a PR for this? Otherwise, I am happy to fix this within a few days. Thank you!

Sorry for the slow response. I've been traveling for the last couple weeks. It doesn't look like I'll be able to get to this anytime soon.  If you're willing to take it from here, that'd be great. Thanks.

I don't have ready access to an OpenBSD machine, unfortunately, so I can only make very slow progress.

authors: aantron mndrix

repo: aantron/luv


text:
Add aggregates for economic & political blocks

It would be great to have additional aggregates of countries in their respective economic/political blocks & institutions, e.g. EU, Schengen Area, G7, G8, G20, Emerging Markets, so you could (for example) compare a single EU country to the EU total… and you'd have a possible indicator for economic recovery, when e.g. both the G7 & the emerging markets display a downward trend.
PS: and a world total would also be a good thing to have.

Maybe simpler, as this will maybe an endless discussion on requests:

Add an input-box with a comma-separated list of country-codes and a button "select"
Add a button "combine" with an input-box, to combine the selected countries under the provided name. This selection is listed (with an 'x' to delete it) at the bottom. Selecting it, makes the graph show the aggregated data.

authors: JayBrown VincentSC

repo: aatishb/covidtrends


text:
🛑 Musga is down

In f937ffb, Musga (https://musga.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Musga is back up in 1217d3d.

repo: abaertsoen/upptime


text:
Compiling older versions of PPL

08062021
Older version failed, still moving to work

ppl-user-c-interface-1.0.pdf

repo: abakasam/abakasam


text:
Videohas no propType for native propRCTVideo.bufferConfigof native typeMap`

When creating an issue, please ensure that you provide as much information as you can. Issues with a basic description will sadly be ignored as it doesn't help diagnose the issue :(
If you don't help me, I can't help you ¯\_(ツ)_/¯
Here are some common things to include that can help your issue be diagnosed.

[ ] react-native-af-video-player version:

[x] React Native version:

[ ] OS:

[ ] Has this issue already been raised?

[ ] Have you clearly read and understood the Readme?

[ ] Code and explanation to replicate this issue:

[ ] Are there any console logs?

[ ] Include Screeshots / Video:

I am also facing the same issue. Help will be appreciated

Same problem. The problem appear when i update some things in gradle because i couldn't install the app in the device. I needed to do thtat because there was a problem with this package "react-native-linear-gradient". After that, this error shows up

The issue is that the new version of react-native-linear-gradient is using the new gradle and some new syntax. Downgrading to linear-gradient 2.3.0 solves the issue! Simply add "react-native-linear-gradient": "2.3.0" to your projects package.json

That not works for me, I've tried to downgrading my version o gradle to 2.2.3 but i'm still having the same problem.
This is my package.json :
"dependencies": {     "moment": "^2.22.2",     "native-base": "^2.7.2",     "react": "16.3.1",     "react-devtools": "^3.2.3",     "react-native": "0.55.2",     "react-native-af-video-player": "^0.2.1",     "react-native-carousel-view": "^0.5.1",     "react-native-datepicker": "^1.7.2",     "react-native-fs": "^2.11.15",     "react-native-router-flux": "^4.0.0-beta.31",     "react-native-smart-carousel": "^1.1.0",     "react-native-svg": "^6.5.2",     "react-native-svg-icon": "^0.8.1",     "react-native-vector-icons": "^5.0.0",     "react-native-video": "^3.1.0",     "react-navigation": "^1.5.12",     "rn-fetch-blob": "^0.10.13",     "react-native-linear-gradient": "2.3.0",     "react-native-keep-awake": "^2.0.6",     "react-native-orientation": "^3.1.0",     "react-native-slider": "https://github.com/abbasfreestyle/react-native-slider.git"   },   "devDependencies": {     "babel-cli": "^6.26.0",     "babel-preset-flow": "^6.23.0",     "babel-jest": "22.4.3",     "babel-preset-react-native": "4.0.0",     "jest": "22.4.3",     "react-test-renderer": "16.3.1"   },   "jest": {     "preset": "react-native"   } }
And this is my build.gradle :
`def enableSeparateBuildPerCPUArchitecture = false
/**

Run Proguard to shrink the Java bytecode in release builds.
*/
def enableProguardInReleaseBuilds = false

android {
compileSdkVersion 23
buildToolsVersion "23.0.1"
defaultConfig {
    applicationId "com.taekwongofront"
    minSdkVersion 16
    targetSdkVersion 22
    versionCode 1
    versionName "1.0"
    ndk {
        abiFilters "armeabi-v7a", "x86"
    }
}
splits {
    abi {
        reset()
        enable enableSeparateBuildPerCPUArchitecture
        universalApk false  // If true, also generate a universal APK
        include "armeabi-v7a", "x86"
    }
}
buildTypes {
    release {
        minifyEnabled enableProguardInReleaseBuilds
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}
// applicationVariants are e.g. debug, release
applicationVariants.all { variant ->
    variant.outputs.each { output ->
        // For each separate APK per architecture, set a unique version code as described here:
        // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
        def versionCodes = ["armeabi-v7a":1, "x86":2]
        def abi = output.getFilter(OutputFile.ABI)
        if (abi != null) {  // null for the universal-debug, universal-release variants
            output.versionCodeOverride =
                    versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
        }
    }
}

}
dependencies {
compile project(':react-native-orientation')
compile project(':react-native-keep-awake')
compile project(':react-native-linear-gradient')
compile project(':rn-fetch-blob')
compile project(':react-native-video')
compile project(':react-native-vector-icons')
compile project(':react-native-svg')
compile project(':react-native-fs')
compile fileTree(dir: "libs", include: ["*.jar"])
compile "com.android.support:appcompat-v7:23.0.1"
compile "com.facebook.react:react-native:+"  // From node_modules
}
// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
from configurations.compile
into 'libs'
}`
`buildscript {
repositories {
jcenter()
maven { url 'https://maven.google.com' }
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
mavenLocal()
jcenter()
maven { url 'https://maven.google.com' }
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
}`

I got the same problem with react-native-linear-gradient : 2.3.0..

I got the same problem with react-native-linear-gradient : 2.3.0..

Still no update with this issue?

authors: MrHazimAli Oshianor VasilNikolov ddonny felire ramviki


text:
Doesn't work with virtual directories

Simply create a virtual directory for the WCF service and things would break.

Swagger UI is still on localhost/api-docs even though I set virt dir as localhost/virt-dir (hence I expect something like localhost/virt-dir/api-docs/swagger.json)
API routes in Swagger UI don't have the virt dir address included

This was more about how the route binding works :smiley:

repo: abelsilva/swaggerwcf


text:
Query parameters not parsed when UriTemplate is not included

I added the following to the IStore.cs file
        [OperationContract]
        [WebInvokeAttribute(Method = "GET")]
        void BookTest(string id1, string id2);

For this declaration, id1 and id2 should be query parameters. SwaggerWcf is treating them as request body parameters.
The swagger.json file has the following:
        "/v1/rest/BookTest":
        {
        "get":{
        "operationId":"SwaggerWcf.Test.Service.BookStore.BookTest",
        "consumes":["application/json","application/xml"],
        "produces":["application/json","application/xml"],
        "parameters":[
        {"name":"id1","in":"body","required":true,"type":"string"},
        {"name":"id2","in":"body","required":true,"type":"string"}],
        "responses":{"default":{"description":"not available"}}}}

    Expected:

        "/v1/rest/BookTest":
        { "get":{
        "operationId":"SwaggerWcf.Test.Service.BookStore.BookTest",
        "consumes":["application/json","application/xml"],
        "produces":["application/json","application/xml"],
        "parameters":[
        {"name":"id1","in":"query","required":true,"type":"string"},
        {"name":"id2","in":"query","required":true,"type":"string"}],
        "responses":{"default":{"description":"not available"}}}},

making these changes only for GET requests

can you check if it works with the latest version?

Yes this works with latest revision. Thank you.

authors: abelsilva colbroth


text:
Expiration status of the '"new-awesome-permission-feature"' flag

The @FlagType.Permission owner: momomomo111 will expire soon!
Please consider deleting @FlagType.Permission as the expiry date of 2023-06-20 is scheduled to pass within a week.The flag of key: "new-awesome-permission-feature" is used in the awesomePermissionFeatureEnabled function.

https://github.com/abema/workflow-test-flagfit/blob/b9094b1a906c362c505d98fbb2f2002ad6d4c165/sample-android/src/main/java/tv/abema/fragfit/SampleFlagService.kt#L48-L57

Warning
The @FlagType.Permission created by owner: momomomo111 has expired!
Please consider deleting @FlagType.Permission as the expiration date has passed on 2023-06-10.
The flag of key: "new-awesome-permission-feature" is used in the awesomePermissionFeatureEnabled function.

Warning
The @FlagType.Permission created by owner: momomomo111 has expired!
Please consider deleting @FlagType.Permission as the expiration date has passed on 2023-06-10.
The flag of key: "new-awesome-permission-feature" is used in the awesomePermissionFeatureEnabled function.

repo: abema/workflow-test-flagfit


text:
Update README.md

Mostly added links to existing content.  Lots and lots of links.

How about now?


text:
Colorspace conversion even if no colorspace was defined

Description
There is a logic bug in the PiGear color conversion, that makes vidgear try to perform said operation even though no colorspace was defined.
gear = PiGear((800, 600), framerate=24)

vidgear throws an exception because opencv's cvtColor does not accept None as colorspace.
Acknowledgment

[X] A brief but descriptive Title of your issue
[X] I have searched the issues for my issue and found nothing related or helpful.
[X] I have read the FAQ.
[X] I have read the Wiki.
[X] I have read the Contributing Guidelines.

There is an issue that seems to have tackled the same problem, yet I wonder why this change has not reached master.
Environment

VidGear version: 0.1.6
Branch: PyPi
Python version: 3.5.2
pip version: 9.0.1-2+rpt2
Operating System and version: Raspbian for Robots 9.11

Expected Behavior
No conversion of colorspace happens.
Actual Behavior
PiGear :: WARNING :: Input camera_num value `{}` is invalid, Defaulting to index 0!
PiGear :: ERROR :: an integer is required (got type NoneType)
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/vidgear/gears/pigear.py", line 147, in __init__
    if not(self.frame is None and self.color_space is None): self.frame = cv2.cvtColor(self.frame, self.color_space)
TypeError: an integer is required (got type NoneType)
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/vidgear/gears/pigear.py", line 147, in __init__
    if not(self.frame is None and self.color_space is None): self.frame = cv2.cvtColor(self.frame, self.color_space)
TypeError: an integer is required (got type NoneType)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/witling/dev/botlib/botlib/bot.py", line 58, in camera
    self._camera = Camera(self)
  File "/home/witling/dev/botlib/botlib/camera.py", line 12, in __init__
    self._stream = PiGear(self._resolution, framerate=self._framerate)
  File "/usr/local/lib/python3.5/dist-packages/vidgear/gears/pigear.py", line 150, in __init__
    raise RuntimeError('[PiGear:ERROR] :: Camera Module failed to initialize!')
RuntimeError: [PiGear:ERROR] :: Camera Module failed to initialize!

Possible Fix
The colorspace conversion can only happen if frame and colorspace are defined so,
I believe that this line https://github.com/abhiTronix/vidgear/blob/8357aa5d6df59df45bd21a7c23c0950c6b152f59/vidgear/gears/pigear.py#L147 should rather be
if not (self.frame is None or self.color_space is None): ...

This way, the conversion will only happen if self.frame and self.color_space are not None. (See DeMorgan's law)

@witling Thanks for finding this bug, much appreciated. I wonder how a small logic error snicked passed without making any error for so long.
Bug: The current logic: if not(self.frame is None and self.color_space is None) is completely incorrect in this context.
Please wait, I'm pushing related PR in the development branch shortly.

@witling Kindly install development branch as follows:
git clone git clone https://github.com/abhiTronix/vidgear.git
cd vidgear
git checkout development
sudo pip install .
cd

Then check if the problem is gone?

if not (self.frame is None or self.color_space is None): ...

Yes, a simple OR will also be correct.

@witling Closed and marked solved for now. Kindly share your results when you're ready. Good luck!

The code works now. Thanks for your effort!

@witling Kindly install development branch as follows:
git clone git clone https://github.com/abhiTronix/vidgear.git
cd vidgear
git checkout development
sudo pip install .
cd

Then check if the problem is gone?

if not (self.frame is None or self.color_space is None): ...

Yes, a simple OR will also be correct.

Hi guys,
I tried the commands above but didnt work?
Any solution?
Thanks...

@fahrettine the first line of the install script has an error. try to adapt your setup script like:
git clone https://github.com/abhiTronix/vidgear.git
cd vidgear
git checkout development
sudo pip install .

Please note that 'didnt work' is not a very helpful problem description for a software engineer.

Hi guys,
I tried the commands above but didnt work?
Any solution?
Thanks...

@fahrettine Either you're not installing vidgear for your python3-pip version, OR calling your script with python2 instead or python3, OR there are multiple python versions are installed on your system, Anyways, Try these commands and revert here:
git clone https://github.com/abhiTronix/vidgear.git
cd vidgear
git checkout testing
sudo python3 -m pip install .
cd

@fahrettine After installing vidgear as shown above, call your script with python3 {your script name}.py

Thank you very much for your quick response guys...
This helped...
git clone https://github.com/abhiTronix/vidgear.git
cd vidgear
git checkout testing
sudo python3 -m pip install .
cd

authors: abhiTronix fahrettine witling

repo: abhiTronix/vidgear


text:
standalone: Add a small "generated by" footer

Adds a very small footer
at the bottom of each page in standalone mode
that indicates that it was generated by doc2go.

Codecov Report
Base: 89.14% // Head: 89.14% // No change to project coverage :thumbsup:

Coverage data is based on head (271adcc) compared to base (809a7a4).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #65   +/-   ##
=======================================
  Coverage   89.14%   89.14%
=======================================
  Files          28       28
  Lines        1492     1492
=======================================
  Hits         1330     1330
  Misses        116      116
  Partials       46       46

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: abhinav codecov-commenter


text:
Error generating code in Local with Anthropic Key

Hi there! I saw that in hosted version a message saying I need to suscribe to a plan to use an Anthropic key appeared once I dropped an screenshot so I thought I had to be suscribed to an Anthropic plan and not a screenshot-to-code one (my fault).
Now I'm trying to use the credit I have but the only thing I am getting are errors. Now I will show all I did and the error that I am getting:
backend
.env file:

other commands:

frontend

error

That is all I have done I do not see any log indicating a problem or anything like that so I need help please. Thanks.

Thanks for sharing all the screens. Seems like you followed the steps correctly.

Can you visit 127.0.0.1:7001 in your browser? What does it look like?
Can you open your browser console after you drop in an image and let me know what's in there?

Thanks to you for answering! Looks like the problem has something to do with what you mentioned...

yeah, looks like your backend server is not actually running at that address. You're definitely running it locally on the same computer as you're using the browser on?

yeah, looks like your backend server is not actually running at that address. You're definitely running it locally on the same computer as you're using the browser on?

Yes, 99.999% sure.

Can you try localhost:7001 in your browser?

Make sure it's http, not https

Can you try localhost:7001 in your browser?

Of course, and it looks like I am getting the exact same error.

I have tried with http, https and different browsers with cache being refreshed. Also cloning the repository once again and re-executing the commands.

@abi, if I do uvicorn command changing port to 8000 for example, look at what I get.

Amazing. That means you can switch the front-end to connect to :8000 and everything should work. See https://github.com/abi/screenshot-to-code?tab=readme-ov-file#-faqs "How can I update the backend host that my front-end connects to?"
If it works, please close this issue :)

Amazing. That means you can switch the front-end to connect to :8000 and everything should work. See https://github.com/abi/screenshot-to-code?tab=readme-ov-file#-faqs "How can I update the backend host that my front-end connects to?"
If it works, please close this issue :)

It works! Closing issue with a smile in my face :)

repo: abi/screenshot-to-code


text:
🛑 DISHANPAN is down

In 522c211, DISHANPAN (https://disketpangan.kalbarprov.go.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DISHANPAN is back up in fed4d73 after 13 minutes.

repo: abimanyu/Kalbarnetworks


text:
🛑 Kab. Landak is down

In 5251350, Kab. Landak (http://landakkab.go.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kab. Landak is back up in 06376f8 after 25 minutes.


text:
emacs ycmd fails at C/C++ completion

Error in *Messages*
REQUEST [error] Error (error) while connecting to http://127.0.0.1:53686/completions.
Exception while fetching candidates: No completions found; errors in the file?

*ycmd-server* buffer
2015-03-27 15:24:30,892 - INFO - Received completion request
 2015-03-27 15:24:30,892 - DEBUG - Using filetype completion: False
 2015-03-27 15:24:31,222 - INFO - Received completion request
 2015-03-27 15:24:31,223 - DEBUG - Using filetype completion: False
 2015-03-27 15:24:31,251 - INFO - Received completion request
 2015-03-27 15:24:31,253 - DEBUG - Using filetype completion: False
 2015-03-27 15:24:32,034 - INFO - Received completion request
 2015-03-27 15:24:32,035 - DEBUG - Using filetype completion: True
 libclang: crash detected during parsing: {
   'source_filename' : '/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp'
   'command_line_args' : ['-Wall', '-Wextra', '-Wc++98-compat', '-Wno-long-long', '-Wno-variadic-macros', '-fexceptions', '-fno-rtti', '-fno-strict-aliasing', '-fPIE', '-fpic', '-DNDEBUG', '-DANDROID', '-DUSE_CLANG_COMPLETER', '-std=c++11'\
 , '-x c++', '-I/local/mnt/workspace/naseer/LA.BF64.1/ .', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libgralloc', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/l\
 iboverlay', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhwcomposer', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libcopybit', '-I/local/mnt/workspace/naseer/\
 LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libqdutils', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libexternal', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/d\
 isplay/libqservice', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libvirtual', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhdmi', '-isystem/local/mnt/workspac\
 e/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/system/core/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/libhardware/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/lib\
 hardware_legacy/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/ril/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/libnativehelper/include', '-isystem/local/mnt/workspace\
 /naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/arch-arm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/k\
 ernel/common', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/kernel/arch-arm', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/nase\
 er/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include/arm'\
 , '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libthread_db/include/', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/native/include', '-isystem/local/mnt/workspace/naseer/LA.BF6\
 4.1/ $ANDROID_BUILD_TOP/frameworks/native/opengl/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/av/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/base/inclu\
 de', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/KERNEL_OBJ/\
 usr/include', '-isystem', '/local/mnt/workspace/naseer/installs/ycmd/ycmd/../clang_includes'],
   'unsaved_files' : [('/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp', '...', 37243)],
   'options' : 143,
 }
 Traceback (most recent call last):
   File "/local/mnt/workspace/naseer/installs/ycmd/third_party/bottle/bottle.py", line 861, in _handle
     return route.call(**args)
   File "/local/mnt/workspace/naseer/installs/ycmd/third_party/bottle/bottle.py", line 1734, in wrapper
     rv = callback(*a, **ka)
   File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/watchdog_plugin.py", line 100, in wrapper
     return callback( *args, **kwargs )
   File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/hmac_plugin.py", line 54, in wrapper
     body = callback( *args, **kwargs )
   File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/handlers.py", line 100, in GetCompletions
     completer.ComputeCandidates( request_data ),
   File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/completers/completer.py", line 158, in ComputeCandidates
     candidates = self._GetCandidatesFromSubclass( request_data )
   File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/completers/completer.py", line 173, in _GetCandidatesFromSubclass
     raw_completions = self.ComputeCandidatesInner( request_data )
   File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/completers/cpp/clang_completer.py", line 101, in ComputeCandidatesInner
     raise RuntimeError( NO_COMPLETIONS_MESSAGE )
 RuntimeError: No completions found; errors in the file?
 2015-03-27 15:24:34,267 - INFO - Received event notification
 2015-03-27 15:24:34,268 - DEBUG - Event name: FileReadyToParse
 2015-03-27 15:24:34,268 - INFO - Adding buffer identifiers for file: /local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp
 libclang: crash detected during parsing: {
   'source_filename' : '/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp'
   'command_line_args' : ['-Wall', '-Wextra', '-Wc++98-compat', '-Wno-long-long', '-Wno-variadic-macros', '-fexceptions', '-fno-rtti', '-fno-strict-aliasing', '-fPIE', '-fpic', '-DNDEBUG', '-DANDROID', '-DUSE_CLANG_COMPLETER', '-std=c++11'\
 , '-x c++', '-I/local/mnt/workspace/naseer/LA.BF64.1/ .', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libgralloc', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/l\
 iboverlay', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhwcomposer', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libcopybit', '-I/local/mnt/workspace/naseer/\
 LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libqdutils', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libexternal', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/d\
 isplay/libqservice', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libvirtual', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhdmi', '-isystem/local/mnt/workspac\
 e/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/system/core/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/libhardware/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/lib\
 hardware_legacy/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/ril/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/libnativehelper/include', '-isystem/local/mnt/workspace\
 /naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/arch-arm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/k\
 ernel/common', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/kernel/arch-arm', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/nase\
 er/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include/arm'\
 , '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libthread_db/include/', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/native/include', '-isystem/local/mnt/workspace/naseer/LA.BF6\
 4.1/ $ANDROID_BUILD_TOP/frameworks/native/opengl/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/av/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/base/inclu\
 de', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/KERNEL_OBJ/\
 usr/include', '-isystem', '/local/mnt/workspace/naseer/installs/ycmd/ycmd/../clang_includes'],
   'unsaved_files' : [('/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp', '...', 37243)],
   'options' : 143,
 }

Just so I remember this in the future: there's very little we can do about libclang crashing, but we might be able to give the user feedback when something like this happens. Maybe even just directing them to the *Messages* buffer would be a good start.

@abingham I think this is an emacs-ycmd issue - comparing the flags below, it appears that the environment variable is not correctly expanded from python in emacs and the paths sent to clang are incorrect
Flags from vim
libclang: crash detected during parsing: {
   'source_filename' : '/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp'
   'command_line_args' : ['-Wall', '-Wextra', '-Wc++98-compat', '-Wno-long-long', '-Wno-variadic-macros', '-fexceptions', '-fno-rtti', '-fno-strict-aliasing', '-fPIE', '-fpic', '-DNDEBUG', '-DANDROID', '-DUSE_CLANG_COMPLETER', '-std=c++11'\
 , '-x c++', '-I/local/mnt/workspace/naseer/LA.BF64.1/ .', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libgralloc', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/l\
 iboverlay', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhwcomposer', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libcopybit', '-I/local/mnt/workspace/naseer/\
 LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libqdutils', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libexternal', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/d\
 isplay/libqservice', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libvirtual', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhdmi', '-isystem/local/mnt/workspac\
 e/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/system/core/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/libhardware/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/lib\
 hardware_legacy/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/ril/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/libnativehelper/include', '-isystem/local/mnt/workspace\
 /naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/arch-arm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/k\
 ernel/common', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/kernel/arch-arm', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/nase\
 er/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include/arm'\
 , '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libthread_db/include/', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/native/include', '-isystem/local/mnt/workspace/naseer/LA.BF6\
 4.1/ $ANDROID_BUILD_TOP/frameworks/native/opengl/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/av/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/base/inclu\
 de', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/KERNEL_OBJ/\
 usr/include', '-isystem', '/local/mnt/workspace/naseer/installs/ycmd/ycmd/../clang_includes'],
   'unsaved_files' : [('/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp', '...', 37233)],
   'options' : 143,
 }

Flags from emacs
libclang: crash detected during parsing: {
   'source_filename' : '/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp'
   'command_line_args' : ['-Wall', '-Wextra', '-Wc++98-compat', '-Wno-long-long', '-Wno-variadic-macros', '-fexceptions', '-fno-rtti', '-fno-strict-aliasing', '-fPIE', '-fpic', '-DNDEBUG', '-DANDROID', '-DUSE_CLANG_COMPLETER', '-std=c++11'\
 , '-x c++', '-I/local/mnt/workspace/naseer/LA.BF64.1/ .', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libgralloc', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/l\
 iboverlay', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhwcomposer', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libcopybit', '-I/local/mnt/workspace/naseer/\
 LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libqdutils', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libexternal', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/d\
 isplay/libqservice', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libvirtual', '-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libhdmi', '-isystem/local/mnt/workspac\
 e/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/system/core/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/libhardware/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/lib\
 hardware_legacy/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/ril/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/libnativehelper/include', '-isystem/local/mnt/workspace\
 /naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/arch-arm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/k\
 ernel/common', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libc/kernel/arch-arm', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/nase\
 er/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libstdc/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libm/include/arm'\
 , '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/bionic/libthread_db/include/', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/native/include', '-isystem/local/mnt/workspace/naseer/LA.BF6\
 4.1/ $ANDROID_BUILD_TOP/frameworks/native/opengl/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/av/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/frameworks/base/inclu\
 de', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/include', '-isystem/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/out/target/product/$TARGET_PRODUCT/obj/KERNEL_OBJ/\
 usr/include', '-isystem', '/local/mnt/workspace/naseer/installs/ycmd/ycmd/../clang_includes'],
   'unsaved_files' : [('/local/mnt/workspace/naseer/LA.BF64.1/hardware/qcom/display/libhwcomposer/hwc.cpp', '...', 37233)],
   'options' : 143,
 }

My ycm_extra_conf.py
flags = [
'-Wall',
'-Wextra',
'-Wc++98-compat',
'-Wno-long-long',
'-Wno-variadic-macros',
'-fexceptions',
'-fno-rtti',
'-fno-strict-aliasing',
'-fPIE',
'-fpic',
'-DNDEBUG',
'-DANDROID',
#'-march=armv7-a',
'-DUSE_CLANG_COMPLETER',
# THIS IS IMPORTANT! Without a "-std=<something>" flag, clang won't know which
# language to use when compiling headers. So it will guess. Badly. So C++
# headers will be compiled as C headers. You don't want that so ALWAYS specify
# a "-std=<something>".
# For a C project, you would set this to something like 'c99' instead of
# 'c++11'.
'-std=c++11',
# ...and the same thing goes for the magic -x option which specifies the
# language that the files to be compiled are written in. This is mostly
# relevant for c++ headers.
# For a C project, you would set this to 'c' instead of 'c++'.
'-x', 'c++',
'-I', '.'
]

if (os.getenv('ANDROID_BUILD_TOP')):
    hqd_path = '/hardware/qcom/display/'
    if (os.getenv('NEXUS_MSM')):
        hqd_path = hqd_path + os.getenv('NEXUS_MSM')
    print hqd_path
    androidflags = [
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libgralloc',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/liboverlay',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libhwcomposer',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libcopybit',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libqdutils',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libexternal',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libqservice',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libvirtual',
    '-I', os.getenv('ANDROID_BUILD_TOP') + hqd_path + '/libhdmi',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/system/core/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/hardware/libhardware/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/hardware/libhardware_legacy/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/hardware/ril/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/libnativehelper/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libc/arch-arm/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libc/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libc/kernel/common',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libc/kernel/arch-arm',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libstdc++/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libstdc++/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libm/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libm/include/arm',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/bionic/libthread_db/include/',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/frameworks/native/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/frameworks/native/opengl/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/frameworks/av/include',
    '-isystem', os.getenv('ANDROID_BUILD_TOP') + '/frameworks/base/include',
    '-isystem', os.getenv('OUT') + '/obj/include',
    '-isystem', os.getenv('OUT') + '/obj/KERNEL_OBJ/usr/include',
    ]
    flags = flags + androidflags

CC @Valloric for info

I'm not sure how emacs-ycmd (or emacs at all) could be responsible for expanding environment variables in Python. All that emacs-ycmd does is tell ycmd where the extra-config is and that it should be loaded. After that it's up to ycmd to "do the right thing" with the values in there.
It might be that ANDROID_BUILD_TOP isn't defined correctly in the emacs environment. If you use M-x getenv, what value (if any) do you see for ANDRDOID_BUILD_TOP? It seems like it must be set to something, otherwise the path in your ycm_extra_conf.py that sets all of the androidflags wouldn't get followed. Based on the error message from libclang, it looks like it is being followed.
Have you tried reconstructing the problematic command line manually to see if it produces a crash?

I have to admit that I'm pretty baffled by the libclang output. For example, it includes things like:
-I/local/mnt/workspace/naseer/LA.BF64.1/ $ANDROID_BUILD_TOP/hardware/qcom/display/libgralloc

I don't understand why $ANDROID_BUILD_TOP is in there, as opposed to the expansion of that variable. You're explicitly calling os.getenv() which ought to expand it.
There are a few things you might try that would clean up (what are to me) some oddities in your extra config. First, use os.path.join() rather than string addition to construct paths. Second, I think you want -I/path/elements/ to be a single value rather than having -I be a separate flag from its associated path. I don't expect that these changes will fix the problem, but they'll certainly remove some noise from the system.

@abingham - I was just trying to follow the convention here - https://github.com/Valloric/ycmd/blob/master/examples/.ycm_extra_conf.py#L44-L52
I agree with you now that this is not emacs specific - but I still don't know how it works with vim. I will try changing the paths as you suggest. One issue I faced yesterday was that changing the ycm_extra_conf.py didn't take any effect on the current project - I'm not sure if there is a cached version somewhere that it reads from.

Using os.path.join seems to have resolved the clang crash - Thanks for the suggestion  :+1:
Now I'm hitting this error in some completions (subclasses) - again, this works fine in vim :(
Traceback (most recent call last):
  File "/local/mnt/workspace/naseer/installs/ycmd/third_party/bottle/bottle.py", line 861, in _handle
    return route.call(**args)
  File "/local/mnt/workspace/naseer/installs/ycmd/third_party/bottle/bottle.py", line 1734, in wrapper
    rv = callback(*a, **ka)
  File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/watchdog_plugin.py", line 100, in wrapper
    return callback( *args, **kwargs )
  File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/hmac_plugin.py", line 54, in wrapper
    body = callback( *args, **kwargs )
  File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/handlers.py", line 100, in GetCompletions
    completer.ComputeCandidates( request_data ),
  File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/completers/completer.py", line 158, in ComputeCandidates
    candidates = self._GetCandidatesFromSubclass( request_data )
  File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/completers/completer.py", line 173, in _GetCandidatesFromSubclass
    raw_completions = self.ComputeCandidatesInner( request_data )
  File "/local/mnt/workspace/naseer/installs/ycmd/ycmd/../ycmd/completers/cpp/clang_completer.py", line 101, in ComputeCandidatesInner
    raise RuntimeError( NO_COMPLETIONS_MESSAGE )

The above issue happens only with spacemacs, not with a clean emacs configuration, will debug further in spacemacs, I guess this bug can be considered closed except for showing the right error message.

OK, I'll close this and reference it in a new defect specifically focused on improved error messages. Thanks for working with me on this, and I hope we get everything resolved with spacemacs!

authors: abingham naseer

repo: abingham/emacs-ycmd


text:
doc: emacs-ycmd requires 127.0.0.1 to be in the NO_PROXY env variable

At work, emacs-ycmd did not work for me at all till today.  I would always see in the debug logs.
HTTP RESPONSE CONTENT

nil

After looking at https://github.com/abingham/emacs-ycmd/issues/404 , I added 127.0.0.1 to the NO_PROXY and no_proxy environment variables and was able to get emacs-ycmd to work. Please add this information regarding NO_PROXY and no_proxy variable setup to the documentation.
I did not face this issue with the YouCompleteMe vim plugin.
regards,
Venkat

emacs-ycmd could automatically set the no_proxy environment variable like YCM does.

I see. Thanks @micbou for the hint. Since we are getting this report from time to time I guess it would be a good idea to set the no proxe environment variable for the ycmd communication

See #438
The PR add the no_proxy variable to the envrionment to bypass proxies

authors: micbou ptrv vmandela


text:
chore: jxpy to 0.0.7

chore: Promote jxpy to version 0.0.7

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Don't expose GeoJsonMessage in the API

I've noticed that in fact, we're exposing the GeoJsonMessage in the LocationHistoryData :thinking: I have mixed feeling about this because that class is a part of our internal DTO that's sent through Ably between Publisher and Subscriber SDKs. And also that LocationHistoryData is meant to be used for debug/development purposes rather than for production use. But still, due to that, we're exposing something that's meant to be our internal implementation detail to the SDK users.
WDYT? Should we create another class that would only be used for that LocationHistoryData or should we leave the GeoJsonMessage exposed in our SDKs?
Originally posted by @KacperKluka in https://github.com/ably/ably-asset-tracking-android/issues/271#issuecomment-811089641
We should create a separate class that will hold the data for the LocationHistoryData.
┆Issue is synchronized with this Jira Task by Unito

The format of the content of messages needs to be public. Customers need to be able to consume messages via means other than Subscriber connections, eg webhooks, other integrations, history etc.
If we had a need to include additional data in LocationHistoryData for debug purposes, then that can be a privately declared class that extends or embeds GeoJsonMessage.

That sounds right but I think it doesn't mean that we need to expose that message classes in the code. If a customer needs to know the format of the messages he can either take a look at our Github repository or we can prepare some kind of a JSON Schema for the messages and put it in the README.
IMO there's no need to expose those internally used message classes in the SDKs because the SDK users won't be able to use them anyway since they're not used anywhere in our API.

I think we should discuss with Quintin. If someone receives a GeoJSONMessage in a webhook request body, for example, it would be useful if they could use a library to decode it. We have a similar thing already for other types in the Ably libary (eg Message.fromEncoded() or something like that).

We've decided that GeoJsonMessage should be exposed and used in the location history data.

authors: KacperKluka paddybyers

repo: ably/ably-asset-tracking-android


text:
RTL10b: Implement untilAttach for RealtimeChannel.history.

Fixes #234.

Beside a small comment, LGTM

Looks good other than small comment

authors: mattheworiordan ricardopereira tcard

repo: ably/ably-ios


text:
AMQP rule does not accept null for channel_filter

Ably AMQP rule does not accept null for channel_filter(it is a mandatory field) but when I set match everything/leave blank in the UI it stores a null in the state file.
resource "ably_rule_amqp" "rule_amqp" {
Must set a configuration value for the source.channel_filter attribute as the provider has marked it as required.

I can use a regular expression that matches everything, but I am not sure that will work as expected.

It seems the REST API we are calling to manage rules requires this field when it really shouldn't. Asking the web team for a fix and once that lands we can fix it here too.

So it seems that the API wants an empty string not a null. So you can just set the value to an empty string as a work around. I have a PR up that makes the field optional so a null will also work on the terraform side.

@Morganamilo Thank you!

authors: Morganamilo kandreasyan

repo: ably/terraform-provider-ably