Attempting to refresh items on compendium actors results in error

For example, I tried refreshing "Ezren (Level 1)"'s "Staff", "Hand of the Apprentice", and "Cooperative Nature":
pf2e.mjs:1 Uncaught (in promise) Error: PF2e System | Item "Staff" (Compendium.pf2e.iconics.Actor.WNX5OQKPh4uaV7mW.Item.epNtNWhBdtOOmHYs) is its own source.
    at ErrorPF2e (pf2e.mjs:1:8618)
    at WeaponPF2e.refreshFromCompendium (pf2e.mjs:1580:215786)
    at Object.onclick (pf2e.mjs:1607:56784)
    at HTMLAnchorElement.<anonymous> (foundry.js:5982:16)
    at HTMLAnchorElement.dispatch (jquery.min.js:2:40035)
    at v.handle (jquery.min.js:2:38006)
ErrorPF2e @ pf2e.mjs:1
refreshFromCompendium @ pf2e.mjs:1580

pf2e.mjs:1 Uncaught (in promise) Error: PF2e System | Item "Hand of the Apprentice" (Compendium.pf2e.iconics.Actor.WNX5OQKPh4uaV7mW.Item.pnIzRwwzr80qTOcw) is its own source.
    at ErrorPF2e (pf2e.mjs:1:8618)
    at SpellPF2e.refreshFromCompendium (pf2e.mjs:1580:215786)
    at Object.onclick (pf2e.mjs:1607:56784)
    at HTMLAnchorElement.<anonymous> (foundry.js:5982:16)
    at HTMLAnchorElement.dispatch (jquery.min.js:2:40035)
    at v.handle (jquery.min.js:2:38006)
ErrorPF2e @ pf2e.mjs:1
refreshFromCompendium @ pf2e.mjs:1580

pf2e.mjs:1 Uncaught (in promise) Error: PF2e System | Item "Cooperative Nature" (Compendium.pf2e.iconics.Actor.WNX5OQKPh4uaV7mW.Item.tU36WCoQKCSx7dgW) is its own source.
    at ErrorPF2e (pf2e.mjs:1:8618)
    at FeatPF2e.refreshFromCompendium (pf2e.mjs:1580:215786)
    at Object.onclick (pf2e.mjs:1607:56784)
    at HTMLAnchorElement.<anonymous> (foundry.js:5982:16)
    at HTMLAnchorElement.dispatch (jquery.min.js:2:40035)
    at v.handle (jquery.min.js:2:38006)
ErrorPF2e @ pf2e.mjs:1
refreshFromCompendium @ pf2e.mjs:1580

Are they in fact their own sources? That error is only thrown when the item's UUID is identical to its source ID.

Sorry, missed your question.
No, Ezren's Hand of the Apprentice is:
"_id": "pnIzRwwzr80qTOcw",
"flags": {
	"core": {
		"sourceId": "Compendium.pf2e.spells-srd.Item.bSDTWUIvgXkBaEv8"
	}
}

Attempting to refresh it emits:
pf2e.mjs:1 Uncaught (in promise) Error: PF2e System | Item "Hand of the Apprentice" (Compendium.pf2e.iconics.Actor.WNX5OQKPh4uaV7mW.Item.pnIzRwwzr80qTOcw) is its own source.

It's important to note that it must be a Compendium actor. Imported actors work fine.

@ammalagonc and @pedrogrullada were able to reproduce the issue.

Repro'd. The thing to stress is that its a compendium actor. The reason is that item.sourceId is always the uuid if its a compendium even if its embedded.


angles: 1.9.10-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository angles to 1.9.10-0:

upstream repository: https://github.com/ros/angles
release repository: https://github.com/ros-gbp/geometry_angles_utils-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.21
previous version for package: 1.9.9-0

angles
* Export architecture_independent flag in package.xml
* Simply and improve performance of shortest_angular_distance(). adding two unit test cases
* check for CATKIN_ENABLE_TESTING
* Contributors: Derek King, Lukas Bulwahn, Scott K Logan, Tully Foote

hold for coordinated


Output test results in JUnit/NUnit/XUnit format

We should write the test results in a standard format, such as JUnit/NUnit/XUnit.
This will allow Visual Studio, VS Code, CI systems and others to parse and present results in a concise format.

Minimal JUnit format output has been implemented.
Once we have reverse lookup working, so we can translate machine address => file:line, we should include file:line info in the failure reports.
Closing for now though.


Fix nested listing and indentation.

Purpose / why
In the Migration overview page, the nested listing didn't render properly.
What changes were made?
Used four spaces instead of two to indent! Github works with 2, but mkdocs needs 4.
Verification
Does the pretty version look right?
Interested Parties
@ysuarez

Checklist

Pull-request reviewer should ensure the following

[ ] Does this PR link to related issues?
[ ] Does the proposed documentation align with the Islandora Documentation Style Guide?
[ ] Are the changes accurate, useful, free of typos, etc?

Person merging should ensure the following

[ ] Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
[ ] If pages are renamed or removed, have all internal links to those pages been fixed?
[ ] If pages are added, have they been linked to or placed in the menu?
[ ] Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

Thanks for fixing my error, and great job updating the style guide.

There's one more list that I think didn't get fixed? Lines 36-38, under Migrate API. Sorry for missing it on my first pass!

Thanks @manez - I think I fixed it.


OBS sometimes segfaults when using screen capture with xdg-desktop-portal-wlr/sway

Describe the bug
I use Sway as Wayland compositor/server and OBS to experiment with screen / window captures.
Currently, window captures just don't work as expected, and instead result in the whole screen being captured.
Screen captures mostly work, but OBS or OBS pipewire threads might segfault when trying to remove the capture from the OBS scene.
e.g. might result in some dmesg messages like (on NixOS 21.11 17f73e226198a511a74a953758ceed6efdad9444 x86-64):
[ 1861.495128] PipeWire thread[6089]: segfault at 7f838c758020 ip 00007f83a295de15 sp 00007f83321ed098 error 4 in libc-2.33.so[7f83a284e000+143000]
[ 1861.495151] Code: 65 05 00 77 20 4d 63 0c 93 48 01 d6 48 01 d7 4d 01 d9 41 ff e1 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 40 38 fe 7e 5b <f3> 0f 6f 06 48 89 f9 48 83 e7 f0 48 83 c7 10 49 89 c8 48 29 f9 48
[ 1877.434762] PipeWire thread[6177]: segfault at 7f8ffdcac000 ip 00007f906e8bdf78 sp 00007f8ffe70d098 error 4 in libc-2.33.so[7f906e7ae000+143000]
[ 1877.434776] Code: 00 00 00 66 0f 6f 26 0f 28 4e 10 0f 28 56 20 0f 28 5e 30 66 0f 7f 27 0f 29 4f 10 0f 29 57 20 0f 29 5f 30 48 81 ea 80 00 00 00 <0f> 28 66 40 0f 28 6e 50 0f 28 76 60 0f 28 7e 70 48 8d b6 80 00 00
[ 2175.654634] .obs-wrapped[6228]: segfault at 1cf ip 00007f228ede1d55 sp 00007fff071e9d38 error 4 in libobs.so.0[7f228edad000+a2000]
[ 2175.654644] Code: fc ff 48 85 c0 74 13 48 89 c2 48 f7 d2 83 e2 1f 48 83 c2 01 48 01 d0 88 50 ff 48 83 c4 08 c3 66 0f 1f 44 00 00 48 85 ff 74 13 <48> 0f be 47 ff 48 29 c7 e9 7e c9 fc ff 66 0f 1f 44 00 00 c3 0f 1f

obs segfault
gdb asm snippet
│    0x7f228ede1d4a                  nopw   0x0(%rax,%rax,1)
│    0x7f228ede1d50 <a_free>         test   %rdi,%rdi
│    0x7f228ede1d53 <a_free+3>       je     0x7f228ede1d68 <a_free+24>
│  > 0x7f228ede1d55 <a_free+5>       movsbq -0x1(%rdi),%rax
│    0x7f228ede1d5a <a_free+10>      sub    %rax,%rdi
│    0x7f228ede1d5d <a_free+13>      jmp    0x7f228edae6e0 <free@plt>
│    0x7f228ede1d62 <a_free+18>      nopw   0x0(%rax,%rax,1)
│    0x7f228ede1d68 <a_free+24>      ret
│    0x7f228ede1d69                  nopl   0x0(%rax)

gdb backtrace
#0  0x00007f228ede1d55 in a_free () from /nix/store/3qwn9mhnpy8q2b7nfxbp7czc6lhiywlh-obs-studio-27.0.1/lib/libobs.so.0
#1  0x00007f2237d51ae8 in update_info_destroy () from /nix/store/3qwn9mhnpy8q2b7nfxbp7czc6lhiywlh-obs-studio-27.0.1//lib/obs-plugins/rtmp-services.so
#2  0x00007f2237d50900 in obs_module_unload () from /nix/store/3qwn9mhnpy8q2b7nfxbp7czc6lhiywlh-obs-studio-27.0.1//lib/obs-plugins/rtmp-services.so
#3  0x00007f228ee392fc in free_module () from /nix/store/3qwn9mhnpy8q2b7nfxbp7czc6lhiywlh-obs-studio-27.0.1/lib/libobs.so.0
#4  0x00007f228ee13fcf in obs_shutdown () from /nix/store/3qwn9mhnpy8q2b7nfxbp7czc6lhiywlh-obs-studio-27.0.1/lib/libobs.so.0
#5  0x00000000004b11d5 in OBSApp::~OBSApp() ()
#6  0x000000000048238b in main ()

Steps To Reproduce
Non-deterministic, I don't know what exactly causes the behavior, besides the stuff mentioned above.
Expected behavior
Neither pipewire threads nor OBS should segfault when trying to remove a screen-sharing connection.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.76, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.5pre20211108_7a71621`
 - nixpkgs: `/etc/nix-flake-channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  - obs-studio
  - pipewire
  - xdg-desktop-portal-wlr
# a list of nixos modules affected by the problem
module:

We've packaged new versions of OBS and a new pipewire capture plugin. Closing this for now since this is an old issue. Please reopen if this still is an issue.


runtime: wrong Unix error code from panic.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +baf3eb1625 Tue Mar 6 01:11:26 2018 +0000 darwin/amd64
% cat p.go
package main

func main() {
	panic(3)
}
% ./p
panic: 3

goroutine 1 [running]:
main.main()
	/Users/r/p.go:4 +0x39
% echo $?
2
%

Exit code 2 traditionally means 'incorrect arguments', as in flag.Usage.
Panic should be something like 127 or 255 on Unix.
Reported by<EMAIL_ADDRESS>on nuts.

or simply 1 meaning 'general error' ?
(http://tldp.org/LDP/abs/html/exitcodes.html)

As has been pointed out in the mail thread, it might be best to leave this alone and say that the error that triggered this is in a program that takes exit code 2 as 'success'. That is certainly nonstandard.

Sure, although a note in the language spec might avoid some similar confusion in the future..
I'll open an issue with Supervisor (http://supervisord.org/)

E-mail thread is at https://groups.google.com/d/msg/golang-nuts/u9NgKibJsKI/XxCdDihFDAAJ .

Thanks!

How's it going @cachvico? Any news from filing the bug with Supervisord?
@ianlancetaylor sure let's document in the spec that a panic returns a non-zero code to the shell.
@robpike @aclements shall we proceed with making a panic return 127 or 255? @robpike if you might have time, a reference to a UNIX manual would be useful for us to include in the commit for posterity.

Thanks - note that the Supervisord issue should be fixed on their side as per the above linked issue.

Exit status 127 is used by the shell to indicate "command not found."
Exit status 126 is used by the shell to indicate "command found but not executable."
Exit status values 128 and up are used by the shell to indicate exiting due to a signal.
If a C++ program exits due to an uncaught throw it raises SIGABRT and therefore exits with status 134 (on GNU/Linux).
If a Python program exits due to raising an exception, it exits with status 1.
I think we should change an unrecovered panic to exit with status 1 rather than 2.  And we should document in the language spec that an uncaught panic will cause the program to exit with a non-zero exit status, but we shouldn't document it further.

The quickest solution to the original problem would simply be a correction to the spec at https://golang.org/pkg/builtin/#panic
I've submitted a change at https://go-review.googlesource.com/c/go/+/167709 - is this correct?

Beg pardon - just realised the previous post said not to document the value explicitly.
May I make the change to  suggested by @ianlancetaylor to change the 2 to 1, and correct my change to the comment appropriately?
This would involve an edit to src/runtime/signal_sighandler.go line 151.

I've submitted a change at https://go-review.googlesource.com/c/go/+/167709 - is this correct?

Thanks for submitting the change @cachvico! I've posted some comments  on it.

May I make the change suggested by @ianlancetaylor to change the process exit code 2 to 1, and correct my change to the comment appropriately?
This would involve an edit to src/runtime/signal_sighandler.go line 151, and a supporting test-case.

Oh yes you can, all yours but we can review and submit those changes piece-meal/independent of the docs update.

@ianlancetaylor Note that only values greater than 128 are used by the shell to indicate exiting due to a signal.

Exit status values 128 and up are used by the shell to indicate exiting due to a signal.

Some documents indicate that 128 is used to indicate an invalid argument to shell builtin exit, but POSIX leave that behavior unspecified.

@Gnouc Thanks for the correction.

Docs updated in https://github.com/golang/go/commit/f947c4dcfe6f22e6c92e6e5a170096b518a18448 to reflect the behaviour of panic()
Thanks all!


Multipart requests do not work

Multipart requests, for example in default_api::system_restore_post, are not implemented.

:thinking: c7cbe7b74d69db328767489e2ab1b5e2fb31598c adds dependency on the multipart crate which is unmaintained for a year (see RUSTSEC-2023-0050).
Would it be possible to use one of the alternatives listed there? (e.g. multer or multiparty)
Thanks for your time! :wave:

I’m aware of the problem but I don’t know a suitable replacement.  multer and multipart only support multipart decoding, not encoding.

I’ve created https://github.com/Nitrokey/nethsm-sdk-rs/issues/29 to keep track of the issue.

I’m aware of the problem but I don’t know a suitable replacement. multer and multiparty only support multipart decoding, not encoding.

Oh, I see. I wonder what would be the effort of writing a limited scope encoder. I haven't checked the usages yet so this may be a very bad idea 😅

It should not be that hard.  I just did not want to include it in this crate directly because I think it should be maintained and tested separately, and I did not want to do that myself unless there are concrete issues with multipart other than being unmaintained.  If you want to look into that, I’m happy to test and eventually migrate.

Agreed. I'll check out if it makes sense to extend existing crates. Thanks for the explanation! 👋


Unable to create /usr/share/jenkins/gituser

I was just trying to run through the documentation and try out the jenkins version of the demo and ran into this problem when trying to run
./start.sh gitUser gitPass gitOrg
Obviously with my real credentials and what not in there and got this error during starting up the containers via docker-compose
/bin/sh: 1: cannot create /usr/share/jenkins/gituser: Permission denied
ERROR: Service 'jenkins' failed to build: The command '/bin/sh -c printf "%s" "${gituser}" > /usr/share/jenkins/gituser' returned a non-zero code: 2
Looking into the Dockerfile I added my credentials there as well (that's a documentation miss I think)
Tried again, same error, which isn't shocking because my change has nothing to do with permissions.
Using ROOT that error disappears, and the credentials appear in jenkins (which I think is all that's doing there) so it seems like a viable solution.
I'm using Mac OS X El Capitan, Docker for Mac 1.12.1, and Virtual Box 5.1.8

So as you can see in the dockerfile we're using ARGS. They are passed from Docker Compose. The script start.sh is passing the username and password via env vars to docker compose. Everything works smoothly. interesting why it's not working for you

Looking into the Dockerfile I added my credentials there as well (that's a documentation miss I think)

This is obviously not the case cause the credentials are passed via args

I too had this issue.  I resolved it by moving the declaration of "USER root" above the RUN commands in the DockerFile.
....
USER root
Generated via start.sh
If you don't want to provide it just put empty files there
RUN printf "%s" "${gituser}" > /usr/share/jenkins/gituser
RUN printf "%s" "${gitpass}" > /usr/share/jenkins/gitpass
Moved to above the RUN commands.
USER root
RUN apt-get update && apt-get install -y
ruby
curl
USER jenkins
....

Fixed


🚀 Feature: Report file name where a test fails

Is it possible to have mocha report the filename containing a failed test? Could I write a reporter that did this? Or would I have to build support for it, and then write such a reporter? Not at all familiar w/ the mocha codebase yet, but I'd be willing to take a dive in and try out contributing this if the Mocha community would welcome it.
After a test fails, I frequently find myself grepping the title of the test to determine the filename so I can then run the test in isolation.
Reporting the filename would save me a step.

I wrote a quick and dirty reporter plugin that seems to be working to accomplish this.
mocha-spec-reporter-with-file-names
output looks like this:

I've been bit by this before. It's quite annoying to run a large test suite containing dynamically generated test names with misleading call stacks, then have to manually figure out where the tests are coming from.
https://www.npmjs.com/package/mocha-spec-reporter-with-file-names looks like a pretty great solution. Nice job @electrovir 😄.
Per #5027, we want to be very careful with landing new big features. Even if they're in output designed to be human-readable and not consumed by machines. So this would be a semver-major I think.
cc @mochajs/maintenance-crew: any objections?

Talking with @voxpelli: this is an issue, interestingly, with quite a few default reporters.
$ npx mocha packages/hello-world/test.spec.js --reporter nyan
 0   -__,------,
 1   -__|  /\_/\
 0   -_~|_( x .x)
     -_ ""  ""

  0 passing (2s)
  1 failing

  1) a mocha test that times out
       does not display the filename containing the failing test:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/josh/repos/mocha-examples/packages/hello-world/test.spec.js)
      at listOnTimeout (node:internal/timers:573:17)
      at process.processTimers (node:internal/timers:514:7)

This brings up another question: should the file name always be there? Or just when the test fails? We're thinking always, for consistency.
Note that built-in reporters generally use the Base reporter's epilogue method. So fixing this is likely to involve modifying Base. But there might be reporters that add in their own logic. Investigation required.


Is this package still maintained?

There's a lot of issues and PRs don't get any attention from maintainers.
Should the package be marked as obsolete?
Not to blame anyone, just to make it clear.

Haven't had any resources left for open source in a long time. I'll try to get some things done soon :)


Add clarity to slot arithmetic functions.

Issue Number
Indirectly related to #466.
Overview
This PR refactors existing slot arithmetic functions to make them easier to call, and to make their behaviour more obvious.
It also adds a set of tests to verify that these refactorings are correct.

we don't know what the future is made of, so let's not add things that might possibly be used.
Let's add them when needed.

These functions are already used.
Their existence makes it convenient to express the following two laws, which are tested:
slotSucc . slotStartingAtOrJustBefore . utcTimePred . slotStartTime == id
slotPred . slotStartingAtOrJustAfter  . utcTimeSucc . slotStartTime == id

maybe it is possible to use those functions somewhere in code as a invariant???

maybe it is possible to use those functions somewhere in code as a invariant???

Interesting. Could you give an example?


go.dev: Displayed README is parent’s, not the current package’s

What is the URL of the page with the issue?
https://pkg.go.dev/github.com/clipperhouse/uax29/words?tab=overview
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
Screenshot

What did you do?
Viewed the overview tab for package documentation on pkg.go.dev (URL above)
What did you expect to see?
The README for the package words
What did you see instead?
The README for the parent package (module) uax29
Thanks!

Thanks for the feedback! We are planning to add this feature in an upcoming round of design changes.
Closing as a duplicate of #38513.


Removed no longer available [PyPI] examples and cleaned up code

See #716 for more details.
The downloads badges are no longer available, so I removed the examples from the homepage. Also switched to our getDeprecatedBadge helper and removed the commented code.

Warnings

:warning:

This PR modified the server but none of the service tests. That's okay so long as it's refactoring existing code.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @PyvesB!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS

Hey, thanks for addressing this. I removed this code as part of #1922 which needs to be reviewed.
I did not remove the badge examples, though I'd be happy to do that.

Oh, I didn't realise that was in flight as well. Feel free to close this once you've removed the examples!

Done! See aa76bb8a462e56c04acd6b5ab354ce6daf9a391a.


[Bug] 事务数过多，导致入库失败，过早的事务为什么还没有被提交？

Search before asking

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

Version
Doris-2.0.2
What's Wrong?
questions:
1.meet error status: [ANALYSIS_ERROR]errCode = 2, detailMessage = current running txns on db 805314 is 1000, larger than limit 1000.
2.Why are there so many previous transactions not processed or submitted？
3.When using stream_load for storage, when the number of transactions exceeds 1000, what is the quick solution?
What You Expected?
When using stream_load for storage, when the number of transactions exceeds 1000, what is the quick solution?
Should you restart the be every time when the problem occurs?
Or，how can we clear premature and unhandled transactions?
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

The quick workaround is to manually stop running transactions: curl -X PUT --location-trusted -u user:passwd  -H "txn_id: 805314" -H "txn_operation:abort"  http://fe_host:http_port/api/{db}/{table}/_stream_load_2pc

You can also increase the corresponding parameters
https://doris.apache.org/zh-CN/docs/dev/admin-manual/config/fe-config/#max_running_txn_num_per_db

The quick workaround is to manually stop running transactions: curl -X PUT --location-trusted -u user:passwd  -H "txn_id: 805314" -H "txn_operation:abort"  http://fe_host:http_port/api/{db}/{table}/_stream_load_2pc
-------How to find out which table the transaction is for？？？？？？thanks

The quick workaround is to manually stop running transactions: curl -X PUT --location-trusted -u user:passwd  -H "txn_id: 805314" -H "txn_operation:abort"  http://fe_host:http_port/api/{db}/{table}/_stream_load_2pc
-------How to find out which table the transaction is for？？？？？？thanks

On doris's web page.
http://fe_host:http_port/System?path=/transactions


Dead code elimination

Can Brunch eliminate dead, unused code from the build like http://stealjs.com/ ? If not, any plans to adding this?

Plugins may do everything. Brunch does not do almost anything opinionated per se.

So, the answer is: you can write a plugin for StealJS or so, that should work.


[fix] #366 fix etcd pod failed to exit init container

fix : https://github.com/coreos/vault-operator/issues/366
I tried Getting start on README.md and apply configs on example/ dir.
but, vault didn't start.
Because etcd-operator fail to exit init container and don't start.
This problem is bug of etcd-operator version 0.8.3.
It fixed to version 0.8.4.
https://github.com/coreos/etcd-operator/blob/master/CHANGELOG.md
Please update etcd-operator from example/ dir.

Thank you. I've stuck by the example for a long time.


roomSearch using Promise.all might cause hostie connection issue

Related to https://github.com/wechaty/wechaty-puppet-hostie/issues/31
Currently the code logic for roomSearch in wechaty-puppet is not using batch operation, like below:
https://github.com/wechaty/wechaty-puppet/blob/804b31b970e931547238d59de43847178a2869cd/src/puppet.ts#L1174-L1212
When the query is passed to the function, it will do a Promise.all() of all rooms, which might cause the problem that we've been fighting for a long time, the grpc issue. So I think we need to use batch operation for this method to avoid the grpc problem.

Thank your very much for this great improvement!

Let's close this issue since the problem should be fixed.

I'm planning to use async pool or iterator worker to implement a Promise.all() with a concurrency limitation.


Switch to using the TIF companion library

See: http://android-developers.blogspot.com/2016/11/adding-tv-channels-to-your-app-with-the-tif-companion-library.html

Is this the successor to the ChannelSurfer library?

Yes, ChannelSurfer is being deprecated

Work on updating library and ExoPlayer now

With TIF supporting both channel icon as well as channel banner, will we see both implemented via cumulus? I'd love to be able to use a white channel icon for the channel and coloured banner within cumulus tv itself.
Examples of both at http://tv.cramer.id.au/indonesia for example.

TIF does not support a channel icon & banner, just a single image for the channel. See the Channel class for all possible attributes.
A program can contain a poster and thumbnail, although I don't know what is done with the poster art. The thumbnail is displayed in the guide.
With regards to the original issue, this is now working and will be in the upcoming beta.


Database tables edits - errors in paypal_standard module

A couple of edit errors in paypal_standard.php when deprecating includes/database_tables.php

Thanks for the PR! This has already been fixed.


Update sbt-scalajs to 1.5.1

Updates org.scala-js:sbt-scalajs from 0.6.33 to 1.5.1.
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.scala-js", artifactId = "sbt-scalajs" } ]

labels: sbt-plugin-update, semver-major

Superseded by #199.


[Feature Request]: Drag & Drop - size of table is not fixed.

How would you like to enhance the existing project.
Enhancement
size of table is not matched with background

box
Describe breifly how would you implement the same.
Solution_steps

src -> games -> Drag & Drop -> App.css
Change the table size in class table.

Are you contributing for a program?
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hi @hetero-1 , I am assigning this task to you. Kindly complete within a week. Good luck for your work.

hi @panwar8279, is it okay or can I do anything else ?


Change default branch name from master to main

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
For context: https://github.com/github/renaming
Describe the solution you'd like
Change default branch name from master to main
Describe alternatives you've considered
Additional context

Duplicate of #2173  ;)

Closed as duplicate


license

can you put a license? i really want to make a brackets plugin for this

package.json tells us that the current version of the code is licensed under an MIT license.

Correct, MIT license.

@falafflepotatoe How do you intend for the plugin to work? I did consider it previously, then concluded that pretty much all editors allow you to run configure commands already, and its easy to integrate that way.

pretty much that, and possibley code a qui to allow the user to configure via gui instead of via args or conf files.


WebDevIconsGetFileTypeSymbol: use if/else

sorry for the delay. will try to get this in for next release


[WIP] Better handling of uniqueness

Current coverage is 62.26% (diff: 59.42%)

Merging #7 into master will decrease coverage by 0.46%

@@             master         #7   diff @@
==========================================
  Files            24         25     +1
  Lines           746        811    +65
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            468        505    +37
- Misses          278        306    +28
  Partials          0          0

Powered by Codecov. Last update 3cd87f0...a045eee


[Coverity CID :197618]Error handling issues in /subsys/shell/shell_telnet.c

Static code scan issues seen in File: /subsys/shell/shell_telnet.c
Category: Error handling issues
Function: read
Component: Other
CID: 197618
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

*** CID 197618:  Error handling issues  (CHECKED_RETURN)
/subsys/shell/shell_telnet.c: 458 in read()
452     if (read_len > length) {
453     read_len = length;
454     flush = false;
455     }
456
457     *cnt = read_len;

CID 197618:  Error handling issues  (CHECKED_RETURN)
Calling "net_pkt_read" without checking return value (as is done elsewhere 26 out of 30 times).

458     net_pkt_read(pkt, data, read_len);
459
460     if (flush) {
461     (void)k_fifo_get(&sh_telnet->rx_fifo, K_NO_WAIT);
462     net_pkt_unref(pkt);
463     }


Indigo game only ever receives a single ViewportResize event.

It seems that in Indigo 0.12.0 (on Windows, in Electron), my game is no longer receiving ViewportResize events.
A single ViewportResize event is emitted when Indigo is done loading the game initially, but no such events are emitted when manually resizing the Electron window, or toggling fullscreen mode.

This might just be that the support js scripts that tell the canvas to resize when the window is resized as using the wrong canvas name or something.
A simple test:
Open the inspector (in electron) and use it to resize the canvas element - do you get the resize event?

Yeah, that gives the resize event.

It's an unfortunate oversight follow the canvas renaming work, the problem is here:
https://github.com/PurpleKingdomGames/indigo/blob/master/indigo-plugin/indigo-plugin/src/indigoplugin/templates/SupportScriptTemplate.scala#L25
Compared to...

I think I'll try and do the fix for this and push out another release since most people won't have been affected yet.


Add option to handle 'dead letters' by sending them to a dead letter queue rather than a dead leter topic

I had some trouble getting the behaviour I wanted from the pubsub component regarding handling 'dead letters'. I'm using RabbitMQ as the pubsub tech. I expected when I forced a drop from the consumer (by sending '"status": "drop"' in the reply) that it would immediately send the message to a RabbitMQ dead letter queue. Instead I found I could configure it to post the message to another topic. In my case I called it deadlettertopic and I sent all message types that were programmatically dropped (or exceeded their retry policy) to that topic. Within the topic consumer I sent these messages (including the cloud events data by NOT using .UseCloudEvents) to a specific queue in RabbitMQ via dapr bindings.
It would be much nicer if I could configure either the pubsub component or the consumer to send all dead letters to a nominated queue directly. I realise that different implementations of the pubsub component have different capabilities but some 'do this if supported' capability would be nice.

@WillPilgrim This would be a good issue for the dapr/components-contrib repo as it'd likely need to be something that was done per-pub-sub component.

No worries. I've moved it to dapr/components-contrib

Closing the issue here as the OP reposted at https://github.com/dapr/components-contrib/issues/3407


Fix wrong parse result from a block sequence as a nested block mapping value

This PR has fixed a wrong parse result generated from a YAML document which contains a block sequence as a nested block mapping value in the middle like the following:
foo:
  bar:
  - 123
  baz: true

The baz: true part mistakenly became a part of the bar block sequence's entry.
For the parser didn't get back to the proper node when a block sequence entry prefix (- ) is as much indented as the parent mapping keys before parsing the baz key. (if the prefix is more indented than the keys, the parse result was correct.)
So, this PR has fixed the node traversal logic and added a new test case to validate the change.
With the fix, the above YAML document is now parsed as expected.

Pull Request Checklist
Read the CONTRIBUTING.md file for detailed information.

[x] Changes are described in the pull request or in a referenced issue.
[x] The test suite compiles and runs without any error.
[x] The code coverage on your branch is 100%.
[x] The documentation is updated if you added/changed a feature.

Please don't

The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
Please refrain from proposing changes that would break YAML specifications. If you propose a conformant extension of YAML to be supported by the library, please motivate this extension.
Please do not open pull requests that address multiple issues.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
3971

Relevant Lines:
3971

💛  - Coveralls


Formalize when we're allowed to make breaking changes in bindings in a proposal

I think we just don't? We break when the underlying API breaks.
We can formalize this of course.

I really want the ability to disable overloads if we reasonably think they are just plain wrong and/or are causing issues en masse in our userbase.
So yeah we need to discuss with the working group when a breaking change is allowed in a minor release, and also discuss whether a ABI break (but not API break) is acceptable as well maybe?

@Perksey wasn't this part of one of the proposals? Or do you want to further discuss specifically disabling extensions

Yes this can be closed once the proposals PR is merged

...or now I guess


chore: enable GraphiQL via feature flag

This sets the GraphiQL feature behind a feature flag and is breaking change in case a user uses the playground module right now. In this case, simply add the feature graphiql to your list of features:
async-graphql = { version = "5.0.5", features = ["graphiql"] }

maybe won't have to be breaking change, if graphiql is added to the default feature flags list?

maybe won't have to be breaking change, if graphiql is added to the default feature flags list?

Yes, would be fine for me as well as written here: https://github.com/async-graphql/async-graphql/pull/1182#issuecomment-1374914891 :)
If you prefer, I will add it as feature. My decision was based on the current README citing that all features are optional. I would adapt the README then accordingly.

maybe won't have to be breaking change or rather less of a breaking change, if graphiql is added to the default feature flags list?

it's separated and enabled by default now.

thanks! 🙂


cmake: build all runtime tests

Referenced issues
Currently the two subfolders binaryen and wavm of test/core/runtime are not included when building the testsuite.
Description of the Change
This patch add the two missing subfolders and their respective CMakeLists.txt file to CMake's the build tree.
Build currently fails because the added tests never compiled when committed in the first place and new changes e.g. in #914 added to that.
Benefits
Once compilation issues are resolved, the new tests for both runtime backends are build and executed.
Possible Drawbacks
Somebody now has to fix all the broken tests in these subfolders.

Replaced by #952.


wrong layout direction while the app language is deferent than local

Summary:
when the phone is in Arabic the layout is RTL
Steps to reproduce:
set your local to any Arabic country and the template will always be RTL despite the app being English
Expected behavior:
the app must be LTR layout
Additional notes:
Tasks

[ ] Task 1
[ ] Task 2
[ ] Task 3

+1


nsd: 4.1.25 -> 4.1.26

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/nsd/versions.
meta.description for nsd is: '"Authoritative only, high performance, simple and open source name server"'.

Checks done (click to expand)

built on NixOS
/nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26/bin/nsd passed the binary check.
Warning: no invocation of /nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26/bin/nsd-checkconf had a zero exit code or showed the expected version
/nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26/bin/nsd-checkzone passed the binary check.
Warning: no invocation of /nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26/bin/nsd-control had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26/bin/nsd-control-setup had a zero exit code or showed the expected version
2 of 5 passed binary check by having a zero exit code.
0 of 5 passed binary check by having the new version present in output.
found 4.1.26 with grep in /nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26
directory tree listing: https://gist.github.com/d8f62c7583dbe7e3bc1fc7614592a7c4
du listing: https://gist.github.com/f519e0c36a32b0479c6b13cec3bb7d81

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

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
nsd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pah3ifk5zh8xqw6yfv404g2ykrdb8h52-nsd-4.1.26 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A nsd https://github.com/r-ryantm/nixpkgs/archive/1679fec4aa3fa8409e73df5fae627bc8258ebd9d.tar.gz

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

cc @hrdinka for testing.

Tested locally and cherry picked onto master in 2b0b12223f4fe81f900553229350b2a2f1c91686, thanks!


More efficient try!() alternative

Our generated code uses the standard try! macro heavily.
match $expr {
    Ok(val) => val,
    Err(err) => {
        return Err(From::from(err))
    }
}

I think practically none of our uses of try! rely on the From::from conversion (i.e. it resolves to the impl From<T> for T). Let's experiment with generating code that omits the conversion and see whether that improves the compile times of the generated code.

Do you want a(n allow-by-default) lint for that?

Thanks! Let's wait until we find out that this helps compile time measurably.
(Or do you mean as a way to help me find all the try! that need to be changed? I'm not worried about that, I can just replace them all and then change back the few that fail to compile.)

I meant more to not regress in the future

Testing against our json-benchmark with --bin json-benchmark --no-default-features --features parse-struct,all-files,lib-serde it looks like the more efficient try!() results in 15% faster "item-bodies checking", 25% faster "borrow checking", 2% faster debug compile overall, 0.6% smaller debug binary, and 0.2% small release binary.


Measurement Noise

In the 15-year data set there is one pulsar that doesn't have an EFAC parameter for one of the backends in the noise files, but does have an EQUAD value. I'm not sure how this comes about, but it is not supported at the moment with the tempo 2 convention (which is also followed in enterprise) that uses both EFAC and EQUAD together.
One solution is to include adding extra flag parameters in the function to add measurement noise so that one can choose. I need to investigate how this pulsar is handled by enterprise in order to make a "consistent" solution. I suspect the right thing to do is to add a default EFAC value of 1 when EFAC is missing and the corresponding EQUAD value is nonzero for a particular backend.

Measurement noise has the value 1.02 in the CW noise dict for this pulsar. The default behavior in enterprise is to set such values to 1.0. Either of these is a good solution here, it seems.


[BUG] @types/express should be peerDependency instead of hard dependency

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
cds-types causes errors when @types/express version listed in cds-types dependencies doesn't correspond to the one used in your own project.
Using v5.0.0 in your own project conflicts with v4.17.21 hard dependency listed in cds-types dependencies.
Expected Behavior
User should be allowed to use >=4.17.21 @types/express version without any errors.
Versions

Package
Version

@cap-js/asyncapi
1.0.2

@cap-js/cds-types
0.8.0

@cap-js/openapi
1.1.0

@cap-js/postgres
1.10.4

@sap/cds
8.5.1

@sap/cds-compiler
5.5.2

@sap/cds-dk
8.5.1

@sap/cds-fiori
1.2.8

@sap/cds-foss
5.0.1

@sap/cds-mtxs
2.4.1

@sap/eslint-plugin-cds
3.1.2

Node.js
v20.18.0

Anything else? Logs?
No response

Hi Tomas,
thanks for your report. What are those errors?
Best,
Daniel

Hi Tomas,
thanks for adding the error!
As express separates its types from its implementation, and we also have to support pure JS projects, we unfortunately cannot assume that user projects always have @types/express available. But I agree that the current situation is not satisfying and I will check back if we can at least upgrade the dependency to v5.
Best,
Daniel

If you use npm or pnpm peerDependencies will be installed automatically. No need for the user to do anything.
Only if you explicitly mark peerDependency as optional, the installation will be skipped.

Hi Tomas,
thanks for pointing this out! This behaviour has indeed changed a few versions of npm ago and I was not aware of this. That does make this change much easier and viable.
Best,
Daniel


Remove commented code

NB: Generally, it's best to remove commented code. We have git history if we need to get it back. https://kentcdodds.com/blog/please-dont-commit-commented-out-code
Originally posted by @lparsons in https://github.com/Princeton-LSI-ResearchComputing/tracebase/pull/273#discussion_r763375149

Appears to have been removed.


use _old_length as isize - size as isize to avoid subtract with overflow

closes #486

old_length >= size should always be true at that point.
If there's some edge case that is leading to that not being true, the root cause should be fixed instead of "fixing" it by allowing the overflow here.
If it's happening because you're using unsafe to concurrently call TcpSocket methods from multiple threads, you should fix your code. You may never ever have two &muts to the same thing concurrently. If you're doing that, the overflow here is the least of your problems. The TcpSocket internal state will get arbitrarily corrupted. You will have more crashes, you will have data corruption.

I see, the socket buffer is not thread-safe either. There is no way of multithreadedly using TcpSocket(or any part of smoltcp) safely without an extra channel, or Lock. Smoltcp is not designed to do so, but I have to hack this way. Extra channel or Lock are not permitted in my project essentially.
------------------ 原始邮件 ------------------
发件人: "Dario @.>;
发送时间: 2021年6月10日(星期四) 上午6:07
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [smoltcp-rs/smoltcp] use _old_length as isize - size as isize to avoid subtract with overflow (#487)
old_length >= size should always be true at that point.
If there's some edge case that is leading to that not being true, the root cause should be fixed instead of "fixing" it by allowing the overflow here.
If it's happening because you're using unsafe to concurrently call TcpSocket methods from multiple threads, you should fix your code. You may never ever have two &muts to the same thing concurrently. If you're doing that, the overflow here is the least of your problems. The TcpSocket internal state will get arbitrarily corrupted. You will have more crashes, you will have data corruption.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

If you're doing that, the overflow here is the least of your problems. The TcpSocket internal state will get arbitrarily corrupted. You will have more crashes, you will have data corruption.

Now I realized, reading tcp's receive buffer from another thread will cause issues with specific tcp endpoints.
My implementation's will cause ack numbers to not increment sometime, and thus cause the spurious duplicate acks and retransmittions. Take Binance's servers for example, they disabled fast retransmittion on duplicate acks. They have a retransmittion interval of 7 seconds, which caused serious thoughput-wise problems for me.


CTRL + L command not working as desired.

Usually  CTRL + L command clears the screen but leaves the input to the current prompt intact.
Here, CTRL + L command clears screen as well as the current prompt.

pull request #63 has the fix for the mentioned issue.

The pull request has been merged. Hence Closing the issue.


[stats] Optimize histogram system

Fix some bugs in codegen, allow the exponent trick to extend repeatedly (though we're not using it for current stats), and hard code the binary search into the bucket find function - tackling this because the current code, whilst correct, is causing a massive number of binary searches in prod that I'd like to eliminate post-haste.

(this brings the maximum number of branches per histogram increment down from OMG to 2 for our current cases)


Nominate Nicolas El Hayek as Voting Member

I would like to nominate @n-elhk to become a MapLibre Voting Member.
Motivation
Nicolas contributed to the Angular bindings https://github.com/maplibre/ngx-maplibre-gl
Checklist

[x] The nominee contributed in a non-trivial way or donated funds to the MapLibre Organization.
[x] This PR updates VOTING_MEMBERS.md with the GitHub handle and current employer (when applicable) of the nominee.
[ ] The nominee has approved the pull request to indicate they want to be a Voting Member of MapLibre.
[x] The nominee has shared their full name and contact e-mail with this form.
[ ] At the voting deadline[^1], more Voting Members have approved this pull request than disapproved this pull request.

More details on the process of nominating Voting Members can be found here.
[^1]: Thursday, Aug 22nd, 2024 at 17:00 CEST

@n-elhk, congratulations on being nominated to become a MapLibre Voting Member. As Voting Member you can elect the Governing Board, more on the election see here.
To accept the nomination please do the following two steps until Thursday, Aug 22nd, 2024:

Approve this Pull Request
Share your email and contact details with us with this online form

Thanks for sending the form with your contact details @n-elhk. Just to confirm, can you press "approve" on this pull request? Thanks!


feat(collectionRepeat): No redraw if the list has been appended to

When creating an infinite list using collection repeat the list is redrawn whenever it is appended to. This is normally OK, except when you have any form of animation happening on the list. This PR adds in an attribute called collection-redraw which takes an expression so you can control if you want you list to redraw when it's edited. This way we can disable redraw when we know that our lists are only going to be appended to.
Thoughts.

Collection repeat has been heavily modified since this was submitted, and I don't believe this is still necessary. Feel free to reopen if I'm mistaken.

Yea should have shut it myself. Cheers


Added Ahmed Amin to Contributors.md

Thanks for the chance !

Hi  @AhmedRedaAmin, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Loading sequence not ok, App shown before icons and images are loaded

Closed with https://github.com/scriptPilot/app-framework/pull/555


Add support for throwing in async handlers.

Adds support for throwing in async handlers without an unhandledPromiseRejectionError warning.
Tested on 8.10.x and made so tests still pass on 0.10.x.
closes #3696

Oops, looks like a spoke too soon in your issue. Didn't notice you already opened a PR at first. I don't know why you would both make an issue and then immediately make a PR without waiting to hear back :) in any case closing this PR, which you can read about why here: https://github.com/expressjs/express/issues/3696#issuecomment-406379621

@dougwilson Sorry. I've often raised issues on things (in other projects) in the past, just to be told 'raise a PR' so I've got in the habit of raising a PR by default.
Apologies.

It's no problem at all. There really is no general right answer. You're always going to end up in a project saying something different.
Myself, I don't mind opening an issue or just going straight for the pull request. The main downside to doing both at the exact same time is you may end up with two conversations separated from each other (one set of users chatting on the issue and another set chatting on the pull request). Other than that it's harmless.
I just happened to be at the computer when you opened the issue and so began typing up a response before you made your PR and then as soon as I posted saw the PR.


Calibration functions are no longer included as part of this library

Calibration functions are no longer included as part of this library.
Originally posted by @flybrianfly in https://github.com/bolderflight/mpu9250-arduino/issues/78#issuecomment-778863376
So what are the alternatives for calibration?

I would collect accelerometer and magnetometer data and use an offline tool, such as Octave, to estimate the bias and scale factors. Accelerometer and magnetometer calibration likely only needs to be performed once. For the gyro, I would collect a few seconds of data and compute the mean (i.e. the sensor bias). Gyro data is highly temperature dependent and likely does need to be performed each time the sensor is used.
Our issue with including calibration in the lib is:

It added complexity to our library, when we would like to focus on simply interfacing with the sensor. Also considering that calibration will need to be applied to every IMU, it didn't make sense to recreate that for each IMU library we develop.
The calibration process was confusing to our users, resulting in a lot of issues that were simply due to running the calibration processes incorrectly.
A generic arduino library has to support a wide range of devices, from the Arduino Uno to a Teensy 4.1. For the magnetometer calibration, I would prefer to fit the data to a sphere using a least-squares fit, but that seemed outside of what we could code for an Uno. Ultimately, the best tools for the job are offline packages, especially since this process doesn't need to be performed often.


@jdalton

TL;DR;
I was rejected by Google, Mozilla, and Twitter before getting hired by Microsoft. No ragrets.
I was rejected by Google and Mozilla in 2011 and then by Twitter in 2012. All were on-site interviews and everyone involved was super friendly. The Google interview was a mixup. They somehow thought I was in for a CSS/HTML design position. I got to see the Google campus and meet Hedger Wang, very old school cool, so it was awesome! The Mozilla interview fell through because I wasn't open to relocation, although I'm not 100% sure on that.
In 2012, post Lodash, I interviewed with Facebook, Twitter, & Microsoft. I was rejected by Twitter because I was too into JavaScript. I think they were looking for someone willing to juggle a few different languages.
All in all I'm really happy with how things turned out. I've gotten to help Chakra become one of fastest JS engines out there, improve JS at its core through the TC39, foster open source at Microsoft, contribute to many JS libraries/frameworks, and improve the web :metal:!

:+1:

I was rejected by Twitter because I was too into JavaScript.

I got a similar response from a Python company because I was too involved with Python :)

Thanks for sharing your story! Huge fan of Lodash and Chakra :) :rocket:


Fusion Tables uploads not correctly escaped

A cell value containing the string "P\Invoke" causes an error, apparently because the \ not getting correctly escaped.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/102581-fusion-tables-uploads-not-correctly-escaped?utm_campaign=plugin&utm_content=tracker%2F32795&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32795&utm_medium=issues&utm_source=github).

can't reproduced under current dev master. The "P\Invoke" was properly exported to Fusion table.  I suspect it's already fixed by Google.
We can close it.


Refactor SAPBW source

Check if _apply_user_mapping() is needed and if possible replace it with df.rename(columns=mapping_dict).
api_connection() should be refactored into to_records() or just included as part of to_df()

remove  mapping_dict from to_df()

Seems like this _apply_mapping is actually doing 2 things: first it filters a dataframe, and then renames the columns. Eg. if we have a filter + mapping dict like this: {"my_col": "my_new_col_name"} and a df with 2 columns, "my_col" and "my_other_col", after applying this function, we'd get a df with 1 column, "my_new_col_name".
So I guess this function is confusing for 3 reasons:

it does 2 things
the naming is misleading, as it only mentions one of the two things it's doing
the docstring doesn't explain what this func is doing, ony uses a generic term "applies mapping"


drivers: entropy: add get_entropy_isr() for CC13x2/CC26x2

A non-blocking, isr-safe version of get_entropy() is necessary in order
to be called during boot time before POST_KERNEL initialization.
Otherwise a crash is seen as the existing get_entropy() implementation
uses k_sem and relies on interrupts.
Fixes #18629
Signed-off-by: Vincent Wan<EMAIL_ADDRESS>

Rebased onto master.

@bwitherspoon would you be able to take a look?


The same HTTPServerRequest object is being used for multiple consecutive requests

Have you tried adding this line to any Router.get method
Log.info(request.headers["Connection"]!)

and then repeatedly refreshing the page? I'll tell you what you get:
keep-alive
keep-alive, keep-alive
keep-alive, keep-alive, keep-alive
keep-alive, keep-alive, keep-alive, keep-alive
keep-alive, keep-alive, keep-alive, keep-alive, keep-alive

Those are strings, by the way. If you wanted to test for Connection: keep-alive, it would only work on the very first try.
This also applies to every header not in the list on line 317 of HTTPIncomingMessage.swift. In other words, it also works for Accept, Cache-Control and most worryingly, Cookie. This means that request.cookies does not work at all for multiple requests on the same connection, if there is only a single cookie. If there are multiple cookies, it will work, presumably because the cookies parser just overwrites the previous values
router.get("/") {
    request, response, next in

    Log.info(request.headers["Cookie"] ?? "nil")
    Log.info(request.cookies.debugDescription)

    if let c = request.cookies["test"] {
        response.send("cookie value \(c.value)")
        let newValue = (Int(c.value) ?? 0) + 1
        response.cookies["test"] = HTTPCookie(properties: [.path: "/", .name: "test", .domain: request.hostname, .value: String(newValue), .expires: Date(timeIntervalSinceNow:60 * 60 * 24)])
    } else {
        response.send("no cookie")
        response.cookies["test"] = HTTPCookie(properties: [.path: "/", .name: "test", .domain: request.hostname, .value: "0", .expires: Date(timeIntervalSinceNow:60 * 60 * 24)])
        // uncomment this next line to unbreak cookies
        // response.cookies["garbage"] = HTTPCookie(properties: [.path: "/", .name: "nothing", .domain: request.hostname, .value: "0", .expires: Date(timeIntervalSinceNow:60 * 60 * 24)])
    }

    next()
}

The result of this in the browser is "no cookie", "cookie value 0", "no cookie", "no cookie", "no cookie".
In the logs, it looks like:
nil
[:]
test=0
["test": <NSHTTPCookie version:0 name:"test" value:"0" expiresDate:(null) created:2016-08-03 05:51:16 +0000 sessionOnly:TRUE domain:"" path:"/" isSecure:FALSE>]
test=0, test=1
[:]
test=0, test=1, test=0
[:]
test=0, test=1, test=0, test=0
[:]
test=0, test=1, test=0, test=0, test=0
[:]

This is a problem for any code that parses header values. The header values are being concatenated not with headers in the same request, but with headers from previous requests. Look at the end of that log: you have multiple values of the same header in the same line.
At the moment I'm fixing this by adding headers.removeAll() to line 126 of HTTPIncomingMessage.parse(_) but to be honest I don't actually know if that's going to cause problems somewhere else. And I don't know what else is being kept around in HTTPServerRequest that shouldn't be.
My gut feeling is that Keep-Alive shouldn't reuse the same HTTPServerRequest unless it's part of the same request flow; that is, if the response was a 100-Continue or similar. There should be a mechanism to reuse connections without reusing HTTPServerRequest objects.

Thank you very much for finding and describing this issue as well as you did.
I am actively working on the fix and should have one shortly.


Provisioning of UEFI machines not possible

/kind bug
What steps did you take and what happened:
When provisioning a hetzner bare meta host with UEFI enabled, the host ist stuck in "image-installing"
The installimage.sh in the rescue errors out because the LINE
PART /boot/efi esp 265M (or something like that)
is missing.
ERROR: ESP missing or multiple ESP found
What did you expect to happen:
I expect this to be added automatically on detecting an efi-enabled system
Anything else you would like to add:
Line in autoconfig 'PART /boot/efi esp 265M' is enough.
It should be possible to also add this in HetznerBareMetalMachineTemplate, but its a hassle to work with labels to support legacy and UEFI
Environment:

cluster-api-provider-hetzner version: v1.0.0-beta.27
Kubernetes version: v1.28.4
OS (e.g. from /etc/os-release): Debian GNU/Linux 12 (bookworm) Rescue

Hey @KoffeinKaio
Hetzner UEFI Boot as of now is in beta and not supported by the project at the moment.
Ref: https://docs.hetzner.com/robot/dedicated-server/operating-systems/uefi/#introduction
To solve the issue please contact Hetzner support, so that they change the machine to legacy boot.

As it seems (at least as our server guy said) newer Server Versions, for example AX52 only support UEFI.

With all new dedicated root server models, Hetzner Online will support UEFI boot natively and discontinue legacy boot (CSM) support.

Ill try to contact hetzner to get a clarification

Ill try to contact hetzner to get a clarification

Answer of hetzner:
"wir bedauern, aber dies ist bei den gemieteten AX52 und auch anderen Servermodellen bereits nicht mehr möglich. Die Server sind UEFI "only" und bieten hier keine Änderungsmöglichkeit."
English:
"We regret to inform you that this is no longer possible with the rented AX52 and other server models. The servers are UEFI 'only' and do not offer any option to change this."

I confirm that the merged PR makes it possible to run the Syself capi provider on Hetzner bare-metal servers with UEFI.
If the provisioning fails to enter the rescue system to install the node image, then the boot order could be wrong.
Then the old OS on the disk gets booted and not the rescue system.
In this case either contact the Hetzner support, or use efibootmgr if you have access to the machine via ssh.

@KoffeinKaio beta32 was released and we sucessfully provisioned some uefi machines (with mdraid and without). Please try it, and provide feedback if it worked for you.


Remedy candidate answer review misbehaviour

Describe the bug
In a situation in which a candidate has skipped questions, when they click next from the final question, they should be taken to a review page where they can see which questions they have answered and which not. When user clicks on an unanswered question and submits an answer/clicks next, the navigation should take them to the next unanswered question, but instead it just takes them to the next question chronologically and they have to navigate through all questions to reach any they have not answered.
An additional mock is planned for 21/11, which gives us time to fix and release to meet that deadline.
Expected behaviour
Candidates should be able to skip through all unanswered questions at the review stage.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Please add your planning poker estimate with Zenhub @tomlovesgithub

@tomlovesgithub You can view the correct behaviour on the practice QT on the website by skipping some questions and then getting to the review after Q5.


PQ Support

This app is sick and has quickly replaced NParse for me, any chance we could get support for Project Quarm as well? It doesn't seem to detect the eqgame.exe for the TAKP emu client.
You da best!

I have to make a seperate version its not hard and something I will do here shortly. Let me see if i can knock it out this weekend

Im pushing the release now to support Quarm. Still testing.
It will be a separate executable

PQ SUPPORT DONE.
I left in the MOB window, which pulls from project1999 wiki for now. Not sure what to do with it. Everything else should work as expected.


How do we get shrunken test cases?

First of all, great project, I love it! It's super useful. Thanks for sharing it with the world.
I notice that FuzzTest has a concept of shrinking (as many property-based testing libraries and fuzzing libraries do). How do I use this? I've created a fuzztest. I've created Domains for my code under test, and fuzztest has found bugs in my code, but it won't shrink the failing stimulus. It's obviously harder to root cause my errors when fuzztest found the error using a complex stimulus, so how do I get fuzztest to shrink when an error is found?

There is a minimizer script in tools directory. In short you have to deal with some undocumented environment variables...
I have a simpler script here: https://github.com/elalish/manifold/blob/ef4df32ba8321d537c92e8a9e4fce7a788f58cbb/minimizer.sh, in case it is useful to you.


Some functions not working with ionic 2

I want to use this plugin in my ionic 2 app. But following methods are not working in ionic 2.

cordova.plugins.backgroundMode.moveToBackground();
cordova.plugins.backgroundMode.moveToForeground();
cordova.plugins.backgroundMode.overrideBackButton();
cordova.plugins.backgroundMode.excludeFromTaskList();
cordova.plugins.backgroundMode.disableWebViewOptimizations();

@rupalpatel0008 The Ionic code base isn't maintained by myself.

I have the same problem in Ionic where could we get help? Please.


Specify repositories to save a package

Hi folks
I've 3 different repositories  local, stable, test
when i run helm package XXX  the package was saved in all repositories.
i tried with the params --save  stable, test  but it didn't worked.
How can i specify to save the package in stable repository for exemple ?
It's a question for support  i didn't find the botom to swith .
Sorry in advance if i make something wrong

AFIK, by default helm package adds the chart to the local repo.  Maybe you could provide more details on how it got saved to the different repos?
Here are some steps to add the chart to an existing repo on <remote_host>:

$ wget http://<remote_host>/charts/index.yaml
$ ./helm repo index --merge index.yaml --url http://<remote_host>/charts/ ./
Copy both the updated index.yaml and the new chart package files from your local host to the matching directory on the remote host.

Closing due to inactivity. Please open a new ticket against Helm 3 if this issue persists. Thanks!


stack.yamls and sync with mvoidex origin repo

Sorry, I seem to have been out of sync with your repo on the last pull request. Now I'm in sync and what I wanted pulled is actually here.

Ok, thanks


Fix description in project file

Probably copy pasted from another project

Good catch, thanks for the PR!
Not sure how that got pasted into there haha.


[docs] Avoiding reference to Guava types

@Naros, quick one for you :)

Applied to main (=2.0) and branch 1.9.


Android Basics: Shared ViewModel

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-shared-viewmodel?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-4%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-shared-viewmodel#2
In which task and step of the codelab can this issue be found?
-Shared ViewModel Across Model
Describe the problem
I am not able to change the title of the app bar

Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version: 4.2.1
API version of the emulator: 30_x86
Additional information
Include screenshots if they would be useful in clarifying the problem.

I experienced same problem and the difference of codelab is onCreate() method in MainActivity...and I found the problem and fixed it.
There are two onCreate(), and I overrided another onCreate().
Override this.
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
}
not this.
override fun onCreate(savedInstanceState: Bundle?, persistentState: PersistableBundle?) {
super.onCreate(savedInstanceState, persistentState)
}

I experienced same problem and the difference of codelab is onCreate() method in MainActivity...and I found the problem and fixed it.
There are two onCreate(), and I overrided another onCreate().
Override this.
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
}
not this.
override fun onCreate(savedInstanceState: Bundle?, persistentState: PersistableBundle?) {
super.onCreate(savedInstanceState, persistentState)
}

@hong-studio
I'm curious about this, why are there two onCreate()? Are they different functions?

nstanceState: Bundle?) {
super.onCreate(savedInstanceState)
}

I also noticed that when using the wrong onCreate(), i.e with 2 param, the up button won't show up. Can someone explain this to me?


scipy.signal.lsim2 returns a wrong result for some transfer functions

Description
The function lsim2 return wrong results for certain transfer functions. I notice that just by slightly changing the parameters of the transfer function the result returned was correct again. This behaviour happened around 4 out of 100 times  when I has evaluating random variations of a particular system.
I have done some experiments changing the tolerance of the ode system under lsim2 but I did not succeed in having consistent results. I observed also that the function lsim do not return the wrong result at least for the system I was evaluating.
Software

scipy 0.16.0
anaconda 2.3.0
python 2.710
x86x64( on darwin, but I have observed similar behaviour in on a windows machine)

Code example
The following code shows two different transfer functions that are identical to the 8th more significant bit, one of them returns the wrong result, H, and the other one, H2, does not.
import scipy.signal.ltisys as lti
from scipy.signal import sawtooth
import matplotlib.pyplot as plt
import numpy as np

Tchirp = 35e-6
ts = 9.50013571622e-10
t = np.arange(0, 5*Tchirp, ts)
#t = np.linspace(0, 1.9*Tchirp, num=round(2*Tchirp/1e-9))
BW = 500e6
fmcw = 500e6*sawtooth(2*np.pi*t/Tchirp)
Navg =<PHONE_NUMBER>6666669

H = lti.lti(
    [ 3.35856979991219650e+23,
     2.200856866394299333e+29],
    [
    1.0000000000000000000e+00,
    1.0952512602246981859e+08,
    8.3901936551890375000e+14,
    2.0936539012439662920e+21,
    1.3719627219081343178e+27
    ])

H2 = lti.lti(
    [ 3.3585698e+23,
     2.20085687e+29],
    [
    1.00000000e+00,
    1.09525126e+08,
    8.39019366e+14,
    2.09365390e+21,
    1.37196272e+27
    ])
t, yH_lsim2, xout = lti.lsim2(H, U=fmcw/Navg, T=t)
t, yH_lsim, xout = lti.lsim(H, U=fmcw/Navg, T=t)
t, yH2_lsim2, xout = lti.lsim2(H2, U=fmcw/Navg, T=t)

The result of the these three calls to the functions is shown in the added plot. The result called H2 lsmi2 is obviously wrong.

Annex: Plotting
plt.plot(t/1e-6, fmcw/1e6, label = 'ideal')
plt.plot(t/1e-6, yH_lsim2/1e6, label = 'H lsim2')
plt.plot(t/1e-6, yH_lsim/1e6, label = 'H sim')
plt.plot(t/1e-6, yH2_lsim2/1e6, label = 'H2 lsmi2')
plt.legend(loc='center left', bbox_to_anchor=(1.0, 0.5))
plt.show()

@jfosorio thanks for the clear bug report. lsim was rewritten for 0.16.0 and is now more correct and much faster than lsim2. The longer term plan is to get rid of lsim2 completely (and impulse2 / step2), but in the meantime we could alias the *2 versions to the better versions.
@jfosorio @WarrenWeckesser do you see any issues with that?

FWIW: Don't forget that lsim2 is documented to be a wrapper of scipy.integrate.odeint.  While odeint is pretty robust, the underlying solver LSODA isn't really designed to handle such a discontinuous input.  The adaptive step size algorithm of LSODA is probably being "fooled" by the initial linear ramp, and then goes off the rails at the first discontinuity.
You can workaround this by passing additional keyword arguments to lsim2 that are passed on to odeint.  In this case, tightening up the absolute error tolerance fixes the computation:
t, yH2_lsim2, xout = lti.lsim2(H2, U=fmcw/Navg, T=t, atol=1e-9)

As I've said elsewhere, getting rid of lsim2, impulse2 and step2 is a good idea; the hard part is making versions of these that "just work" with as wide a variety of inputs as possible.

Thanks for the explanation. I wrote the issue as a way to keep things documented. @WarrenWeckesser the error happens just before the discontinuity, that was the reason I find it intriguingly .

Visually there seems to be less error which matches @rgommers Oct 9 comment.

I'm closing this as fixed given less visual error and @rgommers statement that lsim was improved (without searching for a PR).

Not only the ode solver but LTI object needs scaling here. Easiest ist to write the dynamics in microseconds such that coefficients get back regular order of magnitude.


run book tests and fix book examples

run mdbook tests so we ensure the examples actually compile
There are several examples that were broken and did not actually work (thus making it hard to learn to use async-graphql)

awesome, thank you so much for making this! 👏


Fix contrastive loss with temperature test

For some reason when we run pytest on a subdirectory of tests/ PyTorch is unable to find GPUs if they are present. But when we run just pytest tests/ PyTorch does see the GPU.
This means that in the latter case the contrastive_loss_with_temperature test fails due to tensors on different devices (previously only model params were moved to the current device but the embeddings were not). But random initialization on GPU is different than on CPU so the test will give different results across different types of hardware.
Since the contrastive loss distributed tests are intended to only run on GPU, we leave those as is. But for the remaining test cases we explicitly move everything to CPU so we can ensure consistent results.

@kartikayk no we haven't. But this only manifests locally and not in our CI (since we don't have GPUs for our CI runs currently). So it may be outside their purview (but still it'd be interesting to understand why this happens)


pyspark errors on training

I'm using xgboost4j-0.80.jar, xgboost4j-spark-0.80.jar, and the link to xgboost provided in this post.
I can load and define a model just fine:
spark.sparkContext.addPyFile("sparkxgb.zip")
from sparkxgb import XGBoostClassifier

model=XGBoostClassifier(
    featuresCol="features",
    labelCol="origin_idx",
    predictionCol="prediction"
)

When I try to train the model I receive the following error:
java.lang.NoSuchMethodError: org.codehaus.jackson.map.ObjectMapper.readTree(Ljava/net/URL;)Lorg/codehaus/jackson/JsonNode
I'm on Spark 2.3.
Thanks!

Double check if you are using correct Scala version (2.11). Also, print out the dependency tree (run mvn dependency:tree -Dverbose -Dincludes=commons-collections) and see if there's any conflicting package versions

I met an exactly same issue, I guess it is because I'm using SPARK2-2.3.0.cloudera2, while Upstream XGBoost is not guaranteed to work with third-party distributions of Spark, such as Cloudera Spark.

Interesting!  I'm on cloudera as well.  The fact that its complaining about an old version of jackson makes me think that the problem is fixable.  I just haven't found the solution yet.

No official support on anything other than apache spark, no official support on pyspark (coming in 1.0 release)
Why there is jackson issue? Jackson itself brings some breaking changes, leading to spark doesn’t have cross-version binary compatibility, then when we compile xgboost with spark, it also suffers from that...cloudera is very likely to mask the change of jackson cross their own spark version and therefore becomes binary inconsistent with apache spark which is what xgb compiled against...so...yeah, hard to resolve...

Tested 0.82 version in local mode Apache Spark 2.3.3, not see Jackson readTree issue anymore.


[Backport 2.17] [RW Separation] Add polling segment replication for search replicas (#15627)

manual backport of https://github.com/opensearch-project/OpenSearch/pull/15627 to 2.17

gc didn't report back but it passed https://build.ci.opensearch.org/job/gradle-check/47091/


Add run-book notes to cabot.

Summary: Add runbook field so that cabot checks have a run book.  This seems to work, but there may be some fit and finish to make it look nicer. Mainly it would be good to expand the size of the input box.
Test Plan: Tested locally. UT's pass, save for MYSQL, which also fails on master.
Reviewers: elainearbaugh
Subscribers: #consumer
JIRA Issues: INFRA-4358
Differential Revision: https://phabricator.team.affirm.com/D6640

trigger build


Fix French Translation

Hi,
3 months ago, i've made some changes and correction in the French translation but it still remain the error.
Changes has been made trought transifex
Not in the hurry but did you plan to make a future update ?
Thx for this awesome GUI ;)

@CorentinDy thank you for making these changes.
The Transifex updates are only refreshed when a new version of the application is released.  i.e. when 0.17.0 is released, you will see any updates that have been made to the translations.
I am going to go ahead and close this issue out, but feel free to ask any other questions.


Decrease LinkCacheSize default to 4000

Changes default link cache size for desktop.

I'm merging over this TestTeamRemoveAfterReset continued issue in CI.


Use gradle platform to provide a BOM

Hi,
This change modifies the build process to produce a software bill of materials (BOM) as an additional artefact. We need to consume this artefact in downstream projects to simplify dependency management.
To do this, I switched to using newer constructs in Gradle, in particular the maven plugin has been replaced with the maven-publish plugin with consequent changes to the signing configuration.
Overall the configuration complexity has been reduced very slightly.
All tests pass and the publishToMavenLocal task looks correct. However I can't test the signing task, which might need its conditional Required() check to work
Thanks!

The changes fail the build and are very extensive. I'm not tempted to accept this. Maybe @tmontgomery has a view.  Also a number of plugins have been removed which others require.

I'll take a look at the CI output, I only ran build / test locally thus far.
Wasn't expecting anyone to take this without further discussion but please allow me to fix the build process first.
@mjpt777  Is there a particular plugin's removal you're concerned about?

Why are you removing plugins?

@mjpt777 Switching from older maven plugin to maven-publish plugin to simplify the publication part. CI failed because I neglected to update the default build task (fixed)

I'm pretty sure this will fail when tried to use to push artifacts for publishing. Or if not, likely require quite a few fixes to make it pass cleanly. Unless something has changed, we can't use maven-publish.
Is there a reason for some of these changes that is required for the BOM? Or just easier? If easier, would be better not to change them at the same time as other things. So, would suggest finding the minimum needed for the BOM that touches as little as possible. Can be cleaned up separately, if needed.

@tmontgomery I will rework this to use maven plugin as before, thanks, I wasn't aware there would be an issue publishing to maven central with the newer plugin, its a shame though as it does make the configuration and signing syntax significantly simpler.

@tmontgomery: I've reverted back to old maven plugin and rebased. However at present I cannot find a way to link the old legacy publication method. I've got as far as I can get without switching to the newer publication mechanism. At this point there is nothing further I can do unless you or another member of your team can link the javaPlatform plugin to the old legacy publication mechanism

Closing due to lack of progress.


“Package powershell-6.0.0_alpha.17-1.el7.centos.x86_64.rpm is not signed" when using MS Repo

Configure MS Repo according to https://technet.microsoft.com/en-us/windows-server-docs/compute/Linux-Package-Repository-for-Microsoft-Software
On CentOS:
sudo rpm -Uvh http://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm

Then run yum install powershell
You'll get below “Package powershell-6.0.0_alpha.17-1.el7.centos.x86_64.rpm is not signed" error:
root@******  # yum install powershell Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile
* base: ftp.osuosl.org
* epel: mirror.sfo12.us.leaseweb.net
* extras: lug.mtu.edu
* ius: mirror.team-cymru.org
* updates: mirror.raystedman.net
Resolving Dependencies
--> Running transaction check
---> Package powershell.x86_64 0:6.0.0_alpha.17-1.el7.centos will be
---> installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package   Arch   Version                     Repository                   Size
================================================================================
Installing:
powershell
           x86_64 6.0.0_alpha.17-1.el7.centos packages-microsoft-com-prod  44 M

Transaction Summary
================================================================================
Install  1 Package

Total size: 44 M
Installed size: 44 M
Is this ok [y/d/N]: y
Downloading packages:

Package powershell-6.0.0_alpha.17-1.el7.centos.x86_64.rpm is not signed

looks like you tried this when I was in the process of refreshing the package on packages.microsoft.com.
The package is fine now.

rpm -qpi powershell-6.0.0_alpha.17-1.el7.centos.x86_64.rpm  Name        : powershell
Version     : 6.0.0_alpha.17
Release     : 1.el7.centos
Architecture: x86_64
Install Date: (not installed)
Group       : shells
Size        : 143031860
License     : MIT License
Signature   : RSA/SHA256, Thu 09 Mar 2017 04:09:53 PM EST, Key ID eb3e94adbe1229cf
Source RPM  : powershell-6.0.0_alpha.17-1.el7.centos.src.rpm
Build Date  : Thu 09 Mar 2017 03:25:48 PM EST
Build Host  : 729de4de67fe
Relocations : /
Packager    : PowerShell Team<EMAIL_ADDRESS>Vendor      : Microsoft Corporation
URL         : https://microsoft.com/powershell
Summary     : PowerShell is an automation and configuration management platform.
Description :
PowerShell is an automation and configuration management platform.
It consists of a cross-platform command-line shell and associated scripting language.


Added an example using FastAPI

Added an example showing how FastAPI can be used to view settings.

Hello @yusufk! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file example/fastapi_with_ini/app.py:

Line 15:1: E302 expected 2 blank lines, found 1
Line 19:1: E302 expected 2 blank lines, found 1
Line 23:1: E305 expected 2 blank lines after class or function definition, found 1


M3-2109 M3-2110 Move Images into Redux

Description
The start of M3-2109. Adding the basics of the reducer and state. Additionally requests images on app initialization.
Note to Reviewers

Load application.
Verify a getAll request was sent for images.
Verify Redux store now contains images at state.__resources.images.

Coverage increased (+0.04%) to 33.294% when pulling aed696792f5e5ec364aab7bf94bd36d7ed3a8fdb on rjstires:M3-2109 into 02b4def33839dda5d661f7668e470d28b9d52879 on linode:feature/images-in-state.


Let's add Dead Link Checker to CI/CD

Should we add Dead Link Checker to QXlsx CI/CD? For example this code contains dead link... For example we can use this checker.
My log
a@Asya:~/QXlsx$ lychee QXlsx/source/* -m 0
  37/37 ━━━━━━━━━━━━━━━━━━━━ Finished extracting links                                                                                Issues found in 4 inputs. Find details below.

[QXlsx/source/xlsxdocpropscore.cpp]:
✗ [ERR] http://www.w3.org/2001/XMLSchema-instance | Failed: Too many redirects: error following redirect for url (http://www.w3.org/2001/XMLSchema-instance)
✗ [ERR] http://purl.org/dc/elements/1.1/ | Failed: Too many redirects: error following redirect for url (http://purl.org/dc/elements/1.1/)
✗ [ERR] http://purl.org/dc/dcmitype/ | Failed: Too many redirects: error following redirect for url (http://purl.org/dc/dcmitype/)
✗ [ERR] http://purl.org/dc/terms/ | Failed: Too many redirects: error following redirect for url (http://purl.org/dc/terms/)

[QXlsx/source/xlsxworksheet.cpp]:
✗ [ERR] http://a.com/aaa.html#aaaaa | Failed: Network error: error sending request for url (http://a.com/aaa.html#aaaaa)

[QXlsx/source/xlsxformat.cpp]:
✗ [ERR] http://office.microsoft.com/en-001/excel-help/create-a-custom-number-format-HP010342372.aspx | Failed: Too many redirects: error following redirect for url (http://office.microsoft.com/en-001/excel-help/create-a-custom-number-format-HP010342372.aspx)

[QXlsx/source/xlsxdocument.cpp]:
✗ [ERR] http://en.wikipedia.org/wiki/Open_Packaging_Conventions | Failed: Too many redirects: error following redirect for url (http://en.wikipedia.org/wiki/Open_Packaging_Conventions)

🔍 37 Total (in 0s) ✅ 5 OK 🚫 7 Errors 💤 25 Excluded

You report contains some false positive errors
http://www.w3.org/2001/XMLSchema-instance
http://a.com/aaa.html#aaaaa
http://en.wikipedia.org/wiki/Open_Packaging_Conventions
3 of 7 errors are false positive. Maybe it's a good idea but not in current implementation


release-0.6: Release manifest templates

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Provide jinja2 tempaltes for manifests

@rthallisey anything else needed?

@fabiand also need https://github.com/kubevirt/kubevirt/pull/1210

Darn. Wroing target branch. Reopening a new PR


Issue plotting band structure.

Hi, I have been struggling when trying to plot the projected per element band structure for systems with more than 3 elements. It gives me the error that the default mode 'RGB' only supports up to 3 elements. Is there a way to plot the projected band structure for more than 3 elements?
On the other hand, I was wondering if it's possible to make the vertical lines in the k-points dotted instead of solid?
Thank you so much.

You can use "stacked" mode to plot more than 3 projections. Search for "stacked" in the documentation: https://smtg-ucl.github.io/sumo/sumo-bandplot.html#projected-band-structures
You can customise sumo plots using a matplotlib style sheet. See the docs here: https://smtg-ucl.github.io/sumo/customising-plots.html and the matplotlib docs here: https://matplotlib.org/tutorials/introductory/customizing.html
To control the grid line style you should make a file called mystyle.mplstyle with the following contents:
grid.linestyle: :  # dotted line style, other options are dashed "--", dash dotted, "-." or solid "-".

And then select that style when using bandplot:
sumo-bandplot --style mystyle.mplstyle

Please note, I just pushed a new version (v2.1.1) that allows customising the vertical lines, so you should make sure to update sumo before plotting.


hideRightPanel configuration does not have any effect

I am trying out redocly via the cli. I was testing out some of the configurations and noticed that the hideRightPanel option does not seem to have any effect.
To reproduce: create a redocly.yaml:
theme:
  openapi:
    disableSearch: true
    hideRightPanel: true

Then run redocly build-docs openapi.yaml and view the resulting html page
I was expecting the entire right panel to disappear but it did not. The configuration appears to be correct as the disableSearch works, and there are no errors or warnings in the terminal.
I'm using redocly version 1.18.1 and node v20.10.0.

Redocly CLI correctly resolves the config. It looks like that's related to Redoc itself. Transferring there.


please add support for 1.3.~ angular

Does the lib support 1.3.~ of angular and angular-mocks?

Mox was built for a large project that uses Angular 1.2 and Jasmine 1.x. So it is extensively tested in these versions.
It is lightly built on top of angular-mocks.
Later Jasmine 2.x and Angular 1.3 support was added, so you should be able to use Mox with your Angular 1.3 projects. However, there are as far as I know not yet any large projects in Angular 1.3 that use Mox. I will update the readme.
If you encounter any issues please create a new issue with a more detailed description and I will fix it. If you have any questions, feel free to ask them.


Check-health.sh does not work with crontab

The check-health.sh file right now does not work with crontab because it uses relative paths for util.sh,.env and docker-compose.yml files. We should update these to absolute so that its works with crontab

Note that when installing it as a systemd unit, you can set the working directory. Perhaps we can add some systemd timers for common functionalities like these and renewing the SSL certificate.

Okay thanks. I was only trying to install it as a cron job. Will try the systemd now. Thanks


Vulnerability roundup 92: postgresql-11.7: 2 advisories [8.8]

search, files

[ ] CVE-2020-14349 CVSSv3=8.8 (nixos-20.03)
[ ] CVE-2020-14350 CVSSv3=7.3 (nixos-20.03)

Scanned versions: nixos-20.03: 925ae0dee63.
Cc @danbst
Cc @globin
Cc @ocharles
Cc @thoughtpolice

20.03 is Frozen and EOL.
As such, issue is closed.


Environment-variable does not change

First of all, thanks for your work with this, it's really great :slightly_smiling_face:
I have a question about environments, which is not really clear to me.
This is my PHP-file:
<?php

var_dump(getenv('foo'));

phpinfo();

I deploy it with now.json:
{
  "version": 2,
  "name": "test",
  "builds": [
    {
      "src": "index.php",
      "use": "now-php"
    }
  ],
  "env": {
    "foo": "foo"
  }
}

Thats works as expected and I see string foo dumped with getenv().
But if I change env foo in now.json to something else and redeploy it, the value of foo is still foo. It does not change.
Mabe it's a general problem with now...

Hi @andreasroman.
I must discuss it with ZEIT team. Looks like changes in env don't trigger new build. Could you try now -f?

Hi @andreasroman.
I must discuss it with ZEIT team. Looks like changes in env don't trigger new build. Could you try now -f?

Yes that works :100:


AWS SDK: Update Query/Scan to obey limits

[Update] Query did not obey limit because it would keep
looping as long as there were pages to read. Added count
to return once limit was reached based on scanned records.
[Update] Scan did not obey limit when in batching mode
and would have similar issue as Query. Added count to return
once limit was reached based on scanned records.

Open issue https://github.com/Dynamoid/Dynamoid/issues/85

Coverage remained the same at 96.503% when pulling 428bdf5b23ec8d05aadd790ec88aa1064dfe7eaa on richardhsu:richardhsu/fix-query-scan-limits into 8b51b568ff4732d7595a3c971eb3c71d13ca1913 on Dynamoid:master.

Coverage remained the same at 96.503% when pulling 428bdf5b23ec8d05aadd790ec88aa1064dfe7eaa on richardhsu:richardhsu/fix-query-scan-limits into 8b51b568ff4732d7595a3c971eb3c71d13ca1913 on Dynamoid:master.

Great!


self.RCNN_base(im_data)

hello, Why can't I find self.RCNN_base's definition in the project?

sorry i have found it's location

Hi, I cannot find it either, could you give any hint on its location?


Generate an installation guide, detailing the technologies utilized and documented within the README file.

Create a comprehensive installation guide that effectively guides users through the process of installing the software or project. Within this guide, clear, step-by-step instructions should be provided for downloading, configuring, and setting up the software across various platforms. Additionally, it is important to document the technologies utilized in the project within the README file. These may include programming languages, frameworks, libraries, and other essential tools necessary for the operation of the software. By ensuring that these details are clearly outlined, users will have the necessary information to successfully install and utilize the software.


Add serde roundtrip test for rpc types

Feature Adding #1564

Codecov Report

Merging #1571 (84fad04) into main (b1741bd) will decrease coverage by 37.71%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #1571       +/-   ##
===========================================
- Coverage   75.15%   37.44%   -37.71%
===========================================
  Files         371      371
  Lines       43342    43426       +84
===========================================
- Hits        32572    16260    -16312
- Misses      10770    27166    +16396

Flag
Coverage Δ

integration-tests
?

unit-tests
37.44% <100.00%> (-32.24%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

lint unrelated


Unable to Parse Binding Mode=TwoWay

ListBox Items="{Binding AvailablePackages}" SelectedItem="{Binding SelectedPackage, Mode=TwoWay}" IsEnabled="{Binding EnableInterface}"
Is causing exception:
System.ArgumentException: 'expression' may not be empty.
I think its related to recent fixes on expression parsing.

This works if I use:
SelectedItem="{Binding Path=SelectedPackage, Mode=TwoWay}"

This seems to be a bug in OmniXAML where binding extensions aren't being correctly parsed when a property has a dependency on another property.

Agreed: filed a bug with OmniXaml.
https://github.com/SuperJMN/OmniXAML/issues/45


[Fix #9453] Fix an infinite loop error for Layout/FirstParameterIndentation

Fixes #9453.
This PR fixes the following infinite loop error for Layout/FirstParameterIndentation when EnforcedStyle: with_fixed_indentation is specified for Layout/ArgumentAlignment.
% cat example.rb
# frozen_string_literal: true

RSpec.describe MyController, type: :controller do
  it 'abc' do
    expect(response).to redirect_to(path(
      obj1,
      id: obj2.id
    ))
  end
end

% cat .rubocop.yml
AllCops:
NewCops: enable

Layout/ArgumentAlignment:
  EnforcedStyle: with_fixed_indentation

% bundle exec rubocop -a --only Layout/ArgumentAlignment,Layout/FirstArgumentIndentation
(snip)

Infinite loop detected in
/Users/koic/src/github.com/koic/rubocop-issues/9453/example.rb and
caused by Layout/FirstArgumentIndentation -> Layout/ArgumentAlignment
/Users/koic/src/github.com/rubocop-hq/rubocop/lib/rubocop/runner.rb:304:in
`check_for_infinite_loop'
/Users/koic/src/github.com/rubocop-hq/rubocop/lib/rubocop/runner.rb:287:in
`block in iterate_until_no_changes'

The following is the reason why an error occurs.
First, Layout/FirstArgumentIndentation will auto-correct it.
% bundle exec rubocop -a --only Layout/FirstArgumentIndentation
Inspecting 1 file
C

Offenses:

example.rb:6:7: C: [Corrected] Layout/FirstArgumentIndentation: Indent
the first argument one step more than path(.
obj1,
^^^^

1 file inspected, 1 offense detected, 1 offense corrected

% cat example.rb
# frozen_string_literal: true

RSpec.describe MyController, type: :controller do
  it 'abc' do
    expect(response).to redirect_to(path(
                                      obj1,
      id: obj2.id
    ))
  end
end

Next, Layout/ArgumentAlignment will auto-correct it.
% bundle exec rubocop -a --only Layout/ArgumentAlignment
Inspecting 1 file
C

Offenses:

example.rb:6:39: C: [Corrected] Layout/ArgumentAlignment: Use one level
of indentation for arguments following the first line of a multi-line
method call.
obj1,
^^^^

1 file inspected, 1 offense detected, 1 offense corrected

% cat example.rb
# frozen_string_literal: true

RSpec.describe MyController, type: :controller do
  it 'abc' do
    expect(response).to redirect_to(path(
      obj1,
      id: obj2.id
    ))
  end
end

An infinite loop error occurs because it is corrected to the original code.
This PR makes Layout/FirstParameterIndentation respect Layout/ArgumentAlignment when EnforcedStyle: with_fixed_indentation alternative configuration is specified for Layout/ArgumentAlignment to prevent the error.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


docs: add developers docs around creating new components and creating…

Add developers docs around creating new components and creating…

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes
/start features)

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[X] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Fixes: [ISSUE NUMBER]
What is the new behavior?

Changing the documentation about creating new components
Adding documentation on how to create a commit message

Does this introduce a breaking change?

[ ] Yes
[X] No

Other information

Thanks @carwack ! Requested some changes.


irq.h: build assert modification

The MAX_IRQ_PER_AGGREGATOR should fit into the sum of all enabled bits not just the first level anymore.

The issue title, summary, and commit message should probably be changed to reflect the code changed a bit more accurately.

The issue title, summary, and commit message should probably be changed to reflect the code changed a bit more accurately.

Done it just doesn't appear to show up on this main comments page. You can see it under commits.


Why does going from unspecified to untrusted require a restart?

I clicked don't trust and it says it needs to restart? No extensions should have been enabled at this point?

Also clicking yes didn't restart 😕

likely will just be fixed when we remove the unspecified state

The unspecified state has been removed, and transitioning from Trusted to Untrusted does not require a reload any more.

Marking as verified based on  https://github.com/microsoft/vscode/issues/121110#issuecomment-821525648


Bisect with cargo-bisect-rustc

Yet another step of the process that can be automated!

This script appears to do the job:
#!/bin/bash

if rustup run "${RUSTUP_TOOLCHAIN}" rustc /path/to/ice.rs 2>&1 | grep 'panicked'; then
  exit 1
fi
exit 0