Verbose output option when generating prefixes

Describe what you would like to achieve
Option for providing verbose output for debugging when generating prefixes
Describe why the current solution (if any) is not satisfactory
There seems to be a problem with stat.ripe.net at the moment which is causing all generated prefix lists to be empty. This obviously isn't a problem caused by BGPalerter, but it may have been easier to troubleshoot if there was a way to get more information on the data which is being returned from stat.ripe.net and what BGPalerter is doing when processing that data.
Provide an example
This is what I see currently, which doesn't really give much to go on:
~# bgpalerter generate -a 41000 -o prefixes.yml
Done!
~# cat prefixes.yml
{}

Ideally there would be something like a --verbose or --debug option which would help to see the details of what is happening behind the scenes and track down where the problem is.
Unfortunately as the connection to stat.ripe.net is over HTTPS, I couldn't even see the data in a packet capture.
Your information
Edward Dore, Freethought Internet Limited, AS41000

This affects the generation of new configurations but not the monitoring of already available configurations.

Hi @spheron1,
The auto-configuration already has a verbose output which shows you all the steps and all the prefixes detected.
Also, it reports any error occurred while downloading the data.
The problem here is that at the moment the API of RIPEstat is "working properly" but reporting an empty dataset (or with too old data). Essentially the API is reporting always that the provided AS is not announcing anything at the moment (which could be true in same cases). I honestly would not know what to do in this case.
I'm not aware of other APIs providing the same information of RIPEstat (otherwise we could do some redundancy).
Luckily RIPEstat failures of this scale are rare. I presume it will be fixed soon.
I contacted the RIPE NCC staff, I will keep you informed.
In the meanwhile let me know if you need any help with the manual configuration.

Hi @massimocandela,
As I said, I'm aware that the underlying cause of this particular issue is with RIPEstat and not BGPalerter, but if there was a way for the user to get more verbose data on what is happening behind the scenes then I could have been aware of that a lot sooner and not spent so much time trying to work out what I was doing wrong.
I don't believe this is limited to this particular case either. I think it would be generally useful to have verbose/debugging data available to show what was retrieved from RIPEstat to help track down any differences between what is expected and what is actually happening.
This could potentially be done via two levels - the first to show a summary of what has been retrieved and how it was processed and then a second which gives the actual raw response from RIPEstat.

In addition to writing which prefixes are detected (already available), I added:

A warning, as suggested in my first message, about the list of prefixes being empty.
The option -D to enable the debug mode. You will receive all http queries issued (urls).
The option -H to generate the prefixes with historical visibility data (prefixes announced in the last week).

I think this is a practical and effective solution.

That's great, thank you very much @massimocandela 👍

Btw, RIPEstat is working again.


Fixing device.py so that Travis doesn't fail and added test

In the current prod version of the code, Travis throws an error in device.py (#76). Oddly, the error wasn't there when the affected lines of code was first merged. This is a fix for that error so that Travis can build again. I've also added a test for the set_predefined_color-method.

@balloob created a new, clean, branch with minimum commits


"Page versions" menu only works properly once unless you refresh page

On page versions, if the page versions is opened, closed and opened again it doesn’t display the page versions anymore until the page is refreshed. Looks like a bug recreating the apos-modal-tabs. Is this an apostrophe bug or a site conflict? Easy enough to work around by refreshing or going back to live then back to edit.

This seems to work fine, closing


On BatchedDataLoader performance

Hi all,
I am trying to train a PyTorch model with a pretty big dataset (of the order of millions of samples, ~100 columns, including scalars and arrays) stored as Parquet files. After reading the docs it seems BatchedDataLoader should be the choice.
I have been having a look at the BatchedDataLoader class and despite reading parquet files in parallel with PyArrow, batches seem to be built on demand in an iterative way. This somehow does not leverage the processing power of GPUs and during training I don't observe GPU usage >20% and the GPU usage is very unstable.
I am afraid the GPU is idle waiting all those batches to be built. Would it be possible to build them in advance?

Batch building implementation in BatchedDataLoader should be fairly efficient. Are you sure the slowness comes from BatchedDataLoader? Could it be that the data is not supplied fast enough to the BatchedDataLoader? Did you try tweaking parameters you pass to make_batch_reader (specifically reader_pool_type and workers_count)?

Got it. Interesting. Indeed, multiplicity of columns is tricky since it is handled by these two loops, it might end up pretty slow.
Couple of ideas:

Add a pipelining - a thread + a queue: this way batch construction would be done in parallel with training. I think it's not a large undertaking and can be done externally to petastorm; alternatively, we can think of adding this as a built-in feature into BatchedDataLoader.
Your proposal of moving the batching into worker processes/threads might be doable. I am afraid it would be a bit trickier to implement. Also, a concern of having shuffling done at a per-worker basis would result in worse shuffling quality.

If you are interested, feel free to propose a PR - we can work together to get it into the petastorm codebase.

Could you please elaborate on 1?

In (1) I am referring to the following idea:

Implement a class that has the same interface as BatchedDataLoader
The is instantiated with an instance of a petastorm's BatchedDataLoader
In the constructor it instantiates a queue (bounded size) and a thread
On the thread, we continuously read batches from BatchedDataLoader and store results in the queue
__iter__ of the new class returns data from the queue.

This way, the batching will be done on the background thread. This way the main thread can drive GPU based training while CPU/GIL would be busy creating batches.

Thank you for your clarification. Yeah, I implemented this and it indeed improved GPU usage. I might submit a PR in the coming days.

I wonder if we should put this mechanism behind the current BatchedDataLoader implementation (optional with a switch).

I think it definitely makes sense!


Use Rust union types

For #1020
Replace some types with unions now that rustc supports them.
I also found sigevent.sigev_notify_thread_id, siginfo_t.__data and sigaction.sa_sigaction that I think should be unions, but I wasn't sure.

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

Also I had to ignore iffaddrs.ifa_ifu on Linux to pass CI

Unfortunately I believe this is a breaking change, which means we can't actually do this until we bump the crate version to 1.0.
cc @JohnTitor

I'm aware that it is a breaking change and that's not a problem for me to wait until a new major version for this to be merged.

:umbrella: The latest upstream changes (presumably #1975) made this pull request unmergeable. Please resolve the merge conflicts.

@kellda main is now intended for libc 1.0. Are you able to rebase this?

I'm unsure how to find out what's wrong with sigval on emscripten...

I'm unsure how to find out what's wrong with sigval on emscripten...

I also don't know. I'll mark this as review as a reminder that I need to take a look at this.
@rustbot review

Btw, I noted (when I originally opened this PR) that the following fields may also be wroth considering turning into unions:
* sigevent.sigev_notify_thread_id

* siginfo_t.{_pad/__data}

* sigaction.sa_sigaction

Feel free to submit another PR!

This needs another rebase, feel free to just leave emscripten disabled in build.rs as a FIXME if needed.
Regarding traits: don't add Hash/PartialEq/Eq for unions, or leave them but make the bodies unimplemented!("traits") if some other structs depend on them. We are likely going to drop these in 1.0 so we aren't doing any unsafe union field access.
For Debug, make the unions fmt.debug_struct("type_name").finish_non_exhaustive().
@rustbot author

These changes overall look good to me assuming the traits get figured out. I left comments with sources just to make sure I double checked everything here.
https://github.com/rust-lang/libc/pull/4176 landed so you can remove all debug implementations. If anything else complains about missing traits, just implement the body unimplemented!("traits") so we fix this up later.
Comment @rustbot ready when this is ready for another look.


ubuntu14.04 启动失败

报错信息：
ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/dj_recommend_type' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 94:30-89
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/dj_sub' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 84:19-67
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/event' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 97:18-65
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/fm_trash' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 100:21-71
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/follow' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 102:19-67
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/like' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 105:17-63
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/likelist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 107:21-71
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/logWeb' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 119:20-68
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/login' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 113:18-65
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/loginCellphone' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 110:28-84
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/login_refresh' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 116:58-113
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/lyric' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 122:18-65
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/musicUrl' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 125:22-72
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/mv' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 134:15-59
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/mv_first' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 128:21-71
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/mv_url' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 131:19-67
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/personal_fm' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 137:24-77
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/personalized' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 140:25-79
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/personalized_djprogram' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 143:35-99
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/personalized_mv' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 152:28-85
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/personalized_newsong' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 146:33-95
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/personalized_privatecontent' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 149:40-109
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/playlist_catlist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 162:29-87
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/playlist_detail' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 155:28-85
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/playlist_hot' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 160:25-79
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/playlist_tracks' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 158:28-85
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/program_recommend' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 165:30-89
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/recommend_dislike' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 174:30-89
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/recommend_resource' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 171:31-91
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/recommend_songs' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 168:28-85
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/resource_like' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 176:26-81
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/search' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 179:19-67
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/search_multimatch' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 182:30-89
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/search_suggest' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 185:27-83
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/simi_artists' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 200:24-78
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/simi_mv' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 194:20-69
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/simi_playlist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 188:26-81
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/simi_song' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 191:22-73
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/simi_user' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 197:22-73
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/song_detail' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 203:24-77
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_album' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 206:22-73
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_artists' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 209:24-77
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_list' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 211:21-71
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_mv' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 213:19-67
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_playlist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 216:25-79
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_playlist_highquality' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 219:37-103
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/top_songs' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 221:21-72
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/toplist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 223:20-69
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/toplist_artist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 225:27-83
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/toplist_detail' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 227:27-83
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_audio' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 233:23-75
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_cloud' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 236:23-75
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_cloud_search' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 239:30-89
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_detail' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 244:24-77
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_dj' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 246:20-69
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_event' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 242:23-75
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_followeds' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 248:27-83
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_follows' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 250:25-79
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_playlist' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 230:26-81
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_playrecord' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 254:24-81
 @ ./main.js
 @ multi babel-polyfill ./main.js

ERROR in ./server/api.js
Module not found: Error: Can't resolve '../NeteaseCloudMusicApi/router/user_subcount' in '/home/howie/Documents/programming/git/ieaseMusic/server'
 @ ./server/api.js 252:26-81
 @ ./main.js
 @ multi babel-polyfill ./main.js

npm ERR! Linux 4.4.0-96-generic
npm ERR! argv "/home/howie/Documents/programming/git/nvm/versions/node/v6.11.3/bin/node" "/home/howie/Documents/programming/git/nvm/versions/node/v6.11.3/bin/npm" "run" "build-main"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build-main: `cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config ./config/webpack.config.electron.js --progress --profile --colors`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-main script 'cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config ./config/webpack.config.electron.js --progress --profile --colors'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iease-music package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=production node -r babel-register ./node_modules/webpack/bin/webpack --config ./config/webpack.config.electron.js --progress --profile --colors
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iease-music
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iease-music
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/howie/Documents/programming/git/ieaseMusic/npm-debug.log

npm ERR! Linux 4.4.0-96-generic
npm ERR! argv "/home/howie/Documents/programming/git/nvm/versions/node/v6.11.3/bin/node" "/home/howie/Documents/programming/git/nvm/versions/node/v6.11.3/bin/npm" "run" "build"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: `rm -rf dist && npm run build-main && npm run build-renderer`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'rm -rf dist && npm run build-main && npm run build-renderer'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iease-music package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rm -rf dist && npm run build-main && npm run build-renderer
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iease-music
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iease-music
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/howie/Documents/programming/git/ieaseMusic/npm-debug.log

npm ERR! Linux 4.4.0-96-generic
npm ERR! argv "/home/howie/Documents/programming/git/nvm/versions/node/v6.11.3/bin/node" "/home/howie/Documents/programming/git/nvm/versions/node/v6.11.3/bin/npm" "run" "package-linux"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>package-linux: `npm run build && rm -rf release && build --linux --projectDir ./dist`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>package-linux script 'npm run build && rm -rf release && build --linux --projectDir ./dist'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iease-music package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build && rm -rf release && build --linux --projectDir ./dist
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iease-music
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iease-music
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/howie/Documents/programming/git/ieaseMusic/npm-debug.log

npm-debug.log

子模块缺失，然后就没问题了，等下更下到readme
git submodule init
git submodule update

打包好了 启动报这个错：
A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: Cannot read property 'setIcon' of undefined
    at Object.<anonymous> (/tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:222:121964)
    at a (/tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:1:256)
    at Object.<anonymous> (/tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:222:67043)
    at a (/tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:1:256)
    at /tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:1:616
    at Object.<anonymous> (/tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:1:628)
    at Object.<anonymous> (/tmp/.mount_92CwKB/usr/bin/resources/app.asar/main.js:408:3)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)

你把main.js 520 行的 app.dock.setIcon(${__dirname}/src/assets/dock.png); 注释看看，还有没啥不兼容的

注释掉后 我运行  npm run dev
能打开 但是根本点不动 就自动播放一首电子乐
托盘图标可以上一首 界面基本点不动 无反应

没有linux 😕 你打开dev tool 然后刷新截图给我看看

截哪部分给你看？  就是界面只能看不能点 是不是路径问题？

把network 界面还有控制台的都截图了 我来看看
On Thu, Sep 28, 2017 at 3:25 PM, howie.hu<EMAIL_ADDRESS>wrote:

截哪部分给你看？ 就是界面只能看不能点 是不是路径问题？
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trazyn/ieaseMusic/issues/8#issuecomment-332751563,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsVMtoriRlqzOw9HGwXdV9-ElKG5Vscks5sm0npgaJpZM4PmqhS
.

界面部分看起来是没报错的，控制台的打印也是ok的
界面上那几个小图标不能点击还有歌单也不能滚动么

我装个linux看看吧

好的 麻烦了  我是Ubuntu14.04

嗯知道了

同样这个问题 dev tool 能点击,其他界面点击无效, 点击以后鼠标变成拖动标志
electron 1.6.11 manjaro linux

嗯在装Ubuntu中

用刚装好的Ubuntu事了下，感觉字体有些奇怪啊

我感觉我是不是要加个功能给你们自己去改字体啊:doge:

可以加个功能改字体:smile:

再有个bug 当一首歌暂停一段时间 就没法继续播放～～

@howie6879 界面上基本都是横向滚动的，不是传统的竖着滚动。所以你姿势不对了😂 歌曲都是有时效性的，时间久了就过期了

那linux怎么滑。。加个横条么。。

鼠标直接滚动就行啊
On Fri, Sep 29, 2017 at 3:44 PM, howie.hu<EMAIL_ADDRESS>wrote:

那linux怎么滑。。加个横条么。。
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trazyn/ieaseMusic/issues/8#issuecomment-333055663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsVMhyMDSiSM-2IrVNNEK4L0NP3AgJaks5snJ_HgaJpZM4PmqhS
.

歌曲那个不能先缓存到本地么？

进度条后面的那个就是缓冲进度，很极端的情况下才会出现时效性问题导致播放失败，没显示的字体是emoji，linux下默认emoji很low，黑白还有很多就没有，换个兼容的字库就有了


Missing a feature that allows a generalized way of handling ml models for inputs/outputs

We did this, by using ml context, cost, and configs and allowing personal implementations


flexget: readd transmissionrpc

Motivation for this change
Required for using the transmission integration.
Backport to the appropriate channels would be nice, as to not break other setups.
Things done
Readded transmissionrpc

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

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

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

Thanks!


dev: bump cairo compiler

Bump cairo compiler
Description
Bumps the cairo compiler dependency to 2.4.1.
Description of the pull request changes and motivation.
Checklist

[ ] Linked to Github Issue
[x] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Copied the benchmark results since they can't get posted on the PR because it originates from another repo (i.e. my fork):
Benchmarking results
Benchmark for program factorial_2M
Open benchmarks

Command
Mean [s]
Min [s]
Max [s]
Relative

Cairo-vm (Rust, Cairo 1)
17.937 ± 0.076
17.810
18.106
37.00 ± 0.16

cairo-native (JIT MLIR ORC Engine)
1.403 ± 0.004
1.395
1.408
2.89 ± 0.01

cairo-native (AOT Native binary)
0.700 ± 0.002
0.697
0.703
1.44 ± 0.00

cairo-native (AOT Native binary with host CPU features, march=native)
0.485 ± 0.000
0.484
0.485
1.00

Benchmark for program fib_2M
Open benchmarks

Command
Mean [s]
Min [s]
Max [s]
Relative

Cairo-vm (Rust, Cairo 1)
17.473 ± 0.044
17.411
17.543
598.27 ± 2.43

cairo-native (JIT MLIR ORC Engine)
0.948 ± 0.010
0.932
0.965
32.46 ± 0.36

cairo-native (AOT Native binary)
0.041 ± 0.000
0.041
0.041
1.41 ± 0.01

cairo-native (AOT Native binary with host CPU features, march=native)
0.029 ± 0.000
0.029
0.029
1.00

Benchmark for program logistic_map
Open benchmarks

Command
Mean [s]
Min [s]
Max [s]
Relative

Cairo-vm (Rust, Cairo 1)
1.651 ± 0.013
1.635
1.676
23.64 ± 0.21

cairo-native (JIT MLIR ORC Engine)
0.998 ± 0.007
0.988
1.006
14.29 ± 0.12

cairo-native (AOT Native binary)
0.109 ± 0.000
0.109
0.110
1.57 ± 0.01

cairo-native (AOT Native binary with host CPU features, march=native)
0.070 ± 0.000
0.070
0.071
1.00

@edg-l I've been trying to implement the match_nullable_snapshot as well and I'm facing a weird behaviour, maybe you can see what I'm doing wrong (if not I will just push the compiler version updates):

in the build for snapshot_take, I print the pointer and the underlying value. I use the below code:

let res = entry
    .append_operation(llvm::load(
        context,
        entry.argument(0)?.into(),
        IntegerType::new(context, 8).into(),
        location,
        LoadStoreOptions::new().align(Some(IntegerAttribute::new(
            8,
            IntegerType::new(context, 64).into(),
        ))),
    ))
    .result(0)?
    .into();
metadata.get_mut::<DebugUtils>().unwrap().print_pointer(
    context,
    helper,
    entry,
    entry.argument(0)?.into(),
    location,
)?;
metadata
    .get_mut::<DebugUtils>()
    .unwrap()
    .print_i8(context, helper, entry, res, location)?;

This gives me the below when taking the snap:
[DEBUG] 0x000000010fca3440
[DEBUG] 2

In the build for match_nullable_snapshot which I added, I use the following to print the underlying pointer value:

let (inner_ty, inner_layout) =
    registry.build_type_with_layout(context, helper, registry, metadata, &info.ty)?;
let arg_u8 = entry
    .append_operation(llvm::load(
        context,
        entry.argument(0)?.into(),
        inner_ty,
        location,
        LoadStoreOptions::new().align(Some(IntegerAttribute::new(
            inner_layout.align() as i64,
            IntegerType::new(context, 64).into(),
        ))),
    ))
    .result(0)?
    .into();
metadata
    .get_mut::<DebugUtils>()
    .unwrap()
    .print_pointer(context, helper, entry, entry.argument(0)?.into(), location)?;
metadata
    .get_mut::<DebugUtils>()
    .unwrap()
    .print_i8(context, helper, entry, arg_u8, location)?;

In this case, I get
[DEBUG] 0x0000000142e17180
[DEBUG] 0

Let me know if this is enough info for you, if not I'll just bump the compiler updates and can push the code in another PR.

I havent looked at match_nullable_snapshot but if the argument is a nullable, then its a pointer, which maybe is a pointer to a info.ty itself and not the inner type of the enum?

Hello, and thanks for your PR.
I think your issue with match_nullable_snapshot may be caused by a refactor we did last month to improve the interface between C and Cairo when enums are involved. We still have to update the docs, but basically if the enum meets some criterion, then the enum is passed by reference (a stack-allocated pointer) instead of by value.
Since you're not showing the enum you're testing I'll assume it is indeed one that requires stack allocation, therefore you'd get a !llvm.ptr<!llvm.ptr> instead of a !llvm.ptr<the actual enum type> as an argument to the match_nullable_snapshot libfunc builder.
The fix is to:

Check if the enum is stack allocated.
If it is, then load a pointer.
Load the enum data from the previous pointer if loaded, or the argument otherwise.

Please let us know if this fixes the weird behavior you found.

Codecov Report
Attention: 18 lines in your changes are missing coverage. Please review.

Comparison is base (16b36c8) 76.19% compared to head (5928c21) 76.47%.

Files
Patch %
Lines

src/bin/cairo-native-compile.rs
0.00%
7 Missing :warning:

src/bin/cairo-native-dump.rs
0.00%
7 Missing :warning:

src/bin/cairo-native-run.rs
0.00%
2 Missing :warning:

src/libfuncs/nullable.rs
0.00%
1 Missing :warning:

src/utils.rs
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #412      +/-   ##
==========================================
+ Coverage   76.19%   76.47%   +0.28%
==========================================
  Files         108      108
  Lines       27598    27960     +362
==========================================
+ Hits        21028    21383     +355
- Misses       6570     6577       +7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hey @azteca1998, I had some time to check the code and I think the error comes from desnapping a Nullable. Not sure why but the * operator seems to just replace the value in the Nullable by 0. Below is a test I made that fails to pass:
#[test]
fn run_desnap_nullable() {
    let program = load_cairo!(
        use nullable::NullableTrait;
        use nullable::FromNullableResult;
        use nullable::match_nullable;

        fn run_test(x: u8) -> u8 {
            let a = @NullableTrait::new(x);
            let b = *a;
            let c = match match_nullable(b) {
                FromNullableResult::Null(_) => 99_u8,
                FromNullableResult::NotNull(value) => value.unbox()
            };
            c
        }
    );

    run_program_assert_output(&program, "run_test", &[4u8.into()], 4u8.into());
}

Fails with
thread 'libfuncs::nullable::test::run_desnap_nullable' panicked at 'assertion failed: `(left == right)`

Diff < left / right > :
 Uint8(
<    0,
>    4,
 )

This test compiles and passes using scarb.
Also compiled this very simple cairo code to check what a desnap operator gets compiled to in sierra:
fn test() {
    let c = @NullableTrait::new(1_u8);
    let d = *c;
    match match_nullable(d) {
        FromNullableResult::Null => 1_u8,
        FromNullableResult::NotNull(_) => 2_u8
    };
}

Correct me if I am wrong but the desnap compiles to a drop libfunc and then a rename libfunc. The issue with desnapping is that currently the drop implementation frees the pointer by calling the "free" function of the ReallocBindingsMeta (not sure what the function does, couldn't find info) which in turn I think causes me to have 0 as the underlying value of the pointer.
https://github.com/lambdaclass/cairo_native/blob/16b36c8fb609c5a16ca646b9784fac291994f80f/src/types.rs#L744
Let me know how you want to proceed, I think the drop libfunc needs to be updated for a Nullable as far as I understood.

I think I see the problem now. It has nothing to do with the enums.
Basically, a snapshot in the VM is just a pointer to a segment. This works because memory in the VM cannot be reassigned. However in cairo-native we don't have segments, therefore we need to copy the entire value. This is done in snapshot_take, where there's a section of the code in charge of that (the one that uses SnapshotClonesMeta). The problem is that there's no entry in SnapshotClonesMeta for nullables yet, only for arrays.
You could try to add something like this but in the nullable type builder. You'd need to implement the clone mechanism (example here) too, which should be just a realloc followed by an inline memcpy.
But I think that's enough work to justify a separate PR. Please let me know if you want to try it yourself, meanwhile I'll just open an issue.

Thanks for the detailed explanation! Will push compiler updates here. I don't think I will have time to work on the Nullable issue unfortunately :/ Thanks for your time!

Understood, I'll try to have a fix for your issue by today so that your tests pass.
Also, I think you may have forgotten to change the cairo version to 2.4.2 in the Makefile.


Fix mo generation

Sorry, I did a little mistake... This fixes it.

:ok:

The problem here is that I'm not sure if a translatable string is identified by context+original or by context+original+plural.
This PR adopts the second approach, that's compatible with what we had before all those PRs of mine :wink:

I guess the second approach is the right one, but I'm not sure. :+1:

I guess the second approach is the right one, but I'm not sure.

Me too. From the gettext docs we have:

only the singular of the original string takes part in the hash table lookup

We may think from that sentence that we can't have two strings with the same context+original, even if one is singular and the others have plurals... But since we don't use the hash table let's skip this (rare) argument :wink:


Merge 5.5.0 release branch iterations back into develop

Closes https://github.com/getferdi/ferdi/issues/536. Merging back iterations made on the release branch back to develop for future releases (see git branching model used as inspiration in https://github.com/getferdi/ferdi/pull/641#issuecomment-619375895).

I had to close otherwise AppVeyor wasn't building as the release branch had a pull request opened.


Add example notebook for braket setup and simple circuit

Amazon braket documentation is sometimes not very clear, and pytket-braket doesn't have as much documentation as some other pytket extensions. This notebook is based on a Confluence page I wrote for our team and on a notebook by Callum. I have used the notebook template and generation from pytket-quantinuum.

Could you advise what to do about the failed linting? I assume it comes from the long 'comments' which are turned into markdown cells by p2j. pytket-quantinuum seems to have the same formatting but appears to lint fine, but I couldn't see any particular options which were being used there

Could you advise what to do about the failed linting? I assume it comes from the long 'comments' which are turned into markdown cells by p2j. pytket-quantinuum seems to have the same formatting but appears to lint fine, but I couldn't see any particular options which were being used there

Yes it seems to be coming from the long lines. Can you wrap the lines at 80 characters. or does that break the p2j conversion? If necessary we can exclude the folder from the link check.

Yes, p2j treats each line break as a new markdown cell so it doesn't look the best. I assume in pytket-quantinuum they're simply excluded from the linting check

Yes, p2j treats each line break as a new markdown cell so it doesn't look the best. I assume in pytket-quantinuum they're simply excluded from the linting check

Actually they are not excluded there, and the python files do contain long lines (e.g. https://github.com/CQCL/pytket-quantinuum/blob/develop/examples/python/Quantinuum_circuit_submissions.py ), so I am not sure what's different here...

I think it'd be nice to have an example as some of the syntax for pytket-braket can be confusing. Should we finish this off?

I think it'd be nice to have an example as some of the syntax for pytket-braket can be confusing. Should we finish this off?

Sure, I think it's just some linting issues to fix?

Please rebase and retarget to main which is now the default branch.


No MQTT Events send when changing MLPs

Hello,
I was testing the MQTT event feature of the submodel repository. MQTT events for changed "Property" elements work just fine. However, changing values of "MultiLanguageProperty" elements (or adding/removing of languages) do not seem to lead to an MQTT event.
I used the following setup:

eclipsebasyx/aas-environment:2.0.0-SNAPSHOT
eclipsebasyx/aas-gui:v2-240515

Best regards
Matthias

Hi @de-ich ,
Thanks for raising this issue.
Would it be possible for you to share the configurations you used in this? like application.properties etc

Sure. I use the following configuration files (note that I needed to add 'txt' file ending due to upload limitations of Github):
docker-compose.yml.txt
aas-env.properties.txt
aas-registry.yml.txt
sm-registry.yml.txt
mosquitto.conf.txt

Some additional info:
There was a bug when updating SubmodelElements (including MLPs). This bug has just been fixed as part of this PR: #280
I think this fix is not in the latest version of the snapshot images. Therefore the BaSyx backend components do not support updating MLPs yet.

Update: Since updating an MLP currently uses PUT-Requests this issue is the same as #300.
Therefore please take a look at the latest comment there.

As this problem should have be resolved now in this PR #327 I will close this issue.


Update plugin-codesonar permissions

Description

Request to change permissions for plugin-codesonar: remove "atombrella", add "gt_dbechtold".
Note that "gt_dbechtold" (with underscore) is the Jenkins user name, "gt-dbechtold" (with hyphen) is the GitHub username.
https://github.com/jenkinsci/codesonar-plugin
Submitter checklist for adding or changing permissions

Always

[x] Add link to plugin/component Git repository in description above

When enabling automated releases (cd: true)

[ ] Add a link to the pull request, which enables continous delivery for your plugin or component.
Follow the documentation to ensure, your pull request is set up properly.

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[ ] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[ ] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[ ] All newly added users have logged in to Artifactory and Jira at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

cc @releasePraqma @MadsNielsen @buep @atombrella

@NotMyFault I approve of this. The plugin is getting a new maintiner!


Add a link to report security vuln

Not controversial. Discussed and approved in concept on last UG call. One formal community approval. Merging.


[beta] Do not probe for -Cembed-bitcode

This flag didn't make it to the beta branch of rustc, so remove the
probe here in Cargo. This is intended to be a very small patch to remove
the probe, since the real support is updated on master and will replace
this eventually anyway.

r? @Eh2406
(rust_highfive has picked a reviewer for you, use r? to override)

:warning: Warning :warning:

Pull requests are usually filed against the master branch for this repo, but this one is against rust-1.44.0. Please double check that you specified the right target!

@bors r+

:pushpin: Commit 96d5b73fbd55fab5d98fde5f5982eb046f8cc0d7 has been approved by Eh2406

For some context this was originally added (Apr 3)  in https://github.com/rust-lang/cargo/pull/8066 to accompany https://github.com/rust-lang/rust/pull/70458. Unfortuantely the rust-lang/rust PR did not land due to test issues, but it took quite some time for FCP to pass (closed Apr 19).
We then renamed the option in https://github.com/rust-lang/cargo/pull/8134 (Apr 19) to accompany a new rustc change at https://github.com/rust-lang/rust/pull/71323 which landed Apr 22. The beta cutoff was Apr 21, however, so although the Cargo changes rode the train into beta none of the rustc changes did.
The purpose of this PR is to "back out" the Cargo changes from the beta train. This isn't a straight revert to keep the patch minimal, but the impact of this is that all compilations won't start out with a failed probe to see whether rustc supports -Cbitcode-in-rlib.
Everything should be sorted out on nightly where rustc implements -Cembed-bitcode=no and we very recently renamed this back in Cargo. Once the Cargo submodule is updated on the master branch of rust-lang/rust we should be all set.

:hourglass: Testing commit 96d5b73fbd55fab5d98fde5f5982eb046f8cc0d7 with merge d97ae455a78f8a9179a65b5eb498925fd6a8a813...

:sunny: Test successful - checks-azure
Approved by: Eh2406
Pushing d97ae455a78f8a9179a65b5eb498925fd6a8a813 to rust-1.44.0...


hardware_alarm functions on wrong documentation page

Something isn't right with the documentation for the hardware_alarm functions. The timer.h page (https://raspberrypi.github.io/pico-sdk-doxygen/rp2__common_2hardware__timer_2include_2hardware_2timer_8h.html#a62098633d173c24c56c359df2e886ed2) documents only hardware_alarm_cancel() and hardware_alarm_set_target(), but none of the others. Meanwhile the hardware_timer page (https://raspberrypi.github.io/pico-sdk-doxygen/group__hardware__timer.html#gaa4c3c72008c100ca25f94b806f13f112) documents all the functions except hardware_alarm_cancel() and hardware_alarm_set_target().
I think that these two functions are incorrectly tagged somehow so that they appears in timer.h's documentation but not in `hardare_timer'.

will move them to the same group as the others

merged to master


Selenium driver

This pull request is for integrating the PHP library I developed into Mink, as a Driver.
I tested some basics with this project : https://github.com/alexandresalome/Behat-Sandbox
If you have some more complete test suite, I could be interested.

You should provide a driver test case, same as ZombieDriver or SahiDriver does: https://github.com/Behat/Mink/blob/master/tests/Behat/Mink/Driver/ZombieDriverTest.php
You should send PRs against develop branch

What's the difference between these PR and these: https://github.com/Behat/Mink/pull/84 ?

Ok. I've noticed that you have SeleniumDriverTest :-) My bad, sorry!
I've viewed your code and i like it. It's clean. But test suite fails in many places yet. Fix it and i'll happily merge your driver:
PHPUnit 3.5.15 by Sebastian Bergmann.

EFF...E....E.....F

Time: 04:21, Memory: 10.00Mb

There were 3 errors:

1) Tests\Behat\Mink\Driver\SeleniumDriverTest::testAriaRoles
Selenium\Exception: Unexpected response from Selenium server : Timed out after 5000ms

/Users/everzet/git/Behat/Mink/vendor/php-selenium/src/Selenium/Driver.php:80
/Users/everzet/git/Behat/Mink/vendor/php-selenium/src/Selenium/Browser.php:2057
/Users/everzet/git/Behat/Mink/src/Behat/Mink/Driver/SeleniumDriver.php:508
/Users/everzet/git/Behat/Mink/src/Behat/Mink/Session.php:259
/Users/everzet/git/Behat/Mink/tests/Behat/Mink/Driver/JavascriptDriverTest.php:15

2) Tests\Behat\Mink\Driver\SeleniumDriverTest::testCookie
Selenium\Exception: Unexpected response from Selenium server : ERROR: Cookie 'srvr_cookie' was not found

/Users/everzet/git/Behat/Mink/vendor/php-selenium/src/Selenium/Driver.php:90
/Users/everzet/git/Behat/Mink/vendor/php-selenium/src/Selenium/Browser.php:2151
/Users/everzet/git/Behat/Mink/src/Behat/Mink/Driver/SeleniumDriver.php:207
/Users/everzet/git/Behat/Mink/src/Behat/Mink/Session.php:182
/Users/everzet/git/Behat/Mink/tests/Behat/Mink/Driver/GeneralDriverTest.php:24

3) Tests\Behat\Mink\Driver\SeleniumDriverTest::testElementsTraversing
Selenium\Exception: Unexpected response from Selenium server : ERROR: Could not find element attribute: xpath=(//html//div/strong[2])[1]@class

/Users/everzet/git/Behat/Mink/vendor/php-selenium/src/Selenium/Driver.php:90
/Users/everzet/git/Behat/Mink/vendor/php-selenium/src/Selenium/Browser.php:1537
/Users/everzet/git/Behat/Mink/src/Behat/Mink/Driver/SeleniumDriver.php:283
/Users/everzet/git/Behat/Mink/src/Behat/Mink/Element/NodeElement.php:97
/Users/everzet/git/Behat/Mink/tests/Behat/Mink/Driver/GeneralDriverTest.php:157

--

There were 3 failures:

1) Tests\Behat\Mink\Driver\SeleniumDriverTest::testMouseEvents
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-right clicked
+double clicked

/Users/everzet/git/Behat/Mink/tests/Behat/Mink/Driver/JavascriptDriverTest.php:36

2) Tests\Behat\Mink\Driver\SeleniumDriverTest::testKeyboardEvents
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-key pressed:114 / 0
+key pressed:114 / 1

/Users/everzet/git/Behat/Mink/tests/Behat/Mink/Driver/JavascriptDriverTest.php:64

3) Tests\Behat\Mink\Driver\SeleniumDriverTest::testAdvancedForm
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-w
+off

/Users/everzet/git/Behat/Mink/tests/Behat/Mink/Driver/GeneralDriverTest.php:338

FAILURES!
Tests: 18, Assertions: 95, Failures: 3, Errors: 3.

It's still a work in progress. When I created the PR, there was no test, I
just worked on it. I'll finish it later.
Thanks for feedback !!

Most of the job done so far... The only part after all of this is the "Advanced form" test, which is probably the most important one. For the moment, I just disabled it.
Selenium has a different way for handling fields. For example, getValue() on a checkbox returns "on" or "off" (yeah... boark).
I tried to use some "Crawler" stuff, but I'm about to duplicate a lot of code. I was thinking about some base class for drivers using crawler for form handling (which is very different depending of the driver).
What's your opinion about it ?

At js_test and on some other pages too i'm getting waitForPageToLoad(60000) command in debugger and:
xx:xx:xx.xxx INFO - Command request: waitForPageToLoad[60000, ] on session xxxxxxxxxxxx

on the console. And Selenium actually waits 60 seconds. Even if page is already loaded. It's too bad, because in other tests Selenium is surely faster than Sahi :-(

As of form evaluation, we need just to be sure, that we're getting exact behavior across all drivers. And internally, it should be fastest possible way. For example, Sahi getValue() is not trivial too: https://github.com/Behat/Mink/blob/master/src/Behat/Mink/Driver/SahiDriver.php#L282. It using different functionality to retrieve proper value for concrete field type. I think you should do the same in SeleniumDriver.

What's status of this PR, @alexandresalome ?

I plan to work on it this week, sorry for delay

@alexandresalome awesome. Great to know you're working on it still :-)

+1 - very interested in this implementation.

I prepared a new PR, against develop branch : https://github.com/Behat/Mink/pull/108


[bug] indent characters arent shown with folds unless refreshed

hi!
ive noticed that with indent blankline, whenever using folds in nvim, the indent chars arent shown like this:

this is pretty annoying because visualizing indents is a great help yet it doesnt work when using folds
thanks!

weirdly enough, it seems to work for some folds, but not for others:

these images were taken in the same file
maybe it has to do with multiple fold levels?

Duplicate of #265
It's a limitation of Neovim.
It'll be handled a bit nicer in v3 hopefully, but it's not going to be perfect until there are changes upstream.

oh i see, thanks for the clarification!


Error when compiling

Running on Linux Mint 19.3 - kernel 5.4
I get an error on building using make dev. Any idea what might be causing this?
error[E0599]: no associated item named `MAX` found for type `i32` in the current scope
  --> /home/kilroy/.cargo/registry/src/github.com-1ecc6299db9ec823/mongodb-1.1.1/src/bson_util/mod.rs:71:55
   |
71 |         Some(duration) if duration.as_millis() > i32::MAX as u128 => {
   |                                                       ^^^ associated item not found in `i32`
   |
   = help: items from traits can only be used if the trait is in scope
   = note: the following trait is implemented but not in scope; perhaps add a `use` for it:
           `use rand::distributions::weighted::alias_method::Weight;`
help: you are looking for the module in `std`, not the primitive type
   |
71 |         Some(duration) if duration.as_millis() > std::i32::MAX as u128 => {
   |                                                  ^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `mongodb`.

To learn more, run the command again with --verbose.
Makefile:30: recipe for target 'dev' failed
make: *** [dev] Error 101

hey @kilroyjones
Which Rust version are you using? (rustc --version)
I just tried it with 1.47.0 on Ubuntu 20.04 with kernel 5.4 and it works fine :thinking:

Switched to nightly from 1.42 and it works. My bad. Thanks for the quick response.


Mapping too large for UniProt keyword 'dynein'

The definition for UniProt keyword: Dynein [KW-0243] is:
Large multimeric complex with ATPase activity, responsible for the movement of eukaryotic cilia and flagella (axonemal dynein) and for the intracellular retrograde motility of vesicles, organelles and chromosomes along microtubules (cytosolic dynein). Constitutes the side arms of the outer microtubule doublets in the ciliary axoneme and is responsible for the sliding. Also used for the dynein-associated microtubule-binding proteins (MTBs), e.g. dynactin
But the GO mapping for this includes Motor activity [GO:0003774]
which is wrong for all proteins that are not strictly part of the dynein complex,
(the 'also used for...' part of the UniProt definition).
As a result dynactin components DCTN1 and DCTN2 are wrongly annotated with motor activity...
Reported by: alain-gateau
Original Ticket: geneontology/annotation-issues/1295

@pgarmiri Do you still maintain the KW2GO file ? Can you remove the mapping
UniProtKB-KW:KW-0243 Dynein > GO:motor activity ; GO:0003774
Or should the proteins that are not strictly part of the dynein complex not have the KW? @sylvainpoux ?

Hi,
I think we should remove the mapping between KW-0243 and Motor activity [GO:0003774 and only leave the GO:0030286; C:dynein complex mapping
Thanks
Sylvain

Hi,
Yes, we still do this maintenance. I have removed the mapping between KW-0243 and Motor activity.
Thanks,
Penelope

Thanks !


Automatic dataset creation upon project creation

This is placeholder issue.
Ref:

https://github.com/fractal-analytics-platform/fractal-server/issues/674

As of fractal-server 1.3.12, project creation does not automatically create a dataset.
The current issue (adding fractal-web logic that automates dataset creation upon project creation) is superseded by https://github.com/fractal-analytics-platform/fractal-web/issues/244.


[Feature]: Add support for CrateDB

Module
New Module
Problem
Currently CrateDB is not supported
Solution
Add support for CrateDB is not supported
Benefit
Be able to do integration testing with CrateDB through testcontainers
Alternatives
-none-
Would you like to help contributing this feature?
Yes

Hi @matriv, I see the PR was already created. So, there is no need for an issue. Also, next time please consider open a discussion first.

@eddumelendez Thank you!

Also, next time please consider open a discussion first.

Apologies, thought its was straightforward since I had a basic PR ready, and it's an addition of a new module.


Compact pretty formatter

Especially for representing GeoJSON, the current pretty formatter is not suited ideally. In GeoJSON, 2-dimensional points are represented as arrays of length 2. In the JS world, GeoJSON is often formatted with libraries like json-stringify-pretty-compact, which have a smart logic of keeping short arrays/objects in a single line. This leads make the output nice and easy to work with:

Compact pretty formatter
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[0, 0], [0, 1], [1, 0], [1, 1], [0, 0]]]
      }
    },
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[0, 0.5], [0, 1.5], [1, 0.5], [1, 1.5], [0, 0.5]]]
      }
    },
    {
      "type": "Feature",
      "properties": {"operation": "intersection"},
      "geometry": {
        "type": "MultiPolygon",
        "coordinates": [
          [[[0, 0.5], [0.25, 0.75], [0, 1], [0, 0.5]]],
          [[[0.75, 0.75], [1, 0.5], [1, 1], [0.75, 0.75]]]
        ]
      }
    },
    {
      "type": "Feature",
      "properties": {"operation": "union"},
      "geometry": {
        "type": "MultiPolygon",
        "coordinates": [
          [
            [
              [0, 0],
              [0.5, 0.5],
              [0.25, 0.75],
              [0.5, 1],
              [0, 1.5],
              [0, 1],
              [0, 0.5],
              [0, 0]
            ]
          ],
          [
            [
              [0.5, 0.5],
              [1, 0],
              [1, 0.5],
              [1, 1],
              [1, 1.5],
              [0.5, 1],
              [0.75, 0.75],
              [0.5, 0.5]
            ]
          ]
        ]
      }
    }
  ]
}

The same GeoJSON formatted with a standard pretty formatter becomes very spacious due to the large number of length 2 arrays:

Standard pretty formatter
{
  "features": [
    {
      "geometry": {
        "coordinates": [
          [
            [
              0.0,
              0.0
            ],
            [
              0.0,
              1.0
            ],
            [
              1.0,
              0.0
            ],
            [
              1.0,
              1.0
            ],
            [
              0.0,
              0.0
            ]
          ]
        ],
        "type": "Polygon"
      },
      "properties": {},
      "type": "Feature"
    },
    {
      "geometry": {
        "coordinates": [
          [
            [
              0.0,
              0.5
            ],
            [
              0.0,
              1.5
            ],
            [
              1.0,
              0.5
            ],
            [
              1.0,
              1.5
            ],
            [
              0.0,
              0.5
            ]
          ]
        ],
        "type": "Polygon"
      },
      "properties": {},
      "type": "Feature"
    },
    {
      "geometry": {
        "coordinates": [
          [
            [
              [
                0.0,
                0.5
              ],
              [
                0.25,
                0.75
              ],
              [
                0.0,
                1.0
              ],
              [
                0.0,
                0.5
              ]
            ]
          ],
          [
            [
              [
                0.75,
                0.75
              ],
              [
                1.0,
                0.5
              ],
              [
                1.0,
                1.0
              ],
              [
                0.75,
                0.75
              ]
            ]
          ]
        ],
        "type": "MultiPolygon"
      },
      "properties": {
        "operation": "intersection"
      },
      "type": "Feature"
    },
    {
      "geometry": {
        "coordinates": [
          [
            [
              [
                0.0,
                0.0
              ],
              [
                0.5,
                0.5
              ],
              [
                0.25,
                0.75
              ],
              [
                0.5,
                1.0
              ],
              [
                0.0,
                1.5
              ],
              [
                0.0,
                1.0
              ],
              [
                0.0,
                0.5
              ],
              [
                0.0,
                0.0
              ]
            ]
          ],
          [
            [
              [
                0.5,
                0.5
              ],
              [
                1.0,
                0.0
              ],
              [
                1.0,
                0.5
              ],
              [
                1.0,
                1.0
              ],
              [
                1.0,
                1.5
              ],
              [
                0.5,
                1.0
              ],
              [
                0.75,
                0.75
              ],
              [
                0.5,
                0.5
              ]
            ]
          ]
        ],
        "type": "MultiPolygon"
      },
      "properties": {
        "operation": "union"
      },
      "type": "Feature"
    }
  ],
  "type": "FeatureCollection"
}

This makes handling the files inconvenient, and leads to ~4 times larger file sizes, which becomes an issue especially when dealing with larger GeoJSON data.

I would prefer not to build that directly into serde_json, but serde_json::Serializer accepts external formatters and it would be reasonable for a compact pretty formatter for serde_json to be developed in a separate crate. The compact pretty example output you pasted would be possible to implement that way.


New term request induction and suppression by symbiont of host MAPK signaling pathway

suppression of host MAPK signaling pathway
induction by symbiont of host MAPK signaling pathway
also, change label of 'pertubation of host innate immune response MAPK kinase signaling' to just  'pertubation of host MAPK kinase signaling'

Suppression of host MAPK activity by Eukaryotic Pathogen:

Antigen C10 (AgC10) from Trypanosoma cruzi: AgC10 is a GPI-anchored mucin from Trypanosoma cruzi that inhibits TNF secretion by activated macrophages [PMID:9366425]. AgC10 inhibits TNF, interleukin-10, and cyclooxygenase-2 synthesis by macrophages that have previously been activated with LPS and interferon-gamma. AgC10 destabilizes TNF and COX‐2 mRNA by inhibiting activation of p38 mitogen‐activated protein kinase and its substrate MAPK‐activated protein kinase‐2 [PMID:15162440].
Tc52 from Trypanosoma cruzi: Tc52 is a 445 residue protein that targets the host p38 and extracellular-regulated kinase (ERK) in T cells which leads to increased secretion of host interleukin-10 and inhibition of IL-12 secretion. The protein is probably proteolyzed within the host cell into a 28 kDa cleavage fragment that mediates immunosignaling [PMID:12709028].

Suppression of host MAPK activity by Bacterial Pathogen:

Lethal factor from Bacillus anthracis: Lethal factor is a protease active against nearly all forms of mitogen-activated protein kinase kinase (MAPKK), destruction of which prevents the phosphorylation of a wide variety of regulatory molecules including p38, extracellular-regulated kinase (ERK), and Jun N-terminal kinase (JNK). This prevents the downstream transcriptional activation in the immune cells that respond to bacterial invasion, limiting their ability to defend the host. Lethal factor is a Zn2+-dependent metalloprotease. It requires protective antigen for entry into a mammalian cell via one of two receptors. Lethal factor is active against nearly all forms of mitogen-activated protein kinase kinase (MAPKK), destruction of which prevents the phosphorylation of a wide variety of regulatory molecules including p38, extracellular-regulated kinase (ERK), and Jun N-terminal kinase (JNK). This prevents the appropriate transcriptional activation in the immune cells that respond to bacterial invasion, limiting their ability to defend the host [PMID:26978402].
Yersinia outer protein J (YopJ) from Yersinia pseudotuberculosis: YopJ is a T3SS effector that inhibits activation of host MAPK (ERK1/2, JNK, p38)  and NFkappaB via acetylation of Ser and Thr residues on MAPKK and IKKbeta. Acetylation prevents their activation by upstream kinases [PMID:16728640] and [PMID:17116858]. YopJ is activated by  host inositol hexakisphosphate [PMID:20430892]. YopJ inhibits the response of host of macrophages to infection by diminishing the MAPK/ERK-mediated biosynthesis of prostaglandin E2 (PGE2) by host cyclooxygenase-2 (COX-2) [PMID:34319170].

Suppression of host MAPK activity by Viral Pathogen:

Unique short 28 (US28) from Human herpesvirus 5 (HHV-6; human cytomegalovirus): US28, a cell surface GPCR resembling a host chemokine receptor, attenuates MAPK and NF-kappaB signaling to maintain a latent (hidden) infection in monocytes, even in the absence of chemokine binding [PMID:29208743]. US28 is expressed in both latent and lytic infection and is required for latent infection of hematopoietic progenitor cells [PMID:26719258]. The structure of HCMV US28 in combination with fractalkine, showing how it recognizes host chemokines has been solved [PMID:25745166].
B1 kinase (VPK1) from Vaccinia virus: VPK1 modulates cellular responses via host JUN by two different mechanisms, either by direct phosphorylation or by modulation of upstream JIP1-MAPK complexes [PMID:16840345].
M2 from Vaccinia virus: The M2L protein interferes with the phosphorylation of host ERK2 (MAP kinase) and the subsequent activation of an NFkappaB response.  Mutant viruses lacking M2 activate NFkappaB more readily during infection [PMID:19738427].

Enhancement/Activation of host MAPK activity by Eukaryotic Pathogen:

GRA24 from Toxoplasma gondii: GRA24 is a dense granule protein released into the host cytoplasm that trafficks to the host nucleus and targets host p38alpha which leads to an unusually persistent autophosphorylation and activation of the host kinase in both humans and mice. This results in the upregulation of multiple proinflammatory cytokines including IL-12p40 and  MCP-1/CCL2 [PMID:24043761].

Enhancement/Activation of host MAPK activity by Bacterial Pathogen:


add Yuji to organization

[x] create @noaa.gov GitHub account
[ ] add to noaa-ocs-modeling

following up with<EMAIL_ADDRESS>

Yuji has now made a GitHub account @yujifunakoshiNOAA


No JSON object could be decoded

Expected Behavior
Bot Should start, was working perfectly today.
Actual Behavior
[2016-08-21 10:23:18] [Plugins] Loaded plugin "evolver".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "socket".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "recycle_items".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "collect_rewards".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "catch_pokemon".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "spin_pokestop".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "transfer_pokemon".
[2016-08-21 10:23:19] [Plugins] Loaded plugin "egg_incubator".
[2016-08-21 10:23:19] [x] PokemonGO Bot v1.0
[2016-08-21 10:23:19] [x] Configuration initialized
[2016-08-21 10:23:19] [Socket] Starting socket server...T
raceback (most recent call last):
File "C:\Users\root\Desktop\OpenPoGoBot\pokecli.py", line 88, in
main()
File "C:\Users\root\Desktop\OpenPoGoBot\pokecli.py", line 77, in main
bot.start()
File "C:\Users\root\Desktop\OpenPoGoBot\pokemongo_bot\bot.py", line 59, in st
rt
self._setup_api()
File "C:\Users\root\Desktop\OpenPoGoBot\pokemongo_bot\bot.py", line 89, in s
tup_api
self.set_starting_position()
File "C:\Users\root\Desktop\OpenPoGoBot\pokemongo_bot\bot.py", line 175, in _
et_starting_position
location_json = json.load(last_location_file)
File "C:\Python27\lib\json_init.py", line 291, in load
**kw)
File "C:\Python27\lib\json_init.py", line 339, in loads
return _default_decoder.decode(s)
File "C:\Python27\lib\json\decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Python27\lib\json\decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
Steps to Reproduce
Bot was working fine yesterday, went to go start it today and have this error now after changing nothing.
Other Information
OS: WIN7
Git Commit:

Just have to remove the Filed in Data Labeled Last-Location.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter opensmartcity for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.opensmartcity
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E019] Invalid repository URL in package.json: https://github.com/iobroker/ioBroker.opensmartcity.git. Expected: git@github.com:ioBroker/ioBroker.opensmartcity.git or https://github.com/ioBroker/ioBroker.opensmartcity.git
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 3.0.4 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
[ ] :heavy_exclamation_mark: [E117] Licenses in package.json and in io-package.json are different
[ ] :heavy_exclamation_mark: [E182] Please remove "common.license" from io-package.json as "common.licenseInformation" is declared.
[ ] :heavy_exclamation_mark: [E183] "common.licenseInformation.license" is missing
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/ioBroker/ioBroker.opensmartcity", press the settings button beside the about title and add some topics.

WARNINGS:

[ ] :eyes: [W028] Minimum node.js version 18 recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.
[ ] :eyes: [W105] Missing mandatory translation into de of "common.titleLang" in io-package.json.
[ ] :eyes: [W105] Missing suggested translation into ru,pt,nl,fr,it,es,pl,uk,zh-cn of "common.titleLang" in io-package.json.
[ ] :eyes: [W162] js-controller 5 listed as dependency but 5.0.19 is recommended. Please consider updating dependency at io-package.json.
[ ] :eyes: [W173] Potential sensitive data "password" not listed at "protectedNative" in io-package.json
[ ] :eyes: [W174] Potential sensitive data "password" not listed at "encryptedNative" in io-package.json
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W523] "package-lock.json" not found in repo! Please remove from .gitignore!

SUGGESTIONS:

[ ] :pushpin: [S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Wed, 11 Sep 2024 04:25:14 GMT

Issue outdated due to RECREATE request. Follow up issue #35 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Replace check_ws with subcription to websocket state

https://github.com/uilibs/uiprotect/commit/d7083ab8ced2dc3cc65dcaf6ea2dd8c869e70a96 removed check_ws, migrating the functionality to a websocket state subscription.
This PR adds the subscription, a callback to update self._websocket_state upon any state changes and replaces check_ws with self._websocket_state.
Continuation of discussions in PR #164

If the websocket is already connected by the time the event listener starts its internal state would be stuck on disconnected until the websocket disconnects and a reconnection is triggered?
I also don't think _check_websocket_and_reconnect needs to be run every 60s anymore because we can get a callback when the web socket disconnects


Update 6.0 and 7.0 MSFT-to-source-build baselines

These have diverged and are causing yellow builds in CI and should be updated.

These were updated with https://github.com/dotnet/installer/pull/15561 and https://github.com/dotnet/installer/pull/15560


TP2000-1077  Add review tabs to workbasket detail view

TP2000-1077  Add review tabs to workbasket detail view
Why
The workbasket summary review tabs that were introduced in #1056 should also be incorporated into the workbasket detail view.
What

Modifies review tab view routes to capture a workbasket primary key as a URL param
Adds workbasket primary key kwarg to review view calls
Updates tests

Codecov Report
Attention: 31 lines in your changes are missing coverage. Please review.

Comparison is base (6d6fd80) 92.79% compared to head (dca8ea2) 92.78%.
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1071      +/-   ##
==========================================
- Coverage   92.79%   92.78%   -0.02%
==========================================
  Files         460      460
  Lines       34258    34410     +152
  Branches     2616     2627      +11
==========================================
+ Hits        31790    31926     +136
- Misses       1970     1980      +10
- Partials      498      504       +6

Files
Coverage Δ

commodities/tests/test_views.py
100.00% <ø> (ø)

commodities/urls.py
100.00% <ø> (ø)

commodities/views.py
99.09% <100.00%> (+0.02%)
:arrow_up:

common/models/tracked_qs.py
94.05% <100.00%> (+0.12%)
:arrow_up:

common/models/trackedmodel.py
94.32% <ø> (ø)

measures/views.py
95.49% <100.00%> (+<0.01%)
:arrow_up:

workbaskets/tests/test_views.py
96.37% <100.00%> (+0.25%)
:arrow_up:

workbaskets/urls.py
100.00% <ø> (ø)

workbaskets/views/ui.py
85.71% <68.36%> (-0.69%)
:arrow_down:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Use uwsgi between Apache and Keystone

This switches from using http to uwsgi between Apache and Keystone.
If the uwsgi port setting is used, then mod_proxy_uwsgi will be used.
Otherwise if the file socket setting is used, then the uwsgi module will be used.
Both Ubuntu and Redhat will be able to use the port setting, but
only Ubuntu can use the file socket setting. The file socket was
previously broken but now will work on Ubuntu with this change.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

LGTM

ok to test

Since redhat can't use the file socket setting, I'm wondering if we should just remove the option entirely here. That way we can keep this consistent (using port) across both rhel and ubuntu


What about a "chibi" option?

Allow her to take the form of chibi and this then gives her the freedom to bounce around the screen however she likes. :D

look up shimeji monika
https://www.deviantart.com/childish-n/art/DDLC-Shimeji-Pack-718209813


Implementation of 'struct' for shaders

This huge PR enables the 'struct' keyword and its usage in the shaders. Target to close https://github.com/godotengine/godot-proposals/issues/301
Implemented and worked:

nested struct instances

struct A {
 vec3 color;
};
struct B {
 A a;
 int b;
};

struct constructors

B b = B(A(vec3(1.0, 0.0, 1.0)), 1);

struct arrays

	A test[] = {A(vec3(1, 1, 1))};
	ALBEDO = test[0].color;

struct constant instances (at global scope too)
const A test = A(vec3(1.0));
struct as functions parameters and return type

A test(A a, in B b)
{
	A t;
	t.color = vec3(1, 1, 0) + a.color / b.a.color * float(b.b);
	return t;
}

correct intellisense support (demo screenshot)

Not implemented:

global struct instances like:

struct L {
//...
} instance1, instance2; // <- these instances

I noticed @reduz don't want such global values because they may confuse other users.

After a brief reading of the code, it looks good. GLSL 100 supports structs, so it should be fine on mobile, web, and desktop.
Before accepting, I am going to build it myself and see if I can spot any issues.

GLSL 100 supports structs, so it should be fine on mobile, web, and desktop.

Does this mean GLES2 also can have structs? If so, the PR needs to be updated.

Yes GLES2 supports structs! https://www.khronos.org/files/opengles_shading_language.pdf

Ok, I've re-enabled it.

I've updated this PR to latest master + cut off GLES3 code -> seems worked well

Code of this shader (for debug purposes):
shader_type canvas_item;

// Inspired by:
//  http://cmdrkitten.tumblr.com/post/172173936860

const float Pi = 3.14159265359;

struct Gear
{
    float t;			// Time
    float gearR;		// Gear radius
    float teethH;		// Teeth height
    float teethR;		// Teeth "roundness"
    float teethCount;	// Teeth count
    float diskR;		// Inner or outer border radius
    vec3 color;			// Color
};

float GearFunction(vec2 uv, Gear g)
{
    float r = length(uv);
    float a = atan(uv.y, uv.x);

    // Gear polar function:
    //  A sine squashed by a logistic function gives a convincing
    //  gear shape!
    float p = g.gearR-0.5*g.teethH +
              g.teethH/(1.0+exp(g.teethR*sin(g.t + g.teethCount*a)));

    float gear = r - p;
    float disk = r - g.diskR;

    return g.gearR > g.diskR ? max(-disk, gear) : max(disk, -gear);
}

float GearDe(vec2 uv, Gear g)
{
    // IQ's f/|Grad(f)| distance estimator:
    float f = GearFunction(uv, g);
    vec2 eps = vec2(0.0001, 0);
    vec2 grad = vec2(
        GearFunction(uv + eps.xy, g) - GearFunction(uv - eps.xy, g),
        GearFunction(uv + eps.yx, g) - GearFunction(uv - eps.yx, g)) / (2.0*eps.x);

    return (f)/length(grad);
}

float GearShadow(vec2 uv, Gear g)
{
    float r = length(uv+vec2(0.1));
    float de = r - g.diskR + 0.0*(g.diskR - g.gearR);
    float eps = 0.4*g.diskR;
    return smoothstep(eps, 0., abs(de));
}

void DrawGear(inout vec3 color, vec2 uv, Gear g, float eps)
{
	float d = smoothstep(eps, -eps, GearDe(uv, g));
    float s = 1.0 - 0.7*GearShadow(uv, g);
    color = mix(s*color, g.color, d);
}

void fragment()
{
    float t = 0.5*TIME;
    vec2 uv = 2.0*UV.xy - 1.0;
    float eps = 2.0/512.0;

    // Scene parameters;
	vec3 base = vec3(0.95, 0.7, 0.2);
    const float count = 8.0;

    Gear outer = Gear(0.0, 0.8, 0.08, 4.0, 32.0, 0.9, base);
    Gear inner = Gear(0.0, 0.4, 0.08, 4.0, 16.0, 0.3, base);

    // Draw inner gears back to front:
    vec3 color = vec3(0.0);
    for(float i=0.0; i<count; i++)
    {
        t += 2.0*Pi/count;
 	    inner.t = 16.0*t;
        inner.color = base*(0.35 + 0.6*i/(count-1.0));
        DrawGear(color, uv+0.4*vec2(cos(t),sin(t)), inner, eps);
    }

    // Draw outer gear:
    DrawGear(color, uv, outer, eps);

    COLOR = vec4(color,1.0);
}

K. Lets rock!, structs are mostly ready, I only need to add a support for members array like
struct A {
 float test[5];
}

(it's not so easy as somebody may think)

fragment shader is showing inverted

@IuryBorges1993 What do you mean?

that when they have a shader of a shadertoy fragment, it stays upside down.

@IuryBorges1993 Please upload a minimal reproduction project to make this easier to troubleshoot :slightly_smiling_face:

@Calinou https://github.com/IuryBorges1993/raytrace/tree/master/raytrace
Every shadertoy plotted shader is upside down.

@Chaosus https://www.shadertoy.com/view/XsSSWW

Yeah, for some reason the picture is inverted:

I doubt however that it's related to struct, probably some error in shader code or some coordinate should be negated in order to prevent this behavior in Godot.

@IuryBorges1993 just write uv.y = -uv.y; after uv declaration in your code

Yeah, I remember - in Godot default UV coordinates for canvas_item are different than in the ShaderToy:

@Calinou thank you

@Calinou thank you

@Calinou thank you

maybe @Chaosus? :S

Will there be support for structs as uniforms?
Mainly asking since my shaders currently look like this:

@3top1a Don't use closed pull requests or issues to propose the ideas, use a proposal repository instead.


Istioctl not generate pod securityContext

Bug description
In a new, clean deployment of Istio 1.6.9 on Kubernetes 1.17.11. Istioctl is not respecting the SecurityPolicy field for istio-ingressgateway.
Below is a snippet from the overlay file
    ingressGateways:
    - name: istio-ingressgateway
      enabled: true
      k8s:
        securityContext:
          runAsUser: 1000
          runAsGroup: 1000
          fsGroup: 1000

This securityContext field is not being set in the pod spec for the generated istio-ingressgateway deployment manifest.
The runAsUser and runAsGroup needs to be set in order to ensure non-root policy enforcement by our PSPs so the pod can start.
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
istioctl version --remote
client version: 1.6.9
control plane version: 1.6.9
data plane version: none

How was Istio installed?
istioctl with overlay file
Environment where bug was observed (cloud vendor, OS, etc)
AWS

Istio 1.6.9 doesn't contains that feature, it was merged 15 day ago in https://github.com/istio/istio/pull/27539
please try istio 1.6.12.

This worked thank you.


Add AddBlankField to embed + Allow empty name/values.

Updated Field builder, to allow for "Empty" fields and values.
If you send "_ _" via the API, it will properly display as a blank field. I have tested this locally, and are currently utilizing it in production.
As well,
I Updated the Value setting to use String.IsNullOrWhiteSpace instead of String.IsNullOrEmpty, because passing a string containing nothing but spaces through the API will cause errors as well. However, "_ _" works perfectly.

It's not in our best interest to support this in the library; it relies on a behaviour which could easily change in the near future without warning. If you need this, it would be best to make an extension method.


Add a troubleshooting entry for no depth related to camera connections

From this issue:

So the depth stream not working turned out to be a loose flex cable on the right camera @itsderek23. I have had it slightly pop up a few times now.

I've had a similar issue once with the RPi Compute.

Add of the BW1097 board that show the issue, the code error, and the fix.

Here’s a photo of this:

FFC has been pushed down by a finger when holding the board, which then causes the FFC connector to partially ‘pop out’ and lose electrical/MIPI connection.


search dashboards

we should measure and test these things over a two week period
works search:

[x] are people moving from results to works? ie what's the click through rate?
[x] how does number of results affect click through rate?

image search:

https://reporting.wellcomecollection.org/s/search/app/kibana#/dashboard/c29b1c60-b6e6-11ea-a4b6-c58cbed87118?_g=(filters%3A!()%2CrefreshInterval%3A(pause%3A!t%2Cvalue%3A0)%2Ctime%3A(from%3Anow-90d%2Cto%3Anow))

some weird behaviour, maybe something going wrong with tracking?

querytypes (eg phraserbeam) are being measured on image search results, though I don't think we are using phraserbeam etc here
lots of unspecifieds in data.source, and less image interaction than i'd expect. maybe related, maybe just me being too hopeful about people using image search


how to reproduce zero data result?

as title.
there is a bug:
https://github.com/yhhhli/BRECQ/blob/da93abc4f7e3ef437b356a2df8a5ecd8c326556e/main_imagenet.py#L173
args.batchsize should be args.workers

Thanks,

question not answered, how can i reproduce zero data result?
--num_samples 0 , will triger an error

Do you mean the ZeroQ dataset?
I use the code from https://github.com/amirgholami/ZeroQ,
you can use that code to generate 1024 synthesized images

in your paper, there are results of BRECQ without training data:
https://mmbiz.qpic.cn/mmbiz_png/n3Mr5TfFd0eXzicXVUfiau7CKNQrWiaJpibsjrXPVOXZqbsHsy2x8c4XKYFgo9eY1d3TqhffkrA9CXibA9mkysvQ0xw/640?wx_fmt=png&tp=webp&wxfrom=5&wx_lazy=1&wx_co=1

As I said, I use ZeroQ to generate 1024 synthesized images and then use them to perform BRECQ. You can find it in Section B.2

oh, i see. thank you!


Authentication erediensten mandatarissen

This PR should enable the storing of delta files for worship mandates, protected by an API that needs authentication with account and secret key.

@benjay10 the dumpfiles were not written to the correct graph. Added in the config. Merging


Fix issues with QLF_K6N10 cells_sim.v and dsp_sim.v

This PR has fixes for issues seen while simulating designs with the QLF_K6N10 device.
The major changes are:

add specify blocks
add missing signals in dsp blocks to avoid warnings
add modules LUT_K, fpga_interconnect
add explicit wire type declarations for inputs

@mkurc-ant could someone review this PR and merge?

@mkurc-ant I will discuss these changes and update.

@mkurc-ant I have done the following changes:

Reverted the cells_sim to original version
Created primitives_sim.v file with post-layout macros and respective specify blocks
Made changes that you specified in the dsp_sim.v file

@rakeshm75 Alright, Looks good. Could you please rebase it on top of the main branch? I see that there are conflicts.

@mkurc-ant The CI issues are resolved, now you can merge.


Parent attribute does NOT create a two way link.

For example
$stateProvider
    .state('base', {}  /*attributes here*/ )
    .state('child1', { parent: base /*more attributes*/ }
    .state('child2', { parent: base /*more attributes*/ }

Then, in the template file for child1 I can put $log.info($state.get('^'));, and get the parent appropriately, but $log.info($state.get('^.child2')) is return unresolved. All children are linked to the parent through the parent attribute. But it seems this is not a bidirectional link.
Here's a plunkr: http://plnkr.co/edit/5kaTpgYxrLsl3wV8e5KA

In fact, just ui-sref the child's name works, without any prefix. This doesn't seem correct. Shouldn't nesting help to avoid state namespace collisions as well as offer the benefits of nesting?

Anything every happen with this?

You cannot use '^.child2 as it isn't the 'dot notation' name
It is explained in the docs which refers to issue #368 where the problem is explained.
in brief, using the parent property does not modify the actual state name and if you had 2 parents both containing a child called child2, you would have to use the 'dot notation' for the state names otherwise it would not work at all.


tostring instruction fails on complex examples

Current implementation of tostring seems correct
https://github.com/tenderlove/tenderjit/blob/428c6383297d16bf90822c64a4d4a7846e374433/lib/tenderjit/iseq_compiler.rb#L1156-L1166
However the following test fails
    def complex_tostring
      "#{1234}#{5678}"
    end

    def test_complex_tostring
      meth = method(:complex_tostring)

      assert_has_insn meth, insn: :tostring

      jit.compile(meth)
      jit.enable!
      v = meth.call
      jit.disable!

      assert_equal 1, jit.compiled_methods
      assert_equal 0, jit.exits
      assert_equal "12345678", v
    end

with
--- expected
+++ actual
@@ -1 +1,3 @@
-"12345678"
+# encoding: US-ASCII
+#    valid: true
+"123456785678"

Instructions:
[ruby-3.0.2p107] ruby --dump=insns -e "\"#{1234}#{5678}\""
== disasm: #<ISeq:<main>@-e:1 (1,0)-(1,16)> (catch: FALSE)
0000 putobject                              ""                        (   1)[Li]
0002 putobject                              1234
0004 dup
0005 opt_send_without_block                 <calldata!mid:to_s, argc:0, FCALL|ARGS_SIMPLE>
0007 tostring
0008 putobject                              5678
0010 dup
0011 opt_send_without_block                 <calldata!mid:to_s, argc:0, FCALL|ARGS_SIMPLE>
0013 tostring
0014 concatstrings                          3
0016 leave

I'll try to poke around by myself, but the issue seems a bit complicated.
My first guess is that something is messing up the stack so the second tostring instruction is popping wrong values. Presumably opt_send_without_block may be the cause as it seems to be the most complex piece haha

Extra info: the failed to allocate memory error is raised on the leave handler.


Lazy injections support

Codecov Report

Merging #29 (bae3d81) into main (e18ef67) will decrease coverage by 0.67%.
The diff coverage is 96.46%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##              main      #29      +/-   ##
===========================================
- Coverage   100.00%   99.33%   -0.67%
===========================================
  Files            8        7       -1
  Lines          578      604      +26
===========================================
+ Hits           578      600      +22
- Misses           0        4       +4

Impacted Files
Coverage Δ

pyxdi/ext/fastapi.py
98.18% <90.00%> (-1.82%)
:arrow_down:

pyxdi/utils.py
92.85% <91.66%> (-7.15%)
:arrow_down:

pyxdi/core.py
99.78% <98.33%> (-0.22%)
:arrow_down:

pyxdi/decorators.py
100.00% <100.00%> (ø)

pyxdi/exceptions.py
100.00% <100.00%> (ø)


Fix #9456: incorrect treatment of Accept-Encoding vs Content-Encoding

Codecov Report

Merging #9457 (e17c958) into develop (ad9927d) will decrease coverage by 0.01%.
The diff coverage is 14.28%.

@@              Coverage Diff              @@
##             develop    #9457      +/-   ##
=============================================
- Coverage      54.30%   54.28%   -0.02%
+ Complexity     35864    35859       -5
=============================================
  Files           2460     2460
  Lines         193988   193991       +3
  Branches       35250    35250
=============================================
- Hits          105342   105317      -25
- Misses         73571    73609      +38
+ Partials       15075    15065      -10

Impacted Files
Coverage Δ
Complexity Δ

...ent/server/network/protocol/http/OHttpRequest.java
73.07% <ø> (ø)
19.00 <0.00> (ø)

...rient/server/network/protocol/http/OHttpUtils.java
50.00% <ø> (ø)
3.00 <0.00> (ø)

...rk/protocol/http/ONetworkProtocolHttpAbstract.java
50.95% <0.00%> (-0.77%)
41.00 <0.00> (-1.00)

...server/network/protocol/http/OHttpRequestImpl.java
60.41% <33.33%> (-6.25%)
20.00 <1.00> (ø)

...stributed/OModifiableDistributedConfiguration.java
45.68% <0.00%> (-10.35%)
12.00% <0.00%> (-4.00%)

...orient/core/sql/OCommandExecutorSQLLiveSelect.java
57.65% <0.00%> (-6.31%)
15.00% <0.00%> (-4.00%)

...ntechnologies/orient/server/OClientConnection.java
72.28% <0.00%> (-1.81%)
52.00% <0.00%> (-1.00%)

...aginated/wal/common/deque/MPSCFAAArrayDequeue.java
46.08% <0.00%> (-1.74%)
17.00% <0.00%> (ø%)

...ent/client/remote/OStorageConfigurationRemote.java
63.63% <0.00%> (-1.52%)
16.00% <0.00%> (-1.00%)

...logies/orient/server/OClientConnectionManager.java
55.59% <0.00%> (-1.50%)
41.00% <0.00%> (ø%)

... and 25 more

Continue to review full report at Codecov.

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