Define SYCL_LANGUAGE_VERSION even without including CL/sycl.hpp

I want a quick way to test whether my code is being compiled by a SYCL compiler or not.  This would allow me to use compile-time directives to only compile SYCL code when using a SYCL compiler and fall back to vanilla C++ otherwise.
The DPC++ compiler defines the macro SYCL_LANGUAGE_VERSION even if CL/sycl.hpp has not been included yet.  This allows me to test whether SYCL_LANGUAGE_VERSION is defined without trying to including SYCL first.  Here's a minimal example of what I would like to work.
#if defined(SYCL_LANGUAGE_VERSION) || defined(CL_SYCL_LANGUAGE_VERSION)
  #include <CL/sycl.hpp>
  // include other SYCL code
#else
  static_assert(false, "Not using SYCL compiler.");
#endif

int main(int argc, char** argv) { return 0; }

The above example works as I would expect with the DPC++ compiler.  In hipSYCL, it fails with the static assert case because SYCL_LANGUAGE_VERSION and CL_SYCL_LANGUAGE_VERSION have not yet been defined.  They will only be defined once CL/sycl.hpp is included, as far as I can tell.
If applicable, describe alternatives you've considered
Another macro or workaround would be fine, although I would prefer to have a cross-platform solution so I don't have to test a separate define for each compiler.

After a bit more experimentation, I see that __HIPSYCL__ is defined.  This works for my use case, but I would still prefer a cross-platform solution.  (Maybe this would require an update in the standard?)

I don't think the standard can guarantee that this works, because the standard explicitly allows library-only implementations. In such an implementation, the SYCL implementation is just a library for third-party compilers, and in this case the only way you can define macros is inside the header (unless you want to rely on specific build systems).
As such, I don't think there can be a solution that is guaranteed to work across all implementations in the way you intend.
Generally, syclcc only defines macros starting with __. We can consider whether it makes sense to pull  that macro definition inside syclcc, but I think it's better placed where it currently is:

hipSYCL supports library-only use cases. In principle the supported SYCL standard might then also depend on the third-party compiler that is chosen by the user, which may be more reliably detected from the header file instead of syclcc.
Currently SYCL_* macros are all set in the header files, while __* macros are set by syclcc (with the exception of __SYCL_DEVICE_ONLY__, which is beyond the control of syclcc in some cases`), so keeping it inside the header will be more consistent.

Another approach could be to test with #if __has_include() whether the SYCL header exists, and only then include it. __has_include is widely supported on basically any C++ compiler.

All excellent points.  I am closing this and will use __has_include for now.


Revert "Added Improved_Password_Generator.py"

The code is not visible to me @yash-gulatii
Can you check it once?

Sorry it was a glitch added new pr here https://github.com/MrB141107/Python_Projects/pull/9


No version match with wildcard

Current behavior
When using only * in a crate version, a "No match" message appears, even though this is valid and cargo will accept it.
This does not happen if I use 0.* or any other string that doesn't just contain a wildcard.
Expected behavior
The "No match" message should not appear.
Additional context/Screenshots
Expected behavior:

Current behavior:

Neovim version

nvim --version
NVIM v0.7.0
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -Wimplicit-fallthrough -Wsuggest-attribute=pure -Wsuggest-attribute=const -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/nvim/parts/nvim/build/build/config -I/build/nvim/parts/nvim/build/src -I/build/nvim/parts/nvim/build/.deps/usr/include -I/usr/include -I/build/nvim/parts/nvim/build/build/src/nvim/auto -I/build/nvim/parts/nvim/build/build/include
Compiled by root@lcy02-amd64-012

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

Should be fine now

Working as expected now, thanks!


Add exemplary programs

The capability library has multiple examples of single-file programs. This library, on the other hand, walks through a sample implementation in the README, but has no example programs; it would be nicer to have a whole example laid out in a single file instead of having to stitch together the README's code in order to run it.

Yes, I agree. I think this coincides with the need for more tests in general. I tested all the code on simple examples and some not-so-simple examples, but this is mostly undocumented. Time to bring more structure into the process, I will see what I can do.

I added some examples and tests in the "examples" folder.

Thanks! I'll make some time to check them later and give some feedback here if relevant.


Move defaulting and validation into webhook

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
In a follow-up PR I will ensure that we only default+validate once and at the highest possible level (e.G. MachineDeployment instead of Machine)
Defaulting of machines is now done via a webhook

/hold

/unhold

/hold cancel

@mrIncompetent all comments addressed, PTAL

/lgtm

/lgtm


Adding calendar to MS/Outlook provider causes error, Google does not.

When adding a new calendar for an Outlook provider, and the "description" is set, I get an error and the calendar is not added. The error is specific and tells me that I can't add this calendar due to setting the "description" (and apparently the timezone or location) which is helpful.  However, I feel like this should be a warning, not an error.
One of the main advantages of a standardized API is not having to modify code based off the provider.  So now when adding a Calendar I will need to check the provider first before adding certain elements descriptive elements. Is there something I'm missing on why this request becomes a full-stop error instead of just adding the calendar without a description? Curious your thoughts on is the API should be modified for this scenario.
Code

Calendar calendar = new Calendar();
calendar.setName("My Calendar");
calendar.setDescription("Calendar for UserId: " + appUserId);
calendar.getMetadata().put("UserId", appUserId.toString());
calendar = this.account.calendars().create(calendar);

Error when provider is MS/Outlook
ERROR com.nylas.RequestFailedException: statusCode=400, type=invalid_request_error, message=This provider only supports 'name'; does not support 'timezone', 'description', nor 'location'. 	at com.nylas.RequestFailedException.parseErrorResponse(RequestFailedException.java:84) 	at com.nylas.NylasClient.throwAndCloseOnFailedRequest(NylasClient.java:255) 	at com.nylas.NylasClient.executeRequest(NylasClient.java:239) 	at com.nylas.NylasClient.executeRequestWithAuth(NylasClient.java:204) 	at com.nylas.NylasClient.executePost(NylasClient.java:168) 	at com.nylas.RestfulDAO.create(RestfulDAO.java:88) 	at com.nylas.RestfulDAO.create(RestfulDAO.java:77) 	at com.nylas.RestfulDAO.create(RestfulDAO.java:69) 	at com.nylas.Calendars.create(Calendars.java:36)
Thanks!

@burtonrhodes Thank you for opening this issue and sorry for the delay. I've raised this issue internally and in our next major update for our API we are tackling issues like this by using standardized fields valid for all providers! Unfortunately we are not providing support for this in the existing v2.x of the Nylas API. When I have more news to share I will pass them along here to this ticket. Thanks again for your patience on this.


Update Ruby to 2.2.2

@kevgo @charlierudolph
Was getting warnings in the console output during tests with 2.2.0 for some reason.
/Users/allen/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-13/2.2.0-static/bigdecimal-1.2.7/bigdecimal.bundle: warning: already initialized constant BigDecimal::BASE
/Users/allen/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-13/2.2.0-static/bigdecimal-1.2.7/bigdecimal.bundle: warning: already initialized constant BigDecimal::EXCEPTION_ALL
/Users/allen/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-13/2.2.0-static/bigdecimal-1.2.7/bigdecimal.bundle: warning: already initialized constant BigDecimal::EXCEPTION_NaN
/Users/allen/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-13/2.2.0-static/bigdecimal-1.2.7/bigdecimal.bundle: warning: already initialized constant BigDecimal::EXCEPTION_INFINITY
/Users/allen/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-13/2.2.0-static/bigdecimal-1.2.7/bigdecimal.bundle: warning: already initialized constant BigDecimal::EXCEPTION_UNDERFLOW
...

Yay for living the state-of-the-art!   :ship:


Slice fragment GQL types not generated if not used in a document

Hi Guys,
A limitation exists with the approach this plugin has taken in generating the GQL schema.
Specifically, the Slices dynamic type generation is inferred from the existing slices used in a document. The types would not be generated if not used on any of the documents of that type.
That means that either the code would not work now or would not work when a slice is used for the first time.
For example, assume I have a custom type Page with a slice zone and the following three Slices: Text and Quote and Title.
If the Quote slice is not used on any of the Page document published in the repo - the schema would not generate the PrismicPageBodyQuote fragment.
This query would be invalid:
{
  allPrismicPage {
    edges {
      node {
        data {
          body {
            ... on PrismicPageBodyText {
              slice_type
            }
            ... on PrismicPageBodyTitle {
              slice_type
            }
            ... on PrismicPageBodyQuote {
              slice_type
            }
          }
        }
      }
    }
  }
}

Or in other words the union interface for the field body___NODE would not contain the type for the Quote slice.
Now, even if I were to force the existence of at least one Page with all slices used, this is still fragile since someone might alter that page.
Extremely related to that limitation is the fact that if only one of the slice types is ever used, say only the Text slice is ever used - the schema that is generated for body is an array of PrismicPageBodyText and not a union field.
This makes the schema incompatible since the __typename field does not exist on body at all. (If I were to query for it).
But this is how Gatsby works see here.
The (logical) assumption Gatsby makes for its developers is that the schema is stable so long as the definition does not change. Data can change with no code changes.
With the behavior described above data changes (adding a slice in the editing room which was never used before) changes the schema.
Suggestions:

Not sure if possible - but a way to retrieve metadata about types could resolve this (I don't think Prismic has some sort of an introspection API)
Choose another approach for modeling the GQL schema - instead of making "body" an array of a union - it would be an array of a common type which has slice_type and a payload field with a JSON serialization of the actual slice data. (Yaiks!)
If all fails - as a hackish workaround - always push with all documents with a slice zone empty slices with a special "id" that would be ignored by the plugin (I am not sure this is possible)
And for now, I guess I would have to make sure I always have a single doc with all slices used and ignore that in my queries. (the special id approach - but with a UID).

Sorry, but with an introspection API GQL is not very compatible with Prismic API I guess..

Hey @yoadsn, thanks for the detailed explanation. I agree with everything said.
Slice type unavailable
Right now, Gatsby will only know slice types that are available in the data it fetches. As you found, this means Gatsby will not know about slice types that are not present in at least one document of its type. The only easy solution right now is to save a document with every slice present, as you suggest.
This is a common Gatsby issue, as seen here: Trying out Gatsby at Work & Co:

GraphQL requires all queried fields to be defined in a schema, and Gatsby generates this schema from your site’s existing data. This means, for example, that if you don’t have a Carousel content model on your site right now, but you have a GraphQL query checking for it, the site will fail to build.
The are some really promising discussions on the topic on Github, including an RFC to refactor Gatsby’s schema generation, but in the meantime, most users are getting around this issue by creating placeholder content on Contentful (or whatever their data source is) to guarantee a fully built-up schema.
This got the job done in our case, and we augmented the approach by creating a DummyContentIndex model on Contentful linking to all placeholder content. (In retrospect, I wish I had picked the a more PC name, like ‘PlaceholderContentIndex` 😉.) Using this approach, we could inform our Contentful scripts to make sure placeholder content was copied to the production environment during deploys, so that new models would not break the build.

Specifically for Prismic, you could tag the document with something like "Infrastructure" and mask it out in the Prismic UI.
Ideally, we could query Prismic for the schema of the content type and generate a GraphQL schema to inform Gatsby of the content model. As you mentioned, I don't think Prismic has an API for this, but we should look into that.
Luckily the schema is accessibly in the Prismic UI, so at the very least, a user could copy and paste it into a file for gatsby-source-prismic to parse.
I have had problems in the past generating the GraphQL schema for Gatsby using the setFieldsOnGraphQLNodeType export, but it's something we should definitely figure out. I know others are running into issues with fields being empty and causing Gatsby's GraphQL interface to blow up.
The fact that Prismic does not allow setting a field as required exacerbates the issue.
Slice field not a union type
This is a good catch and is obviously pretty annoying. 😄 This related to above where proving an explicit GraphQL schema to Gatsby would help. For now, I think we could limit the schema extension to just tell Gatsby that any slice field should be a union type of its slices, even if there is only one type.

Until we figure out the schema extensions, I think it's a good idea to mention the "placeholder document" requirement in the README since this is a common issue.

Awesome - I really appreciate your detailed response.
I am going with the placeholder approach. When we finish this integration, if it looks polished enough I might PR this into the readme with a small example. :)

Agree with @angeloashmore that this limitation should be mentioned in the README. Makes sense once you think about it, but just tripped me up in prod.

where's the full schema located in prismic?

Hi @chaoky, you can find the schema in Prismic under Custom Types. Click on the custom type you need and then select JSON on the far right of the page.

@camel113 We ended up not going for the Gatsby implementation - sorry - but I have nothing to contribute on this. Next project maybe 🤷♂

Closing this out as v3 has been in open beta for a while now and solves this issue. Please give it a try if you haven't yet!


Send logs to backend.

Requires changes to website which are in a separate pull request.
UI sends a "include logs" bit to the Core and Core sends logs to backend if appropriate.
Ran grunt test and tested manually.

Small thing about refactoring, otherwise :+1:


 Your question is much more
likely to be answered if it is
a good question

Description
Questions can often be answered by our documentation. Unable to find an answer
in our docs? We'll try to help. In the meantime, if you answer your own
question, please respond with the answer here so that others may benefit as
well. Better yet, open a PR to expand our docs ^_^

Hi @Hariprasathkin
Below is a working OHIF configuration file. You can filter the study list by setting the number of days. Note that the length of results of the study list are also controlled by the underlying PACS, e.g. Orthanc uses "LimitFindResults" and "LimitFindInstances".
{
"apps" : [{
"name"        : "ohif-viewer",
"script"      : "main.js",
"watch"       : true,
"merge_logs"  : true,
"cwd"         : "/app/bundle/",
"env": {
"METEOR_SETTINGS": {
"servers": {
"dicomWeb": [
{
"name": "Orthanc",
"wadoUriRoot": "http://orthanc:8042/wado",
"qidoRoot": "http://orthanc:8042/dicom-web",
"wadoRoot": "http://orthanc:8042/dicom-web",
"qidoSupportsIncludeField": false,
"imageRendering": "wadouri",
"thumbnailRendering": "wadouri",
"requestOptions": {
"auth": "demo:demo",
"logRequests": true,
"logResponses": false,
"logTiming": true
}
}
]
},
"defaultServiceType": "dicomWeb",
"public": {
"ui": {
"studyListDateFilterNumDays": 7000
}
},
"proxy": {
"enabled": true
}
}
}
}]
}

We have stackPrefetch on by defualt which would do the trick for you.
Please review the latest code in the master branch. This issue might have been resolved. If it persists, kindly reopen the issue with updated details.
Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing


Remove all let declarations

It's not functional. Let's replace all of the let statements to the const.

Thanks for your special help, @Funniest and @ltnscp9028


test(linter): add regression tests for import/namespace

Related to #7696

I didn't add tests because this is just testing the behavior of the resolver, which is already covered by the resolver itself.


Stable Release for PX4 v1.11.3-stable

Is there a specific stable version for PX4 v1.11.3?

No, but it should work with v1.11.3. Do you have a specific problem?

Not actually. But after "multiple ekf" I lost the strings :) I flashed pixhawk with v1.11.3.

I'm a bit confused. You are asking here in MAVSDK-Python about the PX4 version you flash on your Pixhawk?
So is this a question about MAVSDK-Python and PX4, or is it solely about PX4 and that's the wrong place to ask? :see_no_evil:

Fair question. Generally MAVSDK should be backwards compatible as it's based on the MAVLink API. In this case, I would recommend PX4 v1.13.x (or main/v1.14) and latest v1.x.y MAVSDK-Python.


Please invite me to the GitHub Community Organization

Name
Irfan Asif
Discord Username (if applicable)
Irfan Asif
Additional Context
I saw Eddie on youtube, his videos were informative as I want to start with open source and I want to join this community.

Welcome to the EddieHub community, @demonicirfan! We're glad to have you here! 🙂👋


Android build fails for 5.2.0 with RN 0.68.2

Current behavior
Describe what happens when you encounter this issue.
Android build fails with newer react native.
Following error occurs
Could not determine the dependencies of task ':react-native-video:compileReleaseAidl'.

Could not resolve all task dependencies for configuration ':react-native-video:releaseCompileClasspath'.
Could not find com.google.android.exoplayer:exoplayer:2.13.2.
Required by:
project :react-native-video
Could not find com.google.android.exoplayer:extension-okhttp:2.13.2.
Required by:
project :react-native-video

Reproduction steps
A 1, 2, 3, etc. list of what's needed to see the issue happen.
Using react-native 0.68.2
run yarn add react-native-video (5.2.0)
run npx react-native run-android
Expected behavior
Describe what you wanted to happen
Build succeeds
Platform
Which player are you experiencing the problem on:

Android

Video sample
If possible, include a link to the video that has the problem that can be streamed or downloaded from.
Not appliccable
Solution
Update shaka-player to 3.2.1
update com.google.android.exoplayer:exoplayer to 2.13.3
update com.google.android.exoplayer:extension-okhttp to 2.13.3

I know version 6 is on its way, which will likely make this issue obsolete, but I thought i would suggest this change, as it would be nice to continue using react-native-video also before version 6 is official.
Let me know if this is wanted and i will make a PR fixing the issue

Update shaka-player to 3.2.1
update com.google.android.exoplayer:exoplayer to 2.13.3
update com.google.android.exoplayer:extension-okhttp to 2.13.3

I'm not overly familiar with node/yarn (or react-native, for that matter), how can I apply this solution?

What I ended up doing was create a patch that yarn can apply automatically, so I would not need to manually edit these files every time I run yarn.
I suggest following this guide: https://dev.to/ajmal_hasan/make-changes-to-nodemodules-files-with-patch-package-updated-52af
TL;DR: install patch-package and postinstall, manually edit node_modules/react-native-video/package.json and node_modules/react-native-video/android-exoplayer/build.gradle with the changes mentioned above, create patch.

I just backported some known fixes on this branch: https://github.com/react-native-video/react-native-video/pull/2795/files
Can you have a quick test with it please ?

release 5.2.1 has been published, let's close this issue


Incorrectly ignores 0 as a value

To reproduce:
testSelector('foo', 0);

The expected value is [data-test-foo="0"]. The actual value is [data-test-foo].
Workaround: convert to a string:
testSelector('foo', `${0}`);

I ran into this because I have a small helper that wraps this and passes in an ID, so:
mySelector = id => testSelector('foo', id);

This works normally, unless the id is 0.

Thanks for reporting - should be pretty easy to fix if you (or anyone) wants to submit a PR.


same input, the quality on huggingface is better than colab, why, ......

as title

There should be no difference in settings, maybe you can try training again or fix the random seed.

ok, thanks.


Add more flex property classes, such as flex-grow-2

From https://github.com/tailwindcss/tailwindcss/issues/603:

We didn't provide flex-basis utilities originally because width does the same thing for 99.9% of cases and we didn't want to increase the size of the framework, but you could easily add your own flex-basis utilities by following the documentation:

https://stackoverflow.com/a/34734145/893907 provides a good explanation of why width classes wouldn't satisfy all the flex-grow, flex-basis, etc. classes.
https://tailwindcss.com/docs/flex-grow/ has .flex-grow and .flex-grow-0 but why not more?
Basically, I want to do this via Tailwind classes:

Adding even a hundred more classes isn't going to significantly increase the size of the library, and with the great build tools like include/exclude/PurgeCSS, there's no major risk in my opinion.
Thanks for Tailwind!

Width and flex-basis are definitely interchangeable except for very rare situations (specifically involving CSS grid and flexbox where you are trying to progressively enhance flexbox to CSS grid). The StackOverflow question you linked is comparing width to flex-grow not flex-basis.
You can add flex-grow-2 if you like by adding it to your config file 👍 Then you'd do this to accomplish what's in that screenshot:

...

https://tailwindcss.com/docs/flex-grow/#grow-values


Move sample of service usage to separate repo

Currently mixing service code, and sample data may lead to confusion, it's better to create separate repo that will be focused on how to use the service. latter we'll add link to that repo into documentation

repo for example https://github.com/ksysoev/deriv-api-bff-example


Need to click twice

Hello,
I would like to test i18n on my angular website. There is a French link and an English link in the footer:

      {{'BUTTON_LANG_EN' | translate }}

      {{'BUTTON_LANG_FR' | translate }}

Here is my protractor test:
it('test', function() {
    expect(usernameLabel.getText()).toBe('Username');
	var frenchButton = element(by.id("BUTTON_LANG_FR" ));
// here I can't understand why 2 clicks are needed
	frenchButton.click();
    frenchButton.click();
    browser.wait(function() {
      return frenchButton.getText().then(function(text) {
        return text === 'Français';
      });
    }, 1000);

    expect(usernameLabel.getText()).toBe('Identifiant');
});

This test is ok, but if I comment one of the 2 frenchButton.click();, the test fails (timeout in browser wait, nothing translated).
I tried to change the template to:

      {{'BUTTON_LANG_EN' | translate }}

      {{'BUTTON_LANG_FR' | translate }}

but this is the same result as the code above.
I also tried browser.wait(EC.elementToBeClickable(frenchButton), 5000); but it doesn't work better
The browser is FF 39.0. When I manually click on the frenchButton, a single click is needed to translate the page. I also tried to pause protractor and manually click on the frenchButton, the page is translated after the 1st click.
My buttons are on the bottom of page, so their coordinates can change during the translation because the content height changes. I tried with browser.waitForAngular() but the test still fails.
How can I check if the click event is emitted by the 1st click?
Thank you for your answer.

Have you tried using browser.pause() to debug your problem?

Sometimes it helps to try and use browser.actions().mouseDown(frenchButton).mouseUp().perform();.
This happens to me sometimes in dropdowns in firefox. Might be worth a shot.

Thanks for your replies.
@sjelin yes I tried. I added browser.pause() before and after clicking: 2 clicks are needed by protractor. If I click manually during the pause, only 1 click is needed
@Droogans I tried browser.actions().mouseDown(frenchButton).mouseUp().perform(); but it is not better, protractor needs these actions twice.
I also tried browser.actions().mouseMove(frenchButton).click().perform();, without success.

I can confirm that I also had similar issue which was solved by double clicking.

I'm trying to update protractor to 3.0.0, because webdriver used by 2.x.x does not support Firefox 43 anymore.
It looks like something has changed in webdriver 2.48.2, because I have similar issues as mentioned above. In some cases I need to click twice. Sometimes when I call element.click() Firefox tries to scroll to this element, but e.g. because of parallax that messes up scroll height, fails, the element is outside of viewport and element.click() does nothing - there's no error, but the element is not clicked. Things like element.getText() work correctly though. I fixed it by adding a helper that scrolls to the element using element.scrollIntoView() and call it before clicking anything. The way Firefox finds elements by itself (unlike e.g. Chrome) was the main reason for me to use it in e2e tests...
I'm not sure if these 2 issues are related, e.g. if the second click scrolls the page so that the element is in the viewport and the click actually works.

Yea I have been trying to do the click twice using protractor and it hasnt been working out. I did Droogan's suggestion and I tried browser.pause() too. The browser I am using is chrome for a testing a non-angular single page application

I too have similar problem on chrome 50 with protractor 3, selenium 2.52 and chrome driver 2.21.
Solved with workaround by clicking twice on element.

I too have similar problem on chrome 50 with protractor 3, selenium 2.52 and chrome driver 2.21.
Solved with workaround by clicking twice on element.

I'm closing this issue as stale - there's a couple bugs listed that I think aren't actually the same thing, and no way for us to reproduce them. If you are still having an issue that you can show us in a reproducible example, please open up a new issue. Thanks!

@mariemignot44 , I am facing the same "Twice click" issue. Did you find any workaround other than clicking twice?


[Doc] Fix incomplete sub-links on download page

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
https://pulsar.apache.org/download/ includes many releases but only some sub-links, including:

https://pulsar.apache.org/download/#release-notes
https://pulsar.apache.org/download/#current-version-

https://pulsar.apache.org/download/#shell
https://pulsar.apache.org/download/#offloaders
https://pulsar.apache.org/download/#connectors

https://pulsar.apache.org/download/#release-integrity
https://pulsar.apache.org/download/#older-releases

However, there are no sub-links to

Pulsar C++ Client
Pulsar Manager
Pulsar Adapters

There are links to the release note, current version and old releases of Pulsar Manager and Pulsar Adapters.
Pulsar Manager:

https://pulsar.apache.org/download/#release-notes-1
https://pulsar.apache.org/download/#current-version--1
https://pulsar.apache.org/download/#older-releases-1

Pulsar Adapters:

https://pulsar.apache.org/download/#current-version--2
https://pulsar.apache.org/download/#older-releases-2

What is your suggestion?
A better design is to add the direct links to these. e.g.

https://pulsar.apache.org/download/#cpp-client
https://pulsar.apache.org/download/#pulsar-manager
https://pulsar.apache.org/download/#pulsar-adapters

Any reference?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@tisonkun Could you take a look?


Fixes #4544 -- error when attempting to zoom to invalid dates

Might also fix #4425.

@mramato I've added validity checks now before our calls to zoomTo, and zoomTo will throw when called with invalid time arguments. That's what you meant, right?
I also added a static function on JulianDate for this kind of validity check, since it's something that needs to be done in a few different places. Not entirely sure what to do if Viewer.js has clock values outside the Iso8601 range and wants to update the timeline, but do we need to take such a case into consideration?
Thanks @mramato!

After stumbling upon a browser support discussion in another PR I realized I shouldn't use Array.prototype.every since it seems to not be available in IE 8.
Ready for review.

@mramato Could you review this?

While looking over the code I realized that some assumptions I had regarding the root cause of this issue may have been wrong.  I need to investigate some more and convince myself this is still the right approach.  I'll keep you posted.  Thanks.

I just opened #4595, sorry for the confusion here.


Warns user that heater is unplugged if switch is not consuming power

Depends on the correct SmartThings device type.  If a switch is on, but there is not power being drawn through the smart outlet, show a warning to the user so they know that the heater probably isn't plugged in.

Depends on jonscheiding/st-power-control#7


[Serializable] attribute does not show up in contracts

[Serializable] class SomeException : Exception { }

PublicApiGenerator won't reproduce the [Serializable] attribute in the generated API string—assuming default PublicApiGeneratorOptions which don't exclude it.
This is likely due to SerializableAttribute being a "pseudo" custom attribute that gets transformed to a TypeAttributes flag in the IL metadata. Unlike System.Reflection, Mono Cecil is more faithful to the actual metadata and won't report it as a custom attribute when querying type.CustomAttributes here.

Hmm... That means the changes introduced in https://github.com/PublicApiGenerator/PublicApiGenerator/issues/117 especially in https://github.com/PublicApiGenerator/PublicApiGenerator/pull/121 are not really working for SerializableAttributes
@stakx would you be able to send in a reproduction test and potentially give a stab a fixing it?

@danielmarbach — will do. I'll likely continue working on the PR I just submitted later today.

10.1.1 is up on Nuget

Awesome @danielmarbach — thanks, once again, for the super quick response time!


Unable to access https://secure.gaug.es

This isn't such a big deal because I can access it just fine on my phone, but I'd like to be able to access it on my computer. No idea what it's using that's being blocked. There's no mention of gaug.es in this repo so it must be a third-party script.
Oh well.

 That's weird as hell, maybe GitHub can't handle it? Anyhoo, I am using Gauges for my site analytics.

Yeah you can't use the search repository function for the hosts files, they are too large and don't get indexed fully.
Next time view raw and search with your browser :)


关于训练数据中的文件 transform.json的来源

Using your own data, after processing with colmap, error is reported during training because there is no transform.json file. How is this file generated?

Are you using ns-process-data? Or just colmap alone?

The colmap approach alone is more helpful to me. It also tells me that ns-process-data is better

Support for using just colmap was added a week ago so you will need the latest version on github - https://github.com/nerfstudio-project/nerfstudio/pull/2115
And add colmap to the end of you training command so that it doesn't using the nerfstudio-data dataparser.

ok ,So I git the latest nerfstudio code using colmap-dataparser.py for my current needs? I want to use my own data to generate nerfstudio training data, including transforms.json files

colmap_dataparser.py   How should I use this file?


SOLR-16621: Admin UI fails to grant user permissions with wildcard role

https://issues.apache.org/jira/browse/SOLR-16621
Always grant access to a permission that has has the wildcard "*" role, no matter what roles user has.
Note, this is not the same as not requiring authentication for the permission, "roles": null. It means that the permission needs an authenticated user, but any role will do.
Also, this is just UI stuff so will not modify actual permissions on the API level, but will align role checking logic so it matches that of the backend.
To test:

Start Solr and enable security./gradlew dev
cd solr/packaging/build/dev/
bin/solr start -c
bin/solr auth enable -credentials solr:solr -blockUnknown true

Log in to Admin UI with 'solr' and 'solr': http://localhost:8983/solr/#/~security
Edit the permissions 'security-edit' and 'security-read' to have * as role
The user can still see the Security Dashboard and edit permissions

(To confirm the bug, do the same test on main branch and see that user is blocked from security dashboard once the permissions are changed to role=*).

@thelabdude I see some duplicate logic in the permission check for Security Dash. I believe you could have used the function isPermitted() already defined in app.js, see https://github.com/apache/solr/blob/main/solr/webapp/web/js/angular/app.js#L528-L533 ?


Reboot loop

It's looping on reboots.
I believe it has to do with the number of elements in my Wi-Fi.
I tried to put all the mac in the "KNOWN_MACS" as an env. variable but same...
when I remove the telegram config it's not rebooting so I guess it's this... how do I fix it?
Thanks
An error occurred while sending the notification: Client error: POST https://api.telegram.org/botxxxxxxxx:xxxxxxx/sendMessage resulted in a 429 Too Many Requests response:
ok=false error_code=429 description=Too Many Requests: retry after 26 parameters={"retry_after":26}

@Lugib it looks like the Telegram API is getting too many requests at once and needs to be rate limited. I updated the Notifier.php and added a backoff on 429 error. Can you try again?

Closing this out, please open a new issue if you're still facing issues with the new release


SSL support for Kafka message bus

We have to provide SSL support for Kafka message bus, I believe it's nearly a requirement for production systems. However adding 2 additional Kafka params means enormous amount of "boilerplate" code if relying on current logic (the params should be added as attributes almost to each class in kafkabus module, it becomes clumsy). I'm proposing 2 things related with the SSL changes to relieve it:

a small helper function to format SSLkwargs
a named tuple to store Kafka parameters common for all needs (location, codec, ssl-related settings)

The only downside is that it breaks backward-compatibility in a case if someone relies on Kafka consumer/producer classes defined in the module, but it should be OK as it's not a part of frontera public API.
Tests are missing yet, but the changes are ready for initial review, please let me know if you disagree on start (and we revise the approach), or think it's appropriate changes and I'll continue with it.

merged in #299


How to serve static files from ./public dir to the root path?

I tried the following, but it didn't work
  router.ServeFiles("/*filepath", http.Dir("public/"))
// or
  http.Handle("/", http.FileServer(http.Dir("public/")))

[using the NotFound handler to serve files] is not a good idea in my opinion

Why not?  I need the ability to server index.html and favicon files from my root, and I'm looking for the best way to accomplish this.

I agree with daveroberts ... ALL root folders on web sites that I develop for my customers contain 1 file (index.html) and various subfolders (eg /static, /api)
Using Juliens  great router component, I can serve a file from any and all subfolders ... however I cannot serve index.html with it.
Advice anyone please ??

The way I solved index problem was to serve index .html like this:
`
func Index(w http.ResponseWriter, r *http.Request, _ httprouter.Params) {
http.ServeFile(w, r, r.URL.Path[1:])
}
func main() {
router := httprouter.New()
router.GET("/", Index)
router.ServeFiles("/app/*filepath", http.Dir("static"))
....
log.Fatal(http.ListenAndServe(":8080", router))
}
`

This forces all of your static files to be accessible under /static.  This may work for some projects, but not all.  A couple of examples which come to mind:

The default path for a favicon is in the root directory.  If a user requests a non-HTML page, the favicon won't load
People may already be linking to files on your site and you can't change the links

What is the best way to wrap the router.ServeFiles in a middleware in case I want to protect some assets?

This is what finally worked for me:
func main() {
	router := httprouter.New()
	router.GET("/", LandingPage)
	router.GET("/Create", Create)
	router.ServeFiles("/static/*filepath",http.Dir("static"))
	logger.LogInfo("Server running at http://<IP_ADDRESS>:3001")
	log.Fatal(http.ListenAndServe(":3001", router))
}

@julienschmidt
I keep running into this issue again and again when trying to convert an existing php/python/vb6/etc. website to go. I love your router but It is not usable for all these websites because the static files never are to be served in a separate path. I would like them to have a separate path but it just isn't actionable to change that for these large projects.

Solved it with 2 separate routers and the NotFound handler. That way I can check for specific routes first and if none of them match serve static files.
	router := httprouter.New()
	router.GET("/", s.index())
	router.GET("/api/", s.api())

	// if not found look for a static file
	static := httprouter.New()
	static.ServeFiles("/*filepath", http.Dir(staticPath))
	router.NotFound = static

Solved it without creating a new router while serving all static files under /
router.NotFound = http.FileServer(http.Dir(staticPath)).ServeHTTP


Automate version updates in MVG

Minimum is to have a check list

Move MVG version info to a separate file. Add a condition in ci-checks workflow so that PR tests fail if that file is not modified.
A release using the version in that file can also be automatically initiated.

Maybe using https://github.com/marketplace/actions/file-changes-action helps to detect changes in the file containing version information


Unique components dde ode

i discovered the following issue: When edge coupling type is not specified (e.g. in getting_started.jl), edges will be reconstructed. As a consequence collect_unique_components can not determine uniqueness anymore? Why? For large networks it then takes ages to finish.

Hans did this basemark against 0.5.4, hence everything seems to works as expected
Job Properties

Time of benchmarks:

Target: 27 Sep 2021 - 19:14
Baseline: 27 Sep 2021 - 19:18

Package commits:

Target: 96d824
Baseline: 1df9bf

Julia commits:

Target: 1b93d5
Baseline: 1b93d5

Julia command flags:

Target: -J/Applications/Julia-1.6.app/Contents/Resources/julia/lib/julia/sys.dylib
Baseline: -J/Applications/Julia-1.6.app/Contents/Resources/julia/lib/julia/sys.dylib

Environment variables:

Target: JULIA_NUM_THREADS => 4
Baseline: JULIA_NUM_THREADS => 4

Results
A ratio greater than 1.0 denotes a possible regression (marked with :x:), while a ratio less
than 1.0 denotes a possible improvement (marked with :white_check_mark:). Only significant results - results
that indicate possible regressions or improvements - are shown below (thus, an empty table means that all
benchmark results remained invariant between builds).


Use HTML tag blacklist instead of no raw html for Goldmark

I understand the need for not allowing arbitrary HTML in Markdown content for security, but Markdown is quite limiting in certain aspects. For example, I resort to using <sub> and <sup> for subscript and superscript because it seems that these can't be unambiguously parsed by CommonMark in order to be included in the specs. I also commonly see the <details> tag being used to hide verbose information in some READMEs. I'm quite sure there's more of these cases.
GitHub allows raw HTML in repository READMEs and I would imagine they have the same security concerns as well. It seems that they have thought about this and opted to use a blacklist of HTML tags instead: https://github.github.com/gfm/#disallowed-raw-html-extension-. From the link, the blacklisted tags are:
<title>
<textarea>
<style>
<xmp>
<iframe>
<noembed>
<noframes>
<script>
<plaintext>

Would this be a good compromise for security, but still allow flexibility in Markdown content?

Would this be a good compromise for security,

Not really. That said, I have some plans (and an issue) to add Bluemonday (a Go HTML sanitizer), which would be an excellent option.

Awesome. Integrating a proper sanitizer is definitely better than a blacklist.

For others browsing, #6530 🙂


Double input showing

Getting a weird  UI issue attached screenshot

My code is pretty simple and based off the example
 {{> afQuickField name="producers" type="select2"}}

producers: {
        type: [String],
        label: "Producers",
        optional: true,
        autoform: {
            type: "select2",
            options: function () {
                var user = Meteor.user();
                return Producers.find({organizationId: user.organizationId}).map(function (obj) {
                    return {label: obj.name, value: obj.name};
                });
            }
        }
    },

You're using the shortcut type: [String] so it doesn't know whether you want the autoform stuff on the array or the array item. Try separating into producers and 'producers.$'.

@aldeed thanks I should have closed this. I ended up having to build a custom form Autoform is great but my needs are very specific and custom which autoform can't do. I think it's good for the more general forms.


Enable underflow fix after specified date

@miguelportilla @scottschurr

Current coverage is 62.00%

Merging #1519 into develop will increase coverage by +0.01% as of 154f4d7

@@            develop   #1519   diff @@
=======================================
  Files           888     888
  Stmts         62871   62871
  Branches          0       0
  Methods           0       0
=======================================
+ Hit           38979   38981     +2
  Partial           0       0
+ Missed        23892   23890     -2

Review entire Coverage Diff as of 154f4d7

Powered by Codecov. Updated on successful CI builds.

:+1: Thanks, Scott!

@seelabs very kindly talked me through the consequences of the change.  We're both convinced it's the right thing.  :+1:

Merged as 278f679bb1355171919df556b8b7614847cc056c


hunting arachnomantis stalker on ka'zaal texture

hunting arachnomantis stalker on ka'zaal has incorrect texture. It doesn't match the uv map

Details
hunting arachnomantis stalker on ka'zaal has incorrect texture. It doesn't match the uv map
Game Version
<IP_ADDRESS>
New Game
Yes
Reproduction Steps
Go to ka'zaal. find hunting arachnomantis stalker

https://i.imgur.com/INiWWM3.png
https://i.imgur.com/aQSgso4.png
https://i.imgur.com/uwZGwSF.png
screenshots of the broken texture


Add FIPS (BoringCrypto) support

Feature Description
In pursuit of FedRamp authorization, there's a customer need to ensure that all cryptographic modules in use within their GCP environment are FIPS validated. BoringCrypto is one such module that could be used by CloudSQL Auth proxy to meet this requirement.
Sample code
// sample code here

Alternatives Considered
No response
Additional Details
No response

We're going to hold off on this since boringcrypto doesn't currently support TLS 1.3.


/ep free teleports freed player to pearl holder.

This defeats the point of preventing /ep summon since it lets you teleport players directly out of the nether while keeping their inventory.
Freeing someone should unpearl but not teleport.

This is fixed.


New author file created

Description
[Added new author file for Yi Lin Yang]
Issues Resolved
[]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@YiLin1818 please check Josh's comments and update, thank you!

I've made the appropriate changes in the pull request: Chore/add-author-YiLin1818. The final commit should be: @YiLin1818
Made changes to author file OSCI

Closing as finished in #2217


deps: update all sorts of stuff

This pr goes through and makes the various updates:

Bumps mill to the latest 0.10.5
Bumps to the latest Scala versions for 2 and latest 3.1.x version
Drops 0.x support for ScalaJS
Move Scala native to 0.4.x
Adds in dependabot
Starts to cross test on 8 and 17
Updates checkout and java actions

So there is still one thing I'm trying to figure out with this. The Mima tests pass for 2.13.6, but once I bump past that the 2.13 ScalaJS check fails with
Found 2 issue when checking against com.lihaoyi:pprint_sjs1_2.13:0.7.3
 * static method apply(scala.collection.Iterable)java.lang.String in class pprint.StringPrefix has a different generic signature in current version, where it is (Lscala/collection/Iterable<Ljava/lang/Object;>;)Ljava/lang/String; rather than (Lscala/collection/Iterable<*>;)Ljava/lang/String;. See https://github.com/lightbend/mima#incompatiblesignatureproblem
   filter with: ProblemFilter.exclude[IncompatibleSignatureProblem]("pprint.StringPrefix.apply")
 * method apply(scala.collection.Iterable)java.lang.String in object pprint.StringPrefix has a different generic signature in current version, where it is (Lscala/collection/Iterable<Ljava/lang/Object;>;)Ljava/lang/String; rather than (Lscala/collection/Iterable<*>;)Ljava/lang/String;. See https://github.com/lightbend/mima#incompatiblesignatureproblem
   filter with: ProblemFilter.exclude[IncompatibleSignatureProblem]("pprint.StringPrefix.apply")
1 targets failed
pprint.js[2.13.7,1.10.1].mimaReportBinaryIssues Failed binary compatibility check! Found 2 potential problems

So trying to figure this out.

Thank you for this @ckipp01!
About the MiMa issue, I released a new version of mill-mima which has the same behaviour as the Sbt plugin, so if you update you should be able to remove the configuration you added:
  // By default in sbt-mima IncompatibleSignatureProblem is actually turned off
  // by default due to false positives. We hit on this with 2.13 > 2.13.6 with
  // * static method apply(scala.collection.Iterable)java.lang.String in class pprint.StringPrefix has a different generic signature in current version, where it is (Lscala/collection/Iterable<Ljava/lang/Object;>;)Ljava/lang/String; rather than (Lscala/collection/Iterable<*>;)Ljava/lang/String;. See https://github.com/lightbend/mima#incompatiblesignatureproblem
  def mimaBinaryIssueFilters = if (crossScalaVersion.startsWith("2.13"))  {
    super.mimaBinaryIssueFilters() ++ Seq(
      ProblemFilter.exclude[IncompatibleSignatureProblem]("pprint.StringPrefix.apply")
    )
  } else {
    super.mimaBinaryIssueFilters()
  }

Also, I released fansi 0.4.0 with your updates.

Sounds good. I updated this and to the new mill-mima.

Sorry, forgot to mention sourcecode 0.3.0 which was released with your changes.


use install@version command to install golangci-lint without adding deps to module

golangci-lint hasn't been working for me locally because of long story short go1.18 requires a newer version of golangci-lint than had been installed by go-common.mk in the past.
The fix was to delete my local install of golangci-lint and install the latest version, but using go get adds all the dependencies to go.mod but in go1.16 they added this install@version command  which is now the way to install packages without modifying the module.
Ideally there would be some way to keep the version of golangci-lint up to date on our computers but that seems a larger task.

In terms of keeping things up to date, we can certainly figure out the currently installed version by running golangci-lint version.  The latest release should be able to be determined with something like gh -R github.com/golangci/golangci-lint release list -L 1.  We could compare those and update if they differed?  It is not quite that straightforward since neither command outputs just the version, but both contain the version and we can extract them and compare.

I would suggest that instead of trying to keep the version up to date on our local machines, we avoid installing/using a hand-installed copy at all, and lean further into making golangci-lint part of the module deps, like we've done with mockery and counterfeiter.
This would involve creating a tools.go file like this one, but referencing the import path of the golangci-lint cmd package. Then, we'd update the makefile to invoke it as
go run github.com/golangci/golangci-lint/cmd/golangci-lint

instead of calling it by name. I haven't tried it, but I think this approach would allow dependenabot to update golangci-lint just like any other version, and it would allow us to pin a version in the commit and make sure that a commit that passes lints locally will be more likely to pass lints in CI if we need to redeploy in a month or two, after new linter versions have been replaced.
The one downside is that it would mean coupling the makefile to our modules. common-make would be dependent on the module actually having included golangci-lint in its deps, and would fail lints if the module doesn't include it.

I would suggest that instead of trying to keep the version up to date on our local machines, we avoid installing/using a hand-installed copy at all, and lean further into making golangci-lint part of the module deps, like we've done with mockery and counterfeiter.
This would involve creating a tools.go file like this one, but referencing the import path of the golangci-lint cmd package. Then, we'd update the makefile to invoke it as
go run github.com/golangci/golangci-lint/cmd/golangci-lint

instead of calling it by name. I haven't tried it, but I think this approach would allow dependenabot to update golangci-lint just like any other version, and it would allow us to pin a version in the commit and make sure that a commit that passes lints locally will be more likely to pass lints in CI if we need to redeploy in a month or two, after new linter versions have been replaced.
The one downside is that it would mean coupling the makefile to our modules. common-make would be dependent on the module actually having included golangci-lint in its deps, and would fail lints if the module doesn't include it.

This sounds like a good idea.  The make recipe could also check if golangci-lint was a current dependency and error if not (with some instructions on how to set it up)

I like the idea of making it a dep and don't think there is necessarily a problem in lints failing if the project doesn't use lint. Could be good to enforce and I think one would still have to run it / add it circle-ci for it to run.
It does beg the question of whether linting makes sense as a "make" command, as it doesn't really make anything. We've got a handful of different answers to how to run things: running through make, running through gulp, npm, running through scripts, loading data from AWS for each run, .envrc files, and maybe more? Linting would work similarly to running and maybe it is about time to decide on our approach?

Hmm regarding how best to invoke it, once it's part of the module, just running it by go run would work, although it is a little verbose since you need to include the full import path every time. So maybe we don't need a make recipe or a script, and we can just run it directly in circle or on the command line? Or is it worth the convenience of an abbreviation?

I like the idea of making it a dep and don't think there is necessarily a problem in lints failing if the project doesn't use lint. Could be good to enforce and I think one would still have to run it / add it circle-ci for it to run.
It does beg the question of whether linting makes sense as a "make" command, as it doesn't really make anything. We've got a handful of different answers to how to run things: running through make, running through gulp, npm, running through scripts, loading data from AWS for each run, .envrc files, and maybe more? Linting would work similarly to running and maybe it is about time to decide on our approach?

Each language has its own peculiarities, so I don't think that we can or should try to settle on a single approach that covers Go, Java and TypeScript/Angular.
For Go, make works pretty well for the build process overall from my perspective.  It's a language that compiles directly into an executable, which is the type of language that make was designed for.  I think it's easy to look at the lint target and see something that doesn't fit into a make recipe with the same purity.  That said, the convenience of using the same tool for all of the Go build and test processes saves cognitive space and I don't think we should discount that in the pursuit of purity.
What we use for other languages and how we run things is probably a broader topic that deserves its own setting.


Fix port issues when deploying two servers

Changes

Check port and append to local server domain
Fix Follow tests

Screenshots
CURRENT_PORT: 8000

CURRENT_PORT: 8080

fun!


Change "Day 1", "Day 2" etc. to actual dates

Currently the app shows the days of the event as "Day 1", "Day 2" etc. Please show the actual dates similar to the web app.

This can be fixed by changing the tab names in the viewpageAdapter, shouldn't be too hard.
@arp95 assigning this to you.

@the-dagger
sure.
started working on it.

@the-dagger
sent the pr.
please review!


[Doc] Add an image for the authentication with Github to travelocity.com application

We need to add images to the last step of 'Testing the sample' section in [1] for login to travelocity with Github as the step for authentication and after the authentication to give a complete picture of the scenario.
[1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+Github+Authenticator#ConfiguringGithubAuthenticator-TestingthesampleTestingthesample

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Kite deletion causing spyder crash maybe!?

Issue Report Checklist

[ O] Searched the issues page for similar reports
[ O] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ X] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ X] Could not reproduce inside jupyter qtconsole (if console-related)
[ O] Tried basic troubleshooting (if a bug/error)

[O ] Restarted Spyder
[ O] Reset preferences with spyder --reset
[ O] Reinstalled the latest version of Anaconda
[ O] Tried the other applicable steps from the Troubleshooting Guide

[ O] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I recently installed Anaconda and Spyder with it installed Kite. Wanted to look about.
Didnt much like Kite so wanted to uninstall on my mac but kept saying its being used even though Anaconda or any other products were closed.
Hence i had to remove it and its components from terminal.
Since then I am getting 2 types of error
What steps reproduce the problem?

when tried to open spyder it says 'Traceback Error
as given below

Every few minutes on my mac started getting a pop up For security reasons, you need to code sign your application or sign your updates with a EdDSA key.

What is the expected output? What do you see instead?
I have reset via terminal
reinstalled Full Anaconda 3 times
Installed Kite seperately and failed to close as it was "being open"
Somehow managed to remove kite from application
But still cant open Spyder
Paste Traceback/Error Below (if applicable)
Traceback (most recent call last):
File "/opt/anaconda3/lib/python3.7/site-packages/spyder/app/mainwindow.py", line 3718, in main
mainwindow = run_spyder(app, options, args)
File "/opt/anaconda3/lib/python3.7/site-packages/spyder/app/mainwindow.py", line 3557, in run_spyder
main = MainWindow(options)
File "/opt/anaconda3/lib/python3.7/site-packages/spyder/app/mainwindow.py", line 423, in __init__
from spyder.preferences.appearance import AppearanceConfigPage
File "/opt/anaconda3/lib/python3.7/site-packages/spyder/preferences/appearance.py", line 20, in
from spyder.plugins.editor.widgets.codeeditor import CodeEditor
File "/opt/anaconda3/lib/python3.7/site-packages/spyder/plugins/editor/widgets/codeeditor.py", line 61, in
from spyder.plugins.completion.kite.widgets.calltoaction import (
ModuleNotFoundError: No module named 'spyder.plugins.completion.kite

PASTE TRACEBACK HERE

Versions
1.9.12

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

Hence i had to remove it and its components from terminal.

I don't know what you did here, but the error above shows an incomplete Spyder installation, i.e. a file is missing from our source code.
To solve it, please remove Anaconda again, then remove this directory /opt/anaconda3 entirely, then reinstall it again. That should solve your problem.

Every few minutes on my mac started getting a pop up For security reasons, you need to code sign your application or sign your updates with a EdDSA key.

I don't know why this warning appears, but it's also probably related to the way you removed Kite.

First, I had installed in my home directory Anaconda
Now i have done as /opt
It did solve one problem but now i have 2 pip and 3 python versions
But yeah one problem down :)

It did solve one problem but now i have 2 pip and 3 python versions

Please uninstall them all because they interfere between each other. And leave only one in Anaconda.

ok, but this will also create issues with previously used pip as having installed a lot of things on it. Also, some paths have to change, is it so?

/Library/Frameworks/Python.framework/Versions/3.8/bin/

It's a really bad practice to install things in your system Python because it can break your operating system. So whatever you installed there, please remove it.

/usr/local/lib/python3.7/site-packages

This probably comes from a Homebrew installation. It's fine to leave it but you need to avoid mixing packages there with Anaconda.

I'm sorry but I'm going to close this issue because it's not a problem with Spyder but with the way you installed and mixed several Python versions. So you need to untangle the mess you made and things should be fine again.

Thanks for the help, actually I was going to uninstall Spyder and all not gonna lie
But you actually helped me through. I will learn to untangle this mess and I will keep and learn more about Spyder :)


Implement Basic VM

One possible interface could be:
type VM interface {
   Execute(opcodes []byte) bool
}

returning true if Execution was successful, false otherwise

@im-kulikov Hey thanks for the offer! This has already been taken, I was opening this up to keep track of any ongoing conversations

@decentralisedkev cool, can you assign he to issue?

issue, without assign, a little confusing

@im-kulikov Yeah sorry for the confusion, I'm not able to assign anyone outside of CoZ github group

sounds sad. @fabwa @anthdm  could you give rights for @decentralisedkev?
or mb @hal0x2328 can help us?

I would but I don't have the power either

So sad

Will do

I have not heard back from those who were assigned this issue. I will assign this to myself to get the ball rolling.


Bumped VPA version to latest with PDB fix

Signed-off-by: Marcus Noble<EMAIL_ADDRESS>This PR:

Adds/changes/removes...

Testing

[ ] Fresh install works.
[ ] Upgrade from previous version works.

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml is valid.

/test create

/test create


DOC: Add Python Quick Start guide

Incorporated from the ITKPythonPackage repository.

@jhlegarreta thank you for the thorough review! :pray:


Update config index schema if needed at the start of each monitor execution

Issue #, if available:
#841
Description of changes:
Update config index schema if needed at the start of each monitor execution. This fixes issues when upgrading the cluster where the index mapping changed and the user has not indexed or updated a new monitor yet.
CheckList:
[X] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #849 (d3b88ce) into main (3f2e651) will decrease coverage by 0.27%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #849      +/-   ##
============================================
- Coverage     75.46%   75.19%   -0.27%
+ Complexity      111      110       -1
============================================
  Files           125      125
  Lines          6885     6891       +6
  Branches       1034     1035       +1
============================================
- Hits           5196     5182      -14
- Misses         1158     1178      +20
  Partials        531      531

Impacted Files
Coverage Δ

...in/org/opensearch/alerting/MonitorRunnerService.kt
75.47% <0.00%> (-6.53%)
:arrow_down:

... and 7 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Looks like bwc test is failing


Fix formatting issue

Missing backtick was causing unhappiness.

Can one of the admins verify this patch?

@googlebot  I signed it!

@Undo1: Thank you for the fix!  Backticks are depressing hard to see. :)


manual install description missing the needed steps

https://samtecspg.github.io/conveyor/getting_started/advanced-installation
the steps needed to execute are missing.
Nothing shown after:  Here are the steps to take for this type of install:
tested on OSX with Firefox/Safari/Chrome

Hey @mdiehm sorry for never writing the docs. installation in an existing cluster is something we haven't tackled for anyone but ourselves and the process is highly dependent upon cluster version, etc.
Are you trying to install in an existing cluster? Have you already tested with our compose and the basic installation?

I actually thought about trying it within my local environment which is build using: https://github.com/elastic/stack-docker/
I run 6.5.1 and was playing with the new data visualizer and the csv import. Some research brought me to conveyor... I work for the university and would love to give our researches a fast and easy way to ingest and visualize their data.

Okay, we will try to update to 6.5.1 today/tomorrow and publish a new version. That way you can test completely using our compose stack and avoid the "advanced installation" for the moment.

@wrathagom
The advanced installation instructions would be nice. I have an existing cluster I would like to install to that doesn't use docker at all.


FEAT - update single source endpoint

What feature would you like to see?
I think it make more sense to update the single source endpoint from /:sourceId to /sources/:sourceId like the regions endpoint.
Possible implementation

change the endpoint for the single source id in src/routes/api/news
convert the sourceId comming from the request params to Lowercase and remove any spaces in `src/middlewares/existingSourceMiddleware

Additional information
No response

hi @TAKANOME-DEV , can you please assign this issue to me?

It's yours :rocket:


Make argparse not print to standart output

Also, fix extra while spaces when no argument is passed.

I have tested this locally :).

Well then -- off we go!


Add OAuth/OAuth2 options to ICRemoteConfiguration

OAuth2 is a popular and secure way to consume APIs without storing usernames and passwords. Many APIs use this authentication method. InstantCocoa would benefit from incorporating this functionality.

Agreed, and it's not clear exactly how that should fit into ICRemoteConfiguration. If you have a proposal, I would definitely be down to hear it.

Why not just have a OAuth2Token property and do setValue:forHTTPHeaderField with Value being: "Bearer {OAuth2Token}" and  HeaderField being "Authorization"


Integration tests

What feature do you want to see added?
Right now we rely exclusively on unit test
We should have some integration test to test the CLI after packaging
This could be achieved using failsafe plugin and maven invoker and running integration test after assembly file
A first iteration could be to run the jar with only some command in dry-run mode
This would allow to catch classpath or packaging issue which can be detected with unit tests
Upstream changes
No response

One example when a unit test is passing when fail at execution

Plan to add integration tests for the CLI using the Maven Failsafe and Invoker plugins. The tests will run in a dry-run mode after packaging (via assembly) to catch classpath and packaging issues not covered by unit tests. I'll update the pom.xml, add integration test cases under src/it, and ensure they execute correctly after the assembly step. Let me know if this approach works or if there are any suggestions!

Sure looks good thanks! There are other component that miss tests, like Maven Invoker.
Any PR that increase coverage is good

Submitted a PR , please review as I am a beginner and this is one of my first contributions this side


Fix location permission test for older Hadoop versions

In older Hadoop versions (2.0), files are always created with permissions that do not have execute bits. In later Hadoop versions, execute permissions are permitted for files. This changes the test location permission case to adjust the expected permissions for the missing execute bits, based on the Hadoop version.
Also fixes an intriguing bug where creating a directory (say a/b/c/) one of whose parents (say a/b) already exists as a file, Hadoop throws an access control exception. This is because the execute bit is not set on files. We must expect that exception and handle it properly.

LGTM


[RELEASE] Console release v0.22.5

Console release v0.22.5 has changes the impact the docs:

[ ] New Encryption tab for setting up KMS PR #2377
[x] Authorized users can perform s3:Get* actions from the Console PR #2559

PR 2559 was addressed indirectly as part of #712.


Tiller crashes when deployment with name containing '/' created

Hi there
Whilst developing some tooling around helm, I've noticed that when creating a resource with a name containing a '/' in it, the local helm client exits with Error: transport is closed, and the Tiller pod crashes (although recovers once k8s restarts it).
I wouldn't expect Tiller to support / characters in names, but I would expect a more helpful error message at some point during the creation. Specifically I'd also not expect a crash from Tiller.
I can help pick apart the codepath to spot where this needs adding in, but want to make a note of it before I do.

Can you provide the crash log's stack trace? You are right that this should not cause a crash.

Having trouble reproducing. Here's my template:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: foo/{{ .Release.Name }}
  labels:
    chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}"
spec:
  replicas: {{ .Values.replicaCount }}
  template:
    metadata:
      labels:
        app: {{ template "fullname" . }}
    spec:
      containers:
      - name: {{ .Chart.Name }}
        image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
        imagePullPolicy: {{ .Values.image.pullPolicy }}
        ports:
        - containerPort: {{ .Values.service.internalPort }}
        livenessProbe:
          httpGet:
            path: /
            port: {{ .Values.service.internalPort }}
        readinessProbe:
          httpGet:
            path: /
            port: {{ .Values.service.internalPort }}
        resources:
{{ toYaml .Values.resources | indent 12 }}

So this will generate names like name: foo/quaffing-panda.
Now if I run it, I get:
$  helm install .
Error: release bold-possum failed: Deployment.extensions "foo/bold-possum" is invalid: metadata.name: Invalid value: "foo/bold-possum": must match the regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* (e.g. 'example.com')

And if I look at the Tiller logs, I see:
2017/01/30 23:35:31 storage.go:37: Getting release "bold-possum" (v1) from storage
2017/01/30 23:35:31 release_server.go:872: Executing pre-install hooks for bold-possum
2017/01/30 23:35:31 release_server.go:899: Hooks complete for pre-install bold-possum
2017/01/30 23:35:31 storage.go:133: Getting release history for ''
2017/01/30 23:35:31 release_server.go:835: warning: Release "bold-possum" failed: Deployment.extensions "foo/bold-possum" is invalid: metadata.name: Invalid value: "foo/bold-possum": must match the regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* (e.g. 'example.com')
2017/01/30 23:35:31 storage.go:45: Create release "bold-possum" (v1) in storage
2017/01/30 23:35:31 release_server.go:633: Failed install perform step: release bold-possum failed: Deployment.extensions "foo/bold-possum" is invalid: metadata.name: Invalid value: "foo/bold-possum": must match the regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* (e.g. 'example.com')

This is on Helm 2.1 and Kubernetes 1.5.2.
Can you provide me a little more data to try to debug?

@munnerz anything you can add to this? I'm stalled out because I can't reproduce. If you can help me, I will push to get this into the next release.

If anyone can reproduce this, please let me know (and please provide an example). I can't reproduce, and I'll have to pull this off of the 2.2.0 milestone in a few days.

Alright, with no new information and a pending release tomorrow, I'm moving this off of the 2.2.0 milestone. Sorry.

@thomastaylor312 Close this as obsolete?

Yep. Closing this as it has seen no activity in over 30 days. If this is still an issue, feel free to let us know here


pdfsam-basic: 5.2.2 -> 5.2.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/torakiki/pdfsam/releases.
meta.description for pdfsam-basic is: Multi-platform software designed to extract pages, split, merge, mix and rotate PDF files
meta.homepage for pdfsam-basic is: https://github.com/torakiki/pdfsam
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.2.3 in filename of file in /nix/store/qwzr4fbkmzm6792ad0a1cbrnp549k3m9-pdfsam-basic-5.2.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

pdfsam-basic

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qwzr4fbkmzm6792ad0a1cbrnp549k3m9-pdfsam-basic-5.2.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pdfsam-basic https://github.com/r-ryantm/nixpkgs/archive/30bf4b308d8e9baa6c79b13e9b822be48a635b5e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/30bf4b308d8e9baa6c79b13e9b822be48a635b5e#pdfsam-basic

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qwzr4fbkmzm6792ad0a1cbrnp549k3m9-pdfsam-basic-5.2.3
ls -la /nix/store/qwzr4fbkmzm6792ad0a1cbrnp549k3m9-pdfsam-basic-5.2.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

pdfsam-basic

Maintainer pings
cc @1000101 for testing.

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

1 package built:

pdfsam-basic


reverted import groups

follow up https://github.com/uber/cadence/pull/3469

Coverage decreased (-0.09%) to 66.824% when pulling af349159c4346e5f1f8a4f3e5dd81707b3e0c84b on mkolodezny:tmp into dcfa0a305a7e0ba734e0b92d9c2c8f1758095f18 on uber:master.


Quote use of get_shim_versions & preset_versions

Summary
I've been getting a syntax error ever since I upgraded to the newest master and tracked it down to functions that needed escaping (I don't remember where I got the escaping idea - maybe issue 581.
Fixes this syntax error:
asdf
/Users/john/.asdf/lib/utils.sh: line 619: syntax error near unexpected token `('
/Users/john/.asdf/lib/utils.sh: line 619: `    grep -f <(get_shim_versions) <(preset_versions) | head -n 1 | xargs echo'
version: v0.7.5-8826dc7
...

Other Information

Doing a git bisect, I found that the error first appeared in (two places) in shim-exec.sh and one of them later moved to utils.sh where I ran into it.

I'm running on macOS 10.15.1 (19B88).

Hey @JohnB this isn't PR'd to the asdf repo. You'll need to update the base to the asdf/master branch.


Space char not working on latest neovim

This is my config:
let g:indent_blankline_char = '│'
"char = '·",
let g:indent_blankline_space_char = '·'
let g:indent_blankline_show_trailing_blankline_indent = v:false
let g:indent_blankline_show_first_indent_level = v:false
let g:indent_blankline_show_current_context = v:true
let g:indent_blankline_use_treesitter = v:true
let g:indent_blankline_buftype_exclude = [ 'terminal', 'telescope' ]
let g:indent_blankline_filetype_exclude = [ 'help', 'startify', 'dashboard', 'packer', 'neogitstatus', 'NvimTree', 'Trouble' ]
let g:indent_blankline_context_patterns = [ 'def', 'class', 'return', 'function', 'method', '^if', '^while', 'jsx_element', '^for', '^object', '^table', 'block', 'arguments', 'if_statement', 'else_clause', 'jsx_element', 'jsx_self_closing_element', 'try_statement', 'catch_clause', 'import_statement', 'operation_type' ]

Neovim version:
NVIM v0.6.0-dev+207-g684550ff3
Build type: Release
LuaJIT 2.1.0-beta3

Code example:

As you can see, space char is not showing.

space_charwas removed in favour of vim's listchars space value.
If you don't want to show a special character for all spaces globally, Neovim has a special listchars lead option, that will only be used for leading whitespace.
You can add that character in your init.lua like so:
vim.opt.listchars:append({lead="."})

(I don't know if this works with Neovim 0.5.x, but you are already on 0.6.x where it definitely does work)

space_charwas removed in favour of vim's listchars space value.
If you don't want to show a special character for all spaces globally, Neovim has a special listchars lead option, that will only be used for leading whitespace.
You can add that character in your init.lua like so:
vim.opt.listchars:append({lead="."})

(I don't know if this works with Neovim 0.5.x, but you are already on 0.6.x where it definitely does work)
In general, since #190, all characters are sourced through the listchars values, so also eol and the tab values will be taken from there and shown when appropriate.

Thanks!


[WFCORE-5340] Create the ModelTestModelControllerService variants for…

… the WF 23 controllers
The first step to have a 7.4.0 temporal version on ModelTestControllerVersion based on WF 23. These constructors are used by wildfly-legacy-tests to boot a legacy sever to test the transformers.
Jira issue: https://issues.redhat.com/browse/WFCORE-5340

Core - Full Integration Build 10453 outcome was UNKNOWN using a merge of 55c594ff54c238bd2785006b8f6d930a28ef8dc2
Summary: Canceled (Tests passed: 682, ignored: 4; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 00:05:01

Core - Full Integration Build 10395 outcome was UNKNOWN using a merge of 55c594ff54c238bd2785006b8f6d930a28ef8dc2
Summary: Canceled (Exit code 1 (Step: Build & test full (Maven)) (new)) Build time: 00:05:03

Superseded by #4537


added navigation to docs using mui accordion

added navigation to docs using mui accordion
new library is installed

pictures
https://github.com/zesty-io/nextjs-website/issues/544


Add check on conda-package metadata to guard against .conda packages

Looks like conda doesn't reliably/correctly update the env/conda-meta/<package>.json file which Metaflow relies on to identify which packages should be moved to S3 and their installation order on AWS Batch.
In this specific scenario, when the compute needs to execute on AWS Batch, Metaflow coaxes conda to generate an environment for linux-64 architectures using only .tar.bz2 dependencies, irrespective of where conda is executed from (usually a user's macOS or linux instance). In some very specific scenarios, conda correctly picks up the .tar.bz2 dependencies from upstream repos but fails to update the manifest, incorrectly pointing to .conda dependencies instead. This leads to incorrect bundling of packages and the user job fails when executing on AWS Batch since we end up packaging a .conda dependency as a .tar.bz2 dependency.

Fixes #108


build arm image

connected to https://github.com/mF2C/cimi/issues/4

there's buildArg which might simplify this code duplication, but the image naming and base images would still be a problem

@cjdcordeiro You should verify that the consolidated assembly descriptor works as expected for you.  It looked OK to me.

lgtm


fix: upgrade dependencies

- What I did

upgraded at_client version  which fixes a bug related to sync/monitor while using pkam private key from secure element
upgraded at_commons and at_utils to latest version
- How I did it
modified pubspec and changelog
- How to verify it
unit tests should pass

closing this obsolete PR


Extended AWS Lambda Support

Cartography currently supports populating only AWS Lambda Functions nodes in graph db. With this PR, following extensions are added to the already existing code -

The code will now also populate resources like Lambda Function Aliases, Event Source Mappings and Lambda Layers.
The code will now ingest more attributes of the AWS Lambda Function resource, thereby providing more information.
Currently the code does not use the UNWIND approach, instead it uses loops to populate the AWS Lambda Function resources. This PR rectifies that.

Also remember to update https://github.com/lyft/cartography/blob/master/cartography/intel/aws/resources.py

I'm sorry but I didn't understand what you're trying to say here. I didn't add a new module in AWS, just some extension in the previous code and since lambda is already mentioned here I thought there was no need of any updates here. Am I missing something?
Also, @achantavy changes made as per your review :)

Also remember to update https://github.com/lyft/cartography/blob/master/cartography/intel/aws/resources.py

I'm sorry but I didn't understand what you're trying to say here. I didn't add a new module in AWS, just some extension in the previous code and since lambda is already mentioned here I thought there was no need of any updates here. Am I missing something?

Ah yeah you're right my bad, makes sense.

Also remember to update https://github.com/lyft/cartography/blob/master/cartography/intel/aws/resources.py

I'm sorry but I didn't understand what you're trying to say here. I didn't add a new module in AWS, just some extension in the previous code and since lambda is already mentioned here I thought there was no need of any updates here. Am I missing something?

Ah yeah you're right my bad, makes sense.

No worries. I thought maybe I missed something 😆. Anyways, Changes made. Lemme know if any more changes are left or else you can merge :D


Delete a repeat instance will trigger all question's validation when "validateContinuously" config is true.

Describe the bug
Delete a repeat instance will trigger all question's validation when "validateContinuously" config is set as true.
To Reproduce
Steps to reproduce the behavior. If applicable please include the smallest possible XLSForm or XForm (as zip or link).

Pulish this xlsform: validation_issue.xlsx, there are a repeat question in it, the next question is a required text question.
Set validateContinuously config as true, open the survey.
Click the ' - ' icon to remove a repeat instance, obeserve, the validation of the text question is triggered.

Expected behavior
For this example, the text question has no relationship with the repeat or the child questions in repeat, so even set validateContinuously as true, removing repeat instance should not trigger the text question's validation.
Screenshots

Browser and OS (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

Anothe example for this issue:
Suppose there is a survey with two pages( sample xls form), the fist page has a repeat, the second page has some required questions:

If user fill questions in first repeat, and click '+' to add new repeat instance, then click "next page", no required message shows in second page, this is a normal correct behavior.
But if user click '-' to delete a repeat instance in first page, then click "next page", all required message shows with red background in second page, users will be confused, because these questions are not touched.

sample.xlsx
@eyelidlessness  @MartijnR , could you take a look at this? If this issue is confirmed,  do you have a timeframe time for this issue to be fixed? Thanks!

Found another related issue: adding or deleting repeat will trigger all the question's calculation outside the repeat,
here is an example:test_getRelatedNodes.xlsx.

the question 'group count' should update automatically(because the question is related to repeat question), the current behavior is correct.
the question 'number with calculation' should not update(because the question has no link to repeat question), the current behavior is: this question value always change.

.
I think this issue and https://github.com/enketo/enketo-core/issues/874 can be summarized as:  for repeat instance changing, the collection of the related nodes is inaccurate.

Thanks for filing, @nanzhang01. Do you believe this to be a change in behavior?
I haven’t looked at these in detail but at least the latest you described doesn’t seem like a bug. The spec makes no guarantee that expressions will only recalculate when values they depend on change. There’s the setvalue action if that’s really what you need. You can also use coalesce or something like if(.!=‘’, expression, .)

Get it, thanks for your detailed explanation! @lognaturel .


remove connection_manager filter configs in examples

Your advice
// deprecated: keep compatible for route config in listener's connection_manager
deprecatedRouter, err := configmanager.ParseRouterConfiguration(&lc.FilterChains[0])
if err != nil {
		log.StartLogger.Fatalf("[mosn] [NewMosn] compatible router: %v", err)
}
if deprecatedRouter.RouterConfigName != "" {
	m.routerManager.AddOrUpdateRouters(deprecatedRouter)
}

connection manager in the filter has been deprecated ，but there are still some examples that contains this deprecated config field. If users keep using this, it will be hard to remove code in the future.
I advise to remove these deprecated fields in examples, and print warning log when users keep using this.
Environment

MOSN Version

https://github.com/mosn/mosn/pull/1083


Localized content/bn/docs/tasks/tools/included/kubectl-whats-next.md

Signed-off-by: Adib Reza<EMAIL_ADDRESS>Localizes content/bn/docs/tasks/tools/included/kubectl-whats-next.md>  to Bengali
This is an initial PR as it may need some improvements!

Tracking issue : #31677

/retitle Localize fragment of kubectl install page to Bengali

/retitle Localized content/bn/docs/tasks/tools/included/kubectl-whats-next.md

/label tide/merge-method-squash

@AdibReza  Kindly complete this pr.


General Questions To Test Runs

I have some general questions concerning the runtime. Im just looking for a rough estimation.
Docking two proteins (globular) of 400aa, how long will it take with default settings (based on run.bash). How does the size of the proteins influence the inference time?
Is FTDMP docking optimised for GPUs? How much faster will it run? Will it run faster if I provide more memory?
Similar questions for FTDMP scoring.
Thanks :)

Hi,
I will try to answer, but my running time estimates will be very approximate, sorry.
Docking in FTDMP is not done on GPU, but it can be done on multiple CPU (either on one machine, on on a cluster via slurm). Docking two 400 aa proteins on 8 CPUs can take up to 1 or 2 hours. Docking time and memory consumption depends no-linearly (i.e. worse than linearly) on the size of proteins. I do not have exact numbers, sorry.
Scoring is a different matter - it runs several algorithms, all of them can run on CPU, but some (the ones involving applying neural networks) will use GPU if GPU is available. Scoring is also adapted to run on a cluster via slurm. Overall, scoring stage can  take about 1 hour on 8 CPUs. Scoring time and memory consumption is much less dependent on the protein complex size. The most costly step in scoring is optional relaxing with OpenMM before final rescoring (GPU is very useful for OpenMM).
So, FTDMP can be quite slow, but it can be run on a multi-CPU cluster, see "--parallel-" and "--sbatch-" parameters in the examples (we usually run FTDMP on a cluster using 64 CPUs in the docking stage and 128 CPUs in the scoring stage).
Scoring can be run separately, without docking, if you already have multimeric models generated with other methods (e.g. deep learning-based methods like AlphaFold or RosettaFold). The scoring time will depend mostly on the number of input structures.
Cheers,
Kliment

Thanks a lot, this already helps me estimating the runtime and resources needed :)


[ReadingService] Add mp support for non-shardable DataPipe

This PR is created on top of https://github.com/pytorch/data/pull/555. And, this PR extends PrototypeMultiprocessingReadingService to accept non-shardable DataPipe.
And, this PR depends on https://github.com/pytorch/pytorch/pull/90769
Main Changes

Add a way to launch a process to fetch data from non-shardable DataPipes and send data to worker processes in a round-robin manner

Add MultipleDataPipesToQueuesLoop to connect non-sharding process to request/response queues
Add find_lca_non_shardable_dp as a graph function to determine the lowest common ancestor of all non-shardable DataPipes. This would guarantee that all non-shardable DataPipes will be running in a single non-sharding process
In each worker process,

If All datapipes are shardable, apply multiprocessing sharding to the graph
If not, worker would use find_shardable_branches to find shardable branches to apply mp sharding to those branches, because all non-shardable branches have been properly sharded by routing data round-robinly to worker processes.

Non-shardable DataPipe should provide a method call ed is_shardable and return False
Properly get ResetEpochResponse from protocol via get_response_reset_epoch
[x] Add tests for two graph functions
[x] Add test to launch non-shardable DataPipe process
Add documents

[ ] Shardable DataPipe/Non-shardable DataPipe
[ ] How PrototypeMPRS handles the above two types of DataPipe
[ ] Microbenchmark result

nit Changes

Rename Spawn to Create as the process has not been started

I think we should provide a definition of non-shardable DataPipe and why that may occur (an abstract example would be helpful as well).

Make sense. I will add doc regarding non-shardbable DataPipe/shardable DataPipe to the documents for dataloader2.

In particularly, as you mentioned, note that we do not want to duplicate such DataPipe into multiple workers and sharding filter should not be applied to it. Instead it should be read round-robin (or something else) by downstream DataPipes that are sharded?

Actually, this is not True. sharding_filter is still needed if distributed sharding is needed. We only disabled multiprocessing sharding for the non-shardable branch. And, round-robin reading is also achieved automatically with ProtoTypeMPRS.

That makes sense. How do you plan to implement that? Will we still have users calling .fullsync() and make modification to the graph in DL2? Or making full_sync an option within DL2? Probably the former?

How do you plan to implement that? Will we still have users calling .fullsync() and make modification to the graph in DL2?

We should allow either users calling fullsync or let DistributedRS attach fullsync automatically. Then, ProtoMPRS should do graph modification. WDYT? I am not going to implement it in this PR for fullsync though.

Replying to https://github.com/pytorch/data/pull/919?notification_referrer_id=NT_kwDOAAwycrE1MDQ4ODIwNTc5Ojc5OTM0Ng&notifications_query=reason%3Areview-requested#issuecomment-1351871160 :

Actually, this is not True. sharding_filter is still needed if distributed sharding is needed. We only disabled multiprocessing sharding for the non-shardable branch. And, round-robin reading is also achieved automatically with ProtoTypeMPRS.

An alternative approach for distributed sharding would be distribute the workload based on filename or some compression/encoding unit in file (in Parquet it's called "Page": https://parquet.apache.org/docs/concepts/) and in ORC I think it's called "Stripe". So it avoid reading the original data multiple times?

Non-shardable is an extremely bad name as it's actually being sharded by round-robin dispatching. The actual meaning here is to prevent copy of DataPipe to multiple processes. I might rename it to non-replicable DataPipe/coordinating process.

Non-shardable is an extremely bad name as it's actually being sharded by round-robin dispatching. The actual meaning here is to prevent copy of DataPipe to multiple processes. I might rename it to non-replicable DataPipe/dispatching process.

I agree with renaming "non-shardable" to "non-replicated" DataPipe. I suppose sometimes it is replicable but the users won't want to?

@wenleix @NivekT This PR has been updated. And updated document can be found in https://ejguan.github.io/dataloader2.html#dynamic-sharding

A seperate question is why we need to find LCA for non-replicate DataPipes (not aware of this in other dataflow systems before)

Using the sample graph in https://ejguan.github.io/dataloader2.html#dynamic-sharding. If there are multiple sharding_round_robin_dispatch, there are two ways to merge them:

Use LCA
Launch one dispatching process per non-replicable DataPipe

I choose to use LCA to reduce the complexity of multiple queues and processes communication. Let's talk more detail offline.

I choose to use LCA to reduce the complexity of multiple queues and processes communication. Let's talk more detail offline.

Makes sense. This helps keep our distribute data loading system (relatively) simple with reasonable perf~  . We can revisit the design decision upon use case~


Bug Report: Score Info Layers Over Previous Songs

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
Windows x64
What version of the game are you using? Look in the bottom left corner of the main menu.
<IP_ADDRESS>
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Happens every time I open Kade Engine.
Please describe your issue. Provide extensive detail and images if possible.
So, when I play songs in Kade Engine, somehow my score info gets layered on top of the score info from the previous songs I've played that session, to the point where after 5 or 6 songs the score info screen is filled with notes.
First song I played after opening Kade, all looks normal:

Second song-- as you can see, the red dots remain (it gets harder to tell which other notes are duplicated, so keep an eye on those ones).

And finally, third and fourth. I had tried to turn on minimalized score info for the fourth song, but it didn't fix the issue, just added fewer notes on top of what was already there.

I had my own version of this bug, but it only affected judgements, I played week 6, and when I went to play the tutorial I had 505 sicks, when I replayed it it went to a normal 53 sicks.


Add documentation for 3D scatter plot & surface plot

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

Project coverage is 62.45%. Comparing base (d3c26cb) to head (2fb8383).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #192      +/-   ##
==========================================
- Coverage   62.48%   62.45%   -0.04%
==========================================
  Files          22       22
  Lines        6416     6416
  Branches     1213     1213
==========================================
- Hits         4009     4007       -2
- Misses       2033     2035       +2
  Partials      374      374

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


Compress images after upload to media library

Hi Alexander,
Question; do you know of a way to compress images when they are uploaded via the media library?
I've noticed that admins don't take into account the filesizes of the uploaded images, causing the server space to fill up rapidly. If I'm not mistaken, there's supposed to be an event handler that is triggered after every upload.
Do you think we could extend the image compress plugin to take into account the media library?
Thanks for your answer.

Hi @maartenmachiels , I think you need to take a look at this file and find the event upload photo:
https://docs.google.com/spreadsheets/d/17vv4zn_ezp9iFBgYhYuYsmUG4MXW9uuIw7aOIrVcHiM/edit?usp=sharing

I don't have a ready-made solution

Hi, thank you for your answer. That's okay, I'll be looking into it as soon as possible and will share my findings.

Maybe this can be helpful:
https://stackoverflow.com/questions/52372399/octobercms-rename-file-after-upload-in-media-file-upload-event

@Wachem thank you so much! This is very useful!