typescript.Symbol["valueDeclaration"] is possibly undefined

Abstract
The Symbol type includes a valueDeclaration member that returns the AST node the symbol corresponds to.

typescript.d.ts

https://github.com/microsoft/TypeScript/blob/master/lib/typescript.d.ts#L2264
    export interface Symbol {
        flags: SymbolFlags;
        escapedName: __String;
        declarations: Declaration[];
        valueDeclaration: Declaration;
        members?: SymbolTable;
        exports?: SymbolTable;
        globalExports?: SymbolTable;
    }

This member is vital for using the compiler API as, when printing e.g. documentation it's necessary to access raw AST data for pretty printing.
The compiler API example uses itself for this purpose.

Compiler API Example

https://github.com/microsoft/TypeScript/wiki/Using-the-Compiler-API#using-the-type-checker
  /** Serialize a symbol into a json object */
  function serializeSymbol(symbol: ts.Symbol): DocEntry {
    return {
      name: symbol.getName(),
      documentation: ts.displayPartsToString(symbol.getDocumentationComment(checker)),
      type: checker.typeToString(
        checker.getTypeOfSymbolAtLocation(symbol, symbol.valueDeclaration!)
      )
    };
  }

However, valueDeclaration, is, in various cases, undefined, resulting in run-time errors.

Testing
https://github.com/Zemnmez/ts-issue-valuedeclaration/blob/master/repl.ts
import * as ts from "typescript";

const p = ts.createProgram(["t.d.ts"], {});
const c = p.getTypeChecker();
p.getSourceFiles().map(f => {
    f.forEachChild(n => {
        if (!ts.isModuleDeclaration(n)) return;
        const s = c.getSymbolAtLocation(n.name);
        if (!s) return;

        const scanMembers = (s: ts.Symbol) => {
            if (s.valueDeclaration === undefined)
                console.log("missing valueDeclaration on", s.getName());
            if (!s.exports) return;
            if (!(Symbol.iterator in s.exports))
                return console.log("not iterable", s.getName())
            for (let [/*name*/, member] of (s.exports as Map<ts.__String, ts.Symbol>)) {
                scanMembers(member);
            }
        }

        scanMembers(s);

    })
})

thomas@soliloquy:/mnt/c/Users/thoma/Documents/devel/typescript-bug$ yarn start
yarn run v1.19.1
$ yarn tsc && yarn node repl.js
$ /mnt/c/Users/thoma/Documents/devel/typescript-bug/node_modules/.bin/tsc
missing valueDeclaration on CollatorOptions
missing valueDeclaration on ResolvedCollatorOptions
missing valueDeclaration on NumberFormatOptions
missing valueDeclaration on ResolvedNumberFormatOptions
missing valueDeclaration on DateTimeFormatOptions
missing valueDeclaration on ResolvedDateTimeFormatOptions
missing valueDeclaration on GlobalDescriptor
missing valueDeclaration on MemoryDescriptor
missing valueDeclaration on ModuleExportDescriptor
missing valueDeclaration on ModuleImportDescriptor
missing valueDeclaration on TableDescriptor
missing valueDeclaration on WebAssemblyInstantiatedSource
missing valueDeclaration on ImportExportKind
missing valueDeclaration on TableKind
missing valueDeclaration on ValueType
missing valueDeclaration on ExportValue
missing valueDeclaration on Exports
missing valueDeclaration on ImportValue
missing valueDeclaration on ModuleImports
missing valueDeclaration on Imports
missing valueDeclaration on abcdtest123
missing valueDeclaration on p
missing valueDeclaration on m
Done in 2.50s.

That in the compiler API example the ! operator is used seems to indicate to me that at some point valueDeclaration was defined to be possibly undefined, but it was changed.

Compiler API example snippet
   // Get the construct signatures
    let constructorType = checker.getTypeOfSymbolAtLocation(
      symbol,
      symbol.valueDeclaration!
    );

TypeScript Version:  3.7.3

Search Terms:
valueDeclaration undefined
Code
https://github.com/Zemnmez/ts-issue-valuedeclaration/blob/master/repl.ts
import * as ts from "typescript";

const p = ts.createProgram(["t.d.ts"], {});
const c = p.getTypeChecker();
p.getSourceFiles().map(f => {
    f.forEachChild(n => {
        if (!ts.isModuleDeclaration(n)) return;
        const s = c.getSymbolAtLocation(n.name);
        if (!s) return;

        const scanMembers = (s: ts.Symbol) => {
            if (s.valueDeclaration === undefined)
                console.log("missing valueDeclaration on", s.getName());
            if (!s.exports) return;
            if (!(Symbol.iterator in s.exports))
                return console.log("not iterable", s.getName())
            for (let [/*name*/, member] of (s.exports as Map<ts.__String, ts.Symbol>)) {
                scanMembers(member);
            }
        }

        scanMembers(s);
    })
})

Expected behavior:
The valueDeclaration member of typescript.Symbol should never be undefined.
Actual behavior:
Many Symbols have undefined valueDeclaration.

Duplicate #24706


@damassi => Redux-backed commercial filtering

Mostly PR-ing this for my own benefit right now (and there's a merge conflict anyways). I have some open questions on how we want to structure/style this going forward, but felt it was easiest to put all the code out there for reference.
So far, redux is 👌 .

TODO (Before merging):

[ ] Tests!

TODO (UI things-- after this PR):

[ ] Implement infinite scroll
[ ] Make jumping behavior only go to top of commercial filter section
[ ] Make sort box adjust based on index of selection
[ ] Add URL handling for default params

We need to add linking to force!
On Tue, Mar 7, 2017 at 7:39 PM Alan Johnson<EMAIL_ADDRESS>wrote:

@acjay commented on this pull request.
In desktop/apps/auction2/reducers.js
https://github.com/artsy/force/pull/982#discussion_r104838022:

   }

 }, state)

} else if (contains(state.filterParams.artist_ids, artistId)) {

 return u({

   filterParams: {

     artist_ids: u.reject((aa) => { return aa == artistId })

   }

 }, state)

} else {

 return u({

   filterParams: {

     artist_ids: state.filterParams.artist_ids.concat(artistId)

   }

 }, state)

}
case actions.UPDATE_MEDIUM_ID:

Do we have a linter config that can protect us from this?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/artsy/force/pull/982#discussion_r104838022, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAOdj5g7TUryx0IxtNTx31GsASQofl7Mks5rjiLwgaJpZM4MWLnR
.

🍏

Looks really good, and super fast work 👍


Change to multi module setup

Situation
The cloud-storage-etl-udfs contains different features such importing/exporting
from cloud storage systems, importing from streaming services Apache Kafka and
AWS Kinesis. However, at the moment we are building a single artifact for all of
them.
Split the project into modules so that each of them can be released and used
independently.
Acceptance Criteria

It is split into different modules: common, storage, streaming-kafka, and
streaming-kinesis.
All unit tests and integration tests pass in the new setup.

Fixed in #85.


Update RAP implementation

This PR introduces updated RAP implementation. To make the RAP fully adaptive, attention mechanism and indexing are needed. Other that that, method should work without any issues.

Thank you so much, @ghkim9213 . I will try to fix the heatmaps to be the same. I have also similar results. I looked into inception v3. The issue is related to index method in preprocessing step of the model, e.g. a[:, 0]

I tested implementation of original RAP package, and it produces similar random results on resnet18

I am not sure about the reason behind such behavior. Authors test correctness of explanations by comparing sums of prediction logits and relevances. I conducted the same test on this implementation version. The results are as follows:
Pred logit : 31.355219
Relevance Sum : 31.355202
Pred logit : 14.111381
Relevance Sum : 14.111369
Pred logit : 16.852928
Relevance Sum : 16.85293
Pred logit : 20.30917
Relevance Sum : 20.309172
Pred logit : 12.61315
Relevance Sum : 12.613142

One more issue, I found during the test is that Pred logit and Relevance Sum values do not match when tensor is batched. However, as it can be seen by the results above, values match, when processed one-by-one.
I will investigate further, just wanted to share the results of my findings.

The last commit fixed an issue with multiple items in a batch

I tested implementation of original RAP package, and it produces similar random results on resnet18

I am not sure about the reason behind such behavior. Authors test correctness of explanations by comparing sums of prediction logits and relevances. I conducted the same test on this implementation version. The results are as follows:
Pred logit : 31.355219
Relevance Sum : 31.355202
Pred logit : 14.111381
Relevance Sum : 14.111369
Pred logit : 16.852928
Relevance Sum : 16.85293
Pred logit : 20.30917
Relevance Sum : 20.309172
Pred logit : 12.61315
Relevance Sum : 12.613142

One more issue, I found during the test is that Pred logit and Relevance Sum values do not match when tensor is batched. However, as it can be seen by the results above, values match, when processed one-by-one.
I will investigate further, just wanted to share the results of my findings.

Same issues of the original package on my env. Just for informing.

tench-vgg

tench-resnet18

tench-resnet50

I guess the author failed to process relevance for the residual connection for the torch model. In the paper, they said they use keras model instead of torch one.
https://github.com/wjNam/Relative_Attributing_Propagation/issues/6

If you do not mind, I will merge existing work to the main, so that we had functioning RAP for now. We can update it, when all issues a resolved.

For some reason applying relu before adding block improves explanation quality substantially


docs: Various issues related to V2 docs

From @cfjedimaster on February 10, 2016 20:33
Type: docs
Ionic Version: 2.x
Platform: all
I created a Gist of my issues:
https://gist.github.com/cfjedimaster/ab78eb3e0adbef982098

Copied from original issue: driftyco/ionic#5398

done


iplBinauralEffectApply always outputs silence on armv8

System Information
Please provide the following information about your system:

Steam Audio version: 4.5.2
Device: Quest 3

Issue Description
Passing valid audio samples (duplexed microphone) to iplBinauralEffectApply always outputs silence, even when spatialBlend is set to 0.0, which should just be a passthrough (nvm, mono input doesn't trigger this).
Steps To Reproduce
Steps to reproduce the behavior:

Create context, default hrtf, binaural effect, mono input, stereo output buffers
In audio callback, read samples into input
Invoke iplBinauralEffectApply with the hrtf.
Manually / otherwise deinterleave into the output buffer

The result is silence (validated programmatically, all samples precisely 0.0). Params are as follows:
IPLBinauralEffectParams params = {
        .direction = { 1.0f, 0.0f, 0.0f },
        .interpolation = IPL_HRTFINTERPOLATION_NEAREST,
        .spatialBlend = 1.0f, // or any value
        .hrtf = ipl_hrtf, // Default hrtf
        .peakDelays = NULL,
};

The issue was caused by incorrect usage of the API in the official documentation.

No volume field is being set here, it needs to be set to 1.0 otherwise the stream will just output silence (I don't remember that field last time I used SteamAudio). Leaving the issue open as this is a documentation bug.

Should have been fixed? https://github.com/ValveSoftware/steam-audio/pull/309

@cshenton This documentation issue was fixed in #309, so I'm closing this issue.

@lakulish
I think the issue is that it was not reflected on github pages doc

Yes, on several different pages on the github pages documentation the incorrect usage is shown. This is what I was referring to.

The documentation in the gh-pages branch will be updated when the next official release is made, which I plan to do soon.


paper link

Hi, has the article been released?

Thank you for your attention of my work! Our camera-ready paper is under revision by the official IJCAI proceeding.  If appropriate, we will release as soon as possible.

Thank you for your attention of my work again! This paper is available at https://www.ijcai.org/proceedings/2021/0168.pdf.


[Wikipedia] ...

Extension
https://www.raycast.com/vimtor/wikipedia
Description
Add Italian language, please! 🙏
Who will benefit from this feature?
Italian users.
Anything else?
No response

@andreaguida adding now

@NikosEfthias Great! Thanks!!! 😊

@raycastbot close this issue

the pr has been merged i think this issue can be closed now

@raycastbot close this issue


[Bug]Creative Empties Reinforced Shulker Inventories

Describe the bug
A clear and concise description of what the bug is:  When in creative mode any interaction with a reinforced shulker box will cause the shulker to “return” empty when dropped.
To Reproduce
Steps to reproduce the behavior:

Open an already placed shulker with items in it while in creative
Then break said shulker and when you view it in your inventory it reads “Empty”
Then when placed, it is indeed empty. Further, one doesn’t even have to open or view the shulker as this will happen even when moving a shulker from say a chest to an ender chest.

Expected behavior
A clear and concise description of what you expected to happen: I would expect no item loss during interactions with reinforced shulker boxes while in creative
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Minecraft: [e.g. 1.16.5]
Fabric Loader: [e.g. 0.11.1]
Fabric API: [e.g. 0.29.4+1.16]

Logs
Pastebin the log [e.g. logs/latest.log] and link it below:

Additional context
Add any other context about the problem here.

Hmmm, I tried the steps to reproduce but no bugs occurred.
Although I have developed this mod while paying attention to the creative behavior, I don't remember occurring it.
Can you tell me your environment?
e.g. the mod version, any other mods you have installed (if you have)

Hello!
Thank you for the reply. I did some initial troubleshooting before reporting here, however it went like this:
1 - I uninstalled everything except the reinforced mods
2 - I checked creative mode - no issues worked as expected
3 - One by one I reinstalled each mod until creative mode "broke" the boxes again
4 - ShulkerBoxToolTip seemed to be the culprit, so I uninstalled it and tried Quick Shulkers - which also caused the same issue
5 - I uninstalled Quick Shulkers and tried MiniHud's and Tweakeroo's version of shulker preview - same issue ocured with both
6 - I gave up and submitted this bug report
I run a server for my family of four on Apex hosting running Fabric 1.18.1
We have the following mods installed:

appleskin-fabric-mc1.18.1-2.3.0
Cardboard-1.17-1.18
deepslatecutting-1.18.1-1.3.1
easy-auto-crafting-1.1+1.18
elytratrinket-fabric-3.0.0-1.18.1
enderite-reinforced-storage-1.0.0beta.1+1.18
enderitemc-enderitemod-1.3.3-1.18.1
fabric-api-0.46.4+1.18
iCommon-Fabric-1.18
InventoryProfilesNext-fabric-<IP_ADDRESS>.4
itemscroller-fabric-1.18.1-0.15.0
linkedstorage-<IP_ADDRESS>
lithium-fabric-mc1.18.1-0.7.8
malilib-fabric-1.18.1-0.11.7
minihud-fabric-1.18.1-0.21.3
pigemb-fabric-1.18.1-1.0
reinforced-barrels-2.0.0-beta.1+1.18
reinforced-chest-2.0.0-beta.2+1.18
reinforced-shulker-boxes-2.0.0-beta.2+1.18
shulkerboxtooltip-3.0.5+1.18
trinketofundying-fabric-2.0.1-1.18
trinkets-3.2.0
tweakeroo-fabric-1.18.1-0.12.3
upgradedechests-1.0.3-1.18
Xaeros_Minimap_<IP_ADDRESS>_Fabric_1.18
XaerosWorldMap_<IP_ADDRESS>_Fabric_1.18

We use Cardboard and its companion iCommon to run some Paper plug-ins for a home system through BareEssentials and LuckPerms. I tested with just those installed with the reinforced storage mods and it worked as expected, so I don't believe the issue lies there. I truly believe the issue rests with attempting some sort of "tooltip" pull/refresh.  For example, while in creative, I placed an empty netherite shulker then grabbed two stacks of random stone and tossed those in. I broke the shulker and it dropped - indicating it had items in the shulker. I picked it up and the dropped shulker entity went to a different inventory slot than the shulker I used to placed the dropped shulker entity. However, when I hovered over the shulker I just picked up, it returned the tooltip message of "Empty" and upon placing it again, it was indeed empty.
Thank you in advanced for looking into this. I truly appreciate your time and effort!
Let me know if you need any additional information and best of luck in solving this issue.

Logs-224FEB2022.zip
Mods-24FEB2022.zip
P.S. I zipped my logs and mods folder and attached them for your reference so you know exactly what we have.

Correct, vanilla shulkers do not have this issue. Thanks, again!

Though I tried single play with your mod configuration, it seemed no bugs occurred. So is there a bug in the server?
Since I'm not familiar with apex hosting and with plugin servers like Bukkit, Spigot, Sponge, or Paper, the reproduction may take some time.
Then, I fixed another bug in the reinforced shulker boxes.

Reinforced Shulker Boxes v2.0.0-beta.3 for 1.18-1.18.1
Enderite Reinforced Storage v1.0.0-beta.2 for 1.18-1.18.1

It may not be related to this bug, but I'll let you know.

Oops, I was able to reproduce it.
And if disabled Cardboard, the bug was fixed.
When I enabled Cardboard with/without the plugin, it happened again.
So probably caused by Cardboard.

I don't know well what they are doing, but it seems they are tweaking the vanilla shulker box (links below).

https://github.com/CardboardPowered/cardboard/blob/cf723e3c7f50186c5a4bbe4920a0594201d92eb7/src/main/java/org/bukkit/craftbukkit/block/CraftBlock.java#L360-L377
https://github.com/CardboardPowered/cardboard/blob/cf723e3c7f50186c5a4bbe4920a0594201d92eb7/src/main/java/org/bukkit/craftbukkit/inventory/CraftMetaBlockState.java#L260-L277

I hypothesize it was empty because the reinforced shulker box hasn't been tweaked by them.

Thanks for the update. I will try your beta versions and see what I can do about Cardboard.  Do you know about a good home system for Fabric?

I tested it (with Cardboard still installed) and the new version did not fix the issue.

Do you know about a good home system for Fabric?

No, I don't...

I tested it (with Cardboard still installed) and the new version did not fix the issue.

Yes, if my hypothesis is correct, unfortunately, I can't fix this bug. This is a Cardboard issue.
Cardboard targets only vanilla shulker boxes, so this bug probably happens not only with my mods but also with other shulker box mods.
In fact, I reproduced the same issue with endritemod's shulker box and Kyrptonaught's Upgraded Shulkers.

Thank you for your help with this.  I truly appreciate your effort.  I've decided to abandon Cardboard at this time. I believe it is causing us other issues as well. If you would like, you may mark this issue as closed/resolved.  Thanks again!


I need a way to avoid passport policies of sails permissions, if exists an attribute public true in some model

Hi. currently, I defined my policies like this:
module.exports.policies = {
  '*': [
  'basicAuth',
  'passport',
  'sessionAuth',
  'ModelPolicy',
  'AuditPolicy',
  'OwnerPolicy',
  'PermissionPolicy',
  'RolePolicy',
  'CriteriaPolicy'
  ],

  AuthController: {
  '*': ['passport']
  },
  UserController: {
  'create': true
  },
  ClassController: {
  },
  CardController: {
  'create' : 'isOwnerClass'
  }
};

and I need to find ways to avoid even the policie of authentication, if I define as True, the attribute public of my model Class.
sorry for my bad english, thankful in advance

and I need to find ways to avoid even the policie of authentication, if I define as True, the attribute public of my model Class.

Your policies config looks fine; I don't quite understand what you're trying to achieve. Can you try to explain again?
Also, see: https://github.com/tjwebb/sails-permissions/issues/200

@robertoandres24 TJ has been posting that issue around to let people know he's no longer going to be maintaining sails-permissions, but just want to clarify -- that repo is his personal project and doesn't impact sails core, so that issue should only affect you if you are using tjwebb/sails-permissions

I would avoid Passport altogether as I have had too many issues with integrations and Express dependencies. @robertoandres24 what is the "real" auth issue that is causing a problem for you? Perhaps our creative minds can give you a reasonable solution.

@crh3675 wonderful advice.  Nothing against passport-- I've just found it's easier in reality to use policies and the session directly.
@robertoandres24 for some conceptual background, you might check out https://github.com/sails101/basic-login

@robertoandres24 by the way, in case this helps: for your particular use case here, I'd recommend writing a custom action.
If you could use some help getting going with that, beyond the tutorial in the repo I linked to above, you might also find Irl's Activity Overlord 2.0 series useful.  If you're more in the mood for a longer-form tutorial, also be sure and check out the free Platzi course I taught last year.  Best of luck!


Cannot start caddy service as non-root user on FreeBSD

1. What version of Caddy are you using (caddy -version)?
Caddy (untracked dev build) (unofficial) from FreeBSD ports (0.10.10 according to freshports).
2. What are you trying to do?
Start caddy as a non-root user via the FreeBSD init script.
3.
In rc.conf:
caddy_enable="YES"
<EMAIL_ADDRESS>caddy_config_path="/www/Caddyfile"
caddy_user="www"
caddy_group="www"

Command:
sudo service caddy start

5. Please paste any relevant HTTP request(s) here.

None
6. What did you expect to see?
Caddy starts.
7. What did you see instead (give full error messages and/or log)?
Caddy does not start. In caddy.log:
daemon: failed to set user environment

And in syslog:
daemon: initgroups(www,80): Operation not permitted

8. How can someone who is starting from scratch reproduce the bug as minimally as possible?

Install www/caddy from ports and configure rc.conf as shown above
sudo service caddy

Did you read this section of the README? https://github.com/mholt/caddy#running-in-production
At a glance this doesn't seem like a problem with Caddy, but rather with your environment.


"TypeError: Cannot read property 'tags' of null" after disconnect

Shortly after this tweet from Moobot about Twitch silently changing something with chat, my instance of Streen (basically just an IPC/RPC wrapper around twitch-irc) crashed with this log:
2015-06-04 17:38: warn: DISCONNECTED: Software caused connection abort.
2015-06-04 17:38: error: TypeError: Cannot read property 'tags' of null
    at DestroyableTransform._transform (/home/endofline/streen/node_modules/twitch-irc/node_modules/irc-message/index.js:148:35)
    at DestroyableTransform.Transform._read (/home/endofline/streen/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_transform.js:184:10)
    at DestroyableTransform.Transform._write (/home/endofline/streen/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_transform.js:172:12)
    at doWrite (/home/endofline/streen/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_writable.js:237:10)
    at writeOrBuffer (/home/endofline/streen/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_writable.js:227:5)
    at DestroyableTransform.Writable.write (/home/endofline/streen/node_modules/twitch-irc/node_modules/readable-stream/lib/_stream_writable.js:194:11)
    at Socket.ondata (_stream_readable.js:520:20)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:166:7)
    at readableAddChunk (_stream_readable.js:145:16)

No worries as pm2 just restarted it immediately, but I figured I'd post it here.

Will see what's going on, so many changes on Twitch lately -_-

Oh, turns out it is because the server is down but the port is still open. This is happening with <IP_ADDRESS>:443 right now.


--twitch-oauth-token argument was removed in Streamlink 2.0.0

Changelog of streamlink 2.0.0:

Argument --twitch-ouath-token used here:
https://github.com/ancalentari/twitch-stream-recorder/blob/fd74d8eb175ec852e1df12a275be395ce5ac4e2e/twitch-recorder.py#L153
Causes a fatal error 👎 The solution would be to just remove the argument altogether. I don't know what purpose it served in the first place

Maybe it's just my missing knowledge about how the python script and streamlink connect to twitch exactly, but why do we need to authenticate in the first place? Why is a registration and token from https://dev.twitch.tv/console/apps neccessary? AFAIK, youtube-dl can also grab and download livestreams from twitch, without token. How is it different from this project?

Maybe it's just my missing knowledge about how the python script and streamlink connect to twitch exactly, but why do we need to authenticate in the first place? Why is a registration and token from https://dev.twitch.tv/console/apps neccessary? AFAIK, youtube-dl can also grab and download livestreams from twitch, without token. How is it different from this project?

Maybe it's just my missing knowledge about how the python script and streamlink connect to twitch exactly, but why do we need to authenticate in the first place? Why is a registration and token from https://dev.twitch.tv/console/apps neccessary? AFAIK, youtube-dl can also grab and download livestreams from twitch, without token. How is it different from this project?

In this script it's used to poll target channel's online status. In streamlink user provided oauth was "disabled" already in April (1.4.0), and I'm not 100% sure what purpose it served

Maybe it's just my missing knowledge about how the python script and streamlink connect to twitch exactly, but why do we need to authenticate in the first place? Why is a registration and token from https://dev.twitch.tv/console/apps neccessary? AFAIK, youtube-dl can also grab and download livestreams from twitch, without token. How is it different from this project?

In this script it's used to poll target channel's online status. In streamlink user provided oauth was "disabled" already in April (1.4.0), and I'm not 100% sure what purpose it served

Only remove following parameters from code and it'll work:
"--twitch-oauth-token", self.access_token,

Only remove following parameters from code and it'll work:
"--twitch-oauth-token", self.access_token,


Fix issue #407

Fixes #407
Proposed Changes

Replaces list comprehension intersection with set intersection

unfortunately the tests are failing, I think this is because your approach might change the order of the categories.
I've followed your idea and just implemented a very basic solution
https://github.com/scikit-learn-contrib/category_encoders/blob/37fcf54613b0a23d52021862d8861600b51dc222/category_encoders/ordinal.py#L232-L233
This should keep the order and since sets are O(1) access time also solve the problem, although it might not be as elegant as yours. If you're happy with it, you can close the issue and PR. I hope I didn't make any mistake here
Thanks for your effort!


Invalid vector size bug during Tree-HDagg partitioning for certain input matrices

Bug description
The SpTrSv_LL_Tree_HDAGG case in SpTRSV_runtime.cpp example leads to error for certain input matrices:
Running LL HDAGG with BIN Code with #core: 4 - The runtime:7.7951e-05
core: 4; bin: 1
Compute DAG
terminate called after throwing an instance of 'std::length_error'
  what():  cannot create std::vector larger than max_size()
Aborted (core dumped)

This happens, for example, with input matrix A = random_square_sparse(200, 0.5, 1.0, 2U);, and with Metis reordering disabled. Depending on the random parameters, some matrices fail while others run fine.
Locating bug
The error occurs inside the HDAGG function, at the following call with invalid vector size nlevels = -1:
https://github.com/sympiler/aggregation/blob/da293bb1d1060bc390ad785978f8452943a8909c/src/hdagg/hdagg.cpp#L663
The invalid value -1 is returned by the build_levelSet_CSC function at line 44:
https://github.com/sympiler/aggregation/blob/da293bb1d1060bc390ad785978f8452943a8909c/src/hdagg/hdagg.cpp#L41-L64
When error occurs, the variable state is  cur_level == n == 2, then -1 is returned. Moreover, the code in line 45~64 is placed after return so will never get executed, so I guess some logic must be wrong here. The assert at line 42 should probably be enabled?
Steps to reproduce
Modify SpTRSV_runtime.cpp with the following input matrix:
n = 200;
double density = 0.5;
matrix_name = "Random_" + std::to_string(n);
A = random_square_sparse(n, density, 1.0, 2U);

...
// disable METIS
#undef METIS
#ifdef METIS
...
#else
  // avoid name conflict with another `tmp` variable later
  CSC *tmp_csc =
      make_half(Lower_A_CSC->n, Lower_A_CSC->p, Lower_A_CSC->i, Lower_A_CSC->x);
  delete Lower_A_CSC;
  Lower_A_CSC = tmp_csc;
  Lower_A_CSR = csc_to_csr(Lower_A_CSC);
#endif

I can also send a draft PR to show such bug, and a parameterized unit test to sweep over various input matrices (update: see #10).
Then, build and run:
cmake -B build_debug -DCMAKE_BUILD_TYPE=Debug
cmake --build build_debug --target Hdagg_SpTRSV
./build_debug/example/Hdagg_SpTRSV   # get bug

Deeper look with GDB:
gdb ./build_debug/example/Hdagg_SpTRSV
(check state of `n` before entering loop)
break src/hdagg/hdagg.cpp:28
(check state of `cur_level` before returning -1)
break src/hdagg/hdagg.cpp:44

(the first break point is inside `SpTrSv_LL_HDAGG` case, not yet to `SpTrSv_LL_Tree_HDAGG`, so no bug)
run
print n
(n equals 200 for this input)

(the second break point is inside the buggy `SpTrSv_LL_Tree_HDAGG`)
c
print n
(n equals 2 because ngroups is used as first argument of HDAGG() function)

(the third break point is just before returning -1)
print cur_level
(cur_level equals 2, so -1 is returned as result of build_levelSet_CSC() function)

c
(crashes when creating a vector of size -1)

Thanks for raising the issue.
@BehroozZare is the creator of HDagg. He might be able to help.


Add hydranfc bbio

To be cleaner, I have created a branch for "Add special bbio mode for hydranfc #120" pull request with the code updated with your remarks.

I am updating my old https://github.com/gvinet/pynfcreader code also.

All good and merged.
Thanks for your contribution !

Thanks for your contribution very good work !!

I found an issue on the command numbers.
The BBIO_MODE_ID (0b00000001) was assigned to BBIO_NFC_RF_OFF. I reordered the command numbers in order to make the mode work like all the others.
This has been fixed in https://github.com/hydrabus/hydrafw/commit/9444937ee824093d8341f3ae5eec3bf66bca024b


File \ New Project in Visual Studio results in extra whitespace between reference items

In Visual Studio (Dev15), create a new .NET Framework Class Library
Inspect the .csproj file

Expected: No blank lines between Reference items
Actual:
  <ItemGroup>
    <Reference Include="System"/>

    <Reference Include="System.Core"/>
    <Reference Include="System.Xml.Linq"/>
    <Reference Include="System.Data.DataSetExtensions"/>

    <Reference Include="Microsoft.CSharp"/>

    <Reference Include="System.Data"/>

    <Reference Include="System.Net.Http"/>

    <Reference Include="System.Xml"/>
  </ItemGroup>

This is probably related to the whitespace preserving functionality, though I'm not sure if the actual bug is in MSBuild or somewhere in VS.

Is it using the latest version of MSBuild? If it is, then it sounds like VS may be inserting spurious white spaces, because:

the first child overwrites any initial empty space in the parent, and adds the proper whitespace for the next element (in this case the closing tag of the parent): https://github.com/Microsoft/msbuild/blob/xplat/src/XMakeBuildEngine/UnitTestsPublicOM/Construction/WhiteSpacePreservation_Tests.cs#L229-L254
subsequent children mirror the trailing whitespace of the first child: https://github.com/Microsoft/msbuild/blob/xplat/src/XMakeBuildEngine/Construction/ProjectElementContainer.cs#L489-L498

Just in case though, I'm going to add unit tests for adding children to parents with existing siblings and assert for whitespace. :)
Do you know who owns the bit of code in VS that adds the references?

Do you know who owns the bit of code in VS that adds the references?

No, I filed the bug here because I wasn't sure

@dsplaisted
I added some tests in #1326 to show what happens on MSBuild's side. What would be really helpful here is to learn what MSBuild APIs the bit of VS code that's adding reference items is using. The tests suggest that VS might be adding some spurious new lines, and then msbuild's logic is "preserving it"

Turns out this also happens in VS 2015, so it's not related to MSBuild preserving whitespace, and not a regression in Dev15.


ARROW-5796: [Release][APT] Update expected package list

libplasma-glib-doc and libgandiva-glib-doc are unavailable
unexpetedly. It should be fixed in the next release.

+1


User can't create news with 257 symbols in the 'Text' field

Environment: macOS High Sierra 10.13, Google Chrome 81.0.4044.129 (64-bit)
Reproducable: always
Build found: commit b517ccb
Preconditions:

User is 'Registered' with correct credentials (email and password) in the GreenCity;
User is 'Sign in' in the GreenCity (https://ita-social-projects.github.io/GreenCityClient/#/news/230).

Steps to reproduce

Click on 'Eco news' button;
Click on 'Create news' button;
Fill in 'Title' field (e.g. '‘Plastic’ bags");
Select one tag (e.g. 'News');
Fill in 'Content' field (e.g. "While we all are going through these strange times, let’s appreciate what we already have. We are lucky to be born on this magnificent planet, which has a very unique way to surprise us each day and makes us fall in love with its beauty all over again. No o");
Fill in 'Source' field (e.g. 'https://www.kyivpost.com/lifestyle/ukrainian-scientist-invents-eco-friendly-plastic-bags.html?cn-reloaded=1');
Drag and drop image (e.g. attached image "Article 1");
Click on 'Publish' button.

Actual result:
News is not created.
Expected result:
News is created.
User story: #505, #525

Fixed bug


Animations breakpoints no longer work since update from 27.5 to 28.0

I have been unable to successfully add functional animation breakpoints to slide animation in the newest release. The breakpoint can be added, and will work correctly within the Jssor workspace when the animation is run using the play button, but when previewing or viewing the animation, the breaks are ignored, as well as when the project is exported and viewed in a browser.
Emails to the developer have gone unanswered.
Can anyone else confirm this behavior?

Looks like this project is abandoned.
It is not even possible to create an account to use the editor.
I guess we need to find an alternative :-(

Wow, that sucks! I have a lot of sliders I built with it, and I still have an online account that I can still access, AND I was billed for it earlier this year. Can't imagine the author would abandon a project without any notice whatsoever.


Create playground for ruby

Create the examples for the playground in ruby with inspiration from these repos:

https://github.com/appwrite/playground-for-deno
https://github.com/appwrite/playground-for-dotnet
https://github.com/appwrite/playground-for-node

Please assign this to me, I have started working on it at https://github.com/avinashupadhya99/playground-for-ruby


http 503 service unavailable with postgresql integration

Hi!
We have a deployment using ManageIQ Ivanchuk-7 in docker containers with an external postgreslq database (pgpool + posgresql/repmgr) all in one virtual machine (so, it shouldnt be a networking problem). Every day several times in a day ManageIQ UI throws http 503 service unavailable that makes the GUI impossible to acces for some minutes.
And evm.log shows the following ERROR messages
[----] E, [2021-11-10T11:08:03.154580 #9093:3d10418] ERROR -- : MIQ(MiqUiWorker::Runner) ID [129] PID [9093] GUID [d9801cc9-4e86-4b9d-9a40-60a1d2315ab1] Error in update_worker_record_at_exit: PG::UnableToSend: no connection to the server
[----] E, [2021-11-10T11:08:03.1 55661 #9093:3d10418] ERROR -- : MIQ(MiqUiWorker::Runner) ID [129] PID [9093] GUID [d9801cc9-4e86-4b9d-9a40-60a1d2315ab1] Error heartbeating because ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly
I'm attaching the logs generated in evm.log during a minute when ERRORs appear.
evm-logs-entries-1m.log
Is there a way to modify how manageIQ handles connections to an external database with a config file?
Also, in pgpool logs I see the following error messages
pid 2102: ERROR:  unable to read data
pid 2102: DETAIL:  child connection forced to terminate due to client_idle_limit:900 is reached
pid 112: ERROR:  unable to read data
pid 112: DETAIL:  child connection forced to terminate due to client_idle_limit:900 is reached
pid 2079: ERROR:  unable to read data
pid 2079: DETAIL:  child connection forced to terminate due to client_idle_limit:900 is reached

Is there a way to modify how manageIQ handles connections to an external database with a config file?

What type of config are you looking to change?  It seems you are having network errors / latency between MIQ and your postgres instance...I'm not sure there's much we can do about that other than fail as above.

Not necessarily related to your question, but you are running a version (Ivanchuk) that is 3 releases behind Lasker (Jansa and Kasparov in between) and we are about to release Morphy.  Maybe it makes sense to upgrade to the latest Lasker?

@Fryguy  I was wondering if there is a way to check if ManageIQ is aware that a idle database connection was killed by postgres and ask for another connection instead of trying to use the old connection. I dont think this is a network problem because the deployment is very simple, all in one virtual machine.
@chessbyte yes, I know that we are using an old MIQ version but at this moment unfortunately we can't do an upgrade.

I thought the connection pooling inside of Rails does this already... @jrafanie do you know?

Also, I made a test deploying manageIQ as a pod in kubernetes in the same node where pgpool/postgres pods are and I got the same behavior
NAME                                             READY   STATUS    RESTARTS   AGE   IP             NODE    NOMINATED NODE   READINESS GATES
manageiq-74fccdb898-crhn4                        1/1     Running   0          9h    <IP_ADDRESS>   node3   <none>           <none>
postgres-postgresql-ha-pgpool-84b46b758f-bxfx8   1/1     Running   0          10h   <IP_ADDRESS>   node3   <none>           <none>
postgres-postgresql-ha-postgresql-0              1/1     Running   0          10h   <IP_ADDRESS>   node3   <none>           <none>

I'm thinking this is turning into an enhancement to support pgpool which seems to have this behavior for killing idle connections that Rails' connection pool cant seem to handle.
@cymile Can you give more information on exactly how you are deploying things, so we can reproduce?

Yeah, it sounds like a "support pgpool" connection disconnect mechanisms such as client_idle_limit and connection_life_time.  I don't know what it's doing but if it's getting in the middle of the connection pool of activerecord and the transaction/session handling, it's possible it just doesn't work correctly out of box or needs some special configuration to get it to work with rails.

@cymile did this work in versions before ivanchuk?  Have you tried jansa/lasker?

@Fryguy here are the details:
K8S
kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:41:28Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}

ManageIQ ivanchuk-7 : manageiq/manageiq:ivanchuk-7
For postgres I used the bitnami chart  postgresql-ha-6.8.0

PGpool : docker.io/bitnami/pgpool:4.2.5-debian-10-r26
Postgresql: docker.io/bitnami/postgresql-repmgr:10

Deployment of manageiq pod
apiVersion: apps/v1
kind: Deployment
metadata:
  name: manageiq
  labels:
    app: manageiq
spec:
  replicas: 1
  selector:
    matchLabels:
      app: manageiq
  template:
    metadata:
      labels:
        app: manageiq
    spec:
      containers:
      - name: manageiq
        image: manageiq/manageiq:ivanchuk-7
        env:
        - name: DATABASE_URL
          value: "postgres://replica_user:password@<PGPOOL IP>:5432/manageiq_db"
        ports:
        - containerPort: 443
      nodeSelector:
        kubernetes.io/hostname: node3

apiVersion: v1
kind: Service
metadata:
  name: manageiq
  labels:
    app: manageiq
spec:
  type: NodePort
  ports:
  - port: 443
    nodePort: 30443
    protocol: TCP
  selector:
    app: manageiq

Postgres
global:
  postgresql:
    username: admin
    password: password
    database: admin
    repmgrUsername: replica_user
    repmgrPassword: password
    repmgrDatabase: replica_db
  pgpool:
    adminUsername: admin
    adminPassword: password
    serviceName: bitnami-postgresql-ha-pgpool
    servicePort: 5432
postgresql-ha:
  enabled: true
  postgresqlImage:
    registry: docker.io
    repository: bitnami/postgresql-repmgr
    tag: 10
  pgpoolImage:
    registry: docker.io
    repository: bitnami/pgpool
    tag: 4.2.5-debian-10-r26
  pgpool:
    nodeSelector:
      kubernetes.io/hostname: node3
    replicaCount: 1
    numInitChildren: 500
    maxPool: 1
    clientIdleLimit: 3600
    connectionLifeTime: 3600
    useLoadBalancing: false
    resources:
      requests:
        cpu: 200m
        memory: 256Mi
      limits:
        cpu: 400m
        memory: 512Mi
    tolerations:
    - key: "node.kubernetes.io/unreachable"
      operator: "Exists"
      effect: "NoExecute"
      tolerationSeconds: 5
    - key: "node.kubernetes.io/not-ready"
      operator: "Exists"
      effect: "NoExecute"
      tolerationSeconds: 5
    readinessProbe:
      enabled: true
      initialDelaySeconds: 30
      periodSeconds: 90
      timeoutSeconds: 20
  postgresql:
    nodeSelector:
      kubernetes.io/hostname: node3
    username: postgres
#    password:
    replicaCount: 1
    affinity:
      podAntiAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
        - weight: 100
          podAffinityTerm:
            labelSelector:
              matchExpressions:
              - key: app.kubernetes.io/instance
                operator: In
                values: [ postgresql ]
              - key: app.kubernetes.io/name
                operator: In
                values: [ postgresql-ha ]
            topologyKey: kubernetes.io/hostname
    resources:
      requests:
        cpu: 300m
        memory: 512Mi
      limits:
        cpu: 600m
        memory: 2048Mi
    sharedPreloadLibraries: pgaudit, repmgr
    maxConnections: 1024
    dbUserConnectionLimit: 1024
  persistence:
    enabled: false
    mountPath: /var/lib/dbdata/postgresql-server
    size: 10Gi
  service:
    type: ClusterIP
    port: 5432

@jrafanie  I only worked with ivanchuk, I will try with the versions you suggested

@jrafanie I only worked with ivanchuk, I will try with the versions you suggested

I don't know that anything is different in other versions but I was curious if you had this working previously and now had issues with ivanchuk or if this has only been tested there and had this issue.

well, I tried with jansa-4/lasker-latest and I got multiple messages like these and the GUI is down
{"@timestamp":"2021-11-11T18:15:11.354238 ","hostname":"manageiq-7788cf8646-9lmlr","pid":7,"tid":"2ad9fd17594c","level":"err","message":"/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:130:in `rescue in handle_exception'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:120:in `handle_exception'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:389:in `create_entity'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:236:in `block (2 levels) in define_entity_methods'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:101:in `method_missing'\n/var/www/miq/vmdb/lib/container_orchestrator.rb:22:in `create_deployment'\n/var/www/miq/vmdb/app/models/miq_worker/replica_per_worker.rb:6:in `create_container_objects'\n/var/www/miq/vmdb/app/models/miq_worker.rb:337:in `start_runner_via_container'\n/var/www/miq/vmdb/app/models/miq_worker.rb:330:in `start_runner'\n/var/www/miq/vmdb/app/models/miq_worker.rb:375:in `start'\n/var/www/miq/vmdb/app/models/miq_worker.rb:280:in `start_worker'\n/var/www/miq/vmdb/app/models/miq_worker.rb:158:in `block in sync_workers'\n/var/www/miq/vmdb/app/models/miq_worker.rb:158:in `times'\n/var/www/miq/vmdb/app/models/miq_worker.rb:158:in `sync_workers'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:56:in `block in sync_workers'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `each'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:24:in `monitor_workers'\n/var/www/miq/vmdb/app/models/miq_server.rb:193:in `block in monitor'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:28:in `realtime_block'\n/var/www/miq/vmdb/app/models/miq_server.rb:193:in `monitor'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:137:in `block in monitor'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:35:in `realtime_block'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:137:in `monitor'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:48:in `block (2 levels) in monitor_servers'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:273:in `block in as_each_server'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:271:in `each'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:271:in `as_each_server'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:48:in `block in monitor_servers'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:46:in `loop'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:46:in `monitor_servers'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:29:in `start'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:81:in `start'\n/var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `\u003cmain\u003e'"}
{"@timestamp":"2021-11-11T18:15:11.361084 ","hostname":"manageiq-7788cf8646-9lmlr","pid":7,"tid":"2ad9fd17594c","level":"info","message":"MIQ(MiqEventHandler.sync_workers) Workers are being synchronized: Current #: [0], Desired #: [1]"}
{"@timestamp":"2021-11-11T18:15:11.400227 ","hostname":"manageiq-7788cf8646-9lmlr","pid":7,"tid":"2ad9fd17594c","level":"err","message":"MIQ(MiqServer#sync_workers) Failed to sync_workers for class: MiqEventHandler"}
{"@timestamp":"2021-11-11T18:15:11.400873 ","hostname":"manageiq-7788cf8646-9lmlr","pid":7,"tid":"2ad9fd17594c","level":"err","message":"[Kubeclient::HttpError]: deployments.apps is forbidden: User \"system:serviceaccount:bitnami:default\" cannot create resource \"deployments\" in API group \"apps\" in the namespace \"bitnami\"  Method:[block (2 levels) in \u003cclass:LogProxy\u003e]"}
{"@timestamp":"2021-11-11T18:15:11.401185 ","hostname":"manageiq-7788cf8646-9lmlr","pid":7,"tid":"2ad9fd17594c","level":"err","message":"/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:130:in `rescue in handle_exception'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:120:in `handle_exception'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:389:in `create_entity'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:236:in `block (2 levels) in define_entity_methods'\n/opt/manageiq/manageiq-gemset/gems/kubeclient-4.9.0/lib/kubeclient/common.rb:101:in `method_missing'\n/var/www/miq/vmdb/lib/container_orchestrator.rb:22:in `create_deployment'\n/var/www/miq/vmdb/app/models/miq_worker/replica_per_worker.rb:6:in `create_container_objects'\n/var/www/miq/vmdb/app/models/miq_worker.rb:337:in `start_runner_via_container'\n/var/www/miq/vmdb/app/models/miq_worker.rb:330:in `start_runner'\n/var/www/miq/vmdb/app/models/miq_worker.rb:375:in `start'\n/var/www/miq/vmdb/app/models/miq_worker.rb:280:in `start_worker'\n/var/www/miq/vmdb/app/models/miq_worker.rb:158:in `block in sync_workers'\n/var/www/miq/vmdb/app/models/miq_worker.rb:158:in `times'\n/var/www/miq/vmdb/app/models/miq_worker.rb:158:in `sync_workers'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:56:in `block in sync_workers'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `each'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers'\n/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:24:in `monitor_workers'\n/var/www/miq/vmdb/app/models/miq_server.rb:193:in `block in monitor'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:28:in `realtime_block'\n/var/www/miq/vmdb/app/models/miq_server.rb:193:in `monitor'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:137:in `block in monitor'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'\n/opt/manageiq/manageiq-gemset/bundler/gems/manageiq-gems-pending-4026507c32b7/lib/gems/pending/util/extensions/miq-benchmark.rb:35:in `realtime_block'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:137:in `monitor'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:48:in `block (2 levels) in monitor_servers'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:273:in `block in as_each_server'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:271:in `each'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:271:in `as_each_server'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:48:in `block in monitor_servers'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:46:in `loop'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:46:in `monitor_servers'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:29:in `start'\n/var/www/miq/vmdb/lib/workers/evm_server.rb:81:in `start'\n/var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `\u003cmain\u003e'"}

Hi,
I also am facing the same problem reported by @cymile, ManageIQ gets Down after 30 minutes or so, and checking the logs it shows:
ERROR: unable to read data
DETAIL: child connection forced to terminate due to client_idle_limit: 900 is reached
I am using this Repo to deploy Postgres and PgPool
https://github.com/paunin/PostDock/tree/master/k8s/example1-basic-multilevel
Do you have any version of Postgres recommended to work well with ManageIQ?
Regards
Javier

Any postgres should work - I think the problem is the pgpool and more specifically the clientIdleLimit: 3600.
@cymile As a workaround, if you remove that setting from the pgpool deployment and/or set it to a ridiculously high number, do things start to work?

Any postgres should work - I think the problem is the pgpool and more specifically the clientIdleLimit: 3600.
@cymile As a workaround, if you remove that setting from the pgpool deployment and/or set it to a ridiculously high number, do things start to work?

Yes, I did that test too (with manageIQ as a container) . I used a client_idle_limit:2592000 value and the errors were less frecuent (between some hours)...with a lower value like 60, the errors appeared each minute. Also, setting with  0 got the same behavior.

我是在vsphere部署master版本，80 443端口正常，evmserverd服务正常，ManageIQ管理无法访问，

报错

Also, I tried connecting manageIQ pod directly with a primary postgresql pod (without pgpool) and got the same behavior.

Do you have any version of Postgres recommended to work well with ManageIQ?

@richardqa I think the question is if pgpool + manageiq podified was ever working properly.  I can't tell if this ever worked or if this is a new problem.
Does anyone have a version of manageiq that successfully worked in podified with pgpool?  We need to figure out if we had a regression or if this is just adding support for pgpool.

Also, I tried connecting manageIQ pod directly to a primary postgresql pod (without pgpool) and got the same behavior.

@cymile by "same behavior", do you mean 503?  What errors did you get in the manageiq and postgresql pod?  I would assume you'd have to manually allow communication between pods.  I don't recall what we had to do to get the standard deployment of manageiq podified with postresql + manageiq to communication together but I'd assume you've have to do some similar things.  For example, the pg container image assets or the other manageiq container environment that sets up the DATABASE_URL and checks for certificates.

Also, I tried connecting manageIQ pod directly to a primary postgresql pod (without pgpool) and got the same behavior.

@cymile by "same behavior", do you mean 503? What errors did you get in the manageiq and postgresql pod? I would assume you'd have to manually allow communication between pods. I don't recall what we had to do to get the standard deployment of manageiq podified with postresql + manageiq to communicate together but I'd assume you've have to do some similar things if you're using an external postgresql pod. For example, the pg container image assets or the other manageiq container environment that sets up the DATABASE_URL and checks for certificates.

Yes, I got error 503 each 20 minutos approx. In ManageIQ I got the same errors  posted at the begining of this issue
 [----] E, [2021-11-10T11:08:03.154580 #9093:3d10418] ERROR -- : MIQ(MiqUiWorker::Runner) ID [129] PID [9093] GUID [d9801cc9-4e86-4b9d-9a40-60a1d2315ab1] Error in update_worker_record_at_exit: PG::UnableToSend: no connection to the server
[----] E, [2021-11-10T11:08:03.1 55661 #9093:3d10418] ERROR -- : MIQ(MiqUiWorker::Runner) ID [129] PID [9093] GUID [d9801cc9-4e86-4b9d-9a40-60a1d2315ab1] Error heartbeating because ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly

And in postgresql pod I didnt see ERROR messages.
When testing MIQ with Postgresql (k8s pods), MIQ was connected to Postgresql using the Cluster-IP assigned to Postgresql pod. All all these pods where located in the same k8s node. So I dont think the problem is pgpool.


Add a minimum value for the CP MTU

Avoid negative numbers and also set a lower bondary.
500 will mean 400 bytes minimum payload that will allow
at least a couple of gossip message to fit.
There is not theoretical limit becasue the message is made of
strings so there is still the possibility to have cases where
the 400 bytes are not enough to fit a single message, but
in that case we should start thinking why do I need a node
name that is long as an enciclopedia
Signed-off-by: Flavio Crisciani<EMAIL_ADDRESS>

LGTM


Implements syscall 165

Fixes #397.

Some errors on certain games, will post in Issues.

#400 #401 #402

#400 #401 #402

Waiting for these to be fixed to merge. Also, was looking into finally starting the lifter but it seems changes are still being made to it as of the last two PRs. Will go ahead and begin once this is merged.

Those issues should not cause any major changes to the EE. So the current changes in this PR should be stable enough for you to continue working on the EE.

Not sure if you are waiting for those issues to be fixed. If yes we should fix it on a separated PR because it might be required some work.

Not sure if you are waiting for those issues to be fixed. If yes we should fix it on a separated PR because it might be required some work.

yeah I was, will merge this then.


Tagging

Tagging would be nice so that it's easy to separate out work life from grocery life from project life, right?
I use tags in evernote heavily and when I first thought of this thing I wanted to basically just put some trigger-type syntax at the bottom of any note, like:
this is some note
this is more of the note

#tags: grocery,personal,fun

they could then be parsed & stripped out during save() so that they don't end up in the saved text of the note, then added back into the body of the note if you edit it again.
what do you think?

Yeah, that'd be perfect and hides it from the UI, which is super simple. I'll brush up on my evernote api.

here's something for starters
4a42fc9b0d09812a91cad95ea6e3be4db3a43714

good enuf https://github.com/sixninetynine/not/commit/a0a5976b3a6cd97ca55ad2ef7eddfe2df82ec0f1


Error running Docker Compose Task for the Kubernates Lab

The Run Service Pipeline task is hanging as it is unable to find the aspnetcore-build:1.0-2.0 Image File
Pulling ci-build (microsoft/aspnetcore-build:1.0-2.0)...
The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.
Searching for this file on the Docker Hub it does not exist.

Hi @montysinha7 ,
The issue was due to the deprecated docker images. We updated the images now. Please try again by creating a new project from the Demo generator and let us know if you face any issues
Thanks

Hi,
Closing this issue for now. Feel free to re-open if the issue still exists.
Thanks


'ERROR: Failed building wheel for triton'  on V100 with cuda10.1

Hi, I have an error when I ran DS_BUILD_SPARSE_ATTN=1 pip install deepspeed
The error message is here.
Collecting deepspeed
  Using cached deepspeed-0.3.16-cp38-cp38-linux_x86_64.whl
Requirement already satisfied: numpy in /opt/conda/envs/temp/lib/python3.8/site-packages (from deepspeed) (1.20.1)
Collecting tensorboardX==1.8
  Using cached tensorboardX-1.8-py2.py3-none-any.whl (216 kB)
Collecting psutil
  Using cached psutil-5.8.0-cp38-cp38-manylinux2010_x86_64.whl (296 kB)
Collecting triton==0.2.3
  Using cached triton-0.2.3.tar.gz (943 kB)
Requirement already satisfied: torchvision>=0.4.0 in /opt/conda/envs/temp/lib/python3.8/site-packages (from deepspeed) (0.8.2)
Collecting ninja
  Using cached ninja-1.10.0.post2-py3-none-manylinux1_x86_64.whl (107 kB)
Requirement already satisfied: tqdm in /opt/conda/envs/temp/lib/python3.8/site-packages (from deepspeed) (4.60.0)
Requirement already satisfied: torch>=1.2 in /opt/conda/envs/temp/lib/python3.8/site-packages (from deepspeed) (1.7.1)
Requirement already satisfied: six in /opt/conda/envs/temp/lib/python3.8/site-packages (from tensorboardX==1.8->deepspeed) (1.15.0)
Requirement already satisfied: protobuf>=3.2.0 in /opt/conda/envs/temp/lib/python3.8/site-packages (from tensorboardX==1.8->deepspeed) (3.17.0)
Requirement already satisfied: sympy in /opt/conda/envs/temp/lib/python3.8/site-packages (from triton==0.2.3->deepspeed) (1.8)
Requirement already satisfied: typing_extensions in /opt/conda/envs/temp/lib/python3.8/site-packages (from torch>=1.2->deepspeed) (<IP_ADDRESS>)
Requirement already satisfied: pillow>=4.1.1 in /opt/conda/envs/temp/lib/python3.8/site-packages (from torchvision>=0.4.0->deepspeed) (8.2.0)
Requirement already satisfied: mpmath>=0.19 in /opt/conda/envs/temp/lib/python3.8/site-packages (from sympy->triton==0.2.3->deepspeed) (1.2.1)
Building wheels for collected packages: triton
  Building wheel for triton (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/conda/envs/temp/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py'"'"'; __file__='"'"'/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-7v5w2e6y
       cwd: /tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/
  Complete output (256 lines):
  /opt/conda/envs/temp/lib/python3.8/distutils/dist.py:274: UserWarning: Unknown distribution option: 'keyword'
    warnings.warn(msg)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-3.8
  creating build/lib.linux-x86_64-3.8/triton
  copying triton/__init__.py -> build/lib.linux-x86_64-3.8/triton
  copying triton/kernel.py -> build/lib.linux-x86_64-3.8/triton
  creating build/lib.linux-x86_64-3.8/triton/_C
  copying triton/_C/__init__.py -> build/lib.linux-x86_64-3.8/triton/_C
  creating build/lib.linux-x86_64-3.8/triton/ops
  copying triton/ops/__init__.py -> build/lib.linux-x86_64-3.8/triton/ops
  copying triton/ops/batchnorm.py -> build/lib.linux-x86_64-3.8/triton/ops
  copying triton/ops/einsum.py -> build/lib.linux-x86_64-3.8/triton/ops
  creating build/lib.linux-x86_64-3.8/triton/nn
  copying triton/nn/__init__.py -> build/lib.linux-x86_64-3.8/triton/nn
  copying triton/nn/attention.py -> build/lib.linux-x86_64-3.8/triton/nn
  copying triton/nn/conv.py -> build/lib.linux-x86_64-3.8/triton/nn
  copying triton/nn/linear.py -> build/lib.linux-x86_64-3.8/triton/nn
  creating build/lib.linux-x86_64-3.8/triton/_C/include
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen
  copying triton/_C/include/triton/codegen/pass.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen
  copying triton/_C/include/triton/codegen/target.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
  copying triton/_C/include/triton/codegen/analysis/align.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
  copying triton/_C/include/triton/codegen/analysis/allocation.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
  copying triton/_C/include/triton/codegen/analysis/axes.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
  copying triton/_C/include/triton/codegen/analysis/layout.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
  copying triton/_C/include/triton/codegen/analysis/liveness.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
  copying triton/_C/include/triton/codegen/selection/generator.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
  copying triton/_C/include/triton/codegen/selection/machine_layout.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
  copying triton/_C/include/triton/codegen/selection/machine_value.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/coalesce.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/cts.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/dce.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/disassociate.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/membar.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/peephole.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  copying triton/_C/include/triton/codegen/transform/reassociate.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/backend.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/buffer.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/context.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/cublas.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/cudnn.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/device.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/dispatch.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/error.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/event.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/handle.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/kernel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/module.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/platform.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  copying triton/_C/include/triton/driver/stream.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/external
  copying triton/_C/include/triton/external/half.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_d3d10.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_d3d11.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_dx9_media_sharing.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_dx9_media_sharing_intel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_egl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_ext.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_ext_intel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_gl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_gl_ext.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_platform.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl_va_api_media_sharing_intel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/opencl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  copying triton/_C/include/triton/external/CL/cl.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL  copying triton/_C/include/triton/external/CL/cl2.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CUDA
  copying triton/_C/include/triton/external/CUDA/cuda.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CUDA
  copying triton/_C/include/triton/external/CUDA/nvml.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CUDA
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/basic_block.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/builder.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/constant.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/context.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/context_impl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/enums.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/function.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/instructions.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/metadata.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/module.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/print.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/type.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/utils.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/value.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  copying triton/_C/include/triton/ir/visitor.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/ast.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/code_gen.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/cpp.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/encoding.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/error.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/evaluator.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/mem_pool.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/parser.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/scanner.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/scope.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/token.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/type.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  copying triton/_C/include/triton/lang/visitor.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/runtime
  copying triton/_C/include/triton/runtime/arg.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/runtime
  copying triton/_C/include/triton/runtime/function.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/runtime
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
  copying triton/_C/include/triton/tools/graph.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
  copying triton/_C/include/triton/tools/thread_pool.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
  copying triton/_C/include/triton/tools/bench.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
  copying triton/_C/include/triton/tools/sha1.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
  creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools/sys
  copying triton/_C/include/triton/tools/sys/getenv.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools/sys  copying triton/_C/include/triton/tools/sys/mkdir.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools/sys
  running build_ext
  -- The C compiler identification is GNU 7.5.0
  -- The CXX compiler identification is GNU 7.5.0
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Found LLVM: /usr/lib/llvm-9 (found version "9.0.0")
  -- Adding Python module
  -- Configuring done
  CMake Warning (dev) at CMakeLists.txt:45 (add_library):
    Policy CMP0038 is not set: Targets may not link directly to themselves.
    Run "cmake --help-policy CMP0038" for policy details.  Use the cmake_policy
    command to set the policy and suppress this warning.

    Target "triton" links to itself.
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMakeFiles/triton.dir/build.make:1358: recipe for target 'CMakeFiles/triton.dir/launch.cc.o' failed
  make[2]: *** [CMakeFiles/triton.dir/launch.cc.o] Error 1
  make[2]: *** Waiting for unfinished jobs....
  CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/triton.dir/all' failed
  make[1]: *** [CMakeFiles/triton.dir/all] Error 2
  Makefile:94: recipe for target 'all' failed
  make: *** [all] Error 2
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py", line 106, in <module>
      setup(
    File "/opt/conda/envs/temp/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
      return distutils.core.setup(**attrs)
    File "/opt/conda/envs/temp/lib/python3.8/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 966, in run_commands
      self.run_command(cmd)
    File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/opt/conda/envs/temp/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 299, in run
      self.run_command('build')
    File "/opt/conda/envs/temp/lib/python3.8/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/opt/conda/envs/temp/lib/python3.8/distutils/command/build.py", line 135, in run
      self.run_command(cmd_name)
    File "/opt/conda/envs/temp/lib/python3.8/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py", line 55, in run
      self.build_extension(ext)
    File "/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py", line 94, in build_extension
      subprocess.check_call(['cmake', '--build', '.'] + build_args, cwd=self.build_temp)
    File "/opt/conda/envs/temp/lib/python3.8/subprocess.py", line 364, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j4']' returned non-zero exit status 2.
  ----------------------------------------
  ERROR: Failed building wheel for triton
  Running setup.py clean for triton
Failed to build triton
Installing collected packages: triton, tensorboardX, psutil, ninja, deepspeed
    Running setup.py install for triton ... error
    ERROR: Command errored out with exit status 1:
     command: /opt/conda/envs/temp/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py'"'"'; __file__='"'"'/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-tk4_o63b/install-record.txt --single-version-externally-managed --compile --install-headers /opt/conda/envs/temp/include/python3.8/triton
         cwd: /tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/
    Complete output (258 lines):
    /opt/conda/envs/temp/lib/python3.8/distutils/dist.py:274: UserWarning: Unknown distribution option: 'keyword'
      warnings.warn(msg)
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-3.8
    creating build/lib.linux-x86_64-3.8/triton
    copying triton/__init__.py -> build/lib.linux-x86_64-3.8/triton
    copying triton/kernel.py -> build/lib.linux-x86_64-3.8/triton
    creating build/lib.linux-x86_64-3.8/triton/_C
    copying triton/_C/__init__.py -> build/lib.linux-x86_64-3.8/triton/_C
    creating build/lib.linux-x86_64-3.8/triton/ops
    copying triton/ops/__init__.py -> build/lib.linux-x86_64-3.8/triton/ops
    copying triton/ops/batchnorm.py -> build/lib.linux-x86_64-3.8/triton/ops
    copying triton/ops/einsum.py -> build/lib.linux-x86_64-3.8/triton/ops
    creating build/lib.linux-x86_64-3.8/triton/nn
    copying triton/nn/__init__.py -> build/lib.linux-x86_64-3.8/triton/nn
    copying triton/nn/attention.py -> build/lib.linux-x86_64-3.8/triton/nn
    copying triton/nn/conv.py -> build/lib.linux-x86_64-3.8/triton/nn
    copying triton/nn/linear.py -> build/lib.linux-x86_64-3.8/triton/nn
    creating build/lib.linux-x86_64-3.8/triton/_C/include
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen
    copying triton/_C/include/triton/codegen/pass.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen
    copying triton/_C/include/triton/codegen/target.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/align.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/allocation.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/axes.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/layout.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/liveness.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/analysis
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
    copying triton/_C/include/triton/codegen/selection/generator.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
    copying triton/_C/include/triton/codegen/selection/machine_layout.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
    copying triton/_C/include/triton/codegen/selection/machine_value.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/selection
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/coalesce.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/cts.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/dce.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/disassociate.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/membar.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/peephole.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/reassociate.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/codegen/transform
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/backend.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/buffer.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/context.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/cublas.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/cudnn.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/device.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/dispatch.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/error.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/event.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/handle.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/kernel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/module.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/platform.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/stream.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/driver
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/external
    copying triton/_C/include/triton/external/half.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL    copying triton/_C/include/triton/external/CL/cl_d3d10.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_d3d11.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_dx9_media_sharing.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_dx9_media_sharing_intel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_egl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_ext.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_ext_intel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_gl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_gl_ext.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_platform.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_va_api_media_sharing_intel.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/opencl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl2.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CL
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CUDA
    copying triton/_C/include/triton/external/CUDA/cuda.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CUDA
    copying triton/_C/include/triton/external/CUDA/nvml.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/external/CUDA
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/basic_block.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/builder.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/constant.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/context.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/context_impl.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/enums.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/function.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/instructions.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/metadata.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/module.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/print.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/type.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/utils.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/value.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/visitor.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/ir
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/ast.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/code_gen.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/cpp.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/encoding.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/error.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/evaluator.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/mem_pool.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/parser.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/scanner.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/scope.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/token.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/type.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/visitor.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/lang
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/runtime
    copying triton/_C/include/triton/runtime/arg.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/runtime
    copying triton/_C/include/triton/runtime/function.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/runtime
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/graph.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/thread_pool.h -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/bench.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/sha1.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools
    creating build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools/sys
    copying triton/_C/include/triton/tools/sys/getenv.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools/sys
    copying triton/_C/include/triton/tools/sys/mkdir.hpp -> build/lib.linux-x86_64-3.8/triton/_C/include/triton/tools/sys
    running build_ext
    -- The C compiler identification is GNU 7.5.0
    -- The CXX compiler identification is GNU 7.5.0
    -- Check for working C compiler: /usr/bin/cc
    -- Check for working C compiler: /usr/bin/cc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Detecting C compile features
    -- Detecting C compile features - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Detecting CXX compile features
    -- Detecting CXX compile features - done
    -- Found LLVM: /usr/lib/llvm-9 (found version "9.0.0")
    -- Adding Python module
    -- Configuring done
    CMake Warning (dev) at CMakeLists.txt:45 (add_library):
      Policy CMP0038 is not set: Targets may not link directly to themselves.
      Run "cmake --help-policy CMP0038" for policy details.  Use the cmake_policy
      command to set the policy and suppress this warning.

      Target "triton" links to itself.
    This warning is for project developers.  Use -Wno-dev to suppress it.

    CMakeFiles/triton.dir/build.make:1358: recipe for target 'CMakeFiles/triton.dir/launch.cc.o' failed
    make[2]: *** [CMakeFiles/triton.dir/launch.cc.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/triton.dir/all' failed
    make[1]: *** [CMakeFiles/triton.dir/all] Error 2
    Makefile:94: recipe for target 'all' failed
    make: *** [all] Error 2
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py", line 106, in <module>
        setup(
      File "/opt/conda/envs/temp/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
        return distutils.core.setup(**attrs)
      File "/opt/conda/envs/temp/lib/python3.8/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/opt/conda/envs/temp/lib/python3.8/site-packages/setuptools/command/install.py", line 61, in run
        return orig.install.run(self)
      File "/opt/conda/envs/temp/lib/python3.8/distutils/command/install.py", line 545, in run
        self.run_command('build')
      File "/opt/conda/envs/temp/lib/python3.8/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/opt/conda/envs/temp/lib/python3.8/distutils/command/build.py", line 135, in run
        self.run_command(cmd_name)
      File "/opt/conda/envs/temp/lib/python3.8/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/opt/conda/envs/temp/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py", line 55, in run
        self.build_extension(ext)
      File "/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py", line 94, in build_extension
        subprocess.check_call(['cmake', '--build', '.'] + build_args, cwd=self.build_temp)
      File "/opt/conda/envs/temp/lib/python3.8/subprocess.py", line 364, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j4']' returned non-zero exit status 2.
    ----------------------------------------
ERROR: Command errored out with exit status 1: /opt/conda/envs/temp/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py'"'"'; __file__='"'"'/tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-tk4_o63b/install-record.txt --single-version-externally-managed --compile --install-headers /opt/conda/envs/temp/include/python3.8/triton Check the logs for full command output.

My machine is V100 with
cuda 10.1
pytorch: 1.7.1
cmake: 3.10.2
g++, gcc: 7.5.0
I ran sudo apt-get -y install llvm-9-dev cmake before DS_BUILD_SPARSE_ATTN=1 pip install deepspeed
llvm-9-dev is already the newest version (1:9-2~ubuntu18.04.2).
Please help me...

In file included from /tmp/pip-install-rb12ymln/triton_44cc137ef32d4085a84ae01e3c15b88a/src/launch.cc:9:0:
/opt/conda/envs/temp/lib/python3.8/site-packages/torch/include/ATen/cuda/CUDAContext.h:7:10: fatal error: cublas_v2.h: No such file or directory
#include <cublas_v2.h>

This suggests a missing cublas header file. Have you tried resolving that?

Thank you for your reply!
Actually I couldn't fix this error, so I used a docker container and it works now!


Light cookies broke some time between 1.69.2 and 1.70.0

Works:
https://launch.playcanvas.com/444422?debug=true&version=1.69.2
Broken:
https://launch.playcanvas.com/444422?debug=true&version=1.70.0

from a quick capture of rendering of the back wall on the left.
correct:

broken:

fragment shader difference (not sure this is the actual issue, but that's the difference I see between captures)

needs more investigation


Post Commit Review for Version PHP-7.0-Linux version 4.0.4

Please have a look a my comments for
https://github.com/Microsoft/msphpsql/commit/4ccffbbe077e87288bf00cc6327142579da46775

I think there a new issue in phpize for pdo_sqlsrv, I'll open a dedicated issue for that.
The Version in version.h is 4.0.0 and not as expected 4.0.4
There are some minor coding style issues.

@xalopp definitely! Will take a look at this. Thanks for reporting them. Formatting issues and version issue looks valid. Will keep you posted.


Add command to produce coalesced base image

Also, we should add integration test for this command. Restore to raw and qcow2, with or without base image, and verify the data.

LGTM. If there isn't anything else need to be updated, can you clean the code? So I can merge it.
Thanks.

Close in favor of #335


Integration Test Workflow

Issue #, if available:
Description of changes:
Integration test workflow with flask web app testing aws sdk, http, flask-sql alchemy instrumentation and metadata-annotations injection

Added terraform to deploy web app on elastic beanstalk
Added Github actions workflow to run end to end integration tests

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

Codecov Report

Merging #246 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #246   +/-   ##
=======================================
  Coverage   79.29%   79.29%
=======================================
  Files          80       80
  Lines        3159     3159
=======================================
  Hits         2505     2505
  Misses        654      654

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 2660af1...679211d. Read the comment docs.

Action items:

Work with new validator module (https://github.com/aws-observability/aws-otel-test-framework/pull/32)
Make sure main repo has aws account creds
Put flask sample apps to sample apps repo
Update the workflow to change repo download config, testing config