cannot run two angular2 apps in parallel

Hi,
just was working on an angular2 app, which I wanted to run on a different port then my other app. Unfortunately the app crashes
You can reproduce it when you checkout https://github.com/Urigo/meteor-angular2.0-socially two times and try to run it
git clone https://github.com/Urigo/meteor-angular2.0-socially socially1
git clone https://github.com/Urigo/meteor-angular2.0-socially socially2
cd socially1 && meteor npm i && cd ..
cd socially2 && meteor npm i && cd ..

Then start them both on different ports:
cd socially1 && meteor
cd socially2 && meteor --port 5000

/Users/bruchmann/.meteor/packages/barbatus_typescript/.<IP_ADDRESS>7iqp++os+web.browser+web.cordova/plugin.typescript.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:116
      throw error;
            ^
Error: UNKNOWN, readdir '/Users/bruchmann/temp/socially2/node_modules/rxjs/src/testing'

the path (here .../node_modules/rxsj/...) of the error seems random
In my real use case it is actually an meteor angular 1.3 and a meteor angular2 but this was the easiest way to reproduce it

I received a similar issue on angular1 as well. We did not intentionally run 2 apps, but a reboot resolved it, so I am assuming it was similar reason

hmm yes, looks like a restart solved this.


Dialogflow with contexts

Hi Team,
I'm trying on implementing hangout bot with dialogflow and one of the intent required certain fields. I can't find sample around on how to use the same sessionID from the first requests.
Current implementation:
export async function dialogflowDetectIntent(projectId, userMessage) {
  const sessionClient = new dialogflow.SessionsClient({ fallback: true });
  const sessionPath = sessionClient.projectAgentSessionPath(
    projectId,
    sessionId
  );
  console.log('Session Path', sessionPath);
  const request = {
    session: sessionPath,
    queryInput: {
      text: {
        text: userMessage,
        languageCode: 'en-US',
      },
    },
  };
  console.log('Inside detect intent');
  const responses = await sessionClient.detectIntent(request);
  console.log('Detected intent');
  const result = responses[0].queryResult;
  console.log(`  Query: ${result.queryText}`);
  console.log(`  Response: ${result.fulfillmentText}`);
  if (result.intent) {
    console.log(`  Intent: ${result.intent.displayName}`);
  } else {
    console.log('  No intent matched.');
  }
  console.log(JSON.stringify(result));
  return {
    result,
    fulfillmentText: result.fulfillmentText,
    intent: result.intent.displayName,
  };
}

Usage
Bot - dialogflowDetectIntent('projectID', 'What are the next holidays?')
Response: Do you want to know on Public or Optional?
User: Public (dialogflowDetectIntent('projectID', 'Public') ) In this place it goes as new request as the sessionId is created again.

How to use the sessionID which is already a part of the outputcontexts?

Hi @saikrishna321. I think you need to handle potential conversation turns in your ```dialogflow''' experience based on the context with the end user. Are you using follow-up intents?
From the docs:

A session represents a conversation between a Dialogflow agent and an end-user. You create a session at the beginning of a conversation and use it for each turn of the conversation. Once the conversation has ended, you discontinue using the session.

https://cloud.google.com/dialogflow/es/docs/contexts-follow-up-intents
https://cloud.google.com/dialogflow/es/docs/api-overview?hl=en
https://www.youtube.com/watch?v=-tOamKtmxdY

@b-loved-dreamer Thanks for quick response. I'm using Liner Dialogs and currently I'm able to get it working by setting a sessionID for the entire session. For Ex:
User: When is the next holiday? -> Unique sessionID is generated using the userID which is 36byte
Bot: Are you looking for Public or Optional Holiday?
User: Public
Bot: Response
For all the request to Dialogflow I'm using the same sessionID created.
Now for the next set of conversation which is a new question, I still use the same sessionID. Is this is the right approach or would there be any side effects as the same sessionID is used for the entire session.

You should be able to use the session through the life of the conversation.  Once the conversations ends, you discontinue using the session.

Thank you for filing this issue. We provided feedback a week or more ago and never heard back from you. We are unable to proceed with this issue until then, so we are closing it. Please feel free to re-open this issue with more information.


Added shortcut aliases for commonly used git commands.

I think the aliases would be best provided by a new module say git-aliases.  While the aliases are less to type there are a lot that are fairly cryptic.  It would easier to just use tab completion than to learn all of these.  And some of these aliases are likely going to interfere with folks' personal aliases.  There are a couple that would stomp over my aliases.


[feature] Add support for checking out from logs

First i'd like to say I love this thing ❤ . It makes working with git branches so much easier.
One of the things I immediately tried was gh f -l and checkout a given entry (often to check for a bug or reset to a sane state). This would be a super useful to be able to add a command to checkout from a log entry (with ctrl+k or something... not sure yet)
That said, my bash-fu is pretty terrible. I'll try to mangle together a PR to add that but figured I'd raise this first to see if it makes sense.

Good afternoon and thank you for your kind words!
If I understand correctly, you would like a key binding (say ctrl-k in your example) to checkout the commit of the selected log entry instead of just showing the commit patch (current behaviour). If so, this was already on my roadmap and it is pretty easy to implement: only at the moment I am on holidays and will have access to a computer next week only.
If you want to have a try yourself you can essentially mimic the code here of the function gh f tags: essentially you have to tell fzf to expect a key-binding and once so, determine the action on the selected line. There is probably some sed/awk/cut to do to make sure you are acting on the commit id rather than the whole line, but if you follow the examples in the other parts of the code it should be easy enough.
This said, in 1-2 weeks I will get to this myself, so if you can survive till then you can just wait and it will be done :)

@gennaro-tedesco You are understanding correctly. I'll try to get a little time and put a PR together.


Abstract Node over some monad

The initial sketch was all IO. Now, it's any m, subject to typeclass constraints depending upon which non-pure functionality the program uses.
Network/Transport.hs was copied, trimmed, and abstracted from the real network-transport package. Multicast stuff was removed.

@ChShersh @dcoutts


[NEW] Emoji Keyboard support

I want to work on this issue.

Sounds good @sharmamohit123 👍

I have made a sample app which includes emojis in keyboard. But I am not understanding the correct file in Rocket Chat app to put this code in. Can I get some help?


Prevent overlapping elements

Version
5.2.0
Reproduction link
https://codepen.io/ataft/pen/dyWxpyG
Steps to reproduce
There are many open issues where various elements are overlapping with each other. Axis names overlap with axis labels, the legend and grid overlap, axis labels are cut, timeline overlaps with axis, etc. This makes it very difficult to manually set grid top/bottom/left/right, axis nameGap, legend location, top/bottom/left/right for non-grid series (e.g. pie), and separate non-series top/bottom/left/right settings (e.g. parallel).
Here are some of the open issues that highlight the problem:
Axis names overlap with axis labels
https://github.com/apache/echarts/issues/9265
https://github.com/apache/echarts/issues/14996
Legend and Grid overlap
https://github.com/apache/echarts/issues/14252
https://github.com/apache/echarts/issues/14724
Axis Labels cut off
https://github.com/apache/echarts/issues/15562
Label overlap in scatterplot
https://github.com/apache/echarts/issues/15509
What is expected?
Elements are sized appropriately based on positions
What is actually happening?
Elements overlap

scatter data label

option = {
  tooltip: {
    trigger: 'item',
    borderWidth: 0
  },
  legend: { show: true, bottom: 0, itemHeight: 8, itemWidth: 8 },
  grid: { left: 16, right: 32, top: 32, bottom: 32, containLabel: true },
  yAxis: {
    type: 'value',
    axisLine: { show: true, onZero: false },
    splitLine: { show: false },
    axisTick: { show: true }
  },
  xAxis: {
    type: 'value',
    axisLine: { onZero: false },
    splitLine: { show: false },
    axisTick: { show: true }
  },
  series: [
    {
      type: 'scatter',
      name: '2021-06-15',
      symbolSize: 8,
      data: [
        {
          value: [0.41, 0.49],
          name: '林业'
        },
        {
          value: [0.97, 0.96],
          name: '农产品加工'
        },
        {
          value: [0.66, 0.69],
          name: '农业综合'
        },
        {
          value: [0.39, 0.55],
          name: '饲料'
        },
        {
          value: [0.31, 0.18],
          name: '渔业'
        },
        {
          value: [0.67, 0.69],
          name: '种植业'
        },
        {
          value: [0.92, 0.96],
          name: '畜禽养殖'
        },
        {
          value: [0.33, 0.44],
          name: '动物保健'
        }
      ],
      label: {
        position: 'right',
        show: true,
        formatter: params => params.name
      },
      labelLayout: { hideOverlap: true, dy: 10 }
    }
  ]
};

codepen: https://codepen.io/eeeqxxtg/pen/WNOxbEm

https://github.com/apache/echarts/pull/15510 is working on the label auto layout on chart like scatter.

What is expected?
Elements are sized appropriately based on positions
We shouldn't expect this to happen all the times.
In my case, even when there is enough space there is overlapping. See below

When there is enough space, they should be autopositioned like HTML elements in html page. (when you add two span tags in html they will appear next to each other, when you add two paragraph tags they appear one below other, block and inline).

Hi guys! Diving deep into legend & grid overlapping issue got this finally working.
This approach is not much tested and should have a lot of pitfalls. The solution I found is based on linear relationship of legend and Grid area (I found it some confusing).
Works for legend at the bottom of grid. Not tested for other layouts. Here awesomeID is a legend id.
const legendY = echartsInstance._componentsMap["_ec_awesomeID_legend.plain"].group.y;

const gridHeight = echartsInstance._coordSysMgr._coordinateSystems[0]._rect.height;
const gridY = echartsInstance._coordSysMgr._coordinateSystems[0]._rect.y;

const gridVerticalOffset = gridHeight - gridY - (legendY - SOMECONSTANTVALUE);

setOption({
    grid: {
        bottom: gridVerticalOffset
    }
});

Don't know why, but SOMECONSTANTVALUE = 80 works great for me with any chart width and any level of legend overlapping.

In my case I want the legend at the top to not overflow the grid.

The solution from @Houstoten didn't work for me as accessing anything from the _componentsMap was always returning undefined.
I was able to come up with this hack:
const found = echartsInstance._componentsViews.find((entry) => entry.type === 'legend.plain');
const legendHeight = found._backgroundEl.shape.height;
if (legendHeight) {
    echartsInstance.setOption({
         grid: {
             top: legendHeight + 20,
         },
    });
}

@Ovilia I saw some of your comments in other related issues about you having internal discussing on how to solve this. Are there any updates on this ?

This could be resolved by implementing something similar to flexbox.
Right now unfortunately, my legends are always overlapping my x-axis labels at certain breakpoints and I can't do anything about it. Would appreciate solutions!

I'm not sure how to make it automatically avoid overlapping because all components (grid, legend, title, and etc.) use absoulute positions (left, right, top, bottom, width, height) and we cannot just move some components to elsewhere if overlap happens.

@Ovilia That makes perfect sense 👍 Is there an example of how we can access the main (legend, grid) elements position and size via the echarts instance ? I could only find that information by accessing private properties which isn't reliable.

If you set these positions like grid.left/right/top/bottom/width/height, you can keep a reference to your option and get that value. Or, you can use chart.getOptions() to get the merged options with default values and get the values actually being used.

This open PR that offers new nameLocation properties ('outsideStart', 'outsideMiddle', 'outsideEnd') would help with some of the screenshots above. It seems like it's very close to being ready to merge, but the author hasn't responded recently, I could potentially address the remaining comments and open a new PR?

Any updates on this issue? It's really annoying

I'm not sure how to make it automatically avoid overlapping because all components (grid, legend, title, and etc.) use absoulute positions (left, right, top, bottom, width, height) and we cannot just move some components to elsewhere if overlap happens.

The indirect approach of competitors to avoid overlapping data labels, for reference(https://github.com/apache/echarts/issues/18780).

Hi everyone,
I found a proper way after looked through all the issues and solutions refer to the "legend overlap element" problems.
This solution leads an ideal direction: https://github.com/lightdash/lightdash/issues/541#issuecomment-1157815376
And my final version:
const [legendHeight, setLegendHeight] = useState(0);
useDebounceEffect(
    () => {
        if (chartRef.current) {
            // @ts-ignore
            const found = chartRef.current._componentsViews.find((entry: any) => entry.type === 'legend.plain');
            const myLegendHeight = found?._backgroundEl.shape.height;
            chartRef.current.setOption({
                grid: {top: myLegendHeight},
            });
        }
    },
    [window_size.width],
    {wait: 200}
);

Cheers!


useErrorBoundary option works in useQueries?

Discussed in https://github.com/tannerlinsley/react-query/discussions/2355

Originally posted by luizeboli June  8, 2021
Hello guys, I have this hook:
export const useOptions = () => {
  return useQueries([
    {
      queryKey: 'groups',
      queryFn: () => axios({ method: 'GET', url: '/groups' }),
      useErrorBoundary: true,
    },
    {
      queryKey: 'types',
      queryFn: () => axios({ method: 'GET', url: '/types' }),
      useErrorBoundary: true,
    },
    {
      queryKey: 'sourcedTypes',
      queryFn: () => axios({ method: 'GET', url: '/sourcedTypes' }),
      useErrorBoundary: true,
    },
  ])
}

The component that consumes this hook is wrapped by a ErrorBoundary, but it doesn't throw while using useQueries. It just works with useQuery.
The only change needed to work correctly is replace useQueries by useQuery.
Is this an expected behavior? I didn't find it in docs

I have the same problem but it does not work yet: https://github.com/tannerlinsley/react-query/pull/2109

Related: https://github.com/tannerlinsley/react-query/issues/1523

does useErrorBoundary work in useQueries without suspense? Also, if you open an issue, please create a codesandbox example that reproduces the issue, thanks.

does useErrorBoundary work in useQueries without suspense? Also, if you open an issue, please create a codesandbox example that reproduces the issue, thanks.

It works in useQuery without suspense so maybe its supposed to.

It works in useQuery without suspense so maybe its supposed to.

That wasn’t the question though. Does it work in useQueries without suspense? Trying to narrow down if it’s useQueries+suspense related, because for that we already have an issue and yes, that doesn’t work yet

Yes useQueries works perfectly without suspense! I only missed an option for refetchInterval in useQueries

okay, I've made a reproduction: https://codesandbox.io/s/holy-darkness-qy5tw?file=/src/index.js
even with suspense: false, useQueries does not correctly work with useErrorBoundary.
However, I think that the open PR that tries to solve #1523 will also fix this issue, see:
https://github.com/tannerlinsley/react-query/pull/2109/files#diff-d1b1d4e3c1d5b653533620a0b77d0873a170c747a9bd5ae5db7d58f8606262d0R59
If I try out the above reproduction with that PR preview build, it seems to work: https://codesandbox.io/s/tannerlinsleyreact-query-basic-forked-vi4gt


Implement (auto-)saving draft versions of folders

Proposed solution
If user currently changes away from form, alert is shown asking if user want's to save the form. Save doesn't do anything, so implement draft possibility.
User should also be notified somehow that they have non-finished versions of forms available.
In best case form is auto-saved every now and then and saving is reported to user via notification.
DoD (Definition of Done)
Saving draft versions is possible.

I'm wondering what information we want to save into drafts.
For now the logical data would be accessionId and schema. To get that data, we need to use createFromJSON or createFromXML methods.
However if user hasn't filled required fields but wants to save form as an draft, createFromJSON method doesn't work since submission doesn't validate.
Example response from Study/form (user has filled only Study Description field):
data:
detail: "Provided input does not seem correct because: ''descriptor' is a required property'"
instance: "/objects/study"
title: "Bad Request"
Example does work when required fields are filled.
Does it make sense that user needs to fill required fields before being able to save a draft?
Any ideas @blankdots, @csc-jm ?

Pending on draft validation changes in back-end.

this would be solved with https://github.com/CSCfi/metadata-submitter/issues/158


please add a constructor for java.io.File

please change the method setFullContent to support java.io.File, thanks.
Reader reader = new Reader();
reader.setMaxContentPerSection(1000); // Max string length for the current page.
reader.setIsIncludingTextContent(true); // Optional, to return the tags-excluded version.
reader.setFullContent(new File(epubFilePath)); // Must call before readSection.

Sure thing.
But just for the sake of curiosity, why do you need another constructor? Can't you just use the current one with file.getPath()? What would be the difference? I might be missing a point, didn't think of it throughly.

This still looks redundant to me since I didn't get any explanation.
You could just call file.getAbsolutePath and send the path.


Feature: Separate resource fragments

Should resolve #40
I tried to implement different resource fragments for List and Detail view. Seems to work well, but truth be told I only tried fetching the data with getList, getOne and direct data provider calls. I have not tried creating a <List> or <Show> component for this virtual resource and just assume it should work, if underlying calls to the data provider work. I also updated the readme to document this new behavior.
I think I've understood how to use git rebase, so I declare this PR as a draft to get your feedback and once it's ready, I'll squash into a single feat:  commit and remove the draft status. If I manage to mess up again, I'll fix it somehow differently 😄

One thing I realized right now - should the many fragment be used just for GET_LIST or also GET_MANY operation?

hi @sMteX, thank you so much for your contributions, i really appreciate it!

, I'll squash into a single feat: commit and remove the draft status. If I manage to mess up again, I'll fix it somehow differently

we can also use "squash and merge" in github to merge it, than we can define the commit message :-)
The changes look good, ping me if you are ready and i'll look over it again

@macrozone Fine by me, can you clarify when are the fragments supposed to be used? Currently I've made it so that one fragment is used in GET_ONE operation and many fragment is used in GET_LIST, but maybe it makes sense to use many fragment also with GET_MANY or even GET_MANY_REFERENCE (though to be honest, I don't know the difference nor understand the reference one).

also not sure, tbh. I think GET_MANY_REFERENCE is used in a reference field. Means, if you use <ReferenceArrayField>, it will use that to fetch the records.
using many on GET_MANY and GET_MANY_REFERENCE probably makes sense

Looking at buildGqlQuery.ts, it looks like GET_LIST, GET_MANY, GET_MANY_REFERENCE is indeed using the same query ("many" of some resource), just using different filters/conditions, so using same fragment for these is probably correct. I added additional tests to make sure they work this way, and also that it should throw an error if it's incorrectly defined. Should be now ready for review.

Hello @macrozone, would you mind taking a look at the changes when you have some time if there's anything you'd like me to change or if it's fine to go? 🙂

:tada: This PR is included in version 4.3.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 6.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support streaming write operations in the generator

I am not sure if there are streaming writes in any of the libraries that we plan to automatically generate. Seems likely.  But I need this feature to automatically generate the *Stub classes for the storage/v2 APIs anyway.

I am going to close this, as I think I have implemented all we need to for streaming-write RPCS.  There are only two services that require streaming writes (see below).

google.actions.sdk.v2 is not a cloud service, it is part of Google Assistant
google.storage.v2.WriteObject requires a custom connection and client (which we have already implemented), generating the *Stub and decorators automatically is all we need.
google.storage.v1.InsertObject will never go GA

cat googleapis/api-index-v1.json | jq '.apis | map(select(.services != null)) | map(.services | map(select(.methods != null)) | map(.methods | map(select(.mode == "CLIENT_STREAMING") | [.mode, .fullName]  ))) | flatten ' | grep -v CLIENT_STREAMING  | grep -v beta
[
  "google.actions.sdk.v2.ActionsSdk.CreateVersion",
  "google.actions.sdk.v2.ActionsSdk.WriteDraft",
  "google.actions.sdk.v2.ActionsSdk.WritePreview",
  "google.storage.v1.Storage.InsertObject",
  "google.storage.v2.Storage.WriteObject"
]


Remove <meta> tag only necessary for IE-compatibility

Given that Internet Explorer is, since some time now, no longer supported in the PDF.js library this <meta> tag can also be removed (added in PR #6374).

/botio-linux preview

Nice find; thanks!


the directory "datasets" doesn't have occ_reid.py

We have some problems when train and test on other environments in OCC-REID, we are now fixing it.
we will release it later.
you can comment out the occ_reid in make_dataloader.py first to run other datasets


Can you add credential options to the docker image?

Caused by:
  failed to clone into: /usr/local/cargo/git/db/protobuf_definitions-ca489d32c7290e5c

Caused by:
  failed to authenticate when downloading repository
attempted to find username/password via git's `credential.helper` support, but failed

Caused by:
  failed to acquire username/password from local configuration

It will be useful on private repos

I could do if I knew how. Are you sure this is a tarpaulin issue? Googling it looks similar to this https://github.com/rust-lang/cargo/issues/3487 which is an issue with cargo unable to download private repos and complaining about git credentials.

actually cargo can do it normally with installed credentials in the OS.
It is not a bug for either cargo or tarpaulin but it cannot be done without modifying the docker image.
So if with added perimeters to the image we don't have to wrap the tarpaulin's docker image and pass all parameters.
If you want it to be minimal, I may just wrap tarpaulin with build-arg to pass arguments in this case then.

No that's fine I was just unsure of what to do. If you could send some documentation on what I'm doing I'll make the modifications

@abbychau I'm still not 100% sure what I'd have to do to fix this issue, I tend not to use docker so am a docker novice. If you can link any examples it would be helpful

Sorry I rethought it again and it seems it makes more sense to keep this image minimal :D
because it is docker's philosophy :)


Wrong time due to recent Mexico time zone & DST changes

Hello,
On the evening of October 28, 2022, the Mexican government published a decree that rescinded the DST changes for the entire country, and moved the time zone for certain regions.
The problem is that the decree took effect on October 30, at midnight.
Adiós al horario de verano | Secretaría de Energía | Gobierno | gob.mx (www.gob.mx) (Governent official website, in Spanish)
Basically, the changes are:

Mexico Central Time (Mexico City, Guadalajara, Monterrey) stays at UTC-6, but removes DST change from April, 2023
Mexico Mountain Time (Chihuahua, Mazatlan, La Paz) stays at UTC-7, but removes DST change from April, 2023
Chihuahua moves to UTC-6, without DST (this applied Oct. 30)

Some municipalities that border with the US will be using US time zones for now.
With that being said, the issue is that right now the clock is displaying the time by 1 hour forward. For example, right now is 9:02 but is displaying 10:02.
Would be nice if this gets fixed since right now the clock is pretty useles.

Hi @daviddesmet,
the analogclock sample-plugin uses the time reported by your operating system to it. (localTimeString).
So most likely this is not (yet) in sync with all the current changes, but will catch-up at some point in time. There's no real control over those time-settings (other than adjusting the value manually in the source-code).
If you want to stick with these GitHub samples, you could try the Sample-Clock-Plugin, but I think the result is similar, because it also relies on the local time reported by the system to Stream Deck.
Or you can try the newer Clocks  plugin from our Stream Deck Store, which has built-in support for timezones in the WorldClock action. There you have a bit more control over DST and timezones.


fix dependencies

Describe what this PR does / why we need it
**Module : **

spring-cloud-alibaba-dependencies
sentinel-example

The example dependencies should not be relied on by the core dependencies ,The dependency is reversed.
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhangkaizhao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Turn off @typescript-eslint/comma-dangle

There is a new extension rule in typescript-eslint since the version 4.2.0 has been released.
The core config has already turned off comma-dangle.
The config of typescript-eslint should respect the same rule as well.
https://github.com/prettier/eslint-config-prettier/blob/9444ee0b20f9af3ff364f62d6a9ab967ad673a9d/index.js#L29
Reference:

typescript-eslint/typescript-eslint#2416
typescript-eslint/docs/rules/comma-dangle.md

Released in v6.12.0. Thank for the report, and thanks @ybiquitous for the pull request!


Can not see all the metrics e.g. jenkins.job.leadtime

Hi,
I have a Jenkins running in a docker container.
I started the datadog agent docker on the same host as jenkins docker.
I executed couple of dummy jobs and still do not see any of the following metrics.
jenkins.job.leadtime
jenkins.job.cycletime
jenkins.job.mttr
jenkins.job.feedbacktime
jenkins.job.mtbf
Am I doing something wrong ?
+
I am using the trial account.

@faizan80, we'll need some additional information to assist. Can you open a support ticket and we'll take it from there? Thanks.
https://docs.datadoghq.com/help/


doc: update IntelSGX

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Currently, the information in the IntelSGX system seems inadequate. In order for beginners to have a better understanding, we will add more information to the documentation. Hence making it more understandable.
Acceptance Criteria
No response
Suggestions for a technical implementation
Will use some pictorial representation for a better understanding.

Agreed, the SGX set-up is more involved and complicated. There are instructions under the Clouds section here https://enarx.dev/docs/Clouds#other-software. But maybe there should be a generic SGX instruction.


Handle memory view serialization in data frame

Help address issue 250 in hyper-h2

@Lukasa added.  Thanks.


Check sha3 for keccak_256, fix assertion error by comparing to string instead of bytes

pysha3 now uses the name keccak for the pre-standard sha3 hash.

The travis build is failing because of an unrelated SSL error. Someone should fix that!

Actually this doesn't fix the real problem with the assertion error, but #425 fixes it. The pysha3 thing is still a thing though.

duplicate of #424 #425 #434


SpawnEntity, DeleteEntity, SetPose Services

Desired behavior
ros_gz_bridge support SpawnEntity, DeleteEntity, and SetPose services, so I can access them through ROS2 client calls.
Alternatives considered
Running gz services through Subprocesses
Implementation suggestion
Is it just ros_gz_bridge/src/service_factories/ros_gz_interfaces.cpp that needs to be changed? Not too sure, but just a thought.
Additional context
Gazebo Garden, ROS2 Humble.
The interfaces for the services, request types, and response types are already supported in ros_gz_interfaces or other

This would be a nice addition. A PR would be welcome 😉 .

I can give it a good go. First open source contribution attempt aha

How is the progress on implementing these services? I would also like to help if needed.

I've begun work on this fork and hacked a solution for my own purposes here: https://github.com/retinfai/ros_gz
But more tweaking is needed before I want to submit for review.
Would love collaboration – I haven't found a lot of time recently.

which ros2 version and gazebo version are you using? I am running humble and garden.

I'm using that too.
ROS2 Humble & Gazebo Garden

Cool, what do you think still needs to be done? You seemed to have all of the features working. I am mainly interested in the set_pose service and it works on my side as well.

It's more like it's incomplete. I don't convert every field.
But for set pose specifically, it gets confusing for me when gz.msgs.Pose doesn't map one to one to anything in the ROS side, so want to know the best practice for mapping 1 to N and vice versa. Set pose request (Entity and Pose on the ROS side) map to gazebo Pose but not all fields in Entity and Pose are used, so I exclude them. That sort of thing

I was wondering how to set the location of an entity spawned within Gazebo Garden. But it's not officially supported.

This is definitely supported. Checkout the message definition https://github.com/gazebosim/gz-msgs/blob/gz-msgs9/proto/gz/msgs/entity_factory.proto#L65

@retinfai I'm not an expert but to call a gazebo service from a ros node, I need the bridge support ?
If not, I'm going to investigate inside the set_pose service, you mentionned !

That's correct, calling the service from a Ros node does require bridge support . Just wanted to clarify.
In saying that, you can pull the fork, which does support it, while I fix issues and create a PR

@retinfai Yes I'll do that! Thanks for the help

I tested the create/remove/set_pose services on Jazzy and Harmonic and the changes in this PR worked fine for me.


Lots of new logs since 3.7.0

Since the 3.7.0 version, we do have a lot of useless logs on all our lambdas:
2024-06-06T13:22:09.119Z	undefined	ERROR	_X_AMZN_TRACE_ID is missing required information
2024-06-06T13:22:09.131Z	undefined	ERROR	Empty or non-string trace ID provided

3.6.0 doesn't log these messages.
How can we deal with them? How can we silent them or removed them?

The PR introduced the issue has been reverted by https://github.com/aws/aws-xray-sdk-node/pull/657
Please bump to the latest 3.8.0 with the fix.

The revert of course fixed the problem.


add fingerprint to debugging log

Can you also update the PR description to include example output of the debug log with this change? This helps verify the logging actually looks like what we expect. You can copy/paste the whole DISTRIBUTED_DEBUG_BEGIN block from your test command.


Add basics of UX terminology

Add basics of UX terminology a web developer should be aware of:

Tools UX use such as Sketch, Figma, Photoshop
Style Guidelines
Consistency between colors, and other values
Font Units
Images, GIFs, etc.
Animations

Would you add it as a PR in the Step Up section?

Would love to 👍

PR raised.

Thanks a lot @Neha ! I really appreciate your contributions ❤


How to get the original job tag?

What did you do?
I create the following ServiceMonitor
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  labels:
    k8s-app: test
  name: test
  namespace: default
spec:
  endpoints:
  - bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
    interval: 15s
    port: metrics
    relabelings:
    - sourceLabels:
      - job
      targetLabel: prometheus_job_name
  namespaceSelector: {}
  selector:
    matchLabels:
      app: test

and get the following prometheus config:
scrape_configs:
- job_name: default/test/0
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  kubernetes_sd_configs:
  - role: endpoints
    namespaces:
      names:
      - default
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  relabel_configs:
  - source_labels: [__meta_kubernetes_service_label_app]
    separator: ;
    regex: test
    replacement: $1
    action: keep
  - source_labels: [__meta_kubernetes_endpoint_port_name]
    separator: ;
    regex: metrics
    replacement: $1
    action: keep
  - source_labels: [__meta_kubernetes_endpoint_address_target_kind, __meta_kubernetes_endpoint_address_target_name]
    separator: ;
    regex: Node;(.*)
    target_label: node
    replacement: ${1}
    action: replace
  - source_labels: [__meta_kubernetes_endpoint_address_target_kind, __meta_kubernetes_endpoint_address_target_name]
    separator: ;
    regex: Pod;(.*)
    target_label: pod
    replacement: ${1}
    action: replace
  - source_labels: [__meta_kubernetes_namespace]
    separator: ;
    regex: (.*)
    target_label: namespace
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_service_name]
    separator: ;
    regex: (.*)
    target_label: service
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_pod_name]
    separator: ;
    regex: (.*)
    target_label: pod
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_service_name]
    separator: ;
    regex: (.*)
    target_label: job
    replacement: ${1}
    action: replace
  - separator: ;
    regex: (.*)
    target_label: endpoint
    replacement: metrics
    action: replace
  - source_labels: [job]
    separator: ;
    regex: (.*)
    target_label: prometheus_job_name
    replacement: $1
    action: replace

I need to get the original job_name as a tag prometheus_job_name, which should results to default/test/0 here, but as the config show, relabelings defined in ServiceMonitor object are appended after built-in configs, so when the last relabeling executing, job has already been modified to test, I have no where to read default/test/0
My question: Is there any way the get the original job tag default/test/0 ?
or how can we change the order of relabelings? So I can read it before modified.
Environment

Prometheus Operator version:

Kubernetes version information:

1.15.0

I'm unsure how breaking it would be if we changed the order of where we insert relabel configs. I think what we can do is we can relabel the original job name into a meta label. Would that work for you?

I think what we can do is we can relabel the original job name into a meta label. Would that work for you?

I think that works for me.

Do you want to open a PR for this? :)

OK, I will try. I am learning about the source code.

Hello,
I have a similar need : get the job label with value as <namespace>/<service>. The reason of my need is that Promtail does it this way and I think they do it the right way (what if you have 2 services with similar name in 2 distinct namespaces ?).
Because this is the default config in Promtail, I would like to configure prometheus-operator in a way that it would also be the default.
Is this the same issue as keeping the original job, or should I open a new issue with my need ?

"the right way" is very opinionated :slightly_smiling_face: . My personal opinion on this is that the job label is an outdated concept, it got into Prometheus because of how borgmon at google handled "tasks". In Prometheus Operator we went the way of denormalizing this need for namespace/service and have distinct labels for these, which are default (and can even be enforced by an administrator using the enforedNamespaceLabel feature. This actually allows for much more flexibility as when namespace labels are enforced, then you can even build tenancy mechanisms around this.
Nonethesless that's just the default, and we do want to enable you to do what you think is "right". In this case all you need to do though is relabel the namespace and service meta labels into the job label. You can do that through the relabelings configuration in your ServiceMonitor and PodMonitor objects.


Where is the deploy to cloud button for resource manager ?

Where is the deploy to cloud button for resource manager ??
See the doc that refers to it.

Hey MarcGueury,
Many thanks for your feedback and thanks for using the service. The Deploy to Resource Manager button will appear soon. We are completing the Schema.yml for ORM and as soon as that is done, we will have the option to run directly via Resource Manager.
~Paul

Hey MarcGueury,
Many thanks for your feedback and thanks for using the service. The Deploy to Resource Manager button will appear soon. We are completing the Schema.yml for ORM and as soon as that is done, we will have the option to run directly via Resource Manager.
~Paul

@MarcGueury we put the deploy to oci button (link) on the readme.


Command Line: Escape markup in command line output

Fixes #3340

You just found and fixed a security vulnerability that has been in Prism for years. Thank you!
The bug has been introduced in #856, almost 4 years ago, and was first released v1.14.0.
I'll release a new version of make an advisory after merging this PR.

Happy to help.
How do the release tags relate to the js/css downloads on the prism site?  The last release was January I think but if I download the css/js from the site now it includes my recent PRs which went in since the Jan release.  Is the site based on master?
I think it may be better if the site was built from a tagged release then the version number in the downloaded css/js would always correspond to a fixed point in the code.

How do the release tags relate to the js/css downloads on the prism site?

Not at all. As you guess, they get everything straight from master.

I think it may be better if the site was built from a tagged release then the version number in the downloaded css/js would always correspond to a fixed point in the code.

I agree, but that's not easy to implement on top of GitHub pages. However, we actually need this for another feature, so it is planned that you will eventually be able to select a specific version on the download page.


Store action report only if the node accepted the transaction

The action reports cannot be trusted for refresh action because an oracle's refresh will most likely be rejected by the node due to double-spending. Because all the oracles posting refresh tx are "competing" to spend the same pool and refresh boxes.
Closing in favor of #278


Face Beautification [GSSoC'23 Project Request]

Is your feature request related to a problem? Please describe.
I would like to add a feature that allows users to apply face beautification effects to their photos. Face beautification is a process of enhancing facial appearance by adjusting various factors such as skin, shape, hair, makeup, lighting, and angle. Face beautification can improve user satisfaction and engagement with photo editing applications.
Describe the solution you'd like
I would like the solution to enhance the appearance of facial features and skin texture in real time. The solution will be able to detect and adjust the lighting, color, contrast, sharpness, and smoothness of the face according to the user's preferences and the environment. The solution will also be able to apply various filters and effects to create different styles and moods. The solution will also be easy to use and compatible with different devices and platforms.
Describe alternatives you've considered
For face beautification, I have considered several alternative solutions besides my proposed method. These include traditional image processing techniques, such as smoothing, sharpening, and contrast enhancement, as well as deep learning-based approaches, such as generative adversarial networks (GANs), style transfer, and facial landmark detection.
Approach to be followed (optional)
For face beautification, the proposed method combines deep learning and geometric transformations. This approach can enhance facial features, remove blemishes, and adjust skin tone in a realistic and controllable manner.

Hi @akshitagupta15june , I'm a GSSoC'23 contributor. I would like to work on the above-mentioned project. Kindly assign this to me.
Thank you.

@shashanksbharadwaj161 you have been assigned the issue


AzureFunctionApp@1 often fails with 'Resource '****' doesn't exist. Resource should exist before deployment.'

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name:  AzureFunctionApp@1
list here (V# not needed):
https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureFunctionAppV1
Environment

Server - Azure Pipelines or TFS on-premises?

Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

Failed Build : https://dev.azure.com/mstack/test-project2/_build/results?buildId=3552
Succeeded : https://dev.azure.com/mstack/test-project2/_build/results?buildId=3545

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:  ubuntu-latest

Issue Description
When rerunning a build and deployment pipeline that only deploys a demo function, I get mixed results. Half the time it succeeds, half the time it gives the same error message.
##[error]Error: Resource 'demo-function-pub' doesn't exist. Resource should exist before deployment.
To display the problem I've created a public function app called demo-function-pub using bicep, and am trying to deploy to that function app. The function app is created ONCE with bicep (manually from my dev PC), and deployed to multiple times (14 to be exact) by rerunning the pipline from the DevOps portal.
When doing 14 deploys to an existing resource of the same unchanged code, 7 fail with the error message
[Include task name(s), screenshots and any other relevant details]
List of manual triggers of the pipeline. Mixed results when deploying unchanged code to existing resource.

Deployment task:
- stage: Deploy
  displayName: Deploy stage
  dependsOn: Build
  condition: succeeded()
  jobs:
  - deployment: Deploy
    displayName: Deploy
    environment: $(environmentName)
    pool:
      vmImage: $(vmImageName)
    strategy:
      runOnce:
        deploy:
          steps:
          - task: AzureFunctionApp@1
            displayName: 'Azure Functions App Deploy: func-rp-alt-westeurope-orch'
            inputs:
              azureSubscription: '$(azureSubscription)'
              appType: functionAppLinux
              appName: $(functionAppName)
              package: '$(Pipeline.Workspace)/drop/$(Build.BuildId).zip'
              deploymentMethod: zipDeploy

Bicep file (to show that its really straight forward function app)
resource storageAccount 'Microsoft.Storage/storageAccounts@2021-06-01' = {
  name: toLower('strpalt${resourceGroup().location}${applicationNamePart}')
  location: resourceGroup().location
  kind: 'StorageV2'
  properties: {
    accessTier: 'Hot'
    encryption: {
      services: {
        file: {
          enabled: true
          keyType: 'Account'
        }
        blob: {
          enabled: true
          keyType: 'Account'
        }
        queue: {
          enabled: true
          keyType: 'Account'
        }
        table: {
          enabled: true
          keyType: 'Account'
        }
      }
      keySource: 'Microsoft.Storage'
    }
    supportsHttpsTrafficOnly: true
    minimumTlsVersion: 'TLS1_2'
  }
  sku: {
    name: 'Standard_LRS'
  }
  tags: {
    role: 'App Service Plan Storage'
    version: versionTagValue
  }
}

resource appInsights 'Microsoft.Insights/components@2020-02-02' = {
  name: 'appi-asp-${applicationNamePart}'
  location: resourceGroup().location
  kind: 'web'
  properties: {
    Application_Type: 'web'
    publicNetworkAccessForIngestion: 'Enabled'
    publicNetworkAccessForQuery: 'Enabled'
  }
  tags: {
    role: 'Application Insights'
    version: versionTagValue
  }
}

var functionName = 'demo-function-${applicationNamePart}'

resource functionApp 'Microsoft.Web/sites@2021-02-01' = {
  name: functionName
  location: resourceGroup().location
  kind: 'functionapp,linux'
  properties: {
    httpsOnly: true
    serverFarmId: servicePlan.id
    reserved: true
    siteConfig: {
      scmType: 'VSTSRM'
      cors: {
        allowedOrigins: [
          'https://portal.azure.com'
        ]
      }
      alwaysOn: true
      appSettings: [
        {
          name: 'AzureWebJobsStorage'
          value: 'DefaultEndpointsProtocol=https;AccountName=${storageAccount.name};AccountKey=${listKeys(storageAccount.id, storageAccount.apiVersion).keys[0].value};EndpointSuffix=${environment().suffixes.storage}'
        }
        {
          name: 'APPINSIGHTS_INSTRUMENTATIONKEY'
          value: appInsights.properties.InstrumentationKey
        }
        {
          name: 'FUNCTIONS_EXTENSION_VERSION'
          value: '~4'
        }
        {
          name: 'FUNCTIONS_WORKER_RUNTIME'
          value: 'dotnet-isolated'
        }
        {
          name: 'APPLICATIONINSIGHTS_CONNECTION_STRING'
          value: appInsights.properties.ConnectionString
        }
      ]
      linuxFxVersion: 'DOTNET-ISOLATED|6.0'
      webSocketsEnabled: true
    }
  }
  tags: {
    role: 'Function App for demo purposes'
    version: versionTagValue
  }
}

Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Deploy_Failed.txt
Deploy_Success.txt
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]
##[error]Error: Resource 'demo-function-pub' doesn't exist. Resource should exist before deployment.

I'm having the same problem.  I had a problem with this earlier this week but after a couple of hours it worked as expected.  Today it has been 6 hours after creating the resource (function app) and Azure Devops still doesn't think it exists.

@safari137,@v-saikumart , @PhilipsonJoseph
it seems related to
https://github.com/microsoft/azure-pipelines-tasks/issues/15532

Over the last weekend I've done c.a. 30 deploys which all were successfull (c.a. 2 days after the resource was created).
So this seems to support that it only affects newly created resources for a period of time (e.g. couple of hours according to @safari137 ).
Is there some kind of consistency issue?

Hi @wkoeter
We are already tracking same issue on https://github.com/microsoft/azure-pipelines-tasks/issues/15532, so we are closing this.
Thank you.


Increase inference performance on Jetson Nano + issues with ctx=gpu()

Hi all! Currently I’m developing with the Jetson Nano, and I’m looking for advice in regards to improving inference performance. I’m using Sagemaker as my training environment for SSD object detection with Resnet-50 as my base network, which exports .params and .json files for mxnet. I’ve built mxnet on the nano using the autoinstaller from the nvidia forum (https://forums.developer.nvidia.com/t/i-was-unable-to-compile-and-install-mxnet1-5-with-tensorrt-on-the-jetson-nano-is-there-someone-have-compile-it-please-help-me-thank-you/111303/25), and I’ve been able to infer via usb webcam by more or less following this guide:
https://aws.amazon.com/blogs/machine-learning/build-a-real-time-object-classification-system-with-apache-mxnet-on-raspberry-pi/
That said, my inference speed is really slow, i.e. it takes around 4-5 seconds per frame with an input size of 512x512. I’ve already tried converting my weights to a different architecture via onnx and mmdnn, but my custom model had operators that were not supported by either format so it looks like I’m stuck with mxnet. The mxnet website says that it has tensorrt integration with mxnet but I can’t find any good examples of that anywhere online. The one on the mxnet website is at best confusing and doesn’t help me in my particular use case
One thing that seems to be holding me back is that I’m only able to infer using the cpu. According to the mxnet website, to use the gpu all you have to do is change ctx=cpu() to ctx=gpu(), and make sure that your data is converted to float32 before inputting it (https://github.com/apache/incubator-mxnet/issues/13332). However, when I do that, it still crashes my Jetson because it seems to run out of memory. Does this have anything to do with the custom build of mxnet for the Nano? Otherwise why would it do that?
Any suggestions are welcome and appreciated!
Here’s my code:
`#import
import mxnet as mx
import numpy as np
import cv2, os, urllib, argparse, time
from collections import namedtuple
Batch = namedtuple('Batch', ['data'])
#array of object labels for custom network
object_categories = ['object 1','object 2']
#load model
""" important: make sure that -symbol.json and -0000.params are in the format network-prefix-symbol.json and network-prefix-0000.params and are located in current directory """
class ImagenetModel(object):
def __init__(self, synset_path, network_prefix, params_url=None, symbol_url=None, synset_url=None, context=mx.cpu(), label_names=['prob_label'], input_shapes=[('data', (1,3,10,10))]):
	# Load the network parameters from default epoch 0
	sym, arg_params, aux_params = mx.model.load_checkpoint(network_prefix, 0)
	# Load the network into an MXNet module and bind the corresponding parameters
	self.mod = mx.mod.Module(symbol=sym, label_names=label_names, context=context)
	self.mod.bind(for_training=False, data_shapes= input_shapes)
	self.mod.set_params(arg_params, aux_params)
	self.camera = None

def predict_from_cam(self, reshape=(512, 512), N=50):

	topN = []

	# Switch RGB to BGR format (which ImageNet networks take)
	img = cv2.cvtColor(frame, cv2.COLOR_BGR2RGB)
	if img is None:
		return topN

	# Resize image to fit network input
	img = cv2.resize(img, reshape)
	img = np.swapaxes(img, 0, 2)
	img = np.swapaxes(img, 1, 2)
	img = img[np.newaxis, :]

	# Run forward on the image
	self.mod.forward(Batch([mx.nd.array(img)]))
	prob = self.mod.get_outputs()[0].asnumpy()
	prob = np.squeeze(prob)
	global results
	results = [prob[i].tolist() for i in range(100)]

if name == "main":
parser = argparse.ArgumentParser(description="pull and load pre-trained resnet model to classify one image")
parser.add_argument('--img', type=str, default='cam', help='input image for classification, if this is cam it captures from the webcam')
parser.add_argument('--prefix', type=str, default='model_algo_1', help='the prefix of the pre-trained model')
parser.add_argument('--label-name', type=str, default='softmax_label', help='the name of the last layer in the loaded network (usually softmax_label)')
parser.add_argument('--synset', type=str, default='synset.txt', help='the path of the synset for the model')
args = parser.parse_args()
mod = ImagenetModel(args.synset, args.prefix, label_names=[args.label_name])
print ("predicting on "+args.img)
if args.img == "cam":
vid = cv2.VideoCapture(0)
while(True):
ret, frame = vid.read()
mod.predict_from_cam()
print(results)
cv2.imshow('frame', frame)
#wait x ms, search for escape keypress on cv2 frame
if cv2.waitKey (1000) & 0xFF == ord('q'):
break
vid.release()
cv2.destroyAllWindows()`

cc @TristonC whose team can best help.


[BUG] "ValueError: operands could not be broadcast together with shapes (135,) (199,)" during qsiprep

qsiprep fails during preprocessing due to value error.
qsiprep version: 0.9.0beta1
Call:
singularity run --cleanenv -B ${data_root}:/data --nv ${img} \
${niidir} ${outdir} participant --work-dir ${workdir} \
--participant-label ${sub} --skip_bids_validation \
--low-mem --mem-mb 47000 --nthreads 1 --omp-nthreads 1 \
--distortion-group-merge average --combine-all-dwis \
--output-resolution 1.5 --force-spatial-normalization \
--eddy-config eddy_params.json \
--fs-license-file ${fs_license}

eddy_params.json:
{ "flm": "linear", "slm": "linear", "fep": false, "interp": "spline", "nvoxhp": 1000, "fudge_factor": 10, "dont_sep_offs_move": false, "dont_peas": false, "niter": 5, "method": "jac", "repol": true, "num_threads": 1, "is_shelled": true, "use_cuda": true, "cnr_maps": true, "residuals": false, "output_type": "NIFTI_GZ", "args": "" }
crash-20200728-122829-anxiousmisery-distortion_merger-8b38500e-d99c-4467-8b5f-166203ea5005.txt
qsiprep_sub-NDARPK532CVC_8193119.o.txt

This participant had their DWI sequences interrupted twice. All of our participants have two pairs (opposite PE) of dir-98 and two pairs of dir-99, with 99 and 100 volume acquisitions, respectively. This participant had both of their PA scans interrupted (dir-98 had 96/99 volumes and dir-99 had 39/100 volumes).

Based on the error message, it seems like the interrupted scans are preventing the distortion group merge from working. For the HCP-style merging you need to have scans with matching bvals/bvecs in both directions. This subject might not be usable


Add curator as optional deployment

The helm chart should be able to also deploy an curator job like:
CFG Map
[zell zeebe-benchmark/ ns:zell-helm]$ cat setup/curator-configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: curator-config
  labels:
    app: curator
data:
  action_file.yml: |-
    ---
    # Remember, leave a key empty if there is no value.  None will be a string,
    # not a Python "NoneType"
    #
    # Also remember that all examples have 'disable_action' set to True.  If you
    # want to use this action as a template, be sure to set this to False after
    # copying it.
    actions:
      1:
        action: delete_indices
        description: "Clean up ES by deleting old indices"
        options:
          timeout_override:
          continue_if_exception: False
          disable_action: False
          ignore_empty_list: True
        filters:
        - filtertype: age
          source: name
          direction: older
          timestring: '%Y-%m-%d'
          unit: days
          unit_count: 1
          field:
          stats_result:
          epoch:
          exclude: False
  config.yml: |-
    ---
    # Remember, leave a key empty if there is no value.  None will be a string,
    # not a Python "NoneType"
    client:
      hosts:
        - elasticsearch-master-headless
      port: 9200
      url_prefix:
      use_ssl: False
      certificate:
      client_cert:
      client_key:
      ssl_no_validate: False
      http_auth:
      timeout: 30
      master_only: False
    logging:
      loglevel: INFO
      logfile:
      logformat: default
      blacklist: ['elasticsearch', 'urllib3']

Cronjob
[zell zeebe-benchmark/ ns:zell-helm]$ cat setup/curator-cronjob.yaml
# https://medium.com/@hagaibarel/running-curator-as-a-kubernetes-cronjob-19eaab9afd3b
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: curator
  labels:
    app: curator
spec:
  schedule: "0 3 * * *" # run every 03:00 AM daily
  successfulJobsHistoryLimit: 1
  failedJobsHistoryLimit: 3
  concurrencyPolicy: Forbid
  startingDeadlineSeconds: 120
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - image: bobrik/curator:5.7.6
            name: curator
            args: ["--config", "/etc/config/config.yml", "/etc/config/action_file.yml"]
            volumeMounts:
            - name: config
              mountPath: /etc/config
          volumes:
          - name: config
            configMap:
              name: curator-config
          restartPolicy: OnFailure

Seems to be no need from the community yet

Today, I had a Camunda Cloud customer asking for guidance on data retention after having 18 months worth of data accumulated and running into limits of the number of indexes and shards in Elasticsearch. So it would be a very useful addition to the Helm charts.
However, the ones from the benchmarks might be too aggressive for production use:
https://github.com/camunda-cloud/zeebe/blob/develop/benchmarks/setup/default/curator-configmap.yaml
https://github.com/camunda-cloud/zeebe/blob/develop/benchmarks/setup/default/curator-cronjob.yaml


Add a mechanism for removing images from the site

Right now it’s an ad hoc process – we should have a script that:

Updates the flag in VHS to say “not cleared for the catalogue API”
Sends a notification to SNS, so it trickles through the pipeline – because we don‘t get notifications of changes on the Miro table

We have a request to remove four images from the library site (see email from 2 January), which is the impetus for writing this now.

Oh hey, I wrote a script for this!


[Issue #491] refactor: user profile same id as supertokens

Description
Changes the UserProfile table so its primary key is the same as the table in the supertokens table.
Before, if I had the id for a userProfile, I would have to fetch that info from the DB to get its userId just to e.g. see the wallets or addresses associated with it. Now id and userId are the same thing, which is what before was called userId.
Test plan
Nothing should change.

Was there a reason why we made them different in the first place?

Was there a reason why we made them different in the first place?

I think it was an overlook on my part.


Docker Hub -> Docker Store?

You mentioned in second step:
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
isn't it now Docker Store?

Nope, Hub is still accurate.  The images are displayed on Store, but
they're pushed and pulled from Hub. 👍


Check dir supplied to copier exists before going through questions

Actual Situation
One may accidentally run a copier copy command without making a new directory first if that's desired.
Desired Situation
I'd want the dir to be created for me, or an error message that comes up telling me the dir doesn't exist before filling in the template.
Proposed solution
Should be a pretty simple check to make, happy to open a PR for this.
Couldn't find this issue documented anywhere, so apologies if this is already supported with a flag or asked elsewhere.
edit: after playing around, I can see that the creation behavior is what happens (but errored on a particular string if the directory is read-only, e.g. /path/to/dir). Happy to close this, but I'd probably like it documented somewhere fairly early in the README that this is what happens!

That's pretty much implied by the first example:

copier copy path/to/project/template path/to/destination

I don't think adding troubleshooting notes early in the README is a good idea, but I'm not opposed to it either. Maybe Copier could instead output a useful error message when the destination directory is read-only.

+1 for the read-only error! You end up with a FileNotFoundError first if that directory doesn't exist.
regarding docs: I submitted some text in #1498 that I think should flag it minimally in the README, and a little more explicitly in the template generation page.

I don't think this is a good idea.
In case you run copy over a preexisting dir, copier will copy on it, just like it should do.
If the dir happens to be a git-tracked template that contains an answers file, you can use copy as a recopy alternative. Sometimes an upstream template lacks some patches, then you need to use a downstream template with those patches and you need to change the origin of the template. The only official way to do that is to issue a copy command over a preexisting template.
Let me close this request because it breaks expected behaviours, just to keep the issue tracker clean. But you can keep commenting if you want 😉

@yajo the suggestion was to handle the case where the destination directory already exists but is read-only, meaning Copier will never be able to write into it (be it for an update or a recopy). But after actually testing this out, it seems we already get a PermissionError, which is explicit enough I think.


Switch redocusaurus for cloud-annotations/docusaurus-openapi

https://github.com/cloud-annotations/docusaurus-openapi provides a style of documentation generation that I prefer, and as a bonus where redocusaurus and #188 didn't easily get along, this plugin provides the 'Execute' button.

https://www.npmjs.com/package/docusaurus-plugin-openapi-docs is though!


Time in specific timezone

Hello I would like to propose a change to the library inside the file countdown_timer_controller.dart
int remainingTimeStamp =
(_endTime - DateTime.now().millisecondsSinceEpoch) ~/ 1000;
I am making a app that should countdown time before a key is available in specific timezone but the problem is that whatever I do DateTime.now() will always use the current timezone of the user.
This line should be changed with optional parameter of specific timezone to be passed so the time is timezone agnostic

OK, I will try to open the current time to get parameters.


Implement ECS Draining Auto Scaling Lifecycle Hook

This is awesome 🎉
I confirmed that an unhealthy container instance was drained using Auto Scaling Groups and AWS Lambda using the following process:

Retrieved the Auto Scaling Group instances:

aws autoscaling describe-auto-scaling-groups \
  --auto-scaling-group-name ecs-default-cluster-Sandbox-EcsClusterAutoScaleGroupSandbox-CLJKMQ0V93DL \
  --region us-west-2 \
  --query 'AutoScalingGroups[*].Instances[*].InstanceId' | grep -o -E 'i\-[a-f0-9]+'

Marked an instance as unhealthy:

$ aws --region us-west-2 \
  autoscaling set-instance-health \
  --health-status Unhealthy \
  --instance-id i-08a1e4cc74fbded49

Checked that the Container Instance entered a DRAINING status.

Checked that the Lambda function was invoke.

This is awesome 🎉
I confirmed that an unhealthy container instance was drained using Auto Scaling Groups and AWS Lambda using the following process:

Retrieved the Auto Scaling Group instances:

aws autoscaling describe-auto-scaling-groups \
  --auto-scaling-group-name ecs-default-cluster-Sandbox-EcsClusterAutoScaleGroupSandbox-CLJKMQ0V93DL \
  --region us-west-2 \
  --query 'AutoScalingGroups[*].Instances[*].InstanceId' | grep -o -E 'i\-[a-f0-9]+'

Marked an instance as unhealthy:

$ aws --region us-west-2 \
  autoscaling set-instance-health \
  --health-status Unhealthy \
  --instance-id <instance-id>

Checked that the Container Instance associated with that instance ID entered a DRAINING status.

Checked that the Lambda function was invoked.


Piano_Playing_Game Added

Piano_Playing_Game Added
#607

Can you please review this pr @panwar8279

@panwar8279

@panwar8279 Please Review this at once!

Can you please review this pr @panwar8279

Can you please merge @panwar8279 @raj03kumar because I have another pr in this repo and if you didn't merge it I won't able to do another pr and that pr time going to up please merge this pr @panwar8279 @raj03kumar

can you please merge my pr @panwar8279 @raj03kumar

@panwar8279 please review!

Can you please review this pr @panwar8279


Clone also the non-current slides (but make them invisible), so that …

…the CSS counter() and maybe other style rules that depend on the presence of other slides continue to work.
That means that for every displayed slide and new copy of the whole slide set is loaded in memory. But it is hard to know what parts of the slide set you can omit without affecting the style of the slide that should be shown.

do you have an example slideset to illustrate this? I wouldn't want to make this the default behavior given the impact on memory; I could imaging this being made possible via an optional attribute, but an example would help identify maybe alternative approaches?

Here is an example:
https://www.w3.org/2024/09/25-cg-revamp-minutes.html


Non-metric rasters will now get converted

Resolves #24 .  I'm a little embarrassed to have left this out previously.
I think that when conversions are necessary they slow processing down by about 10%, and that when they're not necessary the if-then check has no appreciable impact on speed.  But it's hard to be sure because this is within the variance from one run to another on my laptop, which I suppose is another way of saying the impact of this isn't a big deal.

LGTM. I have major doubts that adding in a multiplication causes a 10% slowdown, so it's probably just variance, as you say.


feat: jump state support in devtools

Inspired by https://github.com/pmndrs/zustand/pull/590 - mutating the object when the message.state is safe (no actionsById, which happens in state jumping)
It worked for me, it's up to @dai-shi if he wants to see if this works well!

Would anyone like to check the behavior?


pythonPackages.zstd: <IP_ADDRESS> -> <IP_ADDRESS>

Motivation for this change
Things done

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

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

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

Notify maintainers
cc @

@GrahamcOfBorg build python27Packages.zstd python37Packages.zstd

Built and tested successfully on Darwin with nix-review. It looks good to me.


Updated Security Client APIs

Description
Updated Security Client APIs
Issues Resolved
Related to #435,
Relevant PRs
https://github.com/opensearch-project/opensearch-py/pull/399, https://github.com/opensearch-project/opensearch-py/pull/442
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Renamed the following APIs:

“put_user”  to  “create_user”.
“put_role” to“create_role”.
“delete_role_mappings” to “delete_role_mapping”.
“put_role_mappings” to “create_role_mapping”.
“put_tenant” to “create_tenant”.
“put_audit_configuration” to “update_audit_config”.
"put_action_group"   to "create_action_group"
"put_configuration" to  "update_configuration"
"put_distinguished_names" to "update_distinguished_names"

And also made few other changes to the APIs to maintain uniformity.

@VachaShah, please review and merge this PR. It needs to be done before upcoming python release. Thank you :)

Should I be concerned by the amount of changes and so few in tests?

I made changes with utmost care. But, it is true that Test coverage is low

Hello @florianvazelle, I request you to take a look at these changes. Please let me know if you notice anything wrong.

LGTM :slightly_smiling_face:

@florianvazelle The naming follows the documentation: For example, it's create_user instead of put_user because we call it create user on OS website: https://opensearch.org/docs/latest/security/access-control/api/#create-user
The moving of security plugin endpoints to security namespace (i.e. client.security.create_user for example) along with renaming is to keep the PY client consistent with our API spec. For example, this is the spec for the PUT _plugins/_security/api/internalusers/ endpoint.
The API generator for PY that @saimedhi has been working on will also generate code for all security endpoints based off of that spec. So we're making sure that these endpoints will have the same names and same location in the PY client as they will soon be replaced by generated code.
Hope that's answered your question.

@VachaShah, @dblock Please let me know if any further changes needed. I added working sample and few tests as suggested.

Merged, thanks.


VLQ: Tests update

Split TestEncodeDecodeVarint() into TestDecodeVarint() and TestEncodeVarint() making it easy to work on the exercise one function at a time.

Looks good and necessary. Thanks.


Content is loaded but remains hidden.

The content is loaded properly, but remains hidden.
If I remove class="hidden" in inspect mode, the content shows up. Anyone has any idea why the class hidden stays active even when content is loaded?
Removing
.hidden {
    opacity: 0
}

would obviously be a quick fix, but with the consequence that all content is loaded simultaneously. I'd prefer a fix where animsition works again like it used to.
Thanks in advance for any replies
mikeswildens.nl
(For now I've removed class .hidden, so my content is visible for any visitors)

Any updates on this? I'm seeing the same issue.
Thanks!


rpmcfg.py: enable pushing release commit to origin

Ref. https://github.com/openshift/ocp-build-data/pull/74/files
Fix for https://bugzilla.redhat.com/show_bug.cgi?id=1694183
A standard doozer RPM build is less intrusive to the source repo than
the usual tito flow because the commit it uses for the build isn't
pushed back to origin; the origin commit is tagged and the tag pushed
but the release commit is discarded.
The minor problem with this is that tito release injects the commit
hash it releases right into the build release, and this hash will never
be present in the source repo.
It turns out that for the openshift RPM, something really cares about
that git hash being available in the source repo for validation. So this
change enables an option to push that release commit back to the source.
Also the openshift RPM has specialized tito config already. Doozer logic
already imitates it pretty well, but it seems wisest to minimize
deviations from upstream by actually using the tito config to tag and
release; so now the logic can be configured to do that.

/lgtm


Make syntax and compile errors highlight/underline issues inline inside the code file

It would be nice if this plugin worked like other language plugins and it underlined syntax or compile errors inline inside the code file, where also just like other plugins if you hovered over the underlined issue it would give you more information.

Moved https://github.com/tfehlmann/vscode-snakefmt-provider/issues/9


Test spwrap to be used inside EJB CMT and BMT transactions

Test will be on jboss7.1
attached is the test project used
ejb-test-spwrap-web.gz

Reference

https://docs.oracle.com/javaee/7/tutorial/transactions.htm#BNCIH
http://www.developerscrappad.com/547/java/java-ee/ejb3-x-jpa-when-to-use-rollback-and-setrollbackonly/


When I set find_unused_paramters=True, the val mAP results are all 0. While without find_unused_paramters=True, I got RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one.

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
I try to build a mask-rcnn model with my own backbone and neck. The meta-arch of my model is modified from the _base_/models/mask_rcnn_r50_fpn.py.
But during training, I got RuntimeError(Expected to have finished reduction in the prior iteration before starting a new one. ).
~ - mmdet - INFO - workflow: [('train', 1)], max: 55 epochs
~ - mmdet - INFO - Checkpoints will be saved to path by HardDiskBackend.
Traceback (most recent call last):
  File "tools/train.py", line 220, in <module>
    main()
  File "tools/train.py", line 209, in main
    train_detector(
  File "~/mmdet/mmdet/apis/train.py", line 208, in train_detector
    runner.run(data_loaders, cfg.workflow)
  File "~/miniconda3/envs/mm/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 127, in run
    epoch_runner(data_loaders[i], **kwargs)
  File "~/miniconda3/envs/mm/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 50, in train
    self.run_iter(data_batch, train_mode=True, **kwargs)
  File "~/miniconda3/envs/mm/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 29, in run_iter
    outputs = self.model.train_step(data_batch, self.optimizer,
  File "~/miniconda3/envs/mm/lib/python3.8/site-packages/mmcv/parallel/distributed.py", line 42, in train_step
    and self.reducer._rebuild_buckets()):
RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by (1) passing the keyword argument `find_unused_parameters=True` to `torch.nn.parallel.DistributedDataParallel`; (2) making sure all `forward` function outputs participate in calculating loss. If you already have done the above two steps, then the distributed data parallel module wasn't able to locate the output tensors in the return value of your module's `forward` function. Please include the loss function and the structure of the return value of `forward` of your module when reporting this issue (e.g. list, dict, iterable).

I try to find the exact break point. I find that the training loop was broke just after the first run_iter in train of EpochBasedRunner. The losses returned by run_iter was normal.
class EpochBasedRunner(BaseRunner):
...
    def train(self, data_loader, **kwargs):
        self.model.train()
        self.mode = 'train'
        self.data_loader = data_loader
        self._max_iters = self._max_epochs * len(self.data_loader)
        self.call_hook('before_train_epoch')
        time.sleep(2)  # Prevent possible deadlock during epoch transition
        for i, data_batch in enumerate(self.data_loader):
            self._inner_iter = i
            self.call_hook('before_train_iter')
            self.run_iter(data_batch, train_mode=True, **kwargs)
            self.call_hook('after_train_iter')
            self._iter += 1

        self.call_hook('after_train_epoch')
        self._epoch += 1

I have seen several issues with the similiar problem,  while the other issues with the same RuntimeError have more error info as follows. (for example in #2377)
Traceback (most recent call last):
  File "tools/train.py", line 142, in <module>
    main()
  File "tools/train.py", line 138, in main
    meta=meta)
  File "/home/fitlab/NiCk/mmdetection/mmdet/apis/train.py", line 102, in train_detector
    meta=meta)
  File "/home/fitlab/NiCk/mmdetection/mmdet/apis/train.py", line 182, in _dist_train
    runner.run(data_loaders, cfg.workflow, cfg.total_epochs)
  File "/home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/mmcv/runner/runner.py", line 359, in run
    epoch_runner(data_loaders[i], **kwargs)
  File "/home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/mmcv/runner/runner.py", line 263, in train
    self.model, data_batch, train_mode=True, **kwargs)
  File "/home/fitlab/NiCk/mmdetection/mmdet/apis/train.py", line 75, in batch_processor
    losses = model(**data)
  File "/home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/nn/modules/module.py", line 541, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/nn/parallel/distributed.py", line 459, in forward
    self.reducer.prepare_for_backward([])
RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by (1) passing the keyword argument `find_unused_parameters=True` to `torch.nn.parallel.DistributedDataParallel`; (2) making sure all `forward` function outputs participate in calculating loss. If you already have done the above two steps, then the distributed data parallel module wasn't able to locate the output tensors in the return value of your module's `forward` function. Please include the loss function and the structure of the return value of `forward` of your module when reporting this issue (e.g. list, dict, iterable). (prepare_for_backward at /pytorch/torch/csrc/distributed/c10d/reducer.cpp:518)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7fdbbca8b813 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libc10.so)
frame #1: c10d::Reducer::prepare_for_backward(std::vector<torch::autograd::Variable, std::allocator<torch::autograd::Variable> > const&) + 0x734 (0x7fdc054d0654 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #2: <unknown function> + 0x7bed8a (0x7fdc054bed8a in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #3: <unknown function> + 0x210ba4 (0x7fdc04f10ba4 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #4: _PyMethodDef_RawFastCallKeywords + 0x264 (0x561b42058114 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #5: _PyCFunction_FastCallKeywords + 0x21 (0x561b42058231 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #6: _PyEval_EvalFrameDefault + 0x52cf (0x561b420bce8f in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #7: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #8: _PyFunction_FastCallDict + 0x400 (0x561b42012a30 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #9: _PyObject_Call_Prepend + 0x63 (0x561b4202d943 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #10: PyObject_Call + 0x6e (0x561b42020b9e in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #11: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #12: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #13: _PyFunction_FastCallDict + 0x400 (0x561b42012a30 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #14: _PyObject_Call_Prepend + 0x63 (0x561b4202d943 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #15: <unknown function> + 0x17512a (0x561b4206c12a in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #16: PyObject_Call + 0x6e (0x561b42020b9e in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #17: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #18: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #19: _PyFunction_FastCallDict + 0x400 (0x561b42012a30 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #20: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #21: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #22: _PyFunction_FastCallDict + 0x1d5 (0x561b42012805 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #23: _PyObject_Call_Prepend + 0x63 (0x561b4202d943 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #24: PyObject_Call + 0x6e (0x561b42020b9e in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #25: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #26: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #27: _PyFunction_FastCallKeywords + 0x387 (0x561b42057917 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #28: _PyEval_EvalFrameDefault + 0x6a0 (0x561b420b8260 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #29: _PyEval_EvalCodeWithName + 0xc30 (0x561b42012030 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #30: _PyFunction_FastCallKeywords + 0x387 (0x561b42057917 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #31: _PyEval_EvalFrameDefault + 0x14e6 (0x561b420b90a6 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #32: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #33: _PyFunction_FastCallKeywords + 0x387 (0x561b42057917 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #34: _PyEval_EvalFrameDefault + 0x14e6 (0x561b420b90a6 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #35: _PyFunction_FastCallKeywords + 0xfb (0x561b4205768b in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #36: _PyEval_EvalFrameDefault + 0x416 (0x561b420b7fd6 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #37: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #38: PyEval_EvalCodeEx + 0x44 (0x561b420125f4 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #39: PyEval_EvalCode + 0x1c (0x561b4201261c in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #40: <unknown function> + 0x21c974 (0x561b42113974 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #41: PyRun_FileExFlags + 0xa1 (0x561b4211dcf1 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #42: PyRun_SimpleFileExFlags + 0x1c3 (0x561b4211dee3 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #43: <unknown function> + 0x227f95 (0x561b4211ef95 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #44: _Py_UnixMain + 0x3c (0x561b4211f0bc in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #45: __libc_start_main + 0xe7 (0x7fdc0f0b6b97 in /lib/x86_64-linux-gnu/libc.so.6)
frame #46: <unknown function> + 0x1d0990 (0x561b420c7990 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7fdbbca8b813 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libc10.so)
frame #1: c10d::Reducer::prepare_for_backward(std::vector<torch::autograd::Variable, std::allocator<torch::autograd::Variable> > const&) + 0x734 (0x7fdc054d0654 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #2: <unknown function> + 0x7bed8a (0x7fdc054bed8a in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #3: <unknown function> + 0x210ba4 (0x7fdc04f10ba4 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #4: _PyMethodDef_RawFastCallKeywords + 0x264 (0x561b42058114 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #5: _PyCFunction_FastCallKeywords + 0x21 (0x561b42058231 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #6: _PyEval_EvalFrameDefault + 0x52cf (0x561b420bce8f in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #7: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #8: _PyFunction_FastCallDict + 0x400 (0x561b42012a30 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #9: _PyObject_Call_Prepend + 0x63 (0x561b4202d943 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #10: PyObject_Call + 0x6e (0x561b42020b9e in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #11: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #12: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #13: _PyFunction_FastCallDict + 0x400 (0x561b42012a30 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #14: _PyObject_Call_Prepend + 0x63 (0x561b4202d943 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #15: <unknown function> + 0x17512a (0x561b4206c12a in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #16: PyObject_Call + 0x6e (0x561b42020b9e in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #17: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #18: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #19: _PyFunction_FastCallDict + 0x400 (0x561b42012a30 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #20: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #21: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #22: _PyFunction_FastCallDict + 0x1d5 (0x561b42012805 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #23: _PyObject_Call_Prepend + 0x63 (0x561b4202d943 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #24: PyObject_Call + 0x6e (0x561b42020b9e in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #25: _PyEval_EvalFrameDefault + 0x1e35 (0x561b420b99f5 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #26: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #27: _PyFunction_FastCallKeywords + 0x387 (0x561b42057917 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #28: _PyEval_EvalFrameDefault + 0x6a0 (0x561b420b8260 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #29: _PyEval_EvalCodeWithName + 0xc30 (0x561b42012030 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #30: _PyFunction_FastCallKeywords + 0x387 (0x561b42057917 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #31: _PyEval_EvalFrameDefault + 0x14e6 (0x561b420b90a6 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #32: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #33: _PyFunction_FastCallKeywords + 0x387 (0x561b42057917 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #34: _PyEval_EvalFrameDefault + 0x14e6 (0x561b420b90a6 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #35: _PyFunction_FastCallKeywords + 0xfb (0x561b4205768b in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #36: _PyEval_EvalFrameDefault + 0x416 (0x561b420b7fd6 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #37: _PyEval_EvalCodeWithName + 0x2f9 (0x561b420116f9 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #38: PyEval_EvalCodeEx + 0x44 (0x561b420125f4 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #39: PyEval_EvalCode + 0x1c (0x561b4201261c in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #40: <unknown function> + 0x21c974 (0x561b42113974 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #41: PyRun_FileExFlags + 0xa1 (0x561b4211dcf1 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #42: PyRun_SimpleFileExFlags + 0x1c3 (0x561b4211dee3 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #43: <unknown function> + 0x227f95 (0x561b4211ef95 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #44: _Py_UnixMain + 0x3c (0x561b4211f0bc in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)
frame #45: __libc_start_main + 0xe7 (0x7fdc0f0b6b97 in /lib/x86_64-linux-gnu/libc.so.6)
frame #46: <unknown function> + 0x1d0990 (0x561b420c7990 in /home/fitlab/NiCk/anaconda3/envs/nick_rs/bin/python)

There is ONLY one issue (#2883) that is almost the same as this issue. While unfortunately, this issue has not received a valid answer and was closed.
I try to follow #2377 to set find_unused_paramters=True, the training and evaluating process were normal. But I got the val results as follows.
~ - mmdet - INFO - Evaluating bbox...
Loading and preparing results...
DONE (t=0.00s)
creating index...
index created!
Running per image evaluation...
Evaluate annotation type *bbox*
DONE (t=0.48s).
Accumulating evaluation results...
DONE (t=0.09s).
~ - mmdet - INFO -
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.000
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=1000 ] = 0.000
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=1000 ] = -1.000
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.000
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.000
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=300 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.000

~ - mmdet - INFO - Evaluating segm...
Loading and preparing results...
DONE (t=0.00s)
creating index...
index created!
Running per image evaluation...
Evaluate annotation type *segm*
DONE (t=0.32s).
Accumulating evaluation results...
DONE (t=0.09s).
2022-04-24 00:02:21,774 - mmdet - INFO -
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.000
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=1000 ] = 0.000
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=1000 ] = -1.000
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.000
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.000
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=300 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.000
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.000

~ - mmdet - INFO - Exp name: mask_rcnn_gpwin8_sfp_ws_gn_cs.py
~ - mmdet - INFO - Epoch(val) [1][84]     bbox_mAP: 0.0000, bbox_mAP_50: 0.0000, bbox_mAP_75: -1.0000, bbox_mAP_s: 0.0000, bbox_mAP_m: 0.0000, bbox_mAP_l: 0.0000, bbox_mAP_copypaste: 0.000 0.000 -1.000 0.000 0.000 0.000, segm_mAP: 0.0000, segm_mAP_50: 0.0000, segm_mAP_75: -1.0000, segm_mAP_s: 0.0000, segm_mAP_m: 0.0000, segm_mAP_l: 0.0000, segm_mAP_copypaste: 0.000 0.000 -1.000 0.000 0.000 0.000

Could you please give me some ideas about the causes of such error and how to deal with it. Thx!
Reproduction

What command or script did you run?

A placeholder for the command.

Did you make any modifications on the code or config? Did you understand what you have modified?
What dataset did you use?

Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment information and paste it here.
You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

The problem may be caused by you modificaition to backbone and neck. Would you mind provide your code and your entire config file here?

The mask_rcnn_r50_fpn_1x_coco.py is okay for running. I think this error maybe caused by your own backbone and neck.

Sorry for the late response. 😅. Actually I have solved my problem. Indeed it is related to my backbone and neck. The current training and evaluation are normal. I checked the whole backbone and neck, and made several changes, later I will attach more details about the exact bug after I finished my current experiments.

Hi, I made some modifications to my custom backbone and stuck into similar problem. Could you please share your solution？


added ci.yml for acceptance tests.

reworks spec_helper to support multiple hosts
with different puppet versions.
rake task :ci runs tests on all included hosts.
-> currently: centos 6 with 4 puppet versions

if you are using ruby 1.8.7 make sure not to use rake 11.x.x It requires at minimum ruby 1.9.3.
For ruby 1.8.7 use rake < 11.0.0

Fixed in #231


[publish #36] Publish command must supply md5 hash of files

Coverage decreased (-1.2%) to 81.349% when pulling 1e6c74db13a1382cb4c2b5c0b056e9aedf7a32d6 on subhankarb:master into 81ca0974d2027ffcef8920b2fadf8dbb02418789 on frictionlessdata:master.

Looks fine


codegen: Use ExplicitValueOrControlFlow sparingly

ExplicitValueOrControlFlow (from now EVOCF) is only required when using control
flow features like return(ing from a function), continue or break inside
a match that yields a value, because yielding a value requires usage of an
IIFE. If those features aren't used, or the match doesn't yield a value, there
is no need to forward any control flow through the return channel.
This removes EVOCF instantiations from the clang -ftime-trace profile, since
most matches don't require AK::Variants.

Hello!
One or more of the commit messages in this PR do not match the Jakt code submission policy, please check the lint_commits CI job for more details on which commits were flagged and why.
Please do not close this PR and open another, instead modify your commit message(s) with git commit --amend and force push those changes to update this PR.


Can not ping tunl0 on my openstack vm -----strange question

I install k8s on my openstack cloud. The openstack use vxlan and linuxbridge for network.
Then I setup 3 vm on openstack and deploy single master k8s on it. Emmmm, the 3 vm are on two different physical machine and the k8s use calico which enable IPIP mode for network. Here come the strange question:
vm ip
vm3 <IP_ADDRESS>
vm2 <IP_ADDRESS>
vm1 <IP_ADDRESS>
vm3 and vm1 on the same physical machine openstack-17,vm2 on physical machine openstack-19.
route on vm3 (the physical machine is openstack-17)

I can ping tunl0 on vm2

But I can not ping tunl0 on vm1

vm1 vm2 vm3 are all in the same Security Group on my openstack which allow all traffic.
vm1-3 can ping each other

When I run calicoctl node status, it shows

Can you tell me how this happen? This cost me two days to debug. Thanks very much.

Are your screenshots from different nodes? Because they all look to have the same hostname. That could possibly be part of the problem. I'm thinking this because I noticed that each of the screen shots show the same tunl0 IP address and I believe those should be unique for each of the hosts.

@tmjd
Thank you for your reply, i found the issue and solve it. The reason is Openstack Security Group stop the IPIP packet.


How do I write a tars UDP service?

As with normal services, the address should start with udp when binding.

和普通服务一样的，绑定的时候地址用udp开头应该就行了。


Fix setData

This fixes issues #1324 and #1326 by:

only overwriting values set by setData with setInits if the value from setData is NA.
warning users if they try to overwrite a value set by setData in setInits and the setInits value is different from the setData value and not NA.
adding an includeRHSonly flag to isDeterm with default FALSE and then updating some uses of isDeterm in our codebase to set includeRHSonly to TRUE.
fixing #1326 by indexing into varValue (when checking for deterministic data) and isDataVarValue (when setting data flags) using eval with the scalar node names (similar to how isDataFromGraphID works). This avoids setting the data flag to TRUE for deterministic and RHSonly elements of a variable that has data elements. Note that positions in isDataEnv$x can still be TRUE for positions that do not correspond to any nodes (e.g., if x[1] is not defined at all in the model, but the user provides a non-NA value for x[1] in setData).

Note that I have not yet added various tests, in particular the CR-type example where there are undefined nodes in a variable, such as y[i, 3:6] defined but y[i, 1:2] undefined. I will also review the changes again carefully.

Per discussion in NCT issue 457, this approach won't work because it prevents use of setInits to generally change values.
See next PR that avoids the RHSonly as data issue and simply addresses determ nodes as data.