text:
Only zoom in on wheel any direction

In Google Chrome 44 image only zoom in on wheel event. When I logged event, there wasn't deltaY property, but in originalEvent was.
Works correctly only if change line:
if (e.deltaY < 0) {
to
if (e.originalEvent.deltaY < 0) {

I'm not sure I understand the problem. Your image isn't zooming when you scroll your mouse wheel? Please share some more info. Thanks

First I load an image, then when I scroll the wheel (there is no difference scroll down or scroll up), the image zooms out, when it reaches max zoom I can only drag the image. It happens because in scroll event there is no property deltaY.

You say when it reaches max zoom. If it's max zoom, what are you expecting the mouse wheel to do? I'll be in gitter for a bit, can you join to explain it to me more?
https://gitter.im/twhitbeck/angular-cropper

Ok, issue has been resolved. If jQuery is present, the event does not have deltaY which we use. In this case we must use e.originalEvent.deltaY. Please update.

source: gharchive/issue

authors: alnimu twhitbeck

repo: twhitbeck/angular-cropper

license: mit

license_type: permissive

license_source: bigquery


text:
Inline Twig Includes

Implementing an include in an inline template always throws TwigException: Unable to find template file undefined.
I'm using the API as follows:
Twig.twig({
    allowInlineIncludes: true,
    async: false,
    data: `{% include 'somefile.twig' %}`,
  }).render({});

I have tried with just about every combination of file and base with no luck.
I peaked around at the source and the problem looks to be in twig.core.js.

Much appreciated. That block of code makes much more sense now. :)


text:
feat(pixels): add my new pixel

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

source: gharchive/pull-request

repo: twilio-labs/open-pixel-art

license: MIT

license_source: github-api


text:
global is not defined

Attempting to use twilio-chat in an Angular project with TypeScript. I've tried various methods of importing and they all result in this error when trying to instantiate the Client.

import * as Chat from 'twilio-chat';
const client = await Chat.create(token); // ERR

import Client from 'twilio-chat';
const client = await Client.create(token); // ERR

import { Client } from 'twilio-chat';
const client = await Client.create(token); // ERR

core.js:15714 ERROR Error: Uncaught (in promise): ReferenceError: global is not defined
ReferenceError: global is not defined
    at Object../node_modules/twilsock/lib/tokenStorage.js (tokenStorage.js:51)
    at __webpack_require__ (bootstrap:83)
    at Object../node_modules/twilsock/lib/client.js (client.js:14)
    at __webpack_require__ (bootstrap:83)
    at Object../node_modules/twilsock/lib/index.js (index.js:3)
    at __webpack_require__ (bootstrap:83)
    at Object../node_modules/twilio-chat/browser/client.js (client.js:71)
    at __webpack_require__ (bootstrap:83)
    at Object../node_modules/twilio-chat/browser/index.js (index.js:3)
    at __webpack_require__ (bootstrap:83)
    at resolvePromise (zone.js:814)
    at resolvePromise (zone.js:771)
    at zone.js:873
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:421)
    at Object.onInvokeTask (core.js:17280)
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:420)
    at Zone.push../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:188)
    at drainMicroTaskQueue (zone.js:595)

Inspecting tokenStorage.js reveals the culprit two lines.
/**51 **/ TokenStorage.sessionStorage = global['sessionStorage'];
/**52 **/ TokenStorage.window = global['window'];

Adding (window as any).global = window; is a workaround but one that should not be needed.
I'm not sure if this is the correct place to file issues as the twilio-chat library does not seem to be open source and there isn't a bugs entry in package.json.

I'm having the same issue but in my case the (window as any).global = window; trick doesn't work either. Did you find a better fix?

i am encountering the same problem as above. And the hack is not (window as any).global = window;

I've added, window.global = window; in head of my index.html and it worked.

I've added, window.global = window; in head of my index.html and it worked.

This worked for me, too! Thanks so much.

I've added, window.global = window; in head of my index.html and it worked.

Works, but it is very dirty solution.
@dmorilha-twilio

authors: adamduren amatelic dryize gkucmierz joelcogen miktav

repo: twilio/twilio-chat-demo-js


text:
twilio screen share issue on catalina os safari browser

I'm facing an issue on safari browser in mac catalina os. I am using twilio reactJs sdk. can anyone help me?
Step to produce the issue :

join a room with multiple person.
host is on the mac catalina os.
host shares his screen.
host now open a tab and create google meet meeting.
google meet took camera permission.
now host goes back to twilio conference tab.
safari browser tooks camera permission again for twilio conference tab.
when i give camera permission, other participants are seeing my video, instead of seeing the shared screen.

is this issue meant to be happen?  or i have done something wrong?
p.s : this issue arises only in mac catalina os.

Thanks for the issue @ashrakrahman!
I am able to reproduce this issue. I'm not exactly sure why this is happening, but I suspect that it is a problem with Safari, and not a problem with this app. A quick investigation will be needed to know for sure.
I wanted to ask - is this problem impacting you in any way? Do you have a use case that requires that multiple video apps be used inside Safari?
At this point, a good workaround would be to use Chrome instead. Please let me know what you think.

Closing due to inactivity. Im happy to reopen with more information!

authors: ashrakrahman timmydoza

repo: twilio/twilio-video-app-react


text:
[Snyk] Fix for 10 vulnerabilities

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-BROWSERSLIST-1090194
Yes
Proof of Concept

526/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 4.1
Arbitrary Code Injection SNYK-JS-EJS-1049328
Yes
Proof of Concept

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-GLOBPARENT-1016905
Yes
Proof of Concept

601/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution SNYK-JS-IMMER-1540542
Yes
Proof of Concept

611/1000  Why? Recently disclosed, Has a fix available, CVSS 6.5
Information Exposure SNYK-JS-NODEFETCH-2342118
Yes
No Known Exploit

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Open Redirect SNYK-JS-NODEFORGE-2330875
Yes
Proof of Concept

529/1000  Why? Has a fix available, CVSS 6.3
Prototype Pollution SNYK-JS-NODEFORGE-2331908
Yes
No Known Exploit

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-PROMPTS-1729737
Yes
Proof of Concept

646/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 6.5
Prototype Pollution SNYK-JS-RFC6902-1053318
Yes
Proof of Concept

619/1000  Why? Has a fix available, CVSS 8.1
Remote Code Execution (RCE) SNYK-JS-SHELLQUOTE-1766506
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: react-scripts
    The new version differs by 69 commits.

221e511 Publish
6a3315b Update CONTRIBUTING.md
5614c87 Add support for Tailwind (#11717)
657739f chore(test): make all tests install with `npm ci` (#11723)
20edab4 fix(webpackDevServer): disable overlay for warnings (#11413)
69321b0 Remove cached lockfile (#11706)
3afbbc0 Update all dependencies (#11624)
f5467d5 feat(eslint-config-react-app): support ESLint 8.x (#11375)
e8319da [WIP] Fix integration test teardown / cleanup and missing yarn installation (#11686)
c7627ce Update webpack and dev server (#11646)
f85b064 The default port used by `serve` has changed (#11619)
544befe Update package.json (#11597)
9d0369b Fix ESLint Babel preset resolution (#11547)
d7b23c8 test(create-react-app): assert for exit code (#10973)
1465357 Prepare 5.0.0 alpha release
3880ba6 Remove dependency pinning (#11474)
8b9fbee Update CODEOWNERS
cacf590 Bump template dependency version (#11415)
5cedfe4 Bump browserslist from 4.14.2 to 4.16.5 (#11476)
50ea5ad allow CORS on webpack-dev-server (#11325)
63bba07 Upgrade jest and related packages from 26.6.0 to 27.1.0 (#11338)
960b21e Bump immer from 8.0.4 to 9.0.6 (#11364)
134cd3c Resolve dependency issues in v5 alpha (#11294)
b45ae3c Update CONTRIBUTING.md

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Closing this PR as it contains a breaking change. Will fix manually.

authors: timmydoza twilio-product-security


text:
How to find remote user has using landscape or portrait mode during video call

Hi team,
I am using twilio SDK in my app for app to app video call. When remote user using landscape mode, for others using portrait then I have to make sure that remote view should rotate to portrait mode. Is there any call back when remote user changes their dimension ?
SDK Version -> pod 'TwilioVideo', '~> 3.5'
FYI -> My app will support only portrait mode.
App details : Hullo: Introduce Your Network
Link: https://apps.apple.com/us/app/hullo-introduce-your-network/id1503799717

@madhu-kadyala,
There is a delegate protocol, TVIVideoViewDelegate that can be provided to TVIVideoView. This delegate will receive callbacks when the dimensions of the track it's rendering changes as well as orientation changes if TVIVideoView.viewShouldRotateContent is set to NO. Between these two callbacks, you should have the information that you need to ensure that you UI is being updated accordingly.
Let me know if you need further guidance,
Ryan

@paynerc How can I achieve orientation like how google duo, skype handling. For example, I'm using portrait mode, if the receiver using landscape mode then the remote participant video will automatically rotate in my device. But in twilio remote participant video is not changing in this scenario. I have attached sample screenshot

@ryan-rowland @paynerc Any updates? I'm also facing the same issue. I'm looking forward to a solution.

authors: madhu-kadyala musheer-ahamed paynerc

repo: twilio/video-quickstart-ios


text:
Fixes the base properties like MonoidLaws that weren't running.

Got broken in the scalatest conversion. This brings them back. Fixes #357

For reason 2), there's a way to get similarly precise output from ScalaCheck using 'property labels'. You annotate each test in your property roughly like this:
("commutative" |: a + b == b + a) &&
("associative" |: a + (b + c) == (a + b) + c)

If a condition fails, the offending label should show up in the ScalaCheck output. (I'm not familiar enough with scalatest to know if it surfaces them correctly, though.) The docs are in the User Guide, under 'Labeling Properties'.

Sorry my bad, git foo on cmd line broke stuff and closed all of these

Closed - I went through in #584 and made sure all tests are running.

authors: bkirwi ianoc sritchie

repo: twitter/algebird


text:
Add a metric to indicate average queue length in #packets pending between stmgr and each instance

This metric can be useful to detect overloaded instances.

@avflor By number of tuples, does it count all kinds of tuples? Ack tuples, fail tuples too?

@congwang Just the number of data tuples (no ack tuples). What is fail tuples? If they have failed would they be in the queue?

We have 3 metrics: # of data_tuple, ack_tuple and fail_tuple?

That would be great! We might need these metrics in the future.

Pull request is here: #1695

resolved via https://github.com/twitter/heron/pull/1695

authors: avflor congwang maosongfu objmagic

repo: twitter/heron


text:
check server start() return value in stmgr unit test

check if the server starts successfully

👍

authors: huijunwu kramasamy


text:
hulk -v option isn't working

The long-form --variable works fine, but the short-form is being ignored, resulting in output that uses the default variable name.

It seems to conflict with the "--version" default. Change 'v': ['--variable'], to 'V': ['--variable'], in bin/hulk and you should be fine using -V instead.

authors: atk natearn


text:
Fix rust pingserver integration tests

Some integration tests were disabled in #300
Update the test framework and make necessary changes so we can re-enable.

This is out-dated. Closing

repo: twitter/pelikan


text:
CMO (Chande Momentum Oscillator) calculation

Original CMO explanation from Chande's book:

To Reproduce
df = ta.DataFrame({'close': [101.0313, 101.125, 101.9687, 102.7813, 103, 102.9687, 103.0625, 102.9375, 102.7188, 102.75, 102.9063, 102.9687 ]})
df['cmo'] = ta.cmo(close = ff['close'], length=10)
df

Expected behavior
This should generate THREE cmo values - for the last three rows of data, equivalent to what is in the book.
Instead, we get:
close   | cmo
101.031 | NaN
101.125 | NaN
101.969 | NaN
102.781 | NaN
103.000 | NaN
102.969 | NaN
103.062 | NaN
102.938 | NaN
102.719 | NaN
102.750 | NaN
102.906 | 60.091
102.969 | 61.928

Remark: TA-LIB also mis-calculates CMO and returns different results from the book (and different results from Pandas-TA)...

Hello @mihakralj,
Thanks for sharing the relevant pages of CMO! 😎  This is really helpful. I do want a pure implementation of CMO but the default will always be TA Lib. Hopefully someone can help and submit a PR as a conditional option.
KJ

According to my reproduction, your CMO implementation returns different data than TA-LIB's CMO... And neither of them matches what Chanda wrote in his book...

According to my reproduction, your CMO implementation returns different data than TA-LIB's CMO... And neither of them matches what Chanda wrote in his book...

@twopirllc @mihakralj You're right that ta.cmo returns wrong values, even though that you have made mistake by trying to reproduce the results from the book. You didn't include the first input "101.031" at time 0. That's why you have got 2 results instead of 3. I'll try to make push request regarding ta.cmo() function this week.

@OskarBienko,
Cool!  Looking forward to it. 😎
Thanks,
KJ

@mihakralj, @OskarBienko
Ok. Finally had a bit of time research this.
Pandas TA is also correct when:

When talib=False
The close values in the table in the book begins with two 101.0313's, not one.

Example
import pandas as pd
import pandas_ta as ta

df = pd.DataFrame({"close": [101.0313, 101.0313, 101.125, 101.9687, 102.7813, 103, 102.9687, 103.0625, 102.9375, 102.7188, 102.75, 102.9063, 102.9687 ]})
df.ta.cmo(length=10, talib=False, append=True)
df

Output

This is true for both the main and development branches.

Unless I am mistaken, there is no difference between book CMO and Pandas TA (talib=False) CMO?
KJ

@mihakralj, @OskarBienko
Since there has been no response to confirm or deny the results of my prior results and comment, I'll be closing this issue. Reopen if you have evidence to the contrary.
Kind Regards

@twopirllc @mihakralj
Hello there, sorry for delay. I confirm that with the talib=False argument you obtain the right results. However, by default this argument is set to True, so you obtain wrong results by default. Thus, I recommend changing the default argument talib=True into talib=False. How does that sound?

authors: OskarBienko mihakralj twopirllc

repo: twopirllc/pandas-ta


text:
clean up magic parsing code

https://github.com/twosigma/beakerx/blob/b10cb28a7b1d23f61814d2005feecfa2210ae78a/kernel/base/src/main/java/com/twosigma/beakerx/kernel/commands/MagicCommandFinder.java#L45
please rewrite.
and also this line:
return !(command.replace(tokens.get(0), "").replace(" ", "").length() < 1);

this is too complicated and it is not needed. when it comes time to process the body, check if it is empty and then raise the error.

how about refactoring the magic parsing process?
for example, in two passes:

break the input into lines, recognizing if each line has magic, or is code.  breaking the cell into a list of magics and code blocks.
running the code and the magics.  the some magic lines are parsed with StrTokenizer and after that, accessed as lists.  other magic lines like %time would just pass the remainder of the line to the evaluator.

eg, I think there should only be one result to this search:
https://github.com/twosigma/beakerx/search?utf8=✓&q=StrTokenizer&type=

Actually, really need to rearchitect magics in general:

the MagicCommand class should be for the commands themselves.
there should be subclasses for the various kinds of commands.
there should be a MagicCommandExecutor for running them.

should also allow: https://github.com/twosigma/beakerx/issues/5816

🐬 🐬

repo: twosigma/beakerx


text:
feat: Mithril snapshot reader from Point

Added new functionality for the pallas-hardano crate:

read_blocks_from_point(dir: &Path, point: Point) - Creates a block's iterator starting from the provided point. Performs a binary search over the chunks to find a potential chunk that could contain the provided point. Once the potential chunk is found, it iterates over it until it reaches the specified point and returns an iterator starting from this point. If the point is not found within the chunk, an error is returned.
get_tip(dir: &Path) - Returns a Point value for the latest block. It iterates to the end of the last chunk and returns the Point value of the block.

Closes https://github.com/input-output-hk/hermes/issues/42

@Mr-Leshiy this is amazing, thank you. Very useful and thorough PR.

authors: Mr-Leshiy scarmuega

repo: txpipe/pallas


text:
Fix getFinalRecord to find the final non-path record

What this PR does / why we need it:
Fix getFinalRecord to find the final non-path record
Which issue this PR fixes:
fixes #59
Special notes for your reviewer:
Release note:

Still run into issues with the code. Might be something on my side. Will do another debugging session after grabbing some :shallow_pan_of_food:

Found a few other bugs while debugging this. Will need a fresh mind it seems. Will pick it up as soon as I can tomorrow.

Current best guess:
Code is walking down the whole type=path based records, but doesn't stop at the correct time. It will grab or try to grab a host based one. If that's not possible the fallback code isn't triggered as it would in txtdirect.go.
That leads to an empty record and an error of record type  unsupported.

Ok that partly fixes the issue.
The flow seems still wrong. But probably needs more discussion.
TXT record "example.test"
_redirect         60 IN TXT     "v=txtv0;to=http://fallback.worked.example.test;root=https://root.worked.example.test;type=path"

_redirect._       60 IN TXT     "v=txtv0;to=http://host.example.test;root=https://wildcard-root.worked.example.test;type=path;code=302"

_redirect.host    60 IN TXT     "v=txtv0;to=http://host.worked.example.test;type=host"

Visiting example.test/test leads to the following redirect flow:

(backend) get _redirect.example.test - success
(backend) get _redirect.test.example.test - no record
(backend) get _redirect._.example.test - success
(backend) get _redirect.host.example.test - success
redirect to fallback.worked.example.test

From a flow perspective:

why would it get _redirect.host.example.test?
why does it redirect to fallback.worked.example.test aka rec.To from the first path record?

What do we want chaining to do exactly?
Going through your solution and the various test cases it might just not be an answered question yet.
Probably best to discuss this first and then see how we can fix it.
@alarsyo thoughts?

I'm not sure I'm following what's the problem with the fact that it's getting _redirect.host.example.test :thinking: isn't it supposed to follow that, from the wildcard record ?
Also why does the wildcard need a root config as well ? wouldn't all requests matching the wildcard be redirected to host.example.test anyway ?

I'm not sure I'm following what's the problem with the fact that it's getting _redirect.host.example.test thinking isn't it supposed to follow that, from the wildcard record ?

Ok you are right it might make sense, but that probably depends on what we want chaining to do or if we just disallow it completely.

Also why does the wildcard need a root config as well ? wouldn't all requests matching the wildcard be redirected to host.example.test anyway?

It doesn't need it. Maybe not the best idea to use a wildcard example, could have been just another path enabled redirect, which is unrelated and therefore has the root set.
Also in the mid term we want to support adding or piping data to the redirect such as {url} etc.

I think we need to take a step back and think through the "problem" first. Will try to get that ordered in my head. Happy to take suggestions on chaining in general.

I think chaining makes TXTDirect even more powerful, but it might make some complex configs harder to understand/debug in case something goes wrong. So definitely something think about; I don't know if your use cases would make heavy use of chaining or not

Current use cases wouldn't use chaining. It came up as an edge case during testing. Definitely something that needs more use cases before we can say what makes sense. Considering this not high priority, but something to revisit and think about in parallel I think.

So for this PR. How about we disallow chaining for now. Suggestion:

get path record (as usual) -> used
encounter another path record (chaining) -> not used
log chaining currently not supported
redirect to first path records fallback

That way we just fallback and have the ability to add chaining later on.

Love how pushing something to be revisited simplifies a PR to a few lines.
@alarsyo another look please.

authors: alarsyo erbesharat stp-ip

repo: txtdirect/txtdirect


text:
Adding support for testing with Karma

Hey @tycho01 ,
I love the plugin as its saved me a ton of time when adding new pug templates on my Angular 4 project. I've run into a problem while implementing unit testing for the first time in the app. When I karma start my tests,I run each pug template through a pug preprocessor to convert it to html. During this stage I get the following, familiar errors:
24 07 2017 12:49:41.206:ERROR [preprocessor.pug]: C:/Users/bhay/Desktop/Apps.aMm.Frontend/src/app-ng/app/service-mastermind/service-mastermind.component.pug:8:37
    6|         .head serviceMastermind®
    7|       .pull-right
  > 8|         button.btn.btn-danger(*ngIf="selectedRows.length > 0" (click)="batchDelete()")
-------------------------------------------^
    9|           i.am-icon.am-icon-trash
    10|           |  Delete selected ({{ selectedRows.length }})
    11|         button.btn.btn-success((click)="addFreshUp()")

Syntax Error: Assigning to rvalue

When I add single quotes around each angular specific directive the errors go away, so what's needed is a karma preprocessor plugin to make the necessary changes to convert the pug templates back to html.
Have you tried using your plugin on any projects that required unit testing? Any consideration of writing this code as a karma preprocessor?

Thank you for your kind words.
So this is gonna be a matter of support for passing plugin config to your current way of converting Pug with Karma.
How are you doing that now? I'm seeing that karma-pug-preprocessor for one currently passes hard-coded options to Pug, so you'd have a valid point there. Is that the one you're using?

Currently, I'm not passing any config options to the karma pug preprocessor. I just define that all .pug files should get preprocessed in karma.conf.js:
preprocessors: {
      './src/test.ts': ['@angular/cli'],
      '**/*.pug': ['pug']
    },

It seems possible to chain preprocessors, so I could imagine doing something like this:
'**/*.pug': ['pug', 'pug-plugin-ng']

I see, guess it'd use that karma-pug-preprocessor by default then.
The solution here would not so much be to add extra preprocessors in the chain, but rather to configure the existing one. This appears possible, but I'm not quite knowledgeable about how this works in practice (from either user or preprocessor dev perspectives). Looks like we'd need to take it there -- we'll probably need to do a PR on it. Hopefully someone else will have more of a clue as to how this works on the Karma side.

Opened a PR at StoutLLC/karma-pug-preprocessor#4.


text:
lock the rest of the mounts behind traits

[ ] Ampithere (busted af, lock behind something high tier)
[ ] Dragon
[ ] Horse(?)
[ ] Hippogryph
[ ] Hippocampus
[ ] Tier 1 Dinos
[ ] Tier 2 Dinos

we could use incontrol to set the mob default speed to stop the busted AF mobs. I find a lot of the flying mounts have ridonculous speeds anyway and don't really offer a great exprience in any context

also added tame-locking for some mobs. will deal with amphithere speed in another release.


text:
Segmentation fault

Please let me know if more information is needed.
I am on Ubuntu 22.04 LTS
Using:

ruby 2.3.6p384 (2017-12-14 revision 61254) [x86_64-linux]
Rails 4.2.9
typhoeus (1.4.0)
ethon (0.15.0)
ffi (1.15.5)

When I run the below
> request = Typhoeus::Request.new(
    'https://bible-api.com/john+3:16',
    method: :get,
    timeout: 30
)
> request.run

Response
ETHON: Libcurl initialized
[BUG] Segmentation fault at 0x00007f346d4b3140
ruby 2.3.6p384 (2017-12-14 revision 61254) [x86_64-linux]
-- Control frame information -----------------------------------------------
c:0001 p:---- s:0002 e:000001 (none) [FINISH]
-- Machine register context ------------------------------------------------
RIP: 0x00007f346d4b3140 RBP: 0x000055bea76d4338 RSP: 0x00007ffe83e1be88
RAX: 0x0000000000000000 RBX: 0x00007f346d4b5d80 RCX: 0x0000000000000000
RDX: 0x000055bea2c5c010 RDI: 0x000055bea76d4650 RSI: 0x000055bea70eec10
R8: 0x0000000000000000  R9: 0x0000000000000000 R10: 0x00007f346d8ab650
R11: 0x00007f346d9fd0d0 R12: 0x000055bea76d4330 R13: 0x00007f346db48570
R14: 0x000055bea77f0290 R15: 0x0000000000000000 EFL: 0x0000000000010206
-- C level backtrace information -------------------------------------------
Unexpected size of .debug_line in /home/cgarndt/.rbenv/versions/2.3.6/bin/ruby
/home/cgarndt/.rbenv/versions/2.3.6/bin/ruby [0x55bea1ac3568]
/home/cgarndt/.rbenv/versions/2.3.6/bin/ruby [0x55bea1a9aa8a]
/home/cgarndt/.rbenv/versions/2.3.6/bin/ruby [0x55bea199ee22]
/lib/x86_64-linux-gnu/libc.so.6 [0x7f346e0c3520]
/lib/x86_64-linux-gnu/libssl.so.3 [0x7f346d4b3140]
-- Other runtime information -----------------------------------------------
I will try to post a comment of the full response instead of tacking it on here ...

The response is quite long. Will attach as text file.
typhoeus_response.txt

I switched over to Faraday gem.

repo: typhoeus/typhoeus


text:
Support for openai chat completions / non zero-shot prompts

Support for prompts that are beyond zero-shot would be great. To give an example, see the snippet below:
openai.ChatCompletion.create(
  model="gpt-3.5-turbo",
  messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Who won the world series in 2020?"}
  ]
)

The current examples eg. e-commerce assistant are all zero-shot.

Hi Murat!  This is actually supported right now.
Your prompt.txt (or prompt.json) would be:
[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Who won the world series in {{ year }}?"}
]

Note that {{ year }} will be substituted with the appropriate test variable.
I'll keep this issue open as a reminder to update the docs/example.

authors: muratsu typpo

repo: typpo/promptfoo


text:
Use exact default margins

Description
Currently the auto margins are computed as a factor of the page width. On A4 papers that factor happens to be 0.1190. This is, I suspect, a rounding of 2.5/21 = 119047619047619.
What that means in practice is that A4 default margins aren't 2.5cm but 2.499cm instead, due du to the rounding. I think it would be nicer if margins actually had their intended size, which in practice would require defining them by that actual size directly, rather than a ratio of the page width.
Use Case
Let's be honest, the difference between 2.5cm margins, and 2.499cm margins is incredibly negligible, and it's also trivially solvable by the user by just using explicit margins. That being said, I think it would be nice to not rely on magic numbers and floating point round trips. That would also make the default margins more standard among other documents.

I would be fine with changing the ratio from 0.1190 to 2.5/21.0, but otherwise the current behaviour is intentional because this way we also have reasonable default margins for smaller page sizes like A6. This ratio is of course not perfect for every paper size, but much better than if the default is always 2.5cm on each side.

Whatever the solution, I think the mechanism that is used to determine the margins should be exposed in the documentation. Right now you have to dig into the source to find the number 0.119

authors: Enivex edhebi laurmaedje

repo: typst/typst


text:
⚠ Tyre Pharmacy has degraded performance

In 09f699c, Tyre Pharmacy (https://tyrepharm.ru/) experienced degraded performance:

HTTP code: 200
Response time: 8747 ms

Resolved: Tyre Pharmacy performance has improved in 2477990 after 21 minutes.

repo: tyrepharm/upptime


text:
Read the current status of a connected cloud remote

It seems that for the time this issue is written down the rclone doesn't have any option or feature to read the current state of a connected remote application (google drive, dropbox). What we need is to have the option to read the current sync status of any connected remote, where status could be any information like:

connected/offline
synced/syncing
uploading/downloading

Consider using a work-around like fsnotify to watch the folder of every remote for changes or so or via checking the VFS mode.

repo: tzeikob/stack


text:
建议折叠线API：全部折叠，全部展开

建议折叠线API：全部折叠，全部展开
全部折叠后用户可以手动打开部分，进行对比数据...  便利型需求

已发布 2.3.0 和 3.3.0 更新

authors: redisviewer tzfun

repo: tzfun/vue-web-terminal


text:
feat(eco-content-menu): retrieve configurable deep attributes

Add a better way to configure attribute path from component props using lodash

Or instead of adding individual changes, another alternative could be to add the official lodash-babel plugin https://github.com/lodash/babel-plugin-lodash

Thanks @ChristianMurphy that's a great purpose, I pushed a commit for a such change. :angel:

authors: ChristianMurphy jgribonvald

repo: uPortal-contrib/uPortal-web-components


text:
"Share access" icon tooltip should be accessible onHov

Right now we are treating the "Welcome to uProxy" treatment and tooltip treatment the same.
I propose that we nix the automatic popup of the "Sharing enabled" welcome screen below, and instead create it similarly to a tooltip, wherein a user can access the contact onHov and there's no need for a "Done"/[x] button.

Currently, you nothing happens when you hover or click on the sharing icon, and there's no way to re-access the above screen

Proposed:

Tooltip will appear onHov. Shortened text and nixed triangle in accordance w/ Material Design spec http://www.google.com/design/spec/components/tooltips.html#

Implemented by the prolific @lucyhe :+1:

repo: uProxy/uproxy


text:
Ability to manually change a number of users portal or quota through manual override

This issue has split off from #43.
Primary work will be in user_update script.  At the moment, this script can only handle a single patron.
Desire is a comma-separated list of netid or to have a CSV file.

This has been escalated higher.  It might be best to have this as a feature as I don't think it's an easy fix.  Will push to develop to use temporarily until v0.12.0 is complete.

repo: ualibraries/ReQUIAM


text:
Create account should return a jwt tokent

Currently the client API returns the user's email.

Closed in #93

repo: ubclaunchpad/pinpoint


text:
Patching ranged slice of struct literals

I'm trying to write a patch to transform a ranged slice of (anonymous) struct literals. For example, I want to turn this:
for _, foo := range []struct {
  bar string
  baz string
} {
  {
    bar: "bar",
    baz: "baz",
  },
  // ...
} {
  // do something with foo
}

into this:
foos := []struct {
  bar string
  baz string
} {
  {
    bar: "bar",
    baz: "baz",
  },
  // ...
}

for _, foo := range foos {
  // do something with foo
}

I've tried minor variants of the following patch:
@@
var x identifier
@@
- for _, x := range []struct{ ... } {
  ...
- }
+ foos := []struct { ... }
+ for _, x := range foos {
  ...
+ }

which returns the following error:
0.minus.augmented:4:6: missing ',' before newline in composite literal (and 2 more errors)

@abhinav suggested adding a trailing ; to the elision, but that resulted in the same error.
I'm not sure if this is technically the same thing as #4, but I think for this case it doesn't seem practical to do it in two stages (e.g., a second match on the trailing } { would be extremely ambiguous).
Is this type of patch possible currently?

cc @abhinav @sywhang

@mway I misread the patch.
The issue was that the left and right sides of the patch did not independently make valid syntax. The []struct{ ... } is just the type, it was missing the []struct{ ... }{ a, b, c } bit.
Try this:
@@
var x identifier
@@
- for _, x := range []struct{ ... }{
+ foos := []struct { ... }{
    ...,
- } {
+ }
+ for _, x := range foos {
  ...
  }

It's a bit unreadable, but it appears to work on my local sample.
For a more readable version, the []struct{ ... }{ ... } would have to be all on one line, but right now it can't be because the ... matching is janky. I think there was an issue somewhere to give them names so that you could do something like:
@@
var x identifier
var fields, items dots // TODO: better name
@@
+foos := []struct{ fields }{ items }
-for _, x := range []struct{ fields }{ items } {
+for _, x := range foos {
  ...
  }

Which would eliminate all the bugginess with ... matching.

CC @lverma14

Thanks @abhinav, that worked. :)
As a minor thing, it does end up with the following:
foos := []struct{
  // ...
}{
  // ...
  { // last entry
    // ...
  }}

instead of
foos := []struct{
  // ...
}{
  // ...
  { // last entry
    // ...
  },
}

(note the }} instead of },\n}). This seems to be regardless of any attempt at "forcing" the trailing comma of the list initialization to be included (maybe an artifact of capturing from the ...,?). It wouldn't be a problem if this was something that gofmt or gofumpt corrected, but unfortunately they don't.

Yeah, my local experiment also showed the }}. For now, I would just sed the affected files to fix that. 😆
It's like that partly because ... is greedy about eating up comments and whitespace, so only what's necessary is left behind afterwards. There's definitely some room for improvement there.

Yeah, that's a reasonable workaround. Thanks for the help!

authors: abhinav mway

repo: uber-go/gopatch


text:
Add dependence from coveralls task to codeCoverageReport

This missing dependence was exposed by enabling parallel builds, which allowed for the coveralls task to run before codeCoverageReport.

Hrm, for some reason coveralls didn't post back a comment on this PR, but the upload of the coverage report worked: https://coveralls.io/builds/45644152

repo: uber/NullAway


text:
Add an optional First_Run_At field to StartWorkflowOptions

Summary
[Brief summary of the change, including the rationale and intended effect]
Add a new optional start workflow option called First_Run_At, which would only affect the scheduled time for first run of a workflow.
Type of Change

[x] Add new API(s)
[ ] Add new data type(s)
[ ] Add new field(s) to existing data type
[ ] Remove field(s) from data type
[ ] Remove data type(s)
[ ] Remove API(s)
[ ] Other (please provide detailed description)

Data Effect

[ ] Does it change the data stored in database? No

Detailed Description
[In-depth description of the changes made to the IDL, specifying new fields, removed fields, or modified data structures]
Add a new start workflow option called First_Run_At, which would affect the scheduled time for first run of a workflow.
Impact Analysis

Backward Compatibility: [Analysis of backward compatibility]
Forward Compatibility: [Analysis of forward compatibility]

Testing Plan

Unit Tests: [Do we have unit test covering the change?]
Yes, it would be implemented in both server and client repo
Persistence Tests: [If the change is related to a data type which is persisted, do we have persistence tests covering the change?]
Integration Tests: [Do we have integration test covering the change?]
Compatibility Tests: [Have we done tests to test the backward and forward compatibility?]

Rollout Plan

What is the rollout plan?
Does the order of deployment matter?
Is it safe to rollback? Does the order of rollback matter?
Is there a kill switch to mitigate the impact immediately?

Just tossing some thoughts while thinking through this:

client library probably doesn't care at all about this field, so:

new clients starting + old clients working => field is silently ignored which is fine, clients don't decide when things happen.
old clients starting + new clients working => field is not set and empty values are ignred, which is fine.

[ ] new RPC request to old servers: silently dropped, possibly an issue (but only during rollout and rollback)

is our plan to just have this rolled out in server well before client-side use, or should we try to do something to reject newer requests that use the field?

old request to new servers: seems fine :thumbsup:

a bit more questionable (though I realize this is just rpc, not storage, but it implies storage of some kind...):

[ ] new request to new servers -> rollback: what will this do to task processing, replication, etc?

how will old server instances behave when this field is silently ignored?
do we need to consider this a "do not roll back past this point" marker?

During the rollout, we will roll out the change to all the servers completely before rollout to client.
In terms of rollback the server to older version, the compatibility should be just fine as the field would be dropped by the old server version.

repo: uber/cadence-idl


text:
Dockerhub builds missing

the ubercadence/web dockerhub is missing 3.19.0 and 3.19.1 releases.
https://hub.docker.com/r/ubercadence/web/tags

Hi @AngerM ,
I have uploaded v3.19.1 to docker hub now:
https://hub.docker.com/layers/ubercadence/web/3.19.1/images/sha256-34f01558ce2a7d6274775e5e607c877e30ef1ede181a514b46215634603ccb7f?context=explore
Thanks!

Hi @AngerM ,
I have uploaded v3.19.1-slim which is much smaller in size now:
https://hub.docker.com/layers/ubercadence/web/3.19.1-slim/images/sha256-1a3bc526ce56905d7a1674a64f73a2e4b053408bce55575f7b9425df64e0c384?context=explore
Thanks!

authors: AngerM just-at-uber

repo: uber/cadence-web


text:
Add Documentation for dynamicconfig: value type and allowed filters

What changed?
Add Documentation for dynamicconfig: value type and allowed filters

Why?
In addition to https://github.com/uber/cadence/pull/4129
User needs to know the type info and allowed filters in order to use dynamic config

How did you test it?
No test needed. only comments

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 3f9f438e-d4ad-43c7-b488-b70339ea9e0d

0 of 0   changed or added relevant lines in 0 files are covered.
80 unchanged lines in 9 files lost coverage.
Overall coverage decreased (-0.005%) to 59.731%

Files with Coverage Reduction
New Missed Lines
%

service/history/execution/mutable_state_task_refresher.go
1
75.29%

common/task/fifoTaskScheduler.go
2
87.63%

service/history/execution/mutable_state_builder.go
2
69.85%

service/history/task/transfer_standby_task_executor.go
2
90.77%

service/matching/matcher.go
2
91.46%

common/persistence/cassandra/cassandraPersistence.go
3
52.8%

service/history/queue/timer_queue_processor_base.go
4
78.6%

service/history/execution/context.go
6
67.3%

common/persistence/cassandra/cassandraPersistenceUtil.go
58
89.35%

Totals

Change from base Build 3f1f4ec1-8d26-4705-8472-3412b0ddb4d4:
-0.005%

Covered Lines:
87736

Relevant Lines:
146886

💛  - Coveralls

authors: coveralls longquanzheng

repo: uber/cadence


text:
Scanner to purge deprecated domain workflows

What changed?
Added a new invariant that checks if the associated domain to the execution is deprecated or deleted.

Why?
The changes were made to enable identification of the workflows that are associated with the deprecated or deleted domains and need deletion.

How did you test it?
Updated existing unit tests and tested locally. A variant of this is running in dev environment.

Potential risks
The change is independent of other invariant flows. Unless this invariant is triggered the associated workflows remain intact. There is a hard check on domain status which has to be passed in order for the workflows to be deleted.

Release notes
NA

Documentation Changes
NA

Pull Request Test Coverage Report for Build 0186c374-7b2c-4193-8459-cd632b0fff86

23 of 59 (38.98%)  changed or added relevant lines in 3 files are covered.
92 unchanged lines in 13 files lost coverage.
Overall coverage increased (+0.02%) to 57.113%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/reconciliation/invariant/concreteExecutionExists.go
0
1
0.0%

common/reconciliation/invariant/openCurrentExecution.go
0
1
0.0%

common/reconciliation/invariant/inactiveDomainExists.go
23
57
40.35%

Files with Coverage Reduction
New Missed Lines
%

common/persistence/historyManager.go
2
66.67%

common/task/fifoTaskScheduler.go
2
85.57%

common/util.go
2
52.31%

service/history/task/transfer_active_task_executor.go
2
72.15%

service/history/task/fetcher.go
3
91.75%

common/persistence/serialization/parser.go
4
63.91%

common/persistence/serialization/thrift_decoder.go
4
57.14%

service/history/queue/timer_queue_processor_base.go
4
78.15%

service/history/task/transfer_standby_task_executor.go
4
86.82%

service/history/decision/task_handler.go
5
72.33%

Totals

Change from base Build 0186c32e-67a4-4519-a2e5-d52df0bbe0b5:
0.02%

Covered Lines:
85269

Relevant Lines:
149299

💛  - Coveralls


text:
Emit metrics when transfer tasks could be ratelimited

What changed?
Adding call to workflowID cache based ratelimiter during transfer task execution

Why?
to get metrics on potential hot shards and investigate when requests will be ratelimited

How did you test it?
tested locally and added unit tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018d8e33-9b21-44c1-94c5-101a0f3c9dfd

0 of 9 (100.0%)  changed or added relevant lines in 6 files are covered.
34 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.07%) to 62.721%

Files with Coverage Reduction
New Missed Lines
%

service/history/execution/mutable_state_builder.go
2
68.64%

common/persistence/statsComputer.go
3
95.36%

common/task/fifo_task_scheduler.go
3
84.54%

service/history/queue/timer_queue_processor_base.go
3
77.82%

service/matching/taskListManager.go
5
80.2%

service/history/task/transfer_standby_task_executor.go
6
87.04%

common/persistence/sql/workflowStateMaps.go
12
83.62%

Totals

Change from base Build 018d8cd7-6838-492b-a76e-894fb1359925:
0.07%

Covered Lines:
92286

Relevant Lines:
147137

💛  - Coveralls


text:
Fix comment in workflow id cache config

What changed?
Comment fixed in workflow ID cache config

Why?
It was an error made while changing the flags

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018da804-0a6c-4359-b260-bf972155cff8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
80 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.02%) to 62.787%

Files with Coverage Reduction
New Missed Lines
%

common/membership/hashring.go
2
84.05%

common/task/fifo_task_scheduler.go
2
85.57%

service/history/execution/mutable_state_util.go
2
37.63%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.55%

service/history/task/transfer_standby_task_executor.go
4
86.6%

service/history/task/fetcher.go
5
85.57%

service/history/task/cross_cluster_task_processor.go
8
80.79%

service/history/execution/mutable_state_task_refresher.go
14
63.61%

common/persistence/nosql/nosqlplugin/cassandra/workflow_parsing_utils.go
20
83.06%

common/persistence/sql/workflowStateMaps.go
20
83.62%

Totals

Change from base Build 018da5f3-3627-4ce7-a640-1301a5169ce8:
0.02%

Covered Lines:
92613

Relevant Lines:
147503

💛  - Coveralls


text:
Fix undefined behavior in areNeighborCells

Expected to fix #676.

Coverage increased (+0.004%) to 99.034% when pulling dfe8e3f93c6121e1976731684d27daeb06461a4c on isaacbrodsky:directed-edge-undefined-areneighborcells into d8e8606caf8221b5dfe68b8b199e732269de5c71 on uber:master.

authors: coveralls isaacbrodsky


text:
hoodie-cli hdfsparquetimport failed with 'path' must not be null error

while trying to import an existing parquet file using hoodie-cli hdfsparquetimport  I got the following error
Command failed java.lang.IllegalArgumentException: 'path' must not be null.
'path' must not be null.
java.lang.IllegalArgumentException: 'path' must not be null.
    at org.apache.spark.launcher.CommandBuilderUtils.checkNotNull(CommandBuilderUtils.java:234)
    at org.apache.spark.launcher.SparkLauncher.setPropertiesFile(SparkLauncher.java:165)
    at com.uber.hoodie.cli.utils.SparkUtil.initLauncher(SparkUtil.java:49)
    at com.uber.hoodie.cli.commands.HDFSParquetImportCommand.convert(HDFSParquetImportCommand.java:73)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
    at org.springframework.shell.core.SimpleExecutionStrategy.invoke(SimpleExecutionStrategy.java:68)
    at org.springframework.shell.core.SimpleExecutionStrategy.execute(SimpleExecutionStrategy.java:59)
    at org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
    at org.springframework.shell.core.JLineShell.promptLoop(JLineShell.java:533)
    at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
    at java.lang.Thread.run(Thread.java:745)

On a closer look, it looks like system.getenv is missing a parameter and results in null.
https://github.com/uber/hoodie/blob/master/hoodie-cli/src/main/java/com/uber/hoodie/cli/commands/HDFSParquetImportCommand.java#L72

@ovj - Can you take a look at this please?

yeah. let me look at it.

@alunarbeach quick question. Did you look at this? https://jaceklaskowski.gitbooks.io/mastering-apache-spark/content/spark-properties.html Have you set SPARK_CONF_DIR or SPARK_HOME environment variable from where you are running spark job?

I used Hoodie-cli.sh to launch the admin console and executed this command. By default it should set spark_conf_dir to /etc/spark/conf. Let me check

On May 16, 2017, at 1:10 PM, ovj notifications@github.com wrote:
@alunarbeach quick question. Did you look at this? https://jaceklaskowski.gitbooks.io/mastering-apache-spark/content/spark-properties.html Have you set SPARK_CONF_DIR or SPARK_HOME environment variable from where you are running spark job?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @ovj.
After I added the following export statements in  ./hoodie-cli.sh it worked.
I had to set both SPARK_HOME and SPARK_CONF_DIr though.
export HADOOP_CONF_DIR="/etc/hadoop/conf"
export SPARK_HOME="/usr/lib/spark"
export SPARK_CONF_DIR="/etc/spark/conf"

@ovj do you want to change the hoodie-cli.sh?

hum. probably not. These are usually environment variables you need to set as per environment. @vinothchandar @prazanna - what you guys think? create hoodie-env.sh?

These configs are good defaults. So we can add it to the hoodie-cli.sh
export HADOOP_CONF_DIR="/etc/hadoop/conf"
export SPARK_HOME="/usr/lib/spark"
export SPARK_CONF_DIR="/etc/spark/conf"
These should be documented as well. These are standard hadoop and spark settings that should be set by the user as part of the hadoop user bash profile.

authors: alunarbeach ovj prazanna

repo: uber/hoodie


text:
google.protobuf problem

Describe the bug
when i tried to train my ludwig model, error rasied, ModuleNotFoundError: No module named 'google.protobuf'
but i can fine protobuf in tensorflow
Please provide code, yaml definition file and a sample of data in order to entirely reproduce the issue.
Issues that are not reproducible will be ignored.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

OS: [e.g. iOS]win10 pro
Version [e.g. 22]
Python version 3.7
Ludwig version 0.2.1
tensorflow-gpu 1.14

Additional context
Add any other context about the problem here.

i reinstall everything and solve my problem......

This was likely a tensorflow installation problem

repo: uber/ludwig


text:
gpu training allocates too much memory

Maybe I missed something, but trying to get the image classification example going, i always end up with the following error just after the training starts:
Allocator (GPU_0_bfc) ran out of memory trying to allocate 10.99GiB.  Current allocation summary follows.
No matter what images I use, or if I do it with resize_image in the input_features or bigger or tinier width/height, it always wants to allocate those 10.99GiB (which my GTX1080 hasnt :))
Even when using --gpu_fraction it wants those 10.99GiB (tried values from 0.1 to 0.5)
I'm a tensorfloor noob, so maybe I just got something completely wrong.
Definition:
_input_features:
-
name: image_path
type: image
encoder: stacked_cnn
resize_image: true
width: 28
height: 28
output_features:
-
name: class
type: category_

I had a similar issue, and tried the --gpu_fraction setting to no avail. Ended up addressing it by adjusting the batch size, like this (note the lack of dashes in the training section):
`input_features:
name: image_path
type: image
encoder: stacked_cnn

name: some_number
type: numerical

output_features:
name: label
type: category

training:
batch_size: 64
`

So, TensorFlow by default allocates all the memory on the GPU, and then has an internal allocation system. The fact that it runs out of memory means that there is not enough memory on your GPU for the size of both weights and activation tensors you are computing.
--gpu_fraction instructs TensorFlow to allocate only that fraction of the memory at the beginning of the training, but then it can increase that amount elastically as needed. In your case it need more than your full memory, so it obviously needs also more than the fraction you specify.
You have a few solutions, to use in combination:

Resize your images
decrease the number of filters of the convolutional stack (admittedly the default values are a bit high for most GPUs, in the next release I'm going to decrease them)
decrease the batch size
A combination of these will decrease memory consumption and let you train your model.

I'm closing this, let me know if this doesn't solve your problem.

authors: baderth ksteinfe w4nderlust


text:
guide construction with poutine magic

The problem: it can be a drag to write simple guides for VI, often requiring duplicated code from the model. What's more, it's easy to get the names wrong so guide and model don't line up. We certainly want to have available the option of providing a guide in complete detail, but it would be nice to have more compact ways to make standard guides.
The proposal: taking a queue from poutine.lift, which shifts the type of a param site to sample while also inserting additional computation, we should be able to make poutine.parametrize that intercepts the parameters to the distribution at a sample site, inserting a computation to get them (which might include new param sites).
I imagine this would look something like:
def model():
    x = pyro.sample("foo", dist, params)
    ...

def foo_params(dist, old_params):
    guide_dist = dist  #explicitly provide dist, in case we want to guide with a different dist
    guide_args = pyro.param("foo_params", ...)  #the trainable params, dist args computed from them
    return guide_dist, guide_args

guide = pyro.parameterize(model, {"foo": foo_params})

Optimize(model, guide,...)

much as in lift, in addition to the simple map from names to param fns, we could instead provide a function from name and site info (dist etc) that computes params. it should be straightforward to use this to make an auto-mean field guide: guide = pyro.parameterize(model, make_mean_field).
using parameterize to provide amortized guides may require some extension. i'm not sure the correct interface in general, but simply providing the args of the model to the params function is a start:
def model(data):
    x = pyro.sample("foo", dist, params)
    ...
    pyro.observe(dist, data)

def foo_params(dist, old_params, fn_args):
    guide_dist = dist
    amortized = pyro.module("bar", ...)
    guide_args = amortized(fn_args)  #fn_args will be bound to the arguments of the model/guide
    return guide_dist, guide_args

guide = pyro.parameterize(model, {"foo": foo_params})

is there a more general version? does this need to change to play nicely with irange/iarange?
note: the parameterize poutine yields a style similar to the WebPPL method of providing guides in-line in the model. i think doing this as operations on a model fn is more composable though.

This has roughly been implemented in the pyro.contrib.autoguide module.

authors: fritzo ngoodman

repo: uber/pyro


text:
Question: Where/How is uReplicator deployed so that it can talk to clusters across multiple AWS regions?

I saw this diagram from one of the presentations given this year.
Where/How is uReplicator deployed so that it can talk to clusters across multiple AWS regions?

I am trying to do a POC similar to https://github.com/uber/uReplicator/issues/158 but using the first approach that @xhl1988 mentioned:

(Based on your description, seems this is not your case, but I still want to call out as this is what we are doing now)
If your message can be filtered based on src cluster info inside message body/header, you can aggregate the message into the same topic name in the other cluster.
pros: save disk space since only two copies for each message.
cons: consumer need to do filter if they only want local data

For example, aggregate Topic A in Cluster 1 (us-east-1) and same Topic A in Cluster 2 (us-west-2).
Thanks,
Sangjin Shin

Hi @sangjin-shin-sp , we deploy the uReplicator in the same region as the destination cluster if that's what you are asking. In your case, we would recommend to deploy one uReplicator cluster in us-east-1 to replicate topic A from cluster 2 to cluster 1 and another uReplicator cluster in us-west-2 to replicate topic A from cluster 1 to cluster 2.

Thanks!

repo: uber/uReplicator


text:
BZ1299619: Business Central Repo Clone Fails To Clone SCP Style SSH URLs

See https://bugzilla.redhat.com/show_bug.cgi?id=1299619
This PR upgrades uri.min.js to support git@github.com:<user>/<repository>.git style URL validation and support for SSH Passphrases when cloning. I cannot see any feasible way to write a test for this - although I've confirmed operation with kie-drools-wb (both cloning a github Repository with SCP URL and cloning a Workbench repository with ssh://user@localhost:8001/uf-playground).
Steps to test:-

Create a new Repository at github.com
Create an SSH key; see here (a)
Add your SSH key to github; see here
Run kie-drools-wb (or which ever you fancy)
Clone a Repository using the git@github.com:<user>/<repositorty>.git URL

(a) IF you entered a passphrase when generating your public key you'll need to specify the passphrase with System Property org.uberfire.nio.git.ssh.passphrase

@porcelli You're probably best to review...

Looks like the uri.min.js is a generated file. Just wondering we need to commit it in or if the build recompiles it each time?

+1
uri.min.js can be removed later. It is already in. If it even needs to be removed.

@Rikkola it comes from here. It was included in the previous version; so I simply updated... At the moment it's considered a GWT TextResource and injected into the host page. If we removed from the Uberfire module we'd need to add a <script> element in each webapp's host page. This approach, whilst bundling the source in our source, means it's self-contained and "black boxed".

@psiroky @mswiderski Could you please merge when you get a chance... (I need to submit additional PRs for 6.4.x and 6.3.x once merged into master).

@manstis I don't have access to push to uf repo :(

isn't passphrase per certificate? If yes, wouldn't this limit users to operate ssh (scp style) with a single remote entity?
Sent from my iPhone

On Feb 25, 2016, at 7:14 AM, Maciej Swiderski notifications@github.com wrote:
@manstis I don't have access to push to uf repo :(
—
Reply to this email directly or view it on GitHub.

@porcelli Damn you.. don't you have some Execution Server tests to write? ;)
You are of course correct, but here's my take on it: The public certificate is to set up a trust relationship between a source (the server running the Workbench) and other end-points (git servers/github repositories). So a single "server" public certificate is required that could be added to different end-points and hence a single pass-phrase.
If the Workbench ran under different user accounts, depending who's logged in, we would need to provide the means to interactively request a pass-phrase as the SSH key resolution would be different per-user.. but we don't work like this. The Workbench makes clone requests as a single privileged user (i.e. "the system"). Or, if "the system" wanted to identify itself differently for different end-points we'd need to support the same... but this, IMO, would be a questionable requirement.

@manstis I understand. Althought I don't think this is the ideal solution, it might be good enought for this particular use case (that originated BZ).
I just would make it clear on docs.
(the real solution for that would be way more complex, basically enabling UF to mmanage certificates and passphrases, what for sure would need a lot of careful as it implies in possible security flaws).

authors: Rikkola manstis mswiderski porcelli

repo: uberfire/uberfire


text:
Map in hidden div

Hello
I am using the sample "draggable" in a hidden div , but the map is not correctly shown (only half).
I have read that I need to input the code --> google.maps.event.trigger(map, 'resize')
But where do I put this piece of code? I can get the map working in hidden areas.
Thanks
Kelson

I would say it works with no issues, if it makes some issues, you should call the map resize.
One thing to remember: be sure that you are passing the correct map  object, getting that object is really tricky.
This is how I am making the call:
 google.maps.event.trigger($('#geoComplete').geocomplete('map'), 'resize');

I  am leaving this comment for others, even it came too late.

authors: Arwany kelsjc

repo: ubilabs/geocomplete


text:
fix: hide accent-color errors

Redirecting the error output to /dev/null.
Since this is my first PR on uBlue I wanted to ask if the changes will reflect on Aurora and Bazzite? I assume that I have to open a PR on Bazzite too.

Bazzite doesn't ship a gts/f40 so they're already on gnome 47. Thanks for the PR!

repo: ublue-os/bluefin


text:
Nvidia driver not working for flatpaks

Hi after the release of the stable version of the nvidia proprietary driver i.e. 560.35.03 and after the flatpak driver also being updated to the correct version, it seems that I can't use the nvidia GPU for anything flatpak related.
System Details Report

Report details

Date generated:                              2024-08-24 16:35:38

Hardware Information:

Hardware Model:                              Lenovo IdeaPad Gaming 3 15ACH6
Memory:                                      16.0 GiB
Processor:                                   AMD Ryzen™ 5 5600H with Radeon™ Graphics × 12
Graphics:                                    AMD Radeon™ Graphics
Graphics 1:                                  NVIDIA GeForce RTX™ 3050 Laptop GPU
Disk Capacity:                               1.5 TB

Software Information:

Firmware Version:                            H3CN32WW(V2.02)
OS Name:                                     Fedora Linux 40.20240822.0 (Silverblue)
OS Build:                                    (null)
OS Type:                                     64-bit
GNOME Version:                               46
Windowing System:                            Wayland
Kernel Version:                              Linux 6.10.5-200.fc40.x86_64

Does anyone have a fix for this I'm so confused as to why this isn't working

Same issue on Fedora Silverblue 39, bluefin-dx-nvidia:gts image.
Switch to xorg for a temporary fix until this gets resolved. After it gets resolved, disable updates related to the issue unless you want your system broken every time Nvidia drivers gets an update. For me 5 times this year already.

Switch to xorg for a temporary fix until this gets resolved.

This didn't work for me, the nvidia GPU works fine for system apps it's just flatpaks that don't have access to it for some reason, even though the GPU drivers are the same version.
Not sure how it is worked for you as I don't think this is wayland issue.

Seems like another nvidia and flathub related issue, adding link for future reference.
Closing this, as it's not related to ublue
Unable to see Nvidia GPU in the lastest update

Seems like another nvidia and flathub related issue, adding link for future reference.
Closing this, as it's not related to ublue
https://github.com/flathub/org.freedesktop.Platform.GL.nvidia/issues/288

repo: ublue-os/hwe


text:
inter pod container to container networking does not work

Inspecting services
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Service snap.microk8s.daemon-etcd is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system info
  Copy network configuration to the final report tarball
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Inspect kubernetes cluster

/snap/microk8s/499/inspect.sh: line 100: ufw: command not found
Building the report tarball

i am having a deployment with 2 containers.
however if i exec into it (via dashboard) - i am not able to ping/curl the container
like exec int api
telnet blackfire

DNS failed

containers reach the internet, if i put a serivce in front i can reach containers but containers inside a pod cannot reach each other.
is there any known issue?

nevermind, after going through docs, inter container comm needs to go via localhost