text:
Default value for blockTag argument in provider methods

Added  default values to blockTag params in provider methods, so these methods can be called without specifying blockId.
Swapped order of arguments in getClassAt method, to align it with other Provider methods (potential breaking change)

Codecov Report
Base: 62.50% // Head: 62.40% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (d684c3f) compared to base (f282b4a).
Patch coverage: 40.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #87      +/-   ##
==========================================
- Coverage   62.50%   62.40%   -0.10%
==========================================
  Files          45       46       +1
  Lines        1176     1181       +5
  Branches       68       68
==========================================
+ Hits          735      737       +2
- Misses        422      425       +3
  Partials       19       19

Impacted Files
Coverage Δ

...kotlin/com/swmansion/starknet/provider/Provider.kt
25.00% <25.00%> (ø)

...swmansion/starknet/provider/rpc/JsonRpcProvider.kt
78.90% <100.00%> (+0.16%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: bartekryba codecov-commenter

repo: software-mansion/starknet-jvm


text:
Set up SWR development environment

To enable a seamless development and deployment process, a server infrastructure to be set up at wetransform and made accessible to all SoilWise development teams.
Consider Containerization

From our side was set up:
A Kubernetes cluster as test system including:

A Keycloak instance
A hale-connect installation including the required infrastructure and monitoring via Prometheus and Grafana

Keycloak can be used to authenticate with hale-connect, but does not yet support authentication via GitHub which is planned to be done in https://github.com/soilwise-he/development-environment-and-infrastructure/issues/2
If anyone requires credentials for working with hale-connect or Keycloak please let me know.
Is there are preferred safe way to share credentials within the project?

Hi Simon,
Thank you!
I will ask for safe sharing of credential and will let you know.
With best regards,
Kaanthan
--
Dr. Somakanthan Somalingam
Senior Project Manager
E-Mail: @.***
Web: www.wetransform.tohttp://www.wetransform.to/
Team Phone: +49 6151 6290890
wetransform GmbH
Fraunhoferstr. 5
64283 Darmstadt
Germany

From: Simon Templer @.>
Sent: Friday, June 7, 2024 18:37
To: soilwise-he/development-environment-and-infrastructure @.>
Cc: Somakanthan Somalingam @.>; Assign @.>
Subject: Re: [soilwise-he/development-environment-and-infrastructure] Set up SWR development environment (Issue #1)
From our side was set up:
A Kubernetes cluster as test system including:

A Keycloak instancehttps://id-admin.soilwise.wetransform.eu/
A hale-connect installationhttps://data.soilwise.wetransform.eu/ including the required infrastructure and monitoring via Prometheus and Grafana

Keycloak can be used to authenticate with hale-connect, but does not yet support authentication via GitHub which is planned to be done in #2https://github.com/soilwise-he/development-environment-and-infrastructure/issues/2
If anyone requires credentials for working with hale-connect or Keycloak please let me know.
Is there are preferred safe way to share credentials within the project?
—
Reply to this email directly, view it on GitHubhttps://github.com/soilwise-he/development-environment-and-infrastructure/issues/1#issuecomment-2155176548, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5X6R5OYTBJVQZPEVE6MN4TZGHOWJAVCNFSM6AAAAABGWXV77GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGE3TMNJUHA.
You are receiving this because you were assigned.Message ID: @.***>

source: gharchive/issue

authors: Somakanthan stempler

license: MIT

license_type: permissive

license_source: github-api


text:
Update MS Edge user client string

In Main.awk, the MS Edge user client is specfied as Edg. Change this to Edge.
Not sure if this was intentional or not, please ignore if so. :+1: :rocket:

Can you confirm if the latest Microsoft Edge UA string is Edg or Edge?
I don't have the Edge browser installed right now, but according to Microsoft's own documentation, it's just "Edg":
https://learn.microsoft.com/en-us/microsoft-edge/web-platform/user-agent-guidance#user-agent-strings
Also according to this stackoverflow comment: https://stackoverflow.com/questions/30591706/what-is-the-user-agent-string-name-for-microsoft-edge#comment122093306_33505753 , it was changed from Edge to Edg since 2019.

@soimort you are correct, the modern user agent is Edg. When I went to confirm this, I was looking at outdated documentation from 2017. This PR can be disregarded. :pray:

source: gharchive/pull-request

authors: naltun soimort

repo: soimort/translate-shell

license: unlicense

license_source: bigquery


text:
Add the --numeric-version option to the usage.

Fixes #337.

Released to Hackage as 0.31.1.

authors: philderbeast sol

repo: sol/hpack

license: mit


text:
Introduce ebpf::RETURN instruction

This PR introduces the return instruction in the 0x9d opcode. (See https://github.com/solana-foundation/solana-improvement-documents/pull/178)
PS: The SIMD needs to be amended with the instruction name, which changed from exit to return.

Superseded by #609.

repo: solana-labs/rbpf


text:
JDX ADDING

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

i want to change my name symbol and logo

Mergefy has been remove

@Mergifyio refresh

@Mergifyio rebase

I can help stop wasting your time refer this: #12970

Go my friend but i got nothing for you

@zakimzf  Go my friend but i got nothing for you

@zakimzf   unsupported file modified: .mergify.yml

The configuration has been changed, queue and merge actions are ignored.

@Mergifyio update

@Mergifyio update

@Mergifyio rebase

@Mergifyio refresh

@Mergifyio refresh

authors: sebslater zakimzf

repo: solana-labs/token-list


text:
Adding Toon token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Adding new token :)

I can help refer this https://github.com/zakimzf/profile/pull/1
PS: If you don't need my help then please ignore, no need to respond!

authors: OliveEra zakimzfs


text:
commit BX Bitpoenix X

X time from gitDesktop
I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

please confirm or merge as it says:
2 workflows awaiting approval
First-time contributors need a maintainer to approve running workflows. Learn more. 2 successful and 1 neutral checks


text:
Add language support (localization)

Is your feature request related to a problem? Please describe.
Hi there, I'm currently trying to implement localization within our app, however cannot find a solution to translate the wallet UI.
Describe the solution you'd like
I think it would be a great feature if I was able to pass in localisation as a property within the WalletProvider or Wallet object to dynamically change the locale.
Additional context
I have seen other Solana wallet libraries do this feature and so thought this would be helpful. If this already exists, or if there is an existing solution, please feel free to let me know and close this issue.

Hey, sounds like a great initiative. Not one I'm personally likely to undertake, but I'd be happy to accept PRs!

Iceboxing this until someone wants to take it on.

authors: jordansexton wheeeliam

repo: solana-labs/wallet-adapter


text:
Expose the index of transaction in a block

Definition
As soon as a block has been assembled by the leader the transactions in that block have a strict order. The order can be expressed using an index (0-based). The index does not change as long as the block is not changed.
Motivation

the index can be used to derive an ''happens-before'' relation between two or more transactions inside a block (but also universally)

discussed with jac0xb.sol (Sniper Labs)

Imagine you have two events emitted in two transactions that are related to the same state in one slot. To my knowledge its impossible to know which event went first/last with just getTransaction.

the transactions in that block have a strict order

Just want to make sure this is clear:
It is true that transactions have a strict and consistent order when they are recorded in PoH, but this is not necessarily true about execution order. When a node replays a block, it batches up the transactions based on account-locking rules and the transactions within each batch get executed in parallel. That means each node might execute the transactions within a batch in a different order. In practice, this means you can definitely reason about what "happened first" with 2 transactions that write to the same account, but not with 2 completely disparate transactions that were executed in parallel.
I would say this is a nuance that is not important to most if any RPC consumers.

authors: CriesofCarrots grooviegermanikus


text:
NH-89340: add scan as part of build and publish lambda layer

Description
Test (if applicable)
workflow: https://github.com/solarwinds/apm-ruby/actions/runs/10838011087
scanned result: (in reverse lab)

Looking at the example workflow run, does the scan step actually require the AWS credentials to be set?

authors: cheempz xuan-cao-swi

repo: solarwinds/apm-ruby


text:
NUI-6228 source code in nova docs does not work sometimes

Frontend Pull Request Description
Ticket link
The dashboard in the Nova docs did not display the source code due to the project's file system structure. I corrected the paths and file names, and now all dashboard source codes are displayed correctly.
Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have updated change log
[ ] I have been following Definition of done
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new lint warnings
[ ] New and existing unit tests pass locally and on CI with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

Additional Context (if necessary)

please use bugfix/NUI-6228 branch name because the circle ci will not start

authors: lodnanova-m pavlo-poimanov

repo: solarwinds/nova


text:
Fix: content-negotiation when fetching dataset from url

📁 Related issues

#1039
✍ Description

The reasoning behind this fix was to only use rdf-dereference when the input type is string. That is where the error seems to occur, other flows seem fine. (I might be wrong though)
✅ PR check list
Before this pull request can be merged, a core maintainer will check whether

[ ] this PR is labeled with the correct semver label

semver.patch: Backwards compatible bug fixes.
semver.minor: Backwards compatible feature additions.
semver.major: Breaking changes. This includes changing interfaces or configuration behaviour.

[ ] the correct branch is targeted. Patch updates can target main, other changes should target the latest versions/* branch.
[ ] the RELEASE_NOTES.md document in case of relevant feature or config changes.

I think it looks good now.

Force pushed the new changes

That should do it then

repo: solid/community-server


text:
Refactor AuthenticationResponse.errorResponse method

Refactor AuthenticationResponse.errorResponse method (see issue #9 for details).
Closes #9.

This is a minor refactoring that's adding comments and setting up better error reporting down the line.
cc @kjetilk / @RubenVerborgh for review.

@RubenVerborgh we good, re the comments?

repo: solid/oidc-rp


text:
Remove the LDP Basic tests from suite

As we do not have a strict LDP interpretation in Solid, this is removes the LDP test suite from the test suite itself. Those who use an LDP server below Solid are encouraged to run the LDP test suite as part of their environment.
We need to confirm the Docker container runs with this, thus the Work in progress tag in the subject.

This is a very long discussion, that has been going on for many months.
The spec draft was a quick thing put together by Ruben and myself, and previously, even though the old documentation says that it is an LDP application, NSS is just 20% compliant with the test suite. NSS also doesn't respect the interaction models, etc. In reality, LDP hasn't ever been crucial to Solid.
It might well be that a future Solid spec compliant implementation will pass 100% of the Solid test suite, but we will need to document all of Solid in tests anyway, and the 90 tests there will not change this. Meanwhile, I would be concerned that an implementor would come along and look at LDP and think they have to be Solid compliant, which is a mouthful. It is likely easier to write a compliant Solid implementation from scratch, than an LDP implementation from scratch.
I agree that there is little in terms of text, but it is being worked on. If you wish, we can wait to merge this until the new spec comes to the level where it is clear that the LDP legacy is too much to bear.

repo: solid/test-suite


text:
Comparison with Unlock

This is interesting: https://unlock-protocol.com/

From what I understand, I think the idea behind Unlock's "blockchain magic" can be understood in multiple layers:
Simplest approach:
As a creator, you encrypt your work so that it can only be consumed by consumers who have both the encrypted data and a password. You then provide the encrypted data for free, but sell the password via an e-commerce site.
Slightly improved approach:
Instead of selling the same password string to each customer via your e-commerce website, give each customer a different one (e.g. what PGP does is generate a key for a symmetric cipher, and cipher that for each recipient with their public key). That way each key is traceable to a specific purchase from your e-commerce website.
Add bundles:
The key doesn't open just 1 encrypted item, but several ones.
Combine with subscriptions:
The 'bundle of items' is a feed of episodes over time.
Add timers:
Add an extra step, so that the key doesn't directly open an episode, but needs to be exchanged for an episode key. This exchange can then be made to fail of the key has expired or was revoked.
Add a secondary market:
Let the keys be traded freely in a secondary market, and instead of checking for who purchased a specific key, check for who currently owns it. Smart!
Pretty neat! I think we might be able to copy parts of it into our 402 work (although the secondary market would require a move away from acl:PayingAgent.
Unlock puts the secondary market on Ethereum, but is that essential? I guess a nice feature of that is that a consumer who refuses to log in to your web shop can still buy a second-hand key on Ethereum, and that way you as a creator have no way of knowing who currently owns a given key. Just like when second-hand books change owner multiple times!

repo: solid/webmonetization


text:
Add option to suppress size from being printed

Closes #8

Anything special I need to do to get the same test locally as in CI? When I run the tests locally they all pass.

repo: solidiquis/erdtree


text:
root.tsx's fallback <Title> isn't applied on client side routing

Describe the bug
When you set a fallback <Title> in the root.tsx it's ignored on CSR (Client Side Routing), when you didn't initially loaded a page that used the default title. So for example when we have an application with 2 routes / and /about and we're setting the <Title> in root.tsx to "Default" and change it on the / route to "Home" while not setting any title on the /about route. We will get the following results:

Server Side Rendering

/ = "Home"
/about = "Default"

Client Side Routing

/ = "Home"
/about = "http://..." (default browser title) or "Default"

Reproduction
You can find a repository which contains the code to reproduce this bug here:
https://github.com/UnlimitedBytes/solidstart-bug.
I also hosted the above linked repository here:
https://solidstart-csr-fallback-bug.surge.sh/
Using the hosted version we can see what should happen by:

Opening https://solidstart-csr-fallback-bug.surge.sh/about
Clicking on "Home"
Clicking on "About"
which will give us the title "Default"

And what actually happens (the bug) by:

Opening https://solidstart-csr-fallback-bug.surge.sh/
Clicking on "About"
which will give us the title "http://..." (default browser title)

Severity
serious, but I can work around it

In setting up for SolidStarts next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed by mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience.

See https://github.com/solidjs/solid-start/pull/1139 for more details.

authors: UnlimitedBytes ryansolid

repo: solidjs/solid-start


text:
Add spree route namespace to admin inserted partials

See https://github.com/solidusio/solidus/pull/964 for rationale

Thanks!


text:
dont use resolveconf on system

trying to address:
https://github.com/solo-io/packer-builder-arm-image/issues/58
https://github.com/solo-io/packer-builder-arm-image/issues/50
it seems like mounting resolv.conf by default lead to failures in systemd systems.
this makes it so it is not mounted on known systemd images.
I'm open for discussion of what's the best way here. mount it on known images? add mount_ressolv boolean option? any other ideas?
cc @joshuaspence @hoshsadiq @micchickenburger

I had a bit of a look into this. The original error in #58 is because os.Stat seems to suggest that /etc/resolv.conf doesn't exist (because it is a symlink to a path that doesn't exist), but os.MkdirAll("/etc/resolv.conf", 0755) fails. I think we can fix this by using os.Lstat instead of os.Stat.
I don't think you need to do anything with /run/systemd.

I tried using os.Lstat instead of os.Stat but have now run into this problem: https://unix.stackexchange.com/questions/429724/how-do-i-mount-a-file-on-top-of-a-broken-symbolic-link

i see; so you are saying we should avoid mounting it if it exist.
maybe i'll add an optional mounts field that ignores errors and add resolve conf there?

No, you have to mount it (I think). I mounted the Ubuntu Raspberry Pi image without mounting /etc/resolv.conf and its borked.
root@mnt:/# dig google.com
Unsupported ancillary data: 0/1
Unsupported setsockopt level=41 optname=67
Unsupported setsockopt level=41 optname=66
Unsupported ancillary data: 41/67
Unsupported setsockopt level=41 optname=66
socket.c:2411: setsockopt(20, IPV6_RECVTCLASS) failed: Protocol not available

I am using systemd-nspawn here so it might be doing some magic but things start working if I add --bind /etc/resolv.conf.
root@mnt:/# ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Apr 24 01:02 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

what about copying it instead of mounting it?

@joshuaspence updated pr to copy resolv conf. do you think this will help? i can make the copy default on / optional off.

In my opinion to maintain backwards compatibility it should default to off.
In addition, can I suggest a possibly different approach. Often the reason for @joshuaspence original issue is because of DNS server is misconfigured or unreachable for one reason or another. In theory it's addressable without resolv.conf hacks like this, but that's usually a lot more time consuming, so this is in general easier. My suggestion is, instead of touching resolv.conf file, you could have an option for custom DNS entries, which, if set, simply writes a minimal resolv.conf file with just the DNS entries (nameserver <entry> for each entry item). What do you think?

Copying is not a good idea as then the file ends up in the image being created. I think we can probably bind mount both /run and /etc/resolve.conf (I think you would need to do /run first)
@hoshsadiq this technique (mounting resolve.conf inside a chroot) is quite common and is very similar to what systemd-nspawn.

For example, arch-chroot (https://wiki.archlinux.org/index.php/Chroot) does this too

if the issue that the file ends up in the image, we can make sure it is cleaned up if it was created.
I'm a bit scared bind mounting /run as this gives the image access to the host /run we might be destructive if these are different distributions, no?

I don’t think it would be destructive but the host would have to be a systemd host for mounting /run to be effective.
On Wed, May 20, 2020 at 07:29, Yuval Kohavi notifications@github.com wrote:

if the issue that the file ends up in the image, we can make sure it is cleaned up if it was created.
I'm a bit scared bind mounting /run as this gives the image access to the host /run we might be destructive if these are different distributions, no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think the best solution would be to mimic systemd-nspawn here. In https://github.com/systemd/systemd/pull/9024 they added --resolv-conf (available from version 239). From https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf:

Configures how /etc/resolv.conf inside of the container (i.e. DNS configuration synchronization from host to container) shall be handled. Takes one of off, copy-host, copy-static, bind-host, bind-static, delete or auto. If set to off the /etc/resolv.conf file in the container is left as it is included in the image, and neither modified nor bind mounted over. If set to copy-host, the /etc/resolv.conf file from the host is copied into the container. Similar, if bind-host is used, the file is bind mounted from the host into the container. If set to copy-static the static resolv.conf file supplied with systemd-resolved.service(8) is copied into the container, and correspondingly bind-static bind mounts it there. If set to delete the /etc/resolv.conf file in the container is deleted if it exists. Finally, if set to auto the file is left as it is if private networking is turned on (see --private-network). Otherwise, if systemd-resolved.service is connectible its static resolv.conf file is used, and if not the host's /etc/resolv.conf file is used. In the latter cases the file is copied if the image is writable, and bind mounted otherwise. It's recommended to use copy if the container shall be able to make changes to the DNS configuration on its own, deviating from the host's settings. Otherwise bind is preferable, as it means direct changes to /etc/resolv.conf in the container are not allowed, as it is a read-only bind mount (but note that if the container has enough privileges, it might simply go ahead and unmount the bind mount anyway). Note that both if the file is bind mounted and if it is copied no further propagation of configuration is generally done after the one-time early initialization (this is because the file is usually updated through copying and renaming). Defaults to auto.

#48 is relevant here :)

ok, I think we now have all the options. feedback is welcome

will merge and in a day or two if no objections

authors: hoshsadiq joshuaspence micchickenburger yuval-k

repo: solo-io/packer-builder-arm-image


text:
🛑 svet.kz is down

In 7e3c25c, svet.kz (https://svet.kz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: svet.kz is back up in b7799b0.


text:
rollback pybind11 because the latest one will cause build failure.

A commit used for discussion. Please do not merge this PR.

We will stay with cutting-edge pybind11.

repo: solvcon/solvcon


text:
Investigate why F35 kernel is so much larger

Since adding FC35, I've noticed the build artifacts for it are about 10x bigger than FC34 (bit under 100 MB to around 900 MB).  Why?

Hello,
I just want to add some notes here because I noticed the same problem.
I copied the docker files to my machine and ran builds on kernel-5.14.16 (stable) kernel-5.14.17 (testing)
Both the kernel-modules and kernel-core rpms end up about 10x larger than I am expecting.
Just to rule out the docker image, I also tried basing it off of F36 rawhide but the build sizes were the same as F35.

I tried a few more things. I was able to get the rpms built to the expected sizes by removing the "without debug" options when building.
The exact command I used to run this on the F35 container was rpmbuild -bb --target x86_64 --nodeps kernel.spec
I pulled that from the build logs on koji https://kojipkgs.fedoraproject.org//packages/kernel/5.14.16/301.fc35/data/logs/x86_64/build.log
This does take longer on my machine so I could only imagine how long it would take on github actions. Not to mention impractical if you don't need the debug.
Something seems faulty in the fedora build system to cause this, like a step got misplaced under a debug flag.

Hi @evanjarrett !! It sounds like you and I were thinking along the same lines here. 😁
I was in the Koji build logs last night and that became the basis for this commit and workflow run.  It didn't make sense that explicitly specifying the architecture and not verifying build deps would fix this, but I figured it was worth a shot.
When I originally shoved this into Actions, I found myself limited to not building the debug RPMs by the rather limited disk space on the runners.  I'll see what I can clear up off them and try building without the debug flags.  It doesn't fix the root problem, but at least we won't be slinging around an archive that's 10x what it needs to be.
If I can get some time, I'll dive into the specfile and makefiles around the debug flag.  If you get to doing that instead, mind copying what you find to this issue?  🙌🏻

Quick note to add that this commit is to free up disk space and build debug RPMs too.  This workflow run is testing that theory out.

So this latest commit + workflow run "resolves" it by building the debug RPMs and then not uploading them.  It's not ideal, but I can't fix this upstream.

authors: evanjarrett some-natalie

repo: some-natalie/fedora-acs-override


text:
All cluster together

I was finding it difficult to track the patient location and travel history. So added an other tab to track all the details in one cluster.

Thanks, though this looks quite chaotic. Two suggestions:

Merge latest changes from master that links stateless patients in city filter
Increase edge size/change edge style so that it looks less chaotic

Thanks, though this looks quite chaotic. Three suggestions:

Merge latest changes from master that links stateless patients in city filter
Increase edge size/change edge style so that it looks less chaotic
Making it generic enough so that new filters in the future can be included in the all filter
Add legends of all filters
done

hold it for sometime. I guess instead of showing every patient, let me restrict this to only the selected pID. I think will name it search. So only one patient and it's connected network.

authors: karasatishkumar sibeshkar


text:
jan 23 silent review

cbt
asked for an extension due to computer breaking last week. will have hacks done as soon as possible.

.5 API
.5 DB
1 CPT

repo: sommerss/compsci


text:
Add details on AWS deployment

Including some Sonatype specific links and additional details for new AWS users (like me!).
@bhamail can you please review.

PS: Build may fail due to unrelated OSSIndex issues, so don't spend cycles worrying about that. Merge away if you like.

authors: bhamail theresa-m

repo: sonatype-nexus-community/bbash


text:
docker版启动后，可能得等一阵子才能用api

例行检查

[x] 我已确认目前没有类似 issue
[x] 我已确认我已升级到最新版本
[x] 我已完整查看过项目 README，尤其是常见问题部分
[x] 我理解并愿意跟进此 issue，协助测试和提供反馈
[x] 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

问题描述
docker部署one-api在自己的两台电脑上，两台电脑都出现了一样的问题
数据库用sqllite，挂载了一个本地目录到docker作为/data目录
添加了百度千帆的渠道
大概有一半以上的概率，docker容器启动后，需要等若干时间，api才能使用。也有启动后，很快能用的情况。但没有一直不能用的情况。
看docker logs，没发现有问题的日志
复现步骤
见问题描述
预期结果
每次docker启动，api就能立马可用

持久化编码器就行
TIKTOKEN_CACHE_DIR, DATA_GYM_CACHE_DIR

what is you meaning?
can not understard

docker方式进行部署
解决token-encoder的问题之后，看截图应该是正常启动了。
但访问3000端口一直没反应，页面左上角一直转圈圈

authors: GrayXu NiceToMeetYou2 wencan

repo: songquanpeng/one-api


text:
Set Go stable versions to .travis.yml

The title said all.

@YoshiyukiMineo Please review it if you have free time :)

Thank you.

authors: YoshiyukiMineo osamingo

repo: sony/sonyflake


text:
COM-1106 Add biography field to user

[ ] Mon code est testé unitairement - np

[ ] Mon code est testé avec des tests d'intégration - np

Périmetre roles :  ROF / admin vendeur

Cas d'usage :  MAJ du user

Est-ce qu'il ne faudrait pas ajouter le champs biography dans le payload du test de l'update ?

authors: cmolle jctrebalag

repo: sophiemoustard/alenvi-api


text:
Com 2165

J'ai ajouté une variable d'environnement :

[ ] J'ai précisé sur le slite de MES et MEP les modifications faites

[ ] J'ai verifié la fonctionnalite sur mobile

Périmetre interface : outil

Périmetre roles : coach admin et aux

Cas d'usage : fix du bug d'affichage.

Comment tester :

ETQ Coach admin :

tester le planning aux :

créer deux auxiliaire avec le meme nom dans deux secteurs differents (ou renommer une auxiliaire avec le meme nom qu'une autre)
ajout, suppression de tag des deux auxiliaires doublons
avec le tag secteur, verifier que la bonne auxiliaire est dans le bon secteur, qu'elle apparait pas en double, que son homonyme peut etre ajouté/enlevé

tester le chemin fiche aux -> Planning aux

on arrive bien sur le planning de la bonne aux
on peut ajouter son homonyme, son secteur et tout se passe bien

tester la sauvegarde de la recherche si on sort et on revient sur la page

MEME CHOSE POUR PLANNING BENEF : reprend les mm points un par un

ETQ Aux :

tester le planning aux

mon secteur est present par default
je peux voir mon planning et celui de mon homologue

MEME CHOSE POUR PLANNING BENEF

J’ai du supprimer le emit-value car c’est pas compatible avec map-option
https://github.com/quasarframework/quasar/issues/4567
Du coup, je me retrouve avec des objets (auxiliairy, customer, sector) dans le process de sauvegarde de filtre. Et non pas un tableau d’id comme prevu.
On pourrai faire en sorte que store.planning.filter soit un tableau plus concis:  { value : ObjectId, label: “nom benef ou aux ou secteur”} mais il faudrait faire des appel a l’api dans CustomerPlanning et AuxiliaryPlanning pour re-mapper planning.filter pour les customer et les auxiliaries genre : Auxiliaryfilter = this.planning.filters.filter(f => f.type === AUXILIARY).map( f => { …auxiliaryListFromAPI.find(aux => aux._id === f.value), ...f)  ca m’a l’air relou a faire

Je ne sais pas si ca vient de ta pr mais si je mets sur la planning : l'equipe d'un auxiliaire en doublon + cet auxiliaire + l'autre auxiliaire en doublon et que j'enleve l'un des deux auxiliaires, j'ai une 403 sur la route eventHistories. Est-ce que tu pourrais regarder d'ou ca vient ? Si ca ne vient pas de ta pr, tu peux creer un ticket de bug.

authors: CorentinMartinot cmolle

repo: sophiemoustard/compani-webapp


text:
node_terraform.yml

Merge to main branch

Changed name of the file


text:
YARD completion snippet after typing ##

Motivation

Hoping to encourage more people to write documentation comments in our codebase.
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_LOBTBknX0GuNL2
→ https://go/builds/bui_LOBTsKSYEKYvRJ

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_LOBoAzciK73sp0
→ https://go/builds/bui_LOBoIb6tCCAsWZ

repo: sorbet/sorbet


text:
Allow specifying --track-untyped={everywhere,nowhere}

Motivation

This converts from a bool to an enum class with two entries, and
changes the option parsing to parse string names like
--track-untyped
--track-untyped=everywhere
--track-untyped=nowhere

and also LSP configuration like
"highlightUntyped": false,
"highlightUntyped": true,
"highlightUntyped": "",
"highlightUntyped": "nowhere",
"highlightUntyped": "everywhere",
// and omitted

In the future, I plan to add an option like "EverywhereButTests" which
will use the isPackagedTest flag on core::File to decide whether to
show untyped highlights there.
Test plan

See included automated tests.

Seems to break VS Code in manual testing.


text:
Handle Problems

Hey! I just started experiencing some problems with handles on my yaks that I would assume can be attributed to a recent update that yodel received. I added a handle earlier in the day and now whether I press on or off on the new on/off handle toggle, I still get a handle. Every time I yak then, I have to turn the handle on, delete it, turn it off, and then post the yak. Thanks!

I probably should've tested the handle feature again after I changed the toggle. Grr.
I'll look into it tomorrow.

I just pushed another update, version 1.1.0.3, to fix this. It should be available on the Store in the next few hours. Thanks for reporting this!


text:
Make a Lambda to add users.

sys_user_management

Use SAM
Receive list of names in event
Create users in IAM with these names and random passwords. DO NOT require users to set new passwords.
Attach to them Administrator AWS managed policy
Output a JSON user: pass

Solved in #3

Solved in PR #3

repo: sosw/sosw-master-classes


text:
README.md中使用方法错误

docker run --rm -v `pwd`/fonts:/app/fonts \
                -v `pwd`/output:/app/output \
                soulteary/docker-gitbook-pdf-generator "http://self-publishing.ebookchain.org"

中的pwd`/fonts:/app/fonts`应改为pwd/fonts:/usr/share/fonts

感谢反馈，你提的问题似乎无法复现。
按照 readme 执行结果如下：
docker run --rm -v `pwd`/fonts:/app/fonts \
                -v `pwd`/output:/app/output \
                soulteary/docker-gitbook-pdf-generator "http://self-publishing.ebookchain.org"

/usr/local/lib/python3.7/site-packages/weasyprint/fonts.py:230: UserWarning: FontConfig: No fonts configured. Expect ugly output.
  'FontConfig: No fonts configured. '
crawling :  http://self-publishing.ebookchain.org/index.html
crawling :  http://self-publishing.ebookchain.org/1-干嘛要写书？/1-写书的必要性/readme.html
crawling :  http://self-publishing.ebookchain.org/1-干嘛要写书？/2-写书的好处/readme.html
crawling :  http://self-publishing.ebookchain.org/2-什么是自出版平台？/readme.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/readme.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/1-Summary的安装.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/2-Summary的使用.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/3-电子书的生成.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/4-电子书的发布.html
crawling :  http://self-publishing.ebookchain.org/4-最佳实践/妙手偶得无须刻意.html
crawling :  http://self-publishing.ebookchain.org/5-附录/0-参考信息.html
crawling :  http://self-publishing.ebookchain.org/5-附录/1-关于作者.html
done :  http://self-publishing.ebookchain.org/5-附录/1-关于作者.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/4-电子书的发布.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/2-Summary的使用.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/1-Summary的安装.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/readme.html
done :  http://self-publishing.ebookchain.org/2-什么是自出版平台？/readme.html
done :  http://self-publishing.ebookchain.org/4-最佳实践/妙手偶得无须刻意.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/3-电子书的生成.html
done :  http://self-publishing.ebookchain.org/index.html
done :  http://self-publishing.ebookchain.org/1-干嘛要写书？/2-写书的好处/readme.html
done :  http://self-publishing.ebookchain.org/1-干嘛要写书？/1-写书的必要性/readme.html
done :  http://self-publishing.ebookchain.org/5-附录/0-参考信息.html
crawl : all done!
Generating pdf,please wait patiently
Generated

@soulteary
用您的方式生成，就像回复中的输出一样会提示 "/usr/local/lib/python3.7/site-packages/weasyprint/fonts.py:230: UserWarning: FontConfig: No fonts configured. Expect ugly output.
'FontConfig: No fonts configured. '"
并且生成的 pdf 中文乱码。
用 /usr/share/fonts 路径后，报错消失，生成的 pdf 中文正常。

以下是两条命令的对比
```docker run --rm -v pwd/fonts:/app/fonts
-v pwd/output:/app/output
soulteary/docker-gitbook-pdf-generator "http://self-publishing.ebookchain.org"
crawling :  http://self-publishing.ebookchain.org/index.html
crawling :  http://self-publishing.ebookchain.org/1-干嘛要写书？/1-写书的必要性/readme.html
crawling :  http://self-publishing.ebookchain.org/1-干嘛要写书？/2-写书的好处/readme.html
crawling :  http://self-publishing.ebookchain.org/2-什么是自出版平台？/readme.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/readme.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/1-Summary的安装.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/2-Summary的使用.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/3-电子书的生成.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/4-电子书的发布.html
crawling :  http://self-publishing.ebookchain.org/4-最佳实践/妙手偶得无须刻意.html
crawling :  http://self-publishing.ebookchain.org/5-附录/0-参考信息.html
crawling :  http://self-publishing.ebookchain.org/5-附录/1-关于作者.html
done :  http://self-publishing.ebookchain.org/4-最佳实践/妙手偶得无须刻意.html
done :  http://self-publishing.ebookchain.org/index.html
done :  http://self-publishing.ebookchain.org/2-什么是自出版平台？/readme.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/2-Summary的使用.html
done :  http://self-publishing.ebookchain.org/1-干嘛要写书？/2-写书的好处/readme.html
done :  http://self-publishing.ebookchain.org/5-附录/1-关于作者.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/3-电子书的生成.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/4-电子书的发布.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/readme.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/1-Summary的安装.html
done :  http://self-publishing.ebookchain.org/1-干嘛要写书？/1-写书的必要性/readme.html
done :  http://self-publishing.ebookchain.org/5-附录/0-参考信息.html
crawl : all done!
Generating pdf,please wait patiently
Generated
/usr/local/lib/python3.7/site-packages/weasyprint/fonts.py:230: UserWarning: FontConfig: No fonts configured. Expect ugly output.
'FontConfig: No fonts configured. '

docker run --rm -v pwd/fonts:/usr/share/fonts
-v pwd/output:/app/output
soulteary/docker-gitbook-pdf-generator "http://self-publishing.ebookchain.org"
crawling :  http://self-publishing.ebookchain.org/index.html
crawling :  http://self-publishing.ebookchain.org/1-干嘛要写书？/1-写书的必要性/readme.html
crawling :  http://self-publishing.ebookchain.org/1-干嘛要写书？/2-写书的好处/readme.html
crawling :  http://self-publishing.ebookchain.org/2-什么是自出版平台？/readme.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/readme.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/1-Summary的安装.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/2-Summary的使用.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/3-电子书的生成.html
crawling :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/4-电子书的发布.html
crawling :  http://self-publishing.ebookchain.org/4-最佳实践/妙手偶得无须刻意.html
crawling :  http://self-publishing.ebookchain.org/5-附录/0-参考信息.html
crawling :  http://self-publishing.ebookchain.org/5-附录/1-关于作者.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/readme.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/1-Summary的安装.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/2-Summary的使用.html
done :  http://self-publishing.ebookchain.org/5-附录/1-关于作者.html
done :  http://self-publishing.ebookchain.org/2-什么是自出版平台？/readme.html
done :  http://self-publishing.ebookchain.org/1-干嘛要写书？/2-写书的好处/readme.html
done :  http://self-publishing.ebookchain.org/5-附录/0-参考信息.html
done :  http://self-publishing.ebookchain.org/index.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/3-电子书的生成.html
done :  http://self-publishing.ebookchain.org/1-干嘛要写书？/1-写书的必要性/readme.html
done :  http://self-publishing.ebookchain.org/4-最佳实践/妙手偶得无须刻意.html
done :  http://self-publishing.ebookchain.org/3-如何打造自己的平台？/4-电子书的发布.html
crawl : all done!
Generating pdf,please wait patiently
Generated

authors: atiAkizuki shiny soulteary

repo: soulteary/docker-gitbook-pdf-generator


text:
Trocar setShippingType por metodos mais declarativos

Esperar o noob lembrar quando usar o 1, 2 ou 3, pode ser muita coisa.
Talvez, algo como os exemplos abaixo ajudasse um pouco mais.
$this->setShippingTypePAC(); //$this->setShippingType(1);
$this->setShippingTypeSedex(); //$this->setShippingType(2);
$this->setShippingTypeOther(); //$this->setShippingType(3);
@grolandao o que acha?

Acho valido, essa alteração de fato facilita para uma "leitura" mais clara do código.

Show de bola, precisamos manter todos próximos métodos dessa forma.

authors: Sena grolandao

repo: sounoob/pagseguro-php-sdk


text:
Update stories dependencies (major versions)

Description

There was a massive update to a bunch of packages in the remark ecosystem recently. This PR updates those dependencies, also resolving their associated breaking changes.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 6278579827

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 37.278%

Totals

Change from base Build 6219355459:
0.0%

Covered Lines:
5709

Relevant Lines:
14398

💛  - Coveralls

repo: source-academy/frontend


text:
Implement chained error reporting support

Closes #43

TODO

[ ] add tests
[ ] wait for norad release with latest error handling updates, then update Cargo.toml dependency

rebased on main branch @ commit bb323937f8621b679c652e2142825d6cf6a0f759

The new error handling changes were pushed in norad v0.7.0.  We should be ready to move these updates into a new release.

repo: source-foundry/ufofmt


text:
fix replace prefix logic for infill prompt

noticed this issue while looking at the case issue
This PR fix replacement logic we use for the infill prompt, previously (my bad) we remove the tail from the prefix to reserve the spacing, but this could remove the same code from the earlier part of the prefix.
Example:
We removed the // from earlier part of the code, so it looks incorrect in the request we send to cody, causing cody sometimes reply with unhelpful suggestion

this change makes sure only the last match is removed
Test plan

now it can generate correct suggestions

@tjdevries FYI this is where I update the prompt for the infill mode for claude.

repo: sourcegraph/cody


text:
Support Sidebar: new Community Forum and update Discord icon

CLOSE https://github.com/sourcegraph/cody/issues/3709

[x] Added Discord icon to Cody font
[x] New "Community Forum" and links to https://community.sourcegraph.com/c/cody/vs-code/6 not https://help.sourcegraph.com/hc/en-us/requests/new
[x] The Discord icon should be replaced with the Discord logomark

Test plan

Verify "Community Forum" is showing up and links to https://community.sourcegraph.com/c/cody/vs-code/6 on click
Verify Discord icon is replaced with the Discord logomark outline

After

Before

Strong opinion, fairly strongly held ahead:
I think there's a lot of "link creep" in this panel when it comes to support. I don't think the IDE should be telling users where to go depending on what their question is, as it's such a small piece of real estate and clutters up the general user experience.
Rather, there should be 1 link that takes the user here: https://help.sourcegraph.com/hc/en-us. This, then, is the jumping off point to any support related documentation/forms that help answer the user's question. The added benefit here is we can  also easily adjust the links on this page through our support teams, rather than using eng cycles to update links in the IDE extensions.
CC: @chillatom What do you think?

there should be 1 link that takes the user here: https://help.sourcegraph.com/hc/en-us. This, then, is the jumping off point to any support related documentation/forms that help answer the user's question. The added benefit here is we can also easily adjust the links on this page through our support teams, rather than using eng cycles to update links in the IDE extensions.

+1, supportive of this approach.
So [Community, Support, Discord] -> Support?

@kalanchan can you update the issue with the details for the finalized eng task once this is confirmed please?

there should be 1 link that takes the user here: https://help.sourcegraph.com/hc/en-us. This, then, is the jumping off point to any support related documentation/forms that help answer the user's question. The added benefit here is we can also easily adjust the links on this page through our support teams, rather than using eng cycles to update links in the IDE extensions.

+1, supportive of this approach.
So [Community, Support, Discord] -> Support?

How about:
[Community, Support] -> Support?
and we leave Discord alone? I think the community team likes driving traffic to discord via a dedicated link.
thoughts @jdorfman @kukicado

@jdorfman sounds good thanks!
@abeatrix let's remove the "Community Forum" row, and change the "Support" url to https://srcgr.ph/cody-support and leave Discord

https://srcgr.ph/cody-support

@kalanchan this works for all users and is not limited to Cody-Pro users, right?

@abeatrix oh yes, good point. Let's remove the Cody Pro condition, and open it for all
cc @chenkc805 @chillatom

@abeatrix oh yes, good point. Let's remove the Cody Pro condition, and open it for all
cc @chenkc805 @chillatom

Done. Can I get your review again to make sure the latest change aligns with what we discussed?

authors: abeatrix chenkc805 chillatom kalanchan


text:
bug: java.lang.StringIndexOutOfBoundsException: begin 1, end 0, length 0

Plugin version: 5.2.21709
IDE version: PC-233.13763.11
Exception: java.lang.StringIndexOutOfBoundsException: begin 1, end 0, length 0
Stacktrace:
java.lang.StringIndexOutOfBoundsException: begin 1, end 0, length 0
	at java.base/java.lang.String.checkBoundsBeginEnd(String.java:4606)
	at java.base/java.lang.String.substring(String.java:2709)
	at java.base/java.lang.String.subSequence(String.java:2747)
	at com.sourcegraph.cody.autocomplete.CodyAutocompleteManager.triggerAutocomplete(CodyAutocompleteManager.kt:163)
	at com.sourcegraph.cody.editor.CodyLookupListener$activeLookupChanged$1.uiRefreshed(CodyLookupListener.kt:31)
	at com.intellij.codeInsight.lookup.impl.LookupImpl.fireUiRefreshed(LookupImpl.java:1016)
	at com.intellij.codeInsight.lookup.impl.LookupImpl.refreshUi(LookupImpl.java:1216)
	at com.intellij.codeInsight.completion.CompletionProgressIndicator.hideAutopopupIfMeaningless(CompletionProgressIndicator.java:718)
	at com.intellij.codeInsight.completion.CompletionProgressIndicator.scheduleRestart(CompletionProgressIndicator.java:857)
	at com.intellij.codeInsight.completion.CompletionProgressIndicator.prefixUpdated(CompletionProgressIndicator.java:806)
	at com.intellij.codeInsight.completion.BaseCompletionLookupArranger.prefixTruncated(BaseCompletionLookupArranger.java:588)
	at com.intellij.codeInsight.lookup.impl.LookupImpl.truncatePrefix(LookupImpl.java:404)
	at com.intellij.codeInsight.lookup.impl.LookupImpl.truncatePrefix(LookupImpl.java:399)
	at com.intellij.codeInsight.lookup.impl.BackspaceHandler.truncatePrefix(BackspaceHandler.java:49)
	at com.intellij.codeInsight.lookup.impl.BackspaceHandler.doExecute(BackspaceHandler.java:35)
	at com.intellij.openapi.editor.actionSystem.DynamicEditorActionHandler.doExecute(DynamicEditorActionHandler.java:63)
	at com.intellij.openapi.editor.actionSystem.EditorActionHandler.lambda$execute$4(EditorActionHandler.java:199)
	at com.intellij.openapi.editor.actionSystem.EditorActionHandler.doIfEnabled(EditorActionHandler.java:89)
	at com.intellij.openapi.editor.actionSystem.EditorActionHandler.execute(EditorActionHandler.java:198)
	at com.intellij.openapi.editor.actionSystem.EditorAction.lambda$actionPerformed$0(EditorAction.java:92)
	at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:225)
	at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:177)
	at com.intellij.openapi.editor.actionSystem.EditorAction.actionPerformed(EditorAction.java:101)
	at com.intellij.openapi.editor.actionSystem.EditorAction.actionPerformed(EditorAction.java:77)
	at com.intellij.openapi.actionSystem.ex.ActionUtil.doPerformActionOrShowPopup(ActionUtil.java:344)
	at com.intellij.openapi.keymap.impl.ActionProcessor.performAction(ActionProcessor.java:32)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher$myActionProcessor$1.performAction(IdeKeyEventDispatcher.kt:496)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcherKt.doPerformActionInner$lambda$4$lambda$3(IdeKeyEventDispatcher.kt:831)
	at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:106)
	at com.intellij.openapi.application.TransactionGuardImpl.performUserActivity(TransactionGuardImpl.java:95)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcherKt.doPerformActionInner$lambda$4(IdeKeyEventDispatcher.kt:831)
	at com.intellij.openapi.actionSystem.ex.ActionUtil.performDumbAwareWithCallbacks(ActionUtil.java:381)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcherKt.doPerformActionInner(IdeKeyEventDispatcher.kt:829)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcherKt.access$doPerformActionInner(IdeKeyEventDispatcher.kt:1)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processAction$intellij_platform_ide_impl(IdeKeyEventDispatcher.kt:559)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processAction(IdeKeyEventDispatcher.kt:509)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processActionOrWaitSecondStroke(IdeKeyEventDispatcher.kt:448)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.inInitState(IdeKeyEventDispatcher.kt:441)
	at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.dispatchKeyEvent(IdeKeyEventDispatcher.kt:303)
	at com.intellij.ide.IdeEventQueue.dispatchKeyEvent(IdeEventQueue.kt:620)
	at com.intellij.ide.IdeEventQueue._dispatchEvent$lambda$11(IdeEventQueue.kt:581)
	at com.intellij.openapi.application.impl.RwLockHolder.runWithEnabledImplicitRead(RwLockHolder.kt:75)
	at com.intellij.openapi.application.impl.RwLockHolder.runWithImplicitRead(RwLockHolder.kt:67)
	at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.kt:581)
	at com.intellij.ide.IdeEventQueue.access$_dispatchEvent(IdeEventQueue.kt:72)
	at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1.compute(IdeEventQueue.kt:355)
	at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1.compute(IdeEventQueue.kt:354)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:793)
	at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1.invoke(IdeEventQueue.kt:354)
	at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1.invoke(IdeEventQueue.kt:349)
	at com.intellij.ide.IdeEventQueueKt.performActivity$lambda$1(IdeEventQueue.kt:1014)
	at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:114)
	at com.intellij.ide.IdeEventQueueKt.performActivity(IdeEventQueue.kt:1014)
	at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$7(IdeEventQueue.kt:349)
	at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:848)
	at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.kt:391)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
	at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)

dupe of https://github.com/sourcegraph/jetbrains/issues/560

repo: sourcegraph/jetbrains


text:
Add live_stream parameter to npm_package execution

Description
Adds the ability to set live_stream to monitor npm package installation in real-time
Issues Resolved
None
Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

Simple enough.

npm_package tests should be added before merging this change.

Need README and Changelog updates. I'll add those.

Updates to the change log and readme files are included in another PR>

authors: MarkGibbons bdwyertech

repo: sous-chefs/nodejs


text:
port: [#6685][#4529] Update JwtTokenExtractor

#minor
Description
This PR updates the throws exception on expired token test to avoid the throwing of an exception.
Because the implementation of token handling between botbuilder-dotnet and botbuilder-js is different, we made no changes since botbuilder-js uses a cache check as a security method for the token key. It also does not use two entities to handle the token, it only uses the decoded token.
Specific Changes

Updated authorization token in  throws exception on expired token test.
Replaced the use of sinon.spy by sinon.stub in  throws exception on expired token test in cloudAdapter.test.

Testing
The following image shows the unit test throws exception on expired token passing without throw an error.

/promoted 4531

authors: JhontSouth ceciliaavila

repo: southworks/botbuilder-js


text:
[StyleCop] Fix all the warning in Bot.Builder.Dialogs

Add documentation for constructor and parameters

Promoted to MS # 1444

authors: Aliandi GasparAcevedoZainSouthworks

repo: southworkscom/botbuilder-dotnet


text:
version `GLIBC_2.29' not found (required by himalaya)

Still officially supported Debian versions 9, 10 won't run recent himalaya due to dependency on  GLIBC_2.29.
Is it possible to compile himalaya against musl to make it truly portable or at least lower requirement to avoid be dependent on most recent GLIBC ?

It is a very good question, I need to dig. Any help is welcomed!

Tested it, one needs to jump a few hoops but it's doable:

Install musl and musl-gcc (on debian-ish, that's musl and musl-tools)

Install the musl target: rustup target install x86_64-unknown-linux-musl

Set these to make OpenSSL compile:
export PKG_CONFIG_ALLOW_CROSS=1
export OPENSSL_STATIC=true

(this is where a rustls feature could be helpful)

Build it: cargo build --release --target x86_64-unknown-linux-musl

I tried but it does not compile :disappointed: DSO missing from command line

The only way I know to make truly portable across platform a program on amd64/linux is to spin out in virtual machine (or docker) with  AlpineLinux (that natively using musl instead of glib ) and compile it there

Yeah, that's probably easier. You don't even need a linux, here's me on Windows 10:
❯ docker run -v "${PWD}:/volume" --rm -t clux/muslrust:stable cargo build --release
 # magic is happening
❯ ubuntu2004.exe run ldd target/x86_64-unknown-linux-musl/release/himalaya
        statically linked
❯ ubuntu2004.exe run ./target/x86_64-unknown-linux-musl/release/himalaya -V
himalaya 0.6.1

See https://github.com/clux/muslrust

So technically I can add a musl build to the release via GitHub Actions? I will give a shot and let you know!

So technically I can add a musl build to the release via GitHub Actions? I will give a shot and let you know!

Thank you!
Unfortunately rust isn't my language where I can contribute :(

@CompuRoot could you try the artifact himalaya-musl generated by the CI? https://github.com/soywod/himalaya/actions/runs/3712824669

Awesome, I will add the config to the deployment script. The build will be added to the release section!

Thank you so much !!!

@CompuRoot could you try the artifact himalaya-musl generated by the CI? https://github.com/soywod/himalaya/actions/runs/3712824669

It works !!!
I deeply appreciate what you did !!!

authors: CompuRoot MCOfficer soywod

repo: soywod/himalaya


text:
Connection fails, tested on v1.0.0-alpha6

Decided to give the new tag a try and ran straight forward into a issue. Am I missing something with the new version?
Both tests were performed with https://github.com/sozu-proxy/lapin/blob/master/examples/consumer.rs
Tested with same settings on v0.39.7 (74c88c31cae02ab969e1879481cd47bb4336114c) and works like a charm, but on 1.0.0-alpha6 (5e5dfa9bf0dca58ad09552e231f156a24e4c3e98) it fails to connect to the server, returning the following:

[2020-04-23T15:11:36Z ERROR lapin::io_loop] error writing: IOError(Os { code: 10057, kind: NotConnected, message: "A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied." })
[2020-04-23T15:11:36Z ERROR lapin::channels] Connection error
thread 'main' panicked at 'connection error: IOError(Os { code: 10057, kind: NotConnected, message: "A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied." })', src\bin\main.rs:15:20

Backtrace:
stack backtrace:
   0: backtrace::backtrace::trace_unsynchronized
             at C:\Users\VssAdministrator\.cargo\registry\src\github.com-1ecc6299db9ec823\backtrace-0.3.40\src\backtrace\mod.rs:66
   1: std::sys_common::backtrace::_print_fmt
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\sys_common\backtrace.rs:77
   2: std::sys_common::backtrace::_print::{{impl}}::fmt
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\sys_common\backtrace.rs:59
   3: core::fmt::write
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libcore\fmt\mod.rs:1052
   4: std::io::Write::write_fmt<std::sys::windows::stdio::Stderr>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\io\mod.rs:1426
   5: std::sys_common::backtrace::_print
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\sys_common\backtrace.rs:62
   6: std::sys_common::backtrace::print
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\sys_common\backtrace.rs:49
   7: std::panicking::default_hook::{{closure}}
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panicking.rs:204
   8: std::panicking::default_hook
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panicking.rs:224
   9: std::panicking::rust_panic_with_hook
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panicking.rs:472
  10: std::panicking::begin_panic_handler
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panicking.rs:380
  11: core::panicking::panic_fmt
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libcore\panicking.rs:85
  12: core::option::expect_none_failed
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libcore\option.rs:1199
  13: core::result::Result<lapin::close_on_drop::CloseOnDrop<lapin::connection::Connection>, lapin::error::Error>::expect<lapin::close_on_drop::CloseOnDrop<lapin::connection::Connection>,lapin::error::Error>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\src\libcore\result.rs:991
  14: main::main::{{closure}}
             at .\src\bin\main.rs:16
  15: std::future::{{impl}}::poll<generator-1>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\src\libstd\future.rs:43
  16: futures_executor::local_pool::{{impl}}::run_until::{{closure}}<std::future::GenFuture<generator-1>>
             at C:\Users\Someone\.cargo\registry\src\github.com-1ecc6299db9ec823\futures-executor-0.3.4\src\local_pool.rs:177
  17: futures_executor::local_pool::run_executor::{{closure}}<(),closure-0>
             at C:\Users\Someone\.cargo\registry\src\github.com-1ecc6299db9ec823\futures-executor-0.3.4\src\local_pool.rs:87
  18: std::thread::local::LocalKey<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify>>::try_with<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify>,closure-0,()>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\src\libstd\thread\local.rs:262
  19: std::thread::local::LocalKey<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify>>::with<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify>,closure-0,()>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\src\libstd\thread\local.rs:239
  20: futures_executor::local_pool::run_executor<(),closure-0>
             at C:\Users\Someone\.cargo\registry\src\github.com-1ecc6299db9ec823\futures-executor-0.3.4\src\local_pool.rs:83
  21: futures_executor::local_pool::LocalPool::run_until<std::future::GenFuture<generator-1>>
             at C:\Users\Someone\.cargo\registry\src\github.com-1ecc6299db9ec823\futures-executor-0.3.4\src\local_pool.rs:174
  22: main::main
             at .\src\bin\main.rs:15
  23: std::rt::lang_start::{{closure}}<()>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\src\libstd\rt.rs:67
  24: std::rt::lang_start_internal::{{closure}}
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\rt.rs:52
  25: std::panicking::try::do_call<closure-0,i32>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panicking.rs:305
  26: panic_unwind::__rust_maybe_catch_panic
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libpanic_unwind\lib.rs:86
  27: std::panicking::try
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panicking.rs:281
  28: std::panic::catch_unwind
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\panic.rs:394
  29: std::rt::lang_start_internal
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\/src\libstd\rt.rs:51
  30: std::rt::lang_start<()>
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447\src\libstd\rt.rs:67
  31: main
  32: invoke_main
             at d:\agent\_work\5\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
  33: __scrt_common_main_seh
             at d:\agent\_work\5\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
  34: BaseThreadInitThunk
  35: RtlUserThreadStart

I see you're running windows, this might be related I guess?
Would you be willing to bisect this issue?
git bisect start
git bisect good 0.39.7
git bisect bad 1.0.0-alpha6

Then run your test and use either git bisect good if your test passes or git bisect bad if it doesn't. This will take a few steps and will identify the commit introducing the regression for you.
I do not have any windows system to test this on my side, and on linux everything seems fine

Actually, as a first step you could try with 1.0.0-alpha5, as we switched to our new reactor in alpha6

Alright so it seems that cargo has bugged the registry when I was previously switching from alpha1 to alpha6 because I have already tried them before writing here and they were failing as well. (no wonder the registry was so fast when updating..)
However 1.0.0-alpha5 doesn't seem to have that issue while 1.0.0-alpha6 have it.
Bisecting: 7 revisions left to test after this (roughly 3 steps)
[a1688fa6e94993d92cbd668b2060cbc45b827594] port to Reactor
e01108b4d9b3947eb3b1c997199342dca277004e is fine
Seems like io_loop::handle_write_result() is failing but socket status is can_read=true, can_write=true, has_data=true

Thanks for confirming. I'll see if I can find anything obvious, but might be kind of hand without being able to test myself

I'll continue looking into the issue as well and see what I can dig up
tomorrow.
On Thu, Apr 23, 2020, 22:49 Marc-Antoine Perennou notifications@github.com
wrote:

Thanks for confirming. I'll see if I can find anything obvious, but might
be kind of hand without being able to test myself
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sozu-proxy/lapin/issues/271#issuecomment-618625964,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMPFMZ55K6XN5PQAF3MZCL3ROCLVJANCNFSM4MPEX5GQ
.

@Dango-rs Can you try the "connected" branch I just pushed?

@Keruspe Connects successfully but drops the connection right after that.
Here's the full trace from the log. Basically the error didn't change, it just moved a step.
[2020-04-23T20:38:27Z TRACE amq_protocol_tcp] Connecting to xxxxxxxxxx.com:5672
[2020-04-23T20:38:27Z DEBUG lapin::channels] create channel with id 0
[2020-04-23T20:38:27Z TRACE lapin::channel] channel 0 send_frame
[2020-04-23T20:38:27Z TRACE lapin::channel] channel 0 wake
[2020-04-23T20:38:27Z TRACE mio::poll] registering event source with poller: token=Token(1), interests=READABLE | WRITABLE
[2020-04-23T20:38:27Z TRACE lapin::reactor] reactor poll
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader.Ok] Called from future, registering waker
[2020-04-23T20:38:27Z TRACE lapin::io_loop] io_loop run
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader.Ok] Called from future, registering waker up in chain
[2020-04-23T20:38:27Z TRACE lapin::socket_state] Got event for socket: Wake
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader] Called from future, registering waker
[2020-04-23T20:38:27Z TRACE lapin::socket_state] Got event for socket: Wake
[2020-04-23T20:38:27Z TRACE lapin::io_loop] io_loop do_run; can_read=true, can_write=true, has_data=true
[2020-04-23T20:38:27Z INFO  lapin::io_loop] Connected to xxx.xxx.xxx.xxx:5672
[2020-04-23T20:38:27Z TRACE lapin::io_loop] will write to buffer: AMQPFrame::ProtocolHeader
[2020-04-23T20:38:27Z ERROR lapin::io_loop] error writing: IOError(Os { code: 10057, kind: NotConnected, message: "A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no ad
dress was supplied." })
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader.Ok] Resolving promise
[2020-04-23T20:38:27Z TRACE pinky_swear] Got data, waking our waker
[2020-04-23T20:38:27Z ERROR lapin::channels] Connection error
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader.Ok] Called from future, registering waker
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader] Resolving promise
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader.Ok] Called from future, registering waker up in chain
[2020-04-23T20:38:27Z TRACE pinky_swear] Got data, waking our waker
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader] Called from future, registering waker
[2020-04-23T20:38:27Z TRACE pinky_swear] Got data, notifying next in chain
[2020-04-23T20:38:27Z TRACE pinky_swear] Got data, waking our waker
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader] Dropping promise
[2020-04-23T20:38:27Z TRACE pinky_swear] [ProtocolHeader.Ok] Dropping promise
thread 'main' panicked at 'connection error: IOError(Os { code: 10057, kind: NotConnected, message: "A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supp
lied." })', examples\consumer.rs:13:20

Pushed a new more exhaustive version following up on the same approach

Heh, I didn’t actually mean to auto close this one. Can you confirm the problem is gone with beta 1?

@Keruspe ah, I thought you tested it successfully on another env that's running windows and that's why you closed it and I thought there's no more need to answer.
Yep I tested the same day you merged the extended commit and it was all good.
I just tested beta1 and its working fine both on my app and the example I quoted above.
Just one tiny thing that I saw:
[2020-04-25T18:28:07Z INFO  lapin::io_loop] Connected to xxx.xxx.xxx.xxx:5672
[2020-04-25T18:28:28Z ERROR lapin::channels] Connection error
thread 'main' panicked at 'connection error: IOError(Kind(ConnectionAborted))', examples\consumer.rs:13:20
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\examples\consumer.exe` (exit code: 101)

The success message is triggered too early, in fact its triggered when the connection hasn't been  established yet. Since crate previously wasn't declaring any logs on the info! macro and it was all up to the user to decide which information to log as info, I would suggest to remove the message.
Anyways, I'd like to thank you for all the great work, as I forgot to do it previously in the initial post. Keep it up!

authors: Dango-rs Keruspe

repo: sozu-proxy/lapin


text:
3.10.0 - Raid settings must be viewed prior to starting a raid

raid will refuse to start

Originally written by chomp

FIxed

Originally written by chomp

repo: sp-tarkov/server

license: NCSA


text:
Dead mobs can render below puddles

Hilarious

Should've been resolved by #17052

authors: Vordenburg metalgearsloth


text:
Dead people sometimes stand up

Dead people sometimes stand up and confuse everyone, they can still be stunbatoned or rekilled but they will still stand back up after a moment
Reported by @"Herbert Falsevor"#3037

I'm 99% certain that it was a player/admin rejuvenating themselves or stunned. Also without any steps to reproduce/concrete proofs like screenshots/videos this isn't very useful.

authors: AJCM-git PaulRitter


text:
YAML base files rename

Description
As discussed on the October 2nd meeting, we should rename all base.yml files to have descriptive names.
base.yml -> base_xyz.yml

Sign me up, I'll start it start of next week :)

Sign me up, I'll start it start of next week :)

You still doing this?

Sign me up, I'll start it start of next week :)

You still doing this?

Yeah will hop on this tomorrow. There weren't many examples I had found that didn't have a reasonable base ID but will go through all the entity bases.

I've just checked a large number of examples and they're currently a combination of xyzBase and BaseXyz and are fairly descriptive.
So just to be sure we're on the same page do we want to transition them all to the same format I.e Base_xyz.
For example "ClothingShoesBase" would become "Base_ClothingShoes" or is this really a non issue? Unless someone can point out an obvious non descriptive base.

@Peptide90 this issue is about YAML filenames, not prototype IDs

@Peptide90 this issue is about YAML filenames, not prototype IDs

My bad, fair enough should be a quick fix then. I'll take a quick look.

authors: Peptide90 SweptWasTaken Zumorica


text:
Interacting with lockers and other storage containers is not predicted.

Description
EntityStorage and all that needs made shared, pretty much.
Reproduction
Try opening a locker.
Additional context
Makes lockers feel jank on laggy connections.

@Macoron mentioned they had started ECSing entity storage in #5438. If most of the code is already being re-written anyways, its probably a good time to move a good chunk of it to shared?

it is now

authors: ElectroJr mirrorcult moonheart08


text:
Renamed planet floors

About the PR
Original Issue
Renamed all floor tiles in planet.yml.
I took some liberty with the desert tile names as I felt those names were more descriptive, and looked better in-game.
Let me know if I need to change them back to the original for any reason.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl: Nylux

tweak: Changed the name of planet-related tiles to be more readable.

arent those localized strings? they correspond to entries in ftl files

Oh I see what I've done.
So instead of renaming the global item name, which is meant to be what it was, i just need to rename the EN name for that item where you indicated right ?

yeah I forgot to put them under Resources/Locale

@metalgearsloth I WAS REVIEWING!!!!

authors: Cheackraze Nylux metalgearsloth moonheart08


text:
Rebalanced shields and reflective vest added to research

About the PR

This PR rebalances the existing shields, making them better against their respective damage type and worse against all others.
Especially raising the shield is buffed since you sacrifice your movement completely. I aimed at making it so while raised the shields would block around the same amount of bullets as when normally worn. Raised shields absorb 100% of the damage so raising your shield now makes the shield absorb twice as much damage in exchange for being unable to move.
For example 10 hits from a c20 using .35 auto  while walking around with the shield would break the shield and you will have taken 80 damage(if wearing no other armor) from the 10 bullets(16*0.5). When raising the shield it breaks after 12 .35 auto bullets with you having taken no damage at all, but in exchange you were an easy target for the person shooting at you.
Main Shield types:
Riot shield: Good against blunt and slash, weak against all others.
Riot bullet shield: Good against pierce, bad against all else
Riot laser shield: Good against heat and reflects lasers(50%) if it's in your active hand(so while shooting a gun it won't reflect), bad against all else.
It also rebalances the reflective vest making it's heat resistance the same as kevlar but adding a 40% reflect chance. The pierce armor also got a boost to 40% so that an officer with a reflective vest isn't just a civilian against normal guns. It's still quite a lot weaker than kevlar against pierce(see image below).
The images below contain the hits needed to break a certain shield with a few example weapons and the hits needed to crit a security officer wearing a reflective vest and helmet.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: Dygon

add: With the amount of weapons increasing Nanotrasen has started a research effort to protect their employees, advanced shield technology is now available as a tier 1 research. This research makes specialized protection gear available at the security techfab.
tweak: Changed the resistances of most shields, making them more effective against their specialized damage type but worse against other types.

I'm going to be honest, I think this will make shields worse. The riot shield was already the only shield used because the truth is 95% of the time you have no need to be prepared against one damage type in specific. I don't think I have ever seen the bullet or laser shield used for this reason, and doubling down on it while also making it WORSE against other damage types is only bound to kill them further. You then take the one shield that IS used because it has variety, and remove that variety while making it strong against two of the already easiest to counter damage types.

The reason the other shields aren't used is because they are not mapped in the armory(excapt bullet shield on kettle), they were also just basically a reskin of the normal riot one.

The reason the other shields aren't used is because they are not mapped in the armory(except bullet shield on kettle), they were also just basically a reskin of the normal riot one. The normal riot shield also becomes way stronger against threats security normally has to defend against in this PR(blunt and slash).

You realize that the Riot Bullet & Laser shield are available in the SecTech, right? Same with the riot shield. Nor are they a reskin of the riot shield- they take 80% of their respective damage types. If a security wanted to use them they can get them at the start of the round by going to vend most Sec use anyways- it's just that they're so laughably terrible nobody uses them.

Well currently the bullet shield is actually better against everything that the normal riot shield, needing 6 wielded baseball bat hits and 7 .35 bullets compared to the normal riot shields 5 wielded baseball hits and 6 .35 bullets. So even without my change the Bullet riot shield is just an upgrade of the normal one.

Well currently the bullet shield is actually better against everything than the normal riot shield.... my PR makes it so that it's not just a slightly better riot shield but actually an anti bullet shield.

That''s just not true. You say it's "better against everything" and then tested the two damage types that the bullet shield resists. It has 0 slash resistance and 0 heat resistance. The point isn't that the shields aren't good at what they do- it's that using a hand slot to have good resistances against some specific types inherently isn't that useful.

I do admit I was wrong on that one, I just randomly grabbed two weapons and didn't realize it was the damage type it was especially effective against before my pr. I still think that one bullet difference between the shields just makes having different types completely useless. This time I did test all types
riot shield: 7 laser shots, 6 .35 bullets, 5 wielded baseball bat hits, 9 combat knife hits.
bullet shield: 6 laser shots , 7 .35 bullets, 6 wielded baseball bat hits,  8 combat knife hits.
Laser Shield: 8 laser shots,  5 .35 bullets, 5 wielded baseball bat hits, 8 combat knife hits.
This is such a minor difference that It's completely logical that people aren't looking for any different shield than the normal one.

I do admit I was wrong on that one, I just randomly grabbed two weapons and didn't realize it was the damage type it was especially effective against before my pr. I still think that one bullet difference between the shields just makes having different types completely useless.

Yeah, I also went and tested it myself and realized that the difference is pretty minor, as well as misunderstanding some of the code. That said, I do think it's a good idea to keep the riot shield as a "general" option, and to keep the alternatives from being just blocking like, 2 hits from the other damage types. It seems like the laser shield now basically does a worse job of the niche the reflective vest fills (especially after this buffs it), and with the bullet shield, taking up a hand slot just to be better against bullets is really only helpful if you know there's nukies (and even then, you can barely reload a gun with it). Because of how weak they are against common damage types I don't forsee them ever really being carried still.

That said, I do think it's a good idea to keep the riot shield as a "general" option

The makeshift shield was my idea of the "general option" since it's almost as good as the current riot shield( 1 less bullet, 2 less laser hits, 1 less bat hit). I could tweak it's numbers a bit to make it the same as the current normal riot shield.

makeshift stuff aren't meant to be good, and it cost a full stack of steel

makeshift stuff aren't meant to be good, and it cost a full stack of steel

Well since it is the "general" option it won't be good at anything, just mediocre at everything compared to the specialized versions.

Riot shield should, at the very least, have a higher DT to Blunt. They should not be destructible with mere fists, or even baseball bats. IRL it withstands immense punishment and we have a space version of it.

Will review this week.

Laser Shields are Riot Shields but with way higher heat/laser resistance.

I'll implement the changes you suggested, since you only mentioned resistance should I remove the reflection from the security laser shields and buff their resistance?

I did some testing. Found a different PR introduced a bug where actively blocking destroys shields faster than passively blocking. Not your PR's fault but just a discovery.

It was intentional - active shield takes 100% of damage instead of 50% (but also has slightly better resistance).
Damage is split between user and shield.

It was intentional - active shield takes 100% of damage instead of 50% (but also has slightly better resistance). Damage is split between user and shield.

It was to simulate the shield getting hit twice as much since you're actively blocking the incoming fire right? Which would indeed make it logical to break twice as fast.
I think for balance reasons it's better to make it take the same amount of hits though since you become an unmoving target instead of a moving one.
The logic behind it maybe being you standing still allows you to better angle it to reflect some of the attacks instead of taking them straight on(could add a reflection to all shields if actively blocking instead of higher resistance to simulate this).

Bullet Shields are Riot Shields but with way higher brute/bullet resistance.
Laser Shields are Riot Shields but with way higher heat/laser resistance.

The reason why I made them weaker against the other damage types is because the descriptions said this:

So I assumed that was the direction they were meant to go in

It was intentional - active shield takes 100% of damage instead of 50% (but also has slightly better resistance).

While it may have been intentional for your PR, it's not intentional design for shields.
Intentional design for shields was always to eventually incorporate stamina damage for 100% blocking rate and the shields should be taking less damage while actively blocking.
I should've wrote a design doc for it but it was over a year ago.

So I assumed that was the way they were meant to be balanced, and the reason I started this PR since it's performance was different from the description.

It's how I write things sometimes, so that was on me for not writing what I was thinking explicitly.

Also currently on master items only reflect when in your active hand, I will make it so it also reflects if you wear the item in your inactive hand like you would with a shield if that's allright.

I (think) not reflecting while equipped but while the hand isn't active isn't intentional (see D-Swords). So I'll say yeah you have the go ahead to do that as long as it doesn't activate from storage.

I'll implement the changes you suggested, since you only mentioned resistance should I remove the reflection from the security laser shields and buff their resistance?

Maybe in this case make the other resistances just slightly lower. Just so it's not stupidly godtier.

Also currently on master items only reflect when in your active hand, I will make it so it also reflects if you wear the item in your inactive hand like you would with a shield if that's allright.

I (think) not reflecting while equipped but while the hand isn't active isn't intentional (see D-Swords). So I'll say yeah you have the go ahead to do that as long as it doesn't activate from storage.

@metalgearsloth made it intended

If #18186 gets merged I'll remove changed reflection code

If you merge master it should fix the tests.

Another merge conflict. Sorry, got super busy with real life. Merge master again and should be ok.

@Arendian are you coming back to this?

authors: AJCM-git Aisu9 Arendian LankLTE Myakot Slava0135 keronshb


text:
Biome niceties

Use floor variants for caves.
Add stalagmites to caves.
Use variants for existing biomes too ig.

:cl:

tweak: Tweak biome generation on planets to make floors more varied and add stalagmites to caves.

and need to add mushrooms)!

authors: Arteben metalgearsloth


text:
Solution precision fixes

See commits
:cl:

fix: Fix some rounding issues with complex chemical reactions.

OCD chemists rejoice!

Test failures real

test fail still real afaict

authors: IProduceWidgets PJB3005 metalgearsloth mirrorcult


text:
Adds witch robes

About the PR

Ports witch robes to game from /tg/ station (classic style)
Adds witch hat and witch robes to AutoDrobe

Why / Balance

Porting SS13 content is cool, and Marisa's witch robes are arguably a cultural touchstone worth bringing over.
Complements well with the shrine maiden costume.
Technical details

yaml changes

suits.yml
theater.yml

new RSI

witchrobe.rsi

attributed to /tg/

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame

Breaking changes

Changelog

:cl:

add: Added witch robes and witch hat to the AutoDrobe.

Test failed, looks like I have to increase the cost of the autodrobe crate, gimmie a second

ok it good now


text:
space law book

About the PR

Added space law book, which works like other guidebook books
Also added it to different places
reopened #22921
Why / Balance

Useful to have space law in-game
Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Space Law book added to the game.

I think the the Security 101 book has space law inside

I think the the Security 101 book has space law inside

where is this book located?

I think the the Security 101 book has space law inside

It opens the Security page of the guidebook.

no sprite for the book?

no sprite for the book?

its already exist

authors: Brandon-Huu K-Dynamic Moomoobeef Tayrtahn lzk228


text:
Hristov & .60 changes - Hristov Rework, Part 2

About the PR

This PR focuses on a few different changes to Hristov that are intended to rework the weapon into a formidable sniper rifle, including object penetration and damage changes. This is part 2 of a two-part Hristov rework; part 1 #31626 focuses on extending the gun's range.
This PR implements the following:

The Hristov is now a wield-to-fire weapon.
While being wielded, the wielder gets a 75% speed penalty.
The Hristov takes 2.5 seconds to chamber a round; this delay is also applied when first wielding it.
.60 Anti-Materiel bullets now deal:

75 Piercing Damage
150 Structural Damage
60 Stamina Damage

.60 Anti-Materiel bullets now have the ability to penetrate structures, up to a threshold of 360 damage.

The way this is calculated is that the bullet checks the damage required to break the entity it has hit, and if the bullet has dealt a combined damage under the threshold and the bullet damage itself is enough to break the object, it will continue.
If an entity is missing the ability to take Structural damage, the bullet will stop. This keeps the bullet from penetrating mobs (it's far too powerful for that).

Why / Balance

The Hristov rework is split up in two parts as they implement different features and it would be fairly overwhelming to do both at once. The two parts are also fairly disconnected from each other codewise, so it's easier to implement.
The combined changes in this PR turns the Hristov into a powerful sniper that requires planning to use optimally. The requirement to wield and the long chamber time keeps its DPS down, and it becomes a poor choice for a run-and-gun situation due to the extreme movement speed slowdown. To balance this out the damage rewards landing your shots, and the gun gives you unique tools to let you do that.
The anti-materiel bullets are tweaked such that they are able to penetrate weak structural objects like windows and grilles, but stop at walls. Since fights in groups in long hallways aren't uncommon and damage dealt by the bullets is high, they've been made to not penetrate mobs, making them more effective at single-target elimination. As an added bonus for any entrepreneuring sniper it also features heavy stamina damage; the 60 stamina damage of the first shot is enough to allow a brief moment of slowdown that the sniper is able to capitalize in for one shot, and if hit again the target will be knocked down. The damage is tweaked such that an officer or Captain is able to take 3 hits before being crit, while an unarmored target takes only 2. While the burst damage is strong, the slow reload causes a Time-To-Crit that is comparable to the high-tier lasers such as the laser cannon or advanced laser pistol.
Please consider these changes in the context of Part 1 of the Hristov Rework as well, since the extended range is key to utilizing the Hristov effectively.
For comparison, here is how the new Hristov (12 TC purchase) stacks up against the C20-r (20 TC purchase), the Viper (3 TC purchase) and the Python (8 TC purchase):

Technical details

There are two main components to this PR:
The first is the new property in ProjectileComponent, PenetrationThreshold, which is used in ProjectileSystem to determine if a bullet should penetrate an entity or not.
The second is the SpeedModifiedOnWieldComponent, which is used in WieldableSystem to set the movement speed slowdown.
Media

Youtube video link:

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: .60 anti-materiel bullets now deal a lot more damage and are able to penetrate weak structures.
tweak: Hristov now requires wielding to fire, and slows you down considerably.

so based

Wait c20 is 20tc since when

It isn’t, just checked

Wait c20 is 20tc since when

Oop, miswrote.

holy based

No rework .60 ammo?

Can we make AP .60 rounds which can penetrate whole station like Immovable Rod or like AP rounds in SS13. That AP bullet must be deleted only if hit Human.

authors: 7-62x54r Boaz1111 Everturning KaiserMaus SlamBamActionman UbaserB


text:
add security badges

About the PR

They're badges yo.
Why / Balance

Mostly RP? I have an idea to give officers ID numbers, which would go on this and their mk, but later.
Technical details

Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

add: Security officers now have badges!

I thought about making / upstreaming some sort of "pinning" mechanic so you can pin it to a jumpsuit or to a beret or something. Not sure if that's something we want though.

dunno, it looks weird, because as officer ID numbers they just have their ID cards...

icon sprites looks way way too big

these sprites are massive

please don't make it give sec a different speech bubble.

please don't make it give sec a different speech bubble.

yeah that would make sec abysmal.

that badge looks YUGE

please don't make it give sec a different speech bubble.

I'd say tie it to sec gas mask kinda like how in TG the mask makes you sound like a Half Life 2 combine soldier

please don't make it give sec a different speech bubble.

I'd say tie it to sec gas mask kinda like how in TG the mask makes you sound like a Half Life 2 combine soldier

My main issue with the speech bubble is honestly the way it looks. The red and blue that is used right now just does not look good. If sec were to really have a speech bubble, I believe it should use just the sec colors (red and black) and have some sort of unique design, like the moth and reptilian speech bubbles.

Sprites are too big on the ground. No speech bubble. Everything else is cool but make it so they are tied to something like loadout time requirements or the Head of Security handing them out.


text:
Stop mobs spawning inside the off-limits trade station room

About the PR

Adds a marker to prevent events from spawning mobs near them.

Oh~ I also grayscaled markers because weh.
Why / Balance

Some places shouldn't get random mobs, its not fun.
Technical details

I just search for a dummy comp near the spawn coords. Its probably a little bigger than it needs to be, but I honestly don't think it will matter.
Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

no cl no fun

Could we add the markers to the rest of the ATS too
Not that I don't want slimes or spiders to spawn there, the main problem is the dragon can sometimes spawn there and get stuck.

Dragon spawns in space, so this wont help with that.

This is just areas, just make them only spawn on station grid instead.

They already do that, the ATS is a stationmember because cargo / bank account. I 'want to exclude all members what if multi-part station?

change station grids to be actual parts of the station and grids it owns, have bank etc check owned grids and have events spawn on actual grid(s)

authors: IProduceWidgets deltanedas