[pt] Localize content/en/docs/languages/net/_index.md and  getting-started.md

Issue to localize the following pages to pt:

content/en/docs/languages/net/_index.md
content/en/docs/languages/net/getting-started.md

Puxando essa issue


Merge the first two tutorials and simplify

Is your feature request related to a problem? Please describe.
Merging getting started and flexible inference will make the entry to using the toolbox easier.
One line inference should be avoided.
Describe the solution you'd like
Merge tutorial 0 and 1 and make it clearer for domain scientists what each section corresponds to in their application.
Delete the one line inference.
Describe alternatives you've considered
Keep them as they are just make them clearer.
Additional context

[x] Merge content of 0 and 1
[x] #1075
[x] Ensure README.md tutorial locations/names is updated
[x] remove the one line inference version in tutorial
[x] remove one line inference version and replace by short example in README.md

I turned the docs website updates int o a separate issue


fix(format-to-jsx): use "key in dict" to tell if key is found

Using if (replaceValue) { ... } will yield the false positive: "0" or zero as a number. We prevent that by a more accurate key-in-dictionary check.

Pull Request Test Coverage Report for Build 361

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.515%

Totals

Change from base Build 331:
0.0%

Covered Lines:
138

Relevant Lines:
138

💛  - Coveralls

@matmalkowski Reverted. The change left is just spacing or something irrelevant.

@PoomSmart Please also create a new PR for i18n-jsx once this package gets published and update the dependency as a fix to it as well!

:tada: This PR is included in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


travis: run deploy as final stage

Describe what this PR does
The deploy: section is executed as part of each successful job. That
means the container images are built and pushed many times during
testing after a push/merge event on the master branch.
By creating a deploy stage and listing it after the tests, it is
guaranteed to run only once after all tests have succeeded. By adding a
condition to only run the stage on the master branch for push events,
the images should only get built+pushed after a PR has been merged into
the master branch.
See-also: https://docs.travis-ci.com/user/conditional-builds-stages-jobs#Specifying-conditions

@Mergifyio backport release-v2.1

This can be backported once #999 is merged.


Expose OpenSearch configuration properties in the REST API

References

Required by https://github.com/DSpace/dspace-angular/pull/2475

Description
This PR adds two configuration variables to the REST API whitelist in order for the OpenSearch autodiscovery tag to work properly.
See also #9056
Instructions for Reviewers
You can test the DSpace Angular PR with this one.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[x] My PR passes Checkstyle validation based on the Code Style Guide.
[x] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[x] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[x] If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
[x] If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

I see this enables me to access my websvc.opensearch.shortname configuration property at the http://localhost:8080/server/api/config/properties/websvc.opensearch.shortname endpoint:
{
  "name" : "websvc.opensearch.shortname",
  "values" : [ "CGSpace" ],
  "type" : "property",
  "_links" : {
    "self" : {
      "href" : "http://localhost:8080/server/api/config/properties/websvc.opensearch.shortname"
    }
  }
}

The others work as well.


everything done

Think im good My gosh

Added another Push just cant seem to get the boxes to level in to 2 rows but fixed everything else

Made a few changes to make 800px Responsive design look correct.


Unable to get any query to run on GitHub's API - .then is not a function error

I must admit that I am a beginner with JavaScript and web based technologies.
I followed issues #2 , #21 and #40 along with the code taken straight from this SO answer (corresponding #21), but I get the following error in console -
TypeError: graph(...).then is not a functiongraphql.html:59:4

I made a html file with the following content and all I do is open it in the browser and see the console.
Following is the content of the html file -
<!DOCTYPE html>
<html>
<head>
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <meta content="text/html;charset=utf-8" http-equiv="Content-Type">
</head>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js"></script>
<script src="graphql.min.js"></script>
<script>
var graph = graphql("https://api.github.com/graphql", {
  headers: {
    "Authorization": "Bearer <my id>"
  },
  asJSON: true
});
graph(`
    query repo($name: String!, $owner: String!){
        repository(name:$name, owner:$owner){
            id
        }
    }
`, {
  name: "freeCodeCamp",
  owner: "freeCodeCamp"
}).then(function(response) {
  console.log(response);
}).catch(function(error) {
  console.log(error);
});
</html>

Could you please tell me how should I make it display the response json in the console ?

Any comments on this? I think many folks have got it working, so it should be easy enough. Any hint would be much appreciated.

try this
<!DOCTYPE html>
<html>
<head>
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <meta content="text/html;charset=utf-8" http-equiv="Content-Type">
</head>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js"></script>
<script<EMAIL_ADDRESS><script>
var graph = graphql("https://api.github.com/graphql", {
  headers: {
    "Authorization": "Bearer <my id>"
  },
  asJSON: true
});
graph(`
    query repo($name: String!, $owner: String!){
        repository(name:$name, owner:$owner){
            id
        }
    }
`)({
  name: "freeCodeCamp",
  owner: "freeCodeCamp"
}).then(function(response) {
  console.log(response);
}).catch(function(error) {
  console.log(error);
});
</script>
</html>

graph returns a function, you can then call that function with the variables for the gql query.

@tuananh I am sorry to ask this but how exactly do I do that?

@tuananh I am sorry to ask this but how exactly do I do that?

see the code snippet above. it's just a tiny bit different with yours.

@tuananh  I still get the same error.

All I do is open the html file, Right Click and select Inspect and then go-to Console tab. Is this the correct way to check for the response json ?

try copy again, what i get is 401 error bad cred because i dont have api key

@tuananh Got it working. Thanks a lot!!


Copy missing files

Copy the setup files
Reported in the following post https://www.openmicroscopy.org/community/viewtopic.php?t=8163&p=17699#p17699

I take it this needs the autogen build to run to copy the extra content across?

it will but I still have one thing to do on the omero-install front before we do the autogen

Ah ok, thanks for the clarification.

Related omero-install PR https://github.com/ome/omero-install/pull/126

Since we do not have a job anymore and cannot adjust the develop one w/o resurrecting a number of other jobs, I will open a PR manually copying the missing file and updating the walkthrough

--rebased-to #1585

Closing this PR since the copy will happen manually


performance plot

I have changed the plotting by using Plotly, the only thing I'm not sure about is this coloring thing

make it look somewhat like that, with colors as arguments with reasonable defaults; loss is log scale

Now the visualization makes Plotly plot instead -- the only thing I'm unsure about is this coloring thing:

make it look somewhat like that, with colors as arguments with reasonable defaults; loss is log scale

lgtm, nice work

Two things to follow up on:

I think we want the loss (y axis) to be log scale.

We should make color an argument of visualize_per_token_category (it can default to "purple")

Yeah I just thought that we already have data as in logprobs, so the loss calculated is already in log

I think we want the loss (y axis) to be log scale.

Yeah, I think you're right. Jett, thoughts? You mentioned wanting a log
scale in an earlier comment, were you just referring to charting logprob?
On Mon, Feb 19, 2024, 6:01 PM Siwei Li @.***> wrote:

Yeah I just thought that we already have data as in logprobs, so the loss
calculated is already in log

I think we want the loss (y axis) to be log scale.

—
Reply to this email directly, view it on GitHub
https://github.com/delphi-suite/delphi/pull/35#issuecomment-1953369727,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC5BY5AC5BBIH5EEQNXG4TYUP7WVAVCNFSM6AAAAABDJMJ7RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGM3DSNZSG4
.
You are receiving this because your review was requested.Message ID:
@.***>

just had a meeting with Sil, a few small bits to address and we can merge

Todos:

take log/linear kwarg options
coloring kwargs fo the graph
making dots larger


Suggestion, Add "Cancel" button on picker

Please add the cancel button on picker, show that user can dismiss the picker for example by mistake user open the picker and  don't want to select the image. or not want to select any image then he/she able to dismiss the picker on cancel button click. I know the done button click dismiss. But as per user experience we need add the "cancel" button.

@vinod1988
Thanks for your useful suggestion! I think I'll add the "cancel" button via an optional property :)

Check the 2.4.1 branch:https://github.com/zhangao0086/DKImagePickerController/commit/63df02882b88e851c1ecbf71a6ea98084ee5347d

Hello. I set showsCancelButton to true, but the button shows not show. I'm using the obj-c API.
Thanks!


add readavailable(::BufferedInputStream)

Codecov Report

Merging #46 into master will decrease coverage by 25.89%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
- Coverage   85.38%   59.49%   -25.9%
==========================================
  Files           5        6       +1
  Lines         301      432     +131
==========================================
  Hits          257      257
- Misses         44      175     +131

Impacted Files
Coverage Δ

src/bufferedinputstream.jl
69.16% <0%> (-27.76%)
:arrow_down:

src/io.jl
50% <0%> (-50%)
:arrow_down:

src/BufferedStreams.jl
50% <0%> (-25%)
:arrow_down:

src/emptystream.jl
45.94% <0%> (-23.45%)
:arrow_down:

src/bufferedoutputstream.jl
54.8% <0%> (-17.35%)
:arrow_down:

src/deprecated.jl
0% <0%> (ø)

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 d7806bd...c488bc3. Read the comment docs.

Hey @jkroso, thanks for adding this! Before it's merged, could you add a very simple unit test to cover the function to satisfy codecov?

@BenJWard Sweet done!


[$125] Category - Clicking on a very long parent child category name scrolls the page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.71-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Pre-conditions:

Create a workspace
Create a category name with long parent child relationship (e.g: "A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done"

Navigate to staging.new.expensify.com
Open workspace chat
Click on Plus icon inside compose box > Submit expense > Manual > Enter amount > Click next
Open category list
Click somewhere down the long category list but do not use the mouse scroll wheel

Expected Result:
Nothing should happen
Actual Result:
The page scrolls down
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/52665374-9639-40fd-90a5-ca1a736cc5ae
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~017d72668f5e4a79c3
Upwork Job ID:<PHONE_NUMBER>791183872
Last Price Increase: 2024-05-17
Automatic offers:

nkdengineer | Contributor | 0

Issue OwnerCurrent Issue Owner: @sobitneupane

@sakluger  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

Proposal
Please re-state the problem that we are trying to solve in this issue.
The page scrolls down
What is the root cause of that problem?
We have the logic here to change the focusedIndex when a option is focused
https://github.com/Expensify/App/blob/807c945ef8edabe86cc62f16c866aa754db8750b/src/components/SelectionList/BaseSelectionList.tsx#L362
And then the page scrolls because of the logic here
https://github.com/Expensify/App/blob/807c945ef8edabe86cc62f16c866aa754db8750b/src/components/SelectionList/BaseSelectionList.tsx#L235-L237
What changes do you think we should make in order to solve the problem?
We should check if the options is disabled we will do nothing instead of changing the focusedIndex
onFocus={() => {
    if (isDisabled) {
        return;
    }
    setFocusedIndex(normalizedIndex);
}}

https://github.com/Expensify/App/blob/807c945ef8edabe86cc62f16c866aa754db8750b/src/components/SelectionList/BaseSelectionList.tsx#L362
OPTIONAL: We can also do nothing if we can't select multiple option so the page will not scroll briefly when we select a option and navigate to another page.
What alternative solutions did you explore? (Optional)
If we always want to not trigger onFocus function when the item is disabled, we can do this in BaseListItem
onFocus={() => {
    if (isDisabled && !item.isSelected) {
        return;
    }
    onFocus?.();
}}

https://github.com/Expensify/App/blob/807c945ef8edabe86cc62f16c866aa754db8750b/src/components/SelectionList/BaseListItem.tsx#L84
Result
https://github.com/Expensify/App/assets/161821005/5e39e822-c725-4d83-baaf-6c102fe493de

This seems pretty low-impact and not to big of a fix, I'm going to change the price to $125. Let me know if you disagree.

Thanks for the proposal @nkdengineer
But why is it being displayed in multiple lines like that? I tried adding some long paragraphs without :, it is being displayed only in two lines max with ellipsis.

@sobitneupane The category with : is  long parent child relationship and each category that is separated by : will be displayed in a line.

The category with : is long parent child relationship and each category that is separated by : will be displayed in a line.

@nkdengineer Can you please link the code/issue that is responsible for this feature.

Apologies if this is the wrong place to ask this, I am not overly familiar with the expensify ticketing process, but is there not another bug here? The category hierarchy is so large that the innermost child label is rendered off of the screen. Is that not an issue...? Or would that be handled in a different ticket?

@sobitneupane The option tree function is add from this PR https://github.com/Expensify/App/pull/25777

Reassigning while I'm OOO through May 31.

Thanks for the update @nkdengineer
Proposal from @nkdengineer looks good to me.
🎀 👀 🎀 C+ Reviewed

@sobitneupane this PR is ready for preview.

@sobitneupane could you please complete the BZ checklist?

Bumped in Slack.

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ]  [@sobitneupane] The PR that introduced the bug has been identified. Link to the PR:

Option Tree was implemented by https://github.com/Expensify/App/pull/25777 PR to implement category tree.

[ ]  [@sobitneupane] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

Not Required.

[ ]  [@sobitneupane] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

Not Required.

[ ]  [@sobitneupane] Determine if we should create a regression test for this bug.

Yes.

[ ]  [@sobitneupane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal
Pre-conditions:

Create a workspace
Create a category name with long parent child relationship (e.g: "A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done: A: Very: Long: Category: List: Done"

Open workspace chat
Click on Plus icon inside compose box > Submit expense > Manual > Enter amount > Click next
Open category list
Click somewhere down the long category list but do not use the mouse scroll wheel
Verify that the list is not scrolled on clicking the disabled category in category tree.

Do we agree :+1: or :thumbsdown:

Summarizing payment on this issue:
Contributor+: @sobitneupane $125, please request on Newdot

$125 approved for @sobitneupane

@sakluger @JmillsExpensify Hi, I'm the assigned contributor that raised the PR, and wasn't paid here.
Could you help reopen the issue to handle that?
Thanks

@nkdengineer I'm so sorry for missing your payment. I've completed the payment now, everything should be set here.


adds option of enforcing a version check

If this feature is turned on (currently defaults to off), TaxBrain
will check if the version of the remote workers is the same as the
local version of taxcalc, and raise an error if there is not a match

Addresses #29 and #30


Exited process when members-api errors

refs https://github.com/TryGhost/Ghost/issues/12448
This adds handling to force the process to exit when we receive an error
from the members-api.

@naz I'm going to merge this today as per the messages in Slack - but would be interested to hear what you think about calling process.exit directly here

@naz I'm going to merge this today as per the messages in Slack - but would be interested to hear what you think about calling process.exit directly here

@allouis imo a safer and more universal way to shutdown Ghost is through shutdown() method. This is a central place that takes care of properly closing connections, stopping job execution and maybe some other bits could come here later on.
The main problem I see with straight up process.exit(1) is we might lack logging if pipes don't flush and it would be impossible to track any other generic shutdown handling if ghost calls process.exit(1) at multiple places.

Okay cool :relaxed: I notice that method forces exiting with a code of 0 which I think is wrong for this usecase, do you think I should call the stop() method instead, and then call process.exit OR maybe update shutdown() to accept an optional exit code?

Good point! I think we should modify the shutdown method to accept an error (or exit code) :thinking: While looking at the method saw it uses process.exit(-1). This is quite confusing bth, -1 is not a standard process exit code, am wondering if it's used for any special handling anywhere? I'll do some digging on the -1 topic

I think it's actually OK, in this one particular case to just abort the process, as it's just in development mode when something really bad has happened.
As an aside though, how do I get out of this error? I tried clearing the keys out of my DB but I still can't start Ghost.


"Most frequent bitstring from sampling" is not working for both Max-cut problem and numberpartition problem

I was trying to see how QAOA works through the two examples given. But in both the cases, it is showing the same error in the last part to print "most frequent bitstring from sample".

Thanks for reporting this @riyasett . Would it be possible for you to share the code-snippet that produced this error so I can try to reproduce this on my end?

Oh yes... of course! I have attached the jupyter notebook herewith and the
screenshot of the part which has some problem of being executed.
[image: Inline image 1]
On Sat, Nov 18, 2017 at 7:33 PM, Johannes Otterbach <
<EMAIL_ADDRESS>wrote:

Thanks for reporting this @riyasett https://github.com/riyasett . Would
it be possible for you to share the code-snippet that produced this error
so I can try to reproduce this on my end?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rigetticomputing/grove/issues/107#issuecomment-345461524,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Affj3YSZKDwSy-giWl_i4_Y3Qepo2kBWks5s3yLxgaJpZM4QjA6h
.

--
Yours sincerely,
Riya Sett

@riyasett I can't seem to find the notebook. Maybe github email filtered it out?

Oh, I am extremely sorry. I sent you the notebook through email. I am attaching it here again.

I cannot attach the notebook (.ipynb) here...

hmm .. I unfortunately still can't see the full code to reproduce the error. Can you turn the notebook into a small script that I can run? You can also copy-and-paste the code you are running into a comment here.

import numpy as np
import pyquil.api as api
from pyquil.paulis import PauliTerm, PauliSum
import networkx as nx
from scipy.optimize import minimize
from grove.pyqaoa.qaoa import QAOA
CXN = api.SyncConnection()
def print_fun(x):
print(x)
def maxcut_qaoa(graph, steps=1, rand_seed=None, connection=None, samples=None,
initial_beta=None, initial_gamma=None, minimizer_kwargs=None,
vqe_option=None):
if not isinstance(graph, nx.Graph) and isinstance(graph, list):
    maxcut_graph = nx.Graph()
    for edge in graph:
        maxcut_graph.add_edge(*edge)
    graph = maxcut_graph.copy()

cost_operators = []
driver_operators = []
for i, j in graph.edges():
    cost_operators.append(PauliTerm("Z", i, 0.5)*PauliTerm("Z", j) + PauliTerm("I", 0, -0.5))
for i in graph.nodes():
    driver_operators.append(PauliSum([PauliTerm("X", i, -1.0)]))

if connection is None:
    connection = CXN

if minimizer_kwargs is None:
    minimizer_kwargs = {'method': 'Nelder-Mead',
                        'options': {'ftol': 1.0e-2, 'xtol': 1.0e-2,
                                    'disp': False}}
if vqe_option is None:
    vqe_option = {'disp': print_fun, 'return_all': True,
                  'samples': samples}

qaoa_inst = QAOA(connection, len(graph.nodes()), steps=steps, cost_ham=cost_operators,
                 ref_hamiltonian=driver_operators, store_basis=True,
                 rand_seed=rand_seed,
                 init_betas=initial_beta,
                 init_gammas=initial_gamma,
                 minimizer=minimize,
                 minimizer_kwargs=minimizer_kwargs,
                 vqe_options=vqe_option)

return qaoa_inst

Sample Run:
Cutting 0 - 1 - 2 graph!
inst = maxcut_qaoa([(0, 1), (1, 2)], steps=2, rand_seed=42, samples=None)
betas, gammas = inst.get_angles()
probs = inst.probabilities(np.hstack((betas, gammas)))
for state, prob in zip(inst.states, probs):
print(state, prob)
print("Most frequent bitstring from sampling")
most_freq_string, sampling_results = inst.get_string(
betas, gammas)
print(most_freq_string)

Thanks @riyasett, this will help me in reproducing your error!

On Mon, Nov 20, 2017 at 10:48 PM, Johannes Otterbach <
<EMAIL_ADDRESS>wrote:

Thanks @riyasett https://github.com/riyasett, this will help me in
reproducing your error!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rigetticomputing/grove/issues/107#issuecomment-345843004,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Affj3X8tKGKiuVtPQ0pDt9cpxeMva-ypks5s4fPKgaJpZM4QjA6h
.

--
Yours sincerely,
Riya Sett

@riyasett we just pushed a fix to master for your problem #109. Thanks @jonathanward for this. We will have a release of Grove coming up soon that will contain this fix.

Thank you very much for this...
On Tue, Nov 21, 2017 at 9:12 PM, Johannes Otterbach <
<EMAIL_ADDRESS>wrote:

@riyasett https://github.com/riyasett we just pushed a fix to master
for your problem #109 https://github.com/rigetticomputing/grove/pull/109.
Thanks @jonathanward https://github.com/jonathanward for this. We will
have a release of Grove coming up soon that will contain this fix.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rigetticomputing/grove/issues/107#issuecomment-346146871,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Affj3fUYpfi-gU5TBGqEf4dmj5iY_buQks5s4y6WgaJpZM4QjA6h
.

--
Yours sincerely,
Riya Sett

@riyasett You're welcome! We just pushed a new release of grove. v1.4.0 I hope your problem is fixed there. I'll close this ticket, but feel free to reopen if you encounter the issue again!


replaceDependencies: review and refactor

Description of changes
This is a work in progress review of the amazing upstream 257234.
The local branch is constantly rebased in order to understand the changes.
Tweaks:

[x] Removed issue references in commit messages to avoid repeated pinging of people when force-pushing.
[x] Rebased some latter modifications of replace-dependencies into previous commits to reduce the patch size (done, except for code related to content-addressed derivations).

Track the work in progress in https://github.com/bryango/nixpkgs/pull/8.
Diff with upstream: https://github.com/bryango/nixpkgs/compare/replacedependencies-gen2..replacedependencies
Apply upstream force pushes by amending with two dot patches, such as:

[x] https://github.com/NixOS/nixpkgs/compare/56ddab9deed725525237122aa9621c2ada01ff04..87d7feea533684d72e75f2c3b09747e279db709d

To alois31 in case you are accidentally pinged by github: sorry for the noise... This is not yet ready for your review, but thank you very much for the great work! I hope I can eventually contribute to the review process, but I am very slow...

Closing as it has been merged upstream.


Problem using Nexus to proxy docker hub

Describe the bug
I am trying to setup nexus in the AzureTRE environment to proxy docker hub. I believe I have nexus setup correctly and appropriate docker hosts added the the firewall rules. When I try to run docker login from a VM running in a workspace shared service subnet I see error similar to what is described here. According to Sonatype docs docker needs to be exposed on a different port than the standard ssl port nexus is already running on. However nexus is running in an Azure App Service and I don't see a way to expose custom ports.
Steps to reproduce

setup Nexus to proxy docker hub
add *.docker.io and *.docker.com to firewall rules to allow nexus to access them
create workspace and start vm in shared services subnet
connect to vm using bastion and run docker login nexus-[tre_id].azurewebsites.net:[port]
see timeout error

Can this be assigned to me

@oliver7598 do you have an idea on how to address this?

@tamirkamara myself and @jjgriff93 are going to pair on this as a priority over the next sprint

Sounds good. Can you please share more details on the plan once you have it?
IIRC, I was the one who added this to begin with, so let me know if there's something I can help with...

This doc will be useful - might be we add a second app service just for docker?

Current challenge is exposing a second port in App Service to allow docker hub connections, which is prevented by this limitation: https://docs.microsoft.com/en-us/archive/blogs/waws/things-you-should-know-web-apps-and-linux#you-can-only-expose-one-port-to-the-outside-worldapplies-to-web-app-for-containers

Potential solution is moving nexus to container instances which does support multiple ports, Oliver and I will do some investigation into this

Container instances could work, still need an SSL certificate. VM is potentially a better option - easier to mount disks, backup etc.
Either way I don't think we can avoid generating SSL certificates with ACI or a VM.

We had this thought also, will require some testing as to whether Nexus would support that - I don't think we'd be able to configure anything because we couldn't post configuration to the Nexus API to set up the docker proxy if we've exposed a different port for that instance

Have set up a meeting to discuss further after tomorrow's stand-up - @tamirkamara have invited you if you're able to attend as your input would be valued. If not feel free to post your thoughts on this ticket. Summary of the planned meeting discussion:

How best to enable two exposed ports (limited to one for app service) so we can proxy docker hub on a separate port to the general nexus port (as per https://help.sonatype.com/repomanager3/nexus-repository-administration/formats/docker-registry/ssl-and-repository-connector-configuration)
If we choose to host Nexus on container registry / VM to get around port issues, how we then plan to set up SSL certs in lieu of the app service provided one

Possible approach for working with private VM endpoint proposed by @marrobi in a discussion on this (in terms of supporting dev environments)

 ┌──────────────────────────────────────────┐    ┌────────────────────────────────┐
 │                                          │    │                                │
 │ Public IP: mytre123.uksouth.cloudapp.net │    │  Storage static site           │
 │                                          ├───►│                                │
 │                                          │    │                                │
 └──────────────────────────────────────────┘    └────────────────────────────────┘
                                                        ▲
                                                        │
                                                        │
                                                        │
                                                        │
                                                        │
 ┌──────────────────────────────────┐                   │
 │                                  ├───────────────────┘
 │  Letsencrypt cert                │
 │  processor (run on schedule)     ├────────────────────┐
 │                                  │                    │
 └──────────────────────────────────┘                    │
                                                         │       ▼
                                                         │
                                                         │
                                                         │
                                                 ┌───────▼────────────────────────┐
                                                 │                                │
                                                 │  Key Vault                     │
                                                 │                                │
                                                 └────────────────────────────────┘
                                                         ▲
                                                         │
                                                         │
                                                         │
                          ┌──────────────────────────────┼────────────────────────────────────┐
                          │                              │                                    │
                          │   VNET                       │                                    │
                          │                              │                                    │
                          │                              │                                    │
                          │                      ┌───────┴─────────────────────────────┐      │
                          │                      │                                     │      │
                          │                      │ VM                                  │      │
                          │                      │                                     │      │
                          │                      │                                     │      │
                          │                      └─────────────────────────────────────┘      │
                          │                                                                   │
                          │                                                                   │
                          │                                                                   │
                          │                      ┌─────────────────────────────────────┐      │
                          │                      │                                     │      │
                          │                      │  Private DNS Zone:                  │      │
                          │                      │  map mytre123.uksouth.cloudapp.net  │      │
                          │                      │         to VM IP address            │      │
                          │                      │                                     │      │
                          │                      │                                     │      │
                          │                      │                                     │      │
                          │                      └─────────────────────────────────────┘      │
                          │                                                                   │
                          │                                                                   │
                          │                                                                   │
                          └───────────────────────────────────────────────────────────────────┘

Have added too new issues (see above) to start tracking the work on this

The three tasks associated with this bug are close, and the PR #1584 is merged, so closing this one out.
Thanks all!


Consider adding shader validation to matc / filamat

It would be nice to catch some link-time errors during shader compilation instead of at run time.  This could be done if we invoke the spirv-tools validator in matc. We could do something like this:
https://android.googlesource.com/platform/external/vulkan-validation-layers/+/HEAD/layers/shader_validation.cpp#2299

The spirv-tools validator actually can't catch the adreno bug that I was investigated when I created this ticked, so this doesn't seem like a valuable idea any more.  Closing.


TES and seccomp confinement

Is a TES task currently allowed to use all system calls available? If the host kernel has seccomp and the task container is ran with Docker, all these system calls are, by default, not allowed.
We want access to some of these syscalls for our WDL/CWL runners as it enables us to run Singularity within the TES task.
We saw that TES 1.1 has certain backend_parameters that are available, is there standard way of specifying these parameters or something similar to tell TES what permissions I would want for a task?

As far as I know, there is no TES way of requesting access to sys calls that are blocked by seccomp (if enabled). I am also sceptical about adding this to the TES spec in a way that would force all compliant implementers to support it (I guess seccomp is there for a reason). Possibly this could instead be specced out using extensions?
In any case, for this particular use case - would it make sense to add support for Singularity to Funnel? Also, could you possibly avoid the container-in-container design you are currently using by having your outer TES job sending TES jobs rather than spawning containers? Or perhaps making use of multiple executors (which may use the same volume)?

We don't currently have/test a Singularity implementation of Toil so I'm unsure if Singularity under Funnel would help, though I would think it might as it seems like its possible to run unprivileged singularity inside singularity. I'm unsure if the unprivileged nested container will cause any issues though.
We would like to eventually get rid of the Docker in Docker implementation, but it will be quite a bit of technical debt to get through. The easy way is to get things working immediately is to have more backend privileges, as we are still unsure if getting docker in docker to work out of the box is possible. Avoiding the issue entirely is an option, though we would not be utilizing TES fully; it would work, but for things like WDL, only the bash scripts would run on nodes, and everything else on the leader.
I'm not sure using multiple executors would work. A Toil container will try to run a nested container whenever it wants. Maybe it is possible if we don't allow nested containers to run, and instead consult the batchsystem, though that would also take quite a bit of engineering to send and receive other containers.

Tricky problem indeed. I'm still not sure about a general addition to TES. If you know you are using Funnel, you could maybe work out something implementation-specific (e.g., via env vars) - with a view to a possible (optional) TES extension in the mid-term.


api: fix corner case staggered fd for centered x0

Needed for elastic tti that contains odd centering FD

thanks, nice cleanup, merging


HATCH-338: Client query & mutate functions for number & integer types

core changes moved to main, frontend to feat branch


Binary Search Algorithm in Java

Description
Describe more about the issue.
Programming language

[ ] C
[ ] C++
[x] Java
[ ] Python

Are you contributing under any open-source program ?

Hacktoberfest

There is a document already on binary search. Please add your code with example input and output in Java. Assigning this to you🎊🎊🎊🎊


mmt tune: set default iterations to 10 and add option --maximum-iterations

Currently "mmt tune" can run up to 25 iterations and user can't reduced them.
Please limit to 10 the maximum number of iterations and add in "mmt tune" the parameter
--maximum-iterations
so that user can furterly limit then.
Such parameter interfaces directly with mert-moses.pl
Thanks

To be more clear: having the --maximum-iterations parameter in "mmt tune" allows users to set the maximum number of iterations to a value different from default (such value can be higher or lower than default value).
Concerning which is the appropriate value for the default number of iterations (10 or 25 or ...): esperience of people with more experience on mert issues can provide this info.
For example Mauro says that a good procedure is (1) to execute mert for a number of times (with a random component that differenciates the paths) and (2) to take the average of the weights obtained from the different mert executions.

The Foster&Kuhn paper (WMT, 2009):
http://www.aclweb.org/anthology/W09-0439
analysed the instability of MERT. Successively, in:
http://www.mt-archive.info/MTS-2011-Cettolo.pdf
we proposed and experimentally compared  two methods for overcoming that issue, one of them being the weight averaging mentioned by Roldano. Randomly changing the starting point of MERT, quite large changes of the BLEU score on test sets can be observed (in our exps, even 2-3 points). In fact, it is a matter of fact that it is a good practice to have multiple MERT runs. This should be considered for MMT. Since MERT is time consuming, a tradeoff could be to run 3-5 MERT runs, each for at most 10 iterations; then, in each run look for the weights which maximize the BLEU score on the dev set and finally average them.

By the way, the option of mert-moses.pl to have deterministic MERT runs is "--predictable-seeds" which "provide[s] predictable seeds to mert so that random restarts are the same on every run". If it is not specified, in general different MERT runs give different optimal weights.

We have implemented the option --max-interations=X for ./mmt tune in commit https://github.com/ModernMT/MMT/commit/03c960e621aebf2333070f27055cb020b7ae1c3e .
We opted for keeping the original default iterations right now.
We have also added by default the deterministic tune, if you want to have random seeds, just use the option --random-seeds.


Deadlock acquiring credentials when GlobalRuntimeDependencyRegistry used

Describe the bug
While doing research into publishing a .NET 8 application using native AoT to EKS, I found at deploy-time that the application would fail on a code path we have in an internal library where the AWS SDK would attempt to get credentials using STS. The exception would be the following:
Unhandled Exception: Amazon.RuntimeDependencies.MissingRuntimeDependencyException: Operation failed because of a missing runtime dependency. In Native AOT builds runtime dependencies can not be dynamically loaded from assembles. Instead the runtime dependency needs to be explicitly registered. To complete this operation register an instance of Amazon.SecurityToken.AmazonSecurityTokenServiceClient from package AWSSDK.SecurityToken using the operation Amazon.RuntimeDependencies.GlobalRuntimeDependencyRegistry.Instance.RegisterSecurityTokenServiceClient.

I added the code mentioned to the application and redeployed. At this point it appeared to no longer be responding and crash-looping.
Through various trial and error, I've distilled the problematic code path down to the code snippet below.
My hunch is that the code path is somehow re-entrantly trying to access this lock, causing it to block indefinitely:
https://github.com/aws/aws-sdk-net/blob/f7a3a70a75ff1c4d5bc877b10a03e836cfcbe32a/sdk/src/Core/Amazon.Runtime/Credentials/RefreshingAWSCredentials.cs#L144-L146
That's just a hunch - the issue could be somewhere completely different, but it's the first bit of synchronization I could find on the method call that is blocking. It also blocks using the synchronous version, GetCredentials(), so I'm pretty sure it's not something to do with sync-over-async.
The code appears to deadlock regardless of whether native AoT is actually used at runtime or not.
Expected Behavior
The operation does not block.
With the repro, the following messages should be printed to the console:
GlobalRuntimeDependencyRegistry.RegisterSecurityTokenServiceClient()
AssumeRoleWithWebIdentityCredentials.FromEnvironmentVariables()
AssumeRoleWithWebIdentityCredentials.GetCredentialsAsync()
Credentials obtained

Current Behavior
The application blocks on the call to AssumeRoleWithWebIdentityCredentials.GetCredentialsAsync().
GlobalRuntimeDependencyRegistry.RegisterSecurityTokenServiceClient()
AssumeRoleWithWebIdentityCredentials.FromEnvironmentVariables()
AssumeRoleWithWebIdentityCredentials.GetCredentialsAsync()

Reproduction Steps
Run the following code within EKS where the instance credentials are available.
using Amazon.Runtime;
using Amazon.RuntimeDependencies;
using Amazon.SecurityToken;

Console.WriteLine("GlobalRuntimeDependencyRegistry.RegisterSecurityTokenServiceClient()");

GlobalRuntimeDependencyRegistry.Instance.RegisterSecurityTokenServiceClient(
    (_) =>
        new AmazonSecurityTokenServiceClient());

Console.WriteLine("AssumeRoleWithWebIdentityCredentials.FromEnvironmentVariables()");

var credentials = AssumeRoleWithWebIdentityCredentials.FromEnvironmentVariables();

Console.WriteLine("AssumeRoleWithWebIdentityCredentials.GetCredentialsAsync()");

_ = await credentials.GetCredentialsAsync();

Console.WriteLine("Credentials obtained");

Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.SecurityToken 3.7.300.38
Targeted .NET Platform
.NET 8
Operating System and version
Ubuntu 22.04.3 LTS

Doing a bit more digging, this might be a case of more of a docs/footgun issue than a bug per-se.
Digging around some more, I see here that when not using native AoT, the client is created with explicit anonymous credentials:
https://github.com/aws/aws-sdk-net/blob/f7a3a70a75ff1c4d5bc877b10a03e836cfcbe32a/sdk/src/Core/Amazon.Runtime/Credentials/AssumeRoleWithWebIdentityCredentials.cs#L240
However, in my repo, I'm just calling the constructor with a region, it calls back into FallbackCredentialsFactory, which is what I traced through in a decompiler to get to the minimal repro in the first place:
https://github.com/aws/aws-sdk-net/blob/f7a3a70a75ff1c4d5bc877b10a03e836cfcbe32a/sdk/src/Services/SecurityToken/Generated/_netstandard/AmazonSecurityTokenServiceClient.cs#L90
I haven't tried changing my code yet to do the same, but it raises a few points

From the original error message, it isn't clear that the user needs to do this to prevent a loop when default/fallback credentials are used. It seems like an implantation detail the average user wouldn't know of or find.
Without me digging more in a debugger, if this is the case, I would have thought it would have caused a StackOverflowException rather than hang (unless the runtime is just failing to show that, so it appears to be hanging).

If this does turn out to be what is happening, then I guess the bug is less a deadlock, and more a need for clearer documentation on what the user needs to do in this case.

Yep, that's what it was.
If I change the code to this, the problem goes away:
using Amazon.Runtime;
using Amazon.RuntimeDependencies;
using Amazon.SecurityToken;

Console.WriteLine("GlobalRuntimeDependencyRegistry.RegisterSecurityTokenServiceClient()");

GlobalRuntimeDependencyRegistry.Instance.RegisterSecurityTokenServiceClient(
-   (_) =>
-       new AmazonSecurityTokenServiceClient());
+   (context) =>
+       new AmazonSecurityTokenServiceClient(
+           new AnonymousAWSCredentials(),
+           context.SecurityTokenServiceClientContextData.Region));

Console.WriteLine("AssumeRoleWithWebIdentityCredentials.FromEnvironmentVariables()");

var credentials = AssumeRoleWithWebIdentityCredentials.FromEnvironmentVariables();

Console.WriteLine("AssumeRoleWithWebIdentityCredentials.GetCredentialsAsync()");

_ = await credentials.GetCredentialsAsync();

Console.WriteLine("Credentials obtained");

Maybe it would help give a hint for the user in this case if SecurityTokenServiceClientContext included a property for the credentials to use, which could be set to an instance of AnonymousAWSCredentials?
https://github.com/aws/aws-sdk-net/blob/f7a3a70a75ff1c4d5bc877b10a03e836cfcbe32a/sdk/src/Core/RuntimeDependencies/CreateInstanceContext.cs#L163
public class SecurityTokenServiceClientContext
{
    public enum ActionContext { AssumeRoleAWSCredentials, AssumeRoleWithWebIdentityCredentials, FederatedAWSCredentials };
    public ActionContext Action { get; set; }
    public RegionEndpoint Region { get; set; }
    public IWebProxy ProxySettings { get; set; }
+   public AWSCredentials Credentials { get; set; } = new AnonymousAWSCredentials();
}

The STS dependency is the hardest one to deal with in the SDK for AOT or more specifically now the GlobalRuntimeDependencyRegistry. Even in the assume role case, which requires AWS credentials and not the anonymous credentials, you want to make sure your not just using the default credentials because that would go back to the profile that needs to assume a role instead of the profile that should make the STS assume role call.
I agree this area needs some smoothing out and at the very least better documentation.

If you are using code that gets the role from the running instance which has role assumed in its execution context like Fargate or Lambda (which I believe is using assume role?), is the current correct action to keep <Assembly Name="AWSSDK.SecurityToken" Dynamic="Required All"></Assembly> in the rd.xml file? Or is there another way to use AssumeRoleAWSCredentials without hardcoding the role name itself?
Side note, it's crazy to me that this GitHub issue is the only reference found on Google for RegisterSecurityTokenServiceClient.


Support for tvOS

This adds a dynamic framework for the tvOS platform and makes some adjustments to reduce duplication across the various framework targets.

Cool, thanks @briancroom !!


yml/spaced-comment false positive and fixing increases spaces

ESLint https://github.com/leotm/react-native-template-typescript/blob/master/.eslintrc.js (disabled the rule for now)
YAML https://github.com/leotm/react-native-template-typescript/blob/master/.github/workflows/main.yml
Current

Save

Save again

Great plugin so far, keep up the good work

Thank you for posting this issue.
You need to use yml/spaced-comment instead of spaced-comment.
overrides:
  -
    files: ["*.yaml", "*.yml"]
    rules:
        spaced-comment: off
        yml/spaced-comment: error

I have updated the documentation that explains it.
https://ota-meshi.github.io/eslint-plugin-yml/rules/spaced-comment.html

Np, cheers for updating the docs, JS syntax would be preferable here for .eslintrc.js

Here's a PR https://github.com/ota-meshi/eslint-plugin-yml/pull/92, feel free to close if sticking to yaml syntax


renovate: init at 37.393.0

Description of changes
Automated dependency updates. Multi-platform and multi-language.
https://github.com/renovatebot/renovate
tested with the following command
renovate --token ... --onboarding=true natsukium/nur-packages

closes https://github.com/NixOS/nixpkgs/issues/277588

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@NyCodeGHG
Thank you for tackling and reviewing this packages!
Would you like to be a maintainer as well?

@natsukium yes

fix build on x86_64-darwin https://github.com/NixOS/nixpkgs/compare/59aa56f9fc9a122e25addf8296c33607d7cfd2ca..5e97bc3b0a78cd37d4bf094933dee426a8e6cf62


Fixed text

"Automated investigation" instead of "Alert"

I was just about to ask if there is some reference to prove that this correction is needed. Then I read the sentence. 😄
It appears to be either some form of copy-paste error or other mistake by confusion.
Anyway, the original author must have been pretty tired at this point. 😴
This correction looks good to me.
BTW, if you have got time and feel like adding a small bit of MarkDown codestyle correction to this issue, consider adding 1 space in these lines:
- >[!NOTE]
+ > [!NOTE]
- >Currently, Automated investigation only supports the following OS versions:
+ > Currently, Automated investigation only supports the following OS versions:

(line 37+38 in the document)


[Enhacement][DevX] Add bulk operation scripts for optimising outputs

Is your feature request related to a problem? Please describe.
Users may want to apply some bulk operations on their input images before passing to OMRChecker. These utilities can help the users to compress the overall input size and also optimise the execution speeds on large files for faster tuning and re-runs.
Describe the solution you'd like
A few starter ideas to run on a folder of images:

bulk resize,

clip to max width (or height)
with a conditional trigger if the file size exceeds a provided value

bulk convert :

pdf to jpg
png to jpg or vice versa
tiff

bulk rename files

adding folder name to file name
removing non-utf characters from filename (to avoid processing errors)

add watermark to all images
blur a particular section of the images (e.g. student names and signatures)
create a gif from a folder of images
Save output of cropped pages to avoid cropping in each run (and merge with manually cropped images)
Save output of cropped markers to avoid cropping in each run (and merge with manually cropped images)
More ideas welcome!

Describe alternatives you've considered
N/A
Additional context
There's already a foundation setup in one of the development branches.
Note: please share your queries and approaches on discord for quicker discussions:

Link to the Discord invite
Link to the Hacktoberfest 2024 channel

Hey, I am new to hacktoberfest and I liked this project. I wish to resolve this issue. Can I work on this ?

Hey @amannaik247, which part of the bulk ops ticket would you like to work on? As it's labelled continuous, I'll assign you once you decide a subtask to pick from and share a basic approach for it. Please mind that -

There's already a foundation setup in one of the development branches.
This means you can take reference of the dev branch to work on this in a structured manner. Checkout this folder: https://github.com/Udayraj123/OMRChecker/tree/dev/scripts/local

Hey I would like to work on bulk convertor can you pls assign it to me

Hey @Anushlinux, sure I can assign you this as it's an continuous issue. Please mention which of the starter ideas mentioned above you'd like to work on. Also it'll be convenient if you also join and discuss over the discord channel.

As I mentioned earlier I would try to work on bulk convert start idea> Hey @Anushlinux, sure I can assign you this as it's an continuous issue. Please mention which of the starter ideas mentioned above you'd like to work on. Also it'll be convenient if you also join and discuss over the discord channel.


Add not_analyzed to NonStringIndexOption and make it the default option

This PR is questionable because it changes the default behavior of Index(), which previously defaulted to no, but now will default to not_analyzed.
@Mpdreamz @russcam thoughts?
Closes #1979

It is changing behaviour, albeit correcting an original issue :smile:
The change is from

no -
Do not add this field value to the index. With this setting, the field will not be queryable.

to

not_analyzed -
Add the field value to the index unchanged, as a single term. This is the default for all fields that support this option except for string fields. not_analyzed fields are usually used with term-level queries for structured search.

So consumers won't be losing functionality by the default change but could potentially be storing more data than they did before. Not a bad thing per se.
I think this is a reasonable behavioural change that implements the right default according to the docs so LGTM. We just need to ensure that we highlight it particularly in the release notes.
It'd also be worth adding the descriptions to the XML comments for the NonStringIndexOption enum

LGTM :+1: in 5.0 we need to not have any argument defaults for this one.


Vue.JS Single @ Symbol Support Feature for Razor

Good day everyone!
Using the "@" symbol does a really help in connecting with C# codes inside the cshtml page. I'm also implementing vue.js in my project and I got some issues in using single "@" symbol. In latest version of vue.js, "@" is the shortcut for defining an event in html property instead of "v-on:click." But when I'm trying to call the "@" symbol followed by the event name inside the razor page, I've got an error message that says
<input @click="submitSomething" The name 'click' does not exist in the current context. Cannot resolve symbol 'click'"
I've found a solution instead of using single "@", "@@" will define the single @ symbol of vue.js but is there a way to avoid the conflict of @ from razor and @ from vue.? Or is there any visual studio plugin in supporting the @ of vue.js?

Using @@ to escape a regular @ is the right thing to do. That's just how Razor works, because @ is a reserved character with special meaning. There is no way to disable that behavior because otherwise Razor wouldn't work.

Thank you @Eilon Have a good day! :)


Only last Buttons from multiple utter_buttons_template are displayed

Hey,
if you use multiple (!) utter_buttons_template from Rasa to send buttons within one custom action all the buttons from the utter_buttons_template before the last one are overwritten.
What do I have to change such that all buttons still appear?

I have the same problem.


feat: users - Dynamic OAuth / Social Providers

feat: users - Dynamic OAuth / Social Providers
This update adds a new REST call which pulls back a list of the available strategies which have settings defined within the env config (config\env). This REST end-point is then called from the user AuthenticationController in order to dynamically list strategies within authentication.client.view.html utilizing ng-repeat. The display attributes (Image, alt-text, oauth url) have default values based on the strategy name, but this can also be overridden in the environment configuration.
With this pull request, and my pull request updating the router for Oauth calls; its now possible to add a new Oauth provider simply by adding a strategy.js, and adding the needed config items to the environment config. Everything else is dynamic. There is longer a need to update four places.

I looked at the checks that have failed, and I think they're all intentional. First set of tests failed because there is now a new HTTP Request (/api/auth/strategies). This is expected.
I'm not positive why the second one failed. The "coverage" test is harder to read. I think its something similar.

@securityvoid It looks like the commits from #1564 got into this PR. Perhaps it makes sense to combine the PR's.
Is this PR dependent on the other?

@mleanos No, it is not directly dependent on the other. With the two, everything becomes completely dynamic. However, you could theoretically have the appearing/removal of Auth options even without the dynamic routes. With both of them in place it makes everything very dynamic, which I think makes a lot of sense, but the individual changes are independent.
Do you need me to do something different with the pull request so they don't come in as dependent? Sorry if I didn't bring these in correctly. These are actually the first two pull requests I've submitted.

@securityvoid This PR shouldn't have commits from your other open PR. Otherwise, it doesn't make sense to have them as separate PR's.
As this PR stands, it's difficult to review since it's not clear what the actual changes, and intent, is here.

@mleanos Okay, any idea what the best way is to fix this? Do I need to do a new pull and kill this?

@mleanos I think I fixed it. If there was a better way to do it than I did, please let me know. I've used the basics of git for awhile, but I'm very new to all this fancy "pulling out stuff".

@mleanos I've now figured out how to make this stuff clean, but I couldn't seem to get it right on this branch. I'll resubmit the pull.


[Bug]: build of new image 17.0.5...

Please add the exact image (with tag) that you are using
the new eclipse-temurin:17.0.5 !
Please add the version of Docker you are running
na
What happened?
the repository https://github.com/adoptium/containers has been updated for 17.0.5+8, but jenkins host https://doi-janky.infosiftr.net/job/multiarch/job/amd64/job/eclipse-temurin/ not see the news version....
and no news version on docker hub : https://hub.docker.com/_/eclipse-temurin/tags?page=1&name=17 ...
is normal ?

@mcarbonneaux DockerHub can take a few days before accepting our new images.

@mcarbonneaux they've available now. Sorry for not updating this issue sooner


typo Fixed typos in variables.md

Proposed changes
Fixed typos in variables.md
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[x] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


no scroll up button at landing page

allow me to add the scroll up button with some major changes in css and javascript
please assign me this issue under gssso extd24 , hactober fest , please make it atleast level 2 sir please ....
@mdazfar2

@2004pra You have raised a duplicate issue; it was already raised by someone else.

Look at all the issues, see which ones are available and which ones are not, and create issues accordingly.
This is not the way to work on open source :)


rango renames bookmarks to current tab title

steps to reproduce:

enable rango
open "google.com" and add it to the bookmark toolbar
open new tab and go to "github.com"
while "github.com" beeing active edit the bookmark "google.com" which was just created
enter anything as new title
the result is that the title of the current tab "github.com" will be used as bookmark title

Oh, this is bad. I see why this is happening. I think I can prevent this if I make sure that the current url matches that of the bookmark and the title without decorations contains the title of the bookmark. I'll see if I can fix it soon and make a release.

I for one add links to the bookmarks toolbar and remove (to only have the favicons) or rename the title for beeing shorter.
Don't know how to but maybe only "intercept" if the bookmark is added, but not if it is updated?

I need to use the onChange event too because of the way bookmarks are saved in Chrome.  When the bookmark popup appears the bookmark is saved. We change the title after onCreated is triggered, but when the user hits "done" the title of the bookmark will be changed again to the value of the input field of the popup window.
I think the solution I have come up with is robust and I don't think we'll have any more issues.


Can't install least version R package in Ubuntu

Anyone have same issue?  I tried on two machines.

Can you show some error message?

I installed a new ubuntu VM, and nothing except necessary package and openblas.
Then I try to install mxnet R package with bash install-mxnet-ubuntu-r.sh . Remove openmv, opencv and cuda in config.mk
First error is

** R
** demo
** inst
** preparing package for lazy loading
** help
No man pages found in package  ‘mxnet’
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
Error : .onLoad failed in loadNamespace() for 'mxnet', details:
  call: fun(libname, pkgname)
  error: could not find function "loadModule"
Error: loading failed
Execution halted
ERROR: loading failed
* removing ‘/home/papillon/R/x86_64-pc-linux-gnu-library/3.2/mxnet’
* restoring previous ‘/home/papillon/R/x86_64-pc-linux-gnu-library/3.2/mxnet’

I find is a function in Rcpp and I compared with old version which require(Rcpp) in .onload, so I added this part.
Then I can install the package and load it. However there is nothing exported,

> library(mxnet)
Loading required package: Rcpp
Init Rcpp>
>
>
> mxnet::.__T__
mxnet::.__T__/:base   mxnet::.__T__[[:base  mxnet::.__T__-:base   mxnet::.__T__+:base   mxnet::.__T__*:base

Then I try to generate NAMESPACE

> devtools::document()
Updating mxnet documentation
Loading mxnet
Re-compiling mxnet
'/usr/lib/R/bin/R' --no-site-file --no-environ --no-save --no-restore --quiet  \
  CMD INSTALL '/home/papillon/mxnet/R-package'  \
  --library='/tmp/RtmpC2wlYr/devtools_install_7d47bdc4ddb' --no-R --no-data  \
  --no-help --no-demo --no-inst --no-docs --no-exec --no-multiarch  \
  --no-test-load --preclean

* installing *source* package ‘mxnet’ ...
** libs
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c executor.cc -o executor.o
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c export.cc -o export.o
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c io.cc -o io.o
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c kvstore.cc -o kvstore.o
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c mxnet.cc -o mxnet.o
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c ndarray.cc -o ndarray.o
g++ -I/usr/share/R/include -DNDEBUG -I../inst/include  -I"/usr/local/lib/R/site-library/Rcpp/include"   -fpic  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c symbol.cc -o symbol.o
g++ -shared -L/usr/lib/R/lib -Wl,-Bsymbolic-functions -Wl,-z,relro -o mxnet.so executor.o export.o io.o kvstore.o mxnet.o ndarray.o symbol.o -llapack -lblas -L/usr/lib/R/lib -lR
installing to /tmp/RtmpC2wlYr/devtools_install_7d47bdc4ddb/mxnet/libs
* DONE (mxnet)
Loading required package: Rcpp
Error in find.package(package, lib.loc, verbose = verbose) :
  there is no package called ‘mxnet’

I got same issue after I checkout v0.9.2 or v0.9.1 yesterday. So not sure what happened.

This should be fixed by https://github.com/dmlc/mxnet/pull/4874
The update from roxygen2 broke the mxnet pkg.

This should be fixed. Feel free to reopen if you still met the error.


Add “apps” as a directory for model serving under main-project-stem

It is often necessary to share the model(s) with a user, the management, give a demo, etc. while only focusing on the functionality of the model(s) and keeping the code abstracted away.
Jupyter notebooks can do only so much. Most common requirement in such scenarios is building an app and deploying it: Streamlit, FastAPI, Flask, etc.
Although, perhaps some may argue that a separate repo with building the app keeps things more modular and cleaner, I would like to see what the community and the contributors have to say on this matter.
So, can we consider adding an apps folder under the main repo-stem?
path: REPO/apps

Since now in V2 the template a package by default (so "apps" could happily live in the base module), and the scaffold code is simplified, I am going to close this issue for now.


Make /// comments resolve to description, not summary

Description of the feature
As it is now, /// comments become the summary of your endpoints. For example:
    /// Get the latest ledger information, including data such as chain ID, role type, ledger versions, epoch, etc.
    #[oai(path = "/", method = "get", operation_id = "get_ledger_info", tag = "ApiTags::General")]
    async fn get_ledger_info(&self) -> PoemResult<Json<IndexResponse>> {
        let ledger_info = self
            .context
            .get_latest_ledger_info()
            .map_err(|e| anyhow::anyhow!(e))?;
        let node_role = self.context.node_role();
        let index_response = IndexResponse::new(ledger_info, node_role);
        Ok(Json(index_response))
    }

Generally I would like to use these comments for the description, as the summary is meant to be the shorter field. It'd be nice then in addition to be able to pass summary to oai.
Alternatively, some way to say which part is the summary and which is the description in the comment would be great. Like this:
@summary: <summary>
@description: <description>

Though this doesn't play nicely with newlines.

duplicate #142

Oh awesome, thanks a lot! I'll make a PR to add this to the README somewhere / make an example.


localization:=true does not work, errors

Robot Model
Turtlebot4 Lite
ROS distro
Humble
Networking Configuration
I do not know
OS
Ubuntu 22.04
Built from source or installed?
Installed
Package version
dpkg -s ros-humble-turtlebot4-simulator
Package: ros-humble-turtlebot4-simulator
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 41
Maintainer: rkreinin<EMAIL_ADDRESS>Architecture: amd64
Version: 1.0.2-1jammy.20240415.175517
Depends: ros-humble-turtlebot4-ignition-bringup, ros-humble-turtlebot4-ignition-gui-plugins, ros-humble-turtlebot4-ignition-toolbox, ros-humble-ros-workspace
Description: TODO: Package description
Expected behaviour
Launching with localization:=true does not work; it floods the console with errors. Even when these errors are present, localization seems to work okay, although it is not remarkably accurate and it tends to lose orientation.
It's unclear what the localization:=true even means. There is also a slam argument. Is that different? Should slam and localization be used together? Should they not be used together? There needs to be better documentation and error handling with these arguments.
I like localization:=true because it loads a full map of the warehouse at launch; I haven't found any other way to do this. However, the errors are distracting.
Actual behaviour
I have tried many different combinations of arguments with localization:=true, and they all flood the console with some variation of the following errors. I have found no configuration in which localization:=true works.
ros2 launch turtlebot4_ignition_bringup turtlebot4_ignition.launch.py localization:=true
[amcl-47] [WARN] [1715363981.669834662] [amcl]: AMCL cannot publish a pose or update the transform. Please set the initial pose...
[amcl-47] [WARN] [1715363983.743022749] [amcl]: AMCL cannot publish a pose or update the transform. Please set the initial pose...
[amcl-47] [WARN] [1715363985.795129378] [amcl]: AMCL cannot publish a pose or update the transform. Please set the initial pose...

ros2 launch turtlebot4_ignition_bringup turtlebot4_ignition.launch.py localization:=true slam:=true
[sync_slam_toolbox_node-49] [WARN] [1715363891.195691562] [slam_toolbox]: Failed to compute odom pose
[sync_slam_toolbox_node-49] [WARN] [1715363891.210854090] [slam_toolbox]: Failed to compute odom pose
[sync_slam_toolbox_node-49] [WARN] [1715363891.226011108] [slam_toolbox]: Failed to compute odom pose
[sync_slam_toolbox_node-49] [WARN] [1715363891.244100730] [slam_toolbox]: Failed to compute odom pose
[sync_slam_toolbox_node-49] [WARN] [1715363891.259339848] [slam_toolbox]: Failed to compute odom pose

ros2 launch turtlebot4_ignition_bringup turtlebot4_ignition.launch.py slam:=false nav2:=true model:=lite localization:=true
[controller_server-45] [INFO] [1715365862.863109649] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[controller_server-45] [INFO] [1715365863.363125792] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[controller_server-45] [INFO] [1715365863.863131608] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.

Error messages
see above

To Reproduce
see above
Other notes
No response

Your output suggests that you have not set your initial pose. Please set your initial pose before trying to do anything else.
I will also mention that the output that you have shared does not show any errors. This is all expected output based on what you have launched. Please go through the tutorials and read the documentation to understand what each of these parameters do and when you should use them. In particular, I would suggest starting here: https://turtlebot.github.io/turtlebot4-user-manual/tutorials/navigation.html

This issue is being closed due to inactivity. If you are still experiencing the issue, feel free to reopen this ticket when you are ready to continue the troubleshooting process.


tried to install from github, but I'm getting an error

I tried installing the pluging from github:
npm install https://github.com/map-gl-indoor/map-gl-indoor

it apparently installed fine, but apparently, I can't use it. I'm getting the following error:
Error: src/app/home/home.page.ts:9:55 - error TS2307: Cannot find module 'map-gl-indoor' or its corresponding type declarations.
9 import { addIndoorTo, IndoorControl, IndoorMap } from 'map-gl-indoor';
                                                        ~~~~~~~~~~~~~~~

Inside my node_module directory, there is a map-gl-indoor directory, but aside from the license and readme there is only the package.json, and nothing else.

I then tried to install with:
npm install<EMAIL_ADDRESS>
but I'm getting a 404-error, saying it is not in the registry.

Eventually, I tried to install from the tarball (ver. 0.0.2), but that gives me the same errors - it's not working.
What am I doing wrong?
Could you perhaps provide some more detailed installation instructions or similar? There seem to be some sort of name change in the midst of it from mapbox-gl-indoor to map-gl-indoor adding to the confusion, etc.

Build files are not available on github, just on npm. That is why you could not use the library directly from GitHub.
You must use the last npm version (currently 0.5.0) https://www.npmjs.com/package/map-gl-indoor
Sorry for the late answer.


Panel collapse button

#611
Added 3 new properties to PanelSizingModel:

showSplitter
showSplitterCollapseButton
showHeaderCollapseButton

For left and right collapse panels, I am rendering the header collapse button at the top of the panel header when collapsed. This seemed to make the most sense. At all other times the header collapse button is rendered at the end of the panel header, after all panel header items.
See https://github.com/exhi/toolbox/tree/panelCollapseButton branch in toolbox fo a demo of the new props.

I think the code here is pretty fine -- and I like the behavior and the choice of where to place the icons, and the choice of icons (although I will let others weigh in -- another option for icons would be the flat line, open box sort of thing that windows uses)
I do wonder how this dovetails with the title bar actions,  and what these title bar actions really are actually.  It seems like another approach would be to provide a title bar action that does this, and just leave users to use that API (and enhance that API if needed). On that note, I also wonder if we should have just had a single PanelModel, that could have reasonably housed the title bar actions, which are now weirdly not in a model.
Sorry to be waffling here, and bringing up some issues that go beyond the focus of this feature.  It may be that what we have here is the best way forward.
Finally note, that if we go with these icons, we will definitely want to alter that toolbox example to use different core icons for the panels themselves!


Extra space between about us para and projects

Describe the bug
A clear and concise description of what the bug is.

In the browser, there is extra space seen between about us and project details. Please have a look.

@khushi935 This is the same issue as #42 . Please see its description. You can work on it if you are interested. Also, Please feel free to close this issue

Okay, thanks.


Add codeql analysis for repo.

Enable CodeQL for this repo.

❤☕🙏 🚀Thanks fyi and cc: @peterbom, here is the test run agains my fork repo: https://github.com/Tatsinnit/vscode-aks-tools/actions/runs/7565567641/job/20601535529

This will also increase the SSAT rating of this repo.

looks good to me, Nice that it leaves a comment about the analysis. Is there anywhere we can see detailed report of this code ql analysis?

❤🙏🥂 Thank you and super exciting indeed, step forward for the completeness I guess, here is the doc detailing the logs and other things regarding codeql analysis. https://docs.github.com/en/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs#viewing-the-logging-output-from-code-scanning


Feature/2124 eligibility and character excel downloads

What's included?
Closes #2124
Note: This PR is related to digital-platform: Feature/admin-2124 eligibility and character reports.
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Character issues report
Example exercise: https://jac-admin-develop--pr2145-feature-2124-eligibi-hgpxxyka.web.app/exercise/ZutEH7OHcjRlUIfXLyqP/reports/character-issues

Go to the "Character Issues" report.
Click "Export to Excel" button to download the report file.
Open the file and check if the data of Character information, Professional background, Qualifications and Post qualification experience are in separate cells.

Eligibility issues report
Example exercise: https://jac-admin-develop--pr2145-feature-2124-eligibi-hgpxxyka.web.app/exercise/ZutEH7OHcjRlUIfXLyqP/reports/eligibility-issues

Go to the "Character Issues" report.
Click "Export to Excel" button to download the report file.
Open the file and check if the data of Qualifications and Post qualification experience are in separate cells.

Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Screenshots:

Character information

Professional background

Qualifications and Post qualification experience

Related permissions
Have permissions been considered for this functionality?

No permission changes required
Permissions have been added / updated. Details:

PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING

@HalcyonJAC Should I still be using these links to test?
Character issues report
Example exercise: https://jac-admin-develop--pr2145-feature-2124-eligibi-hgpxxyka.web.app/exercise/ZutEH7OHcjRlUIfXLyqP/reports/character-issues
Eligibility issues report
Example exercise: https://jac-admin-develop--pr2145-feature-2124-eligibi-hgpxxyka.web.app/exercise/ZutEH7OHcjRlUIfXLyqP/reports/eligibility-issues

@HalcyonJAC Should I still be using these links to test?
Character issues report Example exercise: https://jac-admin-develop--pr2145-feature-2124-eligibi-hgpxxyka.web.app/exercise/ZutEH7OHcjRlUIfXLyqP/reports/character-issues
Eligibility issues report Example exercise: https://jac-admin-develop--pr2145-feature-2124-eligibi-hgpxxyka.web.app/exercise/ZutEH7OHcjRlUIfXLyqP/reports/eligibility-issues

Yes, please.

The date format has been fixed.

If there is an end date: 01-2009 - Ongoing Fee paid Tribunal Judge at fake business name
If there is no end date: 01-2009 - 01-2014 Director at fake business name

The space has been added in the PQE.


Support compositional forms

It'd be nice if this worked:
>> f(x)=2x
>> g(x)=x^2
>> (f∘g)(4)
32
>> (f+g)(f)
24

etc.
See https://www.mathsisfun.com/sets/functions-composition.html and https://www.mathsisfun.com/sets/functions-operations.html

Neat, didn't know that was a thing in maths. Hopefully it isn't too awkward to parse. I guess "if function names are used inside a group (parenthesis), expect an argument after this, and parse the group as some sort of function call". This may happen.


Install fails: service "prometheus-operator-operator" not found

What happened?
Followed the https://github.com/prometheus-operator/kube-prometheus#quickstart to install kube-prometheus but it failed with:
...
servicemonitor.monitoring.coreos.com/kube-controller-manager created
servicemonitor.monitoring.coreos.com/kube-scheduler created
servicemonitor.monitoring.coreos.com/kubelet created
Error from server (InternalError): error when creating "manifests/prometheus-rules.yaml": Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post https://prometheus-operator-operator.prometheus-operator.svc:443/admission-prometheusrules/mutate?timeout=30s: service "prometheus-operator-operator" not found

There is a service called prometheus-operator but not a prometheus-operator-operator.
Environment

Prometheus Operator version:

HEAD / 88fe47b35e3c1f1160021ed6cab4d9d8349bddce
release-0.6

Kubernetes version information:

v1.18.6

Kubernetes cluster kind:
DigitalOcean

AFAICT configuring webhooks isn't part of the quickstart instructions. Since it's a cluster-wide setting, it looks like something/someone had already configured a mutating webhook for Prometheus rules. You can try to find out more with the kubectl get MutatingWebhookConfiguration command.

There was in fact a MutatingWebhookConfiguration.
I've deleted all kube-prometheus resources with kubectl delete --ignore-not-found=true -f manifests/ -f manifests/setup. It ran without any errors. And I've deleted the MutatingWebhookConfiguration.
Re-running kubectl create -f manifests/ gives me the same error:
servicemonitor.monitoring.coreos.com/kubelet created
Error from server (InternalError): error when creating "manifests/prometheus-rules.yaml": Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post https://prometheus-operator-operator.prometheus-operator.svc:443/admission-prometheusrules/validate?timeout=30s: service "prometheus-operator-operator" not found

I can't find any occurrence of prometheus-operator-operator in the kube-prometheus repository. Are you sure that your working directory hasn't been modified?

The cluster might have been. The local directory not.
Unfortunately I had to move on and started from scratch so I can't reproduce this issue anymore.
There for I'm closing this issue. Thanks for your help.

I had the same problem
when i follow the "quickstart"  ,and exec this commond :
kubectl apply -f manifests/

alertmanager.monitoring.coreos.com/main unchanged
secret/alertmanager-main configured
service/alertmanager-main unchanged
serviceaccount/alertmanager-main unchanged
servicemonitor.monitoring.coreos.com/alertmanager unchanged
secret/grafana-datasources unchanged
configmap/grafana-dashboard-apiserver unchanged
configmap/grafana-dashboard-cluster-total unchanged
configmap/grafana-dashboard-controller-manager unchanged
configmap/grafana-dashboard-k8s-resources-cluster unchanged
configmap/grafana-dashboard-k8s-resources-namespace unchanged
configmap/grafana-dashboard-k8s-resources-node unchanged
configmap/grafana-dashboard-k8s-resources-pod unchanged
configmap/grafana-dashboard-k8s-resources-workload unchanged
configmap/grafana-dashboard-k8s-resources-workloads-namespace unchanged
configmap/grafana-dashboard-kubelet unchanged
configmap/grafana-dashboard-namespace-by-pod unchanged
configmap/grafana-dashboard-namespace-by-workload unchanged
configmap/grafana-dashboard-node-cluster-rsrc-use unchanged
configmap/grafana-dashboard-node-rsrc-use unchanged
configmap/grafana-dashboard-nodes unchanged
configmap/grafana-dashboard-persistentvolumesusage unchanged
configmap/grafana-dashboard-pod-total unchanged
configmap/grafana-dashboard-prometheus-remote-write unchanged
configmap/grafana-dashboard-prometheus unchanged
configmap/grafana-dashboard-proxy unchanged
configmap/grafana-dashboard-scheduler unchanged
configmap/grafana-dashboard-statefulset unchanged
configmap/grafana-dashboard-workload-total unchanged
configmap/grafana-dashboards unchanged
deployment.apps/grafana configured
service/grafana unchanged
serviceaccount/grafana unchanged
servicemonitor.monitoring.coreos.com/grafana unchanged
clusterrole.rbac.authorization.k8s.io/kube-state-metrics unchanged
clusterrolebinding.rbac.authorization.k8s.io/kube-state-metrics unchanged
deployment.apps/kube-state-metrics unchanged
service/kube-state-metrics unchanged
serviceaccount/kube-state-metrics unchanged
servicemonitor.monitoring.coreos.com/kube-state-metrics unchanged
clusterrole.rbac.authorization.k8s.io/node-exporter unchanged
clusterrolebinding.rbac.authorization.k8s.io/node-exporter unchanged
daemonset.apps/node-exporter configured
service/node-exporter unchanged
serviceaccount/node-exporter unchanged
servicemonitor.monitoring.coreos.com/node-exporter unchanged
clusterrole.rbac.authorization.k8s.io/prometheus-k8s unchanged
clusterrolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
servicemonitor.monitoring.coreos.com/prometheus-operator unchanged
prometheus.monitoring.coreos.com/k8s unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s-config unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
role.rbac.authorization.k8s.io/prometheus-k8s-config unchanged
role.rbac.authorization.k8s.io/prometheus-k8s unchanged
role.rbac.authorization.k8s.io/prometheus-k8s unchanged
role.rbac.authorization.k8s.io/prometheus-k8s unchanged
service/prometheus-k8s unchanged
serviceaccount/prometheus-k8s unchanged
servicemonitor.monitoring.coreos.com/prometheus unchanged
servicemonitor.monitoring.coreos.com/kube-apiserver unchanged
servicemonitor.monitoring.coreos.com/coredns unchanged
servicemonitor.monitoring.coreos.com/kube-controller-manager unchanged
servicemonitor.monitoring.coreos.com/kube-scheduler unchanged
servicemonitor.monitoring.coreos.com/kubelet unchanged
Error from server (InternalError): error when creating "manifests/prometheus-rules.yaml": Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post https://demo-prometheus-operator-operator.prom-test.svc:443/admission-prometheusrules/mutate?timeout=30s: service "demo-prometheus-operator-operator" not found

 kubectl get MutatingWebhookConfiguration
NAME                                   WEBHOOKS   AGE
demo-prometheus-operator-admission     1          47h
istio-sidecar-injector                 1          4d1h
ks-events-admission-mutate             1          4d1h
logsidecar-injector-admission-mutate   1          4d1h
mutating-webhook-configuration         1          4d1h
prometheus-operator-admission          1          2d

i have solved this problem, by follow steps:
# find the out put about demo-prometheus-operator
➜  kube-prometheus git:(heads/v0.6.0) ✗ kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io
NAME                                 WEBHOOKS   AGE
demo-prometheus-operator-admission   1          47h
ingress-nginx-admission              1          4d1h
istio-galley                         2          4d1h
ks-events-admission-validate         1          4d1h
prometheus-operator-admission        1          2d
users.iam.kubesphere.io              1          4d1h
validating-webhook-configuration     3          123m
➜  kube-prometheus git:(heads/v0.6.0) ✗ kubectl get MutatingWebhookConfiguration
NAME                                   WEBHOOKS   AGE
demo-prometheus-operator-admission     1          47h
istio-sidecar-injector                 1          4d1h
ks-events-admission-mutate             1          4d1h
logsidecar-injector-admission-mutate   1          4d1h
mutating-webhook-configuration         1          4d1h
prometheus-operator-admission          1          2d

# and delete it:
➜  kube-prometheus git:(heads/v0.6.0) ✗ kubectl delete validatingwebhookconfigurations.admissionregistration.k8s.io  demo-prometheus-operator-admission
validatingwebhookconfiguration.admissionregistration.k8s.io "demo-prometheus-operator-admission" deleted

➜  kube-prometheus git:(heads/v0.6.0) ✗ kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io  demo-prometheus-operator-admission
mutatingwebhookconfiguration.admissionregistration.k8s.io "demo-prometheus-operator-admission" deleted

# and then  .you can reapply it:
 kubectl apply -f manifests/

alertmanager.monitoring.coreos.com/main unchanged
secret/alertmanager-main configured
service/alertmanager-main unchanged
serviceaccount/alertmanager-main unchanged
servicemonitor.monitoring.coreos.com/alertmanager unchanged
secret/grafana-datasources unchanged
configmap/grafana-dashboard-apiserver unchanged
configmap/grafana-dashboard-cluster-total unchanged
configmap/grafana-dashboard-controller-manager unchanged
configmap/grafana-dashboard-k8s-resources-cluster unchanged
configmap/grafana-dashboard-k8s-resources-namespace unchanged
configmap/grafana-dashboard-k8s-resources-node unchanged
configmap/grafana-dashboard-k8s-resources-pod unchanged
configmap/grafana-dashboard-k8s-resources-workload unchanged
configmap/grafana-dashboard-k8s-resources-workloads-namespace unchanged
configmap/grafana-dashboard-kubelet unchanged
configmap/grafana-dashboard-namespace-by-pod unchanged
configmap/grafana-dashboard-namespace-by-workload unchanged
configmap/grafana-dashboard-node-cluster-rsrc-use unchanged
configmap/grafana-dashboard-node-rsrc-use unchanged
configmap/grafana-dashboard-nodes unchanged
configmap/grafana-dashboard-persistentvolumesusage unchanged
configmap/grafana-dashboard-pod-total unchanged
configmap/grafana-dashboard-prometheus-remote-write unchanged
configmap/grafana-dashboard-prometheus unchanged
configmap/grafana-dashboard-proxy unchanged
configmap/grafana-dashboard-scheduler unchanged
configmap/grafana-dashboard-statefulset unchanged
configmap/grafana-dashboard-workload-total unchanged
configmap/grafana-dashboards unchanged
deployment.apps/grafana configured
service/grafana unchanged
serviceaccount/grafana unchanged
servicemonitor.monitoring.coreos.com/grafana unchanged
clusterrole.rbac.authorization.k8s.io/kube-state-metrics unchanged
clusterrolebinding.rbac.authorization.k8s.io/kube-state-metrics unchanged
deployment.apps/kube-state-metrics unchanged
service/kube-state-metrics unchanged
serviceaccount/kube-state-metrics unchanged
servicemonitor.monitoring.coreos.com/kube-state-metrics unchanged
clusterrole.rbac.authorization.k8s.io/node-exporter unchanged
clusterrolebinding.rbac.authorization.k8s.io/node-exporter unchanged
daemonset.apps/node-exporter configured
service/node-exporter unchanged
serviceaccount/node-exporter unchanged
servicemonitor.monitoring.coreos.com/node-exporter unchanged
clusterrole.rbac.authorization.k8s.io/prometheus-k8s unchanged
clusterrolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
servicemonitor.monitoring.coreos.com/prometheus-operator unchanged
prometheus.monitoring.coreos.com/k8s unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s-config unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
rolebinding.rbac.authorization.k8s.io/prometheus-k8s unchanged
role.rbac.authorization.k8s.io/prometheus-k8s-config unchanged
role.rbac.authorization.k8s.io/prometheus-k8s unchanged
role.rbac.authorization.k8s.io/prometheus-k8s unchanged
role.rbac.authorization.k8s.io/prometheus-k8s unchanged
prometheusrule.monitoring.coreos.com/prometheus-k8s-rules created
service/prometheus-k8s unchanged
serviceaccount/prometheus-k8s unchanged
servicemonitor.monitoring.coreos.com/prometheus unchanged
servicemonitor.monitoring.coreos.com/kube-apiserver unchanged
servicemonitor.monitoring.coreos.com/coredns unchanged
servicemonitor.monitoring.coreos.com/kube-controller-manager unchanged
servicemonitor.monitoring.coreos.com/kube-scheduler unchanged
servicemonitor.monitoring.coreos.com/kubelet unchanged

more info about this issue :
see https://github.com/helm/charts/issues/21080


[question]: cmsis-toolbox-windows-amd64\bin\csolution.exe --version returns 2.6.0 instead of 2.6.1

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
cmsis-toolbox-windows-amd64\bin\csolution.exe --version returns 2.6.0 instead of 2.6.1. Checked only on Windows so far
Expected Behavior
cmsis-toolbox-windows-amd64\bin\csolution.exe --version should return 2.6.1
Steps To Reproduce
No response
Affected tools

[ ] cbuild
[ ] cbuild2cmake
[ ] cpackget
[X] csolution
[ ] packchk
[ ] svdconv

Affected operating systems

[X] Windows amd64
[ ] Windows arm64
[ ] Linux amd64
[ ] Linux arm64
[ ] MacOS amd64
[ ] MacOS arm64

Environment
No response

Note that CMSIS-Toolbox 2.6.1 is a patch release with only a few tools being updated.
See https://github.com/Open-CMSIS-Pack/cmsis-toolbox/releases/tag/2.6.1
Patched Tools:
Build Invocation Utility 2.6.1
Generator Bridge 0.9.12
CMake File Generator 0.9.4

The problems fixed are listed here https://github.com/orgs/Open-CMSIS-Pack/projects/15

OK, got it, thank you for the quick answer.  Is there a way to retrieve the patch/release version from the archive file? Perhaps from a release notes document?

I have created this enhancement ticket: https://github.com/Open-CMSIS-Pack/cmsis-toolbox/issues/184

Note: created-for<EMAIL_ADDRESS>must be used, as csolution version remains 2.6.0 in the patch release CMSIS-Toolbox version  2.6.1.


Set default priority to 50

This is a feature request:
I've been enjoying using the priority feature but i'm finding that I want the ability to put items at the top of the list AND the bottom of the list.
With the default at 100 it forces me to assign a priority to every item. I'd rather not have to do this but only assign a priority to high and low priority items. If default was 50 we could explicitly set items to 1 (high priority) or 70 (low priority) .. without having to set a priority for most of the items that belong in the middle.
hope that makes sense!

i guess even better would be if its setting that can be customized

Yeah, actually that makes a ton of sense, I'm surprised no one has requested that before. I'll try to get this done this weekend, should be a one-liner.

Resolved in<PHONE_NUMBER>382dd64b36f17590b4e0963434e86c and released in 3.0.12, thanks again!


Enum with exactly opposite negative and positive integer values results in duplicate enum entries

When schema contains enums with integer values, their member names are generated as Value${absoluteValueOfActualValue}, which causes Value${absoluteValueOfActualValue} == Value${actualValue}, so when enums have negative and positive values of the same absolute value, they are generated with identical names.
This swagger.json entry:
      "AddressFamily": {
        "enum": [
          0,
          1,
          2,
          3,
          4,
         <...>
          29,
          65536,
          65537,
          -1,
        ],
        "type": "integer",
        "format": "int32"
      },

results in this incorrect typescript enum, since Value1 is duplicate enum member name:
export enum AddressFamily {
    Value0 = 0,
    Value1 = 1,
    Value2 = 2,
    Value3 = 3,
    Value4 = 4,
    <...>
    Value29 = 29,
    Value65536 = 65536,
    Value65537 = 65537,
    Value1 = -1,
}

It broke after release of v12, as previously these were generated as type and worked fine:
export type AddressFamily =
    | 0
    | 1
    | 2
    | 3
    | 4
    <...>
    | 29
    | 65536
    | 65537
    | -1;

latest tested: v12.0.2
Thanks and let me know if you need any extra info

Any update about that ?

Haven't tested this ever since but I see a duplicate issue #623 has been created after latest (v13.0.3) release. I am assuming it is still present.


[Icons] Remove unused clipPath definitions from icons

https://github.com/mui-org/material-ui/pull/12452#discussion_r208852590