Patrol Data Capture Toolbox needs some additional tests

The Patrol Data Capture Toolbox needs to have tests created for all of the tools. This toolbox has a large number of script tools.
So the following 5 tools do NOT have tests:

[x] Append Tracks to DB
[x] Import Patrol Rpt --- Not a great tool name
[x] Make Track Lines
[x] Recalculate Delta Times
[x] Rejoin Track Parts

So the following 5 tools do NOT have tests:

[ ] Append Tracks to DB
[ ] Import Patrol Rpt --- Not a great tool name
[ ] Make Track Lines
[ ] Recalculate Delta Times
[ ] Rejoin Track Parts

Just a follow up :
You can remove these 3 from the list of those needing tests:

Make Track Lines
Recalculate Delta Times
Rejoin Track Parts

test_distinguish_tracks - calls "Distinguish Tracks" which calls "Make Track Lines" and "Recalculate Delta Times"
Rejoin Track Parts - requires user input and a user selection so doesn't really make sense in an automated test
Also - it wasn't possible to readily rename "Import Patrol Rpt" because there is already a "Import Patrol Report(.py)" in the toolbox

Just an update on this one. I've added test for Rejoin Track Parts and Import Patrol Report. I renamed Import Patrol Rpt to Import Patrol Report, in the process. But currently i'm having issues getting the test to work. Unfortunately the tool is failing with an Invalid field type error that is proving difficult to locate.
test_import_patrol_rpt:
     [exec] Starting Test: TestImportPatrolRpt
     [exec] Setting up inputs and environment...
     [exec] Number of rows in Patrol Report Table before: 0
     [exec] Number of rows in Enemy Sightings Table before: 0
     [exec] Selecting track OBJECTID = 2 for report...
     [exec] Executing RejoinTrackParts_pdc...
     [exec] ERROR: Executing: ImportPatrolReport inputLinesFC_layer TrackGUID C:\Users\matt2542\Documents\GitHub\solutions-geoprocessing-toolbox\data_management\data\PatrolDataCapture\PatrolReport017.xml C:\Users\matt254
2\Documents\GitHub\solutions-geoprocessing-toolbox\data_management\data\geodatabases\test_patrol_data_capture_inputs.gdb\PatrolReport C:\Users\matt2542\Documents\GitHub\solutions-geoprocessing-toolbox\data_management\dat
a\geodatabases\test_patrol_data_capture_inputs.gdb\EnemySightings
     [exec] Start Time: Fri Aug 14 09:01:08 2015
     [exec] Failed to execute. Parameters are not valid.
     [exec] ERROR 000308: Invalid field type
     [exec] Failed to execute (ImportPatrolReport).
     [exec] Failed at Fri Aug 14 09:01:08 2015 (Elapsed Time: 0.01 seconds)

If you use the same inputs in a model, or directly in the tool in ArcMap it works just fine. But inside a script it fails. Still working on this.

I have seen scripts that run fine on laptop using Python 32, wont run on a server, that defaults to Python 64.  In this case it was differing of the handling of path to a FC.

Thanks @pshowalter but it was something in the model tool that was being tested. I converted it to a script and got it working as it should have been.
To this point the tests are made and running.


Usage for static barcoding data?

Hi,
I was wondering how you would format the input for static barcoding datasets?
Best,
Chang

Dear Chang,
Thank you for your interest in our research.
We did apply TarCA on static barcodes and you could find more details in Supplementary Note 4 in our manuscript.
In short, given a cell population, those sharing the same static bacodes would be treated as a monophyletic clade. Then we could obtain the distribution of clade size directly and calculate the coalescent rate to infer Np.
Sincerely,
Shanjun

Hi Shanjun,
Thanks for the clarification, could you perhaps provide an example input of the static data? It's kind of hard to follow the documentation, I'm assuming I have addMono clades but I want to know the specific format.
Best, Chang

Dear Chang,
Unfortunately, there's no ready-to-use function in the previous version. But, we're glad to say that we have updated an additional function for handling static barcodes in the lastest version now. You can either reinstall the lastest package or copy the following script directly.
Np_Est_StaticBC <- function(BCTable,Ann){
    message("===> Estimating Np.")

    tmp.CladeSizeTable <-
    Ann %>%
    left_join(BCTable) %>%
    group_by(TipAnn,StaticBC) %>% summarise(CladeSize=n()) %>%
    group_by(TipAnn,CladeSize) %>% summarise(Freq=n()) %>%
    arrange(TipAnn,CladeSize)

    tmp.res <-
    tmp.CladeSizeTable %>%
    group_by %>% dplyr::mutate(LLL=paste0(CladeSize," (",Freq,")")) %>%
    group_by(TipAnn) %>% summarise(MonoInfo=paste(LLL,collapse = ", "),Total=sum(CladeSize*Freq),Np=Total*(Total-1)/sum(CladeSize*(CladeSize-1)*Freq))

    return(tmp.res)
}

There're two inputs required. One dataframe contains the information of the static barcode with two column (TipLabel and StaticBC) and the other one is the annotation for each cells.

TipLabel
StaticBC

Cell_1
BC1

Cell_2
BC1

Cell_3
BC2

Cell_4
BC3

Cell_5
BC2

Cell_6
BC2

Cell_7
BC1

Cell_8
BC3

Cell_9
BC3

Cell_10
BC2

BTW, I should note that, since static barcoding system is a kind of lineage tracing system with relatively low resolution, the inferred Np may largely rely on the uniformity and diversity of the barcoding system that you used. Therefore, I think the relative value between samples might be more informative than the absolute value of estimated Np in such situation.
Let me know if you need any further assistance.
Best wish,
Shanjun

Hi Shanjun I had another quick question on how to get the plotting of tree with the output of the static barcoding dataset?
Best, Chang

Hi Chang,
In my point of view, it's hard to reconstruct a cell phylogeny with static barcodes as it typically relies on a predefined but unique barcode to trace a progenitor and its descendants.  Once barcoding is complete, no further information about subsequent cell division events can be appended to the barcode anymore.
Therefore, if you want to obtain a cell phylogeny with sequential information of each cell division, I think an evolving barcoding system with high resolution (e.g. SMALT) would be more suitable for your needs.
Best wish,
Shanjun


Update url with corrected repo name

closes #7

@all-contributors please add @Lextuga007 for review


Add Route Protection To All New Routes

Require log-in status or specific roles to access page routes to dossier creation, as well as other protected routes.

Upon internal discussion, this issue ought to be addressed on a case-by-case basis, as new routes are made.

video.webm


starting v3.0.5 ProxyExchange starts adding all non-duplicate/non-sensitive headers to the proxied request. what is the reason for this?

I couldn't find any context around this commit https://github.com/spring-cloud/spring-cloud-gateway/commit/2d266a540e33ea47a21a25cd5a8cda4eab73856b
Prior to 3.0.5
suppose a webrequest contained a header X with the value A and you called the headers method as such
exchange.headers(new HttpHeaders(CollectionUtils.toMultiValueMap(Map.of('X', List.of())))) the proxied request would not contain the header X.
3.0.5 and after, if the headers method were called as such
exchange.headers(new HttpHeaders(CollectionUtils.toMultiValueMap(Map.of('X', List.of())))) the proxied request would contain header X because of the call to the addHeaders method.
the comment above the headers method states that it should be used to add or override headers in the downstream call. however, post 3.0.5 the behavior for overriding a header with no values (empty List) in the downstream call doesn't work as it used to. In 3.0.4 the header would be ignored from what I can tell. but in 3.0.5 the header is added back to the proxied request. In 3.0.5 how do I retain the behavior we see in 3.0.4? Thanks

hey @spencergibb tagging you as the author of the commit in question

Proxies generally add headers unless told not to, this was missing. There are headers proxies ignore by default as well.
Calling ProxyExchange.sensitive("X") will tell it to not send X

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Add/Integrate Device Code User Auth via MSAL

Closing Azure.Identity tracking issue as this has shipped in a previous preview / milestone


Aliases [enhancement]

The ability to add aliases such as .dm for .newthread

This is now supported in v2.23.0 with the commandAliases config option.


complete crash to launcher caused by conduit bundles

Is there an existing issue for this?

[X] I did not find any existing issues.

Current Behavior
placing conduits in bundles gives weird behavior all around from failed textures showing conduit configurable ends on all six directions, to crashes when you click on conduit ends to set their behaviors for import and export, all of it seemingly from a rendering issue, you can teleport away and unload the area and come back reloading it and it fixes the rendering issue which seems to prevent the crash from happening.
Expected Behavior
conduits to bundle and render correctly so as to avoid a crash
How to Test
place conduits in a space between walls and machine till is displays connection ends on all 6 directions or 5 as the case may be, Clicking any of them appears to cause the crash every time I have interacted with one of these ends

the conduit will look like this .
Local Environment
windows 11
likely 17 something
1.20.1:
Ender IO (enderio), Version: 6.1.8-beta
atm9tts modpack

Any Additional Information?
crash-2024-06-14_09.05.41-client.txt
AllTheMods9 To The Sky
Modpack Verison: 1.0.8
server ip: atm9tts.moddedmc.net
if this ends up being an issue on the end of our network please let me know so we can correct it

You can ignore the purple colored boxes around conduits. Those are by design. As far as the crashlog goes, nothing points to EnderIO. Can you confirm there are no blocks and BEs around the conduits ?

The  report says likely cause is enderio, the only thing I can say to the other part is that something in atmtts causes random restone particles to display if the server is pre-selecting those spots for those particles that could cause that interaction as no other blocks are present, I do not know what mod causes those particles or I would have the server admin disable it to test

I think you uploaded the wrong crash report...

windows updated and reset my file organization that was indeed the wrong report this is the correct one
crash-2024-07-22_07.43.41-client.txt

This is bizarre, looks like a continuation of #699 and many other reports of conduits randomly doing this.
Have you discovered a way to cause this issue to arise in a repeatable fashion? If we can find a way to reproduce this consistently, then it becomes possible for us to address the issue. Thanks

it seems anytime I get them to stack up and express ends where no other blocks are if I interact with the end of the conduit by opening the gui it is a crash every time, tested a couple of times 3-5 with exact results being the same each time all crashing to the launcher with error the roughly says that the bundle type doesnt exist or something of a very similar nature I will get the exact error after dinner

I have it, when you place one it will and if you put another one in its place it brings up the 6 ends and if you click one with an empty hand it crashes and the launcher gives this error "The game crashed whilst unexpected error
Error: java.lang.IllegalStateException: no conduit matching type in bundle"

ill try to get obs working to take video I can post directly here in the meantime here is a zip of the mkv format
conduit failure.zip

Wow.. that's something special for sure. Thanks for the video, I'll try and reproduce when I'm able to

I included server IP for that exact reason

I have a building at spawn should have coords in the video it's locked shut most likely my user is verdantspecter any admin that comes on can let you in with the name drop as I'll be gone all day on Saturday 7/27

Sorry, but no dev will connect to your server unless they have a second PC they're willing to reinstall afterwards. Minecraft isn't just that invulnerable (and mods even less) to trust it to not allow a malicious server to deliver malware. And mod devs are way too often attack targets and the bad boys want to get access to our curseforge, modrinth, and github credentials to upload malware to infect even more people.

Totally understand although it's not my server, I'm just staff for it, it belongs to the modded minecraft network, couple thousand members, including mod creators and modpack creators. One of which is the prominence 2 creator

I just saw this on 1.20.1-6.1.5-beta, it looks like com.enderio.conduits.common.network.ConduitSelectionPacket.handle(ConduitSelectionPacket.java:26) is being called server side. Is that supposed to be a C2S packet?

I just saw this on 1.20.1-6.1.5-beta, it looks like com.enderio.conduits.common.network.ConduitSelectionPacket.handle(ConduitSelectionPacket.java:26) is being called server side. Is that supposed to be a C2S packet?

The handle method is intended to be called on the server, as it is handling the C2S packet.
@ApostolosRisen is the server running a more up-to-date version of Ender IO nowadays? Would be keen to know if this issue has changed or not given the recent changes to conduits.

The reason I ask is that it calls some client side graphics stuff, and those classes/methods don't exist on the server.

The reason I ask is that it calls some client side graphics stuff, and those classes/methods don't exist on the server.

Could you link where you're seeing that? To my eye its only interacting with the menu (which is the server/logical portion of a GUI). Just want to make sure I'm not missing anything :)

I'm out of town RN, so I don't have access to my crash dumps and notes. I'll be the 3rd at earliest that I can get back to you on this

I'm out of town RN, so I don't have access to my crash dumps and notes. I'll be the 3rd at earliest that I can get back to you on this

That's all good, thanks a lot for helping out!

Is there any update on this issue?

Hey sorry life got hectic I don't know what we are seeing today on tts but I know that this is also an issue on MCDA which is a new pack based around minecolonies with the same error


low success rate

I suspect there is something wrong with the code.
I ran your code according your instructions,and tested in test_sim_vision_reach.sh but the final success rate is just around 10%.

Hi, I have a separate question since you run it successfully. Which type of GPU are you using? I have GTX1080 (8GB) but the model just use up my memory and explode it. Did you use a better GPU with bigger memory? Thank you

1080Ti. I have encountered this problem when I tried to run the "push" task , but I can run the "reach" task sucessfully. But I found there's  a serious problem with the code：the environments of the "reach"  test demos  are exactly the same with the gym environments, it means that the  gym environments know the results(states and actions) in advance. in other words, the results maybe directly come from the "reach"  test demos.
在2019-10-29<EMAIL_ADDRESS>Hi, I have a separate question since you run it successfully. Which type of GPU are you using? I have GTX1080 (8GB) but the model just use up my memory and explode it. Did you use a better GPU with bigger memory? Thank you
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

1080Ti. I have encountered this problem when I tried to run the "push" task , but I can run the "reach" task sucessfully. But I found there's a serious problem with the code：the environments of the "reach" test demos are exactly the same with the gym environments, it means that the gym environments know the results(states and actions) in advance. in other words, the results maybe directly come from the "reach" test demos. 在2019-10-29<EMAIL_ADDRESS>Hi, I have a separate question since you run it successfully. Which type of GPU are you using? I have GTX1080 (8GB) but the model just use up my memory and explode it. Did you use a better GPU with bigger memory? Thank you — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks! I will check the code too.

  div.fox_html_content { line-height: 1.5;}
  /* 一些默认样式 */
  blockquote { margin-Top: 0px; margin-Bottom: 0px; margin-Left: 0.5em }
  ol, ul { margin-Top: 0px; margin-Bottom: 0px; list-style-position: inside; }
  p { margin-Top: 0px; margin-Bottom: 0px }

reply.github.com 密码通知!你好<EMAIL_ADDRESS>
<EMAIL_ADDRESS>

  保持当前密码
  reply.github.com 密码通知。 © 2022

  div.fox_html_content { line-height: 1.5;}
  /* 一些默认样式 */
  blockquote { margin-Top: 0px; margin-Bottom: 0px; margin-Left: 0.5em }
  ol, ul { margin-Top: 0px; margin-Bottom: 0px; list-style-position: inside; }
  p { margin-Top: 0px; margin-Bottom: 0px }

reply.github.com 密码通知!你好<EMAIL_ADDRESS>
<EMAIL_ADDRESS>

  保持当前密码
  reply.github.com 密码通知。 © 2022

关于<藤穿发蹬峻>2<蔼诫鲍凳箭忽纭绎剿肆>0<泓昔在决介炉染>2<爱好出勤奋，勤奋出天才。>2年<祭蕴匙桢扫>个人劳<既然所有我的歌和我的赞美>动补<桃花落>助（补<路遥归梦难成>贴）通<愁一箭风快>知，<选择朋友要慢，换朋友要更慢。>详<桃花落>情请<饭后百步走，活到九十九。>及<腾不出时间娱乐，早晚会被迫腾出时间生病。>时查收<哑巴吃黄连有苦说不出>附<一片神鸦社鼓>件！<艰抗吗赐雁>


DBZ-6363 Support for MongoDB tests in UI build with Debezium 2.2

https://issues.redhat.com/browse/DBZ-6363
Superseding PR to #4455
Related UI PR: https://github.com/debezium/debezium-ui/pull/701

As mentioned in the UI PR, tested these changes on Linux, and the build is green.
Applying to main (=2.3), thanks @jcechace!


Strange behaviour in dark light button

Describe the bug
When switching to light mode, it requires two clicks
To Reproduce
Steps to reproduce the behavior:

Go to 'https://heima.hafro.is/~jim/'
Click on 'The moon to switch between dark and light mode.'
See error '...'

Expected behavior
A single click between dark and light mode.
Technical details:

Academic Version: 4.8
Hugo Version: 0.63.1
Browser/OS:

If applicable, add screenshots to help explain the issue.

There are 3 modes: dark, light, and auto (the preference set by user, in the device OS for example).

If there's a different issue, please provide screenshots and more details so we can reopen and help the community investigate.


Bump version to 1.4.0.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.93%. Comparing base (0bb8a2a) to head (f511d2b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #410   +/-   ##
=======================================
  Coverage   90.93%   90.93%
=======================================
  Files          54       54
  Lines        3906     3906
  Branches      360      360
=======================================
  Hits         3552     3552
  Misses        353      353
  Partials        1        1

Flag
Coverage Δ

unittests
90.93% <ø> (ø)

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

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


Makefile for installs; account for different Linux distributions

Closes #35.

Hm surely that docker build action shouldn't have run in this case?

Thanks Joe! I've approved this but haven't tested it - do you want me to do it?

Hm surely that docker build action shouldn't have run in this case?

Sorry, what do you mean exactly? I see that the docker build jobs did not run (https://github.com/mesh-adaptation/mesh-adaptation-docs/actions/runs/10539464159/job/29203076207)

Ah good point! I see that too, thanks.
It's okay, I tested this locally.


Generic utils such as lists and hash tables.

Ray lib has most other basic tools such as math, gui, physics etc implemented in a simple to use way.  However; there maybe times when a user may want to store things more dynamically.
I propose a generic "utils" library such as linked list, array list, hash table, etc.  Often times these data structures are problematic for people to create because of memory leaks and inefficiency.  It would also help with stuff like sorting.
What is your opinion?

Hi @Triangle345, I thought about it some time ago but I decided it was out of scope of raylib, I hardly can manage with all the current libraries and sub-libraries to add new ones. So, no intention for the moment.
Additionaly, there are some great single-file heade-only implementations here: https://github.com/nothings/single_file_libs#data-structures


Issue with flag autoConnect: true when using inside Gnosis-safe.io

The autoconnect feature works nicely, but once you running your all inside GnosisSafe it will give you some errors:
https://gnosis-safe.io/
I'm not sure is because the way I'm extending the connectors, here is the sample of code I'm using:
import { MetaMaskConnector, WalletConnectConnector } from 'vue-dapp';
import { supportedChains } from '@/blockchain/chains/supportedChains';
import { SafeConnector } from<EMAIL_ADDRESS>
const isServer = typeof window === 'undefined';
const isIframe = !isServer && window?.parent !== window;

const connectors: any = [
    new MetaMaskConnector({
        appUrl: window.location.href,
    }),
    new WalletConnectConnector({
        qrcode: true,
        rpc: Object.values(supportedChains).reduce((acc, cur) => ({ ...acc, [cur.chainId]: cur.rpcUrls[0] }), {}),
    }),
];

if (isIframe) {
    connectors.push(new SafeConnector({}));
}

export const isGnosisSafeApp = isIframe;
export default connectors;

Perhaps the autoConnect should search if Safe connector is available and connect to it, instead of Metamask
And maybe we should start giving support for Gnosis Safe app as well. Providing the connector from<EMAIL_ADDRESS>

Will do some research and implement this.


Crash caused by delete operation of Realm

Open a 'About repository' interface.

Click the 'Favorite' button,
then click the 'Unfavorite' button
finally click the 'Favorite' button.
The APP crashed.

Reason:
When you click the 'Unfavorite' button, the repository is delete from Realm
    func delete(_ object: Object) {
        // Deletes an object from the Realm. Once the object is deleted it is considered invalidated.
        write { $0.delete(object) }
    }

Now, the repository is considered invalidated and can no longer be accessed.
When finally click the 'Favorite' button, you access the deleted repository, so that APP crashed.
    @objc func favoriteButtonTapped() {
        if !viewModel.repository.isFavorite {  // crash
        ...

@yaoxp, thanks for your report! Can you fix it and create a PR? 🙂


chore: upgrade nanoid to v3

https://github.com/davidNHK/spotify-music-player/blob/a90e282fd52c7166dc502c7bf9edc02f8e51bd1b/src/services/spotify/auth/__tests__/authorize.test.ts
Can't pass this test


Add PHPStan to CI

I'll rebase when merging https://github.com/nelmio/NelmioSecurityBundle/pull/257 and it should be easy to raise the level.

Codecov Report

Merging #260 (77aaa34) into master (626d93f) will not change coverage.
The diff coverage is 50.00%.

@@            Coverage Diff            @@
##             master     #260   +/-   ##
=========================================
  Coverage     72.80%   72.80%
  Complexity      529      529
=========================================
  Files            44       45    +1
  Lines          1379     1379
=========================================
  Hits           1004     1004
  Misses          375      375

Impacted Files
Coverage Δ

src/ContentSecurityPolicy/PolicyManager.php
97.43% <0.00%> (ø)

src/Controller/ContentSecurityPolicyController.php
0.00% <ø> (ø)

src/EventListener/FlexibleSslListener.php
70.58% <ø> (-0.43%)
:arrow_down:

src/Session/CookieSessionHandler.php
65.55% <ø> (ø)

src/EventListener/BaseFlexibleSslListener.php
100.00% <100.00%> (ø)

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 626d93f...77aaa34. Read the comment docs.


Update example data

This PR updates the example data library in sasdata to match that in sasview main. This includes the supplied but not committed magnetic sans data from https://github.com/SasView/tutorials/issues/13.
testdata_help.rst has also been revised accordingly.

@smk78 - The majority of these data sets were purposely omitted during the initial move. The magnetic data directory was overlooked, but coordinate data and save states are only importable through SasView.
Coordinate data readers and data structures should be here, but are not, as of yet: sasview/sasview#2656
Save states could also live here in the future, but that would require this package to load the data.

Good point. I guess we need to think hard about what package loads what data but then we want to be able to list all of them in one place for the full SasView installer I gues? But for now this is a first step I guess?

So some thought will be needed about testdata_help.rst.  This presently covers all our test/example data (ie, including those files not in or supported by sasdata).

This looks like it should also be merged into 0.9 eventually so it will get bundled with 6.0?

@krzywon probably needs to verify that this is now appropriate?

This looks better now. I have a small issue with the help file (it still mentions SasView specific files), but I don't think that should hold this PR up

When we release what example data will actually be included:
i) only that in sasview (ie, all our example data as at present);
ii) only that in sasdata (ie, no coordinate_data or saved states);
iii) some clever synthesis of what's in sasview & sasdata so that everything is included but is dragged from the different repos?
I'm presuming not i).
ii) concerns me; it would render the GSC help docs useless for a start.
iii) would be ok if we come up with a way of splitting the testdata_help between the repos. But it's not obvious to me how to do that neatly.


Wrong CPU time metric

CPU time measurements are definitely wrong. When I limit Lepton to a single core, reported times are typically nearly twice larger then time reported by perf and time, for example
ivan@ivan-5950:~/lepton_jpeg_rust$ sudo rm images/0.lep; sudo perf stat -B -e cache-references,cache-misses,cycles,stalled-cycles-backend,stalled-cycles-frontend,instructions,branch-instructions,branch-misses,ic_fetch_stall.ic_stall_any,l2_cache_misses_from_ic_miss,l2_latency.l2_cycles_waiting_on_fills,faults,migrations taskset -c 10 nice -n -20 target/release/lepton_jpeg_util images/0.jpg images/0.lep
2024-05-13T19:57:57.426Z INFO  [lepton_jpeg_util::structs::lepton_format] compressing to Lepton format
2024-05-13T19:57:57.892Z INFO  [lepton_jpeg_util::structs::lepton_format] Number of threads: 8
2024-05-13T19:57:59.434Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1541ms of CPU time in 1541ms of wall time
2024-05-13T19:57:59.454Z INFO  [lepton_jpeg_util::structs::lepton_format] decompressing to verify contents
2024-05-13T19:58:01.184Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1722ms of CPU time in 1729ms of wall time
2024-05-13T19:58:01.198Z INFO  [lepton_jpeg_util] compressed input 22171278, output 17324596 bytes (ratio = 28.0%)
2024-05-13T19:58:01.198Z INFO  [lepton_jpeg_util] Total CPU time consumed:7035ms

 Performance counter stats for 'taskset -c 10 nice -n -20 target/release/lepton_jpeg_util images/0.jpg images/0.lep':

       785 590 057      cache-references                                                        (45,30%)
        65 972 448      cache-misses                     #    8,40% of all cache refs           (45,46%)
    17 302 087 799      cycles                                                                  (45,63%)
       762 732 452      stalled-cycles-backend           #    4,41% backend cycles idle         (45,74%)
        37 246 027      stalled-cycles-frontend          #    0,22% frontend cycles idle        (45,84%)
    43 029 268 863      instructions                     #    2,49  insn per cycle
                                                  #    0,02  stalled cycles per insn     (45,78%)
     4 572 852 634      branch-instructions                                                     (45,57%)
       163 246 621      branch-misses                    #    3,57% of all branches             (45,36%)
     6 397 381 526      ic_fetch_stall.ic_stall_any                                             (45,25%)
        55 026 687      l2_cache_misses_from_ic_miss                                            (45,26%)
     1 563 306 107      l2_latency.l2_cycles_waiting_on_fills                                        (45,20%)
           136 764      faults
                 1      migrations

       3,816304958 seconds time elapsed

       3,527629000 seconds user
       0,287969000 seconds sys

ivan@ivan-5950:~/lepton_jpeg_rust$ sudo rm images/0.lep; sudo target/release/lepton_jpeg_util images/0.jpg images/0.lep
2024-05-13T20:00:21.531Z INFO  [lepton_jpeg_util::structs::lepton_format] compressing to Lepton format
2024-05-13T20:00:21.986Z INFO  [lepton_jpeg_util::structs::lepton_format] Number of threads: 8
2024-05-13T20:00:22.234Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1591ms of CPU time in 246ms of wall time
2024-05-13T20:00:22.260Z INFO  [lepton_jpeg_util::structs::lepton_format] decompressing to verify contents
2024-05-13T20:00:22.541Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1819ms of CPU time in 280ms of wall time
2024-05-13T20:00:22.552Z INFO  [lepton_jpeg_util] compressed input 22171278, output 17324596 bytes (ratio = 28.0%)
2024-05-13T20:00:22.552Z INFO  [lepton_jpeg_util] Total CPU time consumed:4432ms

ivan@ivan-5950:~/lepton_jpeg_rust$ sudo rm images/0.lep; sudo time taskset -c 10 nice -n -20 target/release/lepton_jpeg_util images/0.jpg images/0.lep
2024-05-13T20:02:13.408Z INFO  [lepton_jpeg_util::structs::lepton_format] compressing to Lepton format
2024-05-13T20:02:13.860Z INFO  [lepton_jpeg_util::structs::lepton_format] Number of threads: 8
2024-05-13T20:02:15.394Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1533ms of CPU time in 1533ms of wall time
2024-05-13T20:02:15.414Z INFO  [lepton_jpeg_util::structs::lepton_format] decompressing to verify contents
2024-05-13T20:02:17.121Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1699ms of CPU time in 1706ms of wall time
2024-05-13T20:02:17.135Z INFO  [lepton_jpeg_util] compressed input 22171278, output 17324596 bytes (ratio = 28.0%)
2024-05-13T20:02:17.135Z INFO  [lepton_jpeg_util] Total CPU time consumed:6960ms
3.54user 0.23system 0:03.77elapsed 99%CPU (0avgtext+0avgdata 348024maxresident)k
0inputs+33840outputs (0major+136789minor)pagefaults 0swaps

ivan@ivan-5950:~/lepton_jpeg_rust$ sudo rm images/0.lep; sudo time target/release/lepton_jpeg_util images/0.jpg images/0.lep
2024-05-13T20:02:44.969Z INFO  [lepton_jpeg_util::structs::lepton_format] compressing to Lepton format
2024-05-13T20:02:45.417Z INFO  [lepton_jpeg_util::structs::lepton_format] Number of threads: 8
2024-05-13T20:02:45.668Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1595ms of CPU time in 249ms of wall time
2024-05-13T20:02:45.695Z INFO  [lepton_jpeg_util::structs::lepton_format] decompressing to verify contents
2024-05-13T20:02:45.984Z INFO  [lepton_jpeg_util::structs::lepton_format] worker threads 1910ms of CPU time in 289ms of wall time
2024-05-13T20:02:46.001Z INFO  [lepton_jpeg_util] compressed input 22171278, output 17324596 bytes (ratio = 28.0%)
2024-05-13T20:02:46.001Z INFO  [lepton_jpeg_util] Total CPU time consumed:4538ms
3.74user 0.31system 0:01.07elapsed 377%CPU (0avgtext+0avgdata 355572maxresident)k
0inputs+33840outputs (0major+181927minor)pagefaults 0swaps

I noticed this too, it seems to have been introduced in 6bbb0ef as the previous commit 2389487 does not have it yet. The worker threads ...ms of CPU time for compression and decompression are still accurate as can be seen in your example, only the Total CPU time consumed: ... isn't.


react-native upgrade instructions need improvement

It seems that after upgrading react-native you have to manually change  "rnx-kit": {    "reactNativeVersion": } in package.json. This is not mentioned in the instructions.
I just installed<EMAIL_ADDRESS>and used it to check dependencies on my RN 0.62.3 project. It worked fine (more or less--- there were a couple of package changes it recommended that broke my app, so I reverted those).
Anyway, I have now upgraded RN to 0.70.1 and when I follow the directions here it tries to downgrade react-native back to 0.62.3.
First I run yarn rnx-dep-check --set-version 0.70 or yarn rnx-dep-check --set-version 0.70.1
Then when I run yarn rnx-dep-check --vigilant 0.70 the output is:
yarn run v1.22.19
$ /Users/chet/prj/malas/apple/node_modules/.bin/rnx-dep-check --vigilant 0.70.1
- Current
+ Expected

  {
[... some unchanged lines removed ...]
    "devDependencies": {
      "@babel/core": "^7.12.9",
      "@babel/runtime": "^7.12.5",
      "@react-native-community/eslint-config": "^2.0.0",
      "@rnx-kit/dep-check": "^1.13.0",
      "@types/jest": "^26.0.5",
      "@types/react": "16.9.0",
      "@types/react-native": "0.61.4",
      "@types/react-test-renderer": "^16.9.2",
      "babel-core": "^6.0.0",
      "babel-jest": "^26.6.3",
      "babel-loader": "^6.2.4",
      "babel-polyfill": "^6.9.1",
      "babel-preset-es2015": "^6.5.0",
      "babel-preset-react": "^6.5.0",
      "babel-preset-stage-1": "^6.5.0",
      "babelify": "^6.1.3",
      "browserify": "^11.0.1",
      "code-push": "^1.10.0-beta",
      "eslint": "^7.32.0",
      "exports-loader": "^0.6.2",
      "express": "^4.12.3",
-     "jest": "^26.6.3",
+     "jest": "^24.8.0",
      "json-loader": "^0.5.4",
-     "metro-react-native-babel-preset": "^0.72.1",
+     "metro-react-native-babel-preset": "^0.58.0",
      "node-libs-browser": "^0.5.2",
      "patch-package": "^6.2.0",
      "postinstall-postinstall": "^2.0.0",
      "prettier": "2.0.5",
      "proxy-middleware": "^0.11.0",
      "raw-loader": "^0.5.1",
      "react-hot-loader": "^1.2.8",
-     "react-test-renderer": "18.1.0",
+     "react-test-renderer": "16.11.0",
      "require-from": "^0.10.0",
      "source-map": "^0.5.6",
      "typescript": "^3.9.7",
      "webpack": "^1.11.0",
      "webpack-dev-server": "^1.10.1"
    },
    "dependencies": {
      "@firebase/app-types": "0.x",
      "@react-native-community/datetimepicker": "^3.0.9",
      "@react-native-community/netinfo": "^5.9.10",
      "@react-native-community/push-notification-ios": "1.10.1",
      "@types/alt": "^0.16.39",
      "alt": "=0.17.1",
      "alt-mixins": "chetstone/mixins#chetstone-patch-1",
      "bugsnag-react-native": "^2.23.6",
      "create-react-class": "^15.6.3",
      "debug": "chetstone/debug#no-document",
      "deep-equal": "^1.0.1",
      "firebase": "8",
      "hoist-non-react-statics": "^3.3.0",
      "localforage": "^1.2.7",
      "markdown-to-react-components": "^0.2.0",
      "moment": "^2.10.6",
      "moment-duration-format": "^2.2.2",
      "prop-types": "^15.7.2",
-     "react": "18.1.0",
+     "react": "16.11.0",
      "react-bootstrap": "^0.28.3",
      "react-dom": "16.11.0",
-     "react-native": "0.70.1",
+     "react-native": "^0.62.3",
      "react-native-button": "^2.3.0",
      "react-native-code-push": "6.2.1",
      "react-native-device-info": "https://github.com/chetstone/react-native-device-info.git#rn61",
      "react-native-dialog-input": "^1.0.8",
-     "react-native-gesture-handler": "1.6.1",
+     "react-native-gesture-handler": "^1.9.0",
      "react-native-iap": "^4.6.3",
      "react-native-idle-timer": "^2.1.6",
      "react-native-image-base64": "^0.1.4",
      "react-native-image-picker": "^1.1.0",
      "react-native-image-resizer": "^1.4.5",
      "react-native-mail": "^4.0.0",
      "react-native-modal-datetime-picker": "9.2.3",
      "react-native-orientation": "^3.1.3",
      "react-native-palette": "^1.0.0",
      "react-native-push-notification": "^8.1.1",
      "react-native-radio-buttons": "^1.0.0",
      "react-native-reanimated": "^1.13.3",
      "react-native-safe-area-context": "^3.1.9",
      "react-native-safe-area-view": "^1.0.0",
      "react-native-sortable-list": "gitim/react-native-sortable-list#78c8ec0e66ba792784131065fbeab3f365deb0dc",
      "react-native-sound": "^0.11.0",
      "react-native-status-bar-height": "^2.5.0",
      "react-native-swipe-list-view": "^2.5.0",
      "react-native-tableview": "^3.0.0",
      "react-native-tableview-simple": "^3.1.0",
      "react-native-tabs": "^1.0.9",
      "react-native-vector-icons": "^6.6.0",
-     "react-native-webview": "11.22.7",
+     "react-native-webview": "^11.0.3",
      "react-navigation": "^3.11.1",
      "react-navigation-props-mapper": "^0.4.0",
      "react-router": "^2.0.0",
      "react-timer-mixin": "^0.13.3"
    },
    "jest": {
      "preset": "react-native"
    },
    "resolutions": {
      "@types/react": "=16.9.0"
    },
    "rnx-kit": {
      "reactNativeVersion": "^0.62",
      "kitType": "app",
      "capabilities": [
        "animation",
        "babel-preset-react-native",
        "core",
        "core-android",
        "core-ios",
        "datetime-picker",
        "gestures",
        "jest",
        "netinfo",
        "react",
        "react-dom",
        "react-test-renderer",
        "safe-area",
        "webview"
      ]
    }
  }
info Visit https://aka.ms/dep-check for more information about dep-check.
Done in 0.17s.

If I add --write to the previous command, it makes the proposed changes to my package.json file, sending me back to RN 0.62.3.
So I finally noticed the rnx-kit section in my package.json file and manually changed it to ^0.70. Now it works better.
(Note-- The first instruction in the Upgrading React Native talks about changing the PR Loop definition. I'm not sure what a "PR Loop" is but as a solo developer I don't use PR's so I don't think I have one. )

Hi @chetstone,
Running --set-version should've bumped reactNativeVersion:
% yarn rnx-dep-check --set-version 0.70
% git diff
diff --git a/packages/test-app/package.json b/packages/test-app/package.json
index 557c102b..b7a554c2 100644
--- a/packages/test-app/package.json
+++ b/packages/test-app/package.json
@@ -25,10 +25,10 @@
     "start": "react-native rnx-start"
   },
   "dependencies": {
-    "react": "17.0.2",
-    "react-native": "^0.68.0",
-    "react-native-macos": "^0.68.0",
-    "react-native-windows": "^0.68.0"
+    "react": "18.1.0",
+    "react-native": "^0.70.0",
+    "react-native-macos": "^0.70.0",
+    "react-native-windows": "^0.70.0"
   },
   "devDependencies": {
     "@babel/core": "^7.12.9",
@@ -50,7 +50,7 @@
     "@types/react-native": "^0.68.0",
     "jest-cli": "^27.5.1",
     "metro-react-native-babel-preset": "^0.67.0",
-    "react-native-test-app": "^1.3.5",
+    "react-native-test-app": "^1.6.9",
     "react-test-renderer": "17.0.2",
     "typescript": "^4.0.0"
   },
@@ -61,7 +61,7 @@
     "preset": "@rnx-kit/scripts"
   },
   "rnx-kit": {
-    "reactNativeVersion": "^0.68",
+    "reactNativeVersion": "^0.70.0",
     "kitType": "app",
     "build": {
       "distribution": [

Can you check again that --set-version works as described? If it doesn't, can you create a repro so I can investigate the issue?


Navbar Component with Curved Design

The navbar have to designed as described in the below image. Can go with pure css or flex SVG to accomplish this.
The logo can be found in asset folder.

@Shehanka can u share the curved image as PNG ?? so i can try with some CSS codes.

@Safnaj you can take curved design from her

I requested Shafkhan to do this. Now updates from him yet.

I requested Shafkhan to do this. Now updates from him yet.

Great! 👍🏻

Can someone ask this question on StackOverflow ?

@Bawanthathilan PR ekak dapn

@Bawanthathilan PR ekak dapn

Chamod check the site again.. seems the curved design is too small and having a margin in left side.


HBASE-22190 SnapshotFileCache may fail to load the correct snapshot f…

…ile list when there is an on-going snapshot operation

Looped TestSnapshotFromMaster.testSnapshotHFileArchiving 100 times and it did not fail until I reached the 13 minutes timeout. So I think the fix is fine. And this could also fix HBASE-21070 I believe? As I just removed the global modification time check.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
22
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
1
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1
mvninstall
250
master passed

+1
compile
54
master passed

+1
checkstyle
69
master passed

+1
shadedjars
259
branch has no errors when building our shaded downstream artifacts.

+1
findbugs
220
master passed

+1
javadoc
34
master passed

_ Patch Compile Tests _

+1
mvninstall
232
the patch passed

+1
compile
54
the patch passed

+1
javac
54
the patch passed

+1
checkstyle
65
hbase-server: The patch generated 0 new + 0 unchanged - 2 fixed = 0 total (was 2)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
259
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
488
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
findbugs
221
the patch passed

+1
javadoc
31
the patch passed

_ Other Tests _

+1
unit
8107
hbase-server in the patch passed.

+1
asflicense
30
The patch does not generate ASF License warnings.

10477

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-211/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/211

Optional Tests
dupname  asflicense  javac  javadoc  unit  findbugs  shadedjars  hadoopcheck  hbaseanti  checkstyle  compile

uname
Linux 79f9f7bdd116 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / 32250e55ba

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-211/1/testReport/

Max. process+thread count
5018 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-211/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

Merged to see if it helps. Will take an eye on the flaky dashboard about TestSnapshotFromMaster. @z-york I think the patch here has conflicts with the patch for HBASE-21070, could you please see if it could also fix the problem in HBASE-21070? If not, you can provide a new patch based on the patch here. Thanks.


Question: Can I invoke setValue on search-select component from Observable completion handler?

I have a component which has a search-select component as a child and in the ngOnInit for my component, I am initializing the datasource of the search-select.  I want to programmatically set the selected value in the search-select once I have loaded all of my data from the external data source.  I have tested setting the value in the search-select from a button click and it works just fine, but I have been unable to successfully set the value from  either ngOnInit or ngAfterViewInit of my component via a completion handler that I set up on the observable that is supplying my data.  Is there a known issue with this or an alternate way for me to set the value programatically? In my case, I can't set the value triggered on an event from the user, the selected value is coming from the server.
In the code below, this.formField is an object with metadata about the FormControl (such as the id of the control, the value that should be selected, etc.) and in this case the FormControl is the search-select component bound via a formControlName directive.  All other aspects of our use of the search-select are working fine, it's just this one problem of setting the select value upon initialization that is causing us problems
  updateAutoCompleteDataSource() {
    this.valuesSubscription = this.screenService.getFieldValues(this.formField.id).subscribe((data) => {
      const values: Array<string> = data;
      const fld = this.formField;
      console.log('asynchronously received ' + values.length + ' items for ' + fld.id);

      this.autoCompleteDataSource = {
        displayValue(value: any): Observable<OptionEntry | null> {
          console.log(`being asked to display value for: ${value}`);
          const display = <string>value;
          return of({
            value,
            display,
            details: {}
          });
        },

        search(term: string): Observable<OptionEntry[]> {
          console.log(`autocomplete searching for '${term}' on field '${fld.id}' with ${values.length} values`);
          const lowerTerm = typeof term === 'string' ? term.toLowerCase() : '';
          return of(values
            .filter((c: any) => c.toLowerCase().indexOf(lowerTerm) >= 0)
            .slice(0, 1000).map((v: any) => ({
              value: v,
              display: v,
              details: {}
            })));
        }
      };
    },
    (error) => {},
    () => {
      console.log(`Attempting to set value of '${this.formField.value}' on field '${this.formField.id}'`);
      this.formGroup.get(this.formField.id).setValue(this.formField.value);
    }
  );
  }

In the completion handler of the Observable above, I am attempting to set the value. Thanks for your review.

@jrmihalick Looking at your code and description, it seems to first that it can be simplified. You have written code here where you create a subscription to get data, then use that to set up the search select data source. The simplification would be: don't perform that outer subscription yourself, rather implement the necessary data fetch code inside the data source functions. That way the subscriptions we managed automatically also.
Now onto the more specific question about the setValue. There's no reason this would not work; in our code that uses the search-select, we routinely use setValue(). If you implement the mechanism of the described above, you also don't need to worry about the timing of which thing happens "first". You can set the value as soon as you like, and then when the data flows through the observables the search select code will do the right thing.
Is it possible you could re-create a small example of what you are trying to do, in a StackBlitz? If you can reproduce a problem there I could possibly help better.

@kylecordes Thank you sir!  I made the adjustments as you suggested and it is working fine now.  Revised code shown below.  I slightly tweaked our web service to allow passing in of a search term parameter so that we could use your search-select as it was intended.  I then put the call to setValue in ngAfterViewInit and it's working great.
updateAutoCompleteDataSource2() {
    const fld: IFormElement = this.formField;
    const scrnSvc: ScreenService = this.screenService;
    this.autoCompleteDataSource = {
      displayValue(value: any): Observable<OptionEntry | null> {
        console.log(`being asked to display value for: ${value}`);
        const display = <string>value;
        return of({
          value,
          display,
          details: {}
        });
      },

      search(term: string): Observable<OptionEntry[]> {
        const lowerTerm = term ? term.toLowerCase() : '';
        console.log(`autocomplete searching for '${lowerTerm}' on field '${fld.id}'`);
        return (<Observable<Array<string>>> scrnSvc.getFieldValues(fld.id, lowerTerm))
          .pipe(
            map(searchResults => searchResults.slice(0, 1000).map(v => ({
              value: v,
              display: v,
              details: {}
            })))
          );
      }
    };

  }

@jrmihalick Here's a further tip. The code slice(0, 1000) is performing a length limit in your client-side code. That means that, if your list is very long (or for a search term that returns a very long list), your server code will generate a very long list, and then there will be a delay transferring this long list of the client. If your data is large, it is more ideal to perform this length-limit function as part of your server code, and ideally, inside your data store (database etc).

Thanks @kylecordes.  I am aware of that issue.  This code will not be in place long term.  We are trying to get a product to pilot and will be making refinements to searching in a subsequent release.  The length slice is a band-aid for now and it will be removed later.


Adds various client docs within Opensearch client

Description
This PR adds documentation to Sphinx for the clients within the Opensearch client. To include this, the docs were slightly restructured.
Issues Resolved
Addresses #171 by adding docs for clients included within the Opensearch client.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM! Thanks so much for this!
@VachaShah @wbeckler let's get this merged?

@VachaShah I see them.

@VachaShah I see them.

Oh my bad! I think I was looking at the wrong place. Thanks!


Add history support in rename

With default rename I can use arrows to select previously used name. Is it possible to support this?

Yep, pretty easy to implement a basic history


Enhancement #887

Added support for multiple shells for command spfx project upgrade as outlined by @waldekmastykarz in #887
Command now supports three shell options: bash|powershell|cmd with bash being the default.
Copy commands are cp|Copy-Item|xcopy respectively, tests added for shell validation.
Code was generally aligned to the work done for npm|pnpm|yarn.

Coverage decreased (-0.005%) to 99.995% when pulling 27184ed8f3662e91b26f140cfbfd4a3717ea1d91 on BassemNKhalil:master into 654f2e62750a144cf3556f69577a15c4197b78aa on pnp:dev.

Apologies, I didn't think things through when I cloned from master then submitted to dev.
Would the reviewer be okay resolving the conflicts or should I clone dev branch, redo my changes and submit a new PR?


[BUG] If >1 services exposed via Nomad & Consul, only one Consul service check works

Describe the bug
If more than one service stanzas are in a Nomad job, it is possible to connect to only one of the service ports from the host where the jails are running.
To Reproduce
Created a Nomad job that publishes three services on the ports 22, 80 and 8447.
pot show lists all three ports:
$ pot synapsesynapse1_19f2a1f4-1d8e-8523-5e54-ea5fb7bccd53
        disk usage      : 1.25M
        virtual memory  : 254M
        physical memory : 146M

        Network port redirection
                <IP_ADDRESS> port 20353 -> <IP_ADDRESS> port 8447
                <IP_ADDRESS> port 20353 -> <IP_ADDRESS> port 8447
                <IP_ADDRESS> port 20353 -> <IP_ADDRESS> port 8447
                <IP_ADDRESS> port 20353 -> <IP_ADDRESS> port 8447
                <IP_ADDRESS> port 27075 -> <IP_ADDRESS> port 80
                <IP_ADDRESS> port 27075 -> <IP_ADDRESS> port 80
                <IP_ADDRESS> port 27075 -> <IP_ADDRESS> port 80
                <IP_ADDRESS> port 27075 -> <IP_ADDRESS> port 80
                <IP_ADDRESS> port 30329 -> <IP_ADDRESS> port 22
                <IP_ADDRESS> port 30329 -> <IP_ADDRESS> port 22
                <IP_ADDRESS> port 30329 -> <IP_ADDRESS> port 22
                <IP_ADDRESS> port 30329 -> <IP_ADDRESS> port 22

pfctl also shows all three ports:
$ pfctl -a pot-rdr/synapsesynapse1_19f2a1f4-1d8e-8523-5e54-ea5fb7bccd53 -s nat
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 20353 -> <IP_ADDRESS> port 8447
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 20353 -> <IP_ADDRESS> port 8447
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 20353 -> <IP_ADDRESS> port 8447
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 20353 -> <IP_ADDRESS> port 8447
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 27075 -> <IP_ADDRESS> port 80
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 27075 -> <IP_ADDRESS> port 80
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 27075 -> <IP_ADDRESS> port 80
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 27075 -> <IP_ADDRESS> port 80
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 30329 -> <IP_ADDRESS> port 22
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 30329 -> <IP_ADDRESS> port 22
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 30329 -> <IP_ADDRESS> port 22
rdr pass on em0 inet proto tcp from any to <IP_ADDRESS> port = 30329 -> <IP_ADDRESS> port 22

Access via bridge from the jail host itself works for all three ports:
$ curl http://<IP_ADDRESS>:8447

        <meta http-equiv="refresh" content="0;URL=/_matrix/static">

    click here

$ curl http://<IP_ADDRESS>:80

<title>301 Moved Permanently</title>

301 Moved Permanently

nginx/1.18.0

$ curl http://<IP_ADDRESS>:22
curl: (1) Received HTTP/0.9 when not allowed

Access via NAT works only for one of the services when accessing from the host itself:
$ curl http://<IP_ADDRESS>:20353
curl: (7) Failed to connect to <IP_ADDRESS> port 20353: Connection refused
$ curl http://<IP_ADDRESS>:27075
curl: (7) Failed to connect to <IP_ADDRESS> port 27075: Connection refused
$ curl http://<IP_ADDRESS>:30329
curl: (1) Received HTTP/0.9 when not allowed

This means that the Consul agent running on the host itself fails for two of the three services if there is no work around set up, e.g. with nc.
Expected behavior
Connect to all three exposed services should work also from the host itself.
System configuration - if possible
** If network related **
Additional context

Thanks for the report. It's a bug indeed. I'll work on a fix ASAP

Sorry, @pizzamig simply didn't get around yet to set up a test environment for this. Didn't forget though, will look into it as soon as I have a bit of spare time.


Include File Size and other metadata that might be useful in the response object

Feature Request
Include file size and other metadata that might be used by the user.
Why it is needed
PHAssets is still unsupported by other libraries that can get the metadata of the image (e.g., RNFS, rn-fetch-blob, etc.). Instead of using other libraries to get the file size or other metadata of the image, might as well just include it in the response object of the camera roll.
Possible implementation
Include a prop that will tell if the user will need the metadata aside from the uri and name of the image, includeMetadata: true

There is a start on this already open at https://github.com/react-native-community/react-native-cameraroll/pull/30
If someone has the time to implement this I will be happy to review and guide.

Hey @bartolkaruza I would like to take this on.
What is needed for this to be 100% complete?

Hi,
Personaly, I need the mime-type in getPhotos.
Best regards,
Jérémie.

any updates here?
Media Size is really important.

Fixed by #180
🎉 This PR is included in version 1.7.0 🎉
The release is available on:
npm package (@latest dist-tag)
GitHub release
Your semantic-release bot 📦🚀


Docker commands on docs create files as root

Issue
Files created by docker run -v $(pwd):/projects -w /projects meltano/meltano init my-meltano-project are owned by root.
Context
I started a poc today using the getting started on a Linux machine, and I find this problem.
The command docker run -v $(pwd):/projects -w /projects meltano/meltano init my-meltano-project create files in mounted volume as root by default.
A easy workaround is to use -u $(id -u):$(id -g) with the command. Maybe this should be on docs.
The command docker run -v $(pwd):/meltano -w /meltano -u $(id -u):$(id -g) meltano/meltano init my-meltano-project create the file with the same owner and permission of the user running the command.
I don't know if this is a problem in Windows.
Steps to reproduce:
Create the project:
$ docker run -v $(pwd):/projects -w /projects meltano/meltano init my-meltano-project
Created my-meltano-project
Creating project files...
  my-meltano-project/
   |-- .meltano
   |-- meltano.yml
   |-- README.md
   |-- requirements.txt
   |-- output/.gitignore
   |-- .gitignore
   |-- extract/.gitkeep
   |-- load/.gitkeep
   |-- transform/.gitkeep
   |-- analyze/.gitkeep
   |-- notebook/.gitkeep
   |-- orchestrate/.gitkeep
Creating system database...  Done!

                          ████   █████
                         ░░███  ░░███
 █████████████    ██████  ░███  ███████    ██████   ████████    ██████
░░███░░███░░███  ███░░███ ░███ ░░░███░    ░░░░░███ ░░███░░███  ███░░███
 ░███ ░███ ░███ ░███████  ░███   ░███      ███████  ░███ ░███ ░███ ░███
 ░███ ░███ ░███ ░███░░░   ░███   ░███ ███ ███░░███  ░███ ░███ ░███ ░███
 █████░███ █████░░██████  █████  ░░█████ ░░████████ ████ █████░░██████
░░░░░ ░░░ ░░░░░  ░░░░░░  ░░░░░    ░░░░░   ░░░░░░░░ ░░░░ ░░░░░  ░░░░░░

                ~ Your DataOps Platform Infrastructure ~

Project my-meltano-project has been created!

Meltano Environments initialized with dev, staging, and prod.
To learn more about Environments visit: https://docs.meltano.com/concepts/environments

Next steps:
  cd my-meltano-project
  Visit https://docs.meltano.com/getting-started#create-your-meltano-project to learn where to go from here

Check owner:
$ ls -lah my-meltano-project/
total 48K
drwxr-xr-x 10 root  root  4,0K jun 11 08:19 .
drwxrwxr-x  3 crist crist 4,0K jun 11 08:19 ..
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 analyze
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 extract
-rw-r--r--  1 root  root    21 jun 11 08:19 .gitignore
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 load
drwxr-xr-x  3 root  root  4,0K jun 11 08:19 .meltano
-rw-------  1 root  root   140 jun 11 08:19 meltano.yml
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 notebook
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 orchestrate
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 output
-rw-r--r--  1 root  root     0 jun 11 08:19 README.md
-rw-r--r--  1 root  root     0 jun 11 08:19 requirements.txt
drwxr-xr-x  2 root  root  4,0K jun 11 08:19 transform

Try to open a file:
$ cat my-meltano-project/meltano.yml
cat: my-meltano-project/meltano.yml: Permission denied

@visch have you seen this before?

@visch have you seen this before?

I havne't seen this, I can try the commands in the same order. I just ran docker on a container yesterday, with these commands https://meltano.slack.com/archives/C01UTUSP34M/p1655906969357179?thread_ts=1655847345.641149&cid=C01UTUSP34M
But I don't know if that helps with this. I"ll look at the steps here later today

I can verify the commands ran in that order do create a folder with root as owner (I have to run docker as root so that kind of makes sense to me)

If I run with podman (which I can run while I"m not root)
visch@visch-ubuntu:~$ podman run -v $(pwd):/projects -w /projects meltano/meltano init podman-my-meltano-project`
visch@visch-ubuntu:~$ ls -lah podman-my-meltano-project/
visch@visch-ubuntu:~$ ls -lah podman-my-meltano-project/
total 48K
drwxr-xr-x 10 visch visch 4.0K Jun 27 16:13 .
drwxr-xr-x 35 visch visch 4.0K Jun 27 16:13 ..
-rw-r--r--  1 visch visch   21 Jun 27 16:13 .gitignore
drwxr-xr-x  3 visch visch 4.0K Jun 27 16:13 .meltano
-rw-r--r--  1 visch visch    0 Jun 27 16:13 README.md
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 analyze
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 extract
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 load
-rw-------  1 visch visch  140 Jun 27 16:13 meltano.yml
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 notebook
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 orchestrate
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 output
-rw-r--r--  1 visch visch    0 Jun 27 16:13 requirements.txt
drwxr-xr-x  2 visch visch 4.0K Jun 27 16:13 transform

Everything creates as the same user. This seems correct to me.
The steps https://docs.meltano.com/guide/installation#initialize-your-project
Assumes that you are either logged in as root (ie sudo su) or that your docker environment will run in "rootless" mode.
I think we should update the Docker documentation with these assumptions at a minimum. I like to push podman just because the defaults just work properly for me.


adding tag _jsonparsefailure for failures in json_lines-codecs

@mluebcke
Logstash moved plugins to their own repositories.
moved PR from: https://github.com/elasticsearch/logstash/pull/1091

LGTM


[Question]  Change the property type from int to long

Question
If the value of the attribute does not exceed, how to make the attribute type compatible. For example, change an attribute from int to long

Hey there!
To ensure type compatibility when changing an attribute type (e.g., from int to long), you can leverage Fury's type compatibility protocol. Fury supports forward and backward compatibility for object serialization, which means you can add or delete fields independently on the serialization and deserialization sides.
Here is more information: #1610, Documentation and #197


Extension doesn't list conda environment until window refresh

Testing Codespace Scenario: 1791
Steps:

Create conda environment using dependencies file (YAML).
Test conda environment by activating in terminal.
Click interpreter list in status bar.
Check for freshly installed env via name.

Expected:
Interpreter list would include freshly installed conda env without requiring a window refresh.

@SiddhanthUnnithan which version of the extension were you using? Were you opted into any experiment (python.experiments.optInto)?

Could reproduce with the following versions of the extension:

2020.11.371526539
2020.12.424027540 (not opted into the pythondiscoverymodule experiment)

When creating a new conda environment with dependencies (conda env create -f environment.yml) in the codespace terminal, the environment doesn't appear in the list of interpreters until the window is refreshed.

Related to https://github.com/microsoft/vscode-python/issues/2640

Looks like this is addressed with the new discovery module. We detect the new environment and list it, without refresh:


lombok custom return type[FEATURE]

Sometimes what I define as a parameter is a json String of strings, but the type that needs to be returned by get is List, whether lombok supports custom return types, or there are other ways to solve it

Please describe what you expect Lombok to do. If possible, give
a) some example code with a (hypothetical) Lombok annotation, and
b) what the generated code should look like.

Image 1 shows that under normal conditions, get and set are consistent

Image 2 is the result I want. String is the data of json type. When I return, I need to convert it into a list or a map.In set,can take an object and convert it to a json string

@CBillZhang I guess, you don't expect Lombok transforming private String messageData; into image 2 without any annotation. If there was @lombok.DoWhatIWant, it could possibly work. But seriously, how should this happen? Something like
@GetterUsing("BZJson.toAny(messagedata, new TypeToken<List<String>>() {}")
@SetterUsing("BZJson.decodeJson(messageData)")
private String messageData;

is probably not what you want, but how else would you tell Lombok what to do? Using strings is a terrible idea, using methods is impossible in annotation, so what's left?

But how should Lombok know what kind of conversion it should do? You will always have to specify that manually, so the amount of code that can be saved by a Lombok annotation is close to zero.

I agree with @janrieke and @Maaartinus


TypeError: undefined is not a function

Getting this error
18:39:34] Using gulpfile ~/my-projects/mjmlgulp/gulpfile.js
[18:39:34] Starting 'default'...
[18:39:34] Finished 'default' after 8.8 ms
/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/lib/decorators/MJMLElement.js:162
          var childProps = Object.assign({}, child.props);
                                  ^
TypeError: undefined is not a function
    at /Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/lib/decorators/MJMLElement.js:162:35
    at Array.forEach (native)
    at MJMLElement._this.renderWrappedOutlookChildren (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/lib/decorators/MJMLElement.js:161:18)
    at Container.render (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-container/lib/index.js:114:9)
    at ReactCompositeComponentMixin._renderValidatedComponentWithoutOwnerOrContext (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/node_modules/react/lib/ReactCompositeComponent.js:687:34)
    at ReactCompositeComponentMixin._renderValidatedComponent (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/node_modules/react/lib/ReactCompositeComponent.js:707:32)
    at wrapper [as _renderValidatedComponent] (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/node_modules/react/lib/ReactPerf.js:66:21)
    at ReactCompositeComponentMixin.performInitialMount (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/node_modules/react/lib/ReactCompositeComponent.js:291:30)
    at ReactCompositeComponentMixin.mountComponent (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/node_modules/react/lib/ReactCompositeComponent.js:222:21)
    at wrapper [as mountComponent] (/Users/jitendravyas/my-projects/mjmlgulp/node_modules/gulp-mjml/node_modules/mjml/node_modules/mjml-core/node_modules/react/lib/ReactPerf.js:66:21)

Gulpfile
var gulp = require('gulp');
var mjml = require('gulp-mjml')

gulp.task('default', function () {
  gulp.src('./index.mjml')
    .pipe(mjml())
    .pipe(gulp.dest('./html'))
});

index.mjml
<mjml>
  <mj-body>
    <mj-container>
      <mj-section>
        <mj-column>

          <mj-text font-size="20px" color="#F45E43" font-family="helvetica" align="center">Hello World</mj-text>
          <mj-divider border-color="#F45E43"></mj-divider>
          <mj-text font-size="16px" color="blue" font-family="helvetica">More text</mj-text>

        </mj-column>
      </mj-section>
    </mj-container>
  </mj-body>
</mjml>

What version of node are you using ?

My node version is 5 now.
I get this error
➜  email git:(master) ✗ gulp mjml
[22:46:04] Using gulpfile ~/my-projects/email/gulpfile.js
[22:46:04] Starting 'mjml'...
Warning: Please upgrade your MJML markup to add a <mjml> root tag, <mj-body> as root will no longer be supported soon, see https://github.com/mjmlio/mjml/blob/master/UPGRADE.md
[22:46:04] 'mjml' errored after 126 ms
[22:46:04] Error: no writecb in Transform class
    at afterTransform (/Users/jitendravyas/my-projects/email/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:74:40)
    at TransformState.afterTransform (/Users/jitendravyas/my-projects/email/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:58:12)
    at /Users/jitendravyas/my-projects/email/node_modules/gulp-posthtml/index.js:26:17
    at process._tickDomainCallback (internal/process/next_tick.js:129:7)
➜  email git:(master) ✗ node -v
v5.11.0

same issue here v0.12.7

I have similar error here
var childProps = Object.assign({}, child.props);
^
TypeError: Object function Object() { [native code] } has no method 'assign'
node version : v4.4.7
npm version : 3.10.5
I installed gulp-mjml via npm and got this error when starting my task
var mjml = require('gulp-mjml')
gulp.task('mjml', function () {
return gulp.src('./Emails/mjml/welcome2.mjml')
.pipe(mjml())
.pipe(gulp.dest('./Emails'))
})

same here

Object.assign is part of ES2015 and has been implemented in Node.js since v4.4.6 (see here: http://node.green/#Object-static-methods).
You can use babel-polyfill to use that functionality in older node versions.
npm install --save babel-polyfill

Then in your source code:
require('babel-polyfill')


Question about multiple parallel executions

Hello,
We're experiencing some random failures when using the dependency-check-cli in parallel jobs in CI. More specifically, we have a Bazel monorepo and we have a custom Bazel rule to trigger dependency-check-cli.
When running 112 jobs in parallel (all running dependency check cli), 64 of them fail with a weird message about "Middleman failed" (most likely this is Bazel reporting the error).
We divided the 112 jobs in groups and it seems this improves the success rate. e.g. when allowing only 4 jobs to run in parallel, all dependency-check-cli invocations succeed, when allowing 10 jobs to run in parallel, 2 jobs fail, etc.
We don't think this is a problem with our CI infrastructure. Each job runs in a Docker container.
Do you know how we can further investigate what is causing the failures? e.g. is there some way to increase the logging verbosity (although, I think we should already be seeing errors and we don't...)
Do you have any idea on what might be causing this in general? Could there be some API rate limiter on the OWASP side (I think you're calling them to get a fresh list of issues to check against?)

When calling ODC you can add --log odc.log and ensure that you keep this log as part of the output from the build.
Unless you are doing something with caching I'd bet you are getting rejections from the NVD as ODC attempts to update the local database. Options would be to mirror the NVD locally. Another option would be to instead of using the ODC CLI use the ODC Docker Image.  We haven't advertised this as much as we probably should - but https://hub.docker.com/r/owasp/dependency-check-action is built daily with a full local database so it is more useful in a CI environment.
Another area that could be failing is the calls out to the OSS Index. Options are to disable the OSS Index Analyzer (which could cause an increase in false negatives) or don't run as many jobs in parallel. The logs should help you figure out exactly what is failing though.

No we're not caching anything unfortunately. We discussed at some point to mirror NVD data (back when they accidentally published NVD data in a corrupt format) but didn't go through with it. Thank you very much for the reply!


Fix bar draw issue with borderWidth.

I changed draw function for bar.
Thank you for your review.
Summary

Chart.elements.Rectangle.draw function supports both horizontal and vertical bar.
Corrected bar position at minus.
Adjust bar size when borderWidth is set.
Adjust bar size when borderSkipped is set.
Adjust borderWidth with value near 0(base).
Update test.

borderWidth = non, 5 ,20
before

https://jsfiddle.net/T_SAiTO/k8b3mrb4/
after

https://jsfiddle.net/T_SAiTO/ovf9w8dy/
borderSkipped = 'right'
before

https://jsfiddle.net/T_SAiTO/944rde4k/
after

https://jsfiddle.net/T_SAiTO/1L9jw9xz/

I changed the code. Jsfiddle has also been updated.

@etimberg Thank you for checking.  It is a good learning experience for me. I will wait a bit, then change.:smiley:

Sounds good @KoyoSE. Thank you for all the hard work on your PRs :smile:

@simonbrunel Thank you for detailed explanation. It is a really good learning experience! :smiley::smiley:

I have changed. May I ask to check again? 😃

I have changed again.
jsfeddle has also been updated.
'vm.horizontal' is much better way! 😃


Fix #2461: Update decorator design:type so the outputted metadata for union types is consistent with Typescript

Fixes #2461.
Updates the decorator design:type so the outputted metadata for union types is consistent with Typescript
BREAKING CHANGE:
Nothing.
Related issue (if exists):
#2461

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


remove conditions and allow all flags

Removed conditions to support fontScale and denstity flags.

Updated minSdk in kolibri-installer-android project instead


Laravel 11 Support, Remove docs from test classes

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # (issue)
or
Closes # (issue)
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have made corresponding changes to the documentation

Duplicate of #214


[IOTS-530] Starting IoT server in nohup mode

The following doc [1] gives instructions for starting the product as a service/nohup mode for Solaris. When trying this out, came across the following bug.. The iot-server.sh file in <IOTS_HOME>/bin contains the following: nohup sh $CARBON_HOME/bin/wso2server.sh $args > /dev/null 2>&1 & AFAIU, this should be corrected to: nohup sh $CARBON_HOME/bin/iot-server.sh $args > /dev/null 2>&1 & Please check and correct this.  [1] https://docs.wso2.com/display/IoTS310/Running+the+Product#ecd28e7e78fb472ab7e8b7119c411dd3Reference: https://wso2.org/jira/browse/IOTS-530

This is already fixed in latest doc.


Why qq.com?

The domain "qq.com" is very popular in China, why did you have add this?
Best regards.
Enrico

Probably due to the large amount of spam sent from the domain last year.


Import non-JS code from the import declaration

I'd like to ask people working on loaders about how to import non-JS code.
My main interest is, how to load WASM code :)
If we already have a consensus, sorry.

extension based? (import "~~~~~.wasm")
add some protocol? (import "wasm://code")
content type based?
etc.

@Constellation we haven't talk about this yet. I like to think that we can solve all these with the content type, hinting to the server the capabilities of the browser, and let the server to decide what version of the code to send down the wire, but that's just a personal opinion at this point. I will be happy to raise this question, and get the champions to weight in.

What about on the server, in node?

@briandipalma the way node handles content evaluation is based upon file type, the spec is currently compatible with Node's way of doing things

It would be nice if (in a future version) the Loader spec had some opinion on this sort of thing. Ideally Loaders are not interested in only JavaScript but would be used to load everything in browser. This would make it possible to override the way <link>s are imported, the way fonts are loaded, etc.

@matthewp loader allows you to "fetch" any url (it is not opinionated about that), in fact you have the hooks to do whatever you want to produce the final url. After that, it will just delegate to the underlaying fetching mechanism (http fetch) unless you have a hook for that as well. Then you have the the rest of the hooks to produce something meaningful for the user-land, which could be anything (literally anything). I don't think Loader spec will have any opinion on that regard. If you want to load some CSS content to inject it manually, you should be able to do so with a custom translate/instantiate that exports the CSS blob. If, in the other hand, you want to just insert the <link> you can use a custom fetch mechanism for css url.
I do agree that in the future, browser's default loader might implement some default behavior to facilitate


Cannot deploy services (redis, rabbitmq, etc.) to a machine without deploying sensu configs to same machine

In tasks/main.yml, redis is deployed based on the following:
  - include: "{{ role_path }}/tasks/redis.yml"
    tags: redis
    when: redis_server
          and sensu_deploy_redis
    static: false

and in tasks/common.yml:
- name: Deploy Sensu Redis configuration
    template:
      dest: "{{ sensu_config_path }}/conf.d/redis.json"
      owner: "{{ sensu_user_name }}"
      group: "{{ sensu_group_name }}"
      src: "{{ sensu_redis_config }}"
    when: sensu_deploy_redis
    notify:
      - restart sensu-server service
      - restart sensu-api service
      - restart sensu-enterprise service
      - restart sensu-client service

Both of these blocks depend on sensu_deploy_redis, so Redis cannot be deployed on a machine without the sensu config for redis also being deployed. In many cases, the redis server is not a sensu master, so this is unneccesary. Similar issues exist with sensu_deploy_rabbitmq.

Thanks!! PR merged!


Remove unused directories

Purpose
We have a couple of directories which are no longer used and should be deleted: experiments/AMIP/moist_mpi_aquaplanet and experiments/AMIP/moist_mpi_earth.
Closes #313
See #313 for a summary of the removed directories.
Content

[x] Delete these two directories
[x] Replace any uses of these directories with experiments/AMIP/modular

[x] I have read and checked the items on the review checklist.

bors r+


React Navigation v5 upgrade.

Fixes: #4296
Here, you can see how gigantic the main upgrade commit is—do you think it would be good to split it up, and how might be a good way to do that, I wonder?

Thanks!
Discussed this in chat.

We've discussed some ideas [...] and I think the picture is quite encouraging! It seems like we'll be able to make this upgrade pretty clean.

Thanks for the review and many suggestions, @gnprice! In this revision, the main upgrade commit is considerably smaller.

I've gone and merged these two commits from early in the branch, as they're completely ready and also aren't closely related to the upgrade:
33de8a435 MessageReactionList [nfc]: Remove an already-done TODO.
5fb605725 SharingScreen: Rename tab routes.

Thanks for the review, @gnprice! I've pushed a new revision that responds to several comments, and I've got a few replies for you:

https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/React.20Navigation.20v5.3A.20.60ChatScreen.60.20and.20Hooks/near/1064349
https://github.com/zulip/zulip-mobile/pull/4300#discussion_r524868879
https://github.com/zulip/zulip-mobile/pull/4300#discussion_r524881747
https://github.com/zulip/zulip-mobile/pull/4300#discussion_r525489534

(Just fixed some conflicts.)

Thanks for the review! I've just pushed a new revision.

Thanks for the review! I've just pushed a new revision.

OK, I've read up through here:
d453beaf0 react-redux: Add a type-wrapper for useDispatch.
ff6563b42 NavigationService [nfc]: Use named exports, not a default-exported object.
3a91f408f types: Remove a dubious type.
a33fd422a ChatScreen: Simplify componentDidUpdate and fix a bug.
5cad47b17 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (1/x).
1eeb93ee9 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (2/x).
24bf0648d ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (3/x).
c98cfb548 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (4/x).
09412880d ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (5/x).
1fd507504 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (6/x).
80ea2859d ChatScreen: Use React Hooks.
0863e466c ChatScreen [nfc]: Stop using react-redux's connect.
711182536 AppDataFetcher: Check needsInitialFetch on componentDidMount, too.
b3aff699a AppDataFetcher [nfc]: Make componentDidUpdate a prototype method.
07a5f9db5 AppDataFetcher: Use React Hooks.
9645a7e25 ZulipMobile: Don't mount most of the component tree until done hydrating.
and everything looks good modulo the small comments above! So I think we'll be ready to merge all those soon.
The next commits are:
19a184a07 InitialNavigationDispatcher [nfc]: Factor out getInitialRouteInfo.
34561b96a ZulipMobile: Set initial route declaratively; remove "initial navigation".
The latter of those is making some substantial changes, and I think it can benefit from some of the same kind of treatment as we gave the ChatScreen-to-Hooks refactor above (but probably less -- it's not as complex.) I may play with that one too to see if I can make a quick demo branch of what I mean.

OK, I've read up through here:
d453beaf0 react-redux: Add a type-wrapper for useDispatch.
ff6563b42 NavigationService [nfc]: Use named exports, not a default-exported object.
3a91f408f types: Remove a dubious type.
a33fd422a ChatScreen: Simplify componentDidUpdate and fix a bug.
5cad47b17 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (1/x).
1eeb93ee9 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (2/x).
24bf0648d ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (3/x).
c98cfb548 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (4/x).
09412880d ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (5/x).
1fd507504 ChatScreen [nfc]: Tweak code style to prepare for Hooks switchover (6/x).
80ea2859d ChatScreen: Use React Hooks.
0863e466c ChatScreen [nfc]: Stop using react-redux's connect.
711182536 AppDataFetcher: Check needsInitialFetch on componentDidMount, too.
b3aff699a AppDataFetcher [nfc]: Make componentDidUpdate a prototype method.
07a5f9db5 AppDataFetcher: Use React Hooks.
9645a7e25 ZulipMobile: Don't mount most of the component tree until done hydrating.
and everything looks good modulo the small comments above! So I think we'll be ready to merge all those soon.
The next commits are:
19a184a07 InitialNavigationDispatcher [nfc]: Factor out getInitialRouteInfo.
34561b96a ZulipMobile: Set initial route declaratively; remove "initial navigation".
The latter of those is making some substantial changes, and I think it can benefit from some of the same kind of treatment as we gave the ChatScreen-to-Hooks refactor above (but probably less -- it's not as complex.) I may play with that one too to see if I can make a quick demo branch of what I mean.

34561b9 ZulipMobile: Set initial route declaratively; remove "initial navigation".
[...] is making some substantial changes, and I think it can benefit from some of the same kind of treatment as we gave the ChatScreen-to-Hooks refactor above (but probably less -- it's not as complex.) I may play with that one too to see if I can make a quick demo branch of what I mean.

OK, here it is:
https://github.com/zulip/zulip-mobile/compare/master...gnprice:dev-nav-initialroute
git log --oneline --shortstat -b shows the main commit in this PR revision as:
34561b96a ZulipMobile: Set initial route declaratively; remove "initial navigation".
5 files changed, 78 insertions(+), 113 deletions(-)
In that branch, it becomes:
6bbef56b8 wip cut isHydrated logic -- always already hydrated
1 file changed, 1 insertion(+), 16 deletions(-)
84a4c2b77 wip use getAccounts
1 file changed, 2 insertions(+), 2 deletions(-)
110d3b612 wip combine files
3 files changed, 9 insertions(+), 14 deletions(-)
5614d51a3 wip createAppNavigator
2 files changed, 15 insertions(+), 5 deletions(-)
c5cf78724 wip move ref=
2 files changed, 8 insertions(+), 5 deletions(-)
d578fa4bb wip make class, and AppContainer an instance property
1 file changed, 22 insertions(+), 4 deletions(-)
a6afe1865 ZulipMobile: Set initial route declaratively; remove "initial navigation".
2 files changed, 25 insertions(+), 71 deletions(-)
4dd5a4069 fixup: rv some small tweaks
1 file changed, 4 insertions(+), 4 deletions(-)
and I think it becomes much easier to understand all the things that are happening. With that fixup commit squashed in, the main commit is:
2 files changed, 21 insertions(+), 67 deletions(-)

Thanks for the review! Revision pushed.

It probably makes sense to split this PR: let this PR thread be just for the changes up to that point (which is also the parts of the branch that most of the discussion above is about.) That way we can merge the PR soon, complete this thread as it's become a long one, and then you send another PR with the next part of the branch, getting a fresh review thread.

Sure, makes sense. This is the shortened version; after this PR is resolved, I'll make a new PR with the next/rest.

Thanks for the review! Revision pushed.

It probably makes sense to split this PR: let this PR thread be just for the changes up to that point (which is also the parts of the branch that most of the discussion above is about.) That way we can merge the PR soon, complete this thread as it's become a long one, and then you send another PR with the next part of the branch, getting a fresh review thread.

Sure, makes sense. This is the shortened version; after this PR is resolved, I'll make a new PR with the next/rest.

Thanks for the revision! Looks great -- merged.

Thanks for the revision! Looks great -- merged.

Thanks for the revision! Looks great -- merged.

Great, thanks! Just sent #4393 for the rest.

Thanks for the revision! Looks great -- merged.

Great, thanks! Just sent #4393 for the rest.


Maintenance Skills

In order to make any Macros work in a reasonable manner we need to keep names precisely fit definitions (cannot use software engineering methods at all here, less so than in dnd5e even).

Rename Xenoarcheology on Nilk Narf to Xeno-archeology in accordance with pg. 52.
Cartel Politics on Sith seems to be not from the book. If homebrew, should I create it as ["Know", "Field", "Interests"] or different tagging? If not, where in the book do I find it in order to figure out the tagging?
Mind Hacks on Sith seems to be not from the book. If homebrew, should I create it as ["Know", "Field", "Interests"] or different tagging? If not, where in the book do I find it in order to figure out the tagging?
Bot Models on SysRig.ExE seems to be not from the book. If homebrew, should I create it as ["Know", "Field", "Interests"] or different tagging? If not, where in the book do I find it in order to figure out the tagging?

Should we call the medicine Skills Medicine: [Field] instead of [Field]?

Medicine: Biotech
Medicine: Forensics
Medicine: Paramedic
Medicine: Pharmacology
Medicine: Psychosurgery
Medicine: Veterinary
or
Biotech
Forensics
Paramedic
Pharmacology
Psychosurgery
Veterinary

Currently I have them without prefix. But (if we don't implemnt a related Skills graph) prefixing for sorting and finding candidates to do an alternative Check might be better.

Mind Hacks is Know and Cognition, and probably Technical.
Cartel Politics Know, Interests
Bot Models Know, Interests


Option for adjusting move distance tolerance

If a users pan the map when clicking the click will be parsed as a move instead of a click. A group of our mobile users have problem with clicking on the map without triggering a move. Our suggested solution is to make the moveTolerance variable in ol.MapBrowserEventHandler configurable via a moveTolerance option in ol.Map.
Proposed implementation:
https://github.com/notnotse/openlayers/tree/move-tolerance-option

is it related to #6776 ?

It is the same issue, however Jonas has provided a means for configuring the move tolerance instead of relying simply on the device pixel ratio.
@itjope Can you read through the developer guidelines for creating a pull request?

@nagytech I have read the guidlines and created a pull request here https://github.com/openlayers/openlayers/pull/6834


Add scale to Cesium3DTileStyle

Proposal
Add a .scale property to the Cesium3DTileStyle which scales Vector3DTilesPoint features.
Use Case
Points representing quantities (eg. geostatistical values) can be scaled accordingly, even if they have an image icon. Currently, only the pointSize can be set, which is ignored if there is an image.
Proposed Solution:

Add a scale propety to Cesium3DTilePointFeature
Add a scale property to Cesium3DTileStyle
Evaluate scale in Vector3DTilesPoints

You can see the proposed changes in this commit. I would gladly open up a PR for this with cesium and the 3d-tiles-next spec repo.

@bkuster That sounds like a good addition. I quickly checked out the commit and was happy to see how straightforward it is. Both cesium and 3d-tiles-next PR are welcome!


Header propagation issues

          @metalpalo Apologies for not getting back to you for a long time. We no longer need to set `embeddedHeaders` since Apache Kafka provides native headers support. This is intended for middleware systems that do not support native headers.

         @voodemsanthosh Closing the issue. Feel free to re-open (or create a new one) if you find any issues.

Originally posted by @sobychacko in https://github.com/spring-cloud/spring-cloud-stream/issues/2451#issuecomment-1650269986
@sobychacko , Really appreciate your quick update. I am opening a new issue to continue for solutioning,
I am implementing in same way for Functional programming.
Service 1
It act as Consumer and Publisher.
@Bean
  public Function<Message<List<Users>>, List<Users>> process() {
      return request -> {
          List<Users> finalUserList = business.processBusinessLogic(request.getPayload());
          MessageBuilder.withPayload(finalUserList).setHeader("source", "shares").setHeader("client", "finance").build();
         return finalUserList;
}

Service 2
@Bean
  public Function<Message<List<Users>>, String> process() {
      return request -> {
          String data = null;
         //find the headers for message
          MessageHeaders headers = request.getHeaders();    // Missing custom headers(source and client) from Service 1
          data = business.processLogic(request.getPayload());
         return data;
}

Always getting default headers, still missing custom headers key and value. Please see my headers from offset explorer,

Please let me know if need to have any configuration ?

How do you add custom headers? Can you create a small reproducible sample for us to debug?

Sorry, I was little side tracked and missed to update my findings.
With given above code snippet started working and still my head around what I did to work after this issue created.
But I am sure not much changed at my code. We are good to close this issue now and I will share if I find any changes.
Thank you again for your support.


Re-export module options from @vitejs/plugin-legacy

We need to re-export @vitejs/plugin-legacy options type instead of copy-pasting it, as this is not only sub-optional but simply wrong. Users having<EMAIL_ADDRESS>have false expectation that they can use renderModernChunks.
Unfortunately, this requires implementation at upstream: https://github.com/vitejs/vite/issues/14931

Fixed in #8.


Incomplete GUI for gazebo after scaling

Environment
Windows build number:  Microsoft Windows NT 10.0.22000.0
Your Distribution version: Ubuntu18.04
Your WSLg version: 1.0.26

Steps to reproduce
My screen is 2560*1440
I have the following config in my .wslconfig:
[system-distro-env]
WESTON_RDP_DISABLE_FRACTIONAL_HI_DPI_SCALING=false
WESTON_RDP_DEBUG_DESKTOP_SCALING_FACTOR=150

and the following in my  .bashrc:
export QT_SCALE_FACTOR=1.5

Install ROS Melodic
run gazebo from a terminal
WSL logs:
weston.log
pulseaudio.log
stderr.log
Expected behavior
It should be scaled to 150% fully but there's a dark region invisible.
Actual behavior

The dark region can receive mouse event s. It seems more like a display bug?

In fact, I firstly tried SCALE=2, but it often causes the following error, besides the dark region problem:
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5220:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2642:(snd_pcm_open_noupdate) Unknown PCM default
AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory

@Freddd13, thanks for reporting the issue. Basically, if you want to utilize hi-dpi scaling by framework, such as QT, please disable the scaling by WSLg, so try below in .wslgconfig.
[system-distro-env]
WESTON_RDP_DISABLE_HI_DPI_SCALING=false

@hideyukn88  I have tried this, but everything remains the same :(.


Can't compile on android

Hi, when I tried to run the build I get a massive java compiler bug.  Has this package been tested on android before?
Thanks

An exception has occurred in the compiler (1.8.0_242-release). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com) after checking the Bug Database (http://bugs.java.com) for duplicates. Include your program and the following diagnostic in your report. Thank you.
java.lang.AssertionError: annotationType(): unrecognized Attribute name MODULE (class com.sun.tools.javac.util.UnsharedNameTable$NameImpl)
	at com.sun.tools.javac.util.Assert.error(Assert.java:133)
	at com.sun.tools.javac.code.TypeAnnotations.annotationType(TypeAnnotations.java:231)
	at com.sun.tools.javac.code.TypeAnnotations$TypeAnnotationPositions.separateAnnotationsKinds(TypeAnnotations.java:294)
	at com.sun.tools.javac.code.TypeAnnotations$TypeAnnotationPositions.visitMethodDef(TypeAnnotations.java:1066)
	at com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:778)
	at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49)
	at com.sun.tools.javac.code.TypeAnnotations$TypeAnnotationPositions.scan(TypeAnnotations.java:275)
	at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:57)
	at com.sun.tools.javac.code.TypeAnnotations$TypeAnnotationPositions.visitClassDef(TypeAnnotations.java:1042)
	at com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:693)
	at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49)
	at com.sun.tools.javac.code.TypeAnnotations$TypeAnnotationPositions.scan(TypeAnnotations.java:275)
	at com.sun.tools.javac.code.TypeAnnotations$1.run(TypeAnnotations.java:127)
	at com.sun.tools.javac.comp.Annotate.flush(Annotate.java:152)
	at com.sun.tools.javac.comp.Annotate.enterDone(Annotate.java:129)
	at com.sun.tools.javac.comp.Enter.complete(Enter.java:512)
	at com.sun.tools.javac.comp.Enter.main(Enter.java:471)
	at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:982)
	at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:857)
...
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
	at java.lang.Thread.run(Thread.java:748)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':flutter_blue_plus:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 37s
Exception: Gradle task assembleDebug failed with exit code 1

Actually, i just noticed that it mentions flutter blue in the stack trace 😅 I shall go looking there, sorry


Negative protobuf field numbers cause task to panic

Steps to reproduce:
foo.proto:
message Bar {
  optional string name = 1;
}

main.rs:
extern crate protobuf;
use protobuf::core::parse_from_bytes;

mod foo;
use foo::Bar;

fn main() {
  let bar: Bar = parse_from_bytes(&[1, 2, 3]).ok().unwrap();
  println!("{:?}", bar);
}

Expected:

parse_from_bytes returns a Result with an Err(ProtobufError::WireError(...))

Actual:

The task panics:
thread '<main>' panicked at 'field number must be positive', /home/dflemstr/.cargo/git/checkouts/rust-protobuf-ed1e2bca5258dbce/master/src/lib/stream.rs:86

An unknown error occurred
```

It seems to be a correct error message. First byte (1) is decoded to field number 0 and wire type 1. 0 is not valid field number.

Also, please note, that rust-protobuf itself does not cause panic. It is client code that panics when rust-protobuf reports error.

I'm 100% sure that it is the protobuf code that panics. It uses assert! which causes the panic.
I have to write this code to work around the issue:

try!(s.recv(&mut msg, 0));
unsafe {
    // This is the most annoying thing ever; the protobuf library
    // crashes on bad input.  We need to actually catch this error
    // using super unsafe code

    // If the try block doesn't set anything, this is the default
    let mut parsed = Option::None;

    // Isolate the execution
    let r = try(|| {
        parsed = Option::Some(
            protobuf::parse_from_bytes::<Request>(msg.as_slice())
                .map_err(|e| Error::Protobuf(e)))
    });

    match r {
        Err(e) => {
            let m = e.downcast::<&str>().map(|b|*b)
                .ok().unwrap_or("Unknown error").to_string();
            parsed = Option::Some(
                Err(Error::Protobuf(ProtobufError::WireError(m))))
        },
        _ => {}
    }

    parsed.unwrap()
}

I can contribute a fix for this as soon as the issue is acknowledged!

Sorry, you are right, it is protobuf who causes panic. I was confused by your code example which calls unwrap (which also could cause panic).
I'll fix that.

Thanks for the quick fix! :+1:


INPHB DOMAINE NAME

@messan1 I am sorry for a delay with processing your request.
Pull request merged. Thank you!