Only push tagged to test.pypi.org

If my suggestions are adopted, it will mean:

To publish to test pypi: GitHub Releases -> Draft a new release -> create a new tag (with rc naming convention) -> check "Set as a pre-release" -> publish release
To publish to prod pypi: GitHub Releases -> Draft a new release -> create a new tag (with rc naming convention) -> check "Set as the latest release" -> publish release

NOTE: GitHub Releases do NOT do annotated tags. On GitHub, you can see what user did a Release, if needed. You do lose out on some git functionality without being able to have the annotated tags, though, with timestamps, git describe, user, signing, etc.
Feature request to GitHub: https://github.com/orgs/community/discussions/4924
A workaround would be to figure out how to have the GitHub workflows triggered by prereleases and releases to delete and then recreate the tag but as an annotated tag, if an annotated tag would be desired. That, or have a workflow you can launch that will create an annotated tag, first, before going through the Release page and doing a release based on the new tag. A variant of this could prob be done following https://stackoverflow.com/a/64479344/5340149 (but with a prior step doing github.rest.git.createTag() which would be required for an annotated tag before the step doing github.rest.git.createRef().


Allow attention_mask=None for BetterTransformer in the inference batched case for gpt2 & gpt-neo

As per title, fixes https://github.com/huggingface/optimum/issues/1179

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


API is not working.

Request failed with status code 503

I am getting this same error...does anyone know what happened?

Bro, https://api.codex.jaagrav.in/. The API seems to be suspended and still we are not getting any support, smh..

@Jaagrav Any idea about this issue?

Done fixed, check now. I don't know why render.com does not auto-credit the invoice from me. Constantly need to add my credit card again and again.


Hamburger menu is not working

when i click on the hamburger icon it is changing to cross icon but the nav links are not opening
Could you please assign me this issue under GSSoC 2024

@khushi-joshi-05  please assign this to me i am GSSOC'24 contributor with 2+ years of experience in development

This issue is already solved.
Try to contribute to different issues.


Pre-publish Checklist: Add triggers for page additions

Context
Adding triggers to the Pre publish checklist (PPC).
Summary

When a second page is added the recommended section will become enabled.
When a fifth page is added the high priority section will become enabled.

Relevant Technical Choices
n/a
To-do

[ ] update the tooltip once #7139 is enabled

User-facing changes

Testing Instructions

Create a new story
Click on checklist. All sections should be disabled
Add a new page to your story
The Recommended section should now be enabled
Keep adding pages until you get to 5. The High Priority section should be enabled

QA

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Create a new story
Click on checklist. All sections should be disabled
Add a new page to your story
The Recommended section should now be enabled
Keep adding pages until you get to 5. The High Priority section should be enabled

UAT

[x] UAT should use the same steps as above.

Reviews
Does this PR have a security-related impact?
no
Does this PR change what data or activity we track or use?
no
Does this PR have a legal-related impact?
no
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[x] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #7139
Fixes #7140

Issues open when hitting the 2 and 5 page triggers:


model: Add Reactions data structure, for efficient access in UI

I thought I'd check in with my progress toward keeping an efficient data structure to support the list of reaction buttons on a message in the message list. 🙂
As discussed in chat, this goes directly on Message instances.
In this revision, the data structure retains a raw, "unaggregated" list, like the list it gets from the server. That doesn't have to stay, since it takes up space, but it does make it efficient to count reactions for UserSettings.displayEmojiReactionUsers, and it supports a nice and efficient Reactions.toJson in case the app starts requiring that.
There are TODOs in the tests, but I'll get to those. 🙂
Related: #121

Thanks for the review! Revision pushed, and I've addressed those self-TODOs in the tests this round. 🙂

Thanks for the review! Revision pushed, and see one small query here: https://github.com/zulip/zulip-flutter/pull/286#discussion_r1316570841

Thanks for the review! Revision pushed.

Thanks! All now looks good, but there's conflicts with your #298 which I just merged. Would you rebase past those?

Sure! Thanks for the review; just rebased past those conflicts and pushed the result here.

Thanks! Merging.


SparkClr upgrade to spark 1.5.2 and deprevate API: DataFrame.InsertInto, Save, SaveASTable, SaveAsParquet

Current coverage is 45.64%

Merging #216 into master will not affect coverage as of 449cf93

@@            master    #216   diff @@
======================================
  Files           44      44
  Stmts         4108    4108
  Branches       379     379
  Methods          0       0
======================================
  Hit           1875    1875
  Partial        120     120
  Missed        2113    2113

Review entire Coverage Diff as of 449cf93

Powered by Codecov. Updated on successful CI builds.

LGTM


Utility class border radius

Closes #29989
Updated the docs pages by searching for the .rounded classes and replacing them by the new .border-radius classes.
See
https://deploy-preview-30048--twbs-bootstrap.netlify.com/docs/4.3/utilities/borders/#border-radius
https://deploy-preview-30048--twbs-bootstrap.netlify.com/docs/4.3/utilities/borders/#sizes

This PR does not include rename the border class name, but as @mdo commented above, the new name for border must also be considered. (This does not mean to include it in this PR.)

We should avoid conflicting br (border-radius and border-right). The best solution here is to match Zen Cording.
e.g.

bd-1 : border: 1px solid $border-color;
bdt-1: border-top: 1px solid $border-color;
bdr-1: border-right: 1px solid $border-color;
bdrs-1: border-radius: $border-radius-sm:

This also compatible with the spacing classes.

@JensLuyten Could you change the class names to bdrs?

@ysds At that point, we might as well use radius instead of abbreviating :). I don't mind that fwiw.

@JensLuyten Could you please take a pass at updating this to reflect the latest comments? We're backpedaling on the abbreviations and are opting for radius as the clearest option.


[HOLD for payment 2023-09-12] Dev: Web - Request button in the wrong position

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

Action Performed:

Open the website
Click the + icon from LHN
Click request money
Enter the amount and click next
Observe the Request button from cash detail

Expected Result:
The Request button should be at the bottom
Actual Result:
The request button is in the wrong position
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: Dev <IP_ADDRESS>
Reproducible in staging?: no
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/0b6d9bb3-aac9-43ef-9d6b-af619255d671
Expensify/Expensify Issue URL:
Issue reported by: @misgana96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693502582644489
View all open jobs on GitHub

It is reproducible in staging too for the latest version v1.3.61-2
Screencast from 01-09-2023  7:28:50 ከሰዓት.webm

Proposal
Can create a PR ASAP if required
Please re-state the problem that we are trying to solve in this issue.
Next button while creating split bill is not at bottom
What is the root cause of that problem?
Regression from #26179
Because of added ScrollView, it's not taking full height.
What changes do you think we should make in order to solve the problem?
We should make this flex grow
in MoneyRequestConfirmPage
<ScrollView contentContainerStyle={[styles.flexGrow1]}>
                        <ScrollView
                            horizontal
                            contentContainerStyle={[styles.flex1, styles.flexColumn]}
                        >

result -

What alternative solutions did you explore? (Optional)

@tjferriss Can you please close this one? We will handle this in https://github.com/Expensify/App/issues/26544

@s77rt Why do we close this one? since #26544  is a dupe of #26418

@misgana96 No specific reason except that I'd like to work on the other issue and this one is not assigned to anyone. You'd be still the bug reporter for the other issue.

@s77rt Thank you for your quick response

Even though this issue was first I'm closing it in favor of https://github.com/Expensify/App/issues/26544 since we have already started fixing it over there.

@marcaaron @tjferriss The payment was scheduled for 2023/09/12 if there is no regression. Can you process the payment, please? It is almost 11 days since the PR was deployed to production, and I haven't received the payment for the bug reporter. Thank you

@marcaaron @tjferriss still waiting for your response. It is almost 16 days since it merged in the production but payment not processed still now.

Not involved in the payments system. I will reopen it so that @tjferriss can take a look though.

Not involved in the payments system. I will reopen it so that @tjferriss can take a look though.

Thank you

@misgana96 sorry for the delay. Let's get you paid. I just sent an offer via Upworks: https://www.upwork.com/jobs/~01f0919fe7166fcdbe.

Payment has been sent to @misgana96

Accepted. Thank you


Add more support for Substrait to Velox

Supported TPC-H Q1 related conversions from Substrait to Velox, including:

avg, count, row construct,  plus, minus

Supported using a pre-built plan node as the data source node.
Supported validations based on current supported cases, including:

validations for TableScan (with Filter pushdown), Project, Aggregate

@mbasmanova @pedroerp Would you like to take a review? Thanks.

CC: @ZJie1

@rui-mo Rui, a high level question. Why do we need a separate validation logic that repeats a lot of conversion logic. Why can't we just try converting and catch an exception?

Thanks for your comment.
In validation, we validate the Substrait plan of an operator, and decide whether to offload the computing to Velox based on the validation result. If the validation fails, the compute will fallback to Spark for execution.
Currently the validation is strict, and the not-verified or unsupported cases in TPC-H would fallback. As we continue working on this, we will let more cases pass the validation, and always make sure the TPC-H queries can pass based on this validation and fallback logic.
About you question, there are some differences between the validation and the real conversion, including:

In real conversion, a node can need a child node as its input, but the Substrait plan for its validation only contains itself, which can cause failure if we send this plan to the real conversion.
In real conversion, the input types of a plan node can be deduced from its child node, but in validation we need to send them through the Substrait plan for a type validation.
There are some code not needed for validation in real conversion.
There are some special logic in the validation because current supporting and verifying is still on-going.

We believe the conditions for a validation success will become more broad and general as we continue working on this.

@rui-mo Thank you for explaining the motivation for adding a separate validation logic. As this is non-obvious, would you file a GitHub issue to describe the problem and proposed solution. This would allow reviewers and future readers to understand the design better.
This PR is 3.5K lines long. Can you think of a way to break it up into smaller pieces? This would make it easier to review.

The length of this PR is 1.7k, but 800+ lines are occupied by json files. And 200 lines are from PR#1581, which can be removed if that PR gets merged.

@mbasmanova Thanks for your comment. My colleague @zhejiangxiaomai will help continue fixing the comments. We plan to raise PR from our oap-project instead of personal branch in the future.

@rui-mo Rui, thank you for the heads up. Welcome @@zhejiangxiaomai .


How to handle forked repositories with mure issues

It seems that we need to make some changes to how mure issues handles forked repositories.
I am currently managing https://github.com/kitsuyui/sxd_html/ . This is a fork of  https://github.com/diogo464/sxd_html .
I am the owner of the crates.io package, so I am the one who is actually maintaining it.
The current mure issues does not display a summary for forked repositories.
This means that I might miss issues and pull requests for sxd_html.
Problems

Many forked repositories are created to send pull requests to the original repository. There is no need to manage these with mure.
On the other hand, I want to manage repositories that I am effectively maintaining, such as sxd_html, with mure.

Solution
I implemented https://github.com/kitsuyui/mure/pull/248 and released v0.2.4.
Now you can specify multiple queries to mure issues command.
So you can specify forked repositories individually.
[github]
queries = [
    "user:kitsuyui is:public archived:false fork:false",
    "user:kitsuyui is:public archived:false fork:true sxd_html",
]


Tieredz armor stands reforge unmodified armor

If you equip an armor stand with an unmodified armor piece, it reforges it

Fixed with https://github.com/Globox1997/tiered/commit/8e5eda279b5cb5f0eceadd1f35212a55181d6378


Move logic to redirect to default documentation into a route handler

[ ] Make a generic link that encodes the logic we use for the "Documentation" link from package pages. So, visiting https://swiftpackageindex.com/vapor/postgres-nio/documentation would redirect to https://swiftpackageindex.com/vapor/postgres-nio/1.11.1/documentation/postgresnio or https://swiftpackageindex.com/vapor/postgres-nio/main/documentation/postgresnio if there was no stable release.
[ ] Remove that logic from the package page so that right-clicking the "Documentation" page lets people copy a stable link that will always work.

Thanks to @fabianfett for the suggestion!

That's awesome! Thanks so much!

We should also pass along any catchall after the .../documentation to support deeper links. I.e.
https://swiftpackageindex.com/vapor/postgres-nio/documentation/foo

would ideally resolve to
https://swiftpackageindex.com/vapor/postgres-nio/1.11.1/documentation/postgresnio/foo

as per the rules above.


Use config file instead of flags

There's a config file - config.ini
Default content:
# List of all opts:
# port
# debug
# offset
# should_check_version
# is_write_mode
# open_browser
# open_neat_window

# Port for website
port=:500
debug=false
# number of records on a single screen
offset=100
should_check_version=true
is_write_mode=true
open_browser=true
# has effect only if 'open browser' is true
open_neat_window=true

At first, the program parses the file. If it doesn't exist, program creates config.ini with default content. Next, the program checks is there any flags. If a user sets any flag, program overwrites data, which was got from config.ini


The check rule of expiry is not correct!

1).
I found that the check rule of "expiry" is not correct for most of my cards and no scan result in "expiry" field!! (Most of my cards' maximum year of expiry is "2020")
The check rule in function "expiry_string_to_expiry_month_and_year" ( in expiry_categorize.cpp , dmz) is as below, and it is not correct or say it should be (full_year <= current_year + 5) ?
if (full_year < current_year + 5
    && (full_year > current_year || (full_year == current_year && month >= current_month))
        ) {
..................
}

2).
I got some information by Google, and it seems that maximum year of expiry may be between 3~8 (usually 5)

@dgoldman-ebay IIRC we used to accept cards up to 15 years in the future. Thoughts?

The greater our tolerance, the fewer complaints we'll get from people entering far-future cards. But we'll also see some increase in incorrect expiry scans for near-future cards being interpreted as farther in the future than they really are.
It's a tradeoff, and not one that's easy to quantitate.
So if people are going to be complaining about 5 years being too tight a tolerance, I'd lean toward opening things up a bit, but not too much. Based on @AlanYen's googling, how about 8 years?

8 years SGTM.


Modified "Star us" in the footer

Changed the button text and modified the CSS for better readability as well as design.#146

fixes #146

can you change color of rateus to purple (original) and don't add hover on blue box, add just on rate us text @sau-mili

Okay i will change those and mention here

You can check it now @HimanshuNarware

@HimanshuNarware please check and merge this.. I have been waiting for days :(

Ok good Work @sau-mili

Can you please add the gssoc and level labels?


fix: expand ReentrantLock scope in MonitorThreadContainer for better …

…thread safety
Summary
Remove race condition in MonitorThreadContainer between getInstance() and releaseInstance() methods.
Description
In the MonitorThreadContainer, there are possible race conditions between the getInstance() and releaseInstance() methods.
In one of the race conditions is in the getInstance().
...
      } finally {
        LOCK_OBJECT.unlock();
      }
    }
    CLASS_USAGE_COUNT.getAndIncrement();
    return singleton;
  }

Just after the lock object is unlocked, is an opportunity for a race condition with another thread in the releaseInstance() method.
...
    if (CLASS_USAGE_COUNT.decrementAndGet() <= 0) {
      LOCK_OBJECT.lock();
      try {
        if (singleton != null) {
          singleton.releaseResources();
          singleton = null;
          CLASS_USAGE_COUNT.set(0);
...

If the locked block is entered, a race condition may result.  getInstance() may  return a null singleton which will be followed by a NPE. Or another scenario is that a non-null singleton will be returned, but singleton.releaseResources() is called so the MonitorThreadContainer's threadPool will be shutdown and subsequent usage of the threadPool will result in a RejectedExecutionException.
Additional Reviewers

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Just realized that perhaps using synchronized on both methods may be a better solution.

Instead of using synchronized it would be better to use the re-entrant lock before the first check. synchronized is still a heavier lock.


A combination of the functionality in both #38 (continued)

Hello,
this pull request tries to continue, where https://github.com/tonybaloney/sphinxcontrib-confluencebuilder/pull/38 left off. I rebased @JPTeasdale changes to the current master branch and applied some of the suggested changes by @jdknight.
Regards,
Przemek Czerkas

@jdknight how does this PR relate to the page hierarchy in #58 ? Is this one still required?

@tonybaloney , this PR (as well as #38) are both related to the changes introduced in #58. PR #58 takes a subset of changes introduced in #38, which are also used in this PR.
If possible, I would prefer if this PR (and #38) still remain open for now as the "maximum page depth" capability has yet to be ported over (another task I'm hoping to perform; see #35). My plan was to re-look at these PRs to port the request feature (and possibly other minor updates) into the newer set of code (which can been brutally refactored a bunch with other changes I wanted to make).
I would like to propose to leave them open for reference until I've assessed #35 completely (hopefully before the end of this year); however, if you're looking to cleanup this repository, I can make a snapshot of the current PRs and save them in another location for the interim. Either solution works for me.

The changes introduced in the pull request have be addressed in other recently merged requests (see #35 for more details). Marking this PR as closed.


CI/CD fixes

Fix the CI/CD failures mentioned in https://github.com/scipy/scipy/pull/15641#issuecomment-1489241125.

Slightly loosen the inequality KKT multiplier tolerances in _check_kkt. Previously required g_eval >= -1e-14, now require g_eval > -1e-12. Theoretically, if a solution satisfies the inequality constraints then they must be non-negative, but in practice sometimes they turn into small negative floats. The tests originally passed locally with the stricter tolerances, but failed on the CI/CD server side test (one multiplier was about -2e-14).
Fix my formatting mistake in the _minimize example.

@mdhaber this PR addresses the CI/CD failures you found. I think the base branch needs to by updated to sync with the upstream scipy:main?

The best way to submit PRs in this manner, that prevents all the git mess are to:

git add remote andyfaff https://github.com/andyfaff/scipy.git
git fetch andyfaff
git checkout kkt
git checkout -B mychanges

git push origin mychanges
Start a PR on my fork, against my kkt feature branch, asking to merge in Tenavi:mychanges.

The best way to submit PRs in this manner, that prevents all the git mess are to:
1. `git add remote andyfaff https://github.com/andyfaff/scipy.git`

2. `git fetch andyfaff`

3. `git checkout kkt`

4. `git checkout -B mychanges`

5. <git commit>

6. `git push origin mychanges`

7. Start a PR on my fork, against my `kkt` feature branch, asking to merge in `Tenavi:mychanges`.

Ah I see thanks for those instructions. I wasn't sure how to grab changes from your fork directly. I'll close this PR and redo with the workflow you suggested.

The third step may be git checkout andyfaff/kkt. You can use what I wrote if you don't have a branch called kkt.


Querying entities

Thank you for this great extension. I checked it in detail and noticed there is no native way to "hide" soft deleted data when querying.
Do you have any suggestions how to achieve that?

I found interesting solution:
https://haacked.com/archive/2019/07/29/query-filter-by-interface/

Hi @stzoran1, thank you for your attention.
As I noted in scope 3.2 of the proposal, you should use query filters in your application's context for querying soft deleted data.
Like this: modelBuilder.Entity<Category>().HasQueryFilter(x => x.DeletedAt == null);
In future versions, I will implement another way to querying soft-delete data.

Thank you for quick reply.


request_id missing from handshake error responses

When a handshake request fails because of the following reasons, the response is missing the request_id:

Unauthenticated connections are not allowed
Anonymous connections are not allowed
Unknown handshake method XYZ

For example:
{
    "method": "anonymous",
    "request_id": 0
}

===>
{
    "request_id": null,
    "error": "Error: Anonymous connections are not allowed.",
    "error_code": 0
}

I'm tinkering with a Horizon client for Android. Without the request_id in the response, it makes it challenging to look up and invoke the listener method provided when the handshake request was made. It would be risky to assume the handshake request ID is always 0 as clients may re-try failed handshakes (with a new, non-expired token for example.)
Server version: 2.0.0
Client version: 2.0.0

Did you add this in your server side as well as client side authType:anonymous or unauthenticated
const horizonServer = horizon([publicServer, loopbackServer], {
    project_name: 'myProjectName',
    auth: {
      token_secret: 'foo-bar',
      allow_anonymous: true,//this is important
      allow_unauthenticated: true,//important
    },
});


Avoid self-intersections during ray tracing

Potential method to implement:
A Fast and Robust Method for Avoiding Self-Intersection (Chapter 6), Ray Tracing Gems.

Implemented in d548ed9.


Photos changing too fast

I downloaded the Google photos module and it works fine for the first 5 min but then the photos start change really fast. I looked at config file but i don't see anything wrong with my code. are you guys able to help?

Please try with the latest version and share the logging.


#1938 Added Create rig functionality

Fixes
This pull request fixes #1938
Description
Type of change

[ ] Bugfix
[x] New feature (non-breaking change which adds functionality)
[ ] Enhancement of existing functionality
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Impacted Areas in Application

[x] Frontend
[x] API
[ ] WITSML
[ ] Other (please describe)

Checklist:
Communication

[ ] I have made corresponding changes to the documentation
[ ] PR affects application security

Code quality

[ ] I have self-reviewed my code
[x] No new warnings are generated

Test coverage

[x] New code is covered by passing tests

Further comments

Please fill out the issue number under "Fixes" in the PR template to link this PR to its respective issue

There seems to be an issue with approving PRs https://github.com/orgs/community/discussions/58535
Give this comment a thumbs up and I will merge the PR.


Add Delegates and Events video

Describe the bug
Add the Programming in Practice - Delegates and Events

Duplicates #406


v3.0.0 Broke Spell Check

After updating to 3.0.0 my spell check doesn't work. I had to do a complete reinstall after updating to 3.0.0 due to only seeing a white screen, if that could have done anything.

spell check worked for me for the first load, and then after that I am not longer seeing it working.

After update mine is also not working.

No spell check on Mac or Windows.  Gotta have spell check so unfortunately switching back to using messages in Chrome for the time-being.

Oh man, I keep checking back on Mac to see if the spellcheck works and it doesn't and I keep going back to using Chrome which does.  Is this in the works at all?  This is useless to me without spellcheck.  I appreciate the effort but that's such a core thing to be missing with a texting app.


[Bug]: Cannot open isa.study.xlsx file in Excel (macos and windows)

Contact Details
No response
What happened?
When opening isa.study.xlsx file in Excel after adding a study sheet and populating it with headers (both macos and windows) it prompts an alert message (see screenshots).
To open the file, it has to "repair it". If you then save the changes, the sheet will not appear in arcitect any longer.

The changes automatically made are the following (macos):

What did you expect?
No response
Host
ARCitect
Host Details
Excel version 16.78 (macos)
Swate version
Swate Release Version v1.0.0-beta.04

Hello! Could you share an example file with us? I will look into this!

Here you go
isa.study.xlsx

Ah okay, i see the issue the table from worksheet NewTable0 is removed, after reopening. This makes it not readable for Swate/ARCitect. Sadly this seems to be a deeper nested issue, which might take some time to investigate.

Hey again, i tried to investigate this issue but i am unable to reproduce it with the columns you used. I am on windows 11. You said you had the same issues on windows?

I'm facing the same issue. I can easily reproduce it. I just created a new table and added a "Characteristics" column. When I then want to open the xlsx with Excel then i receive the mentioned warning and the file is broken afterwards.

Hey @arendd can you upload an file? I want to checkout the exact file 🙂

Sure, here it is: isa.study.xlsx

Thanks! Will look into this as soon as possible!

Hey Kevin, I think i have an idea, what is the reason. This error comes when creating a new empty table with just some headers, but without rows. As long as you do not add any row via "+" button you can save the table within the ARCitect, but you can not open the according xlsx with Excel. After adding at least one line, Excel no longer throws this warning. Can you reproduce this?

Yes can replicate this!
@HLWeil i thought we resolved this issue somewhen in ARCtrl? I am running version [2.0.0-beta.8.swate].

@HLWeil bump


Changed the binary site path to download from but npm adds a path

NPM version (npm -v): 6.4.1
Node version (node -v): 10.14.1
Node Process (node -p process.versions):
{
http_parser: '2.8.0',
node: '10.14.1',
v8: '6.8.275.32-node.36',
uv: '1.23.2',
zlib: '1.2.11',
ares: '1.14.0',
modules: '64',
nghttp2: '1.34.0',
napi: '3',
openssl: '1.1.0j',
icu: '62.1',
unicode: '11.0',
cldr: '33.1',
tz: '2018e'
}
Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): 4.9.3*
npm node-sass versions (npm ls node-sass): N/A

*the issue is trying to download node-sass
Basically, I can't access github for node-sass from this corporate network on my virtualmachine. However, we have a proxy where node-sass is located: http://our-proxy.com/respository/node-sass
This repo has version 4.9.3 in it, but it's a tar.gz file. I'm not sure if npm doesn't like that.
I've set my SASS_BINARY_SITE to the node-sass location on the proxy and npm acknowledges it:
Downloading binary from https://our-proxy/repository/npm-proxy/node-sass/v4.9.3/linux-x64-64_binding.node
Cannot download "https://our-proxy/repository/npm-proxy/node-sass/v4.9.3/linux-x64-64_binding.node": tunneling socket could not be established, statusCode=405
When I run npm install, install.js is adding the "v4.9.3/linux-x64-64_binding.node" to the end of the site path so it basically can't find the download because nothing exists at that path.
So it there a way to also change the download path that npm is searching our proxy site for? OR is there a way to not try to download node-sass at all because this is mainly for resolving giant globs of errors that don't necessarily affect the rest of the build.

Ended up using a locally downloaded version of node-sass and pointing npm to it with
SASS_BINARY_PATH and SASS_BINARY_DIR. Needed to set both for it to work.


Model does not produce expected results

I have followed the directions in the repository to download and run the model. The code successfully executes for the following image (directly from the Tensorflow im2txt repository)

However, when I run the model against this image, I receive the intended results:

What could be the problem that I am running into?

I have the same issue.  Also, I get the same out of memory warnings you're getting on my 1080, and I had to add allow_growth config option or it would bomb.
I also tried it on a rented 2080 ti and got the same classification, but no memory warnings.

Same probleme here, any update yet?
Also tried this implementation here: https://modeldepot.io/leeryboy/show-and-tell but the results are the same.

Hello, I have the same issue of poor performance.
Can you tell me what is the problem

Found the solution:
https://github.com/tensorflow/models/issues/6513

When I change line 182 to:
most_likely_words = np.argsort(word_probabilities)[-self.beam_size][::-1]
I get:
IndexError: invalid index to scalar variable.
Did anyone face this or know how to solve it?


Add slack channel when logging error.

Add the slack channel when logging error from slack.
https://github.com/prometheus/alertmanager/issues/2176

You need to sign your commit.
git amend -s
git push origin

Is the test failed because of my commit ?
--- FAIL: TestReload (5.15s)     acceptance.go:186: starting alertmanager cluster: starting alertmanager failed: timeout     acceptance.go:177: Error sending SIGTERM to Alertmanager process: no such process

This is a flake, I've retriggered the test.

Thanks!


conntrack: Cleanup egress entries and distinguish redirects per endpoint

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

The re-enabled conntrack tests are passing with this fix: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1458/
Will do at least one more build to be sure.

test-me-please

test-me-please

Last run failed in K8sValidatedKafkaPolicyTest. Unrelated to this PR.
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1465/
Starting another run.

test-me-please

Still seeing failure in the conntrack tests:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1459/execution/node/55/log/
But this is a new failure mode which I haven't seen before:
07:49:42 RuntimeValidatedConntrackTable
07:49:42 /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:170
07:49:42   Testing L3-L4-L7 policy while the L3-L4 connection was previously made to confirm L3-L4-L7 policy enforcement over the proxy with the same source port [It]
07:49:42   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:202
07:49:42
07:49:42   Failed to httpRequest 'docker exec -i  client bash -c "python ./nc.py 11111 5 f00d::a0f:0:0:ba08 80 \"/public\" | head -n 1 | grep \"HTTP/1.*200 OK\""' from client to f00d::a0f:0:0:ba08: Traceback (most recent call last):
07:49:42     File "./nc.py", line 26, in <module>
07:49:42       data = clientsocket.recv(4096)
07:49:42   socket.timeout: timed out
07:49:42   Traceback (most recent call last):
07:49:42     File "./nc.py", line 26, in <module>
07:49:42       data = clientsocket.recv(4096)
07:49:42   socket.timeout: timed out
07:49:42
07:49:42   Expected
07:49:42       <bool>: false
07:49:42   to be true

This turns out to be half-OK. The previous nc connections matching the same conntrack entries and accessing /private were fine:
07:49:09 time="2018-03-21T07:49:09Z" level=debug msg="running command: docker exec -i  client bash -c \"python ./nc.py 11111 5 f00d::a0f:0:0:ba08 80 \\\"/private\\\" | head -n 1 | grep \\\"HTTP/1.*200 OK\\\"\""
07:49:09 time="2018-03-21T07:49:09Z" level=debug msg="running command: docker exec -i  client bash -c \"python ./nc.py 11111 5 <IP_ADDRESS> 80 \\\"/private\\\" | head -n 1 | grep \\\"HTTP/1.*200 OK\\\"\""
07:49:09 time="2018-03-21T07:49:09Z" level=debug msg="running command: docker exec -i  client bash -c \"python ./nc.py 11111 5 f00d::a0f:0:0:ba08 80 \\\"/public\\\" | head -n 1 | grep \\\"HTTP/1.*200 OK\\\"\""

So the conntrack entries are what we expect them to be. HTTP requests are going through and getting filtered by Envoy.
This must therefore be a failure in Envoy for this particular HTTP request.

@jrajahalme Incidentally, I see this in the logs:
Mar 21 07:36:31 runtime cilium-agent[16349]: level=warning msg="Envoy: Execution failed: signal: segmentation fault (core dumped)" error="signal: segmentation fault (core dumped)"

It's not related to the failure I saw, as the timestamps don't match. And that's inconsequential. But we need to get to the bottom of those sporadic segfaults.

test-me-please

Build passed: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1468/

test-me-please


support "system" package manager

The default package manager is npm@latest, but that should probably be npm@system.  That is whatever npm is in your PATH.
Since system is not a dist-tag used by any package managers (I don't love relying on that, but whatever), we'll need to special-case it.  In the case of yarn@system, this is whatever yarn you have installed.
If a "system" package manager is not found, throw.

done in #402


Heating and Cooling Thresholds always read 80°; Illegal Heat Threshold Values in Log

Hi! I've had some success with the plugin: I can use it to shut my Carrier off, and change it between heating and cooling. It reads back the temperature and mode correctly to HomeKit. But I can't seem to set the heating or cooling set points. No matter what the Carrier reads, HomeKit always reads the set point at 80° F.
Possibly related, I get these log entries frequently. I turned on debugging to get the stack trace:
[8/29/2022, 9:11:44 PM] [homebridge-infinitude-v2] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 26.666666666666664 exceeded maximum of 25. See https://homebridge.io/w/JtMGR for more info.
[8/29/2022, 9:11:44 PM] [homebridge-infinitude-v2] Error:
    at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
    at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2049:14)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1617:24
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:10:18
    at InfinitudeThermostat.<anonymous> (/homebridge/node_modules/homebridge-infinitude-v2/src/InfinitudeThermostat.js:168:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

26.66° C == 80° F, so the error is probably connected to the display issue.
That log was from just a few minutes ago, but the Carrier is in cooling mode. So I'd expect a warning about the cooling threshold, not the heating threshold.

@johnataravir Is the thermostat in Celsius or Fahrenheit? Also, can you check what Infinitude is reporting as your heat setpoint? My current thought is it might be a conversion issue, but this information will help.

Oh- also, I made a mistake above. I confirmed last night that the plugin is setting the setpoints correctly. The only problem is that once it does, HomeKit still reads them as set to 80.

Could you drop your status.json from the infinitude instance? You can get it by going to http://infinitude-ip:port/status.json.

Sure thing! It's enclosed. Github "doesn't support that format" (JSON), so I changed the extension to .txt.
status.txt

So, this is odd. I grabbed and uploaded the above status.json a minute ago, and uploaded without looking at it. Then I went upstairs, and realized it was really hot. Sure enough, the Carrier was actually set to a CLSP of 80°, and the output agrees. So I'm enclosing the one I took last night, as well. I verified that HomeKit said the CLSP was 80° when I took this one, but you can see that the CLSP for Zone 1 is 71°.
status-original.txt
I'm not sure what to make of that. Maybe HomeKit is somehow getting 80° as the CLSP, and is then setting it again when it sees drift?
I'm wary of changing too many variables at once, but I haven't blocked the API servers, so the pump is still talking to Carrier. I know Infinitude should bypass all that, but let me know if you think I should block those. It might eliminate a potential variable.

I found something interesting. The JSON you sent me shows a CLSP and HTSP of 80°, but I am unable to actually get Infinitude to take 80° for the heat set point. I am not sure what is going on there.
I do have an update that might fix the issue. The 80° heat set point might be soft locking the plugin, causing it to not read and write other values correctly. The new version should be on NPM shortly. Let me know if it fixes your issue. It fixes some other small issues.

Awesome! Thanks so much for the fast response on this. I'll test it out as soon as I can and let you know how it goes.

No problem. If this patch doesn't work, we can try blocking the Carrier API, but I have not had to do that for the plugin to work, but it might comedown to variances in hardware/system configuration.

I'm running the patched version now. It seems like HomeKit is now unable to change the set point at all. It can still turn the device on and off, but no matter what I do, the set point seems fixed at 80 (which appears to be some kind of default in the Carrier: it's set at 80 whenever I turn it back on from being off).
I'm also seeing this error in the logs, which seems new:
[8/30/2022, 9:07:34 PM] [homebridge-infinitude-v2] This plugin generated a warning from the characteristic 'Target Temperature': characteristic value expected valid finite number and received "[object Promise]" (object). See https://homebridge.io/w/JtMGR for more info.
[8/30/2022, 9:07:34 PM] [homebridge-infinitude-v2] Error:
    at TargetTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
    at TargetTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2030:14)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1617:24
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:10:18
    at InfinitudeThermostat.<anonymous> (/homebridge/node_modules/homebridge-infinitude-v2/src/InfinitudeThermostat.js:59:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I took some time to review the JSON you sent in more detail, and there are some differences between it and what I see on my local system. One thing that stands out to me is you version is 1.41 and mine is 1.7. I am not exactly sure where Infinitude pulls this, but what thermostat do you have (model #) and what version/firmware is it on? I believe you can check in one of the setting menus on the t-stat itself. It might be a compatibility issue with either newer/older hardware.
Also, if you set the heating/cooling set point directly with Infinitude, does it set it correctly? I want to try to reduce the number of possible breakpoints and rule out infinitude as the culprit.
One final thing, do you know how to install plugins manually to Homebridge? I can create a branch you can grab to test changes from, instead of dropping updates on the main plugin.

Interesting. I've confirmed that the system thinks it's up to date, at least. It did an OTA update within the last month.

Probably irrelevant, this is the information on the heat pump:
model: 25VNA024A00300
software version: CESR131438-09
And this is what it shows for the Infinity Touch controller, which is a "Series B":
model: SYSTXCCITC01-B
software version: 131626-04.05
I've confirmed that setting the set points directly with Infinitude works fine.
I came across these instructions on using npm to run a non-prod version of the plugin, but couldn't get them to work with the auto-updated Docker setup I have. If you have some instructions or anything you think would help, I'd happily test from a new branch.
Thanks for your help with this!

This is good information. You definitely have a different version of the t-stat than mine.
Could you provide the json you get  from http://:/api/config and http://:/api/status?
I noticed the JSON from the status.json endpoint can be different from those endpoints and those are what the plugin uses.
Since infinitude can set the temperatures correctly, my guess is the data is different than what the plug-in is expecting. Hopefully, the config/status JSON will provide some more insight.
As for the manual plugin setup, it can be pretty complicated (especially with docker, since symlinks are weird). I can provide instructions if there isn't something clear I can get from the config and json.

Makes sense, and sounds good re: the manual plugin stuff. Here are the files:
api-status.txt
api-config.txt

I wasn't able to find anything explicit in those. I can say there are some additional parameters in you config/status calls, but I am not sure that it means that is the issue. I released a new version that adds a new option in the plugin config to enable verbose logging. If you could turn that on and try to set the temperature from HK and send the log file that would be helpful. You can find the log in the root of the homebridge install (if using docker, it's where you mounted the Docker volume). The file should be called homebridge.log.

Thanks! I updated the plugin, restarted, and to get some good logs, I tried to set the cooling threshold to 63°— and it worked. So I turned it off, then set it to cool to 67°, which is the value I'd tested so many times before, and that worked, too. I didn't change anything else.
Unfortunately, it looks like homebridge.log contains all the logs from my homebridge system, some of which are more sensitive than I'd want to post on Github. Is there an address I could send them to you at?
I did capture this, which is what the plugin printed just after I set the heat to 63° for the test. I noticed that the clsp isn't exactly 63, and it doesn't correspond to a clean number in Celsius, either. (It's 17.2° C.)
[9/5/2022, 7:10:04 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F
[9/5/2022, 7:10:04 PM] [homebridge-infinitude-v2] [VERBOSE] http://unicron:3000/api/1/activity/home?clsp=68.00 response: {"clsp":["68.00"],"fan":["high"],"htsp":["55.0"],"id":"home"}
[9/5/2022, 7:10:40 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F
[9/5/2022, 7:10:40 PM] [homebridge-infinitude-v2] [VERBOSE] http://unicron:3000/api/1/activity/home?clsp=62.96 response: {"clsp":["62.96"],"fan":["high"],"htsp":["55.0"],"id":"home"}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] GetTemperatures(): Found zone with ID 1: {"clsp":["63.0"],"currentActivity":["home"],"damperposition":["15"],"enabled":["on"],"fan":["high"],"hold":["off"],"htsp":["55.0"],"id":"1","name":["ZONE 1"],"occupancy":["unoccupied"],"occupancyOverride":["off"],"otmr":[{}],"rh":["67"],"rt":["69.0"],"zoneconditioning":["idle"]}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] GetTemperatures(): Response to HomeKit {"htsp":12.78,"clsp":17.22,"currentTemp":{},"mode":"cool"}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] GetTemperatures(): Found zone with ID 1: {"clsp":["63.0"],"currentActivity":["home"],"damperposition":["15"],"enabled":["on"],"fan":["high"],"hold":["off"],"htsp":["55.0"],"id":"1","name":["ZONE 1"],"occupancy":["unoccupied"],"occupancyOverride":["off"],"otmr":[{}],"rh":["67"],"rt":["69.0"],"zoneconditioning":["idle"]}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] GetTemperatures(): Response to HomeKit {"htsp":12.78,"clsp":17.22,"currentTemp":{},"mode":"cool"}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] GetTemperatures(): Found zone with ID 1: {"clsp":["63.0"],"currentActivity":["home"],"damperposition":["15"],"enabled":["on"],"fan":["high"],"hold":["off"],"htsp":["55.0"],"id":"1","name":["ZONE 1"],"occupancy":["unoccupied"],"occupancyOverride":["off"],"otmr":[{}],"rh":["67"],"rt":["69.0"],"zoneconditioning":["idle"]}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] GetTemperatures(): Response to HomeKit {"htsp":12.78,"clsp":17.22,"currentTemp":{},"mode":"cool"}
[9/5/2022, 7:12:27 PM] [homebridge-infinitude-v2] [VERBOSE] getTemperatureScale() response: F

Let me know what you think! If I turn verbose logging back off and it still works, then my problem is solved, technically, anyway. I can always keep an eye on it and get back in touch if it stops working again.
(Enabling logging masked a bug in something I worked on, once. Printing set an uninitialized value to empty, or something- it was a long time ago. I don't think that's happening here, but since then, I've always been careful about setting my config back to a production state and testing one last time.)

One thing I also changed with this patch that might have been the issue is rounding to two decimal places, so it's possible that the version of the thermostat you have doesn't like going beyond a certain number of decimal places. There was a bug where it wasn't rounding all the time. I will probably bump that down to a single decimal place, I just chose two out of habit haha.
I shouldn't need the homebridge.log
I will close this for now. If you disable logs and it breaks, let me know.


Add 3.28 LTS scenario to test matrix

Tests fail with error
TypeError: Ember.computed.reads is not a function at http://localhost:7357/assets/vendor.js, line 112172

will keep looking and updating other reps

updated some other deps so this now pass


[Feature Request] Support Windows integrated PackageManagement (OneGet)

Is there any plan to add appget as a provider to OneGet?
That would mean, that users could just type
Install-PackageProvider appget
Install-Package firefox

on any fresh Windows 10 installation to install firefox (just an example) without opening any browser to search and install appget first.

I already looked for appget on the list of Provider-Requests for OneGet but there doesn't seem to be an entry for appget.

If you haven't heard of OneGet see https://blogs.technet.microsoft.com/packagemanagement/2015/05/05/10-things-about-oneget-that-are-completely-different-than-you-think/

How to Implement a Package Provider

This is definitely something we would want to do. but I can't really promise any timelines. as always contributes are more than welcome,


Broken "tempDirectory"?

In the latest version the tempDirectory is ignored and the .nyc_output is simply placed top level.
This used to work fine when defined in package.json as
{
 "nyc": {
    "tempDirectory": "./coverage/.nyc_output",
    ...
  }
 ...
}

So apparently this was renamed. I consider this a breaking change...?!

Pending investigation but this appears to be a newly introduced bug.


Not compiled with GPU support

❓ Questions and Help
RuntimeError: Not compiled with GPU support (nms at /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/csrc/nms.h:22) frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x45 (0x7fda63bc0915 in /home/hjl/anaconda3/envs/pytorch1.0/lib/python3.7/site-packages/torch/lib/libc10.so) frame #1: nms(at::Tensor const&, at::Tensor const&, float) + 0xd4 (0x7fda5ee41954 in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so) frame #2: <unknown function> + 0x14e1d (0x7fda5ee4de1d in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so) frame #3: <unknown function> + 0x12291 (0x7fda5ee4b291 in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so) <omitting python frames> frame #62: __libc_start_main + 0xe7 (0x7fdaa4e11b97 in /lib/x86_64-linux-gnu/libc.so.6)

When you compiled maskrcnn-benchmark, you probably didn't have a PyTorch with CUDA enabled.
How did you install maskrcnn-benchmark?

I have the same error as HLearning. I have built maskrcnn with CUDA 9.2 enabled with python3 setup.py build develop.
I checked if cuda.is_available() and CUDA_HOME, and I get True and /usr/local/cuda-9.2 as expcted.
But I still get the same error.
Where else could the problem be?
thanks

Are you running in docker?
This might be related to https://github.com/facebookresearch/maskrcnn-benchmark/issues/167

No, I followed the Option 1: Step-by-step installation.
I saw the thread and was also wondering if it is related to the cuda version (I am running on 9.2)

Yeah that's what I thought, I uninstalled it and manually removed all dependencies. It's still not working after trying to reinstall.

inside the setup.py script, can you print torch.cuda.is_available() and CUDA_HOME?

I get True and /usr/local/cuda-9.2 resp.

@Nacho114 what's the code that you are trying to run? And what is the full error message?

I am running a modified version of maskrcnn-benchmark/tools/train_net.py to run if my custom dataset.
The full error message is:
. . .
eight                  loaded from conv1.weight                 of shape (64, 3, 7, 7)
2018-11-29 13:38:21,685 maskrcnn_benchmark.trainer INFO: Start training
Traceback (most recent call last):
  File "relational_rxn_graphs/detector/train.py", line 227, in <module>
    main()
  File "relational_rxn_graphs/detector/train.py", line 220, in main
    model = train(cfg, data_cfg, args.local_rank, args.distributed)
  File "relational_rxn_graphs/detector/train.py", line 71, in train
    arguments,
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/engine/trainer.py", line 66, in do_train
    loss_dict = model(images, targets)
  File "/u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/nn/modules/module.py", line 479, in __call__
    result = self.forward(*input, **kwargs)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/detector/generalized_rcnn.py", line 50, in forward
    proposals, proposal_losses = self.rpn(images, features, targets)
  File "/u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/nn/modules/module.py", line 479, in __call__
    result = self.forward(*input, **kwargs)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/rpn/rpn.py", line 100, in forward
    return self._forward_train(anchors, objectness, rpn_box_regression, targets)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/rpn/rpn.py", line 116, in _forward_train
    anchors, objectness, rpn_box_regression, targets
  File "/u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/nn/modules/module.py", line 479, in __call__
    result = self.forward(*input, **kwargs)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/rpn/inference.py", line 138, in forward
    sampled_boxes.append(self.forward_for_single_feature_map(a, o, b))
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/rpn/inference.py", line 118, in forward_for_single_feature_map
    score_field="objectness",
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/structures/boxlist_ops.py", line 27, in boxlist_nms
    keep = _box_nms(boxes, score, nms_thresh)
RuntimeError: Not compiled with GPU support (nms at /ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/csrc/nms.h:22)
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0xb0 (0x1002eb242d70 in /u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/lib/libc10.so)
frame #1: nms(at::Tensor const&, at::Tensor const&, float) + 0x108 (0x10031db394d8 in /ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-35m-powerpc64le-linux-gnu.so)
frame #2: <unknown function> + 0x1a10c (0x10031db4a10c in /ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-35m-powerpc64le-linux-gnu.so)
frame #3: <unknown function> + 0x163e8 (0x10031db463e8 in /ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-35m-powerpc64le-linux-gnu.so)
<omitting python frames>

the . . . is just the weights being imported and displayed in std out.

we are running against the same error with docker (although it works for me in our cluster)

My environment:
Below Anaconda:
Python: 3.7
Cuda:9.2
Cudnn:7.2
Pytorch:1.0
G++, gcc: 5.5
A lot of modifications have been tried, but mistakes always occur.
run： python tools/train_net.py --config-file "configs/e2e_mask_rcnn_R_50_FPN_1x.yaml" SOLVER.IMS_PER_BATCH 2 SOLVER.BASE_LR 0.0025 SOLVER.MAX_ITER 720000 SOLVER.STEPS "(480000, 640000)"
show：
RuntimeError: Not compiled with GPU support (nms at /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/csrc/nms.h:22)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x45 (0x7fd1fcde78d5 in /home/hjl/anaconda3/envs/maskrcnn/lib/python3.7/site-packages/torch/lib/libc10.so)
frame #1: nms(at::Tensor const&, at::Tensor const&, float) + 0xd4 (0x7fd1f7dc4564 in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so)
frame #2: <unknown function> + 0x15d05 (0x7fd1f7dd0d05 in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so)
frame #3: <unknown function> + 0x15dfe (0x7fd1f7dd0dfe in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so)
frame #4: <unknown function> + 0x12c3e (0x7fd1f7dcdc3e in /home/hjl/PyTorch_MaskRcnn/maskrcnn-benchmark/maskrcnn_benchmark/_C.cpython-37m-x86_64-linux-gnu.so)
<omitting python frames>
frame #63: __libc_start_main + 0xe7 (0x7fd23ded2b97 in /lib/x86_64-linux-gnu/libc.so.6)

I tried to run other pytorch code, CUDA is working

The problem has been solved.
If you use anaconda,  activate envs,
conda install -c pytorch pytorch-nightly cuda92

@Nacho114 is the solution from @HLearning the right one for you?

@Nacho114 is the solution from @HLearning the right one for you?

yes

@Nacho114 one thing to check: verify that the python that you are using to run the python setup.py build develop is the same as the one you are running your scripts
which python

should help you there, as well as the pytorch versions / location in each one of the interpreters

I've tried to be meticulous with witch python I'm using.
So after a clean reinstall of everything I am getting a new error (good!):
2018-12-03 14:19:21,321 maskrcnn_benchmark.trainer INFO: Start training
/ibm/gpfs-homes/ial/.local/tmp_compilation/pytorch-master-at10.0/pytorch/aten/src/THCUNN/ClassNLLCriterion.cu:105: void cunn_ClassNLLCriterion_updateOutput_kernel(Dtype *, Dtype *, Dtype *, long *, Dtype *, int, int, int, int, long) [with Dtype = float, Acctype = float]: block: [0,0,0], thread: [21,0,0] Assertion `t >= 0 && t < n_classes` failed.
Traceback (most recent call last):
  File "relational_rxn_graphs/detector/train.py", line 227, in <module>
    main()
  File "relational_rxn_graphs/detector/train.py", line 220, in main
    model = train(cfg, data_cfg, args.local_rank, args.distributed)
  File "relational_rxn_graphs/detector/train.py", line 71, in train
    arguments,
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/engine/trainer.py", line 66, in do_train
    loss_dict = model(images, targets)
  File "/u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/nn/modules/module.py", line 489, in __call__
    result = self.forward(*input, **kwargs)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/detector/generalized_rcnn.py", line 52, in forward
    x, result, detector_losses = self.roi_heads(features, proposals, targets)
  File "/u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/nn/modules/module.py", line 489, in __call__
    result = self.forward(*input, **kwargs)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/roi_heads/roi_heads.py", line 23, in forward
    x, detections, loss_box = self.box(features, proposals, targets)
  File "/u/ial/.local/deeplearning/pytorch-master/lib64/python3.5/site-packages/torch/nn/modules/module.py", line 489, in __call__
    result = self.forward(*input, **kwargs)
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/roi_heads/box_head/box_head.py", line 55, in forward
    [class_logits], [box_regression]
  File "/ibm/gpfs-homes/ial/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/roi_heads/box_head/loss.py", line 144, in __call__
    sampled_pos_inds_subset = torch.nonzero(labels > 0).squeeze(1)
RuntimeError: copy_if failed to synchronize: device-side assert triggered

At first glance this seems to be a problem on my side, so I will report back if it works after this.

This error is a bug in PyTorch that has normally been fixed with the latest version that is available. Which version of PyTorch are you running?

Hum, weird. I believe this problem should have been fixed with your version of PyTorch.
Can you double check that this is indeed picking this version, and if that's the case open a new issue?
The original issue seems to have been fixed.

Will do, thanks.

Will do, thanks.

Hi, I encountered the same error as you did. I reinstalled everything but had no luck. Then I randomly deleted folder "build/" under the maskrcnn_benchmark and rebuilt the project with setup.py. Now everything works.
This solved my problem. Hope it solve yours too.

Will do, thanks.

Hi, I encountered the same error as you did. I reinstalled everything but had no luck. Then I randomly deleted folder "build/" under the maskrcnn_benchmark and rebuilt the project with setup.py. Now everything works.
This solved my problem. Hope it solve yours too.

Your solution also works for me！@randomwalk10

Will do, thanks.

Hi, I encountered the same error as you did. I reinstalled everything but had no luck. Then I randomly deleted folder "build/" under the maskrcnn_benchmark and rebuilt the project with setup.py. Now everything works.
This solved my problem. Hope it solve yours too.

Your solution also works for me！@randomwalk10

Glad to hear! I guess "python setup.py clean" does NOT clean everything  and  we have to manually delete "build/" in the end LOL.

Just for anybody else creating a docker image of this that runs into this problem -- with an environment with a valid cuda setup that's not being picked up, setting the environment variable FORCE_CUDA to 1 before building/installing the project resolved this issue for me

I run into the problem when using pycharm to debug remotely. And in my case the problem is caused by the file SOURCES.txt under the folder maskrcnn_benchmark.egg-info.

Will do, thanks.

Hi, I encountered the same error as you did. I reinstalled everything but had no luck. Then I randomly deleted folder "build/" under the maskrcnn_benchmark and rebuilt the project with setup.py. Now everything works.
This solved my problem. Hope it solve yours too.

This is right! After re-install the CUDA, we must re-build!

Will do, thanks.

Hi, I encountered the same error as you did. I reinstalled everything but had no luck. Then I randomly deleted folder "build/" under the maskrcnn_benchmark and rebuilt the project with setup.py. Now everything works.
This solved my problem. Hope it solve yours too.

This is right! After re-install the CUDA, we must re-build!
谢谢，英语不好，就用中文了，其实问题去年已经解决了，造成这个问题的原因是，我使用了conda 并且conda 中安装的cuda 和ubuntu 系统中的版本不一致，然而，编绎时，用的系统中的cuda 进行编绎的，而调用时则用的conda 中的cuda ，所以一直无法调用。重装能解决问题也要两个cuda 版本一致才可以

Will do, thanks.

Hi, I encountered the same error as you did. I reinstalled everything but had no luck. Then I randomly deleted folder "build/" under the maskrcnn_benchmark and rebuilt the project with setup.py. Now everything works.
This solved my problem. Hope it solve yours too.

Thanks. Solve my problem too. I also counter the "Not compiled with GPU" problem. Actually I have successfully run the demo before. But later I move the file to another folder. And just following the INSTALL.MD to rebuild it doesn't work.
First I also think the problem originate from CUDA. But after checking my CUDA over and over again, I'm pretty sure it works exatly fine. After seeing your answer, I try to delete the build folder and rebuild it. Then some magic just happens and it works perfectly.
So I guess maybe delete the build folder before rebuilding is pretty important!


Detect .nomad files as filetypes to parse

Hashicorp's Nomad orchestrator commonly uses the filetype .nomad for its files. While the file extension is named differently, these files are in fact HCL files, and it would be great if this plugin detected and parsed .nomad files as well, which it doesn't seem to do now. I think this has already been done for .tf terraform files in this plugin, I get syntax highlighting for those. .tf files are in the exact same position as .nomad files - not named .hcl, but the contents are always HCL.

Hey, this (detection and configuration) is usually handled by the editor. Are you using neovim by chance?

Yes, neovim is what I'm running

Ok then we could probably create a PR to neovim-treesitter to add nomad to https://github.com/nvim-treesitter/nvim-treesitter/blob/d642de92f700c74613977fe6697fb42b299177c9/lua/nvim-treesitter/parsers.lua#L4. That should suffice i think! If not then we would need to set the filetype for .nomad files too. I can try to create a PR over the weekend! One problem could be that the queries are geared to terraform currently but that may be acceptable for now.

You can solve this by following this https://neovim.io/doc/user/filetype.html#new-filetype and adding
au BufRead,BufNewFile *.nomad                set filetype=hcl

to your ~/.config/nvim/ftdetect file


Fix Min-up/down time constraints in UC formulation

We need to round up minimum up/down time requirement to integers.
Would prefer to have this added in PowerSystems parsing checks, rather than in constraint creation
Fixes #124

This is already addressed in #134. Even if the model has a fraction of hour Min-Up Down times this would be relevant for models with sub-hour resolutions. For now, it is ok and just needs to have a warning that UC models only solve for hourly resolution.

LGTM you can merge as soon as the tests pass. We will release as v0.1.1

Codecov Report

Merging #150 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #150      +/-   ##
==========================================
+ Coverage   85.44%   85.46%   +0.01%
==========================================
  Files          44       44
  Lines         907      908       +1
==========================================
+ Hits          775      776       +1
  Misses        132      132

Impacted Files
Coverage Δ

src/devices/device_models/thermal_generation.jl
98.19% <100%> (+0.01%)
:arrow_up:

...vices/device_models/common/duration_constraints.jl
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update Gradient2Limit.java

Fix formula to be in accordance with code

Nice one, I was confused, how the min(0.5, max(1.0, whatever)) could ever make sense.

@guohao  Thanks for the doc fix.


Multi Node Transaction Creation

Problem
Within the transaction creation screen, the Submit to node field only accepts a single entry. This requires the re-entry of all transaction details to create a transaction that should be submitted to multiple nodes.
Solution
Update the Submit to node field to accept multiple entries and when the CREATE AND EXPORT button is pressed it should create a transaction for each node listed in the Submit to node field.
Alternatives
No response

Revisit if this is a relatively easy feature add.


CodeSystem resource lookup results in search even though the resource is available from other resource providers

Describe the bug
When testing update-as-create using an Observation resource, processing search parameters results in search queries executed by the persistence layer to resolve CodeSystem resource lookups:
[18/10/2021, 11:02:29:395 UTC] 00000030 FHIRPersisten 1   Processing SearchParameter resource: Observation, code: code, type: token, expression: AllergyIntolerance.code | AllergyIntolerance.reaction.substance | Condition.code | (DeviceRequest.code as CodeableConcept) | DiagnosticReport.code | FamilyMemberHistory.condition.code | List.code | Medication.code | (MedicationAdministration.medication as CodeableConcept) | (MedicationDispense.medication as CodeableConcept) | (MedicationRequest.medication as CodeableConcept) | (MedicationStatement.medication as CodeableConcept) | Observation.code | Procedure.code | ServiceRequest.code

Results in the following query:
[18/10/2021, 11:02:30:429 UTC] 00000030 QueryUtil     1        query string:
      SELECT COUNT(*) AS CNT
        FROM CodeSystem_LOGICAL_RESOURCES AS LR0
       WHERE LR0.IS_DELETED = 'N'
         AND EXISTS (
      SELECT 1
        FROM CodeSystem_LOGICAL_RESOURCES AS LR1
  INNER JOIN CodeSystem_STR_VALUES AS P2 ON P2.LOGICAL_RESOURCE_ID = LR1.LOGICAL_RESOURCE_ID
         AND P2.PARAMETER_NAME_ID = 20764
         AND (P2.STR_VALUE = ?)
       WHERE LR1.LOGICAL_RESOURCE_ID = LR0.LOGICAL_RESOURCE_ID)

In this case the search is for bindString(1, 'http://snomed.info/sct')
If we try the lookup directly from the registry, we see it is successful:
CodeSystem snomed =
                FHIRRegistry.getInstance().getResource("http://snomed.info/sct", CodeSystem.class);
        assertNotNull(snomed);

but we still drop through to the persistence layer to perform a search, which slows down ingestion considerably.
Environment
4.10.0
To Reproduce
Ingest an Observation resource with a code value like:
   "code": {
        "coding": [{
            "system": "http://snomed.info/sct",
            "code": "363779003",
            "display": "Genotype determination"
        }],
        "text": "Diplotype Call"
    },

Expected behavior
When the serverRegistryResourceProviderEnabled is true, the registry lookup should be sufficient and no search query is needed.
Additional context
This needs to be addressed before any further performance measurement work is done.

In the case of SNOMED, we do cache the result, although by default the time-to-live is very short. Need to see cache statistics in real-world scenarios to understand the performance impact. Without that insight, it's difficult to assess the real priority for this issue.

With the caching thats in place, we should only pay this cost when the cache is stale.
I think its working as designed, although there is work that could be done to change/control the ordering for the RegistryResourceProviders.


Is RexRay actively maintained?

Summary
As I don't see any activity since January 2019 on this repository, I'm wandering if the project is still maintained. My use case is the integration with open-source DC/OS external persistent storage.
Will new features be added?
Will new bugs be fixed?
The question is mainly for the the vmware Rex-Ray project maintainers: @codenrhoden @akutz @clintkitson

Hello Catalin,
Have you looked at CSI? CSI was introduced a couple of years ago and is the
focus of numerous storage providers for interop with K8s/Mesos. Generally,
community PRs are welcome across the repo and releases are as needed at
this point. Our focus is on parts of REX-Ray such as the gocsi library.
On Mon, Oct 28, 2019 at 1:19 AM Catalin Jora<EMAIL_ADDRESS>wrote:

Summary
As I don't see any activity since January 2019 on this repository, I'm
wandering if the project is still maintained. My use case is the
integration with open-source DC/OS external persistent storage
https://docs.d2iq.com/mesosphere/dcos/1.12/storage/external-storage/.
Will new feature be added?
Will new bug be fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rexray/rexray/issues/1338?email_source=notifications&email_token=AAKUYMIXH2E2PO6K5AKFSELQQ2OC5A5CNFSM4JFW3ZB2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HUWFR6A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKUYMN7O5PXMCV42ENQLPLQQ2OC5ANCNFSM4JFW3ZBQ
.

Sigh.  Literally went live with this solution last December for a large open source project.  I ended up scaling it back due to #1331  glad I did :-|
Anyone interested in forking / maintaining or taking over the project from the original author? (if you can find them)

Sorry for this @kallisti5. If there are community members that are interested in maintaining please do let me know.

@kallisti5 what did you use instead?
@clintkitson I would love to help but don't even know what language rexray is written in :/ Looks like you are the last "active" maintainer of this repo, is that correct?

@clintkitson I'm willing to help maintain this project. Kinda sucks most of the CSI available implementations are done mostly for k8s and e.g. in case of AWS ECS we have to use RexRay for ECS <-> EBS integration, so RexRay is great here.

Glad to hear you're making use of it @Trojan295. Do you have any thoughts about the direction you would want to take the project?

If the rexray maintainers are willing to give up control that would be useful, otherwise a fork wouldn't be a bad idea. It's a shame how projects like these get abandoned... probably just the company shifting priorities but still... at the very least hand it over to someone that cares

@clintkitson Given the lack of clear direction from Mirantis and the closed sourcing/deletion of CloudStor documentation I'd really like to see this pick up as it is the only remaining solution for Docker Swarm (especially for AWS and OpenStack).
If there are some people interested i'd love to see a group start picking this back up. Some ideas i've had:

Cleanup and Close existing PR's
Stand up community resources
Work to implement/refactor both Rexray and it's documentation to highlight it's use as a "native" CSI solution/bridge for Swarm

I have my own fork that brings in several PR's for and a few of my own fixes for the OpenStack Cinder but I'd be happy to work with a few folks bring them and many of the others in. I've noticed that the community (especially the Swarm community) is starting to just take for granted that we are "second-string" despite the fact that most of us are firm believers that it is a better solution (for us anyway) than K8s, mesos etc. I have experienced what Mirantis support looks like, (at least in the short term) and if we want to save Swarm we are going to have to do it ourselves.
/rallycry

@Enquier yes please. We make use of docker in swarm mode extensively using Caprover and have now reached the point where we really need swarm mode data persistence, which we planned to achieve using Rexray/s3fs.

I am open to having a community Zoom call to further discuss. Please thumbs
up if you would attend and reply if there are any special considerations
for time etc.
On Thu, Jul 9, 2020 at 2:07 AM Floris van Lint<EMAIL_ADDRESS>wrote:

@Enquier https://github.com/Enquier yes please. We make use of docker
in swarm mode extensively using Caprover
https://github.com/caprover/caprover and have now reached the point
where we really need swarm mode data persistence, which we planned to
achieve using Rexray/s3fs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rexray/rexray/issues/1338#issuecomment-656008697, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKUYMNLCDP63TCPQWY7FX3R2WCGTANCNFSM4JFW3ZBQ
.

@Enquier @clintkitson I am willing to throw my hat in to help with keeping this project going.
I'm actually using the Hashicorp Nomad Orchestrator on Openstack and this projects Cinder Docker Volume Plugin makes life so much easier.
Yeah, Nomad is slowly adding CSI support but, even though it's supposed to be a "platform agnostic" specification, I have yet to come across a single CSI driver that documents its deployment process.
The docker volume plugins however are truly orchestrator agnostic and it took me about 3 minutes to find the information I needed to install/configure the plugin and have migratable persistant storage across my cluster.
@Enquier Can you share what fixes you made in the cinder driver (as mentioned before, this is what i'm using Rexray for)? I started digging into the Cinder driver to look into adding Application Credentials support but was curious if that may have been one of the things you worked on in your own fork?

@cPanelRicky Check-out logitainer/rexray I wasn't sure if @clintkitson was more interested in handing off or starting a fork so I moved mine over to that as a starting point

@Enquier Perfect, appreciate it!
I started attempting to migrate over to Go modules as well but found that there are going to be some modules that have become incompatible over the last year or so (mainly the Gophercloud module) so that's gonna take some work to get fixed up.

@Enquier  Yoo hello, Im interested, Im building a PoC using Docker Swarm and I was searching for a persistent storage solution until the algorithm showed me this repository
where can I found a list of issues we should solve? how should we prioritize them?
Because I read that some people are using OpenStack, others DigitalOcean, and I was looking to use another provider which is not listed (I would write the code for it so no worries), but would rather write that later, I think there are more important issues like the guy hitting the api limits on DigitalOcean (which probably will apply to another cloud providers)

So @Enquier how did this turn out? I'm looking at logitainer/rexray and it look stalled :(
I'm looking for a good storage solution for Swarm.

I have the same issue @jostmart. Running a swarm cluster with nodes on VMWare platform. We sadly can't use the VSFD plugin : https://github.com/vmware-archive/vsphere-storage-for-docker.
I'm in need of a storage provider that can use vSphere as a provider.
Has anyone tried to create a vSphere provider for REX-Ray ?

Apparently, VMware maintains this.
https://blogs.vmware.com/cloudnative/2018/06/22/rex-ray-persists-your-questions-answered/

Is REX-Ray still being maintained?  A: Yes, by VMware.

Apparently, VMware maintains this.
https://blogs.vmware.com/cloudnative/2018/06/22/rex-ray-persists-your-questions-answered/

Q. Is REX-Ray still being maintained?  A: Yes, by VMware.

Q. To what extent is VMware maintaining REX-Ray? A: VMware has committed multiple open-source engineers to REX-Ray.

Q. I’ve been a part of the REX-Ray community for a long time, where should I go for continued support and collaboration?

A: The REX-Ray GitHub repository.

That's quite unexpected. But cool!

Note that blog post is nearly two years old. I’m fairly certain that VMWare
has since created a separate CSI based plugin elsewhere.
On Sat, Oct 24, 2020 at 06:40 Floris van Lint<EMAIL_ADDRESS>wrote:

Apparently, VMware maintains this.
https://blogs.vmware.com/cloudnative/2018/06/22/rex-ray-persists-your-questions-answered/
Q. Is REX-Ray still being maintained? A: Yes, by VMware.
Q. To what extent is VMware maintaining REX-Ray? A: VMware has committed
multiple open-source engineers to REX-Ray.
Q. I’ve been a part of the REX-Ray community for a long time, where should
I go for continued support and collaboration?
A: The REX-Ray GitHub repository.
That's quite unexpected. But cool!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rexray/rexray/issues/1338#issuecomment-715909239, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNEWT6FW6R6O4Y425FU7K3SMLDKZANCNFSM4JFW3ZBQ
.

--
-Chas

So @Enquier how did this turn out? I'm looking at logitainer/rexray and it look stalled :(
I'm looking for a good storage solution for Swarm. My platform is Vmware Simplivity and I can't see any support for it.

It’s still there. It’s still my intention that it be maintained but I was looking for a signal one way or the other from the original team.
It seems to me the most valuable piece here is maintaining the CSI compatible interface for swarm and that should allow other CSI plug-ins for K8s PV to work for swarm. So factoring that out and then identifying working solutions from other sources seems to be the right approach

I’m fairly certain that VMWare has since created a separate CSI based plugin elsewhere.

Yes but VMWare gave a commitment to the Open Source community. Therefore they are obliged to ensure the project is maintained (nobody is asking for new features, just bugs fixed, maintenance releases and commitment adhered to).

I’d appreciate any support from VMware but at this point all of us using non K8 solutions are on our own.
So, I’ve expressed willingness to start working the crank. I have a solution that works for me over at logitainer/rexray and other than working to add native efs support I don’t have a clear feature path. I’d like to start by getting some of the PR’s closed out. So I would put out a call to anyone who made a PR to clean them up and reprise them in Logitainer and we can start to triage them. We will need to sort out the build pipelines from there

Hello, I saddened to see the status of this project 😢 .
I come here because I just ran into an issue with the dobs integration. I looked at the code and opened a PR only to 5 minutes later realize that someone else had opened another PR for the same issue with a very similar solution. Would it be possible to merge it? https://github.com/rexray/rexray/pull/1344
Also, I've tried building the project locally but I'm unable to do it. Help?

I’m fairly certain that VMWare has since created a separate CSI based plugin elsewhere.

Yes but VMWare gave a commitment to the Open Source community. Therefore they are obliged to ensure the project is maintained (nobody is asking for new features, just bugs fixed, maintenance releases and commitment adhered to).

No, they are not obliged to do anything. Making software Opensource does not mean there is a contract to maintain or even pay attention to your issues, you are however free to ignore certain contributors or companies in the future. Depending on the Opensource license you are however free to fork the project and run it as your own.

@clintkitson the website and installer are offline as bintray.com is EOL.  Any chance this could be resolved?

is it possible to build and host the binaries in github releases instead of bintray ?  Since rexray provided instruction to build the go binaries, that isn't difficult to do.  I believe many people are getting Forbidden when they reach out to bintray.com

I've had very poor experiences with Rexray in the past and do not recommend it.  Rclone offers a much better (maintained!) volume driver for Docker Swarm: https://rclone.org/docker/
Have been using this volume driver in production with no issues for well over a year.

Is there an alternative to using Rexray?

Is there an alternative to using Rexray?

We moved to https://github.com/sapk/docker-volume-rclone first, then later migrated our entire Docker Swarm setup to https://github.com/rancher/rancher with https://github.com/longhorn/longhorn, but there is an rclone-CSI as well https://github.com/wunderio/csi-rclone

I have only started to have this problem today in one of my environments.... Am I the only one?

any of these support EBS? (https://github.com/rexray/rexray/issues/1282#issuecomment-1600973555)

@bram-tv,
My fork was pretty recently updated for newer toolchain and library dependencies based on govulncheck (purely a compliance measure - I doubt anything was ever exploitable in something like this, but we like to play it safe). I'd have to check, but this was just a couple weeks ago so it should still be clean per govulncheck.
However I've just recently moved on from the employer where that work was performed and I've not currently got access to any AWS test systems. I'd be willing to keep merging toolchain and dependency updates (this is only a few minutes of work every few weeks) but will not be able to test them unless things change. It might be time to see if anyone else is interested in keeping this project fresh.
Also, I don't know who runlo is. Looks like somebody building their own image from my fork.

@bram-tv, my process had been:

Commit dependency and toolchain updates as needed (plus the occasional random bugfix)
Push that code to my active branch (revert-1345) in the fork
Build EBS driver image and push to the latest tag in the repo I was managing
If this seems to work fine (as in, it's mounting volumes successfully--just basic testing really), re-push to the stable tag


[Bug]: Delete selected files

What happened?
Hi, I know that it's not the repo where the dashboard is deployed, but I found a strange bug.
When I select multiple files, it doesn’t let me delete them (just works if I delete them separately).
Also after I delete them separately, the button has some bug...

What did you expect to happen?
Let me delete multiple files at once
Version
3.0.5
Reproduction Steps

have more than 1 file.
select multiple files and press the "Delete selected" button.

Reproduction Repository
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I have a PR up right now that makes a lot of changes to the files table, which should hopefully fix this as well. Hoping to get that merged today or tomorrow!

Thank you!


Dash 8 Map please?

I really want to make Dash 8 liveries but I can't find the map. Maybe because I'm just lazy to find or they didn't send the aircraft map. Can someone send me the image or link??

Dash8 is still in development, I'm trying to figure out how to recolor the top of the vertical stab. Until that you can try to repaint this texture, but I don't know yet when will it be avaliable in the addon.
https://www.geo-fs.com/backend/aircraft/repository/E01_166635_247/texture.png

thx so much i'll ad the dash 8 to my addon

thanks :D

i just made new flybe


[BUG] bug The task instance log shows failure, but the status shows success without alarm

*For better global communication, please give priority to using English description, thx! *
Describe the bug
The task instance log shows failure, but the status shows success without alarm

To Reproduce
Steps to reproduce the behavior, for example:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Which version of Dolphin Scheduler:
-[1.1.0-preview]
Additional context
Add any other context about the problem here.
**Requirement or improvement

Please describe about your requirements or improvement suggestions.

which soft dose the first screenshot use ?

which soft dose the first screenshot use ?

WeChat, corporate WeChat can be？

Close the issue since no updates for long long time


please add babel-runtime as a prod dependency

Hi @dotneet!
We recently had a security audit at my company -- and it was discovered that the NPM module babel-runtime is actually needed for chromy at runtime.  This dependency is added by Babel during build and required by babel for runtime polyfills.  In most installation cases this works fine since other packages already declare this package implicitly -- but for chromy to pass our validation it needs to explicitly declare this runtime library in chromy's package.json   (it must be under dependencies not devDependencies)
Would it be possible to declare this dependency?
I will try to create a PR to make it easier.
Cheers.

Hi @garris!
It's ok. I'll wait your PR.

I've published v0.5.5. please check it!

Ok. we are finally checking this on our infrastructure today.  Will follow up soon.

Worked in prod!   This is great!   Closing.


Configmap for configuiring redis

as a promised to do a PR in https://github.com/AmadeusITGroup/Redis-Operator/pull/22

Codecov Report

Merging #23 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
- Coverage   37.08%   37.02%   -0.06%
==========================================
  Files          37       37
  Lines        3422     3422
==========================================
- Hits         1269     1267       -2
- Misses       2036     2037       +1
- Partials      117      118       +1

Impacted Files
Coverage Δ

pkg/controller/clustering/cluster-placement.go
58.53% <0%> (-1.63%)
:arrow_down:

Continue to review full report at Codecov.

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


Symtab output should be suppressed on success

This was the previous behavior but was likely broken in:

#1686

Presently we emit too much nuisance output.

This is way too annoying... I'll fix it