[ldd-img_surface] Reachability labels

Add support for two reachability products: ARM type, and GRN/GRA/GRC types.
Standard reachability use case:
INSTRUMENT_BAND_ID=(DRILL, GDRT, ...)
CONFIGURATION_BIT_ID=(ARM_SO_EU_WU, ARM_SO_EU_WD, ...)
(CONFIGURATION_BITS = 2)  default to 2 if not given for compat

<img_surface:Reachability>
   <img_surface:device_id>Arm</>
   <img_surface:Reach_Instruments>
      <img_surface:Reach_Instrument>
         <img_surface:instrument__id>DRILL</>
         <img_surface:band>1</>
      </>
      <img_surface:Reach_Instrument>
         <img_surface:instrument_id>GDRT</>
         <img_surface:band>2</>
      </>
      ...
   </>
   <img_surface:Configurations>
      <img_surface:Configuration>
         <img_surface:device_config>ARM_SO_EU_WU</>
         <img_surface:start_bit>15</>
         <img_surface:stop_bit>14</>
      </>
      <img_surface:Configuration>
         <img_surface:device_config>ARM_SO_EU_WD</>
         <img_surface:start_bit>13</>
         <img_surface:stop_bit>12</>
      </>
   </>
</>

Reachability goodness use case:
INSTRUMENT_LIST_ID=(DRILL, GDRT, ...)
CONFIGURATION_BIT_ID=(ARM_SO_EU_WU, ARM_SO_EU_WD, ...)
CONFIGURATION_BITS = 1
CONFIGURATION_BAND = 2

<img_surface:Reachability>
   <img_surface:device_id>Arm</>
   <img_surface:Reach_Instruments>
      <img_surface:Reach_Instrument>
         <img_surface:instrument_id>DRILL</>
      </>
      <img_surface:Reach_Instrument>
         <img_surface:instrument_id>GDRT</>
      </>
      ...
   </>
   <img_surface:Configurations>
      <img_surface:band>2</>
      <img_surface:Configuration>
         <img_surface:device_config>ARM_SO_EU_WU</>
         <img_surface:start_bit>7</>
         <img_surface:stop_bit>7</>
      </>
      <img_surface:Configuration>
         <img_surface:device_config>ARM_SO_EU_WD</>
         <img_surface:start_bit>6</>
         <img_surface:stop_bit>6</>
      </>
   </>
   ...
</>

The Configuration keywords would not appear if the optional 2nd band was missing.
Reachability - child of Surface_Imaging, card 0-1
This class describes Reachability products, which define whether and how a moving device (such as an arm) can contact, view, or otherwise interact with the world at each pixel of an image.
device_id - child of Reachability, card 0-1. 2020 and MSL valids: Arm
Identifies the device that this Reachability applies to, for example as "Arm".
Reach_Instruments - child of Reachability, card 0-1
Lists the instruments involved in this reachability assesment.
Reach_Instrument - child of Reach_Instruments, card 0-any
Defines a single instrument for this reachability assessment. For products where each instrument is associated with a band in the output, the "band" attribute specifies which band it is. For products where instruments are involved in the computation but not represented individually in the output, the band should be omitted.
instrument_id - child of Reach_Instrument, card 1. 2020 valids: "DRILL","GDRT","SHERLOC_WATSON","SHERLOC","PIXL", "FCS" . MSL valids: "DRILL","DRT","MAHLI","APXS","SCOOP_TIP" . Note, do not lowercase these in the template, most are acronyms.
Identifies the instrument used in reachability assessment.
band - child of Reach_Instrument, card 0-1, valid 1-any
Specifies the band number (1-based) of the band in which the data for the specified instrument resides.
Configurations - child of Reachability, card 0-1
Specifies the configurations of the device used for reachability assessment. The specific values will be device-dependent but could include e.g. shoulder in/out, elbow up/down, wrist up/down.
Configuration - child of Configurations, card 0-any
Defines a single configuration for this reachability assessment.
device_config - child of Configuration, card 1. MSL and M20 valids: "ARM_SO_EU_WU", "ARM_SO_EU_WD", "ARM_SO_ED_WU", "ARM_SO_ED_WD", "ARM_SI_EU_WU", "ARM_SI_EU_WD", "ARM_SI_ED_WU", "ARM_SI_ED_WD"
Names a specific configuration of the device.
start_bit - child of Configuration, card 0-1, valid 0-any (really don't want to limit the # of bits to anything specific...)
For Configurations that are bit-packed into a word, specifies the starting bit for this configuration. Bits are numbered starting at 0 for the least-significant bit.
stop_bit - child of Configuration, card 0-1, valid 0-any (really don't want to limit the # of bits to anything specific...)
For Configurations that are bit-packed into a word, specifies the ending bit for this configuration. Bits are numbered starting at 0 for the least-significant bit. If present, stop_bit must be equal to or less than start_bit. If absent, start_bit identifies a single bit.

A little confusing. I think I got it implemented correctly in v<IP_ADDRESS>
So continuous integration failed on this build for 1.F.0.0. GEOM needs some updates to support 1.F.0.0 so for now I built a release for 1.D.0.0 for testing and potential official release.
https://github.com/pds-data-dictionaries/ldd-img_surface/tree/master/build/release/1.E.0.0_<IP_ADDRESS>


Align component integration test case with assertion of default state of component

relates to #783

@notmessenger is this considered done via #783? Or is there more to do here? Please elaborate.

@SpikedKira Not sure - would have to look through the PR to see if this issue was addressed by it.  If it seems that it has been let me know and I will close this issue.  As long as the test aligns with all the others then I don't recall anything special remaining to be addressed.

Double checked.  Yes, I do believe this has been resolved.


fix(nuxt): add baseURL to NuxtIsland fetch request

🔗 Linked issue
resolve https://github.com/nuxt/nuxt/issues/22002

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Hi :wave: this PR prepend the fetch request of NuxtIsland with the baseURL or it wouldn't correctly hit the endpoint of islands renderer

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

@danielroe can i set a app.baseURL for fixtures/basic ?

edit: building it with app.baseURL crash due to prerender -> https://github.com/nuxt/nuxt/issues/22010

Regarding setting app.baseURL we do this already dynamically in one of the tests - maybe you could reproduce the issue in a regression test that way?

Sure ! I'll convert this PR to draft. Will finish in a few days


russian language updates

grammar, punctuation, better readability

Hey @Grawl, thanks for the improvements.

Thank you for such a great game! Without it, it’s will be hard to understand grid basics.


[x] website builds and runs in production - for information on how to test locally go here.

Description
Restructure "deploying" doc to be clearer
Related Issues
Related to #359
Fixes: https://github.com/appsody/appsody/issues/885
Note: the ### Deploying your application through Docker Hub and ### Deploying your application to a custom registry sections get fixed as part of https://github.com/appsody/website/pull/566

For the FAQ section, appsody init is the only command that still works fine with minikube. I'm not sure if we need to document that or if we should just say generally that appsody commands won't work here


Mask visibility always on (ie mask placeholder)

Provide the ability to always see the mask. As an example, when viewing an input field for a phone number, instead of filling in the mask as the user types, we would see (__) - in the empty input field. As the values are inserted, they replace the relative _underscore in the masked text string.
Ideally, one could control this visibility (displayPlaceholder) through a simple T/F (default F) property and also have an optional parameter to provide the placeholder (default is '_' underscore)

+1

This would be a great addition. I used this feature with ui-mask but it's not near as robust as ngMask.

+1

+1

+1

+1

+1


What "skip swap ... as aggregator is busy" means?

Hello,
I'm doing a simple tcp-check through HAproxy:
tcp-check send *1\r\n
tcp-check send $4\r\n
tcp-check send PING\r\n
tcp-check expect string +PONG

From the HAproxy's point of view the nodes are up and respond the excepted "PONG" but if I check the Dynomite logs the connections seams to be dropped. The reccurent messages are "Connection reset by peer" coupled with "skip swap...".
I've pasted my log for one call:
Thanks a lot for your help.
Verbose 7
[Thu Apr 23 13:30:18 2015] dyn_proxy.c:341 accepted c 10 on p 7 from '<IP_ADDRESS>:17312'
[Thu Apr 23 13:30:18 2015] dyn_message.c:221 alloc_msg_count : 1
[Thu Apr 23 13:30:18 2015] dyn_message.c:221 alloc_msg_count : 2
[Thu Apr 23 13:30:18 2015] dyn_core.c:324 close c 10 'unknown' on event FF00FF eof 0 done 0 rb 14 sb 7: Connection reset by peer

Verbose 11
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:261 epoll 0001 triggered on conn 0x1502c80
[Thu Apr 23 13:29:33 2015] dyn_core.c:455 event 00FF on p 7
[Thu Apr 23 13:29:33 2015] dyn_client.c:51 ref conn 0x150d450 owner 0x14fb2a0 into pool 'bbc_test'
[Thu Apr 23 13:29:33 2015] dyn_connection.c:324 get conn 0x150d450 client 1
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1247 metric 'client_connections' in pool 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1264 incr field 'client_connections' to 1
[Thu Apr 23 13:29:33 2015] dyn_proxy.c:341 accepted c 9 on p 7 from '<IP_ADDRESS>:17303'
[Thu Apr 23 13:29:33 2015] dyn_proxy.c:285 accept on p 7 not ready - eagain
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1198 skip swap of current 0x14fe390 shadow 0x150e410 as aggregator is busy
[Thu Apr 23 13:29:33 2015] dyn_core.c:575 timeout = 30000
[Thu Apr 23 13:29:33 2015] dyn_core.c:555 length of C2G_OutQ : 0
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:249 epoll ep 5
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:261 epoll 0005 triggered on conn 0x150d450
[Thu Apr 23 13:29:33 2015] dyn_core.c:455 event FFFF on c 9
[Thu Apr 23 13:29:33 2015] dyn_message.c:351 get msg 0x1514ee0 id 3 request 1 owner sd 9
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:108 get mbuf 0x1519008
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:197 insert mbuf 0x1519008 len 0
[Thu Apr 23 13:29:33 2015] dyn_connection.c:468 recv on sd 9 14 of 16328
[Thu Apr 23 13:29:33 2015] dyn_redis.c:1621 parsed req 3 res 0 type 80 state 0 rpos 14 of 14
00000000  2a 31 0d 0a 24 34 0d 0a  50 49 4e 47 0d 0a         |*1..$4..PING..|
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1247 metric 'client_read_requests' in pool 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1264 incr field 'client_read_requests' to 2
[Thu Apr 23 13:29:33 2015] dyn_server.c:902 server_get_dc pool  'dc1'
[Thu Apr 23 13:29:33 2015] dyn_server.c:932 server_get_rack   'rc1'
[Thu Apr 23 13:29:33 2015] dyn_vnode.c:72 peer name       : '<IP_ADDRESS>'
[Thu Apr 23 13:29:33 2015] dyn_vnode.c:73 peer rack       : 'rc1'
[Thu Apr 23 13:29:33 2015] dyn_vnode.c:74 peer dc       : 'dc1'
[Thu Apr 23 13:29:33 2015] dyn_vnode.c:75 peer->processed = 1
[Thu Apr 23 13:29:33 2015] dyn_dnode_peer.c:1217 dyn: key '' on dist 3 maps to server '<IP_ADDRESS>:8101'
[Thu Apr 23 13:29:33 2015] dyn_message.c:171 insert msg 3 into tmo rbt with expiry of 10000 msec
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'in_queue' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1384 incr field 'in_queue' to 1
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'in_queue_bytes' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1418 incr by field 'in_queue_bytes' to 14
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'read_requests' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1384 incr field 'read_requests' to 2
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'read_request_bytes' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1418 incr by field 'read_request_bytes' to 28
[Thu Apr 23 13:29:33 2015] dyn_request.c:524 local forward from c 9 to s 6 req 3 len 14 type 80 with key ''
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1198 skip swap of current 0x14fe390 shadow 0x150e410 as aggregator is busy
[Thu Apr 23 13:29:33 2015] dyn_core.c:575 timeout = 10000
[Thu Apr 23 13:29:33 2015] dyn_core.c:555 length of C2G_OutQ : 0
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:249 epoll ep 5
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:261 epoll 0004 triggered on conn 0x1502ad0
[Thu Apr 23 13:29:33 2015] dyn_core.c:455 event FF00 on s 6
[Thu Apr 23 13:29:33 2015] dyn_request.c:749 send next req 3 len 14 type 80 on s 6
[Thu Apr 23 13:29:33 2015] dyn_connection.c:519 sendv on sd 6 14 of 14 in 1 buffers
[Thu Apr 23 13:29:33 2015] dyn_request.c:763 send done req 3 len 14 type 80 on s 6
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'in_queue' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1401 decr field 'in_queue' to 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'in_queue_bytes' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1435 decr by field 'in_queue_bytes' to 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'out_queue' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1384 incr field 'out_queue' to 1
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'out_queue_bytes' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1418 incr by field 'out_queue_bytes' to 14
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1198 skip swap of current 0x14fe390 shadow 0x150e410 as aggregator is busy
[Thu Apr 23 13:29:33 2015] dyn_core.c:575 timeout = 10000
[Thu Apr 23 13:29:33 2015] dyn_core.c:555 length of C2G_OutQ : 0
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:249 epoll ep 5
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:261 epoll 0001 triggered on conn 0x1502ad0
[Thu Apr 23 13:29:33 2015] dyn_core.c:455 event 00FF on s 6
[Thu Apr 23 13:29:33 2015] dyn_message.c:351 get msg 0x1519190 id 4 request 0 owner sd 6
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:108 get mbuf 0x151d2b8
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:197 insert mbuf 0x151d2b8 len 0
[Thu Apr 23 13:29:33 2015] dyn_connection.c:468 recv on sd 6 7 of 16328
[Thu Apr 23 13:29:33 2015] dyn_redis.c:2033 parsed rsp 4 res 0 type 118 state 0 rpos 7 of 7
00000000  2b 50 4f 4e 47 0d 0a                               |+PONG..|
[Thu Apr 23 13:29:33 2015] dyn_message.c:189 delete msg 3 from tmo rbt
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'out_queue' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1401 decr field 'out_queue' to 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'out_queue_bytes' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1435 decr by field 'out_queue_bytes' to 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'read_responses' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1384 incr field 'read_responses' to 2
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1366 metric 'read_response_bytes' in pool 0 server 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1418 incr by field 'read_response_bytes' to 14
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1198 skip swap of current 0x14fe390 shadow 0x150e410 as aggregator is busy
[Thu Apr 23 13:29:33 2015] dyn_core.c:575 timeout = 30000
[Thu Apr 23 13:29:33 2015] dyn_core.c:555 length of C2G_OutQ : 0
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:249 epoll ep 5
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:261 epoll 0004 triggered on conn 0x150d450
[Thu Apr 23 13:29:33 2015] dyn_core.c:455 event FF00 on c 9
[Thu Apr 23 13:29:33 2015] dyn_response.c:325 send next rsp 4 on c 9
[Thu Apr 23 13:29:33 2015] dyn_connection.c:519 sendv on sd 9 7 of 7 in 1 buffers
[Thu Apr 23 13:29:33 2015] dyn_response.c:338 send done rsp 4 on c 9
[Thu Apr 23 13:29:33 2015] dyn_message.c:453 put msg 0x1519190 id 4
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:220 remove mbuf 0x151d2b8 len 0
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:136 put mbuf 0x151d2b8 len 0
[Thu Apr 23 13:29:33 2015] dyn_message.c:453 put msg 0x1514ee0 id 3
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:220 remove mbuf 0x1519008 len 0
[Thu Apr 23 13:29:33 2015] dyn_mbuf.c:136 put mbuf 0x1519008 len 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1198 skip swap of current 0x14fe390 shadow 0x150e410 as aggregator is busy
[Thu Apr 23 13:29:33 2015] dyn_core.c:575 timeout = 30000
[Thu Apr 23 13:29:33 2015] dyn_core.c:555 length of C2G_OutQ : 0
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:249 epoll ep 5
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:261 epoll 0019 triggered on conn 0x150d450
[Thu Apr 23 13:29:33 2015] dyn_core.c:455 event FF00FF on c 9
[Thu Apr 23 13:29:33 2015] dyn_core.c:324 close c 9 'unknown' on event FF00FF eof 0 done 0 rb 14 sb 7: Connection reset by peer
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1247 metric 'client_connections' in pool 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1282 decr field 'client_connections' to 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1247 metric 'client_err' in pool 0
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1264 incr field 'client_err' to 2
[Thu Apr 23 13:29:33 2015] dyn_client.c:70 unref conn 0x150d450 owner 0x14fb2a0 from pool 'bbc_test'
[Thu Apr 23 13:29:33 2015] dyn_connection.c:428 put conn 0x150d450
[Thu Apr 23 13:29:33 2015] dyn_stats.c:1198 skip swap of current 0x14fe390 shadow 0x150e410 as aggregator is busy
[Thu Apr 23 13:29:33 2015] dyn_core.c:575 timeout = 30000
[Thu Apr 23 13:29:33 2015] dyn_core.c:555 length of C2G_OutQ : 0
[Thu Apr 23 13:29:33 2015] dyn_epoll.c:249 epoll ep 5

That is for swapping of stats aggregator structure.  There are 2 threads checking on that variable on whether to move forward for processing.  It should be harmless.
Btw, you should not run Dynomite with that high level debug logging.


Add UMD galaxy unit tests into metal CI pipeline

Tests found here tt_metal/third_party/umd/tests/galaxy.
These tests are pretty old.. Should probably add into existing [TG] TG unit tests pipeline

merged with https://github.com/tenstorrent/tt-metal/pull/11677


Feature Request: Add dockerfile for digital ocean webapp hosting and for local dev

For digital ocean they require the usage of a dockerfile for the build process so adding one would help with those deployments. Adding a docker file would also make the project easier to locally maintain as it would remove the need of installing rust tools on one's machine.

I'm fine with having a dockerfile for local development (it'd be short and sweet), but we use Heroku to deploy the app!


Serialize messages to JSON in dashboard

Fixes #1464
Pull Request Checklist
(Please keep this section. It will make maintainer's life easier.)

[x] Privileged views and APIs are guarded by proper permission checks.
[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Database queries are optimized and the number of queries is constant.
[x] The changes are tested.
[x] The code is documented (docstrings, project documentation).
[x] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[x] JavaScript code quality checks pass: eslint.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0f577d6). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master    #1471   +/-   ##
=========================================
  Coverage          ?   83.21%
=========================================
  Files             ?      128
  Lines             ?     5857
  Branches          ?      676
=========================================
  Hits              ?     4874
  Misses            ?      821
  Partials          ?      162

Impacted Files
Coverage Δ

saleor/dashboard/templatetags/utils.py
86.3% <100%> (ø)

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 0f577d6...d104b54. Read the comment docs.

@dominik-zeglen We can remove the _messages.html file.


Improved/optimized triplestore

Desired features of a new/improved triplestore

Fast compression on disk (lz4?)
Fast queries
De-duplicate fields in memory (use tokens instead of ids/predicates?)
Use existing solution (Cayley?)

As for Cayley, see concerns https://news.ycombinator.com/item?id=10589886

Optimized batch inserts with GORM by using transactions. https://github.com/degdb/degdb/commit/4dbc82cc167404b90920ff0e08a4d14caa870945

Cayley investigation: https://github.com/google/cayley/issues/344


[BRN-105] Add all active strategy's json files

Added all active, non-v1 strategies to strategy directory. Make sure to double check that everything is correct pls. As of now some descriptions have links and some do not. I can go through and fix this in a bit. All v2 strategies should be listed, if any are missing let me know.

Some general comments:

VoterProxy, Genlender, Convex, Pool Together, Idle, and other strategies that are similar but the only change is the token. Is there a way to generalize them? I've seen the {{token}} variable but I don't know if there are others or we can do it so it's faster to describe a lot of similar strats.
This is for EARN: data/strategies/LPProfitSwitching.json. Are we keeping this in yearn meta? Do we put EARN addresses here?

@DarkGhost7 We ran into these same issues when making strat diagrams and i'm working on narrowing them down right now. Have you started taking an approach to condensing generic vault descriptions? If not, the list I'm making right now for strats will probably help with descriptions as well.

Thinking I should change all instances of re-deposited into the vault to re-deposited into the strategy? We kind of use the two through the descriptions to mean the same thing. Basically change all instance of 'vault' that isn't deposit tokens into another yVault into strategy. Non of these strategies actually send back to the vault that is the vault contracts job to manage this, correct?
Example:
Curve Boosts Strategy
This vault takes your deposited token and turns it into {{token}}... change vault to strategy
Idle COMP Reward Strategy
... Rewards are harvested, sold for more {{token}}, and deposited back to the vault. change vault to strategy

Also, later, if needed we can have fields name pretty  = something like Compound Leverage Strategy  and name = {{name}} pulling this from the strategy contract data. Depending on what people will use the API data for they might want to know what the name of the strategy is from the strategy contract.

@DarkGhost7 Don't worry, I'll address both issue.

Updated most of it, still have to go through:
Proxy:

[ ] data/strategies/individual_strats/voterproxy_unique/CurveFRAX3CRV-fVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/Curvea3CRVVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/CurvealUSD3CRV-fVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/CurveankrCRVVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/CurvecrvPlain3andSUSDVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/CurveoBTCsbtcCRVVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/CurvepBTCsbtcCRVVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/CurverCRVVoterProxy.json
[ ] data/strategies/individual_strats/voterproxy_unique/StrategystETHCurve.json

Other:

[ ] data/strategies/VoterProxy.json
[ ] data/strategies/individual_strats/AaveLender_unique/AaveLenderLINKBorrowerSUSD.json
[ ] data/strategies/individual_strats/AaveLender_unique/AaveLenderWBTCBorrowerUSDC.json
[ ] data/strategies/individual_strats/AaveLender_unique/AaveWETHLenderUSDTBorrower.json
[ ] data/strategies/individual_strats/DAOFeeClaim.json
[ ] data/strategies/individual_strats/Generalized one-sided/StrategyeCurveWETHSingleSided.json
[ ] data/strategies/individual_strats/Generalized one-sided/StrategysteCurveWETHSingleSided.json
[ ] data/strategies/individual_strats/IBLevComp.json
[ ] data/strategies/individual_strats/SingleSided_unique/SingleSidedCrvSynthsETH.json
[ ] data/strategies/individual_strats/SingleSided_unique/SingleSidedCrvsUSD - saave.json
[ ] data/strategies/individual_strats/SingleSided_unique/SingleSidedCrvsUSD - susd2.json
[ ] data/strategies/individual_strats/StrategyGenericLevCompFarm.json
[ ] data/strategies/individual_strats/StrategySynthetixSusdMinter.json
[ ] data/strategies/individual_strats/StrategyYearnVECRV.json

@DarkGhost7 @philburrrt I've cleaned up all strats. Text is final and should be consistent between all jsons. I propose you review that this is true and we merge this PR as is. After that we have to:

[ ] remove duplicate strats or combine strats which have generalized description
[ ] fix filepaths
[ ] rename all starts to have generic names
[ ] add protocols touched by strategies

Looks good to me ready to merge.


terraform-providers: update providers

Motivation for this change
Apart from a couple of problematic providers this updates everything using the terraform registry.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

cc @zimbatm

@ofborg build terraform-full

Result of nixpkgs-review pr 153201 run on x86_64-linux 1

1 package marked as broken and skipped:

terraform-full

66 packages built:

terraform-providers.aci
terraform-providers.auth0
terraform-providers.avi
terraform-providers.aviatrix
terraform-providers.baiducloud
terraform-providers.bigip
terraform-providers.brightbox
terraform-providers.checkpoint
terraform-providers.ciscoasa
terraform-providers.cloudscale
terraform-providers.constellix
terraform-providers.dme
terraform-providers.dnsimple
terraform-providers.docker
terraform-providers.dome9
terraform-providers.exoscale
terraform-providers.flexibleengine
terraform-providers.fortios
terraform-providers.gridscale
terraform-providers.heroku
terraform-providers.huaweicloud
terraform-providers.huaweicloudstack
terraform-providers.icinga2
terraform-providers.infoblox
terraform-providers.ksyun
terraform-providers.launchdarkly
terraform-providers.linode
terraform-providers.logicmonitor
terraform-providers.mailgun
terraform-providers.matchbox
terraform-providers.mongodbatlas
terraform-providers.ncloud
terraform-providers.newrelic
terraform-providers.ns1
terraform-providers.nsxt
terraform-providers.nutanix
terraform-providers.okta
terraform-providers.oktaasa
terraform-providers.opc
terraform-providers.opennebula
terraform-providers.opentelekomcloud
terraform-providers.opsgenie
terraform-providers.pagerduty
terraform-providers.panos
terraform-providers.pass
terraform-providers.powerdns
terraform-providers.rundeck
terraform-providers.scaleway
terraform-providers.selectel
terraform-providers.signalfx
terraform-providers.skytap
terraform-providers.spotinst
terraform-providers.stackpath
terraform-providers.statuscake
terraform-providers.sumologic
terraform-providers.tencentcloud
terraform-providers.tfe
terraform-providers.triton
terraform-providers.turbot
terraform-providers.ucloud
terraform-providers.vcd
terraform-providers.venafi
terraform-providers.vra7
terraform-providers.vultr
terraform-providers.wavefront
terraform-providers.yandex

I'm not sure why terraform-full was skipped, but it builds fine here.

After this PR is merged, ["cloudstack", "segment", "vthunder"] are the only providers that don't have a provider-source-address. I propose that those get removed so we can remove the old support.

After this PR is merged, ["cloudstack", "segment", "vthunder"] are the only providers that don't have a provider-source-address. I propose that those get removed so we can remove the old support.

I've got a PR for those: https://github.com/NixOS/nixpkgs/pull/153206


chore: Check new git permissions for respective git operations

Description
This PR uses the new Git permissions for Connect to Git, disconnect from Git, Protect branch and manage auto commit settings.
PR fixes following issue(s)
Fixes #29963
Media
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
How Has This Been Tested?

[x] Manual
[x] JUnit

Test Plan
Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

Refactor

Enhanced Git integration for improved application-level permission handling.

Tests

Updated test cases to accommodate the new permission model for Git operations.

/build-deploy-preview

/build-deploy-preview

/build-deploy-preview

/ok-to-test sha=3105aa2

/build-deploy-preview skip-tests=true

/ok-to-test<EMAIL_ADDRESS>


anchor channel

Done all we can do with this for now. An alert from this PR will tell us when we need to bump the closing fee from our side.


chore: change code owners to whole team and limit access to license file

Description
Make the whole team the owner of the code, but limit access to the license file to the admins as licenses have to be validated by lawyers and shouldn't be changed by everyone.

We can go with a red pipeline as we have to switch to the new default workflows.

@kindermannlennart you have to approve this MR too in order for this to be merged.


Implement inbound passthrough hairpin

For https://github.com/istio/ztunnel/issues/73

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@howardjohn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

More testing is in https://github.com/istio/ztunnel/pull/319


Fix sketch canvas not resizing properly. Fix #973

@avandecreme Thank you!
@leesei I've gone ahead and merged it, but can you verify that it's working to fix your issue?


Update index.md

Fixes #15797
cc @guardrex  @serpent5

There is no direct relationship between dotnet run and the server(s) involved.
If anything, I'd rest easier ⚰ by saying ...

Kestrel is the default web server specified by the ASP.NET Core project templates.

... the server isn't "included" in the template in any cosmic sense. The template is set up to use it, so it seems more "specified by" than "included in."

@guardrex  better - but - what about 85% of our customers who create templates and launch from VS, where IIS Express is the default web server?

It's a little further down in the Windows tab ... gets into it.
This has been a pain point from the start with explaining ASP.NET Core. Yes, indeed ... there often hasn't been just one server for most users, but many devs come in looking to hear about the ONE server that they'll be using. The word "server" is overloaded. They eventually learn that there are several servers around here.
... tack on "host" (two other things now because IWebHostBuilder is still a thing with the Generic Host), and "host" is overloaded with "server." Welcome to my world of the Host and Deploy node! :smile::cry::smile:


Certificate error launching new VDC

I launched a new VDC. I got an error at the end but did not get payback.
When trying to access the VDC, I get a 'cert error'
3bot: geertincubaid
VDC: silver11
https://geertincubaid-silver11.vdctest.grid.tf/vdc_dashboard gives cert-error, no possibility to bypass

Probably linked to https://github.com/threefoldtech/tf_operations/issues/294


Fixes 4338: add content uploading proxy apis

Summary
Adds the following proxy APIs for uploading content to pulp:

Create an upload
Upload a file chunk
Finish an upload
Fetch a task

Testing steps
There are a lot of steps to test this flow.

Pulp's API docs for uploads can be found here
Usage docs can be found here
You can also use this script which may be helpful

Otherwise you can test with the following steps:

Download and extract the LibreOffice rpms to test with. After extracting, the rpms will be in the RPMS directory.

Get the size in bytes of the rpm you plan to test with (there are lots of ways to do this):
ls -l <rpm_file> | awk '{print $5}'

Split one of the rpms into chunks (this is splitting into 6MB chunks and each chunk will be named like test_aa, test_ab, etc):
split -b 6M <rpm_file> test

Generate the checksum for the rpm:
Mac: shasum -a 256 <rpm_file>
Linux: sha256sum <rpm_file>

Optionally generate checksums for each rpm chunk. The chunk's checksum is an optional parameter for the PUT request.

Create the upload:

curl -X POST localhost:8000/api/content-sources/v1.0/pulp/uploads/ \
  -H 'x-rh-identity: <identity_header>' \
  -H 'Content-Type: application/json' \
  -d '{"size": <rpm_size>}'

Response should look like this:
{
    "pulp_created": "2024-07-01T14:04:44.220526Z",
    "pulp_href": "/api/pulp/dd51c811/api/v3/uploads/01906e9c-bd3b-74b2-a7b3-e122e9ca88d5/",
    "pulp_last_updated": "2024-07-01T14:04:44.220541Z",
    "size": 7056
}

The pulp_href is the upload_href you will use in the next 2 requests.

Upload a chunk:

Content-Range header values:

start = chunk number * chunk size in bytes (chunk number starts at 0)
end = start + chunk size in bytes - 1

curl -X PUT localhost:8000/api/content-sources/v1.0/pulp/uploads/<upload_href> \
  -H 'x-rh-identity: <identity_header>' \
  -H 'Content-Range: bytes <start>-<end>/*' \
  --form 'file=@"<chunk_file>"' \
  --form 'sha256="<rpm_chunk_checksum>"'

Response should look like this:
{
    "pulp_created": "2024-07-01T14:44:58.435098Z",
    "pulp_href": "/api/pulp/dd51c811/api/v3/uploads/01906ec1-93c2-7af5-99b5-12d880a1e485/",
    "pulp_last_updated": "2024-07-01T14:44:58.435113Z",
    "size": 7056
}

Finish the upload:

curl -X POST localhost:8000/api/content-sources/v1.0/pulp/uploads/<upload_href> \
  -H 'x-rh-identity: <identity_header>' \
  -H 'Content-Type: application/json' \
  -d '{"sha256": "<rpm_checksum>"}'

Response returns the task href that is queued to create the artifact and should look like this:
{
    "task": "/api/pulp/dd51c811/api/v3/tasks/01906eb8-d423-7323-9123-03a775bb3500/"
}

Get the artifact href from the task:

curl -X GET localhost:8000/api/content-sources/v1.0/pulp/tasks/<task_href> \
  -H 'x-rh-identity: <identity_header>' \
  -H 'Content-Type: application/json'

Response should look like this, the artifact_href is under created_resources:
{
    "child_tasks": [],
    "created_by": "/api/pulp/dd51c811/api/v3/users/1/",
    "created_resources": [
        "/api/pulp/dd51c811/api/v3/artifacts/01906ea1-4343-7a12-a71a-180bd6faa122/"
    ],
    "finished_at": "2024-07-01T14:09:40.68993Z",
    "logging_cid": "9ad506d1-9f18-44f0-abe4-615056e51817",
    "name": "pulpcore.app.tasks.upload.commit",
    "progress_reports": [],
    "pulp_created": "2024-07-01T14:09:40.609565Z",
    "pulp_href": "/api/pulp/dd51c811/api/v3/tasks/01906ea1-4301-7315-8cc9-f517f5fa79d7/",
    "pulp_last_updated": "2024-07-01T14:09:40.609584Z",
    "reserved_resources_record": [
        "/api/pulp/dd51c811/api/v3/uploads/01906e9c-bd3b-74b2-a7b3-e122e9ca88d5/",
        "prn:core.upload:01906e9c-bd3b-74b2-a7b3-e122e9ca88d5",
        "shared:prn:core.domain:019027bb-562c-7ab6-8636-50d1e0134ea8",
        "shared:/api/pulp/default/api/v3/domains/019027bb-562c-7ab6-8636-50d1e0134ea8/"
    ],
    "started_at": "2024-07-01T14:09:40.657947Z",
    "state": "completed",
    "unblocked_at": "2024-07-01T14:09:40.619289Z",
    "worker": "/api/pulp/default/api/v3/workers/01902733-d5d1-7de0-a98e-df71415e451b/"
}

Checklist

[ ] Tested with snapshotting feature disabled and pulp server URL not configured if appropriate

https://issues.redhat.com/browse/HMS-4338


Add support for --before, --then and --else flags

Fix #410
Description of the change
Added support for commands to be run around the build. --before is run before the build, --then following a successful build and --else following an unsuccessful build.
I realise there were some alternative suggestions in the issue, but I personally prefer the original suggestion as I really liked the way it worked with Pulp.
Checklist:

[*] Added the change to the "Unreleased" section of the changelog
[*] Added some example of the new feature to the README
[*] Added a test for the contribution (if applicable)

P.S.: the above checks are not compulsory to get a change merged, so you may skip them. However, taking care of them will result in less work for the maintainers and will be much appreciated 😊

It has also occurred to me that the build should be cancelled if the command fails in some way. Currently it is ignoring the result.

I have changed the example just just post a notification. Inspiration for anything else just wasn't coming!
Now if the command returns an error, it will halt the build.
I have also moved the then command so it runs after the postBuild. I feel it makes more sense to run this after bundling has completed when running bundle-app. It could be useful to do some processing with the bundled file.
Let me know if you want me to revert either of these additional changes.

@FungusHumungus all the new changes look great, thank you for doing this! :slightly_smiling_face:

It was a pleasure! :-)


Investigate Adding script/installer to automatically add chook to ribbon or context menu

Create an installer or script to automatically place the files into the correct directory (based on readme)
and also one to automatically add the icon to the context menu and/or ribbon

Email sent to Mastercam SDk team about adding to context menu or existing menu (instead of creating a whole new tab for it)

Mastercam confirmed it is not possible to add the icon to an existing tab.
Since this chook is only one icon, the installer will just copy/paste files to the chook directory


Question - Sign Language Datasets

An emerging field in NLP is SLP - sign language processing.
I was wondering about adding datasets here, specifically because it's shaping up to be large and easily usable.
The metrics for sign language to text translation are the same.
So, what do you think about (me, or others) adding datasets here?
An example dataset would be RWTH-PHOENIX-Weather 2014 T
For every item in the dataset, the data object includes:

video_path - path to mp4 file
pose_path - a path to .pose file with human pose landmarks
openpose_path - a path to a .json file with human pose landmarks
gloss - string
text - string
video_metadata - height, width, frames, framerate

To make it a tad more complicated - what if sign language libraries add requirements to nlp? for example, sign language is commonly annotated using ilex, eaf, or srt files, which are all loadable as text, but there is no reason for the dataset to parse that file by itself, if libraries exist to do so.

Even more complicating -
As I see it, datasets can have "addons".
For example, the WebNLG dataset is a dataset for data-to-text. However, a work of mine and other works enriched this dataset with text plans / underlying text structures. In that case, I see a need to load the dataset "WebNLG" with "plans" addon.
Same for sign language - if there is a dataset of videos, one addon can be to run OpenPose, another to run ARKit4 pose estimation, and another to run PoseNet, or even just a video embedding addon. (which are expensive to run individually for everyone who wants to use these data)
This is something I dabbled with my own implementation to a research datasets library and I love to get the discussion going on these topics.

This is a really cool idea !
The example for data objects you gave for the RWTH-PHOENIX-Weather 2014 T dataset can totally fit inside the library.
For your point about formats like ilex, eaf, or srt, it is possible to use any library in your dataset script.
However most user probably won't need these libraries, as most datasets don't need them, and therefore it's unlikely that we will have them in the minimum requirements to use nlp (we want to keep it as light-weight as possible). If a user wants to load your dataset and doesn't have the libraries you need, an error is raised asking the user to install them.
More generally, we plan to have something like a requirements.txt per dataset. This could also be a place for addons as you said. What do you think ?

Thanks, Quentin, I think a requirements.txt per dataset will be a good thing.
I will work on adding this dataset next week, and once we sort all of the kinks, I'll add more.


CI complains about Flutter valid archies

Context https://github.com/getsentry/sentry-dart/pull/345#issuecomment-795726263

@denrase just reading your comment, tbh I'm not sure what to do either, we need to be able to run on the simulator, that's for sure.

when I run the pod lint locally, it works sentry_flutter passed validation., Flutter v2.0.1

Hmm, weird. I also ran it locally and it failed for me. Flutter 2.0.1 and Dart 2.12.0.

@denrase maybe you could have a look at it then, cus I can't reproduce it, I've opened a PR to test it out on CI but it didn't help :(

@marandaneto
No luck so far, still get the error when building with 'VALID_ARCHS[sdk=iphonesimulator*]' => 'x86_64', as the Flutter.xcframework contains ios-x86_64-simulator ios-armv7_arm64 slices, and somehow the matching between them fails. When i change the valid archs to ios-x86_64-simulator, pod lint is successful, but i still have warnings.
 -> sentry_flutter (0.0.1)
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | xcodebuild:  note: Building targets in parallel
    - NOTE  | xcodebuild:  note: Using codesigning identity override: -
    - NOTE  | [iOS] xcodebuild:  note: Planning build
    - NOTE  | [iOS] xcodebuild:  note: Constructing build description
    - NOTE  | [iOS] xcodebuild:  warning: None of the architectures in ARCHS (arm64, x86_64, i386) are valid. Consider setting ARCHS to $(ARCHS_STANDARD) or updating it to include at least one value from VALID_ARCHS (ios-x86_64-simulator). (in target 'sentry_flutter' from project 'Pods')
    - NOTE  | [iOS] xcodebuild:  warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'Flutter' from project 'Pods')
    - NOTE  | [iOS] xcodebuild:  warning: [CP] Unable to find matching .xcframework slice in 'Flutter/Flutter.xcframework Flutter framework ios-x86_64-simulator ios-armv7_arm64' for the current build architectures (arm64 x86_64 i386).

Also checked out  #349, it's the same either way.
Somewhere the matching between x86_64 and ios-x86_64-simulator seems to fail. And Flutter versions below 2 seem to have the slices for arm64 x86_64 i386 in the Flutter.xcframework, as the last warning is not displayed when setting the Flutter version to 1.22.4 in the podspec.

I see, well, I don't know what to do either, nothing about that (flutter repo)?

I commented out for now https://github.com/getsentry/sentry-dart/commit/82ef2abed5cf256b47aeb45f56dc2f51fa7843db
as it does change the functionality of the SDK anyway.

We should also add linting for the macOS podspec file.


VSCode crash with error code 132 on Linux

Does this issue occur when all extensions are disabled?: I don't know, it often happens, but it takes a long time to reproduce.

VS Code Version: 1.63.2
OS Version: Fedora 35

Steps to Reproduce:
This is a bit complicated for me to give info and try to find information about the problem. This has been happening very frequently since the last month or so.
My linux install of VSCode crashes very suddenly with the message reason: crashed. Error code: 132 similar to #136479
I didn't use to do this, but now the behavior happen fairly frequently. Since the crash is sudden, I don't have an opportunity to dig in to find more information about what happens.
What is the meaning of error 132? What can I do to help solve this issue?

this also happened to me linux ubuntu 21.10. when I'm trying to debug is crashing, and now I'm not able to debug.

Can you attach the crash dumps following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports, thanks!

I'll do it next time it happens!

I have two crash dumps, I'm not sure which is good, but I think they have been created by the same type of crash:
chromium-renderer-minidump-.zip

I also encountered the issue and was able to create a docker image which seems to be usable for reproducing the error.
Docker build context should contain Dockerfile and entry.sh (remove .txt extensions)
Dockerfile.txt
entry.sh.txt
Build with docker build -t crashtest:latest . when inside the build context dir
Start the container using the following command (depending on your system configuration, you have to play around with xauth, but on Ubuntu 18.04 it works fine):
docker run -it --rm --security-opt seccomp=unconfined -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY="$DISPLAY" -e LOCAL_UID=$(id -u) -e LOCAL_GID=$(id -g) crashtest:latest bash

To reproduce the error in the container:
[foo@c16f267e03ec /]$ /VSCode-linux-x64/code --verbose

Open /etc/bash.bashrc, maximize the window and hold Ctrl++ to zoom in. Repeat with Ctrl+- and so on until crash occurs. Usually occurs within 1-5 seconds.
Log will now show:
[main 2022-02-02T15:53:10.244Z] CodeWindow: renderer process crashed (reason: crashed, code: 133)
[main 2022-02-02T15:53:10.268Z] Error sending IPC message to channel 'vscode:leaveFullScreen' of window 3: Render frame was disposed before WebFrameMain could be accessed
[main 2022-02-02T15:53:10.271Z] Extension host with pid 265 exited with code: 0, signal: null.

I hope you will be able to reproduce the issue using this comment.

Update: I was able to prevent the issue from occurring in the docker image by supplying a large /dev/shm/ size (shared memory) using the flag --shm-size=8G of docker run. This sets the size of /dev/shm/ to 8G, instead of the default of 64M. Maybe the other users encountering this issue may also have too little shared memory? You can find out how much you have using df -h | grep shm.

I still had this issue very recently, especially when running jupyter notebooks

I have somewhat similiar crashes using KDE Wayland (5.24.5) and Manjaro Linux.
For me the error code is 139, but the error message is the same:
[main 2022-06-14T07:54:55.097Z] CodeWindow: renderer process crashed (reason: crashed, code: 139)
[main 2022-06-14T07:54:55.200Z] Extension host with pid 92277 exited with code: 0, signal: null.
Error sending from webFrameMain:  Error: Render frame was disposed before WebFrameMain could be accessed
    at EventEmitter._send (<anonymous>)
    at EventEmitter.n.send (node:electron/js2c/browser_init:165:417)
    at EventEmitter.b.send (node:electron/js2c/browser_init:161:2494)
    at v.send (/usr/lib/code/out/vs/code/electron-main/main.js:21:10266)
    at a.sendBuffer (/usr/lib/code/out/vs/code/electron-main/main.js:20:4330)
    at a.send (/usr/lib/code/out/vs/code/electron-main/main.js:20:4270)
    at a.sendResponse (/usr/lib/code/out/vs/code/electron-main/main.js:20:4125)
    at /usr/lib/code/out/vs/code/electron-main/main.js:21:340
    at h.invoke (/usr/lib/code/out/vs/code/electron-main/main.js:16:145)
    at C.deliver (/usr/lib/code/out/vs/code/electron-main/main.js:16:2269)
    at m.fire (/usr/lib/code/out/vs/code/electron-main/main.js:16:1847)
    at S._handleEventMessage (/usr/lib/code/out/vs/code/electron-main/main.js:18:41535)
    at S._handleMessage (/usr/lib/code/out/vs/code/electron-main/main.js:18:40515)
    at S.handleMessage (/usr/lib/code/out/vs/code/electron-main/main.js:18:40308)
    at Worker.<anonymous> (/usr/lib/code/out/vs/code/electron-main/main.js:18:42117)
    at Worker.emit (node:events:390:28)
    at MessagePort.<anonymous> (node:internal/worker:233:53)
    at MessagePort.[nodejs.internal.kHybridDispatch] (node:internal/event_target:562:20)
    at MessagePort.exports.emitMessage (node:internal/per_context/messageport:23:28)
(electron:92105): Gdk-WARNING **: 09:54:55.202: Server is missing xdg_foreign support
[main 2022-06-14T07:55:03.255Z] IPC Object URL: Removed channel vscode:aad81794-1bde-4478-8608-333cfd440e75.
[main 2022-06-14T07:55:03.255Z] Lifecycle#window.on('closed') - window ID 1
[main 2022-06-14T07:55:03.256Z] Lifecycle#onWillShutdown.fire()
[main 2022-06-14T07:55:03.259Z] IPC Object URL: Removed channel vscode:7c66d9a6-1b1d-42a2-b376-b03db60c8603.
[main 2022-06-14T07:55:03.260Z] storageMainService#onWillShutdown()
[main 2022-06-14T07:55:03.261Z] SharedProcess: disposing worker (reason: 'closed') {
  process: {
    moduleId: 'vs/platform/files/node/watcher/watcherMain',
    type: 'fileWatcher'
  },
  reply: {
    windowId: 1,
    channel: 'vscode:createSharedProcessWorkerMessageChannelResult',
    nonce: 'ab95547b-b911-4f95-a8f9-fda0725aee77'
  }
}

I attached the crash dump, hope that it helps to find the issue.
crash_dump.tar.gz

Hey @deepak1556, this issue might need further attention.
@MalcolmMielle, you can help us out by closing this issue if the problem no longer exists, or adding more information.

I'm currently mainly working on Windows so I+m not sure if the issue has been solved

Hey @deepak1556, this issue might need further attention.
@MalcolmMielle, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This should be addressed in latest stable 1.74 with Electron 19


Dependency on globally installed _ (lodash)?

There seems to be a dependency on the underscore symbol, which not only requires lodash installed (as mentioned in dependencies), but also installed globally (which is typically not acceptable).
Source location: (https://github.com/FiguredLimited/vue-mc/blob/d5e15e4aefb75e26c58cbf4e73d6f28f15a05651/src/Structures/Model.js#L9)

The same applies for Vue, I needed to add global.Vue = Vue to make it work.
Looking at the test index.js, I fear I need to include also other libs:
https://github.com/FiguredLimited/vue-mc/blob/master/test/index.js
Moreover for lodash, it would be better to include a function at once, as per your need, instead of including the entire lib as it's quite big.

This is now a work in progress on the 0.2 branch. See https://github.com/FiguredLimited/vue-mc/pull/13

Moreover for lodash, it would be better to include a function at once, as per your need, instead of including the entire lib as it's quite big.

Rollup does that for us. ✨


Destroy the blue notification bubble

The point of notifications is to get ones you want to see and not get ones you don't want to see.  If this were on a different website that I am not working on I would have instantly made a uBlock rule hiding the "notifications" link in the nav forever.
This feature will be fine once there is a way to cause the notification bubble to only appear for things you want to see.

Thanks for your feedback! It's good to know that notifications can become annoying.
However, it is common practice, and definitely helps us surface interesting content. It would be better to adjust notifications to not include things you don't want to see.
Let's punt on this for a few days to gauge other users' reactions. You also might get used to it!

at least it's not red

@mqp are you satisfied with the notification controls enough to close this PR? You can select the 'None' toggle in the notifications settings to stop seeing the blue bubble

Nice! I am satisfied.


CHOMP: Fix handling of mimic joints

As the CHOMP planner only considers active joints:
https://github.com/moveit/moveit/blob/7a51eeae283512e8f4364bdd1fab009bd7e7a93d/moveit_planners/chomp/chomp_motion_planner/src/chomp_trajectory.cpp#L58
it needs to call setJointGroupActivePositions() instead of setJointGroupPositions(). Otherwise, this assertion fails:
https://github.com/moveit/moveit/blob/7a51eeae283512e8f4364bdd1fab009bd7e7a93d/moveit_core/robot_state/include/moveit/robot_state/robot_state.h#L643

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 47.19%. Comparing base (c174715) to head (599fbde).
Report is 27 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3625      +/-   ##
==========================================
+ Coverage   47.15%   47.19%   +0.04%
==========================================
  Files         603      604       +1
  Lines       58999    59162     +163
  Branches     6969     6989      +20
==========================================
+ Hits        27814    27913      +99
- Misses      30773    30831      +58
- Partials      412      418       +6

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


keeps failing running on ubuntu bionic

ubuntu@ip-XXXXXXX:~/dart-pad$ grind serve
grinder running build serve

build
  /usr/lib/dart/bin/pub run build_runner build -r -o web:build
  [INFO] Generating build script...
  [INFO] Generating build script completed, took 600ms

  [INFO] Creating build script snapshot......
  [INFO] Creating build script snapshot... completed, took 25m 41s

  [SEVERE] Failed to snapshot build script .dart_tool/build/entrypoint/build.dart.
  This is likely caused by a misconfigured builder definition.

failed with exit code 78
#0      run (package:grinder/src/run.dart:48:5)
#1      Pub.run (package:grinder/grinder_sdk.dart:241:12)
#2      _PubLocalApp.run (package:grinder/grinder_sdk.dart:593:16)
#3      build (file:///home/ubuntu/dart-pad/tool/grind.dart:132:32)
#4      _LibraryMirror._invoke (dart:mirrors-patch/mirrors_impl.dart:1093:36)
#5      _ObjectMirror.invoke (dart:mirrors-patch/mirrors_impl.dart:244:25)
#6      TaskDiscovery.discoverDeclaration.<anon> (package:grinder/src/discover_tasks.dart:77:38)
#7      _rootRun (dart:async/zone.dart:1184:13)
#8      _CustomZone.run (dart:async/zone.dart:1077:19)
#9      _runZoned (dart:async/zone.dart:1619:10)
#10     runZoned (dart:async/zone.dart:1539:10)
#11     ZonedValue.withValue (package:grinder/src/utils.dart:113:12)
#12     GrinderTask.execute (package:grinder/src/grinder_task.dart:63:27)
#13     Grinder._invokeTask (package:grinder/src/grinder.dart:193:27)
#14     Grinder.start.<anon> (package:grinder/src/grinder.dart:168:16)
#15     Future.forEach.<anon> (dart:async/future.dart:494:26)
#16     Future.doWhile.<anon> (dart:async/future.dart:536:26)
#17     _RootZone.runUnaryGuarded (dart:async/zone.dart:1374:10)
#18     _RootZone.bindUnaryCallbackGuarded.<anon> (dart:async/zone.dart:1413:26)
#19     Future.doWhile (dart:async/future.dart:551:18)
#20     Future.forEach (dart:async/future.dart:492:12)
#21     Grinder.start (package:grinder/src/grinder.dart:167:21)
#22     runTasks (package:grinder/src/cli.dart:67:38)
#23     grind (package:grinder/grinder.dart:46:12)
#24     main (file:///home/ubuntu/dart-pad/tool/grind.dart:23:28)

what do i do? runs well on macos

Attempting to run Dart Pad on Ubuntu 18.04 is failing. Any ideas @johnpryan?

What build_runner-dependent packages are used in dart-pad? IIRC, there's shelf_route_generator, but I thought that was it.
Is it possible a dependency is out of date, and we could fix this with pub outdated and some edits?

Yeah I would like to see if pub upgrade fixes it.

@johnpryan  didn't work. though does grinder has internal timeout system for the build time? that running it on aws ec2 micro throws that error, but bumping the instance size to medium, now it works. odd...

It's going to require 4 gig of ram for the Dart compiler to work correctly. Without sufficient RAM, things go sideways.

is it by design? then how could dart be used for micro services, etc..? (i know its not the right place to ask but ..)

Compilers are memory hungry these days, especially when compiling the Flutter library.
Back in the bad old days, compilers dealt with low memory situations by doing things like requiring all functions be pre-declared before usage (hello C/C++) and requiring variables to be declared at the top of the function. Pascal was designed to be a single pass compilation to reduce memory pressure. None of these language constraints apply to modern languages, which keep everything in memory while compiling.
So, yeah, it's by design. I'm curious what you are attempting to compile in a microservice?

msa was just an example for making my point. thanks for helping me out!


Allow importers to override remote write HTTP client

This PR adds a NewClient field to remote.WriteStorage to define the function used to create a remote write client. This can allow downstream repositories using Prometheus to add extra functionality to the created HTTP clients used in the remote write queues.
The rws field of remote.Storage has been exposed as Write to give users of remote.NewStorage access to the new field.
I'm opening this in draft for now; it's not clear if this is the best approach to being able to modify the underlying HTTP client that are created for the queues.
/cc @cstyan @tomwilkie
Signed-off-by: Robert Fratto<EMAIL_ADDRESS>

Since grafana agent will become part of Prometheus, why not implementing your use case directly in Prometheus? What are we talking about?

Since grafana agent will become part of Prometheus, why not implementing your use case directly in Prometheus? What are we talking about?

Since "agent" will become part of Prometheus, why not implementing your use case directly in Prometheus? What are we talking about?

This was used for implementing SigV4 support in grafana/agent. I'm happy to contribute it upstream, though I think AWS's SDK might be considered a pretty heavy dependency for prometheus/common.

I am ok with this as is, though I do wonder if there is a nicer way to handle customization like this. External sources having to know about all of these components is not ideal, I wonder if passing in a client or providing an option pattern would be nicer?

Yeah, I'm still looking for a nicer way to do this too. In this case, it wouldn't be sufficient for me to just pass in a client directly, since I needed the name of the remote write target to conditionally change the behavior and enable SigV4.
The option pattern would be fine with me, as long as it gives a func(name string, conf *ClientConfig) (WriteClient, error) function and not just a shared client to use across all remote writes.

Since "agent" will become part of Prometheus, why not implementing your use case directly in Prometheus? What are we talking about?

This was used for implementing SigV4 support in grafana/agent. I'm happy to contribute it upstream, though I think AWS's SDK might be considered a pretty heavy dependency for prometheus/common.

I am ok with this as is, though I do wonder if there is a nicer way to handle customization like this. External sources having to know about all of these components is not ideal, I wonder if passing in a client or providing an option pattern would be nicer?

Yeah, I'm still looking for a nicer way to do this too. In this case, it wouldn't be sufficient for me to just pass in a client directly, since I needed the name of the remote write target to conditionally change the behavior and enable SigV4.
The option pattern would be fine with me, as long as it gives a func(name string, conf *ClientConfig) (WriteClient, error) function and not just a shared client to use across all remote writes.

Since "agent" will become part of Prometheus, why not implementing your use case directly in Prometheus? What are we talking about?

This was used for implementing SigV4 support in grafana/agent. I'm happy to contribute it upstream, though I think AWS's SDK might be considered a pretty heavy dependency for prometheus/common.

On the other hand, inside Prometheus, we already have the AWS SDK built-in. It seems that this would be pretty useless in common, I wonder if there is a way to have this in this repo. Would need approval of remote write maintainers ofc.

Since "agent" will become part of Prometheus, why not implementing your use case directly in Prometheus? What are we talking about?

This was used for implementing SigV4 support in grafana/agent. I'm happy to contribute it upstream, though I think AWS's SDK might be considered a pretty heavy dependency for prometheus/common.

On the other hand, inside Prometheus, we already have the AWS SDK built-in. It seems that this would be pretty useless in common, I wonder if there is a way to have this in this repo. Would need approval of remote write maintainers ofc.

It seems that this would be pretty useless in common

Keep in mind that the http config in common is used in other places too, any changes there need to make sense in not only all the places we expose HTTP config in Prometheus but also Alertmanager and the blackbox exporter. Nor would it make sense for their to be some auth options that work in some places but not others.
I'd advise against trying to support non-standard authentication methods out of the box, as basically every cloud and hosting provider has their own - in addition to the bespoke auth mechanisms that organisations come up with for their own internal use.

It seems that this would be pretty useless in common

Keep in mind that the http config in common is used in other places too, any changes there need to make sense in not only all the places we expose HTTP config in Prometheus but also Alertmanager and the blackbox exporter. Nor would it make sense for their to be some auth options that work in some places but not others.
I'd advise against trying to support non-standard authentication methods out of the box, as basically every cloud and hosting provider has their own - in addition to the bespoke auth mechanisms that organisations come up with for their own internal use.

Yes, I said useless, not useful.

Yes, I said useless, not useful.

I'm

I'm

Any opinions on merging this as is vs providing an option pattern?

Any opinions on merging this as is vs providing an option pattern?

I think we should keep this sort of thing to the simplest thing possible, and I don't think we can get much simpler than this PR.

I think we should keep this sort of thing to the simplest thing possible, and I don't think we can get much simpler than this PR.

Since we have consensus on having sigv4 directly in Prometheus, is it still needed for grafana agent?

Since we have consensus on having sigv4 directly in Prometheus, is it still needed for grafana agent?

No, we wouldn't need this once sigv4 gets merged upstream.

Closing this for now, reopen if needed.


Create OKX Kaia Explorer

Add OKX Kaia Explorer
Proposed changes

Describe your changes to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes
Please put an x in the boxes related to your change.

[x] Minor Issues and Typos
[ ] Major Content Contribution
[ ] Others

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING GUIDELINES
[x] I have read the CLA and signed by comment I have read the CLA Document and I hereby sign the CLA in first time contribute
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Related issues

Please leave the issue numbers or links related to this PR here.

Further comments
If this is a relatively large content contribution, kick off the discussion by explaining why you would suggest the content contribution, etc...

@Iris3329 Please change the file name from "OKX Kaia Explorer" to "okx-kaia-explorer.md" or something and add this file as a new entry (i.e. 'build/tools/block-explorers/okx-kaia-explorer') under 'build/tools/block-explorers/kaiascope' to the sidebars.js file.

Duplicated https://github.com/kaiachain/kaia-docs/pull/151


Issue with ResourceGroup when creating a new WebApp

Describe the bug
I am trying to create a WebApp using the CLI but I get an error 'NoneType' object has no attribute location when launching az webapp create. I guess this error happens since it is targeted the wrong ResourceGroup.
When I launch the command az webapp list I get the error ResourceGroupNotFound - Resource group <resourceGroupName> could not be found where <resourceGroupName> is not a ResourceGroup that exists in any of my Azure subscriptions. I verified this with both the web portal and the CLI command az group list.
To Reproduce

Login into my Azure account with az login,
Check my active subscriptions with az account list --output table,
Select the desired subscription from the list shown at point (2) with az account set --subscription <subscriptionName>,
Create the webapp with az webapp create --resource-group <resourceGroupName> --plan <subscriptionName> --name <appName>. I get the error 'NoneType' object has no attribute location
I check the existing web apps by executing az webapp list and I get the error ResourceGroupNotFound - Resource group <resourceGroupName> could not be found where <resourceGroupName> is not a ResourceGroup that exists in any of my Azure subscriptions

Expected behavior
I expect to have the web app correcly created in point (4) and to see the correct list of web apps in point (5). There should be a way to uniquely target the ResourceGroup as it happens for the Subscription
Environment summary
CLI version:  2.0.71 / OS version: Windows 10 / Shell Type: Powershell

Run the command with --debug flag to see what the error message is. I assume its because the RG doesn't exist or is not not in the right subscription.  you can also to try to run the command with --subscription parameter to see if that resolves this as well.

@panchagnula thanks for your help. However the issue solved itself, I still do not know why it wasn't targeting the wrong resource group, I tried again the command batch and it worked.


reset_rot still missing in latest mpv release

Hi @dfaker I use the latest self-compiled mpv, and it has the missing reset_rot in libavfilter, however mpv complaints: "Can't load unknown script: 360plugin.lua"
$ /usr/local/bin/mpv --script=360plugin.lua --script-opts=360plugin-enabled=yes  Example\ QooCam\ VR180\ unedited\ .mov\ file\ output\ from\ Camera.\ Merry\ Go\ Round\ Test..webm
Can't load unknown script: 360plugin.lua
 (+) Video --vid=1 (*) (vp9 3840x1920 29.970fps)
 (+) Audio --aid=1 --alang=eng (*) (opus 1ch 48000Hz)
AO: [coreaudio] 48000Hz mono 1ch floatp
VO: [libmpv] 3840x1920 yuv420p
AV: 00:00:00 / 00:00:11 (6%) A-V:  0.000

Close it as I forgot to compile mpv with lua support.


Allow navigating between all code libraries

It's not angular, but it's easy.
Shows all dart libs at the top. You can click on each and see the diff.

@srawlins ping? This actually allows you to navigate through all of the libraries

LGTM with one nit.


*: fix asan false positive case

What problem does this PR solve?
Issue Number: ref #5294
Problem Summary:
https://ci.pingcap.net/blue/rest/organizations/jenkins/pipelines/tiflash-sanitizer-daily/runs/486/nodes/83/steps/87/log/?start=0
[2022-08-30T19:21:23.463Z] ==10469==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffe30dca61f at pc 0x000000490b4f bp 0x7ffe30dca550 sp 0x7ffe30dca548
[2022-08-30T19:21:23.463Z] READ of size 32 at 0x7ffe30dca61f thread T0
[2022-08-30T19:21:23.463Z]     #0 0x490b4e in mem_utils::details::load_block32(void const*) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/include/common/avx2_mem_utils.h:66:12
[2022-08-30T19:21:23.463Z]     #1 0x490b4e in mem_utils::details::get_block32_cmp_eq_mask(void const*, long long vector[4] const&) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/include/common/avx2_strstr.h:34:24
[2022-08-30T19:21:23.463Z]     #2 0x490b4e in char const* mem_utils::details::avx2_strstr_impl<mem_utils::details::avx2_memchr(char const*, unsigned long, char)::'lambda'(char const*)>(char const*, char, long, mem_utils::details::avx2_memchr(char const*, unsigned long, char)::'lambda'(char const*)&&) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/include/common/avx2_strstr.h:139:21
[2022-08-30T19:21:23.463Z]     #3 0x490b4e in mem_utils::details::avx2_memchr(char const*, unsigned long, char) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/include/common/avx2_strstr.h:267:12
[2022-08-30T19:21:23.463Z]     #4 0x490b4e in mem_utils::avx2_memchr(char const*, unsigned long, char) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/src/avx2_mem_utils_impl.cpp:46:12
[2022-08-30T19:21:23.463Z]     #5 0x42ab3b in TestFunc(unsigned long) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/src/tests/gtest_mem_utils_opt.cpp:40:5
[2022-08-30T19:21:23.463Z]     #6 0x42ea67 in MemUtilsTestOPT_CompareNormal_Test::TestBody() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/libs/libcommon/src/tests/gtest_mem_utils_opt.cpp:85:9
[2022-08-30T19:21:23.464Z]     #7 0x523750 in void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2443:10
[2022-08-30T19:21:23.464Z]     #8 0x523750 in void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2479:14
[2022-08-30T19:21:23.464Z]     #9 0x4c1158 in testing::Test::Run() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2517:5
[2022-08-30T19:21:23.464Z]     #10 0x4c42e7 in testing::TestInfo::Run() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2693:11
[2022-08-30T19:21:23.464Z]     #11 0x4c585f in testing::TestCase::Run() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2811:28
[2022-08-30T19:21:23.464Z]     #12 0x4f0278 in testing::internal::UnitTestImpl::RunAllTests() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:5177:43
[2022-08-30T19:21:23.464Z]     #13 0x525e20 in bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2443:10
[2022-08-30T19:21:23.464Z]     #14 0x525e20 in bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:2479:14
[2022-08-30T19:21:23.464Z]     #15 0x4eeaf1 in testing::UnitTest::Run() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest.cc:4786:10
[2022-08-30T19:21:23.464Z]     #16 0x468f0f in RUN_ALL_TESTS() /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/include/gtest/gtest.h:2341:46
[2022-08-30T19:21:23.464Z]     #17 0x468f0f in main /home/jenkins/agent/workspace/tiflash-sanitizer-daily/tiflash/contrib/googletest/googletest/src/gtest_main.cc:36:10
[2022-08-30T19:21:23.464Z]     #18 0x7f315cadd554 in __libc_start_main (/lib64/libc.so.6+0x22554)
[2022-08-30T19:21:23.464Z]     #19 0x317ce8 in _start (/tiflash/gtests_libcommon+0x317ce8)

caused by #5658
https://github.com/pingcap/tiflash/blob/a8c8cb1e2b8f358d7c14a3009ab2e1e6684908f6/libs/libcommon/include/common/avx2_strstr.h#L130-L141

load block 32 from new aligned address may cause false positives when using AddressSanitizer because asan will provide a malloc()/free() alternative and detect memory visitation.
generally it's safe to visit address which won't cross page boundary.

What is changed and how it works?
use stl function if ADDRESS_SANITIZER is defined
verified in https://ci.pingcap.net/blue/organizations/jenkins/tiflash-sanitizer-daily/detail/tiflash-sanitizer-daily/487/pipeline
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-sanitizer-test asan

/run-all-tests

/merge

/run-all-tests

/run-all-tests

/run-integration-test

/merge

/rebuild

/merge

/rebuild

/merge

/rebuild

/run-integration-test

/run-unit-test


Variable group shared across different team projects in a same organization

Is there a way/feature to share Variable group across different team projects in a same organization?

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

ID: 4827aa99-ae62-bd63-6f2f-a87a4065ed27
Version Independent ID: c9e461ee-7f42-3503-9460-18fa3a807bbb
Content: Variable groups for Azure Pipelines and TFS - Azure Pipelines
Content Source: docs/pipelines/library/variable-groups.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

I mean that we only need to put these variable group in one place, then we can use the variable group in different team projects.

Sharing of Variable groups is on our backlog. At this point in time there is no time-line that I can share.
We know this is important for you. If you could take time and vote/suggest feature request on Developer Community, it will help us prioritize it appropriately.
For now, if you are using Azure, you can store the secrets in Azure Key Vault and use it across multiple projects

It is ridiculous that this still isn't a feature - you should not have to put ALL of your code under one project to share variables.  Octopus has had this feature for 5+ years.


Collect simulation dataset

Hi,
In the paper, you have mentioned that the training data from XA dataset is collected in simulation.
Is it possible that you can provide more information on how you collect the point cloud data with segmented index? (is the data generation source code available on github?)
Thanks

I generated the simulation scene by the bullet engine (c++). the source is available at https://github.com/naoya-chiba/visibleBinSceneMaker.
C++ is faster, more stable and more accurate, but python is easier to compile
I consider uploading a simulation code (python version), but it will take some time.
I used the C++ version in my paper from the link above.
After the simulation of each scene is over, you will get the pose matrix (4X4) of each object.

The first pose matrix is multiplied by the model point cloud of the object.
Attach an instance index (1) to each point.
The second pose matrix is multiplied by the model point cloud of the object.
Attach an instance index (2) to the new point.
....
In this way, a training data set can be generated.
PS: You can also calculate the center score in this process.

If possible, I can send you an imperfect simulation code (python version). After you modify it, please upload it to github, and then give me a link.

sure, i can try to improve the python version simulation

Thank you for your help.
I attached the code to this email.

use creat_scene.py to generate scene. you can get Rotation and
Translation of each object.
use creat_matrix_by_RT.py to get 4X4 matrix.
use make_scene_by_matrix.py to reconstructe scene with instance label
and center score.
use remove_hiden_point.py to remove the points that camera can't capture.

These files are for students to practice using the bullet physics engine,
so the code is a little bad.
If you can do some integration and modify the function and parameter naming
to make it easy to read, it would be very grateful.
waiyc @.***> 于2021年9月14日周二 下午6:16写道：

sure, i can try to improve the python version simulation
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/xyjbaal/FPCC/issues/2#issuecomment-918969490, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVALZSK3AZWBOFLGGI4YMFLUB4HH7ANCNFSM5D7NHCIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you for your help.
I upload the code to https://drive.google.com/file/d/1pEo1ILlPiefHBRHgALo1NMb0updPzjtB/view?usp=sharing

use creat_scene.py to generate scene. you can get Rotation and Translation of each object.
use creat_matrix_by_RT.py to get 4X4 matrix.
use make_scene_by_matrix.py to reconstructe scene with instance label and center score.
use remove_hiden_point.py to remove the points that camera can't capture.

These files are for students to practice using the bullet physics engine, so the code is a little bad.
If you can do some integration and modify the function and parameter naming to make it easy to read, it would be very grateful.

Thanks. I will give you an update once I complete the development.

Hi,
For generating center score, may I know how to define the max_r correctly for each item?
It is a bit confusing to me, because max_r in FPCC algorithm is # gear: 0.08 ring: 0.1  but in for data generation code the max distance is another value.
Is it based on model's maximum length? If yes, then the maximum length for gear shaft model would be around 0.4 based on the model size?

For calculating the center score, max_r is about half of the maximum length of the object. ( max_r = the maximum distance from geometric center point to the farthest point of the object).
You are right. The maximum length for gear shaft model is around 0.4, so the max_r should be 0.2.
But because the shape of the gear is a long strip, I used a relatively small r in our code.
Set max_r to 0.08 (for gear), you can get a better result than our reported results in the paper.
For better segmentation results, you can adjust R according to your parts to make the distribution of the center score more uniform, which is convenient for network learning.
Sorry to confusing you

Thank you for the explanation.
I will use 0.08 for the max_r in the data generation for now.

Hi @xyjbaal ,
I have uploaded the dataset generation environment to https://github.com/waiyc/Bin-Picking-Dataset-Generation. Please take a look and thank you for providing me the your initial code

Thank you very much.
I browsed your page, you are so great. LOL.
I added the link you provided on the project page of FPCC.
wish you great success in your studies.

Thank you. Looking forward for your next paper :)
All the best ! :+1:


Address of Pcode not correspond to Instruction

I'm trying to using FunctionManager.getReferencesTo() , HighFunction.getPcodeOps() and getDef()/getDescendants() to find Varnodes at the referencing Address, and find Pcodes using these Varnodes as Inputs.
But when I'm trying pass an Address from getReferencesTo()  to HighFunction.getPcodeOps(), it returned nothing. Is there any other way to do this, or where did I go wrong?
Below are what I found when addressing this problem:
I found this Function is so large (10000+ Nodes) .
When I decompiled this large function using headless analyzer and listed it's Pcodes, I got something like:
...
[0004730c]  ---  BRANCH (ram, 0x4e070, 1)
[0004730c]  ---  BRANCH (ram, 0x4e070, 1)
[0004732c] (unique, 0x1000353f, 4) COPY (const, 0xe05c4, 4)
[0004732c] (stack, 0xfffffffffffffb78, 4) INDIRECT (stack, 0xfffffffffffffb78, 4) , (const, 0xf42, 4)
        [0004732c] (register, 0x20, 4) CALL (ram, 0xf71c, 8) , (register, 0x2c, 4) , (unique, 0x1000353f, 4)
[0004732c] (stack, 0xfffffffffffffb7c, 4) INDIRECT (stack, 0xfffffffffffffb7c, 4) , (const, 0xf42, 4)
        [0004732c] (register, 0x20, 4) CALL (ram, 0xf71c, 8) , (register, 0x2c, 4) , (unique, 0x1000353f, 4)
...

But When try to get Pcodes using Instruction( like currentProgram.getListing().getInstructionContaining(currentAddress).getPcode() ) got
...
[00047304] (ram, 0x101708, 4) INDIRECT (ram, 0x101708, 4) , (const, 0xf10, 4) ---- 61
	 [000471b0] -----> (ram, 0x101708, 4)
	 [00047304] -----> (const, 0xf10, 4)
------------ from high function
[0004730c]  ---  BRANCH (ram, 0x4e070, 1) ---- 4
	 [0004730c] -----> (ram, 0x4e070, 1)
------------ from high function
[00047318] (register, 0x2c, 4) INT_ADD (register, 0x54, 4) , (const, 0xfffff72c, 4) ---- 19
	 [NO ADDRESS] -----> (register, 0x54, 4)
	 [00047318] -----> (const, 0xfffff72c, 4)
------------ from high function
[0004732c] (register, 0x20, 4) CALL (ram, 0xf71c, 8) , (register, 0x2c, 4) , (const, 0xe05c4, 4) ---- 7
	 [0004732c] -----> (ram, 0xf71c, 8)
	 [00047318] -----> (register, 0x2c, 4)
	 [0004732c] -----> (const, 0xe05c4, 4)
------------ from high function
[0004732c] (stack, 0xfffffffffffffb90, 1) INDIRECT (stack, 0xfffffffffffffb90, 1) , (const, 0xf42, 4) ---- 61
	 [00047050] -----> (stack, 0xfffffffffffffb90, 1)
	 [0004732c] -----> (const, 0xf42, 4)
------------ from high function
...

Seems like some Pcodes were merged during decompilation, but DecompileResult.decompileCompleted() is True.

Can you elaborate on what you are trying to do?  For example, are you trying to find places where a global variable is modified?  Are you trying to determine where values passed to a function are created?
I don't understand your second code snippet - you stated that the pcode is from the Listing, but the snippet mentions high functions (and INDIRECT ops are only found in high functions, not the listing).  Also, presumably you meant ReferenceManager and not FunctionManager?


Example deployment with snmp and snmp trap listener in k8s sending to nr

Making a quick demo service showing how to send data into NR via k8s.
Uses secrets to store account ID and API KEY.

thanks for the reviews!


Tabs: after nav.push() I have to click 2 times on the tab's icon

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X ] 3.x
I'm submitting a ...  (check one with "x")
[X ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Hello,
I have a page with tabs, the first tab has links, by clicking one on them I change the page by using
nav.push() (the tabs bar remains visible)
When i click on the first tab's icon, the first time ionic reloads exactly the same page (the one I opened with push), the second time it finally goes to the original tab.
Expected behavior:
I expect to return immediately to the right tab
Other information:
global packages:
@ionic/cli-utils : 1.4.0
Cordova CLI      : 7.0.1
Ionic CLI        : 3.4.0

local packages:
@ionic/app-scripts              : 1.3.7
@ionic/cli-plugin-cordova       : 1.4.0
@ionic/cli-plugin-ionic-angular : 1.3.1
Cordova Platforms               : android 6.1.2 browser 4.1.0
Ionic Framework                 : ionic-angular 3.5.0

System:
Node       : v7.7.1
OS         : Linux 4.10
Xcode      : not installed
ios-deploy : not installed
ios-sim    : not installed
npm        : 4.1.2

Thanks for opening an issue with us, would you mind sharing a minimal repo we can use to reproduce this issue?

I discovered the source of the problem.
When I push a page, starting from a tab, I don't want the tab I start from remains highlighted,
I think it is misleading for the user so the all tabs should be "off"
I achieved the result by the following line:
this.navCtrl.parent._tabs[0].isSelected=false;
This introduces the problem...
Can you advice for the correct way to achieve the goal, without breaking things?
Thanks!

As this seems like more of a support question I will urge that you ask this question on our forum or on our [slack channel](https://ionicworldwide.herokuapp.com/]. Thanks for using Ionic!


migrate to ghost 1.x

If you want to migrate to ghost 1.x, you'll need to update some variables.
I did not check deeply, but it seems to be okay on my blog: https://blog.ticabri.com/

Ohhh, didn't see other PR before. What's wrong with them (travis's failing).
I first checked the release.zip and did not see PR like #171 which seems not enough though.

It seems travis want a big update on 3rd-party libs' versions.


Potentially faster Matrix multiplication Implementation?

https://github.com/thismarvin/susurrus/blob/76a95ec79dc41cb0c034bd07cd2830f9f7d5f1cf/src/lib/maths/matrix.ts#L121
Look into ikj multiplication

You are currently using ijk?

(Apparently the most efficient method?)

haha didnt mean to press that