text:
Autocomplete: Fix 26 year rate limit bug

The warning message when you exceed the rate limit is wrong

pic for ref:

🤔

authors: abeatrix philipp-spiess

repo: sourcegraph/cody


text:
bug: Document code command bad diff when using Azure OpenAI

Version
v1.2.3
Describe the bug
When using the document code command when connected to Azure OpenAI the entire function is being duplicated in addition to the code getting added
Expected behavior
The only diff should be the new documentation added
Additional context
Below is a screenshot of the diff, this occurred both when highlighting the entire function or placing the cursor on the command name and triggering the document command.

@taylorsperry it would be good if we could prioritize this for Feb release as Azure is a common choice for enterprise customers.

@chwarwick Enterprise customers have to opt in to use Azure OpenAI right? Is the default Claude?
I think this is happening because Edit currently defaults the custom model to use chatModel. I can add an editModel option that they would need to set instead

@chwarwick Can you provide some reproduction sets as to what I need to add to site configuration to replicate this?
We should only ever use anthropic/claude-2.0 for doc/fix/test commands, so I wouldn't expect to see OpenAI being used for this

@chwarwick Can you provide some reproduction sets as to what I need to add to site configuration to replicate this?
We should only ever use anthropic/claude-2.0 for doc/fix/test commands, so I wouldn't expect to see OpenAI being used for this

@umpox  I can help configure an Azure OpenAI env for you.  Not all enterprise customers use or allow anthropic models, Azure OpenAI has been a common choice for several enterprises due wanting to run everything within their own environment.

@umpox  I think the difference is that not all enterprise customers use the Cody Gateway, and are commonly using things like AWS Bedrock (anthropic models) or Azure OpenAI (openai models).  We can no longer have commands that only work with specific models.

source: gharchive/issue

authors: chwarwick umpox

license_type: permissive

license_source: github-api


text:
add OpenCtx context mention provider

Allows any OpenCtx provider to be used as a ContextMentionProvider to provide @-mentionable context.
For example, the Google Docs OpenCtx provider makes it possible to @-mention Google Docs.
This lets us add more context providers without committing them to the cody repo. We can even add them by external HTTP URLs if there is some service that implements the HTTP OpenCtx API.
Test plan
CI

@sqs Is the gdocs provider the only provider that works with this feature? I tried the hello world and link provider from the openctx.org docs but I'm not seeing @octx complete anything in chat.

I followed the docs here and I'm still not getting @octx to work in chat https://sourcegraph.com/github.com/sourcegraph/openctx@8b11111e9fccb207828b9b8ec5217a44acaa108d/-/blob/provider/google-docs/README.md

Installed the OpenCtx extension
Added settings

    "https://openctx.org/npm/@openctx/provider-google-docs": {
      "googleOAuthCredentialsFile": "/Users/olafurpg/dev/client_secret_888411641236-8bg8o02lt1fn8vccihfdlp3q0ej8eucl.apps.googleusercontent.com.credentials.json",
      "googleOAuthClientFile": "/Users/olafurpg/dev/client_secret_888411641236-8bg8o02lt1fn8vccihfdlp3q0ej8eucl.apps.googleusercontent.com.json"
    }

Enabled debug logging, see the following error for gdoc provider

[providerClient(https://openctx.org/npm/@openctx/provider-google-docs)]: failed to get provider capabilities: Error: Cannot find module '/v135/node_fs.js'

When building the Cody extension locally, I see this warning that might be relevant
[0] ✘ [ERROR] No matching export in "../lib/shared/dist/index.js" for import "setOpenCtxExtensionAPI"
[0]
[0]     src/context/openctx.ts:1:35:
[0]       1 │ ...OpenCtxExtensionAPI, setOpenCtxExtensionAPI } from '@sourcegraph...
[0]         ╵                         ~~~~~~~~~~~~~~~~~~~~~~

@olafurpg Thanks!
It looks like adding the gdocs provider via https://openctx.org/npm/@openctx/provider-google-docs is broken because it uses node's fs and the on-the-fly bundler that is used (https://esm.sh) shims node fs in a way that breaks. I got it working when I pointed it to the gdocs provider on the file system, but I'll look into this.
I also just made it so the hello world provider works for at-mentions:

This just requires the following VS Code settings:
"openctx.providers": {
    "https://openctx.org/npm/@openctx/provider-hello-world": true,
}

I'm on d7baa7a0fcbe740c5e08ebd26468af6d6f944957, configured the hello world provider
  "openctx.providers": {
    "https://openctx.org/npm/@openctx/provider-hello-world": true
  },

I'm still still not getting @octx to work 🤔

OK, 2 other (undocumented) things to check:

VS Code setting cody.experimental.noodle set to true
On the prerelease version of the OpenCtx extension

@sqs I enabled the noodle setting and installed the latest pre-release v0.3.1714489462 but it's still not working for me. I also tried 0.2.5, which is a more recent release.

OK strange. I will try on my Mac in the morning and will see if it works there and on some other people's machines.

@olafurpg It works for me on macOS on 2 separate devices. I am going to merge this and then we can troubleshoot sometime.

source: gharchive/pull-request

authors: olafurpg sqs


text:
Remove noodle flag set to true for Cody Web

context: https://linear.app/sourcegraph/issue/SRCH-821/context-is-not-being-fetched-on-vs-code-even-though-its-being-fetched
https://sourcegraph.slack.com/archives/C05D629GWJK/p1722933166623269?thread_ts=1722620916.715349&cid=C05D629GWJK
The experimental.noodle flag is enabled by default for Cody Web which should not be the case. Some experimental feature like chat query rewrite are therefore enabled right now.
This PR sets the experimental.noodle flag to false.
Test plan

cd web
pnpm dev
Submit a chat message in chat and monitor the network request to getCodyChat to make sure the query string is the chat message without the mention chips text.

Changelog

Vova mentioned this in the Slack thread:

Reason: at the beginning noodle project had some features like remote file mentions I think that we wanted to have in Cody Web too, that’s why it’s true.

Is that no longer relevant?

As far as I can see, mentioning files work right now with the flag off.


text:
Missing Errors() []error if used Go 1.20

Ok, my bad, now it's Unwrap() []error.
IMO it should be noted somewhere, that the behavior of the library varies based on the version of used Go.
It can cause backward incompatibility to some.
Old text:
The errors.Join() feature in Go 1.20 is nice, but it's not possible to split the errors back to slice of errors.
With Uber implementation, that's under build tag for Go 1.19, it is possible

@camdencheek thoughts?

authors: jdorfman prochac

repo: sourcegraph/conc

license: MIT


text:
Get error of "Header must provide a Content-Length property" and then go language server shut down.

I am working on the integration of a editor and go language server. In rare cases, I can see error "Header must provide a Content-Length property" and then go language server shut down.
I saw in the output of go language server, its response is malformed like below, which causes the client side cannot parse the response correctly.

The error above is from gocode and the "invalid memory address or nil pointer dereference" it refers to is in function fixup_packages. In the first if statement, pcache[path] is nil, but it tries to access its defalias.
func fixup_packages(filescope *scope, pkgs []package_import, pcache package_cache) {
	for _, p := range pkgs {
		path, alias := p.abspath, p.alias
		if alias == "" {
			alias = pcache[path].defalias
		}
		// skip packages that will be merged to the package scope
		if alias == "." {
			continue
		}
		filescope.replace_decl(alias, pcache[path].main)
	}
}

One thing I found is in gocode, if something gets wrong,  sometimes print_backtrace(err) is called to write panic and related information to standard output, which may pollutes the response.
Related file: https://github.com/nsf/gocode/blob/416643789f088aa5077f667cecde7f966131f6be/autocompletecontext.go
https://github.com/nsf/gocode/blob/d09cef6327ed848a446636a857cd851dc7e63d19/utils.go#L184
It is not easy for me to reproduce this problem which makes debugging difficult. If you have more knowledge of gocode and go language server, could you please let me know if my guess is correct.

Nice catch with both the upstream issue in gocode and it printing to stderr. We actually need to switch to https://github.com/mdempsky/gocode anyways. We probably need to work out a way to more cleanly integrate gocode as it is. Right now it is manually vendored in and modified, and as such it makes it harder to integrate upstream changes.

Thanks for the reply. I think the gocode write error directly into stdout instead of stderr, it uses fmt.Printf to write errors and the response write to stdout also.

authors: dianedanlai keegancsmith

repo: sourcegraph/go-langserver

license: mit

license_source: bigquery


text:
JetBrains: Alt+\ is not triggering autocompletion, instead opening File menu

IDE Information
PyCharm 2023.3.4 (Community Edition)
Build #PC-233.14475.56, built on February 26, 2024
Runtime version: 17.0.10+1-b1087.17 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Registry:
ide.experimental.ui=true
Non-Bundled Plugins:
com.sourcegraph.jetbrains (6.0.10-nightly)
Bug Description
Platform: Windows
Steps to reproduce:

Have Cody plugin installed in your JB IntelliJ editor
Login to Cody with a Pro account
Open any source code and start coding
Hit Alt + \ to trigger Cody autocomplete

Observed behavior:
Cody autocomplete will not be triggered and instead file menu opened.
Expected behavior:
Cody autocomplete should be triggered correctly.
Additional context
Video link:
https://drive.google.com/file/d/1-qkBah4X1r--AsMVzkGVPxsJKtJwJkLr/view?usp=drive_link

Works fine on my macOS machine. I have no access to anything running Windows. Can someone else check this one? 🙏

@mkondratek I am on macOS with PyCharm and the option + \ seems broken. It prints « character instead of triggering autocomplete.
cc @taylorsperry @kalanchan It was working with earlier releases.

i believe we fixed this, please re-file if it's still a problem

authors: jay-fibi kalanchan mkondratek

repo: sourcegraph/jetbrains


text:
use vendored deps when building inside docker

@keegancsmith I noticed in the course of trying to debug something that involved a dep in our vendor folder, that my changes weren't reflected when I built the image.
I think that we need to make the changes in this PR in order to actually use the vendored deps when building the binary?

@ggilmore I pushed some changes, including some general org changes. Take a look, and if you are happy merge away :)

authors: ggilmore keegancsmith

repo: sourcegraph/lsp-adapter


text:
Add OFP as a git submodule

See #119 as well.
I have updated the git setup/config scripts to help ease working with
submodules. I suggest re-running the git setup developer script.
Submodules are a somewhat complicated beast, but I really think for our usage,
pulling in OFP via submodule sounds like the best route. If we change our minds
once we start hacking with OFP, we'll be able to investigate other alternative
integration strategies. (Subtree merge, committing code directly, scripted external
dependency, etc.)
To begin reading up: https://git-scm.com/book/en/v2/Git-Tools-Submodules

No idea why pull approve thinks this has been approved...

Current coverage is 39.12%

Merging #127 into master will not affect coverage as of 84f8a01

@@            master    #127   diff @@
======================================
  Files            2       2
  Stmts          892     892
  Branches         0       0
  Methods          0       0
======================================
  Hit            349     349
  Partial          0       0
  Missed         543     543

Review entire Coverage Diff as of 84f8a01

Uncovered Suggestions

+1.92% via src/mpi/mpi_caf.c#1903...1919
+1.58% via src/mpi/mpi_caf.c#2001...2014
+1.58% via src/mpi/mpi_caf.c#1557...1570
See 7 more...

Powered by Codecov. Updated on successful CI builds.

LGTM! #shipit

authors: codecov-io zbeekman

repo: sourceryinstitute/opencoarrays


text:
setting owner and group to non-root makes golang::packages fail

golang::packages tries to cache the package in the chef client cache directory, which is only writable by root:
      Recipe: golang::packages
         * golang_package[github.com/etsy/hound/cmds/...] action install
           * bash[Installing package github.com/etsy/hound/cmds/...] action run

             ================================================================================
             Error executing action `run` on resource 'bash[Installing package github.com/etsy/hound/cmds/...]'
             ================================================================================

             Mixlib::ShellOut::ShellCommandFailed
             ------------------------------------
             Expected process to exit with [0], but received '141'
             ---- Begin output of "bash"  "/tmp/chef-script20160620-579-420w5l" ----
             STDOUT:
             STDERR: /tmp/chef-script20160620-579-420w5l: line 1: /tmp/kitchen/cache/github.com-etsy-hound-cmds-...: Permission denied
             ---- End output of "bash"  "/tmp/chef-script20160620-579-420w5l" ----
             Ran "bash"  "/tmp/chef-script20160620-579-420w5l" returned 141

             Cookbook Trace:
             ---------------
             /tmp/kitchen/cache/cookbooks/golang/providers/package.rb:14:in `block in class_from_file'

             Resource Declaration:
             ---------------------
             # In /tmp/kitchen/cache/cookbooks/golang/providers/package.rb

        5:   bash "Installing package #{new_resource.name}" do
        6:     code "#{node['go']['install_dir']}/go/bin/go get -v #{new_resource.name} 2> >(grep -v '(download)$' > #{tmp_file_path})"
....

The cache file needs to be created with the correct ownership.

the fix was merged 4 years ago

repo: sous-chefs/golang


text:
Standardise files with files in sous-chefs/repo-management

Signed-off-by: Dan Webb dan.webb@damacus.io

Released as: 4.0.4

authors: damacus kitchen-porter

repo: sous-chefs/nrpe


text:
[09.message-routing] Unify structure of 'readme.md'

Proposed Changes
Unify the structure of readme.md across the differente languages in sample 09.message-routing.
Testing
The behaviour of the code was not modified.

No longer needed

No longer needed

repo: southworkscom/BotBuilder-Samples


text:
🛑 Media is down

In 60a440d, Media ($SITE_1) was down:

HTTP code: 403
Response time: 97 ms

Resolved: Media is back up in b0e469d.

repo: soxfor/upptime


text:
Background cache reloading

Added ability to url-data & category lookup table cache to
deliver data from cache while reloading new data in the background.
This leads to faster response time as the relevant data is either
already prefetched by a previous request or will be for the next
request.

I won't be in my office till July 22.
You are welcome to contact my representative: thomas.mann@framefield.com
with kind regards,
Rainer

authors: mutaphysis nero-still

repo: sozialhelden/wheelmap-react-frontend


text:
Точно обновление не трупа... Outpost

Описание PR

Думайте будет шутка? Нет, я не придумал...
Медиа

Играйте сами :(
Проверки

[x] PR полностью завершён и мне не нужна помощь чтобы его закончить.
[x] Я внимательно просмотрел все свои изменения и багов в них не нашёл.
[x] Я запускал локальный сервер со своими изменениями и всё протестировал.
[ x ] Я добавил скриншот/видео демонстрации PR в игре, или этот PR этого не требует.

Изменения

:cl: SonicHDC

add: Добавлено пробитие в пещерах!
add: Теперь вы можете вызвать отряд ОБР, кнопки ищите сами!
fix: Атмос теперь прикрыт стеной!
tweak: Теперь инженеры используют радиоактивную энергию!
tweak: Небольшой монтаж командного блока!
tweak: Шпаклёвка стен химии!

:)


text:
Relay input entities are wrong

Code cleanup casualty, it's passing in the entity itself and not the relay entity.
@Plykiya

can do

authors: Plykiya metalgearsloth


text:
Deleting the gravity generator doesn't disable gravity

Description

Delete the gravity generator with the entity spawner eraser
Gravity will remain on

It looks to me like the Gravity System doesn't actively check for Gravity Generators and no events get emitted when the Gravity Generator gets destroyed.

gravity generator system should hook into when the component is deleted and disable gravity on the grid accordingly

authors: AJCM-git mirrorcult thevinter


text:
Rewrite access component + ID Computer UI

Description
So access component needs to support:

[x] Hidden access levels that don't show on the ID card (for antags).
[ ] An all access flag for captain and centcom (to reduce duplicated access tags).
[ ] Rework ID console to have nicer segreagation?

And from other issues:

[ ] Support being written to an airlock board when hit with an ID #5353, similarly for private crates.
[ ] Support per station access #5683

Related:
Change AccessReader to use bitmasks for faster AI pathfinding #3595

not super actionable + mostly done

authors: Peptide90 ShadowCommander mirrorcult


text:
Adds damage on tool interaction component (#1060)

Goal:
Addressing #1060. Make the fuel tank explode if ignited with a welding tool.
Implementation:
Created a new component -> DamageOnToolInteract.
When interacted with tool checks to see if interacted with a valid tool:
yes -> check for damageable component
    yes -> apply damage using takedamage function.
    no -> check if damage exceeds 0:
        yes -> call HandleDestruction system on Owner. (fallback)

Result:
fuel tank explodes if ignited with a welding tool. You can still fuel welder if the welder is turned off.

Supports:

[x] All Tools supported
[x] Multiple Tools causing damage to one entity
[x] Fallback if no damage system is in place

Why this method?
the component system isn’t designed for a single use case solutions. It is designed to be reused. Instead of creating a component with specific implementation in mind I created a more flexible component that adds damage when interacted with a tool and then lets other components handle events relating to that damage, such as an explosion on death.

Nice first PR!
@Zumorica is more familiar with the tool code and exactly how to use it correctly, so I won't comment on that stuff.

Hmm, I wonder if this is the best way to go about this. Having to add the DamageOnToolInteract component to every single entity that can be damaged by tools doesn't seem like a good idea. Then again, I understand that this is probably the most straightforward way to go about it. Maybe this component could be merged with DamageableComponent instead?

Hmm, I wonder if this is the best way to go about this. Having to add the DamageOnToolInteract component to every single entity that can be damaged by tools doesn't seem like a good idea. Then again, I understand that this is probably the most straightforward way to go about it. Maybe this component could be merged with DamageableComponent instead?

I considered making this a child of Damageable Component because I felt like using a tool to do damage to something was more of an outlier case that shouldn't be automatically added to every Component which requires Damageable. From my understanding the Welder doing damage to a fuel tank is the only example of tool damage from the original game.
The reason why I didn't was because I felt like the child solution would create more issues then its worth and people would likely add both a Damageable Component and a DamageOnToolInteract Component to every class anyway and I assumed that might cause some issues as both classes handle damage together.
However I could definetly see this merged into Damagable Class some time in the future. Especially if its expanded upon to include all acts of use rather then just tools. A DamageOnUse function is better system to add to the Damageable Class IMO.

authors: ComicIronic Jackw2As Zumorica


text:
Moves head's fluff items out of lockers into dressers

About the PR

Moves head's fluff items out of lockers into dressers

Why / Balance
I tossed this idea out in Ideadudes and didn't receive any feedback but it did garner a couple 's. So, I went ahead and just did it.
My main thoughts were:
Pros: Reduces contents in lockers, Dressers make bedrooms cozy, Allows for more fluff items in the future or downstreams w/out further overfilling lockers
Cons: Not every head has a bedroom on every map maybe, Bedrooms are often tight spaces that might not already have a dresser mapped in or space for one.
Technical details
With this change, there are still at least a couple slots left in the lockers for future content. But, when using gridventory, if a bunch more content is added, dresser space may need to be increased. Not really an issue at the moment though.
Media

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

Breaking changes
n/a
Changelog
:cl: Velcroboy

tweak: Moved head clothing items out of their lockers and into their dressers.

I like this idea, also seeing all the clothes in a grid-inv is cool.

I like this idea, also seeing all the clothes in a grid-inv is cool.

Yeah, here, some example screens of what that looks like:

this is pretty based

authors: DogZeroX IamVelcroboy UbaserB


text:
fix fire spread round removal

About the PR
fixes #27983
Why / Balance
instantly gaining 1m firestacks is bad
Technical details

removed copy paste shitcode that used 2 different methods of calculating spread
comment is better
the spreading code now uses bounds checking so its not possible to get trolled ever again

Media
https://github.com/space-wizards/space-station-14/assets/39013340/27dc547b-94f7-4f03-8cd9-0bd23950e60c
forced 10 firestack mouse doesnt crit a urist when in contact for a few seconds
~4 firestack urist instantly puts mice to 10 firestacks because of mass difference

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

Breaking changes
no
Changelog
:cl:

fix: Fixed fire spreading being insane.

o7 gamer

authors: UnicornOnLSD deltanedas


text:
Ichor Now Clots Blood

About the PR

Makes Ichor clot blood like Tranexamic Acid.
Why / Balance

More of a QOL for dragons; it gets that little red bleed symbol to vanish and allows the dragon to not worry about losing health when out of combat. Healing wise It would not affect the dragon in any significant way. Due to the dragon's fast metabolism, devouring right before you go into combat should not prevent bleed stacks from changing the fight.
Technical details

Adds ModifyBleedAmount effect to Ichor.
Media

https://github.com/space-wizards/space-station-14/assets/83733158/cd760c64-87e6-4966-be7a-754887154b33

[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: Devouring bodies now reduces bleed for Space Dragons.

Makes sense. Thanks for the contribution.

authors: Cojoke-dot slarticodefast


text:
Add missing LV cables in Omega atmos

About the PR
Adds missing LV cables in atmos burn chambers that leave light and scrubber unpowered. Also replaces left salvage ore refinery windoor with a cargo locked variant.
Why / Balance
Needed and helpful.
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.

Changelog
No CL

Wish I had noticed this before my earlier PR today, whoops


text:
Fix: Radio jammer now doesn't show setting changes to other players

About the PR

Title! Before the jammer used PopupPredicted which showed the change to anyone nearby. I changed it to PopupClient so only the client actually changing the settings gets the popup.
I did test this but I can't record and have two clients open at once 😔

Thanks for the fix.
While testing I found another, unrelated bug: The popup will only show up if the jammer is turned on.
Just in case you want to fix that one as well 😄

Looks like that was because the check is only for updating it if the jammer is currently on! I just took off the if statement so it has the popup if its on or off.

we really need a github action for merging hotfixes to make this easier

authors: beck-thompson slarticodefast


text:
Atmos sign

Atmos sign
changelog
-atmos sign

(atmo sign)

I think the license you are listing is incorrect. It looks like it's duel licensed under GPL3, and AGPL3. I think GPL3 is the less restrictive of the two, so you could list that as the license.
For the links, the Beestation github looks like the more official source, so just a link to that commit should work.
https://github.com/discordia-space/CEV-Eris/tree/4e0bbe682d0a00192d24708fdb7031008aa03f18
https://github.com/BeeStation/BeeStation-Hornet/tree/13dd5ac712385642574138f6d7b30eea7c2fab9c
I'm not a lawyer, so I might be wrong, but best effort.

bee is a tg downstream which uses CC for its licenses
"All assets including icons and sound are under a Creative Commons 3.0 BY-SA license unless otherwise indicated." in their readme

Then the link should be to wherever that is

it is, thats in the beestation readme

im confused as to what i need to change here

nothing, your meta is fine

Yeah, don't worry about it.

authors: Emisse mirrorcult wrexbe


text:
BUG？？ finished streaming call with code Unknown

Description

2024-01-12T22:16:19.360Z	ERROR	grpc	finished streaming call with code Unknown	{"module": "grpc", "grpc.start_time": "2024-01-12T19:00:17Z", "system": "grpc", "span.kind": "server", "grpc.service": "spacemesh.v1.PostService", "grpc.method": "Register", "peer.address": "127.0.0.1:35610", "error": "context canceled", "grpc.code": "Unknown", "grpc.time_ms": 11761421}
2024-01-12T22:16:19.360Z	INFO	[2024-01-12T22:16:19Z INFO  post_service::client] disconnected: Err(status: Unknown, message: "transport error", details: [], metadata: MetadataMap { headers: {} }
2024-01-12T22:16:19.360Z	INFO
2024-01-12T22:16:19.360Z	INFO	    Caused by:
2024-01-12T22:16:19.360Z	INFO	       0: transport error
2024-01-12T22:16:19.360Z	INFO	       1: connection error: stream closed because of a broken pipe
2024-01-12T22:16:19.360Z	INFO	       2: stream closed because of a broken pipe
2024-01-12T22:16:19.360Z	INFO
2024-01-12T22:16:19.360Z	INFO	    Location:
2024-01-12T22:16:19.360Z	INFO	        /home/runner/work/post-rs/post-rs/service/src/client.rs:142:24)
Steps to reproduce
Environment
Please complete the following information:

OS:
Ubuntu22.04
Node Version:
go-spacemesh:v1.3.2

It is not a bug. It's post-service being disconnected from a node. All is ok. it will self-reconnect afterwards but yes I agree the logging should be better cc @fasmat

the message comes directly from the post service. Maybe we just don't print anything when the post service disconnects and successfully reconnects @poszu

ok，thanks

the message comes directly from the post service. Maybe we just don't print anything when the post service disconnects and successfully reconnects @poszu

@fasmat The ERROR log message comes from the GRPC logging middleware on go-spacemesh side. The following INFO logs are from the post-service side. I could change it to log at info that it disconnected and log the error details on debug level. What do you think?

authors: bugxzhu fasmat pigmej poszu

repo: spacemeshos/go-spacemesh


text:
cleanup makefile

Motivation
Old zombie code in makefile causes confusion.
Changes
Remove old, non-functional versions of make commands. Remove -elk/_ELK suffix from make commands and env variables.
Non-code changes:

set_gcloud_service_account_cred in 1Password has been updated with a backwards compatible version (works with code in this PR and before this PR). In this file the env vars CLUSTER_NAME and CLUSTER_ZONE have been updated to have the same values as CLUSTER_NAME_ELK and CLUSTER_ZONE_ELK, respectively.
The same (backwards compatible) change has been applied to the secrets in Github Actions.

Test Plan
Use existing tests and ensure everything still works.
TODO

[ ] After this has been merged to develop and other PRs have rebased, we should replace set_gcloud_service_account_cred in 1Password with a cleaner version that isn't backwards compatible: remove CLUSTER_NAME_ELK, CLUSTER_ZONE_ELK and ES_PASSWD.
[ ] Do the same to the secrets in Github Actions.

DevOps Notes

[ ] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
It does in CI. See above.
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors try

bors try

bors merge


text:
prune active set from ballot blob

Motivation
Closes #4985
Changes

actually prune active set from ballot blobs in db
use a empty migration to facilitate the pruning.
we only want to prune/vacuum/checkpoint once per software upgrade
the code allow any upgrade from migration <=4 to 5 to

extract active set from ballots
prune active set from blob
vacuum and checkpoint

the final size of the state should be < 1GB

bors merge

bors cancel

bors merge


text:
Clear the saved jwt token (admin login) upon signature mismatch

Issue
Redeploying space-cloud on same domain causes signature mismatch issue upon login due to the previously saved jwt token in local storage (with a different password/secret)
Temp Fix
Clear the old jwt token from local storage manually
Solution
Clear the saved jwt token from local storage via front-end upon signature mismatch error

Just to confirm, @s-kris you are running space-cloud without the --dev flag right?

@YourTechBud correct, without --dev flag.

Apart from clearing the JWT token on signature mismatch, I think the Mission Control should also redirect to the login page right? @s-kris

@Jayesh333 Yes! I saw that #340 is already in progress, you should be able to bind the functionality.

Done. Coming in v0.16.0. Thanks @s-kris for bringing this up!

authors: Jayesh333 YourTechBud s-kris

repo: spaceuptech/space-cloud


text:
Fixes and cancelled/failed states

@spadgett

@fabianofranz thanks, might conflict with @sg00dwin's change. holding off merging for the moment

@spadgett ok

Sorry @fabianofranz conflicts now. Can you rebase?

authors: fabianofranz spadgett

repo: spadgett/origin-web-console


text:
Seeds parameter

Looks like is_seed parameter needed, not on RichPlant level, but on Plant level, to filter list before enrichment.

8b23c449317b0d64c238c5edcb9ada0a6d73d69d
25ae96d838a04daa179d49af3f9bc057552b87bb
059c29eb66d27f65b4897a6931407d30cfd5da19
1c323b43f2c9750b7968ee39e95d635f6bfb69e3
a94a5749a3121fab7f7768d88248e86044deea96

repo: spalk/Plant-Passport-gitpod


text:
Add "mirror" renderer option

Similar to "reverse", but instead of inverting the progress, it will simply reverse the RGB values in each rendered frame of the effect, creating a mirror image.

Not planning on doing this any more, may revisit in the future.

repo: sparkled/sparkled


text:
Please release sqlite3 binary gem for Ruby-2.4 !

Now, that RubyInstaller-2.4 is released, every rails newbie stumbles across the sqlite3 gem, which doesn't contain a ruby-2.4 binary so far. Although it's not too complicated to install the source gem, the error messages are confusing for many users and it requires some additional steps.
So my solicitation is to merge https://github.com/sparklemotion/sqlite3-ruby/pull/214 and release a new version (per rake gem:windows). Thank you!

@tenderlove , @luislavena The non working sqlite gem is currently the only blocker to make RubyInstaller version 2.4 a general recommendation for new users. Could you please publish a new release?
Can I help maintaining this library? I already maintain a database gem ...

I just noticed, that the latest sqlite3 gem has ruby 2.4 inside and it works fine on RubyInstaller-2.4. So the only issue here is that the gem dependencies needs to be updated... Sorry for the noise!


text:
update package-lock and package.json and added docker change to remov…

…e package-lock so dependencies can update in the container
Description
This PR resolves an issue with npm where git-url packages are locked by their first commit-hash, where subsequent commits to the branch will not trigger an update to the code unless package-lock and node_modules are removed.
To work around this, we remove package-lock.json before copying files into a final container in docker. This provides the environment that will allow the dependency to update inside the container and the changes to be viewed.
WARNING: This means that lnd-engine will be a dynamic dependency
Related PRs
Related issue: https://github.com/npm/npm/issues/17028
Todos

[n/a] Tests
[n/a] Documentation
[x] Link to Trello

 lnd-engine not updating in docker container

repo: sparkswap/broker


text:
Black screen / Flickering issues - Fedora Linux

Sparrow 1.7.6
This happens constantly, and Sparrow is unusable. This never happened with previous versions of Fedora Linux.

OS: Fedora Linux (38)
Windowing System: Wayland
Kernel Version: Linux 6.2.15-300.fc38.x86_64

Try running with
_JAVA_OPTIONS=-Dprism.order=sw /opt/sparrow/bin/Sparrow

Some systems have hardware acceleration bugs - this uses a software pipeline.

Thanks for updating, but as a Nvidia driver bug I'm going to close this here.

authors: Roninpus craigraw

repo: sparrowwallet/sparrow


text:
testing failure on python3.8

our CI tests fail on 3.8 because a dependency conflict causes the conda solver to churn forever. Nothing in our dependencies suggests an obvious potential conflict with 3.8--except region.
Looking a bit closer at region's reqs, it specifies sklearn instead of scikit-learn, which is a deprecated alias. I'm guessing that's the culprit. I'm not sure the best way to resolve this. We're not planning to release spopt for awhile, and we've decided not to do any more releases of region (though this would be a very quick and easy change). What do you think @sjsrey?

I think a quick bug fix type release of region makes sense in this case.

if you try to install region in an empty 3.8 envirionment you get
test38 ❯ conda install region
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions
Note that strict channel priority may have removed packages required for satisfiability.

so i'm fairly confident this is the root of the problem

this happens on tobler too, so now i'm not so sure about the root cause...

Seems to be several dependency conflicts:
1880    Package pytest conflicts for:
1881    pytest-cov -> pytest[version='>=3.6|>=4.6']
1882    pytest-mpl -> pytest
1883    pytest
1884
1885    Package rasterio conflicts for:
1886    rasterstats -> rasterio[version='>=0.27']
1887    rasterio
1888
1889    Package importlib-metadata conflicts for:
1890    pytest -> importlib_metadata[version='>=0.12'] -> importlib-metadata[version='>=1.1.3,<1.1.4.0a0|>=1.5.0,<1.5.1.0a0|>=1.5.2,<1.5.3.0a0|>=1.6.0,<1.6.1.0a0|>=1.6.1,<1.6.2.0a0|>=1.7.0,<1.7.1.0a0']
1891    twine -> importlib_metadata -> importlib-metadata[version='>=1.1.3,<1.1.4.0a0|>=1.5.0,<1.5.1.0a0|>=1.5.2,<1.5.3.0a0|>=1.6.0,<1.6.1.0a0|>=1.6.1,<1.6.2.0a0|>=1.7.0,<1.7.1.0a0']
1892
1893    Package zope conflicts for:
1894    pytest -> attrs[version='>=17.2.0'] -> zope
1895    rasterio -> attrs -> zope
1896
1897    Package boto3 conflicts for:
1898    rasterio -> boto3[version='>=1.2.4']
1899    quilt3 -> boto3[version='>=1.10.0|>=1.8.0']
1900    rasterstats -> rasterio[version='>=0.27'] -> boto3[version='>=1.2.4']

seems like it may be quilt

also seems to be conda-specific, because i dont have conflicts with pip

https://github.com/pysal/tobler/pull/78

the quilt issue was solved thanks to some fantastic help from @marcelotrevisani. Now the blocker seems to be pulp, and it looks like that's a known issue

resolved thanks to some fantastic help from @marcelotrevisani

authors: jGaboardi knaaptime sjsrey

repo: spatialucr/geosnap


text:
Compatibility with Laravel 5.4

Hey there!
I'm trying to set this up with a fresh Laravel 5.4 (latest dev as of today) project, but unfortunately it seems to be creating a Fatal Error after adding the package to my service provider:
  Call to undefined method Illuminate\Foundation\Application::share()

Detailed stacktrace:
https://cl.ly/2U2D1s2O2v1A
Any ideas?
Cheers! :)

Hi,
I've just tagged a version that should be compatible with Laravel 5.4
Run composer update to fix the problem.

Amazing, thanks for the super quick turnaround @freekmurze! 👍
Unfortunately even with 1.1.4 I am getting a different error now:
[ErrorException]
  Illegal offset type in unset

Detailed stacktrace: https://cl.ly/0109383S0X0e

Damn, sucks :)
I'll take a look at this tomorrow.
On Fri, 20 Jan 2017 at 00:09, Joey Kudish notifications@github.com wrote:

Amazing, thanks for the super quick turnaround @freekmurze
https://github.com/freekmurze! 👍
Unfortunately even with 1.1.4 I am getting a different error now:
[ErrorException]
Illegal offset type in unset
Detailed stacktrace: https://cl.ly/0109383S0X0e
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spatie/laravel-tail/issues/7#issuecomment-273927903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdiDQh4tHh1iTTJNQB4Dt1ClHbSNJQ1ks5rT-0egaJpZM4Loqau
.

--
Freek Van der Herten https://spatie.be +32 495 84 27 91

No problem. Cheers!

authors: freekmurze jkudish

repo: spatie/laravel-tail


text:
failed to run some FPGA samples

Describe the bug
I can run  dace/samples/fpga/rtl/fladd.py without issues but failed in running other rtl examples. Here is the error log:
python dace/samples/fpga/rtl/pipeline.py

Traceback (most recent call last):
  File "/home/<user>/Workspace/dace/pipeline.py", line 164, in <module>
    sdfg(A=a, B=b, N=N)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/sdfg/sdfg.py", line 2342, in __call__
    binaryobj = sdfg.compile()
                ^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/sdfg/sdfg.py", line 2254, in compile
    program_objects = codegen.generate_code(sdfg, validate=validate)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/codegen.py", line 231, in genera
te_code
    (global_code, frame_code, used_targets, used_environments) = frame.generate_code(sdfg, None)
                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/framecode.py", line 831,
 in generate_code
    states_generated = self.generate_states(sdfg, global_stream, callsite_stream)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/framecode.py", line 408,
 in generate_states
    callsite_stream.write(cft.as_cpp(self, sdfg.symbols), sdfg)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/control_flow.py", line 217, in a
s_cpp
    expr += elem.as_cpp(codegen, symbols)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/control_flow.py", line 129, in a
s_cpp
    expr += self.dispatch_state(self.state)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/framecode.py", line 385,
 in dispatch_state
    self._dispatcher.dispatch_state(sdfg, state, global_stream, stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 354, in dis
patch_state
    disp.generate_state(sdfg, state, function_stream, callsite_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/fpga.py", line 637, in g
enerate_state
    self.generate_kernel(sdfg, state, kernel_name, single_sgs, function_stream, callsite_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/fpga.py", line 2263, in
generate_kernel
self.generate_kernel_internal(sdfg, state, kernel_name, predecessors, subgraphs, kernel_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/xilinx.py", line 1094, in generate_kernel_internal
    self.generate_modules(sdfg, state, kernel_name, subgraphs, subgraph_parameters, module_stream, entry_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/fpga.py", line 2316, in generate_modules
    self.generate_module(sdfg, state, kernel_name, module_name, subgraph, subgraph_parameters[subgraph],
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/xilinx.py", line 823, in generate_module
    self._dispatcher.dispatch_subgraph(sdfg,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 393, in dispatch_subgraph
    self.dispatch_node(sdfg, dfg, state_id, v, function_stream, callsite_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 420, in dispatch_node
    disp.generate_node(sdfg, dfg, state_id, node, function_stream, callsite_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/rtl.py", line 64, in generate_node
    self.dispatcher.dispatch_copy(src_node, node, edge, sdfg, dfg, state_id, function_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 562, in dispatch_copy
    target.copy_memory(sdfg, dfg, state_id, src_node, dst_node, edge, function_stream, output_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/rtl.py", line 110, in copy_memory
    callsite_stream.write(line)
                          ^^^^
UnboundLocalError: cannot access local variable 'line' where it is not associated with a value

note that "line" is possibly unbound in dace/codegen/targets/rtl.py:110
Desktop (please complete the following information):

OS: Ubuntu 20.04.6 LTS x86_64
Dace: Version: 0.14.4

Anything I missed?

Hi @remifan ! You were right, some of the RTL samples weren't set up properly, resulting in them not using the workflow for which they were intended, which led to the error you encountered. After #1403 this shouldn't be the case anymore, and each sample should run as intended.
Could you verify whether you're still having the problem with the current master branch? And do say if you encounter any more problems. :)

Thanks a lot for the fixes, the examples are working now

authors: carljohnsen remifan

repo: spcl/dace


text:
Validation issue with undefined LicenseRefs

In this SPDX document (it is in JSON format, but has .txt extension because of GitHub), the LicenseRef-21495e9 (among others) is used twice in the document, but not defined anywhere.
This issue is not picked up by the java-tools validation.
For reference, the issue came up here.

Here is the list of all undefined LicenseRefs that the python-tools picked up on:
LicenseRef-21495e9
LicenseRef-1c734cf
LicenseRef-fa9fd02
LicenseRef-4ccf56f
LicenseRef-39c3ee0
LicenseRef-21495e9
LicenseRef-1b79b75
LicenseRef-ca2312b
LicenseRef-45c771b

Closing due to this comment.

repo: spdx/tools-java


text:
Improve ASGI server documentation

Discussions in #1757 indicate that we should document this more clearly.

coverage: 94.237%. remained the same
when pulling 8d1c6e16a15c1c8cb73479895d8a0eaaa758a2b8 on docs/gunicorn
into bcf4c63b32835eddd624d6b936abfccad1646908 on main.

authors: RobbeSneyders coveralls

repo: spec-first/connexion


text:
Don't skip redundant lines

To fix SpWizard compatability

Closing this as it wasn't the root cause of the SpWizard compatibility issue


text:
Schema reference support - AVRO

See
https://docs.confluent.io/platform/6.2/schema-registry/serdes-develop/index.html#referenced-schemas
Currently specmesh will only bind schemas to topic-subjects, however cascading/references are not published. A schema may reference common types etc - they common types need to be packaged, managed and publishing
Lookup strategies are used when publishing the 'subject' of the schema: CFLT uses:
https://docs.confluent.io/platform/6.2/schema-registry/serdes-develop/index.html#subject-name-strategy

TopicNameStrategy
Derives subject name from topic name. (This is the default.)

RecordNameStrategy
Derives subject name from record name, and provides a way to group logically related events that may have different data structures under a subject.

TopicRecordNameStrategy
Derives the subject name from topic and record name, as a way to group logically related events that may have different data structures under a subject.

APICurio supports
https://github.com/asyncapi/bindings/blob/master/kafka/README.md
https://www.apicur.io/registry/docs/apicurio-registry/2.2.x/getting-started/assembly-using-kafka-client-serdes.html#registry-serdes-concepts-strategy_registry
RecordIdStrategy - Avro-specific strategy that uses the full name of the schema.
TopicRecordIdStrategy - Avro-specific strategy that uses the topic name and the full name of the schema.
TopicIdStrategy - Default strategy that uses the topic name and key or value suffix.
SimpleTopicIdStrategy - Simple strategy that only uses the topic name.

done!

repo: specmesh/specmesh-build


text:
[Feature Request]: Streaming ASR (WIP)

🚀 The feature
Streaming ASR being a goal for SpeechBrain has already been discussed internally among the core team members, but it seems worthwhile to share the info/personal notes/WIP I have and to keep this publicly updated. I'll try to semi-regularly update the issue according to how things evolve, and it will be closed once a working implementation is merged.
Solution outline
The current plan is to base off work on #1782, first meaning changes to certain modules have to be done to enable streaming and having a working recipe. Implementing the actual interfaces for streaming ASR can come after once there is a proven to be working model. Certain features (like beam search decoding or LM rescoring) are non-essential for a proof-of-concept.
Some notes:

k2/icefall appears to use https://arxiv.org/pdf/2012.05481.pdf aka a form of "chunked attention"

during training, at a given batch, a random chunk size is emulated by aligning visible future context for an output token to the chunk size (the paper explains it better)
because the model is trained with multiple chunk sizes, it can be adjusted for a latency-performance tradeoff at runtime
DCConv is an interesting variant (implemented and detailed further down): https://arxiv.org/pdf/2304.09325.pdf

Implementation status:
tl;dr on the streaming architecture changes:

Feature extraction sees little changes

Padding is adjusted/performed manually in order to make it easier to align frames exactly as we want, because center==True in STFT could cause problems otherwise with certain sequence lengths. No other change.

Conformer changes

Attention is masked in "chunks": All outputs within a chunk (of e.g. 16) can "see" the keys of its chunk + eventually some left context. For example, assuming infinite left context:

ALL outputs 0..15 will depend on inputs 0..15, but cannot depend on 16..
ALL outputs 16..31 will depend on inputs 0..31, but cannot depend on 32..
ALL outputs 32..47 wil ldepend on inputs 0..47, but cannot depend on 48..
etc.
Thus, if we were to have no left context, each output would reliably only depend on 16 inputs.

The convolution requires masking, because with no special care its perceptive field would peek into future frames. I use the DCConv approach (AWS paper) which effectively "masks" frames future to each chunk.

The way it is done is that the convolution operator is replaced to split the input into chunks (the same way as attention effectively does). Then, we add the left context (of size (kernel_size-1)/2) to serve as left padding to the convolution. The right padding will be applied as normally, and will not be future chunk data (but zero-padding or reflected padding or whatever).
This means that we need to perform the padding manually for best efficiency. Otherwise, the convolution would add left padding to our left padding, and output a tensor of length (chunk_size + left_context) even though we only need the last (chunk_size) elements.
We also (ab)use the DCConv operator to limit left context in the way that we would like. TODO: is this necessary

Dynamic Chunk Training is implemented: For each back, 50% chance of full context (as usual) or 50% chance of picking a random chunk size between e.g. 8 and 32 chunks. Papers mention this as a requirement for proper convergence.

Randomly switching between chunk sizes means the model should be able to adapt to them, meaning the chunk size can be selected at runtime for a tradeoff between accuracy and latency.

Limiting left context is slightly tricky, because allowing chunks to see e.g. 1 chunk to the past means this will repeat across every layer of the conformer. Thus with 12 encoder layers, a left context of 1 chunk ultimately translates into 12 chunks of left context.

... Unless the left context visibility is only applied to a single layer, but I do not know how standard that is.
Left context is specified in number of chunks as it is the most natural fit (consider inter-chunk dependencies across layers) and we probably do not nede finer granularity.

Depending on certain batching and masking circumstances, it is possible for some sequences to be entirely masked, i.e. their keys are set to -inf in attentional score calculation. This is a problem, because it means that all inputs to the softmax layer in attention can become -inf, which causes all outputs to become NaN (because the divisor in the softmax formula sums to 0 as e^-inf = 0). This regularly broke training with NaN losses that never recovered. Adding an epsilon value to the divisor mitigates the issue as it will become > 0.

Computing chunk sizes, required left contexts, etc. and effective frame counts is entirely predictable here, but it does depend on deep understanding of the models inputs. Here, 8 chunks corresponds roughly to a latency of 365ms (to double check).
tl;dr on what will be required for the model when it comes to streaming interfaces:

For feature extraction, chunking is relatively easy, but carries left dependencies due to the striding nature of the FBanks and CNN.
At the output of each conformer layer, the input-output dependency properties mentioned before for attention are respected. Thus, left context of chunks can be cached at each layer of the conformer.
Left context keys and values can be cached in the MHA.
For everything involved, some adjustments may prove necessary for chunk-by-chunk inference.

tl;dr on what work would be needed to port this approach to the Branchformer:

At a glance, it does not seem like many conceptual changes are necessary compared to the Conformer model here. DCConv-like masking should be applied in the Conv1D in the CSGU (aside of the attn changes) and that should be about it.
Investigate if any other "bricks" were modified that could cause issues; adjust contexts and chunk size effective frame count calculations. Use the dependency detection functions I made.

Additional context
No response

Quick notes I wrote of the DCConv which may help visualizing:

As for what the DCConv implementation does:

(Big image) Input are taken with strides of 5ms (80 frames) on the x axis for testing wrt the input @16kHz with a transformer chunk size of 8 (post CNN downsampling). This is an example for a 5s (random) input signal on an untrained model.
This is a "dependency plot" which highlights which inputs every output depends on. Right now, this is with full left attention, so an output token can see all prior input tokens.

Full attention would mean the entire image would be red. Here, you can observe "chunks" of attention, which are of perfect/predictable length in time. This is what most of this preliminary work focused on accomplishing.
For example, if you looked at x=80(*80 = 6400 for actual input frame) and y=5, the cell is white, meaning the 5th output token does not depend on the 6400th input frame.

repo: speechbrain/speechbrain


text:
snipmate error on launch

Error detected while processing ~/.vim/bundle/snipmate.vim/plugin/snipMate.vim:
line   31:
E117: Unknown function: funcref#Function
E116: Invalid arguments for function get(s:snipMate, 'get_snippets', funcref#Function("snipMate#GetSnippets"))
E15: Invalid expression: get(s:snipMate, 'get_snippets', funcref#Function("snipMate#GetSnippets"))
vim 7.3 on ubuntu 11.04
i have this plugins :
checksyntax_vim
commant-t
delimitMate
FindFile
nerdtree
PIV
snipmate-snippets
snipmate.vim
supertab
vim-files
vim-fugitive
vim-git
vim-markdown

This has been resolved in the latest branch.


text:
versioned releases

The page is published to https://[user name].github.io/[repo name]/
There is no option to publish a versioned release
In this workflow, the versioned release is made possible by peaceiris/actions-gh-pages@v3 and inputs:
publish_dir: ./public
destination_dir: 1.0.0

Which would produces our coveted versioned site
https://[user name].github.io/[repo name]/1.0.0/

What is the tradeoffs between actions/deploy-pages@v4 and peaceiris/actions-gh-pages@v3 ??

Just to future proof. multiple language support
https://[user name].github.io/[repo name]/en/stable/

Just because actions/deploy-pages@v4 is an official action and does not know about peaceiris/actions-gh-pages@v3. I think it is ok to switch to the latter one (without breaking anything), PR is welcome.

authors: SilverRainZ msftcangoblowm

repo: sphinx-notes/pages


text:
Sprial cannot be downloaded from spiral get-binary for Chinese users

the network will timeout when Chinese user to execute vendor/bin/spiral ， so a binary image should be added

Can you try to download it directly from GitHub? Is it being blocked by the Chinese firewall?

Can you try to download it directly from GitHub? Is it being blocked by the Chinese firewall?

It is not blocked by GFW of China, but it's very slow for Chinese developers to download assets from github(with s3 CDN).

Any recommendations? I'm not able to debug it from my end. We can increase the timeout.

My recommendations:

Download the binary from a mirror URL instead of github release. The problem is S3 storage used by github.
You can support an environment variable like SPIRAL_BINARY_MIRROR, when there is such variable in user's enviroment, use it. (Like puppeteer, node-sass, node-sqlite3...)

@wolfy-j You can contact "jsdelivr", they can provide CDN for spiral's binary. It works perfectly both inside and outside China.
See jsdelivr's readme:

We can work together and setup a custom configuration for your project. This way, you can have full control over your files and the ability to utilize the full power of jsDelivr.
This kind of custom hosting can be suitable for:

Binary hosting. Windows executable files and zips.
Frequently updated files.
Projects that can't follow jsDelivr file structure.
Some other use that will blow all of our minds.

Simply send an email to dak@prospectone.io with a request for more information.
Current OSS projects using custom configs:

webjars
webpack webpackbin and codesandbox

Thank you for the suggestion! I'll add this thing to our pipeline.

thank u

Please try to download directly from GitHub in the meantime. I can not provide you a clear ETA at the moment.

I downloaded through some tools and it can be used normally at present, but the current situation is very unfriendly to most Chinese users

I downloaded through some tools and it can be used normally at present, but the current situation is very unfriendly to most Chinese users

you can use https://github.com/nkbai/githubdns to solve this issue temporarily.

authors: fengahan krwu wolfy-j

repo: spiral/app


text:
ruby2.5で動くようにする

以前は、2.5だと接続処理が進まなかったけど、今は動くようになっているはず。
それと、rbenvを依存にしたくなくて、aptで入れたrubyでも動いたほうがドキュメントが薄くなっていい。

最初はラグかったけど、10分くらいつなげていると普通に使えるようになってた。
----
ProconBypassMan::VERSION: 0.2.1
RUBY_VERSION: 2.5.5
Pbmenv::VERSION: 0.1.10
pid: 2621
root: /usr/share/pbm/v0.2.1
pid_path: /usr/share/pbm/v0.2.1/pbm_pid
setting_path: /usr/share/pbm/current/setting.yml
uptime from boot: 1035 sec
use_pbmenv: true
session_id: s_d5a2ed5c-7612-46fa-a12c-afa123fa31fe
device_id: d_9fadc91f-65*************************
bypass_mode: normal(10)
----


text:
PAPP-22080: update release note for fips

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Run the pipeline in gitlab and it's successful: https://cd.splunkdev.com/phantom-apps/app-tests/-/pipelines/4435442


text:
Generate python 3.9 wheels

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[X] Testing of all the changes has been performed (for bug fixes / features)
[X] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[X] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[X] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[X] Verify all checks are passing.
[X] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[X] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

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

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Could you add release note for the py39 change as well?
reference: https://github.com/splunk-soar-connectors/safebrowsing/pull/2/files#diff-39546c13b2e65128c3c87daae7669c4eb99144207b446fc902bedacdd3e60345R2

Could you add release note for the py39 change as well?
reference: https://github.com/splunk-soar-connectors/safebrowsing/pull/2/files#diff-39546c13b2e65128c3c87daae7669c4eb99144207b446fc902bedacdd3e60345R2

Done!

authors: jdemelo paulnawat

repo: splunk-soar-connectors/winrm


text:
Requirement test/addon 32746

Please review - Merge requirement test to PSA

Requirement tests added to standard library under  pytest_splunk_addon/standard_lib/requirement_tests. This adds test_requirement_params to tests
TA_requirement_test folder added to tests/addons. Requirements folder removed from TA_fiction.
test_splunk_app_requirements added to test_splunk_addon.py.
Addon  in TA_requirement_test is "Splunk Add-on for Juniper addon" with successful/failure case sample_requirement_file.
Constants [ TA_REQUIREMENTS_PASSED, TA_REQUIREMENTS_FAILED] added to constants.py for test results reporting.

We will need to add requirement files to the TA and add parameter "--requirement-test" to pytest run command for requirement tests

:tada: This PR is included in version 1.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: nandinivij rfaircloth-splunk

repo: splunk/pytest-splunk-addon


text:
AAD signins - not all riskEventTypes_v2 values collected

Using the add-on,  we don't see any riskyIPAddress values in the indexed riskEventTypes_v2 fields of Splunk events.
I have searched back over our entire index and don't get any hits for this:
index=azure  sourcetype="azure:aad:signin"   riskEventTypes_v2{}=*risk*

even though I can find events that should match when I query Graph directly:
Get-MgAuditLogSignIn -All -Filter "riskEventTypes_V2/any(c:c eq 'riskyIPAddress') and createdDateTime ge 2023-08-01T00:00:00Z and createdDateTime lt 2023-08-29T00:00:00Z"

An example of a Graph-fetched log:
  {
    "CorrelationId": "108e77d9-dd07-4455-8f2b-db3562c68d9d",
    "CreatedDateTime": "2023-08-16T03:31:47Z",
...
    "IPAddress": "185.220.101.20",
    "Id": "62b96348-b714-43a3-a909-cbf49e63cb00",
    "IsInteractive": true,
    "Location": {
      "City": "Schoenwalde-Glien",
      "CountryOrRegion": "DE",
...
      "State": "Brandenburg"
    },
    "ResourceDisplayName": "Office 365 Exchange Online",
    "ResourceId": "00000002-0000-0ff1-ce00-000000000000",
    "RiskDetail": "userPassedMFADrivenByRiskBasedPolicy",
    "RiskEventTypes": [
      "anonymizedIPAddress"
    ],
    "RiskEventTypesV2": [
      "anonymizedIPAddress",
      "riskyIPAddress"
    ],

and the same event logged in Splunk.   Note the difference in the RiskEventTypesV2 field values
{
  correlationId: 108e77d9-dd07-4455-8f2b-db3562c68d9d
  createdDateTime: 2023-08-16T03:31:47Z
...
  id: 62b96348-b714-43a3-a909-cbf49e63cb00
  ipAddress: 185.220.101.20
  isInteractive: true
  riskEventTypes: [ [-]
    anonymizedIPAddress
  ]
  riskEventTypes_v2: [ [-]
    anonymizedIPAddress
  ]
  riskLevelAggregated: none
  riskLevelDuringSignIn: medium

The non-beta endpoint returns these values whether I use Get-MgAuditLogSignIn (see example in original note) or  https://developer.microsoft.com/en-us/graph/graph-explorer (pic below).

repo: splunk/splunk-add-on-microsoft-azure


text:
当js模块的文件名含有"."时，无法将这个模块的依赖转化到依赖这个模块的依赖里？

呃，可能标题描述得有点绕。
大概就是
a.js依赖b.js
b.js依赖c.js
正常情况下，transport这三个模块时，a模块会被转化为 require('a', ['b', 'c'] ....)
但是假如b.js的文件名中含有另一个"."，例如命名为 "b.b.js"时，a模块就只会被转化为require('a', ['b.b'] ...)。因此，concat配合transport使用时，也就不会把c.js也合并进去。
这是否是一个BUG？
https://github.com/xosuperpig/seajs-learning
这是我的测试代码。
执行grunt，会输出with.js和without.js，对应src_withpoint和src_withoutpoint里的代码

目前我自己定位到的问题所在是
在grunt-cmd-transport/tasks/lib/script.js 179行里使用map方法过滤掉了所有依赖的.js后缀名，之后通过appendext补回后缀名，但appendext方法中误将.b当成了真正的后缀名，因此这个文件就没有被补回，于是它的依赖就没有被递归搜集到。
对seajs并不是非常了解，所以我目前自己暂时强制 +='.js'处理了

我也遇到了这样的情况，在开发环境中，我使用seajs-text来加载.tpl文件，但在生产环境中，没有使用seajs-text, 而使用.tpl.js把模板当模块加载（因为使用了不支持跨域的静态资源服务器），这样的情况下，transport解析出来的依赖把模板丢失了。建议增加当非.js文件a.b不存在时，对a.b.js的检测

@lepture  我也遇到 文件名有’.'会丢掉依赖

@popomore @lifesinger @lepture @afc163  我也遇到了这个问题，文件名是a.b.js，依赖老是提取不到，换成a.js，就可以提取了，能修复下这个bug吗

@xhxno36  已经有人处理过了，搜下替换下就可以避免这个问题

@liupeng110112 在哪里，是按照他说的方法改吗？@xosuperpig

@xhxno36  http://life.leanote.com/post/grunt-cmd-transport-deps-bugs 看下这个 覆盖下试试

repo: spmjs/grunt-cmd-transport


text:
Angular 1.4.8 throws Cannot read property 'activeDate' of null

It seems like https://github.com/spongessuck/gm.datepickerMultiSelect/blob/master/src/gm.datepickerMultiSelect.js#L125 is reversed, as in the the controller is the last of the controllers array, instead of the first.
The bug doesn't occoure when using angular 1.4.7 and angular-bootstrap 0.14.3. Upgrading to 1.4.8 produces the error.

This was due to using a new angular-bootstrap version and using the old directives (datepicker instead of uib-datepicker).


text:
Update Gemfile & Fix Codecov

Update Gemfile to silence a warning. Also, pass -X xcodeplist to codecov uploader to scan for and process xccoverage reports instead of using llvm-cov.

👍

Codecov Report

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

@@          Coverage Diff          @@
##           master   #357   +/-   ##
=====================================
  Coverage       0%     0%
=====================================
  Files           7      7
  Lines         132    132
=====================================
  Misses        132    132

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cedb505...1ebd193. Read the comment docs.

authors: 8W9aG codecov-io dflems

repo: spotify/HubFramework


text:
docs: minor typo correction

Hey, I just made a Pull Request!
Minor doco correction

Hey, I see that we had an underlying Prettier error. I made a PR to fix it, would you mind rebasing on that after it is merged? https://github.com/spotify/backstage/pull/2308

@freben sure thing, no worries

Welcome to Backstage @davidamitchell 🎉

authors: davidamitchell freben stefanalund

repo: spotify/backstage


text:
catalog: use the ownedBy relation to display owners

Fixes #2959, kinda. It was implemented as part of #2617, but this adds consumption in the frontend to ensure that types etc. work e2e.

@freben except that we have no idea how to do that properly atm 😅


text:
Support for H2 embedded Java database

This PR will add support for H2 as another database option. As H2 supports a Postgres combat mode, only minor changes were needed when it comes to SQL and JDBC handling.
Using H2, reaper can be distributed as a self contained package (except for yaml config) without having to rely on the in-memory store. Database files will be created automatically using the schema in the new reaper_h2.sql file.

I like the idea of using H2, but I'm not totally sure about the current proposed implementation. I will ponder a bit on this, and think what would happen if a third database implementation was added.

TBH my first plan was to add MySQL or H2 support by implementing the IStorage API. However, that would require to refactor out some common classes out of the postgres package that could be used in new implementations as well. The alternative would be to just duplicate the postgres implemenation and fix all incompatibilities which would result in a lot of duplicated code.
It would be great if the storage API JDBI integration could be made more DB agnostic. But the effort should be considerable.
Given the postgres compatibility, introducing h2 into the project using the existing postgres storage implementation was a better option that could be done much quicker. In case at some point adding new storage implementations would be easier, I'd be happy to adapt the h2 code for that as well. Until then I think the h2 option lowers barriers and might help people to make up their minds to give the project a test drive.

To me it feels like just adding more database implementations doesn't really serve an acute user need, unless it brings in more capabilities for the system. H2 implementation does bring the ease of use in case you don't want to separately maintain a separate database instance. Adding MySQL in addition to Postgres doesn't seem to add anything else except complexity into the code. Thus I'm starting to lean into having a bit custom, as long as it is short and simple as possible, implementation for the H2.

authors: spodkowinski varjoranta

repo: spotify/cassandra-reaper


text:
[query-builder] aggregation change function

Currently when you set an aggregation like max for-each you cannot change max to something else. This requires you to delete the aggregation and then add it again. If you have many aggregations you have to delete them all since you cannot click and drag the aggregations around.

I would find this very helpful 👍

repo: spotify/heroic-grafana-datasource