Personal Life tests (and other goodies)

@molliem — definitely want your feedback on this, I've made quite a few decisions when implementing that are pending your approval!
This begins to address #9.

Reorganized module
I moved things around slightly to enable modules to import common utilities like Document. I arbitrarily named the python module genderbias — obviously, that's changeable!
In particular, I moved tests out of the same file as Document, and gave the Document class its own file in document.py. That way, subodules, such as genderbias.personal_life, can reference Document if needed. @neiljp, I know you were the latest to touch that code — please feel free to yell at me if I misunderstood or misinterpreted your architecture!
Documents from strings
Now, you can also create a document by passing a string directly; use Document("my sentence") or Document("./my-file.txt").
Tests directory
I moved all tests to live in the tests/ top-level directory in pursuit of making it easier to keep track of what tests need to be run for what. I also switched the test-runner to nose, which I don't feel strongly enough about to make waves, if anyone else feels strongly that pytest is the right way to go.
My favorite thing about nose + unittest is that it's standard-library, so everyone's guaranteed to have it, and now running nosetests in the root directory will automatically hunt down all tests and run them and print a nice report. You can also run ./test.sh in case we decide to add extra functionality or commandline flags here.
pipenv
I also added support for pipenv, which I think will make life a lot easier, especially as we have more people contributing with more dependencies. But this is strictly opt-in, so you can totally ignore. I also added a companion requirements.txt so new users can pip install -r ./requirements.txt to get all of the packages we use. (It took me a bit to track down dependencies so I thought I'd save others the hassle.)

Please let me know if I jumped the gun on any of these things! Not trying to be presumptuous, just trying to maximize helpfulness :)

If you'd like, I can also set us up with CircleCI or another service that will automatically run tests on new pull-requests so that maintainers can see at-a-glance if the new contribution breaks anything.

I've made a few more changes to make this more usable from the start. In particular, I reorganized this into a Python module:
bin/
    genderbias

genderbias/
    personal_life/
    effort/

What this means is that you can now access a particular check using import genderbias.personal_life.
I also added a more consistent architecture for checkers so that it'll be more obvious to future developers how to create something that is perfectly harmonious with the rest of the existing library.
A Detector class (genderbias/detector.py) accepts a document and runs its own flavor of check: So there's a PersonalLifeDetector, and I ported @cmd16's work into a EffortDetector. (Catherine, please let me know if I did a bad job!)
You can create a Document using @neiljp's work, and pass it into the Detector like so:
from genderbias import Document, ALL_DETECTORS

letter = """
This lady is good. She's basically the lab mother!

Signed,
Jerk M.D.
"""

doc = Document(letter)

flags = []
for detector in ALL_DETECTORS:
    flags += detector().flag_words(doc)

print("\n".join(str(f) for f in flags))

And this will return a list of issues based upon ALL of the issues anyone has ever implemented.

This seems like a pretty common use-case, so I converted this into a command-line-executable script, again borrowing syntax from @cmd16.
I ran this on a test file; this is what happens:
genderbias --file ./example_letters/letterofRecM
[0-0]: This document has a high ratio of words suggesting effort to words suggesting concrete accomplishment.
[674-685]: Effort vs Accomplishment: The word 'willingness' tends to speak about effort more than accomplishment. (Try replacing with phrasing that emphasizes accomplishment.)

Woo! It outputs a list of issues, and suggestions!
To get yours to do this too:

Check out my branch (git clone https://github.com/j6k4m8/gender-bias/ && cd gender-bias && git checkout personal-life)
Install this module; pip install -e . from inside the top-level directory. This will install the genderbias package so you can access it from Python, and it will also add the genderbias tool to your command-line.
Use the tool! genderbias --file [your file]

Hi @j6k4m8, This looks like some great changes, but a lot in one pull request, and only in one commit? (except the contributor detail)
I'm aware this is an early/new project, but would it be reasonable for you to split the changes into many much smaller commits that are easier to assess? Even separate PRs. You've also ended up adjusting the code somewhat to do more than just the original issue, which again is great for covering a lot of ground - but can end up with a lot of comments/reviews/changes, based on my previous experience.

Agreed — am already working on a split up version!! Small PRs always
better. But my implementation for personal life checks branches from the
module style architecture so I left this here temporarily as a manifest of
all proposed changes. I'll tag you in the more atomic PRs if you'd be
willing to do some code review before merge?
On Thu, May 17, 2018, 11:35 PM Neil Pilgrim<EMAIL_ADDRESS>wrote:

Hi @j6k4m8 https://github.com/j6k4m8, This looks like some great
changes, but a lot in one pull request, and only in one commit? (except the
contributor detail)
I'm aware this is an early/new project, but would it be reasonable for you
to split the changes into many much smaller commits that are easier to
assess? Even separate PRs. You've also ended up adjusting the code somewhat
to do more than just the original issue, which again is great for covering
a lot of ground - but can end up with a lot of comments/reviews/changes,
based on my previous experience.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/molliem/gender-bias/pull/22#issuecomment-390084375,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqVB0hM2riJIr2ad0BJcf4p-Ii4V3LGks5tzkFlgaJpZM4UD8XG
.

I'm definitely up for some code review to help things along.
Do you have a plan as to how to break it down? Some changes are likely more straightforward than others, but there are a lot of primary design decisions/changes you've made. For that reason there could be a lot of dependencies between PRs/commits - though that's the challenge with doing a lot of development in larger PRs/commits before pushing/reviewing, I suppose ;)

Closing this one in favor of #23, #24, and (a final Personal Life implementation, probably #25)


void-dom-elements-no-children throws a TypeError when installed from the current master branch.

Hey there! I hate to be a bother, but I just tried installing this plugin from GitHub, overeager to see if JSX indentation had been improved, and ran into a little trouble linting one of my source files. The void-dom-elements-no-children rule is throwing a TypeError on line 107:
Cannot read property 'value' of undefined
TypeError: Cannot read property 'value' of undefined
    at EventEmitter.CallExpression (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/eslint-plugin-react/lib/rules/void-dom-elements-no-children.js:107:34)
    at emitOne (events.js:101:20)
    at EventEmitter.emit (events.js:191:7)
    at NodeEventGenerator.enterNode (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/eslint/lib/util/node-event-generator.js:39:22)
    at CodePathAnalyzer.enterNode (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/eslint/lib/code-path-analysis/code-path-analyzer.js:607:23)
    at CommentEventGenerator.enterNode (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/eslint/lib/util/comment-event-generator.js:98:23)
    at Controller.enter (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/eslint/lib/eslint.js:928:36)
    at Controller.__execute (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/estraverse/estraverse.js:397:31)
    at Controller.traverse (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/estraverse/estraverse.js:501:28)
    at Controller.Traverser.controller.traverse (/Users/daniel/Repos/Ignota/rupertsberg/node_modules/eslint/lib/util/traverser.js:36:33)

Logging node.arguments shows that it's an empty array just before the crash, but honest I don't know nearly enough about your lovely linter's deep magic to say any more than that. Please let me know if it'd be helpful to Gist the source file, though, or if I can furnish any other information I've got. Disabling the rule in my ESLint config stops the crash for now.

It would absolutely be helpful to gist the source file it crashes on, thanks!

Sure thing! Went ahead and dumped the JSX, my .eslintrc.yml, and the error here: https://gist.github.com/phyllisstein/04036a187aa4c2d4195a67cefb4170cb. Let me know if you need anything else!

@phyllisstein I assume https://gist.github.com/phyllisstein/04036a187aa4c2d4195a67cefb4170cb#file-button-jsx-L112-L119 is the problem - if you remove https://gist.github.com/phyllisstein/04036a187aa4c2d4195a67cefb4170cb#file-button-jsx-L113 does the problem go away? (if not that, this?)

So I did a little ham-handed investigation and started deleting lines blindly. Turns out it's the handleClick function? Including any of the lines in the range https://gist.github.com/phyllisstein/04036a187aa4c2d4195a67cefb4170cb#file-button-jsx-L58-L64 causes it to throw, whereas deleting it entirely seems to work around the issue. Heaven knows what that portends though.

Interesting - probably because it's an arrow function class property. If instead (which would be much more performant) it was a true instance method, and you did this.handleClick = this.handleClick.bind(this) in the constructor, I suspect it'd work.
Thanks though, this should be very helpful to fix the bug.

which would be much more performant

Why exactly? You still create a bound function in constructor, that's roughly what arrow function property compiles to

Yes, in the constructor once, instead of thousands of times once per render.

I thought if the arrow function is a class property, it is also only computed once?
class Foo extends Component {
  myArrowFunc = () => { ... }
}

Din't think @Hypnosphi is talking about arrow functions within render().

Yes, that's true. But at that point the meat of the function isn't in an optimized prototype method, its newly created on every render. Constructor-bound prototype methods are the best approach.

I didn't know that, thanks! Fixes an incorrect belief of mine.

´´´
class Foo {
myArrowFunc = () => { ... }
}
´´´
Excuse me, but I don't see any rendering here. Did you mean "on every instance creation" instead?

@Hypnosphi yes, you're right that your example isn't about the render path. However, https://github.com/yannickcr/eslint-plugin-react/issues/1101#issuecomment-297098189 still applies.


When deleting a backup using an API, a timeout occurs.

What would you like to be added?
Hello,
When managing backups via API, if the backup file size is large (e.g., 200GB), the deletion process can take several minutes, and depending on the network configuration environment (such as using a Load Balancer), timeouts may occur. Is it possible to add an async mode for operations like CreateBackup and CreateRestore to address this issue?
Why is this needed?
If an HTTP timeout occurs, a failure response is received even if the backup deletion is proceeding normally.
Anything else?
No response

Got it, it is a nice to have feature. Will support it @ian-lss


[Fix] Event handlers are not properly deregistered

What was changed

Removes event listeners
Closes local servers
Clears timeouts
Throws additional errors
Adds content security policy
Etc.

Why?

Addresses some of the TODO comments in the code.
Checklist

Closes
https://github.com/temporalio/vscode-debugger-plugin/issues/21
How was this tested: TBD

Any docs updates needed? n/a

@bergundy I've made a few updates based on your comments. If there are still things that need to be addressed I'll open up a follow-up PR.

I checked the 2 commits you pushed, they're not what I had in mind. Let's sync on this.


Added + Send to InfluxDbClient.query()

Added + Send to the return type of InfluxDbClient.query() so it can be used with tokio::spawn() as demonstrated here: https://github.com/aisrael/tokio-influxdb/blob/master/src/main.rs#L11
Fixes #11

Hey, thanks for this PR! Great the solution worked for you.
Would you mind adding the + Send to all the other places as well, so that all of the futures this crate exposes can benefit from being Sendable?

Fixed in #32


⚠ Bofrost.lu has degraded performance

In 9070d5c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1168 ms

Resolved: Bofrost.lu performance has improved in b759e3b after 6 minutes.


New and improved/enhanced vid-to-gif function

Based on the gif plugin but with many additions.
Added support for giflossy by @pornel (drop-in for gifsicle)
Added support for gifski (also by @pornel)
Added getopt parsing to allow lots of options, such as tweaking quality, FPS and tagging of resulting GIF files by different qualities and options used

Great idea! Does this replace the existing gif plugin? https://github.com/Bash-it/bash-it/blob/master/plugins/available/gif.plugin.bash
If so, is it a good idea to do this in a new plugin file? Why not replace the existing one?

It is based on it and supplants it, but breakes commandline option compatibility, so it's no longer a drop-in replacement.

It supports multiple files and multiple quality options, so parameters are no longer positional.
it changes the name "gifify" so as not to clobber a package by that name that is related but not identical in function (links in the code).

So I think it deserved to either be added to the current plugin or replace it, But I leave it to you, as the orchestrator, to pick which way it should go. If you think adding it to gif with or without removing the one function that's already in it makes sense, we can do that too, or kill the old gifify function, or rewrite it as a wrapper for v2gif for backwards compat. All's good :)
During the night I thought I'd add one more feature though, a warning if the file size is over a certain size, I might add a commit soon. This makes sense to me since GIF is a horribly bloated standard, but as long as services like Twitter and WhatsApp don't support webm but also block GIFs over 5MiB, we may as well make tools like this helpful :)

I'm not sure how many people are actually using the old function - no idea.
From my perspective (and since I added the original function, if I remember correctly), I wouldn't mind replacing it with your new code. If we break people's workflow, they will hopefully either adopt the new one, or speak up, and then we can think about creating a wrapper.
I think having one plugin that does this work is the way to go - I don't want to add yet another plugin that has 90% overlap with another one...

so you are giving your blessing to rename this from v2gif to just gif?

Thanks!

Sure. Though I just saw I made a typo in the username :-)
On to destroy other plugins' dreams of living a long happy life...

Keep'em coming!


gnupg21: 2.1.18 -> 2.1.19

Motivation for this change
This PR is against staging branch since the libgpg-error update causes a mass rebuild.
Things done

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

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Works fine for me and the YubiKey issue on macOS is fixed in this version indeed.


iOS crash:  malloc: *** error for object 0x100000105480379: pointer being freed was not allocated

SIGABRT
BlueWallet > BlueWallet(5532,0x16cb6f000) malloc: *** error for object 0x100000105480379: pointer being freed was not allocated

Steps to reproduce:

start the app
connect to TOR, do something (HTTP request, socket interaction etc)
lock iphone
wait 2 minutes
unlock iphone
app crashes

stacktrace I got from our sentry:
SIGABRT: BlueWallet > BlueWallet(5532,0x16cb6f000) malloc: *** error for object 0x100000105480379: pointer being freed was not allocated

  ?, in core::ptr::drop_in_place
  ?, in tcp_stream_destroy
  File "Tor.swift", line 265, in Tor.startTcpConn
  File "<compiler-generated>", in Tor.startTcpConn
  File "Tor.swift", line 282, in Tor.startTcpConn
...
(15 additional frame(s) were not displayed)

looking at timestamps here, looks like waiting is not necessary, crash happens when we go in background:

ufff that's nasty. Thanks for reporting @Overtorment  will get on it.

ufff that's nasty. Thanks for reporting @Overtorment  will get on it.

Issue replicated and confirmed.
Seems limited to TCP stream connections.
Patching now

Issue replicated and confirmed.
Seems limited to TCP stream connections.
Patching now

patched in https://github.com/Sifir-io/react-native-tor/pull/19 for iOS.
@Overtorment  please give that branch a shot and let me know.
Will check if Android is affected later in the day

patched in https://github.com/Sifir-io/react-native-tor/pull/19 for iOS.
@Overtorment  please give that branch a shot and let me know.
Will check if Android is affected later in the day

will do, thanks!

will do, thanks!

can confirm that the issue is solved. Im able to lock iPhone, unlock, and everything works (and selftest that checks TOR availability passes)

can confirm that the issue is solved. Im able to lock iPhone, unlock, and everything works (and selftest that checks TOR availability passes)

Fixed by #19

Fixed by #19


1.15 unable to build/link failing with windows exit status<PHONE_NUMBER> / 0xC0000005

What version of Go are you using (go version)?

go version go1.15.3 windows/amd64

Does this issue reproduce with the latest release?
Yes,
Tested and failed with 1.15.2 and 1.15.3.
No problems with prior versions including 1.13.15 and 1.14.9.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Fox\AppData\Local\go-build
set GOENV=C:\Users\Fox\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=c:\GoPath\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=c:\GoPath
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\Fox\AppData\Local\Temp\go-build476616686=/tmp/go-build -gno-record-gcc-switches
GOROOT/bin/go version: go version go1.15.3 windows/amd64
GOROOT/bin/go tool compile -V: compile version go1.15.3
gdb --version: GNU gdb (GDB) 7.9.1

What did you do?
Attempted to migrate working program to 1.15.  Silent failure with no indication as to why.
Traced down problematic package to a go wrapper around the C libde265 video decoder.
Program "appears" to build and run, but never progresses to user code when executed and fails with an exit status.
"go run" returns the error exit status.
I do not know now to dig into the build / link process to troubleshoot further.....
What did you expect to see?
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go version
go version go1.14.9 windows/amd64
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go run .
Starting test program, initializing decoder
Decoder created, exiting program
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
0
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go install .
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>test.exe
Starting test program, initializing decoder
Decoder created, exiting program
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
0
What did you see instead?
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go version
go version go1.15.3 windows/amd64
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go install .  note silent failure with no error or messages
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>test.exe      silent failure to do anything, never gets to any init functions much less main()
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
-1073741819
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go run .
exit status<PHONE_NUMBER><PHONE_NUMBER>== 0xC0000005 indicates windows access violation
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
1
libde.zip

C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go install . note silent failure with no error or messages

Was a %errorlevel% reported?

C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>test.exe silent failure to do anything, never gets to any init functions much less main()

If the previous command did not succeed could it be possible that test.exe was not what you expected?
Lastly, I’m sorry to ask, but it’s windows, so I must, have you ruled out interference by AV software?

You can also try ‘go install -x’ to encourage the go tool to print the commands it intends to run.

C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go install . note silent failure with no error or messages

Was a %errorlevel% reported?
No, install command returned errorlevel 0 when queried.  After install, running the executable generated returns a different errorlevel when queried (-1073741819, which I have not found any info on).  I get the errorlevel return when using 'go run .'  I am hoping the difference in errorlevel between go install, running executable, and go run may be a clue as to where or how it is breaking???

C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go version
go version go1.15.3 windows/amd64
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go install .
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
0
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>test
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
-1073741819
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go run .
exit status<PHONE_NUMBER>

C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>test.exe silent failure to do anything, never gets to any init functions much less main()

If the previous command did not succeed could it be possible that test.exe was not what you expected?
Good question, but no.  I just reverified again with which test.exe, but more directly my test was run back to back between go 1.14.9 and 1.15.3 with the only intervening steps being go resinstall...
Lastly, I’m sorry to ask, but it’s windows, so I must, have you ruled out interference by AV software?
I have run exactly the same commands back and forth with the only change being reinstalling a different go version between the tests with AV and windows firewall all turned off, so I am pretty sure this is not it (but as you say, it is windows... :)

You can also try ‘go install -x’ to encourage the go tool to print the commands it intends to run.

Install thinks is succeeds.  My hypothesis is that one of the intermediate steps of the installer is / could be returning an errorlevel that is not checked that is then overwritten by the next step which succeeds with errorlevel 0.
After install I have an 11 kB executable that does nothing (fails before user code with an errorlevel).
Run from 'go install -x":
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>go install -x .
WORK=C:\Users\Fox\AppData\Local\Temp\go-build024877162
mkdir -p $WORK\b001
cat >$WORK\b001\importcfg.link << 'EOF' # internal
packagefile github.com/axionat/eagle/piglet/libde265/test=C:\Users\Fox\AppData\Local\go-build\29\291ee374c5b3eb9336b4c2d0a0e0de034be7fa3a3a0ab5082374eecd9b3058e0-d
packagefile fmt=c:\go\pkg\windows_amd64\fmt.a
packagefile github.com/axionat/eagle/piglet/libde265=C:\Users\Fox\AppData\Local\go-build\16\16a726d7627eab3263438f17f67c5a6c8bc41e0678a4b871189969c2d293f25e-d
packagefile runtime=c:\go\pkg\windows_amd64\runtime.a
packagefile errors=c:\go\pkg\windows_amd64\errors.a
packagefile internal/fmtsort=c:\go\pkg\windows_amd64\internal\fmtsort.a
packagefile io=c:\go\pkg\windows_amd64\io.a
packagefile math=c:\go\pkg\windows_amd64\math.a
packagefile os=c:\go\pkg\windows_amd64\os.a
packagefile reflect=c:\go\pkg\windows_amd64\reflect.a
packagefile strconv=c:\go\pkg\windows_amd64\strconv.a
packagefile sync=c:\go\pkg\windows_amd64\sync.a
packagefile unicode/utf8=c:\go\pkg\windows_amd64\unicode\utf8.a
packagefile encoding/base64=c:\go\pkg\windows_amd64\encoding\base64.a
packagefile runtime/cgo=c:\go\pkg\windows_amd64\runtime\cgo.a
packagefile syscall=c:\go\pkg\windows_amd64\syscall.a
packagefile internal/bytealg=c:\go\pkg\windows_amd64\internal\bytealg.a
packagefile internal/cpu=c:\go\pkg\windows_amd64\internal\cpu.a
packagefile runtime/internal/atomic=c:\go\pkg\windows_amd64\runtime\internal\atomic.a
packagefile runtime/internal/math=c:\go\pkg\windows_amd64\runtime\internal\math.a
packagefile runtime/internal/sys=c:\go\pkg\windows_amd64\runtime\internal\sys.a
packagefile internal/reflectlite=c:\go\pkg\windows_amd64\internal\reflectlite.a
packagefile sort=c:\go\pkg\windows_amd64\sort.a
packagefile math/bits=c:\go\pkg\windows_amd64\math\bits.a
packagefile internal/oserror=c:\go\pkg\windows_amd64\internal\oserror.a
packagefile internal/poll=c:\go\pkg\windows_amd64\internal\poll.a
packagefile internal/syscall/execenv=c:\go\pkg\windows_amd64\internal\syscall\execenv.a
packagefile internal/syscall/windows=c:\go\pkg\windows_amd64\internal\syscall\windows.a
packagefile internal/testlog=c:\go\pkg\windows_amd64\internal\testlog.a
packagefile sync/atomic=c:\go\pkg\windows_amd64\sync\atomic.a
packagefile time=c:\go\pkg\windows_amd64\time.a
packagefile unicode/utf16=c:\go\pkg\windows_amd64\unicode\utf16.a
packagefile internal/unsafeheader=c:\go\pkg\windows_amd64\internal\unsafeheader.a
packagefile unicode=c:\go\pkg\windows_amd64\unicode.a
packagefile internal/race=c:\go\pkg\windows_amd64\internal\race.a
packagefile encoding/binary=c:\go\pkg\windows_amd64\encoding\binary.a
packagefile internal/syscall/windows/sysdll=c:\go\pkg\windows_amd64\internal\syscall\windows\sysdll.a
packagefile internal/syscall/windows/registry=c:\go\pkg\windows_amd64\internal\syscall\windows\registry.a
EOF
mkdir -p $WORK\b001\exe
cd .
"c:\go\pkg\tool\windows_amd64\link.exe" -o "$WORK\b001\exe\a.out.exe" -importcfg "$WORK\b001\importcfg.link" -buildmode=pie -buildid=jRSTOByoppzB5ofTwt_S/7S_F-1wXxcPeRIoqjSgV/uZzVaGEIrRYiTi4-yhSs/jRSTOByoppzB5ofTwt_S -extld=gcc "C:\Users\Fox\AppData\Local\go-build\29\291ee374c5b3eb9336b4c2d0a0e0de034be7fa3a3a0ab5082374eecd9b3058e0-d"
"c:\go\pkg\tool\windows_amd64\buildid.exe" -w "$WORK\b001\exe\a.out.exe" # internal
mkdir -p c:\GoPath\bin
cp $WORK\b001\exe\a.out.exe c:\GoPath\bin\test.exe
rm -r $WORK\b001\
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
0
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>test.exe
C:\GoPath\src\github.com\axionat\eagle\piglet\libde265\test>echo %errorlevel%
-1073741819

@davecheney I manually ran though the install commands reported by 'go install -a -x -work' related to my packages and had no errors reported, I also checked the windows errorlevel between each step and it was always 0.  I am not sure where else to look to find out where it is failing...

Have you checked the related issues, both open & closed?
https://github.com/golang/go/issues?q=is%3Aissue+is%3Aopen+0xC0000005+

Have you checked the related issues, both open & closed?
https://github.com/golang/go/issues?q=is%3Aissue+is%3Aopen+0xC0000005+

@networkimprov I had looked at open issues and found nothing, going back to closed issues I found https://github.com/golang/go/issues/41329 which was closed without a fix and does seem to be my issue....
Forcing buildmode=exe (vice new 1.15 default of buildmode=pie) allows my program to compile and execute without further issues.  (@escholtz @zx2c4 )
I strongly doubt I will be the last person who comes across this problem with the 1.15 migration, so I would offer a couple of thoughts to consider...
The easiest fix would be to go back to buildmode=exe as default windows behavior to maintain compatibility and not break anything for others. (@alexbrainman @ianlancetaylor @bradfitz @FiloSottile discussion on #35192)
If there is consensus that going back to buildmode=exe by default to maintain compatibility is unacceptable or undesirable, then some thoughts / suggestions based on my experience working through this one:
(1) Add a very conspicuous note / caveat to 1.15 release notes along the following lines as a proposed new second paragraph under Ports-Windows:
"Note that buildmode=pie will break programs using Cgo if any imported C libraries are not pie/aslr compliant, generating executables that silently crash.  Either forcing buildmode=exe or acquiring or generating updated pie/aslr compliant C libraries will be necessary for those programs."
(2) Does anyone know if there is a way to detect if Cgo imported libraries are pie/aslr compliant so that we can either (a) fail the compilation issuing an error that buildmode=exe is required to support the C libraries or (b) automatically revert to buildmode=exe and issue a warning that buildmode=exe is being used for compliance with C libraries?
(3) If (2) is not simple, is there some way it would be possible to catch this OS error and exit code and generate a useful error or warning instead of a silent crash from the failing program?  Something that includes "if you are using Cgo, try buildmode=exe to resolve this issue" would be really nice and helpful here.
Although I am back up and running, I would not recommend closing this issue until at least (1) is done, and hopefully one of (2) and (3) as well if possible.
Given the nature of the failure encountered and the difficulty characterizing it to even search for solutions, my recommendation would be to make a 1.15 minor release that reverts default behavior to buildmode=exe until at least one of (2) or (3) can be completed along with (1) to enable a graceful migration to default behavior of buildmode=pie without difficult to diagnose failures of existing programs.
Thanks all for your quick responses and thoughts.

Sorry you have run into trouble.  I hope that people more familiar with Windows will be able to answer your questions.  It is extremely unfortunate that linking non-PIE code into a PIE does not produce an error at link time (it does on Unix systems).
I don't think it would be a good idea to change the default build mode in a minor release.  That will be confusing in a different way.

@jasonpfox

Traced down problematic package to a go wrapper around the C libde265 video decoder.

Sorry. I did not even looked at your code. I don't have free time.

The easiest fix would be to go back to buildmode=exe as default windows behavior to maintain compatibility and not break anything for others.

Yes, that would work for people who use Cgo. But we would have to disable ASLR for every Go user. We provided buildmode=exe fallback specifically for cases like yours. I think our decision is reasonable.

(1) Add a very conspicuous note / caveat to 1.15 release notes along the following lines as a proposed new second paragraph under Ports-Windows:
"Note that buildmode=pie will break programs using Cgo if any imported C libraries are not pie/aslr compliant, generating executables that silently crash. Either forcing buildmode=exe or acquiring or generating updated pie/aslr compliant C libraries will be necessary for those programs."

I am not Cgo expert. I don't use if what you say in this paragraph is true. I will let others decide if it is appropriate to include statement likes in the docs.

(2) Does anyone know if there is a way to detect if Cgo imported libraries are pie/aslr compliant ...

I do not know, if what you propose is possible. I believe that ASLR is controlled by combination of GCC flags. So it is up to package user / author to set these flags appropriately for their Cgo build.

(3) If (2) is not simple, is there some way it would be possible to catch this OS error and exit code and generate a useful error ...

Again. I am not expert enough to answer your question.
Alex

@gopherbot remove WaitingForInfo


fix: remove appsmith from widget entity dropdown

Description

Remove appsmith as an entity (incoming / outgoing entity) from the entity dropdown, widget property pane.

Fixes #15120
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Tested Manually on the canvas.

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=08ac5b5

Have checked all the widgets, in a new workspace, dragging and dropping each of them, it shows "No entity". Working fine moving to done.

/ok-to-test sha=d85d4f0

/ok-to-test sha=c643f64


added copy store function

the pull request for copy store data

Thanks @mxab looks good! I've added some comments, let me know what you think

Hi, the TODO: was copied from the other copy function, so it was actually aldeed's idea.
I added the moveData call

@raix @mxab, I vote we create an issue to discuss and track the TODO / SA idea, and go ahead and merge this as is for now.

Ok, makes sense to track it for later - its not part of the official api :)
@mxab I guess I'd have to get started on some contributor t-shirts soon... :)

yeah :)

:D
logo +1
t-shirts +1

:) did you guys check out the logo? ideas are welcome

yeah, looks good to me.


Netlify fail

Hi,
While deploying it to the Netlify i get this error

ERROR in   Error: Child compilation failed:
1:15:49 PM:   Module not found: Error: Can't resolve './assets/image1.png' in '/opt/bu  ild/repo/src':
1:15:49 PM:   Error: Can't resolve './assets/chinguBanner.png' in '/opt/build/repo/src'
1:15:49 PM:   Module not found: Error: Can't resolve './assets/image2.png' in '/opt/bui  ld/repo/src':
1:15:49 PM:   Error: Can't resolve './assets/jsHackeryou.png' in '/opt/build/repo/src'

Hi @RavalVarun I have the exact same issue. How did you resolve this issue?


The Bulldog Shotgun is too light

Description

it weighs 5. gun refactor oversight moment.
Reproduction

Screenshots

Additional context

apparently fixed ages ago


feat(eslint): Enable no-non-null-assertion rule

The type of this PR is: Feat
Description
Thank you @gkartalis for the suggestion to add this to our estlint 🙏 Looking at our eslint file, found that it was disabled, probably due to some migration at some point. Turned it back on!

Lol, it really can be SO EASY @gkartalis 😭

Oh wait, just saw that in eigen there is another one https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-non-null-asserted-optional-chain.md
didn't know about that, maybe we should enable both?


Docker 1.7.1: Panic due to invalid memory address or nil pointer dereference

This is similar to other issues, except our stack trace is a bit different.  Unfortunately, I can't paste all of the information that is asked for, but I'll provide as much as I can.
  This job has 600 containers running.  This panic caused unrelated containers to stop running, thus putting our cluster into an unstable state.
Describe the results you expected:
All of the containers to continue to work as advertised during the restart.
Provide additional info you think is important:
The docker registry (2.0) is in a container as well.
Stack trace (partial)
goroutine ... [running]:
runtime.gopanic(...)
    /usr/local/go/src/runtime/panic.go:425
runtime.panicmem
    /usr/local/go/src/runtime/panic.go:42
runtime.sigpanic
    /usr/local/go/runtime/sigpanic_unix.go:26
bufio.(*Writer).flush
    /usr/local/go/src/bufio/bufio.go:530
bufio.(*Writer).Flush
    /usr/local/go/src/bufio/bufio.go:519
net/http.(*response).Flush
    /usr/local/go/src/net/http/server.go:1047
github.com/docker/docker/pkg/ioutils.(*WriteFluser).Write
    /root/rpmbuild/BUILD/docker-engine/.gopath/src/github.com/docker/docker/pkg/ioutils/writefluser.go:21
github.com/docker/docker/pkg/progressreader.(*Config).Read
    /root/rpmbuild/BUILD/docker-engine/.gopath/src/github.com/docker/docker/pkg/progressreader/progressreader.go:37
io.Copy
    /usr/local/go/src/io/io.go:362
github.com/docker/docker/graph.func
    /root/rpmbuild/BUILD/docker-engine/.gopath/src/github.com/docker/docker/graph/pull:602
github.com/docker/docker/graph.func
    /root/rpmbuild/BUILD/docker-engine/.gopath/src/github.com/docker/docker/graph/pull:602
runtime.goexit()
    /usr/local/go/src/runtime/asm_amd64.s:2232
created by github.com/docker/docker/graph.(*TagStore).pullV2Tag
    /root/rpmbuild/BUILD/docker-engine/.gopath/src/github.com/docker/docker/graph/pull:602

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

was fixed


the error ???

the code is :
package com.vcg.community.kafka.data.api.domain;
import com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBAttribute;
import com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBHashKey;
import com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBRangeKey;
import com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBTable;
import java.io.Serializable;
/**

@author felayman

@since 16/1/7
*/
@DynamoDBTable(tableName = "vcg-activity-master-test")
public class Entity  implements Serializable{
private static final long serialVersionUID =<PHONE_NUMBER>601772126L;
private String mainTypeId;
private String relativeTypeId;
private long eventTimestamp;
private String eventDate;
private boolean isDeleted;
private String itemType;
private String ownerType;
private String ownerId;
private String relativeType;
private String relativeId;
private String properties;
@DynamoDBHashKey(attributeName = "main_type-id")
public String getMainTypeId() {
return mainTypeId;
}
public void setMainTypeId(String mainTypeId) {
this.mainTypeId = mainTypeId;
}
@DynamoDBRangeKey(attributeName = "related_type-id")
public String getRelativeTypeId() {
return relativeTypeId;
}
public void setRelativeTypeId(String relativeTypeId) {
this.relativeTypeId = relativeTypeId;
}
@DynamoDBAttribute(attributeName = "event_timestamp")
public long getEventTimestamp() {
return eventTimestamp;
}
public void setEventTimestamp(long eventTimestamp) {
this.eventTimestamp = eventTimestamp;
}
@DynamoDBAttribute(attributeName = "event_date")
public String getEventDate() {
return eventDate;
}
public void setEventDate(String eventDate) {
this.eventDate = eventDate;
}
@DynamoDBAttribute(attributeName = "is_deleted")
public boolean isDeleted() {
return isDeleted;
}
public void setDeleted(boolean deleted) {
isDeleted = deleted;
}
@DynamoDBAttribute(attributeName = "item_type")
public String getItemType() {
return itemType;
}
public void setItemType(String itemType) {
this.itemType = itemType;
}
@DynamoDBAttribute(attributeName = "owner_type")
public String getOwnerType() {
return ownerType;
}
public void setOwnerType(String ownerType) {
this.ownerType = ownerType;
}
@DynamoDBAttribute(attributeName = "owner_id")
public String getOwnerId() {
return ownerId;
}
public void setOwnerId(String ownerId) {
this.ownerId = ownerId;
}
@DynamoDBAttribute(attributeName = "related_type")
public String getRelativeType() {
return relativeType;
}
public void setRelativeType(String relativeType) {
this.relativeType = relativeType;
}
@DynamoDBAttribute(attributeName = "related_id")
public String getRelativeId() {
return relativeId;
}
public void setRelativeId(String relativeId) {
this.relativeId = relativeId;
}
@DynamoDBAttribute(attributeName = "properties")
public String getProperties() {
return properties;
}
public void setProperties(String properties) {
this.properties = properties;
}
@Override
public String toString() {
return "Entity{" +
"mainTypeId='" + mainTypeId + ''' +
", relativeTypeId='" + relativeTypeId + ''' +
", eventTimestamp=" + eventTimestamp +
", eventDate='" + eventDate + ''' +
", isDeleted=" + isDeleted +
", itemType='" + itemType + ''' +
", ownerType='" + ownerType + ''' +
", ownerId='" + ownerId + ''' +
", relativeType='" + relativeType + ''' +
", relativeId='" + relativeId + ''' +
", properties='" + properties + ''' +
'}';
}
}

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityRepository': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: No field annotated with interface org.springframework.data.annotation.Id found!
how  should i deal the error ?

How does your Repository class looks like?
(Please use some code formatting for improved readability)

Please provide more information / answer to the question above at https://github.com/derjust/spring-data-dynamodb/issues/24.
As (privately) communicated with @michaellavelle, the project will continue under https://github.com/derjust/spring-data-dynamodb.

I've come across this error myself and just happened across this issue. A request for @derjust - can we rename this issue something like "No field annotated with interface org.springframework.data.annotation.Id found!" because it's likely other people have hit this problem but won't spot this issue because of the title.
The problem is that if you're using a hash key and a range key you have to design the entity class, and an "id" or primary key class, and do it in a particular way or you get this error message that doesn't really explain the problem. At first I presumed that spring-data-dynamodb simply doesn't support the hash and range keys together like you can with the AWS SDK. When I had a look at the sample code in the older repo, I found that there was an example. The entity and "id" class pattern is a bit odd, but it works.
To anyone seeing this error, make sure you're doing the following:

You need a specialized class for your primary key. It needs to implement Serializable and will have the fields, getters, and setters for your hash key field and range key field.
In your entity class, instead of the hash key field and range key field, you have a field that is an instance of the specialized key class mentioned above. You must annotate that field with Spring's @Id annotation, but do not provide a getter or setter.
Also in your entity class, do provide a getter and setter for your hash key field and range key field, even though your entity doesn't have those fields. You pass those through to the corresponding method on your primary key field.
Make sure to lazy-create your primary key field in the hash key and range key setters in the entity.
The hash key and range key getters in both your entity class and primary key class have to be annotated with @DynamoDBHashKey and @DynamoDBRangeKey, respectively. Yes, this is redundant.
Make sure that your repo uses the primary key class for the "ID" class, otherwise you'll get another weird error about something not being an instance of the right class.

Do all of the above and the hash-key/range-ky combo will work properly. See the following two code examples, from the older spring-data-dynamodb repo, as a reference:
Entity class
Entity id class

This isn't a bug. There's a particular way you have to structure your entity class and "id" class for it to work in spring-data-dynamodb.
I've commented in the corresponding issue in the new repo:  https://github.com/derjust/spring-data-dynamodb/issues/24

I will try to provide a better message. Chances are that this is generated by Spring itself thus there is little influence by us.
But I try. Thanks for the exhaustive list.

I wouldn't worry about the error message, and for that matter, don't worry about renaming this issue. I think you can close this issue; there isn't a bug, just some odd behavior. The software works once the programmer determines the "recipe", which is available by looking at the example code.
The challenge is that Spring-Data has its own annotations and way of doing things, the AWS SDK has its own annotations and way of doing things, and spring-data-dynamodb is an integration of two. It isn't surprising that occasionally something strange happens. An exhaustive examination of all the edge- and error-cases is tough to do without a sizable team and plenty of time. You're doing great, thanks for keeping up the repo and keeping up this project.
If I have time to contribute to the code base, I'll check in with you. I'm actively using this project at the moment.

The challenge is that Spring-Data has its own annotations and way of doing things, the AWS SDK has its own annotations and way of doing things, and spring-data-dynamodb is an integration of two.

yeah that's the fun for this issue.
Having a better error message on the other hand for sure would direct people in the right direction (as the existing one is somewhat non-conclusive)
Thanks!

Yeah, good point. Mysterious error messages don't help.
The pattern required for the hash key/range key combination is a bit odd. Having the same getters and setters with AWS annotations in both the entity and it's embedded "Id" class is what threw me off because it's redundant. If you got rid of the requirement to have hash- and range-key methods/annotations in the entity class when there's an embedded "Id" class it would make more sense (and be backward-compatible for people who've had to do it the current way).
Just an idea.

hi @derjust i am also getting same issue
No field annotated with interface org.springframework.data.annotation.Id found!
Here is my Entity
`@Data
@DynamoDBTable(tableName = "user")
public class User{
@DynamoDBHashKey(attributeName = "roleNumber")
private String roleNumber
@DynamoDBAttribute(attributeName = "correlationId")
private String correlationId;

@DynamoDBAttribute(attributeName = "carrier")
private String name;

}
@Configuration
@EnableDynamoDBRepositories("org.myapp.dynamo")
public class DynamoDBConfig {
@Value("${ENV}")
private String environment;

Supplier<AWSCredentialsProvider> credentialSupplier = ()->{
    return new AWSCredentialsProviderChain(new EnvironmentVariableCredentialsProvider(),
            new SystemPropertiesCredentialsProvider(),
            new ProfileCredentialsProvider(),
            new InstanceProfileCredentialsProvider(false));

};

//    @Bean
//    public DynamoDBOperations dynamoDBOperations() {
//        final DynamoDBTemplate dynamoDBTemplate = new DynamoDBTemplate(amazonDynamoDB());
//        final DynamoDBMapperConfig.TableNameOverride tableNameOverride = DynamoDBMapperConfig.TableNameOverride .withTableNamePrefix(environment);
//        dynamoDBTemplate.setApplicationContext();
//
//        return dynamoDBTemplate;
//    }
@Bean
public AmazonDynamoDB amazonDynamoDB() {
    AmazonDynamoDB amazonDynamoDB = AmazonDynamoDBClientBuilder.standard()
            .withRegion(System.getenv("AWS_REGION"))
            .withCredentials(credentialSupplier.get())
            .build();

    return amazonDynamoDB;
}

}
@EnableScan
public interface UserRepository extends CrudRepository<User,String> {
User findByCorrelationId(@Param(value="correlationId") String  correlationId);

}
`
i am using below dependency in my pom
   <dependency>             <groupId>com.amazonaws</groupId>             <artifactId>aws-java-sdk-dynamodb</artifactId>             <version>1.11.297</version>         </dependency>         <dependency>             <groupId>com.github.derjust</groupId>             <artifactId>spring-data-dynamodb</artifactId>             <version>4.5.5</version>         </dependency>
THere is no documentation what @EnableScan does
Please help me where i am doing wrong with configuration


Help Buffer Size ESP32

Hello.
I'm struggling to find a way to set the BSSLBufferSize and ResponseSize using firebase on ESP32.
I've been using the FirebaseESP8266 library on my projects, and now I'm moving to ESP32.
Everything works fine on my project, but when I try to receive a large data from the server, ESP32 crashes, and I believe it happens because there is not enough allocated memory for this task (even when I have 150000+ of free Heap).
Is there any similar way to define a buffer size on firebaseESP32, as similar as setBSSLBufferSize and setResponseSize found on firebaseESP8266?
Thank you for your excelent work on this libraries!

No limit of buffer size as in ESP8266 which you should manage by yourself.
You should...
Avoid to get large payload by redesign your database.
Read smaller data multiple times.
Use query filter.

When I try to read an object greater than 800 bytes I'm receiving this error. If I reduce the object's size to 700 bytes, esp32 reads perfectly. I have 156kb of free heap. Do you have any idea what's going on?
PC: 0x40001615
EXCVADDR: 0x40000000
Decoding stack results
0x400da783: FirebaseESP32::strpos(char const*, char const*, int) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 4991
0x400da7cd: FirebaseESP32::getHeader(char const*, char const*, char const*, int&, int) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 2740
0x400dab44: FirebaseESP32::parseRespPayload(char const*, server_response_data_t&, bool) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 2629
0x400de4aa: FirebaseESP32::handleResponse(FirebaseData&) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 3145
0x400deed8: FirebaseESP32::waitResponse(FirebaseData&) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 2900
0x400df145: FirebaseESP32::handleStreamRead(FirebaseData&) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 3678
0x400df1b9: FirebaseESP32::readStream(FirebaseData&) at C:\Users\geova\Documents\Arduino\libraries\Firebase_ESP32_Client\src\FirebaseESP32.cpp line 1961
0x400d638d: loop() at C:\Users\geova\Documents\Arduino\SmartHome_v2\central\esp32\central_v4.4\central_v4/central_v4.ino line 188
0x400e922d: loopTask(void*) at C:\Users\geova\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.4\cores\esp32\main.cpp line 19
0x40088ddd: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c line 143

Don't expected anything from the stack trace without your code.

As I recommend above don't get large payload especially from stream.
Stream is for Realtime, small data only, you need to redesign your database.
Please look at this
void setStreamCallback(FirebaseData &fbdo, StreamEventCallback dataAvailablecallback, StreamTimeoutCallback timeoutCallback = NULL, size_t streamTaskStackSize = 8192);

The default stream stack size is 8k, you can increase this but reduce the payload data size is recommended.
That stack memory also use to store the mbedTLS resources while cpu services some interrupt from the system tasks which required large memory.

I finally found this is the bugs from the find string utilities which use internally caused this wdt reset issue. This happens to both ESP8266 and ESP32 Firebase libraries which the whole new code was written.
Now the bugs was fixed and I also add the setResponseSize function as in ESP8266 version.
Please update the library.

Thank you so much for your effort!
I'd decided to rewrite my code using Get functions instead of Stream functions. Now I will update my library and test everything again.
I really appreciate your work!


InvalidArgument: The parameter ForwardedValues cannot be used when a cache policy is associated to the cache behavior

When updating an aws.cloudfront.Distribution instance from:
defaultCacheBehavior: {
      targetOriginId: originId,
      forwardedValues: {
        cookies: {
          forward: 'none',
        },
        queryString: false,
      },
      allowedMethods: [
        'GET',
        'HEAD',
        'OPTIONS',
        'PUT',
        'POST',
        'PATCH',
        'DELETE',
      ],
      cachedMethods: ['GET', 'HEAD', 'OPTIONS'],
      viewerProtocolPolicy: 'allow-all',
    },

to
defaultCacheBehavior: {
      targetOriginId: originId,
      cachePolicyId: cfCachePolicy.id,
      originRequestPolicyId: cfOriginRequestPolicy.id,
      allowedMethods: [
        'GET',
        'HEAD',
        'OPTIONS',
        'PUT',
        'POST',
        'PATCH',
        'DELETE',
      ],
      cachedMethods: ['GET', 'HEAD', 'OPTIONS'],
      viewerProtocolPolicy: 'allow-all',
    },

pulumi up errors with:
InvalidArgument: The parameter ForwardedValues cannot be used when a cache policy is associated to the cache behavior
then, I have to export stack > remove forwardedValues references, import stack, and reapply
Expected behavior
pulumi phases the change in 2 (ie remove forwardedvalues, add cachepolicy), if a single update not allowed by aws
Current behavior
error above
Steps to reproduce
delta above
Context (Environment)
pulumi version 2.21.2
under pulumi's docker image
Affected feature
pulumi up

This is an upstream bug tracked in https://github.com/hashicorp/terraform-provider-aws/issues/17626

You have to disable the forwarded section if applying a custom cache_policy and origin_request_policy.
Eg/-
ordered_cache_behavior {
path_pattern     = "/*"
allowed_methods  = ["GET", "HEAD", "OPTIONS"]
cached_methods   = ["GET", "HEAD"]
target_origin_id = "${var.s3_origin_id}"
#origin_request_policy_id = aws_cloudfront_origin_request_policy.origin_request_policy.name
#cache_policy_id = aws_cloudfront_cache_policy.cache_policy.name
origin_request_policy_id = aws_cloudfront_origin_request_policy.origin_request_policy.id
cache_policy_id = aws_cloudfront_cache_policy.cache_policy.id
forwarded_values {
query_string = false

cookies {
forward = "none"
}
}
min_ttl                = 0
default_ttl            = 3600
max_ttl                = 86400
compress               = true
viewer_protocol_policy = "redirect-to-https"

}

I can confirm this issue. The only workaround is to remove cachePolicyId which is not ideal.

Hi, I had the same issue in Terraform and resolve with parameters    use_forwarded_values   = false . i hope this can help you

use_forwarded_values = false works and needs to be set to all default_cache_behavior and ordered_cache_behavior that have cache_policy_id. You can see in the terraform plan that setting use_forwarded_values = false explicitly remove the forwarded values field (which terraform generates by default, always)

i was going nuts also, confirm that adding in terraform use_forwarded_values = false works when creating a cloud front distribution. Had this issue when sourcing https://github.com/terraform-aws-modules/terraform-aws-cloudfront and was trying to use Cache policy and origin request policy by adding cache_policy_id .

Since the upstream issue was closed as completed, I'm going to close out this issue as well.

yes, but you probably want both, a proper cache policy while modifying things going to the origin


Split Chapter option

A way to do all of the following steps from a selected move:

create the PGN from the current FEN and continuing from the current move
remove all continuations from the current move
create a new chapter with the created PGN
add a comment to the current move with the link of the new chapter

This should be handled in the PGN editor (https://github.com/Siderite/lichessTools/issues/210) Closing for now.

Also added chapter split option in the Bookmarks feature


The following assertion was thrown building Container(padding: EdgeInsets(20.0, 0.0, 20.0, 0.0), constraints: BoxConstraints(0.0<=w<=Infinity, h=200.0)): Failed assertion: boolean expression must not be null

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hi @Ajit00-code
This platform is not meant for assistance on personal code.
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow.
If you believe that it's an issue with flutter, please provide a minimal complete code sample to reproduce the problem, and I will reopen it
Thank you


fix: rune asset trades

Description
Adds a THORChain pool mapping to thorchainAssetId, allowing trades into and out of RUNE to use the quotes endpoint. Currently they are falling back to the hacking pool size approximation to get quote data.
Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A, bug in production.
Risk
Small - changes quote source for RUNE quotes to a more accurate one.
Testing
With the network tab open, stage a THORChain trade to or from RUNE to the Trade confirm screen.
Observe that requests to the lcd/thorchain/quote/swap endpoint no longer have undefined as the from_asset or to_asset, and that the request now returns a quote instead of an error.
Engineering
☝
Operations
☝

check that RUNE trades still work as expected.

Screenshots (if applicable)
N/A

Current dependencies on/for this PR:

develop

PR #4352   👈

PR #4353

This comment was auto-generated by Graphite.


ENH: Standardize header buttons

This standardizes our header button behavior, to automate more things, and ensure standard structure, style, and behavior. The user-facing API shouldn't change at all, this is all under-the-hood stuff. However, this should make it much less work to create a "pluggable" header infrastructure when the time comes (ref: #470)
Major changes:

We now have macros that create different kinds of topbar buttons, and we re-use these throughout
The header button logic now creates a list of dictionaries that define metadata for the header buttons - this is then rendered into the proper HTML at the end
Updated the style of the header buttons so that it doesn't use alternating background colors
The timing of the tooltips is a bit more delayed now so they don't pop up immediately
Rename the "topbar" to the "article header", in line with the basic-ng theme and more specific.
Had to update (and in some cases simplify) a bunch of test infrastructure to accommodate the more standard buttons

supercedes https://github.com/executablebooks/sphinx-book-theme/pull/425
OLD:

NEW:

Will merge this one in so that we can cut a pre-release and give others a chance to try it out. I took another look and don't think there are any regressions, but something might pop up (if there is something, I suspect it'd be the launch button URL generation)


Change #logo for StWelcomeBrowser to answer an ImageMorph with the FormSet for the icon

This pull request changes #logo for StWelcomeBrowser to answer an ImageMorph with the FormSet for the icon.
This requires pharo-icon-packs pull request #11 to be merged first.

@jecisc Thanks! Could you merge pharo-icon-packs pull request #11 as well? Otherwise the logo will be too small when using canvas scale 2 due to the FormMapping in ScalingCanvas mapping it to a Form with extent 256@256 instead of 512@512. You may also want to merge pharo-icon-packs pull request #10.

I don't have the write access in this project :(

@tesonep @estebanlm: Could either of you merge pharo-icon-packs pull requests #10 and #11? Looking at closed pull requests in that repository, you two do have write access.

@jecisc: Did you maybe get write access now? The pharo-icon-packs pull request still needs to be merged to fix the logo in the Welcome Browser being too small when using world renderer canvas scale factor 2 (see screenshot below using Pharo 12 build 1504).

Sorry but I'm in holiday :( I do some review sometimes but I did not see the others to ask accesses.
Also with P12 been released I don't know if we should merge those in P12 branch

Ah OK! @estebanlm: Could you merge pharo-icon-packs pull request #11 then? And maybe also #10 and #12?


Add comment to the piece of code in the new branch created

Modify the code to meet needs of all clients

modify the design to meet add users needs


Broadcast Page Design

SWOC
Issue that this pull request solves
The UI issue of broadcast page
Closes: #53
Proposed changes
Implementing the design for Broadcast page.
Brief description of what is fixed or changed

Adding the multi carousel(slider) for the broadcast.
Adding the popup after clicking any broadcast card.

Types of changes
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[x] Other (please describe):Implementing UI

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes does not break the current system and it passes all the current test cases.

Screenshots
Please attach the screenshots of the changes made in case of change in user interface

Other information
Any other information that is important to this pull request

@Kajol-Kumari  Ok Got it!!

@Kajol-Kumari  Ok Got it!!

@amanprateek123 please do the following changes:

Revert/Remove the faq related changes from this PR. (faq.css and faq.png file)
The ellipses(...) shouldn't be done manually, instead when the text size goes beyond the size of the card, make it break in the form of ellipses
The model is appearing same for each card, instead it should show the content of the card which is being clicked.

Hey @amanprateek123 let's not make all these changes in this PR only as it would become too large. Please resolve the conflict, we will merge this and I will open up a new issue for the changes I suggested you in here

@amanprateek123 please do the following changes:

Revert/Remove the faq related changes from this PR. (faq.css and faq.png file)
The ellipses(...) shouldn't be done manually, instead when the text size goes beyond the size of the card, make it break in the form of ellipses
The model is appearing same for each card, instead it should show the content of the card which is being clicked.

Hey @amanprateek123 let's not make all these changes in this PR only as it would become too large. Please resolve the conflict, we will merge this and I will open up a new issue for the changes I suggested you in here

@Kajol-Kumari  Got it. I will solve the conflicts.But please assign that new issue to me.

@Kajol-Kumari  Got it. I will solve the conflicts.But please assign that new issue to me.

@Kajol-Kumari  please review this PR again and tell me that everything is fine or not(regarding conflicts)

@Kajol-Kumari  please review this PR again and tell me that everything is fine or not(regarding conflicts)

@Kajol-Kumari Got it. I will solve the conflicts.But please assign that new issue to me.

Sure @amanprateek123 !

@Kajol-Kumari Got it. I will solve the conflicts.But please assign that new issue to me.

Sure @amanprateek123 !

@Kajol-Kumari  please open the new issue and assign to me(regarding updates in broadcast page)

@Kajol-Kumari  please open the new issue and assign to me(regarding updates in broadcast page)

@Kajol-Kumari please open the new issue and assign to me(regarding updates in broadcast page)

@amanprateek123 please claim this

@Kajol-Kumari please open the new issue and assign to me(regarding updates in broadcast page)

@amanprateek123 please claim this


[Select] ListSubheader overlapping

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When grouping items in the <Select/> component, the sticky headers will overlaps once scrolled down:

Expected Behavior 🤔
Only the last visible header should be displayed.
Steps to Reproduce 🕹
This is a modified grouping example, so the list is a bit longer:
https://codesandbox.io/s/material-demo-forked-vm71d?file=/demo.js
Your Environment 🌎
Google Chrome Version 90.0.4430.93
Safari Version 14.0.3 (166<IP_ADDRESS>.7)

Duplicate of #18200

Fixed in v5


Streaming Response Bodies

Hello,
We just started using your gem, but we have a lot of data through a whole day, which makes the export 100MB +, I was thinking if there's a way of implementing an HTTP stream ( example here ), maybe as optional around this line: https://github.com/keolo/mixpanel_client/blob/master/lib/mixpanel/uri.rb#L22
What do you think?

Hi David,
That sounds interesting. Would you like to take a stab at it?

Eh. Looks like you already did. https://github.com/keolo/mixpanel_client/pull/45
I'll take a look soon. Sorry for the delay.


New package: AdaStress v0.1.0

Registering package: AdaStress
Repository: https://github.com/NASA-SW-VnV/AdaStress.jl
Created by: @rlipkis
Version: v0.1.0
Commit: 17a4e85136d3957ad4626ea291349ed319aa2870
Reviewed by: @rlipkis
Reference: https://github.com/NASA-SW-VnV/AdaStress.jl/commit/17a4e85136d3957ad4626ea291349ed319aa2870#commitcomment-66474491
Description: Reinforcement learning framework to find and analyze the likeliest failures of a system under test.

@rlipkis please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]

AutoMerge doesn't appear to recognize our OSI-approved license.
[noblock]

Understandably, it doesn't read PDF :slightly_smiling_face:  the license must be a plain-text file which can be correctly identified by licensecheck
[noblock]


Wrong filename in package()

In PKGBUILD in package() the source file name for the installation of macfand.service is wrong.
package() {...      install -Dm644 macfand.service "${pkgdir}/usr/lib/systemd/system/macfand.service" ... }
It must be called
package() { ...      	install -Dm644 macfand.service.gen "${pkgdir}/usr/lib/systemd/system/macfand.service" ... }
Otherwise package() fails with exit code 4

Hello @kappilini ,
I have done the following changes you mentioned and hopefully @ablakely or @b- can accept my PR for the fix.


MC-HEVC Support

It doesn't appear that the command-line version has MC-HEVC support like Unsqueeze does. Any chance this could be added? 🙏

Hi, spatial videos should definitely be supported. I just tried one and it worked, are you seeing a specific issue?

Thanks! I was doing something wrong on my end. Appreciate all you do!! Btw, your upscaler has been added to: https://github.com/cbusillo/BD_to_AVP


undefined "writeKeyToCore" and "saveKeyFromCore" function

Seems like there are 2 unrenamed functions in KeyCommands.js in the latest master.

writeKeyToCore:
commands/KeyCommands.js:286 is line
return that.writeKeyToCore(deviceid + "_new", true);
saveKeyFromCore: commands/KeyCommands.js:164 is return that.saveKeyFromCore(prefilename);

Replacing those instances with writeKeyToDevice and saveKeyFromDevice made everything works again.
I could submit a PR for this, in case is needed.

@endorama, thanks for the bug report!
If you'd like to submit a PR, that would certainly be welcome! Otherwise, I am happy to fix this myself.
Let me know what you think!

Pull request ready!
PS: I read from contribution guidelines that I should sign the Spark Individual Contributor License Agreement (CLA). Should I simply fill the GDocs form?

@endorama correct! Just fill out this form if you will: https://docs.google.com/a/particle.io/forms/d/1_2P-vRKGUFg5bmpcKLHO_qNZWGi5HKYnfrrkd-sbZoA/viewform
Thank you so much! :smile_cat:

Form filled, please let me know if further steps should be taken.

that's it! thanks so much!


Install AdminDashboard{Testing}Module in a Misk module

Currently this is done in an internal wrapper library. Doing this in Misk will make life easier for any further services we choose to open source that do not get to use the wrapper library.

Going to punt on this for now but may re-open in the future of other open sourced service built on Misk require it.


Ticket28565 rebased

To review only from https://github.com/torproject/sbws/commit/70531ba0fa0e424480d8b9b91f2bfac5618e972e included

Also, i would replace all the keys:
s/_measurement_exclusion_/_measurements_excluded/
What do you think?

I think i'm also going to modify the code so that the relay_recent_measurement_exclusion(*) is not present when it actually does not exclude any measurement.
I think it make it clearer and less data in the file.

I made a "wip" commit with the names i was suggesting, because i don't know if you would like them.

I think i'm also going to modify the code so that the relay_recent_measurement_exclusion(*) is not present when it actually does not exclude any measurement.

In the end i only include them when a measurement is excluded, no matter if the relay is excluded or not.
That commit would need to be squashed if you think is a good solution.
I also change the name of a key in that commit (should have been in the wip commit)

Also, i would replace all the keys:
s/_measurement_exclusion_/_measurements_excluded/
What do you think?

Yes, that seems easier to understand.

I think i'm also going to modify the code so that the relay_recent_measurement_exclusion(*) is not present when it actually does not exclude any measurement.
I think it make it clearer and less data in the file.

Ok

I will review the new code in about 12-18 hours.

Added more tests in last fixup

Also, i would replace all the keys:
s/_measurement_exclusion_/_measurements_excluded/
What do you think?

Yes, that seems easier to understand.

I think you missed this change.

made other fixup, squashed all, force pushed


database connection issue

hello @Harshitazz , I have some experience in building REST API and GraphQL servers and I hope to contribute on this issue. Thanks

I have experience with MongoDB, and can solve this issue, can connect it to mongoose as well as MongoDB

It is done purposely for now.
By today you all get a Discord server link
Join thereafter this error will not come

Hello @itsmohit097 can you please assign this issue to me


[HELP] Could you provide your pretrained models?

Hey guys, recently I implemented many recipes and added new configs such as melgan.
I want to try these new configs for each recipe and upload pretrained models, but I have not enough GPUs.
Therefore, if you trained the models which have not yet uploaded as the pretrained model, could you provide them to me?
Thank you for your cooperation in advance.
TODO
parallel_wavegan.v1

[x] LibriTTS #124

melgan.v3

[ ] JSUT
[ ] CSMSC
[ ] CMU Arctic
[ ] JNAS
[ ] VCTK
[ ] LibriTTS

parallel_wavegan.v3
This configuration requires too much time, so low priority.

[ ] JSUT
[ ] CSMSC
[ ] CMU Arctic
[ ] JNAS
[ ] VCTK
[ ] LibriTTS

seems u have done all recipe :))))) or is there a recipe here that u haven't trained yet ?

I will make TODO-like list.

Will try on my GPU, by the way, @kan-bayashi this paper (https://arxiv.org/pdf/2005.05106.pdf)  uses similar concept of MelGAN with multiresolutionSTFT loss as used in this repo but with minor tweaking in the base model.

@rishikksh20 Thanks for your info! It seems that the idea is almost the same as this repository. I will check in detail.

I will close this issue.


This is how the conversation actually went down before you start putting words in my mouth:

MinGW 7 isn't needed. Looking at the old bug report, your problem is that your particular mingw build was created without threading support; this is a known issue on some distros and actually mentioned in the README.
Note that you'll need to perform the fixup for the i686-w64-* binaries as well for 32-bit support.


NPE while updating classpath

Description
Not sure how to reproduce it, but I keep getting the following NPE on a hybrid java/kotlin project.
Nov 22, 2022 3:09:06 P.M. org.eclipse.lsp4j.jsonrpc.RemoteEndpoint fallbackResponseError
SEVERE: Internal error: java.lang.NullPointerException: Cannot invoke "org.eclipse.lsp4j.jsonrpc.messages.Tuple$Two.getFirst()" because "modelAndProjectInfoAndCancelChecker" is null
java.util.concurrent.CompletionException: java.lang.NullPointerException: Cannot invoke "org.eclipse.lsp4j.jsonrpc.messages.Tuple$Two.getFirst()" because "modelAndProjectInfoAndCancelChecker" is null
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture.postFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
Caused by: java.lang.NullPointerException: Cannot invoke "org.eclipse.lsp4j.jsonrpc.messages.Tuple$Two.getFirst()" because "modelAndProjectInfoAndCancelChecker" is null
	at org.eclipse.lsp4mp.ls.properties.PropertiesFileTextDocumentService.lambda$definition$8(PropertiesFileTextDocumentService.java:198)
	... 10 more

Extension version
v0.2.26

Are there any more to the stack trace? It says "... 10 more", is that cut off by you or the language server? Would be nice to have more to see where in the language server this happens.

That's a cutoff by the language server itself, unfortunately. Is there any parameter I can tweak to get a longer stacktrace? Then I can apply that and wait for it to happen again.

@vhdirk , not that I know of. Is this during the initialization of the server? Or does it happen at random times afterwards? Is it a closed source project? Or something you can share?
Also, does it affect the usage? Or does everything still work even when you get this NPE? The language server currently will print a lot of stack traces in some projects, especially with the hover functionality (some parts it can't get any meaningful information about). Those are usually of the UnsupportedOperationException-variety though. Some of it should probably not be printed all the time, as it is just confusing the users 🙁


Doc Feedback: Wording

Location : https://ei.docs.wso2.com/en/latest/streaming-integrator/quick-start-guide/getting-started/create-the-siddhi-application/
Fix wording:
Before: The details to be captures include the room ID,
After: The details to be captured include the room ID,

This is addressed via [1].
[1] https://github.com/wso2/docs-ei/pull/1618


Update timeout for .github/workflows/_unit_tests.yaml

This is an automated pull request to update default timeouts for all jobs in .github/workflows/_unit_tests.yaml that do not currently contain a default timeout property.
Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.
Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.
Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing in favour of already merged #5733


AJ-1473: dont show Authorization Domain panel for Azure workspaces

Status 4:45pm Monday Nov 20: The runtime code for this PR, in the first commit, is simple and I have tested it by running locally. In the second commit, I added my attempt at unit tests. The unit tests have some duplicated code that could be cleaned up, but more importantly they are failing with:
    TypeError: Cannot read properties of undefined (reading 'makePath')

      68 |     `No handler found for key ${name}. Valid path keys are: ${_.map('name', routeHandlersStore.get())}`
      69 |   );
    > 70 |   return handler.makePath(params);

and I need some help resolving that.

Jira Ticket: https://broadworkbench.atlassian.net/browse/AJ-1473

Summary of changes:
Remove the "Authorization Domain" panel for Azure workspaces; leave it for Google workspaces.
Why
From the Jira ticket:

Rawls returns group constraint policies as authorization domains. As a result, the authorization domains panel shows on the workspace dashboard for workspaces with group constraint policies.
However, we don’t want to mention “authorization domains” for Azure workspaces. They’ve been replaced by “data access controls” and shown in a different place on the dashboard (AJ-1460).
Thus, we should remove this panel for Azure workspaces.

Testing strategy

[ ] View an Azure workspace with auth domain. The panel should not display.
[ ] View a Google workspace with auth domain. The panel should display.

I took a look at this, and I recommend that the very minimal code change goes in without a unit test.
The issue that @davidangb is hitting is that the WorkspaceDashboard component is huge and not written in a testable fashion. It isn't just the RHS components, it's the entire page, and it has a lot of Ajax calls and state management.
Writing a unit tests for it in its current format would require a lot of Ajax mocking unrelated to the code change David is making. In fact, the existing "Dashboard.test.ts" file should be renamed "AzureStorageDetails.test.ts", as that is all it tests, and the AzureStorageDetails has been moved out into its own file. I will put in a PR for that update.
I spent a couple of hours trying to extract parts of Dashboard.ts to make whether or not the the Auth Domain section is displayed testable. I kept finding more and more things that needed to be rewritten, and I realized that this task is well beyond the scope of David's particular ticket, as it would require tests to be written for more of the dashboard so that we could be confident that nothing was broken.

@cahrens I'd approve this PR with just the oneliner change, I can park David's test efforts on another branch, and reset this one back to just having the initial commit which we could then both approve if you're ok with that approach.  That way the original PR can land with this conversation attached to it.

Note that I renamed the test in https://github.com/DataBiosphere/terra-ui/pull/4490.
I'm happy to approve the one-line change in either this PR or a new one.

Followup ticket for unit tests.


java.io.IOException in MainRobotActivity

Error in runmyrobot_android_dev
java.io.IOException in MainRobotActivity
write failed: EPIPE (Broken pipe)
View on Bugsnag
Stacktrace
IoBridge.java:558 - libcore.io.IoBridge.write

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
java.io.IOException in MainRobotActivity


Update usage of IOUtils.closeQuietly in CsvReaderDataSource to be backwards-compatible with older apache ioutils versions

See the closeSource() method where we close the csvreader variables
Try this on older 1.0 or 1.3.2 versions

Will not fix this issue: the UTF BOM byte processing is in commons-io 2.0 and so we can't work with earlier versions


Separate scene from object

This is an example of the .ply mesh created by generfacto, loaded with a render software

The objective would be to separate the background (here for the case of 3D object generation, only the object is necessary) from the created objects.

https://github.com/nerfstudio-project/nerfstudio/issues/1498


Error on attempting to run Example application

What version of electron-installer-windows are you using?
v0.2.0
What version of node and npm are you using?
node - v6.9.1
npm - 3.10.8
What operating system are you using?
OS X 10.11.6
Can you compile the example app successfully?
No
If not, paste here the output of the following commands:
$ git clone https://github.com/unindented/electron-installer-windows.git
$ cd electron-installer-windows/example
$ DEBUG='electron-installer-windows' npm run build

(previous step missing an 'npm install')
Scrollback to the output is here
https://gist.github.com/qbunt/4eebd98d63c1ba042bae8451c2860cfd
What did you do? Please include the configuration you are using for electron-installer-windows.
The above steps
What did you expect to happen?
A completed .exe build of the example app.
What actually happened?
The above error.

I should also add that this was on a fresh install of mono and wine via homebrew. Any hints here would be great, I thought the error was something caused by my application, I realize it's a very hard issue to resolve.

It sounds like an issue with Squirrel and Mono. Here's a similar report: https://github.com/electron/windows-installer/issues/63
I'm afraid I don't know that much about Squirrel's internals, so I'd suggest building on a Windows box...

For what it's worth, this is not the only project I'm unable to build with, it's been basically every project I've tried for generating exe or msi installers that fails in a similar (though not identical way). Thanks for the fast response man, feel free to close if you're confident it's something upstream out of your control. Cheers!

@unindented maybe it should note in your readme that this doesn't currently run on a Mac, it would have saved me a bunch of time.


Database backup error: Postgres subprocess ('/usr/bin/pg_dump', '--no-owner', '--file=/tmp/tmp7pm2w6fh/dump.sql', 'cTurtle98.com') error 1

on /web/database/manage I get this error when trying to backup my database
I found this old issue on odoo 12 that said this is caused by a mismatch between the expected and actually used versions of postgres
https://github.com/odoo/docker/issues/234
no clue if thats what the issue is this time.
I am using your container through truecharts on truenas scale RC1
https://truecharts.org/apps/stable/odoo/
version: 14.0_3.0.2

you can update the sql client version by this  one command  to solve the issue
apt install wget &&
sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt bullseye-pgdg main" > /etc/apt/sources.list.d/pgdg.list' &&
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add - &&
apt-get update &&
apt install postgresql-client-15 -y


Getting Data

Which topic should I use to get 1 min candles of BTC in Kucoin futures API?
How can I get the last price of BTC in kucoin futures API?
I've use '/market/candles:BTC-USDT_1min' for spot in python. What address is same as this for futures?

Hi
If you mean candles in future via websocket, it is not supported.
The topic you  mentioned belongs to Spot and we don't have it for future at the moment

We now support the following types: 1min, 3min, 5min, 15min, 30min, 1hour, 2hour, 4hour, 8hour, 12hour, 1day, 1week, 1month.
For more detailed information, please refer to our documentation: https://www.kucoin.com/docs/websocket/futures-trading/public-channels/klines


do not apply paging when grouping

This fixes the problem described in https://github.com/esvit/ng-table/issues/795 for me. The applied paging breaks the manual setting of params.total(). I am using async getData, grouping and pagination. I think my fix will break things for non asyc data but i do not know how to set the right condition. Perhaps someone could help me out here.

Review this issue #893

Ok, now i figured out that my view on grouping is different from how it is currently implemented. I thought of having count results on a page and they should be grouped. But it seems, that if grouping is enabled, count is for the number of groups on one page which is not what i expected.
I will close this PR because it does not fit in the current concept of grouping.


Trouble setting up a cluster with kubeadm (timeoutForControlPlane not recognized in config)

This is a Bug Report

Problem:
I encountered an error while using kubeadm with version v1beta4. The configuration file includes a field apiServer.timeoutForControlPlane which results in a strict decoding error: unknown field "apiServer.timeoutForControlPlane".
Proposed Solution:
The apiServer.timeoutForControlPlane field should either be supported in the kubeadm v1beta4 schema or removed from the configuration examples in the documentation if it's not a valid field. If it's deprecated or moved, the documentation should reflect the current correct field or provide migration guidance.
Page to Update:
The official kubeadm configuration documentation page needs to be updated to accurately reflect the available fields for the v1beta4 version of ClusterConfiguration. The specific page is:
kubeadm config reference

v1.32.0

When attempting to initialize a Kubernetes cluster with kubeadm, I followed the documentation and included the apiServer.timeoutForControlPlane field in the ClusterConfiguration. However, kubeadm v1beta4 does not recognize this field, causing the initialization to fail with the error message mentioned above. This discrepancy between the documentation and the actual schema can lead to confusion and should be addressed to prevent further issues for users.

/triage accepted
/priority backlog
/language en

I've attempted to write it in this manner, yet the system continues to report that it cannot recognize the input. This leaves me quite puzzled, as it seems logical that adhering to the correct format or guidelines should preclude such errors. Hence, the ClusterConfiguration.timeoutForControlPlane field has been superseded by Timeouts.controlPlaneComponentHealthCheck. Could you please clarify the proper syntax and provide an illustrative example?

There are examples in the docs, but I don't think you read it.
There are field descriptions about the type and usage, and I don't think you read it.
So ... I think this issue can be closed.

Within the documentation at https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta4/, I've observed that this detail is mentioned in the "Overview" section, with the precise content stated below:

Introduction of a Timeouts structure into InitConfiguration, JoinConfiguration, ResetConfiguration, and UpgradeConfiguration allows for the configuration of various timeouts.
The ClusterConfiguration. timeoutForControlPlane field has been superseded by Timeouts.controlPlaneComponentHealthCheck.
The JoinConfiguration.discovery. timeout has been replaced with timeouts.Discovery.

Nevertheless, I was unable to locate an instance demonstrating "The ClusterConfiguration. timeoutForControlPlane field has been superseded by Timeouts.controlPlaneComponentHealthCheck."  Could you kindly provide the URL for this specific example?

This statement is pretty clear. You are supposed to study the Timeouts structure in the InitConfiguration, JoinConfiguration ... struct. timeoutForControlPlane is gone.
Timeouts is a struct. You can search it in the reference page. You can find how it is reference from the above mentioned structs. All information are in the same page.

I apologize for the oversight. I realized that there are discrepancies between the English and Chinese documents, and I should refer to the English version. In the English version, this attribute configuration has been removed, and it is also not possible to add Timeouts in the kind ClusterConfiguration. I am very sorry for the inconvenience and appreciate the experts' patient explanations.

English document:

Chinese document:

The Chinese version has not be updated.
/close


feat(analytics): Track search events

This tracks a new "Search Performed" goal in Fathom analytics. No search query is sent! (Fathom doesn't even support it)
While the cloud offering of Meilisearch has basic "analytics" that tells us how many searches are performed, it'd be nice to have this tracked over time.
Depends on #240.

Stamping with approval but I consider this a premature split from the main PR. This would be nice to have to the main branch when you merge in the above.

They're split for easier reviews, testability, and easy reverts (generally speaking). They will be going out at the same time :-)


Claim evidence gathering

As a user, I want the system to prompt me for the evidence required to support my claim
Story Points

13

Priority

High

Risk

High

3 UI designs for system
2 UI Mockups for evidence-gathering
Validate what pieces of evidence are required by law-domain expert
Determine all possible valid piece of evidence to be supplied by the user
Obtain image/text file/decision from the user and store in database
Have a basic yes/no decision tree of what evidence to ask for

As part of this user story, we should finalize the domain of law that we will be diving into

UI Designs for both the system and the feature should be completed by this thursday, so that we can obtain feedback about it on friday.

Acceptance criteria "Chatbot is able to prompt for all possible relevant evidence in a variety of scenarios" is overly broad. We have to limit this user story's scope.

This story may also involve the creation and persistance of data in a database, that is capable of storing various types of data. Also "Have a basic yes/no decision tree of what evidence to ask for (? h)" is being worked on as a side-effect of #20.
For "Validate what pieces of evidence are required by law-domain expert", we can limit this to images of a lease and receipts

Does what it's supposed to do. Rest is in other user stories.


Update eff to 5.14.0

Updates org.atnos:eff from 5.13.0 to 5.14.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.atnos", artifactId = "eff" } ]

labels: library-update, semver-minor

Codecov Report

Merging #162 (66250bc) into master (ec4fa78) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #162   +/-   ##
=======================================
  Coverage   71.59%   71.59%
=======================================
  Files          12       12
  Lines         426      426
  Branches       23       21    -2
=======================================
  Hits          305      305
  Misses        121      121

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 ec4fa78...66250bc. Read the comment docs.


[LAB] Week 2_Problem 1_Hajin KIM

import torch
from random import random
from typing import Callable
Problem 1

Arbitary x_train, y_train are given.
Suppose that x and y have linear correlation, y=wx+b.
In function training(), you should return [w, b].
In function predict(), you should return
list y_test corresponding to x_test.
Made by @jangyoujin0917

NOTE : Feel free to use torch.optim and tensor.
def training(x_train : list[float], y_train : list[float]) -> list[float]: # DO NOT MODIFY FUNCTION NAME
# Data normalization code (prevents overflow when calculating MSE, prevents underfitting)
# Note that you need to convert [w, b] to the original scale before returning value
# w = w * (y_max - y_min)
# b = b * (y_max - y_min) + y_min
y_min = min(y_train)
y_max = max(y_train)
normalize = lambda y : (y - y_min)/(y_max - y_min) #y값은 0~1 사이로 압축한 뒤 계산.
### IMPLEMENT FROM HERE
w_init = (normalize(y_train[1])-normalize(y_train[0]))/(x_train[1]-x_train[0]) #초기값
b_init = normalize(y_train[0]) - w_init*x_train[0] #초기값
elnum = len(x_train) #원소개수
norm_y = y_train #normalize 한 ytrain
for i in range(elnum):
norm_y[i] = normalize(y_train[i])
def loss(tan : float, y0 : float) -> float:
    res = 0
    for i in range(elnum):
        res += (tan*x_train[i]+y0-norm_y[i])**2
    err = (1/(2*elnum))*res
    return err
def wdiff(tan: float, y0 : float) -> float:
    res = 0
    for i in range(elnum):
        res += ((tan*x_train[i])+y0-norm_y[i])*x_train[i]/elnum
    return res
def bdiff(tan: float, y0: float) -> float:
    res = 0
    for i in range(elnum):
        res += ((tan*x_train[i])+y0-norm_y[i])/elnum
    return res
stepsize = 0.05
w = w_init
b = b_init
for i in range(100):
    w = w - stepsize*wdiff(w, b)
    b = b - stepsize*bdiff(w, b)
    #print('loss = ' + str(loss(w,b)))#loss 확인
    #print(w, b)
return[w,b]

def predict(x_train : list[float], y_train : list[float], x_test : list[float]) -> list[float]: # DO NOT MODIFY FUNCTION NAME
[w,b] = training(x_train, y_train)
y_test = x_test
for i in range(len(x_test)):
y_test[i] = x_test[i]*w + b
return y_test
if name == 'main':
x_train = [0.0, 1.0, 2.0, 3.0, 4.0]
y_train = [3.0, 1.0, 6.0, 7.0, 10.0] # Note that not all test cases give clear line.
x_test = [5.0, 10.0, 8.0]
w, b = training(x_train, y_train)
y_test = predict(x_train, y_train, x_test)

print(w, b)
print(y_test)

Rewrite another issue. the form is broken. will be resolved.


respect timezone by itself in off hours tag

Let me know how this looks.
I’m not thrilled with the repeated parsing, but I couldn’t do the same caching trick used in parse() since the new method is static. The performance difference is probably not noticeable, but if you want me to address that, I’d probably argue for making raw_data() a stand-alone function independent from the ScheduleParser class (and create a cache variable for it outside the class as well.)

Thanks! the re-parse is fine

hmm this original pull request had some other issues, it used an instance value to change the default value on the filter processing the set.

If you’re referring to self.default_tz = raw_data['tz’], I’ve looked over the changes and that was done to influence the behavior of the subsequent call to self.get_default_schedule(). If setting that property is causing side-effects (which is sounds like it is), we can address it.
We could just store the value of default_tz before calling get_default_schedule() then restore it, but that sounds like a hack that would invite race conditions. To really fix it, we’d need to

Refactor so get_default_schedule() can use something other than default_tz
Add some tests that will fail as a result of the side-effect.

Let us know if you want us to start on that or if you’ve got something in the works.

fixes were applied in https://github.com/capitalone/cloud-custodian/pull/640


upload worker should take in a max storage radius option

the upload worker should take in a max storage radius option so that the uploads can stop once the radius is reached.
acquire the storage radius either from the /reservestate or /status
the idea is after picking an uploader node, the storage radius should be checked (of the uploader). if the radius is above the allowed maximum value, the upload should not happen.
the worker can then sleep for 5-10 min, then repeat the same thing.
this task applies to the smoke/load job in beekeeper and not the smoke job
the maximum allowed radius will be a new config option passed to the job

Released with v0.17.0 (https://github.com/ethersphere/beekeeper/releases/tag/v0.17.0)