doc sync session

hi again, just a small fix-up to get sync_session to show up in docs. There are bunch of other things with #[cfg(not(feature = "async"))] that get excluded, but because they share the same name in #[cfg(feature = "async")], enabling those doesn't work together :/

Hi @tzemanovic

hi again, just a small fix-up to get sync_session to show up in docs.

I was thinking it is suppose to be there... but not async version... :(
https://docs.rs/expectrl/latest/expectrl/session/index.html
First of all I think that we shall show sync version by default not async.
But ideally could be cool to show both.
I've seen this this not a long time ago.
https://github.com/zhiburt/tabled/blob/10c17c80d9489150a0c5b216d917d179a5287de9/Cargo.toml#L54-L58
Which allegedly may help but I did not run yet it.

hi, yeah, apparently docs.rs builds with --all-features, but that means that not(feature = "async") == true, because "async" feature gets enabled. With #[cfg(any(not(feature = "async"), doc))] they both appear in the docs now

hi, yeah, apparently docs.rs builds with --all-features, but that means that not(feature = "async") == true, because "async" feature gets enabled.

Interesting if true.

With #[cfg(any(not(feature = "async"), doc))] they both appear in the docs now

Personally I'd love sync and async to pop up in the docs.
But either we would need to do your approach in other places or came up with some other magic.
Give me a bit time and we'll see what we could do.
If follow your approach then we'll merge it OK?

https://github.com/rust-embedded/gpio-cdev/blob/2c7ef82343e1331cc2805dc682afb3a699d0da7d/src/lib.rs#L121

https://github.com/tokio-rs/tokio/blob/b42f21ec3e212ace25331d0c13889a45769e6006/tokio-stream/src/macros.rs#L31-L39

This approach works but seemingly we can't do it if things have the same name or contradictional nature.

To summarize.
You approach is the approach.
We would need to follow it.
But because main thing we'd love to render in docs in async_session::Session and sync_session::Session which contradicts each other, and can't be showed correctly.
I've just switched all-features off to render the not async version.
https://github.com/zhiburt/expectrl/blob/8fc3cc32e0daf828bd6907f44617fa5ffdd9d824/Cargo.toml#L36-L37
See https://docs.rs/expectrl/0.5.2/expectrl/session/sync_session/struct.Session.html
Thank you for opening it.
I think we can close it?
Then take care.


[fixes #3742] Fix render when i18n hook is disabled

After i18n upgrade (sails 0.12.2+), sails.renderView() no longer works when i18n hook is disabled, because it was never configured. This patch will skip i18n.init() when this hook was disabled.

ok, fixed!

Thanks @Mordred!


Ability to set the textarea id attribute

It would be nice to be able to set the id of the generated textarea, like we can for the name and others. I need this to be able to get a <label for='myid'>...</label> element to auto focus onto the textarea when clicked.
Great little code editor BTW. It's very useful to have a lightweight option for React.

Another nice to have prop is placeholder. The textarea element has it built-in but I can't seen to be able to set it though simple code editor.

@davidjamesstone maybe you could do this instead:
<label>
This is some label
<Editor />
</label>

IMO IDs don't play very well with component-based designs because they need to be unique.
@oliveiraddb can you send a PR adding the prop? note that you'll also need to add the following CSS for the placeholder to showup.
.editor textarea:empty {
  -webkit-text-fill-color: initial !important;
}

@satya164 Implicit labels wont work in my case as they break the css/layout which I have no control over. They also aren't as well supported as explicit labels in assistive / accessible tooling.
I agree about IDs being kind of at odds with component based design but I don't have an alternative here.

@davidjamesstone Okies! I sent a PR adding a prop for that. Lemme know if it works for you.

Looks good & Thank you!

See #13 and #14 around how we'd like to avoid preventing more customisation in the future :) It's becoming apparent that every time someone discovers some smaller prop issues or sth they need to customise, they hit a wall and need a fix in the main lib, so customisability would be a neater answer ✨

Thanks @satya164. Much appreciated.

Actually this prop isn't released. I just added placeholder prop. Will support id with render props later.


Preparing to publish Tamil Qiskit Documentation

Summary
This PR adds Tamil to the translations list.
Details and comments
This PR is ready to be merged after https://github.com/qiskit-community/qiskit-translations/runs/2875235896 builds successfully.

Marking as on hold until the tamil translations are published.

After the rclone outage was resolved the translation build and published finished and tamil is on the site now: https://qiskit.org/documentation/locale/ta_IN/ so this is unblocked now.


multiple emojis do not work

0This works
library(ggplot2)
library(emoGG)
set.seed(123)
pos_df <- data.frame(x=rnorm(10),
                     y=rnorm(10),
                     emoji=rep(c("1f382","f1f389"),5))
ggplot(pos_df,aes(x,y)) +
  geom_emoji(emoji="1f382") +
  coord_fixed()

But using the emoji var with the emoji aesthetic does not work:
library(ggplot2)
set.seed(123)
pos_df <- data.frame(x=rnorm(10),
                     y=rnorm(10),
                     emoji=rep(c("1f382","f1f389"),5))
ggplot(pos_df,aes(x,y)) +
  geom_emoji() +
  coord_fixed()

Replacing geom_emoji by either geom_emoji(emoji=emoji) or geom_emoji(aes(emoji=emoji) always produces Error: Not Found
I am using ggplot <IP_ADDRESS>0 from github and emoGG 0.0.2 in RStudio 1.2.1170 wih R 3.5.1 on MacOS 10.14.2.
Is there a way to define which emoji should be placed where with x, y and an additional aesthetics variable?

In fact, using geom_text and svg output works:
library(tidyverse)
library(emoGG)
svg()
pos_df <- data_frame(x=rnorm(10),y=rnorm(10))
  ggplot(pos_df,aes(x=x,y=y,label=rep(c("\U1f389","\U1f382"),5))) +
  geom_text(family="OpenSansEmoji")
  coord_fixed()

But this way I can get only black and white outlines of the emojis, colors are not used.
Cann this be achieved?


Separate "list" and "show" action of WIT and WILT

WIT "show" action was moved from
    /api/spaces/00000000-0000-0000-0000-000000000004/workitemtypes/00000000-0000-0000-0000-000000000003

to
    /api/workitemtypes/00000000-0000-0000-0000-000000000003

WILT "show" action was moved from
    /api/spaces/00000000-0000-0000-0000-000000000003/workitemlinktypes/00000000-0000-0000-0000-000000000002

to
    /api/workitemlinktypes/00000000-0000-0000-0000-000000000002

The "list" actions for WIT and WILT remained at
    /api/spaces/00000000-0000-0000-0000-000000000004/workitemtypes
    /api/spaces/00000000-0000-0000-0000-000000000003/workitemlinktypes

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1989-1

Codecov Report

Merging #1989 into master will increase coverage by 0.04%.
The diff coverage is 77.63%.

@@            Coverage Diff             @@
##           master    #1989      +/-   ##
==========================================
+ Coverage   64.89%   64.94%   +0.04%
==========================================
  Files         148      150       +2
  Lines       13630    13632       +2
==========================================
+ Hits         8845     8853       +8
+ Misses       3956     3950       -6
  Partials      829      829

Impacted Files
Coverage Δ

controller/workitem.go
81.49% <100%> (ø)
:arrow_up:

controller/work_item_link.go
85.47% <100%> (ø)
:arrow_up:

controller/workitemtype.go
61.26% <100%> (-0.01%)
:arrow_down:

controller/work_item_link_type.go
84.34% <100%> (-0.05%)
:arrow_down:

controller/workitemtypes.go
66.66% <66.66%> (ø)

workitem/workitemtype_repository.go
70.83% <80%> (+2.86%)
:arrow_up:

controller/work_item_link_types.go
87.09% <87.09%> (ø)

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 9c6e5c7...0a98c53. Read the comment docs.


feat: support @mapbox/node-pre-gyp workflows

Resolves https://github.com/vercel/nft/issues/199.

I think we need to keep node-pre-gyp since it still gets 2.7 million downloads a week and has 812 packages that depend on it.
Regarding mkdirp we can drop it in #260, thanks!


Suggestion: add 'tools:replace="android:name"'

Hi,
Looking forward to use your library, good job.
Unfortunately I get 2 errors while compiling:
1)
Attribute application@name value=(***.Application) from AndroidManifest.xml:9:9-40 	is also present at [com.github.dev-prajwal21:CustomerSupportDesk:1.0] AndroidManifest.xml:16:9-74 value=(com.dev21.customersupportdesk.helper.AppController). 	Suggestion: add 'tools:replace="android:name"' to <application> element at AndroidManifest.xml:8:5-108:19 to override.

uses-sdk:minSdkVersion 16 cannot be smaller than version 19 declared in library [com.github.dev-prajwal21:CustomerSupportDesk:1.0] as the library might be using APIs not available in 16 	Suggestion: use a compatible library with a minSdk of at most 16, 		or increase this project's minSdk version to at least 19, 		or use tools:overrideLibrary="com.dev21.customersupportdesk" to force usage (may lead to runtime failures)
So why is the minSdkVersion 19 and why is there an Application(AppController) in your library?

Hi Devofure,
Thanks for your appreciation. The purpose for the AppController is to overcome MultiDex error. Also for the error that you are facing you can use the suggestion given by android studio. The reason for keeping minimum sdk version 19 is just that the android community is now moving to the latest versions of android. Please let me know if you still face any issues.


Opaque Error Cases

:wave: I think this project is cool, and I am glad to see the elixir ecosystem grow! I was hopping to give back and contribute!
About This PR
Currently the XSD.Type.Opaque module can be built using negative lengths when calling build_type/2. I assume that negative length types is an illogical state, and that only lengths satisfying XSD.Size.verify?/1 can result in a valid opaque type, right? Tests were also added to support this change.
API Changes
Before
iex> XDR.build_type(XDR.Type.Opaque, -1)
%XDR.Type.Opaque{length: -1, type_name: "Opaque", value: nil}

After
iex> XDR.build_type(XDR.Type.Opaque, -1)
** (XDR.Error) length must be between 0 and<PHONE_NUMBER> [0,<PHONE_NUMBER>]
    (exdr) lib/xdr/types/opaque.ex:19: XDR.Type.XDR.Type.Opaque.build_type/2

Coverage
Coverage was tested with mix coveralls
Before
COV    FILE                                        LINES RELEVANT   MISSED
71.4% lib/xdr/types/opaque.ex                        76       21        6
[TOTAL]  78.7%

After
COV    FILE                                        LINES RELEVANT   MISSED
100.0% lib/xdr/types/opaque.ex                        76       21        0
[TOTAL]  80.7%

Questions
In my tests I use assert_raise/3 which validates the message returned by the error. I believe this message is very handy to the reader because it is more clear which error is being reproduced. Alternatively I could use assert_raise/2 which doesn't validate the message making for more robust tests. What do y'all think?
My Environment
I am using asdf and am using the .tool-versions provided with the repository.
elixir 1.8.2
erlang 20.2
nodejs 12.8.0

@lbhdc Thanks so much for the contribution. I think it's great as-is!

@grossvogel It looks like the CI pipeline failed for this commit. I looked at the logs and it was a format issue. I ran mix format and pushed the changes. How would you prefer to handle that?

@lbhdc Oops, thanks for pointing that out! I just made a separate PR to master to clean up the formatting and it passed fine, so we should be good.


Rate n QOS on 'PE-D1-BDS-iNET'

After i re-probe several times, still return null on rate and QOS at PEINTERFACE with node = 'PE-D1-BDS-INET'
oo iya Fis, mau tanya tentang progres nya PE-Transit gimana ya?

Fixed in Build 6, there are some weirdness for interface-qos handling in non-asr cisco. The probe is now will use show policy-map interface input brief command by default, if it fails then use show policy-map interface | in Service-policy_input|Service-policy_output|Ethernet|Serial instead.


Calculate n based on alpha instead of using n=1E6 as default value.

Sorry for the change in compare_joint_models.py . This should have been done on master and already been pushed. Please only consider only the change in contours.py


Add Feathercoin

As discussed with Paul, we'd like to add Feathercoin as a currency to Edge.
I'm opening this PR now to see if the CI passes.
Tests and formatting should be ok (according to the nice hook), but I couldn't test yet with the full build (incl. UI) - the npm install in the edge-react-gui repo always hangs somewhere forever.
Thanks for your work!
Lucas

Thanks Lucas. We’ll give this a shot and see how it works.
Try using yarn 1.3.2 or higher to install the GUI. npm gives us problems.

See new PR which has fixes to this PR and also includes latest develop branch
https://github.com/Airbitz/edge-currency-bitcoin/pull/35


configurable endpoints URLs

Refer to this link for build results (access rights to CI server needed):
http://jenkins.inscitivops.com//job/api-node-pulls/2/
Test FAILed.


Docs: Fix typos in docs

This PR fixes some of the spelling mistakes in the docs.

Automated message from Dropbox CLA bot
@staranjeet, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@staranjeet, thanks for signing the CLA!

Merged, thanks @staranjeet for all the typo fixes!

Hey @timabbott
in readme-symlink.html, links to README.dev.md and README.prod.md are pointing to 404, probably because it is symlinked to README.md in the outer directory. For README.md it works fine, since github supports relative links, but for readthedocs it does not.
Probable fix can be absolute links like

Yep, agreed, someone just reported that here at the Pycon sprints as well, agreed that absolute links is the right fix if you want to take a pass at this.


Update frozen graph import to support both ragged and unragged tensors

While trying to import the frozen graphs from SLEAP, there is an issue where an Object reference error that pops up when you import. This is due to the default in the previous versions (< 1.3) of SLEAP had ragged tensors, while it is by default unragged tensors for versions > 1.3.
So to fix this, I have modified the code to read the correct tensor with the correct shapes.
This potentially could solve this issue https://github.com/talmolab/sleap/issues/1542
But there is a need to store more metadata to distinguish reading the ragged tensors from unragged tensors, for a future enhancement in SLEAP

 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.

Thanks for submitting the PR! I tried to implement this in the past but I couldn't find a satisfying way to support both versions. If we are merging this (and thus breaking the support for previous sleap versions) it would be nice to converge on a stable metadata format for the network export in sleap. This is also related to #10. I haven't thought about this in a while, but if there was a way to generate a single, merged, config file that also includes the tensor information on top of the training metadata would be ideal. Let me know if this makes sense and happy to discuss further!

FYI both - just commented on the relevant issue in the SLEAP repo.

FYI this issue is solved in the 'develop' branch, so for those who need it asap, checking that out will work. Then just waiting for the merge and release.

it would be nice to converge on a stable metadata format for the network export in sleap

Also fyi I suggested a format to @ssrinath22 a few months ago, and I believe this will be implemented soon

Hi guys,
Just had a chance to review this. The changes implemented here will fix compatibility with non-ragged exported models (the new default in newer SLEAP versions), but won't work for ragged models (default in older versions).
Since we support both and they have potentially different use cases, I'd like to also support both on this side as well.
I've asked @shrivaths16 to make a couple of additional changes to the current PR to hardcode some heuristic checks for whether it's ragged or unragged based on clues available in the shape and keys. For example, checking for the rank of centroidArr or the presence of "Identity_6" which vary across the two model types. This will allow this extension to be maintain compatibility with both ragged and unragged.
After this PR is merged in, we can add support for using the metadata model spec file. Technically, we already export an info.json file (here) together with the model artifact, but I think that maybe the issue is that it might not be explicit enough to describe whether it's ragged or not ragged. We'll add a key to this JSON file to make it more explicit and then send a new PR that tries to use that information if it's available (this will also require a new SLEAP version release, so it might need to wait a little).

I have added support for both ragged and unragged versions of the tensors of the frozen graphs. It might be a little repetitive but this seems to work.

Ok, not the prettiest solution but it gets this working again for the foreseeable future until we update the metadata we store in info.json.
This is fine by me if it's cool with the Bonsai folks! @jkbhagatio @bruno-f-cruz

@shrivaths16 Thanks for taking a jab at this!
I agree with @bruno-f-cruz it would be nicer to have a more stable JSON spec, but also understand this is getting people stuck so is probably worth resolving in a backwards-compatible way for now.
I have a few ideas to remove repetition and also to avoid detecting "raggedness" by catching exceptions (it's actually enough to do a null test).
I'm happy to either directly edit your branch or make a PR, but would you mind first removing the double quotes from your commit messages? Not sure how they got there in the first place, but it is a little bit distracting.
If you are able to edit them, I would also recommend making them slightly shorter to fit on GitHub without trimming, e.g.:

Update frozen graph import to support unragged tensors
Add support for both ragged and unragged tensors

If you need you can always add extended description using extra lines below the message title.

@shrivaths16 I was able to rebase and reword the commit messages accordingly so no need to do anything for now, will push my proposed refactoring soon.

@shrivaths16 @talmo one last question: I can see that PredictSinglePose was not touched. Is it because this particular model is not affected by the difference between ragged and unragged tensors, or should it also be updated accordingly?

This all sounds great @glopesdev! Thanks for making the changes!
Yes, single instance models always produce fixed size outputs so are never ragged.

@shrivaths16 @talmo I have tentatively refactored the code assuming both assumptions stated above are true and pushed the changes to @shrivaths16 fork.
Not sure how much time I will have today to test this on all possible model combinations, but if you have a setup ready to do this, then it would be great to see whether we could have a single code base to deal with both ragged and unragged versions.

This looks great! Thanks for the refactor @glopesdev!
@shrivaths16 let us know when you get a chance to test out all the configurations.

@shrivaths16 @talmo Sorry for the late review comments, I had forgotten to actually submit the review.
These are both outdated now, but they are meaningful since they describe the assumptions underlying my refactor. The code simplification I propose should be valid only if the above two comments hold.

Hi @glopesdev,
I reviewed the code and tested with all the different configurations and this only works for the unragged versions for PredictPoses and PredictCentroids modules, where the other configurations causes Index out of bounds error and Tensor size mismatch. This is because the shape of the arrays that are created while fetching the outputs from the frozen graph outputs are incorrect. Please let me know if anything else is needed to make changes to the code!

@shrivaths16 Is there a way for us to access a test suite of exported frozen graph models for all these different configurations? That would greatly accelerate iteration time on this.

@shrivaths16 Is there a way for us to access a test suite of exported frozen graph models for all these different configurations? That would greatly accelerate iteration time on this.

For top-down supervised ID:
Models:
https://storage.googleapis.com/sleap-data/reference/flies13/centroid.fast.210504_182918.centroid.n%3D1800.zip

https://storage.googleapis.com/sleap-data/reference/flies13/td_id.fast.v2.210519_111253.multi_class_topdown.n%3D1800.zip

Test data:
https://storage.googleapis.com/sleap-data/reference/flies13/190719_090330_wt_18159206_rig1.2%4015000-17560.mp4

Extract, then run (in a conda environment with SLEAP installed):
sleap-export -m centroid.fast.210504_182918.centroid.n=1800 -m td_id.fast.v2.210519_111253.multi_class_topdown.n=1800 exported_model

(optionally with --unrag, see docs)
@shrivaths16 since you've already done this, maybe you can share the exported model folder in a Google Drive link or something?
P.S.: if it's helpful for covering other model types, here's some models we use in our core SLEAP test fixtures

@talmo @shrivaths16 thank you for the feedback and all the information, I think everything is more clear now.
I fixed the ragged detection for the top-down centroid model and also relaxed the constraints around copying of unjagged arrays, where the TF wrapper library was being overly conservative (in our case we want to ignore shape differences as long as we can ensure the array type and size matches).
My only remaining question is around the pose-identity top-down model. In this case, e.g. PredictPoseIdentities model, it looks like part of the shape of the tensors did not change at all from the previous "ragged" version. From looking at the earlier commits and from testing myself with a pre-trained model, it looks like only centroidTensor and centroidConfidenceTensor really change shape, and the code for everything else should be left as it was before.
@shrivaths16 can you confirm this is the case? I think this is really the only detail left to wrap this up.

@glopesdev
Yes, in the PredictPoseIdentities model, the shape changes for centroidConfTensor and centroidTensor. The other 3 tensors remain with the same shape for both ragged and unragged versions.

@shrivaths16 great, in that case this last commit should finish the refactor and work for all cases of both ragged and unragged. If you have a set of models you could use for double-checking and testing this that would be great, and I will then merge and publish a new version.

@glopesdev
awesome, I checked with different configurations and it works fine, so should be good to merge!

@shrivaths16 @talmo merged and release deployed, thanks for contributing this!

@glopesdev
Awesome! Thanks a lot!


openr_kvstore_snooper and clients connected to OpenrCtrl thrift server throw error

Issue Description
semifuture_subscribeAndGetAreaKvStores thows error when subscribe updates from OpenR kvstore.
The openr log shows a stream-0 is attached, but the stream is ended immediatly and openr_kvstore_snooper throws error.
Environment

OS version: ubuntu2004

What's the actual result?
terminate called after throwing an instance of 'apache::thrift::transport::TTransportException'
  what():  TTransportException: Timed out
*** Aborted at<PHONE_NUMBER> (Unix time, try 'date -d @1658243418') ***
*** Signal 6 (SIGABRT) (0x3e8000536c4) received by PID 341700 (pthread TID 0x7eff0a7ef600) (linux TID 341700) (maybe from PID 341700, UID 1000) (code: -6), stack trace: ***
(error retrieving stack trace)
Aborted (core dumped)

After digging in to the KvStoreSnooper.cpp and logs from OpenrCtrlHandler.cpp, I found that the subscription API takes relative long time to return the Future result. Typically > 5s on my computer.
Then I tried openr_kvstore_snooper -processing_timeout_ms=10000 or set to 0 for no timeout (correct me if I'm wrong), everything goes well.


Questions about issue 45

Hi, I'm having the same problem as issue 45 when I'm working on an SCD task, but I don't see a solution. Firstly, the problem arises on the premise that:

I downloaded the processed SECOND dataset posted in your link directly, without any changes;
there should be no problem with the runtime environment, as my BCD task is running fine;
train_MambaSCD.py is used for training, and the programme proceeds to

                    for (pred_scd, label_scd) in zip(preds_scd, labels_scd):
                        acc_A, valid_sum_A = accuracy(pred_scd, label_scd)
                        preds_all.append(pred_scd)
                        labels_all.append(label_scd)
                        acc = acc_A
                        acc_meter.update(acc)

            kappa_n0, Fscd, IoU_mean, Sek = SCDD_eval_all(preds_all, labels_all, 37)

def SCDD_eval_all(preds, labels, num_class):
    hist = np.zeros((num_class, num_class))
    for pred, label in zip(preds, labels):
        infer_array = np.array(pred)
        unique_set = set(np.unique(infer_array))
        assert unique_set.issubset(set([x for x in range(num_class)])), "unrecognized label number"
        label_array = np.array(label)
        assert infer_array.shape == label_array.shape, "The size of prediction and target must be the same"
        hist += get_hist(infer_array, label_array, num_class)

There is a
File "/models/changedetection/utils_func/mcd_utils.py", line 209, in SCDD_eval_all
   assert unique_set.issubset(set([x for x in range(num_class)])), "unrecognized label number"
AssertionError: unrecognized label number

problem.
I debugged and found that in
for pred, labels in zip(preds, labels):
  infer_array = np.array(pred)
  unique_set = set(np.unique(infer_array))
  assert unique_set.issubset(set([x for x in range(num_class)])),

{-1} in unique_set at some point in the loop.

This question has puzzled me for a long time, I hope you can solve my problem in your free time, thank you very much!

Hi @heikeyuhuajia ,
Thank you so much for your question. We have not encountered this problem. I think it may be out of this part of the assignment.
`preds_scd = (preds_A - 1) * 6 + preds_B
preds_scd[change_mask == 0] = 0
        labels_scd = (labels_A - 1) * 6 + labels_B
        labels_scd[labels_cd == 0] = 0 `

When the network is adequately trained at the begining before the first validation, it should not encounter this problem. So I suggest you just assign the negative number to 0. This will solve the problem.
Best,

Thank you very much for your answer, during the validation process, the code had the part you mentioned:
preds_scd = (preds_A - 1) * 6 + preds_B
                    preds_scd[change_mask == 0] = 0

                    labels_scd = (labels_A - 1) * 6 + labels_B
                    labels_scd[labels_cd == 0] = 0

                    for (pred_scd, label_scd) in zip(preds_scd, labels_scd):
                        acc_A, valid_sum_A = accuracy(pred_scd, label_scd)
                        preds_all.append(pred_scd)
                        labels_all.append(label_scd)
                        acc = acc_A
                        acc_meter.update(acc)

            kappa_n0, Fscd, IoU_mean, Sek = SCDD_eval_all(preds_all, labels_all, 37)
            ```

Unfortunately, there is still no solution to this problem, I hope you keep this issue and when I finish my recent paper I will come back and look into this again, thank you for your patience!

Hi @heikeyuhuajia ,

Unfortunately, there is still no solution to this problem

As I said, [you can just assign the negative number to 0. This will solve the problem].
Best,

Hello @ChenHongruixuan,
thank you very much for your reply, I have set up the following settings as you said to solve the above problem:
preds_scd = (preds_A - 1) * 6 + preds_B
                    preds_scd[change_mask == 0] = 0

                    labels_scd = (labels_A - 1) * 6 + labels_B
                    labels_scd[labels_cd == 0] = 0

                    # chenhongruixuan: As I said, [you can just assign the negative number to 0. This will solve the problem]
                    preds_scd[preds_scd < 0] = 0
                    labels_scd[labels_scd < 0] = 0

                    for (pred_scd, label_scd) in zip(preds_scd, labels_scd):
                        acc_A, valid_sum_A = accuracy(pred_scd, label_scd)
                        preds_all.append(pred_scd)
                        labels_all.append(label_scd)
                        acc = acc_A
                        acc_meter.update(acc)

Does this manual setup lead to artificial effects on the model?
Best,

Hi @heikeyuhuajia ,
Essentially this won't cause any problems. It is caused by pixels labelled 0 (i.e. unchanged pixels). This part of the pixel is not counted as a loss in the classification branch, so after hundreds of iteration at the beginning, there should be no pixel that would be classified as 0 (at least in our experiments). Therefore, we did not add a special treatment for this part of the pixels at the beginning.
Best,

Thank you very much for your patience and assistance. I wish you great success in your work and good health!


puzzle about training result

Is this training result normal? espacially for the result of "turtlebot" and "turtlebot-a2c"

Not sure, it doesn’t look like my training results.

I believe it is in the paper.

From: GongYanfu @.>
Sent: Tuesday, September 6, 2022 1:00:52 PM
To: jkulhanek/robot-visual-navigation @.>
Cc: Jonáš Kulhánek @.>; Comment @.>
Subject: Re: [jkulhanek/robot-visual-navigation] puzzle about training result (Issue #16)
Can you show the training result of this? about experiments of turtlebot, turtlebot-a2c and turtlebot-unreal
—
Reply to this email directly, view it on GitHubhttps://github.com/jkulhanek/robot-visual-navigation/issues/16#issuecomment-1238050542, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABAGZIXXTPZTLLL5EE6MLR3V44W7JANCNFSM54O2CFEQ.
You are receiving this because you commented.Message ID: @.***>

This should now be resolved by commit: https://github.com/jkulhanek/robot-visual-navigation/commit/2c87a2d871eb2982a1070fe4425bd1218d4958b8


Implement traffic light OFF at sechub client

SecHub client must be able to handle the OFF value introduced with #809 .

At this point #806 must be already done.
In case of OFF the status must be checked to decide if build is broken or not. With OFF we must always break because there is no longer a way to decide if the build is broken or not by

FAILURE: exit with error code for failed execution
SUCCESS: exit with special error code, that there is LOGIC_PROBLEM  (success may not happen when traffic light is off)

sub issue for #808

Looked into it:
Currently all displayed status information comes from the get status call (https://mercedes-benz.github.io/sechub/latest/sechub-restapi.html#user-checks-sechub-job-state) - not from the report.
This makes sense, because if the report format is html, the above mentioned informations are not present (additionally, parsing a html file is not easy).
So the get status call should contain all informations about failures.
(and a scan summary (w critical findings, x high, y medium, z low) if we want the SecHub client to display this information)
Currently, the status call contains these informations:
{
  "jobUUID": "37008e19-f592-4afb-b11d-d45faad23725",
  "owner": "myuser",
  "created": "2022-02-03T16:32:50.631346",
  "started": "2022-02-03T16:32:51.885962",
  "ended": "2022-02-03T16:32:52.044051",
  "state": "ENDED",
  "result": "OK",
  "trafficLight": "RED"
}

To make it report format agnostic, we agreed to add the messages to the get status call.
{
  "jobUUID": "37008e19-f592-4afb-b11d-d45faad23725",
  "owner": "myuser",
  "created": "2022-02-03T16:32:50.631346",
  "started": "2022-02-03T16:32:51.885962",
  "ended": "2022-02-03T16:32:52.044051",
  "state": "ENDED",
  "messages" :  [
                  {
                       "type" : "ERROR",
                       "text" : "The code scan execution did fail"
                  }
  ]
  "result": "OK",
  "trafficLight": "RED"
}


Execute SQL Operation should not return null

It breaks contract of PreparedOperation.

Hey there,
it seams that its still possible to get null as result:
storIOSQLite
                .get()
                .object(TextMessageEntity.class)
                .withQuery(TextMessageTable.QUERY_ALL)
                .prepare()
                .createObservable()
                .map(textMessageEntity -> {
                    Log.d("TAG", textMessageEntity.toString()); // textMessageEntity is null
                    return textMessageDataMapper.transform(textMessageEntity);
                });

Am I doing something wrong or why is it null?

Hi @BraunreutherA
This issue relates just to raw sql query. I think, null is the most expected when we request nonexistent object (executeAsBlocking for this case is still nullable).
@artem-zinnatullin to make it fairly, should we mark base method as nullable?

to make it fairly, should we mark base method as nullable

Well… Yes, let's do it.
@BraunreutherA it's expected behavior since object with required query params may not exist in the db, for example get().listOfObjects() will return empty list in such case.

Okay, that makes sense. I was confused cause it was marked as a non-null method. Thanks for the explanation!

@BraunreutherA yeah, sorry, my bad!
Hope you're enjoying the library :)


(Swift) Hello-World testcase error

Hello! While this is related to the entry level exercise, I'm raising this concern in case it also is mirrored across the remaining Swift exercises which I have yet to venture into. I had an issue with the test file missing the parameter reference in the function call which caused issues with the test cases themselves (i.e. hello("bob") instead of the required hello(parameter: "bob")). Once I added the parameter reference to the function call they worked fine.
Please let me know if I'm missing something here. I'm obviously new to the language :).

CC @exercism/swift

Swift uses enforced labels on the declaration side so if you do declare a label on the definition, the compiler will try to help you but suggesting a fix it on the call site. Just use an underscore on the definition. Skim over the swift manual.
let me know if you have any issues on the swift repo. https://github.com/exercism/xswift/blob/master/exercises/hello-world/Sources/HelloWorldExample.swift

@Illoric Once you figure this out, would you be willing to help suggest an improvement to the "getting started" documentation for Swift?
It lives here: https://github.com/exercism/xswift/blob/master/docs/TESTS.md
and is displayed on the site here: http://exercism.io/languages/swift/tests

@masters3d Thank you! It appears I glanced over this bit of magic previously.
@kytrinyx Overall, I think the documentation was quite helpful. This "issue" could've been avoided with some further due diligence on my part :). However, I would be happy to contribute to documentation updates/improvements.

@Illoric Excellent. If you do have suggestions or tweaks, please submit them in the xswift repository. ✨


Provide some example(s) to get started

Hi there,
Is this still working as it should, @ghostbar ?
I ask because I can't get deb-build-pkg do anything, not on Linux nor on macOS.
All I ever get when running with the build option is this:
# deb-build-pkg build
Will build version unstable for some-project on debian...
unstable: Pulling from resnullius/debian-devel
Digest: sha256:c2af3281872daddfef0438b097a671d09977d9e1ff6a289f4f1664c245ea7221
Status: Image is up to date for resnullius/debian-devel:unstable
docker.io/resnullius/debian-devel:unstable
/opt/workplace/some-project /opt/workplace

FYI I have a debian/ dir inside some-project and using run instead of build will get me going on the prompt in Docker, but then I have to run the regular build commands by hand.
So could you please confirm this still works and if so, give a real world example in the README.md. TIA!
UPDATE 1
Probably something is missing in my debian/ dir, because when I checkout resnullius/capstone.deb, and run deb-build-pkg build over there, it starts to do something more (but the build fails due to failing orig.tar.gz one dir up).
UPDATE 2
Adding a URL to debian/watch started something. 🎉
However, the build failed due to the fact that the upstream tarball could not be found:
dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../some-project_3.1.1.orig.tar.{bz2,gz,lzma,xz}

On the local FS the orig.tar.gz is one dir up, but that's not added to the Docker container somehow.
The same error as for resnullius/capstone.deb.
UPDATE 3
Now experimenting with the right "filenamemangle" in debina/watch. A "v" is added for versioned released, I need to get that letter removed.

Hi!
https://github.com/resnullius/docker-deb-devel/blob/master/versions/x86_64/debian-unstable/scripts/entrypoint.sh#L68-L72
deb-build-pkg is basically a simple fast call for docker in order to use docker-deb-devel to do all the heavy lifting.
Indeed, the source package is not taken from your local FS but with uscan. That's the lines I just put in the URL.
It is weird capstone is no longer working. Its debian/watch must be out-of-date now.

Thanks, Jose-Luis!
I see from current experience the crux is in the debian/watch indeed. 😉
I have a somewhat working "filenamemangle" to strip the letter "v" form the release:
opts="filenamemangle=s/(?:.*)?v?(\d[\d\.]*)\.tar\.gz/<project>-$1.tar.gz/" \
  https://github.com/<user>/<project>/tags (?:.*/)?v?(\d[\d\.]*)\.tar\.gz

but this needs to be fine-tuned.
PS. This is an awesome script / Docker image to use!

I'm happy someone else is using it!
Yes, debian/watch can give some pain. Capstone is not failing itself, it's just downloading a newer tarball than the version is packaged so it fails like "can't get 3.0.4" because of course, it downloaded 3.0.5. :-)
Hope you keep finding it useful :-)!!


$stateNotFound with 1.0.0 beta 3

Hello,
I would like to know how to rewrite the code I currently have that handles the "$stateNotFound" event. From what I understood, I should now use the transition API, but for this specific error I don't know what to use and how.
Should I just check if transition.targetState().exists() in the $transition$.onError transition callback function? If transition.targetState.exists() is false, will transition.to() return null?
Sorry for the newbie questions btw :)

Sorry for the newbie questions btw :)

Don't be sorry, and that's not a newbie question at all!
$stateNotFound was replaced by onInvalid but that detail didn't make it into the migration guide.
I created an issue to track this missing documentation.
Why not a transition hook?
I can explain why onInvalid is different than transition hooks:
We decided that an Transition object with an non-existent TargetState shouldn't be allowed.  This made a lot of things inside the Transition class more consistent (we don't have to check if the target state is valid() all over the place).
Because of that, an onBefore transition hook doesn't make sense for this use case.  Instead, the transitionTo method of StateService performs some pre-checks before creating and running a Transition.
As long as I'm pasting code, here's the onInvalid handler code

Thanks for the thorough answer. I'll test this now :)
One last question: what's the purpose of the .exists() method on Transition objects then? A leftover of an earlier design? Or are there still use cases for that?

Works like a charm, thanks a lot @christopherthielen !

@dsebastien

One last question: what's the purpose of the .exists() method on Transition objects then? A leftover of an earlier design? Or are there still use cases for that?

Do you mean TargetState.exists()?  I don't see exists on the Transition object


Update apiVersion to work with 1.16

extensions/v1beta1 is no longer supported, using apps/v1 instead.

/kind api-change

Special notes for your reviewer:
Release note:

does apiVersion: apps/v1 work on 1.13?

it is working since v1.9


[admin] Publish

Docs Build status updates of commit 709419d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Smart Editor - Smartform expressions not working for "Date Modified" and "Date Created" fields

When creating an expression with "Date modified" or "Date Created" fields, results do not show.
Example:
Hide "Ancilliary Role" WHEN "Date Modified" is 06/03/16. (DOES NOT WORK)
Hide "Ancillary Role" WHEN "MANUFACTURER" is 'esri' (DOES WORK)
I have tried various expressions with "Date Modified" and "Date Created" fields; none have worked so far.

Can you share the map so I can repo.  I was not able to repo it on my dataset.

nevermind, found the bug, good find!  Will fix it

Ok. I will keep bug hunting.  I plan to look through batch attribute editor, smart editor and group filter.  Let me know if you need me to work on something else.
From: Michael Miller<EMAIL_ADDRESS>Sent: Friday, June 3, 2016 6:25 PM
To: Esri/solutions-webappbuilder-widgets<EMAIL_ADDRESS>Cc: Martin Paz<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Esri/solutions-webappbuilder-widgets] Smart Editor - Smartform expressions not working for "Date Modified" and "Date Created" fields (#608)
nevermind, found the bug, good find! Will fix it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_solutions-2Dwebappbuilder-2Dwidgets_issues_608-23issuecomment-2D223728065&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=qJDHIyZb9OyyV80NcLYmmQ&m=b6L0xcRZXXqYPb2dfA_41alg7kmTOGyyN6vH3Ethqao&s=SRhaarfX6v5bjrOhlCa1cz89EN5C-ToyuLgb6KCgCNU&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe_AS0ePil9kKNzWcAdJLgqo-5F9IjN4vLcZLks5qINPkgaJpZM4ItxG7&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=qJDHIyZb9OyyV80NcLYmmQ&m=b6L0xcRZXXqYPb2dfA_41alg7kmTOGyyN6vH3Ethqao&s=1Xx9VxuLuv8DDn69wGfaeRfvxCejfgfPPQk-IQLScZE&e=.


Update relevant schema documentation on how to handle breaking changes in common schemas

User Story
As a report stream admin, I would like to understand the process for editing a common translation schemas that is stored in the source code
Description/Use Case
For the foreseeable future, schemas that are used across organizations will continue to exist in the source code and will be edited there.  There needs to be documentation on how to edit those safely.
Risks/Impacts/Considerations
The main item that needs to be fully documented is the process of introducing a breaking change to a commonly used schema. See this of the design.
Dev Notes
Acceptance Criteria

[ ] The process for editing schemas in the source code is added to UP documentation

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @brick-green @jack-h-wang @JessicaWNava @JFU-NAVA-PBC @jimmyfagan @luis-pabon-tf @mkalish @thetaurean

Linked to #10491


Prototype RSpec-retry and Github actions workflow for flakey tests

Context
Proof of concept for flakey test workflow reporting

Run tests (generates flakey test report)
Set job variable from contents of flakey test report file
Read job variable and comment on PR if flakey test var is not empty

Changes proposed in this pull request

Guidance to review

Link to Trello card

Things to check

[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] API release notes have been updated if necessary
[ ] Required environment variables have been updated added to the Azure KeyVault

Closing as this proof of concept is being implemented in various PRs now.


Refactor RepeatedOperation & RetryOperation

At the moment, RepeatedOperation uses two generators, one for delays and another for the operation, which in hindsight is a little bit limiting.
A better approach would be a generator of type (NSTimeInternal?, T) or (NSDate?, T)... so that the generator can be responsible for injecting it's own delay.
Another factor would be how to take latest and aggregate errors into account.

Current coverage is 72.01%

Merging #168 into development will decrease coverage by -0.14% as of 838e5b3

@@            development    #168   diff @@
===========================================
  Files                51      51
  Stmts              3020    3009    -11
  Branches              0       0
  Methods
===========================================
- Hit                2179    2167    -12
  Partial               0       0
- Missed              841     842     +1

Review entire Coverage Diff as of 838e5b3

Powered by Codecov. Updated on successful CI builds.

Change in this PR:

Now, the generator element for Repeated is a tuple: (Delay?, T) which means that at the lowest level, which has the most flexible, it is possible to provide a generator which does the following:

return .None to stop repeating, i.e. end the RepeatedOperation.

return (.None, operation) to add the operation to the queue immediately.
return (.By(1.0), operation) to add the operation to the queue, but depending on a 1 second delay.
return (.Until(date), operation) to add the operation to the queue, but depending until a date in the future.

Additionally, RetryOperation is a thin facade over this structure which accepts an error handler.The handler is this type:
typealias Handler = (RetryFailureInfo<T>, Delay?, T) -> (Delay?, T)?

The failure info value encapsulates error information related to all the previous failed operation instances. It can be inspected to adjust the return tuple. For example to modify the delay, or provide a completely new operation instance, or to add dependency operations.
For example:
typealias Handler = RetryOperation<MyOperation>.Handler
let handler: Handler = { info, delay, op in
    let extra = AnExtraOperation()
    op.addDependency(extra)
    // Will add another operation to the group's queue separate to the primary operation
    info.addOperations(extra)
    return (delay, op)
}


Weights and model saved

There was a reason at some point why I was only persisting weights instead of the model, but this should be reviewed at some point. There's no harm in doing both, but it's a bit inconsistent. Now going to save both due to ongoing analysis work, so it's getting a bit messy
model/train.py - train_model
    weights_path = os.path.join(network_folder,
                                "{}.network_{}.{}.h5".format(run_name,
                                                             dataset.identifier,
                                                             seed))
    model_path = os.path.join(network_folder,
                              "{}.model_{}.{}".format(run_name,
                                                      dataset.identifier,
                                                      seed))

There's no harm in saving both, for the moment closing this following the sort out of #69


Clicking on the notification in playlist mode crashes the app

The issue occurs only if the video being played is not the first one. It's most probably associated with startActivity being called with other videoId than the initial one.

Fixed by ensuring onNewIntent returns if intent's extras are null


chore(ci): bump deps versions

Happy lunar new year 🎉

Perhaps we should use dependabot to update deps versions.
This way we can avoid forgetting to update these deps versions.
see https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates
How do you think? @ayamir

i dont think using a dependabot is a good idea.
we might have supply chain attack issue.
it's very own security news.


Disable whitespace trimming in password related serializers

Disabled password whitespace trimming as that interferes when password ends with a space, which although should be allowed results in a mutated password. Same way, if a user enters 8 black spaces, the password is rejected stating that it is blank.
For more information check: https://github.com/Cloud-CV/EvalAI/issues/1543

Thanks for submitting this PR!
I'm in favor of merging this in. That said, would it make sense to have this as a configurable toggle (with a default to True)?

It would make less sense to add a configurable toggle (since this issue is a bug and not a feature) as mutating the password entered by the user at any point in the lifecycle of the code will have ill effects.

Hey, any update on this?

Hi,
as a user of rest-auth, thanks for the contribution!
This repo is not maintained anymore, so the development moved to dj-rest-auth. (reference: https://github.com/Tivix/django-rest-auth/issues/568)
It may be best, if you move this PR there. (and upgrade to using dj_rest_auth)
new repo link: https://github.com/jazzband/dj-rest-auth (I'm not the upkeeper of that repo, it just makes sense for me to help you merge your PR)
Many Thanks,
Barney


Weird email address parsing

Stephanie got the email, her CC to herself shows up, but the other cc's she adds (Ed's email address) come back as a bunch of letters separated by commas. Issue comes up when using commas or semicolons as separators in the cc field.

Ok this was actually dumb.

Fix incoming


Test XMLExporter

Having troubles fixing the broken Clipboard tests.
I fixed this one: https://github.com/substance/substance/commit/f274b55d1283370620346eb8b068242d11b3a97d
Here we have the situation that we have root, a DefaultDOMElement that wraps the document node. So we can not call createElement on it, as this requires ownerDocument to be set.
I wonder if we should allow wrapping documents into elements at all? If we allow it, then rootEl.createElement would feel natural though and we should make it work somehow.
Then in ClipboardImporter we have some occurences of this.$$ which still points to the static DefaultDOMElement.createElement. Now the question is, should we play the same game for importers and store a this.state.documentEl (either an empty XML doc or HTML doc?). Our first assumption was that we only need this stuff for the exporter.


libspdm_try_send_receive_key_exchange function should call libspdm_release_receiver_buffer function before return error.

I think line 668 should be changed like line 674~675 goto receive_done;, call libspdm_release_receiver_buffer function before return error.
https://github.com/DMTF/libspdm/blob/de3c5030ed37cc68717aa4e41d6c33f73028476c/library/spdm_requester_lib/libspdm_req_key_exchange.c#L665-L676
https://github.com/DMTF/libspdm/blob/de3c5030ed37cc68717aa4e41d6c33f73028476c/library/spdm_requester_lib/libspdm_req_key_exchange.c#L716-L718

A check for this should be incorporated into the Requester / Responder unit tests as well. Once the function-under-test returns then it should check that the buffers have been released. I'll file a separate issue for that.

I will check this


Issue with Application Gateway Ingress Controller

Report
I am trying to migrate the ingress controller from Nginx to Azure Application Gateway. The following is my ingress configuration. I get a 404 Not Found error. Azure Application gateway tries to connect to keda-add-ons-http-interceptor pod for health probe and it is failing, I have attached the screenshot
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    meta.helm.sh/release-name: xkcd
    meta.helm.sh/release-namespace: keda-tester
  creationTimestamp: "2024-07-17T06:55:08Z"
  generation: 1
  labels:
    app.kubernetes.io/managed-by: Helm
  name: xkcd-dev
  namespace: keda
  resourceVersion: "118833"
  uid: 0d93e746-8789-424a-a043-5d90952e9f72
spec:
  ingressClassName: azure-application-gateway
  rules:
  - host: kedatester.mydomain.net
    http:
      paths:
      - backend:
          service:
            name: keda-add-ons-http-interceptor-proxy
            port:
              number: 8080
        path: /
        pathType: Prefix

Azure App gateway health screenshot

Expected Behavior
Http Addon needs to work with Azure Application Gateway ingress controller.
Actual Behavior
Http Addon is not working with Azure Application Gateway ingress controller.
Steps to Reproduce the Problem

Install xkcd example with ingressClassName: azure-application-gateway
Connect to the end point

Logs from KEDA HTTP operator
example

HTTP Add-on Version
0.8.0
Kubernetes Version
1.28
Platform
Microsoft Azure
Anything else?
No response

Hello,
The problem is that currently we check the user agent to discover if the request is a probe or not and handle it as probe and not as a legit request:
https://github.com/kedacore/http-add-on/blob/08c811fe205daaf2bc55c6a46155be2729f21916/interceptor/middleware/routing.go#L85-L89
Does AGIC support adding custom user agent to the probe? if yes, just use kube-probe and it'll pass. If not, we will need to include the AGIC user agent. Do you know which is it? Are you willing to open a PR supporting it?


Timeout: py34.test.unit._cython._read_some_but_not_all_responses_test.ReadSomeButNotAllResponsesTest

https://grpc-testing.appspot.com/job/gRPC_pull_requests_linux/4465/testReport/junit/(root)/aggregate_tests/run_tests_python_linux_dbg_native/

not seen for >1month.


Upon window resize the bgimage does not update vertical height

This is most probably due to the fact that the bgimg is given the original window height of the users machine and then is not updated when resized.

fixed in ad6500e


docker run/start failed after switch ros console

RancherOS Version: (ros os version)
v1.3.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS, docker-machine
Here are my steps.

Create a RancherOS v1.3.0 on AWS.

~# sudo ros os version
v1.3.0

Switch user docker to 17.03.2-ce

~# docker version
Client:
 Version:      17.03.2-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 01:35:00 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.2-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 01:35:00 2017
 OS/Arch:      linux/amd64
 Experimental: false

Start rancher server

sudo docker run -d --restart=unless-stopped -p 8080:80 -p 6443:443 rancher/rancher

switch console to alpine

sudo ros console switch alpine

After switched console, I can't restart my rancher server or run a new container.

~# docker start e716bef059ca
Error response from daemon: unknown service types.API
Error: failed to start containers: e716bef059ca

Everything will be OK after reboot. But error still occurs after switching console again.

This is due to the container-shm process is killed after switching console.
And in the old version of docker,there is a endless loop to check whether a container pid without containerd-shm has been killed, however, if the pid can not be killed -9, this loop will be endless(blocked all containerd process), and this loop is in containerd startup processs(the main goroutine), which used for restoring containers, and if this process is blocked, the rpc service types.API will not be started. so the error will come out.
This problem has been fixed after the 17.12.0-ce version


Requesting (Draw Call) Batching for the DragonBones GDExtension

Describe the project you are working on
I work on a project that relies heavily on multiple (!) DragonBones Armatures simultaneously on the screen.
I am evaluating different game engines that I can use for this.
Describe the problem or limitation you are having in your project
Drawcalls get in the hundreds when instancing. Looks like no batching is done.
Drawcalls for the Default DB Dragon and also for a custom character of mine
are already in the twenties.  (Haxeflixel has an extension, too. Tried this as well. Has also no Batching. Same amount of drawcalls.)
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Batching would reduce Drawcalls mostly to 1 per Armature or Object.
(CocosCreator 3.x has batching.  So in CocosCreator 20-30 DragonBones Armatures will have 20-30 Drawcalls.
in Godot this would be 200-500 depending on the Armature.)
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
No idea. I think this has to be done at the core of the extension.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Possibly not.  If there is a way to do this in game code, I'd like to hear how to do this.

You can try to merge this batching rendering pr into godot and compile a custom godot editor to test this issue.
Currently each display object of DragonBone armature is a Node2d, this is Inherited from the old project.
I'm not sure that compose all displays drawing logic in _draw() of one object (may be DragonBoneArmature) can reduce draw call or not.
Even if this does solve the problem, I don't have time to implement it.
Welcome to do in-depth research and submit your optimization pull request.


Not a valid calendar for given culture in bit date picker in release mode

I'm trying to use Bit date picker v1.8.0.
But in release mode with Linker config i got this error.

Not a valid calendar for the given culture.

I tried to skip these assemblies in linker config but still this error shows up.
  <assembly fullname="Bit.CSharpClient.Controls">
    <type fullname="*" />
  </assembly>
  <assembly fullname="System.Core">
    <type fullname="*" />
  </assembly>
  <assembly fullname="NodaTime">
    <type fullname="*" />
  </assembly>

What assembly should i skip in linker config to make this control work?

https://github.com/bit-foundation/bit-framework/blob/master/Samples/CSharpClientSamples/Controls.Samples/Samples.Android/LinkerConfig.xml


Support secure RabbitMQ installations

The current check-rabbitmq-alive.rb script does not allow for checking secure RabbitMQ installations that have verify and fail_if_no_peer_cert enabled on the server. This PR adjusts the script to allow passing in certificates.
Since the default Sensu SSL certificate generation scripts use a common name of sensu, verify_peer on Bunny will fail as it uses the common name for additional verification. I could not see an easy way to pass in the common name to verify with Bunny, hence the reason for explicitly disabling verify_peer on the check.

@eheydrick thanks for catching that error. It's been addressed.

Released in 1.2.0.


macOS: Enable wasm and allow to load .wasm on Apple silicon

Commit Message: This applies changes from https://chromium-review.googlesource.com/c/v8/v8/+/3700352 as a fix for MemoryAllocator::PartialFreeMemory() which shouldn't try to change permissions of RWX pages.
This mainly affects macOS > 11.2 due to mprotect() behavior changes (https://github.com/envoyproxy/envoy/issues/23243, https://chromium-review.googlesource.com/c/v8/v8/+/3610445/comment/6294ada3_a3cab643/) on Apple silicon.
This also flips the Wasm feature to be enabled by default on macOS.
The future patch removal task is tracked in https://github.com/envoyproxy/envoy/issues/23258.
Signed-off-by: Dhi Aurrahman<EMAIL_ADDRESS>Additional description:
By applying this patch on my local (macOS, 12.6 (21G115), M1), I can run envoy to load a .wasm from the examples/wasm-cc. Before this patch, it was caught by: EACCESS error. See https://github.com/envoyproxy/envoy/issues/23243 for more details.
$ uname -a
Darwin Dhis-MacBook-Air.local 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101 arm64
$ pwd
/Users/dio/src/envoy/examples/wasm-cc
$ ~/src/envoy/bazel-bin/source/exe/envoy-static -c envoy.yaml

Also, I think we need to backport this to release/1.23 (which has the same v8 version), hence the Homebrew build for Apple silicon will have this Wasm feature enabled.
Risk Level: Low, since the current behavior is preserved, and the patch is included on upstream (v8, 10.5-lkgr has it)
Testing: existing, and manual testing on macOS M1
Docs Changes: N/A
Release Notes: N/A (should we add an announcement since we enable wasm by default again?)
Platform Specific Features: enable wasm (v8 runtime) on macOS by default
Fixes #23243

Thanks, @lizan! 🙇🏾

/lgtm deps

@PiotrSikora sure. I'll try. However, since release/1.23 is on this <IP_ADDRESS> I thought we can backport this for release/1.23, and not sure if updating deps (with minor release version) can be done in stable branches.

(sorry for the spammy request for re-reviewing this, seems like there was a glitch on GitHub on my side)

@PiotrSikora sure. I'll try. However, since release/1.23 is on this <IP_ADDRESS> I think we can backport this for release/1.23 first, and not sure if updating deps (with minor release version) can be done in stable branches.

Good point. I guess we could merge this (since it's already approved) and then update V8 in a follow-up PR.

/lgtm deps

@lizan could you help to approve and merge this? 🙇🏾


ModuleNotFoundError: No module named 'vtkOpenGLKitPython'

The function fails to import vtkOpenGLKitPython module while it's shipped with the vtk python module
Investigative information
Please provide the following:

Timestamp: 2019-09-09 12:34:52.203

Expected behavior
The function should work as expected as in local environement
Actual behavior
The function fails to import vtk module
Executed 'Functions.HttpTrigger' (Failed, Id=1fef9317-1095-41f8-bdab-656267ca3569)

Result: Failure
Exception: ModuleNotFoundError: No module named 'vtkOpenGLKitPython'
Stack:   File "/usr/local/lib/python3.6/site-packages/azure_functions_worker/dispatcher.py", line 309, in _handle__invocation_request
    self.__run_sync_func, invocation_id, fi.func, args)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/azure_functions_worker/dispatcher.py", line 426, in __run_sync_func
    return func(**params)
  File "/home/site/wwwroot/HttpTrigger/__init__.py", line 463, in main
    _meshs, _meshs_files = save_meshs(project_format, output, _objects_treed_list)
  File "/home/site/wwwroot/HttpTrigger/__init__.py", line 356, in save_meshs
    convert(file_content, full_path, thirdparty_format, file_ext)
  File "/home/site/wwwroot/HttpTrigger/__init__.py", line 57, in convert
    import vtk
  File "/home/site/wwwroot/.python_packages/lib/python3.6/site-packages/vtk/__init__.py", line 12, in <module>
    from .vtkOpenGLKit import *
  File "/home/site/wwwroot/.python_packages/lib/python3.6/site-packages/vtk/vtkOpenGLKit.py", line 9, in <module>
    from vtkOpenGLKitPython import *

Requirements
pydicom==1.2.2
lxml==4.4.1
vtk

@daker, what command did you use to publish the app?

@maiqbal11 i use the func azure functionapp publish MyFunc, the zip file contains the vtkOpenGLKitPython.so file. i have read somewhere that the libgl1-mesa-glx deb package needs to be installed...

Can you try func azure functionapp publish MyFunc --additional-packages libgl1-mesa-glx. This is documented here: https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local#publish.

@maiqbal11
$ func azure functionapp publish MyFunc --additional-packages libgl1-mesa-glx
Getting site publishing info...
Deleting the old .python_packages directory
Collecting pydicom==1.2.2 (from -r /home/daker/cad/requirements.txt (line 1))
  Using cached https://files.pythonhosted.org/packages/43/88/d3c419ab2e753e7651510882a53219373e78fb55294cb247dffd3934ea55/pydicom-1.2.2-py2.py3-none-any.whl
  Saved /tmp/azureworkerw5isl1gv/pydicom-1.2.2-py2.py3-none-any.whl
Collecting lxml (from -r /home/daker/cad/requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/e4/f4/65d145cd6917131826050b0479be35aaccba2847b7f80fc4afc6bec6616b/lxml-4.4.1-cp27-cp27mu-manylinux1_x86_64.whl (5.7MB)
  Saved /tmp/azureworkerw5isl1gv/lxml-4.4.1-cp27-cp27mu-manylinux1_x86_64.whl
Collecting vtk (from -r /home/daker/cad/requirements.txt (line 3))
  Using cached https://files.pythonhosted.org/packages/bc/39/99d717feb6246e875188e60cc7200e60f862a457972e32c250a0cb8d2b3d/vtk-8.1.2-cp27-cp27mu-manylinux1_x86_64.whl
  Saved /tmp/azureworkerw5isl1gv/vtk-8.1.2-cp27-cp27mu-manylinux1_x86_64.whl
Collecting six (from -r /home/daker/cad/requirements.txt (line 4))
  Downloading https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl
  Saved /tmp/azureworkerw5isl1gv/six-1.12.0-py2.py3-none-any.whl
Successfully downloaded pydicom lxml vtk six
pip download -r /home/daker/cad/requirements.txt --dest /tmp/azureworkerw5isl1gv
pip download --no-deps --only-binary :all: --platform manylinux1_x86_64 --python-version 36 --implementation cp --abi cp36m --dest /tmp/azureworker4273t_as lxml==4.4.1
pip download --no-deps --only-binary :all: --platform manylinux1_x86_64 --python-version 36 --implementation cp --abi cp36m --dest /tmp/azureworker4273t_as vtk==8.1.2
pip download --no-deps --only-binary :all: --platform manylinux1_x86_64 --python-version 36 --implementation cp --abi cp36m --dest /tmp/azureworker4273t_as pydicom==1.2.2
pip download --no-deps --only-binary :all: --platform manylinux1_x86_64 --python-version 36 --implementation cp --abi cp36m --dest /tmp/azureworker4273t_as six==1.12.0

Uploading package...
Uploading 66,88 MB [##############################################################################]
Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Functions in MyFunc:
    converter - [httpTrigger]
        Invoke url: https://MyFunc.azurewebsites.net/api/converter

I still get a 500 Error on azure and the log is the same, i have tried adding the vtk path before importing it but without a success.
import site
site.addsitedir('/home/site/wwwroot/.python_packages/lib/python3.6/site-packages/vtk/')

Do you get different results if you use func azure functionapp publish MyFunc --build-native-deps --additional-packages libgl1-mesa-glx on standard Windows? Or func azure functionapp publish MyFunc --build remote?

No difference between --build-native-deps and --build remote, i get the same error
$ sudo func azure functionapp publish MyFunc --build-native-deps --additional-packages "libgl1-mesa-glx libsm6"
Getting site publishing info...
Running 'docker pull mcr.microsoft.com/azure-functions/python:2.0.12493-python3.6-buildenv'...done
Running 'docker exec -t d0c18c apt-get update'.......done
Running 'docker exec -t d0c18c apt-get install -y libgl1-mesa-glx libsm6'...done
Running 'docker exec -t d0c18c chmod +x /python_docker_build.sh'..done
Running 'docker exec -t d0c18c /python_docker_build.sh'.................................done
Running 'docker cp d0c18c:"/.python_packages/."
Uploading 36,18 MB [##############################################################################]
Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Functions in MyFunc:
    converter - [httpTrigger]
        Invoke url: https://MyFunc.azurewebsites.net/api/converter

$ func azure functionapp publish MyFunc --build remote
Getting site publishing info...
Removing WEBSITE_RUN_FROM_PACKAGE app setting (URL)
Creating archive for current directory...
Perform remote build for functions project (--build remote).
Deleting the old .python_packages directory
Uploading 66,88 MB [##############################################################################]
Remote build in progress, please wait...
Updating submodules.
Preparing deployment for commit id 'e0906bfcee'.
Running oryx build...
Writing the artifacts to a Squashfs file
Parallel mksquashfs: Using 1 processor
Creating 4.0 filesystem on /home/site/deployments/20190910220355.squashfs, block size 131072.

[=============================================================\] 2384/2384 100%

Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072
	compressed data, compressed metadata, compressed fragments, compressed xattrs
	duplicates are removed
Filesystem size 37050.83 Kbytes (36.18 Mbytes)
	18.70% of uncompressed filesystem size (198169.68 Kbytes)
Inode table size 12141 bytes (11.86 Kbytes)
	30.05% of uncompressed inode table size (40402 bytes)
Directory table size 11454 bytes (11.19 Kbytes)
	37.63% of uncompressed directory table size (30437 bytes)
Number of duplicate files found 156
Number of inodes 1067
Number of files 985
Number of fragments 77
Number of symbolic links  0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 82
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)
Uploading built content /home/site/deployments/20190910220355.squashfs -> URL
Reseting all workers for MyFunc.azurewebsites.net
Running post deployment command(s)...
Deployment successful.
App container will begin restart within 10 seconds.
Remote build succeeded!
Syncing triggers...
Functions in MyFunc:
    converter - [httpTrigger]

@maiqbal11 thanks that's what i did at the end also but this means i won't be able to use the consumption plan

@daker, yes, unfortunately that would be the case. We are hoping to have custom containers in consumption as well so that we can enable these scenarios.


How to remove legend?

Hi,
Thank you for this wonderful package. I have been looking for a package like this for a long time.
I have one question. How can I remove the legend if I do not want it?
For example, in ggolot2 I would do p+theme(legend.position = "none").
But I cannot do this in forestplot, I guess that is because the theme is internally overwritten by theme_forest.
So I am wondering if there is a way to work around it?
Thanks!

Hi @Zepeng-Mu,
Can you confirm that you are using ggforestplot::forestplot() function not ggforestplot::plot_all_NG_biomarkers()?
In case of ggforestplot::forestplot(), you can remove the legend as follows:
ggforestplot::forestplot(...) + theme(legend.position = "none").
Best,
Anna

Hi @Zepeng-Mu,
Can you confirm that you are using ggforestplot::forestplot() function, not ggforestplot::plot_all_NG_biomarkers()?
In case of ggforestplot::forestplot(), you can remove the legend as follows:
ggforestplot::forestplot(...) + theme(legend.position = "none").
Best,
Anna

Hi,
I tried again and it is indeed working. Yesterday I was trying to modify other aesthetics such as the color of axis labels in theme, but it did not seem to work. But when I tried just now, it is actually working. I guess yesterday there was some problem with my input.
So I do not have any problems right now, and this issue could be closed.
Thank you so much once again!

Alright! Glad this was solve fast. Not usually the case. And thanks @acichonska !


TextBox HorizontalScrollBar not displayed properly when setting AcceptsReturn to true

        <Style Selector="TextBox.xaml">
            <Setter Property="AcceptsReturn" Value="True"/>
            <Setter Property="TextWrapping" Value="NoWrap"/>
            <Setter Property="HorizontalScrollBarVisibility" Value="Auto"/>
            <Setter Property="VerticalScrollBarVisibility" Value="Auto"/>
        </Style>

        <Style Selector="TextBox.xaml">
            <Setter Property="AcceptsReturn" Value="True"/>
            <Setter Property="TextWrapping" Value="NoWrap"/>
            <Setter Property="HorizontalScrollBarVisibility" Value="Visible"/>
            <Setter Property="VerticalScrollBarVisibility" Value="Auto"/>
        </Style>

The reason this isn't working is that the TextBox.HorizontalScrollBarVisibility property is currently a hack and should be treated as read-only.
You should use the ScrollBar.HorizontalScrollBarVisibility attached property instead (as in WPF) and it should work according to my tests.

@grokys The issue is still present when combining AcceptsReturn=True and TextWrapping=NoWrap
        <Style Selector="TextBox.xaml">
            <Setter Property="Padding" Value="4"/>
            <Setter Property="FontSize" Value="12"/>
            <Setter Property="Background" Value="{StyleResource BackgroundBrush}"/>
            <Setter Property="TextAlignment" Value="Left"/>
            <Setter Property="BorderBrush" Value="{StyleResource BorderBrush}"/>
            <Setter Property="BorderThickness" Value="1"/>
            <Setter Property="AcceptsReturn" Value="True"/>
            <Setter Property="TextWrapping" Value="NoWrap"/>
            <Setter Property="ScrollViewer.HorizontalScrollBarVisibility" Value="Auto"/>
            <Setter Property="ScrollViewer.VerticalScrollBarVisibility" Value="Auto"/>
            <Setter Property="Foreground" Value="{StyleResource ForegroundBrush}"/>
        </Style>

Looks like here https://github.com/Perspex/Perspex/blob/165702c73e3468a78330e080180d6e504d9c7112/src/Perspex.Controls/Presenters/TextPresenter.cs#L41 is unsued variable _canScrollHorizontally related to the TextWrappingProperty.

Hmm, setting ScrollViewer.HorizontalScrollBarVisibility="Visible" on a multiline text box produces this for me:

However it doesn't seem to be respecting the TextWrapping property - is that your problem?

Yes I have same issue:

using
<Setter Property="AcceptsReturn" Value="True"/>
<Setter Property="TextWrapping" Value="NoWrap"/>
<Setter Property="ScrollViewer.HorizontalScrollBarVisibility" Value="Visible"/>
<Setter Property="ScrollViewer.VerticalScrollBarVisibility" Value="Auto"/>

and

using
<Setter Property="AcceptsReturn" Value="True"/>
<Setter Property="TextWrapping" Value="NoWrap"/>
<Setter Property="ScrollViewer.HorizontalScrollBarVisibility" Value="Auto"/>
<Setter Property="ScrollViewer.VerticalScrollBarVisibility" Value="Auto"/>

And this is look I wantexpected:

but do get this I have to set AcceptsReturn to False.

Looking into it, it seems to be a problem with the layout system...

Ok, think I've fixed it this time.


chore: print storage so that we can monitor our disk storage

FYI: with #1402 we might save a lot of space; a lot of unneeded dependencies - tooling for flutter_rust_bridge and whole Flutter SDK disappears from most of the jobs!


Need http proxy

need support for
HTTP_PROXY and NO_PROXY

:rocket: This issue is resolved in version 1.28.2 of JET Pilot!


Update dependencies version

https://github.com/Meruya-Techhnology/network_inspector/pull/50#pullrequestreview-1348446507

Bumped dio to latest version and fixed Dart version constraint :)

Thanks mate, cheers !


[#3815] Add RequestTraceReader and ServerRequestRecorder

#3815

Codecov Report

Merging #3816 into master will increase coverage by 0.11%.
The diff coverage is 40.82%.

@@            Coverage Diff             @@
##           master    #3816      +/-   ##
==========================================
+ Coverage   40.86%   40.97%   +0.11%
==========================================
  Files        2174     2182       +8
  Lines       70772    70602     -170
  Branches     9743     9676      -67
==========================================
+ Hits        28919    28928       +9
+ Misses      39094    38912     -182
- Partials     2759     2762       +3

Impacted Files
Coverage Δ

...pinpoint/plugin/jetty/JettyServerRequestTrace.java
0% <0%> (ø)

...y/interceptor/AbstractServerHandleInterceptor.java
0% <0%> (ø)
:arrow_up:

...e/interceptor/AbstractServerHandleInterceptor.java
0% <0%> (ø)
:arrow_up:

...tty/interceptor/Jetty8ServerHandleInterceptor.java
0% <0%> (ø)
:arrow_up:

...ptor/ServerConnectionHandleRequestInterceptor.java
0% <0%> (ø)
:arrow_up:

.../plugin/websphere/WebsphereServerRequestTrace.java
0% <0%> (ø)

...ty/interceptor/Jetty8xServerHandleInterceptor.java
0% <0%> (ø)
:arrow_up:

...gin/jetty/interceptor/ServerHandleInterceptor.java
0% <0%> (ø)
:arrow_up:

...esin/interceptor/ServletInvocationInterceptor.java
0% <0%> (ø)
:arrow_up:

...pinpoint/plugin/resin/ResinServerRequestTrace.java
0% <0%> (ø)

... and 24 more

Continue to review full report at Codecov.

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


Suggestion: Regex Replies

Being able to set multiple regex with corresponding reply texts so that if the message to the bot matches the regex it will send the corresponding text as auto reply.

Regex matches should be limited to the first message to the bot and the reply upon match in this case should replace the standard auto reply so that it does not interfere when a modmail is being handled by a moderator
Maybe the second message immediately after bot auto reply can be matched too since people sometimes send only 'hi' or '.' as their first message
Regex corresponding replies could be set to snippet names so that you could simply make a snippet and use it manually or have it auto reply. Snippets are also easier to update any time.

Extends #357


Deferred rendering

Is your feature request related to a problem? Please describe.
No. I do not have issues with the current forward rendering implementation. I just think deferred rendering as a nice bonus,
Describe the solution you'd like
Deffered rendering implementation that can be added in the Graphics Compositor.
(I deleted the other questions, since it may be obvious how deferred rendering affects the engine).
For these who don't know what deferred rendering is, I think the wikipedia article is a good starting point : https://en.wikipedia.org/wiki/Deferred_shading (Deferred rendering and deferred shading are terms used interchangeably)
I'm not familiar enough with Stride's Rendering Hardware Interface(RHI). Otherwise I could have gave a try on implementing this myself.

If there is any other issue suggesting deferred rendering, please point it here. Otherwise I request the Epic label.

Nevermind, I didn't notice Stride uses a clustered forward sharing implementation.


[OFFICIAL] Generated Issue: ParserException

Please fill out the details below.
Summary:
Anime ID 51409 fails to parse
Steps to reproduce:
Visit https://api.jikan.moe/v4/anime/51409/full
Additional Details
Jikan Parser Version: v3.2.0@5ee048c2ad235e7cd65b6b251595be97949f5b8c
PHP: 8.0.19
Redis: Connected
Exception: Jikan\Exception\ParserException
Code: 0
Message: Failed to parse 'https://myanimelist.net/anime/51409/'
Trace: /var/www/jikan-rest/vendor/jikan-me/jikan/src/Exception/ParserException.php on line 24
Request: GET /v4/anime/51409/full

Sentry: https://sentry.io/share/issue/4a48eb61c19c44c6b1d85944014f2d83/

Will be resolved by https://github.com/jikan-me/jikan-rest/pull/268


Adds Service Accounts tab

Description
Updated UI to make use of new separate Internal/service accounts API endpoints being added to security plugin backend via PR https://github.com/opensearch-project/security/pull/2786
Differently From Internal Accounts, 'Delete' and 'Create' Buttons were removed for Service Accounts.
'Internal Users' renamed to 'Internal Accounts' to be in line with 'Service Accounts' as discussed on https://github.com/opensearch-project/security/issues/2842
Category
Enhancement
Why these changes are required?
Improve UX
What is the old behavior before changes and new behavior after changes?
All accounts had to be requested, without filtering Internal/Service
Issues Resolved
#2704
Testing
Manual test on UI
Check List

[ ]  New functionality includes testing
[ ]  New functionality has been documented
[x]  Commits are signed per the DCO using --signoff

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.

@samuelcostae  We've got an upcoming 2.10 release and I'm reviewing outstanding pull requests, would you like this pull request to be considered for inclusion?
Some commits are missing the DCO and tests failing, is this ready to review?  Let me know and I'll start to take a look

working on adding tests to new service account panel

Here is the final look and feel:

Thank you @samuelcostae. One final question, with this PR, we are not adding the functionality to Create Service account, but if one is already created we can edit update and delete it. Is that correct?

@DarshitChanpura I would recommend not making changes on the frontend at the moment. Service accounts are quite nascent and used for extensions, which is not being developed on at the moment.
Is there any plan to add an experimental label on this for the initial release?
There is text on the screen about updating roles mappings of service accounts, but we have also discussed limiting service accounts of the reserved indices of the extension/plugin that they are associated with. I'm for creating UX for this feature long term, but I think its pre-mature to add UX around service accounts.

@DarshitChanpura I would recommend not making changes on the frontend at the moment. Service accounts are quite nascent and used for extensions, which is not being developed on at the moment.
Is there any plan to add an experimental label on this for the initial release?
There is text on the screen about updating roles mappings of service accounts, but there has also been discussion around limiting service accounts to the reserved indices of the extension/plugin that they are associated with. I'm for creating UX for this feature long term, but I think its pre-mature to add UX around service accounts.

Ahh.. makes sense. What do you think about enabling the view with a feature flag too?

@cwperks  As we discussed on the call Thursday, the feature flag won't be necessary, can you review the PR as one more is needed for the merge? Thanks

@DarshitChanpura  Thanks for syncing up the branch with main, it seems the Cypress tests  failures at the same occurring in the other branches.
I think that  those errors were mentioned in the call today and already being looked at, right?

Yes, Cypress failures are seem unrelated to the changes in this PR.

@samuelcostae Looks like there are still a number of outstanding items - can you follow up on those unresolved conversations?

Hi @cwperks Could you please review this once more? Thanks

Hey @samuelcostae , it still feels a bit pre-mature to me to add UX but I will defer to @scrawfor99 and @peternied who have been more involved with the planning and delivery of this feature. For the first time a new feature is released like this, I think it would be appropriate to have an experimental label which implies that a future minor version can make breaking changes to the feature and that backward compatibility will not be guaranteed.
IMO I would also like to keep the terminology internal users because it is prevalently used. I see why internal accounts would be more consistent with service accounts, but internalusers is used in API routes like this: https://opensearch.org/docs/latest/security/access-control/api/#get-user
From what I understand, in an initial release service accounts will not be very interesting from an end user perspective. They are completely restricted to a set of protected indices associated with the extension/plugin that they represent. Even if its possible to map a service account to roles, the action would not result in any new behavior granted to the service account because its restricted to a set of indices strongly.

As it pertains to this particular PR, I do see that there is an option to Edit the account. From what I understand, a service account is currently distinguished from a regular account because it has an attribute with a key of service and a value set to true. Using the UX from this PR, is it possible that an admin can hit the Edit button and demote the account to a regular account?

Using the UX from this PR, is it possible that an admin can hit the Edit button and demote the account to a regular account?

Correct, this is currently possible.   @peternied  Is this something we would like hide in the front-end?

@scrawfor99  friendly ping

@DarshitChanpura  seems you need to approve again after the changes :)

@samuelcostae Could you look into Unit test failures?

Same with @peternied , I don't have strong opinions so I defer to the rest of the team.
I see that there's a column for backend roles, is that something that can be added to a service account?
If extensions was further along, I would also recommend an admin page for extensions where security settings for extensions could be configured along with other settings.

I see that there's a column for backend roles, is that something that can be added to a service account?

If we plan to, then let's address it in a follow-up PR @samuelcostae . As I see no more blockers, I'll merge this now.

@samuelcostae Could you look into 2.x backport failure


Improve CI workflow

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

Project coverage is 99.45%. Comparing base (13d312d) to head (8325d7b).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #201   +/-   ##
=======================================
  Coverage   99.45%   99.45%
=======================================
  Files           6        6
  Lines         182      182
  Branches       27       27
=======================================
  Hits          181      181
  Partials        1        1

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


Changes to some instructions in the tutorial.md file

Link to pull request with suggested changes: #9329

Hi, I'm outreachy applicant, i will be working on this issue.

Hi, I'm outreachy applicant, i will be working on this issue.

Hello, I already made a pull request suggesting some changes so you can look through more of the documentation and check for more issues to fix.

noted, thanks

Welcome, have you been through the contributor checklist for documentation?

noted, thanks

Welcome, have you been through the contributor checklist for documentation?

yes, i launched to get started with wagtail tutorial

@DokuaAsiedu when opening an issue, make sure to describe a specific problem / feature request / change you think is needed. Just opening an issue to link to a pull request only creates noise for people who triage Wagtail’s issues.

@DokuaAsiedu when opening an issue, make sure to describe a specific problem / feature request / change you think is needed. Just opening an issue to link to a pull request only creates noise for people who triage Wagtail’s issues.

Alright sorry about that


Docker doesn't use Go filepath.Match, fix docs

File: engine/reference/builder.md
The section ".dockerignore file" states that Go's filepath.Match rules are used although this is actually not the case.
In dockers source you can find the following comment:
filepath's Match() has some really weird rules that are inconsistent
so instead of trying to dup their logic, just call Match() for its
error state and if there is an error in the pattern return it.
If this becomes an issue we can remove this since its really only
needed in the error (syntax) case - which isn't really critical.

You might have a look on docker/docker#29014 as well

I'll take this up!

I cannot find a builder.md file in the engine folder to make the changes. Am I missing something?

@shubheksha let me take a look, the file might have moved.

@shubheksha Okay, this is a bit tricky, but do-able :-)

we have a few sets of reference files that were originally in the docker/docker/ repository and never moved (when we moved the rest of the documentation to its own repository). API docs, and some sets of commands, stay with the codebase. This is one of them.

So to work on this file, you would have needed to clone the docker/docker repository and there find the file in docs/reference/builder.md

However, Solomon just open-sourced docker/docker today at the conference to moby/moby! So if you already had cloned docker/docker you will be redirected to moby/moby.

If you are starting with this repository for the first time, then clone [moby/moby/](https://github.com/moby/moby](https://github.com/moby/moby). You will find the file at moby/moby/docs/reference/builder.md.

Thanks for the detailed info :)
Should I just remove the line which claims that Go filepath.Match is used to fix this?

@londoncalling, found the text relevant to this issue:
"Matching is done using Go's filepath.Match rules. A preprocessing step removes leading and trailing whitespace and eliminates . and .. elements using Go's filepath.Clean. Lines that are blank after preprocessing are ignored.
Beyond Go's filepath.Match rules, Docker also supports a special wildcard string ** that matches any number of directories (including zero). For example, **/*.go will exclude all files that end with .go that are found in all directories, including the root of the build context."

@shubheksha yes I'm looking through this, it's a bit complicated. Let's try to figure it out together.

@thaJeztah @duglin @johnstep Can you give us some guidance on docs fixes with regard to this? It looks like the related issues in the codebase are fixed (https://github.com/docker/docker/issues/29014) but it is not totally clear whether docs fix is to remove all mention of Go's filepath.Match rules. If so, we need to describe the rules that are in place and might need some guidance here.
cc: @shubheksha

Any update on this?

No response from Dev yet .. someone else at Hackathon was looking at it as
well but I don't think any of us is going to figure it out without input
from Dev.
On Thu, Apr 20, 2017 at 3:47 AM Shubheksha Jalan<EMAIL_ADDRESS>wrote:

Any update on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/issues/761#issuecomment-295638238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALHuA50LIKL4YM2fPfOhDzbj5CDFDAMAks5rxxuXgaJpZM4LBEnE
.

Sorry @shubheksha we did not get you the info in time for the hackathon!

@mstanleyjones, no issues! 😄

@thaJeztah ping? I'd like to get this one taken care of, but we need some technical guidance.

Closing due to lack of info.


[Translation] Mongolian Cyrillic language translation

Please add a Mongolian Cyrillic language translation to Crowdin.
Locale: mn_MN

I can only find Mongolian, but no Mongolian Cyrillic in the crowdin language list. And there is no customized language name option. Should I add Mongolian?

Yes please. I just wanted to give an information that language is Cyrillic. 😅

Could you tell me your name in crowdin so that I can add you as proofreader .

My name on Crowdin is "Almas". Thanks.
https://crowdin.com/profile/almas

@almas done.


Add doc comments to each function/method

Mostly so it can be read with an LSP - in neovim, doing shift+k will show you the documentation around a function (at least with my config). We should add something like this to rawterm.

hello @Ttibsi  can i work on this issue?

@renu-123-pixel Go ahead - please make a PR with your changes in a separate branch. Thanks. :)

would u let me know like how much time do i get to get this commit done?

can u please explain this .... do we need to add comment in rawterm document ?

jus comment?

Yea, above each function in the source code, please add information that might be useful to know alongside the function signature. If there are any parameters, explain what those should be. (Same for the return types). It shouldn't be more than a few lines, and should intend to make using the library easier instead of just repeating information that's already there.


Drop support for editor 10.x releases

Overview
This PR drops support for @lblod/ember-rdfa-editor 10.x range.
Note: this PR is not breaking, the 10.x range of the @lblod/ember-rdfa-editor package never contained stable releases.
We managed to release the new editor version as a 9.x minor release (and the alpha 10.x releases are thus obsolete).
How to test/reproduce
N/A
Checks PR readiness

[x] UI: works on smaller screen sizes
[x] UI: feedback for any loading/error states
[x] Check if dummy app is correctly updated
[x] Check cancel/go-back flows
[x] changelog
[x] npm lint
[x] no new deprecations

I'll merge this so I don't have to immediately merge/rebase my PR for updating appuniversum.


Training Mini-batches of data (without labels) for unsupervised learning problem

Hi Everyone,
Has anyone trained mini-batches of data for an unsupervised learning problem?
The feed_dict uses the label and in an unsupervised setting. How do you overcome that? Could we use fake labels that never contribute to the loss function?
Basically, I want to iterate over my huge dataset and then optimize a custom loss function. However, I couldn't figure out how to retain my training parameters (weights) when using a new mini-batch from the data explicitly.
For example, the whole dataset is 6000 points and the mini-batch size is 600.
Currently, for every mini-batch I could only use new independent weight parameters because the weights are initialized based on the data points from this mini-batch. When we optimize the loss over the first mini-batch of 600 data points, we get some optimized weights. How does one use these weights to optimize the next mini-batch of 600 data points and so on. The problem is we cannot use a shared global variable.
Any help or pointers in this regard would be really appreciated. Thanks in advance!

Variables should maintain state between calls to run so unless you're reinitializing the weights between every minibatch, you shouldn't have an issue. An example demonstrating your problem would be helpful.
Also, his question would be better suited for Stack Overflow than a GH issue

Hi Adam,
I researched on stackoverflow forums but couldn't find anything relevant for mini-batches over unsupervised data. Hence, I posted here after a friend's suggestion. My apologies for the same.
'f' is my whole dataset say text data of N points with dimension D
U is cluster centroid with K clusters again of dimension D
I define my variables as below:
F = tf.Variable(f.astype(np.float32), name='F')
U = tf.Variable(u.astype(np.float32), name='U')
FMod = tf.reshape(F, [N/K, K, D], name='FMod')
UMod = tf.reshape(U, [1, K, D], name='UMod')

Then I define a custom loss or objective function as 'objective'
Next I use an optimizer
optimizer = tf.train.AdamOptimizer(learning_rate)
train_W = optimizer.minimize(objective, var_list=[F, U])

Finally, I evaluate the variable as
with tf.Session() as sess:

    # Initialize all the variables
    sess.run(init_op)

    for n in range(noEpochs):

        objval1 = sess.run([train_W, objective])

The thing I am stuck at - is to iterate over batches of my data 'f' which is ultimately used in the optimizer train_W. If I have a for loop over these mini-batches, I will assign a new variable train_W for each of these iterations. How can I pass this value so that it can be used in the next mini-batch?
The full code can be found at this link: Semi-supervised Clustering

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Issue with interactions of random effects

I'm currently having issues fitting a model with interactions in the random effects. This model does work in R with lme4. The model I'm trying to fit is:
mdl = GeneralizedLinearMixedModel(@formula(response ~ 1 + (1|x/y)), dat, Bernoulli());
It works without the y term, i.e.:
mdl = GeneralizedLinearMixedModel(@formula(response ~ 1 + (1|x)), dat, Bernoulli());
works just fine.
The error I get is:
MethodError: no method matching getindex(::DataFrames.DataFrame, ::Expr) Closest candidates are:   getindex(::DataFrames.DataFrame, !Matched::Colon) at C:\Users\Danny.Vargovick\.julia\packages\DataFrames\KUWId\src\dataframe\dataframe.jl:261   getindex(::DataFrames.DataFrame, !Matched::Colon, !Matched::Colon) at C:\Users\Danny.Vargovick\.julia\packages\DataFrames\KUWId\src\dataframe\dataframe.jl:321   getindex(::DataFrames.DataFrame, !Matched::Union{Integer, Symbol}) at C:\Users\Danny.Vargovick\.julia\packages\DataFrames\KUWId\src\dataframe\dataframe.jl:249   ... Stacktrace:  [1] (::getfield(StatsModels, Symbol("##18#19")){DataFrames.DataFrame})(::Expr) at C:\Users\Danny.Vargovick\.julia\packages\StatsModels\AYB2E\src\modelframe.jl:145  [2] iterate at .\generator.jl:47 [inlined]  [3] collect_to!(::Array{Array{Int64,1},1}, ::Base.Generator{Array{Any,1},getfield(StatsModels, Symbol("##18#19")){DataFrames.DataFrame}}, ::Int64, ::Int64) at .\array.jl:656  [4]
I'm running Julia version 1.0.2.
Any help is much appreciated!

That slash syntax on the groups isn't currently supported (which is the cryptic error your seeing) and I'm actually not sure what exactly it does in lme4; fit random effects of x nested in y?
Maybe @dmbates can suggest an alternative way of specifying the same model.  Perhaps with separate random effects by x and y?

Thanks, @kleinschmidt.
I was under the impression that the slash syntax was supported. From http://dmbates.github.io/MixedModels.jl/latest/MultipleTerms/:

For convenience, a model with multiple, nested random-effects terms can be specified as
strength ~ 1 + (1 | batch/cask)
which internally is re-expressed as
strength ~ 1 + (1 | batch) + (1 | batch:cask)

I've also tried
mdl = GeneralizedLinearMixedModel(@formula(response ~ 1 + (1|x) + (1|x:y)), dat, Bernoulli()); mdl = GeneralizedLinearMixedModel(@formula(response ~ 1 + (1|x:y)), dat, Bernoulli());
and that didn't work either.
FWIW, in R with lmer4, the (1|x/y) syntax will produce a random effect for x and a random effect for the interaction of x and y.