text:
Playlist continues to play on a scene onto which it is not assigned

Description of the problem
I have a playlist assigned on a scene but when i leave this scene to another (with no playlist assigned), the playlist continues to play whereas it should not.
ForgeJS version
0.9.5
Browser

[ ] All of them
[x] Chrome
[x] Firefox
[ ] Internet Explorer

OS

[ ] All of them
[ ] Windows
[x] macOS
[ ] Linux
[ ] Android
[ ] iOS

How to reproduce the problem

On a story with at least 2 scenes, assign a valid playlist to a scene, for example the first (scene 1)
Launch and listen scene 1, it is ok
Now go to the scene 2, the playlist still plays whereas there is no JSON config set

To really work around and stop the playlist on scene 2, i need to assign a invalid playlist id to the scene 2

Hi @oblanc-gpsw can you post the config.json of your project that use distant resources in order to test your use case ?
Thanks for the report !

authors: oblanc-gpsw rroux-gpsw

repo: gopro/forgejs


text:
How to get timestamp of every point?

Hi,
I didn't understand very well how to get GPSU for each payloads.
Thanks in advance

GPSU is not stored for every GPS5 sample, but as the sample interval is constant you can interpolate between GPSUs from each payload.  The GPSU value is the first GPS5 coordinate in each payload.

source: gharchive/issue

authors: LucaTrip dnewman-gpsw

repo: gopro/gpmf-parser

license_type: permissive

license_source: github-api


text:
删除liyu36/kubectl-version-manager包

麻烦删除一下github.com/liyu36/kubectl-version-manager包，包名称有问题，我已经修改过，但是问题版本已经被缓存了。

经查看，无改库的缓存

repo: goproxyio/goproxy

license: MIT


text:
Merge layers

I added a feature to obtain a single map[string]interface{}, instead of the usual slice, containing all the layers.
And I also added a method that will use this merge: a MergeAndDecode method that will decode our configuration directly in a struct using mapstructure, that is already a dependency of this project.
I hope you'll be glad of my adds and you will merge this feature to your project! We would like to use onion in our, I liked the layer concept and how you have implemented it.
Thanks in advance

There is similar functionality in the file writer (https://github.com/goraz/onion/blob/master/onionwriter/onion_writer.go#L13)
But I prefer your implementation. The only problem is the new dependency in the main package.
My suggestion is to move this code to the onionwriter, refactor SerializeOnion to use your method, export two functions: MergedLayersData(o *Onion) map[string]interface{} and also MergeAndDecode(o *Onion, obj interface{}) error

Also just an idea, with your function we can have a layer that actually is another onion object. I am not sure if it is useful or not tho.

There is similar functionality in the file writer (https://github.com/goraz/onion/blob/master/onionwriter/onion_writer.go#L13)
But I prefer your implementation. The only problem is the new dependency in the main package.
My suggestion is to move this code to the onionwriter, refactor SerializeOnion to use your method, export two functions: MergedLayersData(o *Onion) map[string]interface{} and also MergeAndDecode(o *Onion, obj interface{}) error
Also please add tests for these new functions.

I would like to move my code inside onionwriter but there's a problem if I call onionwriter from onion:
can't load package: import cycle not allowed
package github.com/goraz/onion
        imports github.com/goraz/onion/onionwriter
        imports github.com/goraz/onion

Also just an idea, with your function we can have a layer that actually is another onion object. I am not sure if it is useful or not tho.

I think I'll use this function for implement the folder feature.

I can not understand why you import configwriter in onion?

I can not understand why you import configwriter in onion?

onionwriter! If I move my code that do the merge in onionwriter, then I need to recall it from onion.go for the apis
MergedLayersData(o *Onion) map[string]interface{}
MergeAndDecode(o *Onion, obj interface{}) error

Sure, it is already imported in the onionwriter, my question was why you need to import onionwriter in onion. (the circular import)

Sure, it is already imported in the onionwriter, my question was why you need to import onionwriter in onion. (the circular import)

I wanted to move a merge method in onionwriter.
Ok, I'm going to finish to write even the folder part and commit, then you will tell me :)

Cool! Thank you :)
On Thu, Mar 12, 2020 at 4:07 PM Cirelli notifications@github.com wrote:

Sure, it is already imported in the onionwriter, my question was why you
need to import onionwriter in onion. (the circular import)
I wanted to move a merge method in onionwriter.
Ok, I'm going to finish to write even the folder part and commit, then you
will tell me :)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/goraz/onion/pull/19#issuecomment-598239983, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHEJ46NA3CDJKCGX4VZYD3RHD3DBANCNFSM4LFWIIXA
.

I think I did what you asked me!
I had to create a package for a function that is used both from onionwriter and onion:  utils package...
I'm going to write some test for folder-layer and that's all folks!

Just a minor issue: why the directory_layer is not an external layer inside the layers folder (https://github.com/goraz/onion/tree/master/layers)

I didn't understand why some layers are outside and some inside layers: however I now moved as you asked.
I have some problems with the test with go versions before 1.14, I don't know why...

This is why onion is different. the problem I had was having too many
dependencies for one simple task. If you don't want to use the etcdlayer,
adding etcd library to your code is not a good idea. also the same for the
watch file layer and in this case, the folder layer. in the end, the
compiler merges them into one single file, so there is no performance
problem with many files. (like python/PHP and scripting language in
general)
So basically you can add any layer, without modifying the main library (the
onion package itself).
On Mon, Mar 16, 2020 at 2:42 PM Cirelli notifications@github.com wrote:

I didn't understand why some layers are outside and some inside layers:
however I now moved as you asked.
I have some problems with the test with go versions before 1.14, I don't
know why...
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/goraz/onion/pull/19#issuecomment-599542971, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHEJ44D6F7GHDMJHOJUHT3RHYUFLANCNFSM4LFWIIXA
.

I also misnamed the directorylayer package.
I fixed the empty lines you asked and something more in directorylayer.
Maybe maybe it's the right time...

Tests are going wrong because behaviour of https://golang.org/pkg/io/ioutil/#TempDir has changed.

source: gharchive/pull-request

repo: goraz/onion


text:
Unable to Change Username and Password in Gorse

I am unable to change the username and password for the Gorse  when running the application using Docker.
can u suggest some steps for change this one

How you change username and password?

i,m changing username and password using docker commands

You can change username and password in config file or via environment variables:
https://gorse.io/docs/master/config.html

repo: gorse-io/gorse


text:
How to make a pdf read-only?

Is there any way to lock down a generated pdf so it's read-only?

Hello @WKampel,
It is not possible currently, but I added it to my TODO list.

authors: WKampel gulien

repo: gotenberg/gotenberg


text:
[Feature Request]: ASP MVC Razor frontend Demo

Relevant Scope
Frontend specs
Description
Hello can you please include an ASP Core MVC front end in this as well.
Describe the solution you'd like
ASP Core MVC with ViewComponents and the other advanced frontend techniques to interweave dual binding, rx.js etc
Describe alternatives you've considered
No response

Hello @fasteddys,
Implementations are created by the community.
Feel free to work on one matching your expectations to share it with the community.

authors: fasteddys geromegrignon

repo: gothinkster/realworld

license: mit

license_source: bigquery


text:
how to destroy Timeout

i had use glib.TimeoutAdd to create timeout and get the result typeof glib.SourceHandle but i dont't know how to stop it

Hi,
Actually, you cannot do that rightly as indicated in glib reference manual:

g_source_remove ()
g_source_unref ()
g_source_destroy ()

these binding does not exist at this time (I will work on it).
so, while reading the f.....g manual, I figure out:
g-timeout-add:

Sets a function to be called at regular intervals, with the default priority, G_PRIORITY_DEFAULT. The function is called repeatedly until it returns FALSE, at which point the timeout is automatically destroyed and the function will not be called again. The first call to the function will be at the end of the first interval .

return false and you do it ...
declare global var:
var timeoutContinue = true
make your timeout:
glib.TimeoutAdd(uint(1000), func() bool {
	fmt.Println("timed out")

	return timeoutContinue
})

Button's callaback func:
// Example, in callback to "clicked" signal for a button.
func toStopTimeout(){
	timeoutContinue=false
}

Bye.

thinks for help

Done
https://github.com/gotk3/gotk3/pull/436
An example on how to use:
package main

import (
	"fmt"
	"log"

	"github.com/gotk3/gotk3/glib"
	"github.com/gotk3/gotk3/gtk"
)

var timeoutContinue = true
var tos glib.SourceHandle

// Create and initialize the window
func setupWindow(title string) *gtk.Window {
	win, err := gtk.WindowNew(gtk.WINDOW_TOPLEVEL)
	if err != nil {
		log.Fatal("Unable to create window:", err)
	}

	win.SetTitle(title)
	win.Connect("destroy", func() {
		gtk.MainQuit()
	})
	win.SetPosition(gtk.WIN_POS_CENTER)
	width, height := 600, 300
	win.SetDefaultSize(width, height)

	box, _ := gtk.BoxNew(gtk.ORIENTATION_VERTICAL, 0)
	btn, _ := gtk.ButtonNew()
	btn.Connect("clicked", ButtonClicked)
	btn.SetLabel("Stop timeout")

	box.Add(btn)
	win.Add(box)

	return win
}

func main() {
	gtk.Init(nil)

	win := setupWindow("Go Example Testreport")

	win.ShowAll()

	// Init timeout:
	tos, _ = glib.TimeoutAdd(uint(1000), func() bool {
		fmt.Println("timed out")

		return timeoutContinue
	})

	gtk.Main()
}

func ButtonClicked() {
	var methode int

	// Three methods to stop timeout:
	// 1- Destroying
	// 2- Removing
	// 3- Returning false by called function

	// Choose one of them:
	methode = 3

	switch methode {
	case 1: // 1- Destroying
		mcd := glib.MainContextDefault()
		src := mcd.FindSourceById(tos)
		src.Destroy()
		fmt.Printf("Timeout stopped & IsDestroyed: %v\n", src.IsDestroyed())

	case 2: // 2- Removing
		glib.SourceRemove(tos)
		fmt.Printf("Timeout stopped but still referenced\n")

	case 3: // 3- Returning false by called function
		timeoutContinue = !timeoutContinue
		fmt.Printf("Timeout stopped but still in memory and referenced\n")
	}
}

pretty well,thinks

@hfmrow want to add that example to gotk3/gotk3-examples?
@liao725636367 The PR for the missing bindings is merged. Is your issue resolved now?

we close the issue, since there was no response.
It can be opened at any time if the issue exists.

authors: andre-hub founderio hfmrow liao725636367

license: isc


text:
Retain search query in search box

What do you need?
To remind the user which search term they used on the search results page.

One way to do this would be to retain the search query in the box ala 18F.

Which entry/section is this related to?
Any search result

Now being tracked in Trello

authors: gazanson joolswood

repo: govau/content-guide


text:
when I install this configuration, my tmux looks different than the one in the videos

my tmux only has blue, but in the video there is red, yellow and white and other colors. Is there something I should enable or is it not meant to be like that on default?

My OS is OpenBSD 7.3 Release
tmux tells me the version is "tmux openbsd-7.3"
the value is xterm-256color
here's a screenshot:

although when I try it on Arch Linux it works...

tmux reads configuration files in the following order

/usr/local/etc/tmux.conf
~/.tmux.conf
$XDG_CONFIG_HOME/tmux/tmux.conf
~/.config/tmux/tmux.conf

It doesn't stop at the first one it finds. Please have a look if you don't have configuration files laying around that would set status-left and status-right.

I only have a configuration in my HOME

I didn't reproduce with an OpenBSD 7.3 Vagrant box
$ vagrant init fnichol/openbsd-7.3
$ vagrant ssh
$ su -
$ pkg_add git
$ exit
$ git clone https://github.com/gpakosz/.tmux
$ ln -s .tmux/.tmux.conf
$ cp .tmux/.tmux.conf.local .
$ tmux

What's the output of the following command please?
$ env | grep TMUX

sorry for the late reply, the output of the command is:
TMUX_CONF=/home/light/.tmux.conf
TMUX=/tmp/tmux-1000/default,9689,0
TMUX_SOCKET=/tmp/tmux-1000/default
TMUX_PROGRAM=tmux
TMUX_PANE=%1
TMUX_CONF_LOCAL=/home/USER/.tmux.conf.local

Is tmux in your path?

@allthelightwe
Can you please clone and install again? There was an issue with GitHub picking the wrong branch as the default branch

Hello @maneater2 👋
Are you still facing this issue?

yes

could it be a issue with tmux not associating .tmux.local.conf with itself?

could it be a issue with tmux not associating .tmux.local.conf with itself?

I don't think so
As I said I didn't reproduce in an OpenBSD 7.3 Vagrant box.
Are you still using this version of OpenBSD?

no, I'm using 7.4-current

I'm seeing the same thing here on NixOS 23.11.
If I include a theme plugin, it sets up the status bar just fine.
Just using the default settings in the .local.tmux.conf file, I get the same behavior as shown in the screenshot above

@gpakosz You are correct.  I just pulled the latest and the status bar is working again now.


text:
fixes #24

on method
de.andreasschmitt.export.exporter.AbstractExporter#formatValue
I added a defaultFormatter (a configurable Closure) that format the object if is not defined a formatter for that field
Greetings

@icecuber Can you please add the test case around the functionality.
Also, it seems like the version has been reduced to 1.6.1 from 1.7-SNAPSHOT. Do you any specific reason for this?

authors: icecuber puneetbehl

repo: gpc/export


text:
Override address question?

Is it possible when using the override to display the original email intended address that is being overridden? This would make testing considerably easier if the original address was somehow listed but not sent.

@uhuntgx00 I was looking to obtain the same thing. Were you able to display the original recipient?

repo: gpc/grails-mail


text:
Some allocation records disappear in between two consecutive dumps with -alloc_space or -alloc_objects

Hello, we see the following strange behavior with gperftools v2.9.1 as well as latest v2.13.
In a dump 0001.heap, processed with -alloc_space (and -top) pprof options, we get the following output:
Type: alloc_space
Showing nodes accounting for 37059.20kB, 96.79% of 38287.35kB total
Dropped 1209 nodes (cum <= 191.44kB)
      flat  flat%   sum%        cum   cum%
29917.87kB 78.14% 78.14% 29917.87kB 78.14%  s1::util::StdNewDeleteResource::Allocate
         ... other items ...
         0     0% 96.79%  9625.52kB 25.14%  TiXmlAttribute::operator new
         0     0% 96.79% 25661.21kB 67.02%  TiXmlDocument::LoadFile
         0     0% 96.79% 25657.21kB 67.01%  TiXmlDocument::Parse
         0     0% 96.79% 27344.76kB 71.42%  TiXmlDocument::allocate
         0     0% 96.79% 26500.98kB 69.22%  TiXmlElement::Parse
         0     0% 96.79% 26063.46kB 68.07%  TiXmlElement::ReadValue
         0     0% 96.79% 17719.24kB 46.28%  TiXmlElement::operator new
         ... other items ...

We can see that there were allocations of ~ 38 MB, most of that coming from TiXml* classes through s1::util::StdNewDeleteResource::Allocate. However, in a later dump 0002.heap, taken after the TiXml classes have released their memory, and again processed with -alloc_space option, we get the following output:
Type: alloc_space
Showing nodes accounting for 12040.94kB, 95.46% of 12613.90kB total
Dropped 1271 nodes (cum <= 63.07kB)
      flat  flat%   sum%        cum   cum%
 3418.61kB 27.10% 27.10%  3418.61kB 27.10%  s1::util::StdNewDeleteResource::Allocate
         ... other items ...

We see the absolute number of memory allocated dropped to ~ 12 MB. And no trace of TiXml* classes. How is that possible? Shouldn't -alloc_space and -alloc_objects numbers be ever-increasing with consecutive dumps, and catch all allocations performed until that point (including -- and this is essential here -- those that were deallocated)?
This appears to be a bug, and makes it impossible for us to use gperftools reliably, because we don't know whether it catches all allocation-deallocation peaks done in between two dumps.
What do you think the cause could be? Thanks much for your help.
Architecture we are using: aarch64
May be related to #1388

Thanks for raising this. So heap profiler only dumps 1 meg worth of "stuff" each time it wakes up.
See here: https://github.com/gperftools/gperftools/blob/d1a0cbe1bfd8bfaa6223fb9913fa872a760e536e/src/heap-profiler.cc#L253
I don't know if it is "it" or you're facing some other artifact (I'd also double check what pprof does; keep in mind that your can do a closer inspection of profiles by doing pprof --raw (go pprof of course)).
We actually have a DCHECK (i.e. when NDEBUG isn't set) that crashes the process if heap exceeds the limit (!!), here: https://github.com/gperftools/gperftools/blob/d1a0cbe1bfd8bfaa6223fb9913fa872a760e536e/src/heap-profile-table.cc#L384
So you should be able to check if this condition affects your case or it is something else.
Let me know what you think.

@alk Thanks for your response.
Yes, each and every dump is ~ 1 MB large (with minor differences in the range of bytes). Is that OK? Logically I would expect each consecutive dump to be larger or equal to the previous dump, since many more allocations/deallocations from many new places occur in the mean time...
I don't fully understand your point about kProfilerBufferSize. Shall I try to increase kProfilerBufferSize, compile gperftools and see if it helps?
Regarding RAW_DCHECK, I will try it tomorrow and let you know.

Let me try to rephrase. We dump top-N of samples that add to this limit of 1 meg. Likely explains slight mismatches you see

Hi @alk. I've just tried to enable RAW_DCHECK by appending -UNDEBUG to gperftools build flags, but no crash. I then tried increase kProfilerBufferSize and re-build. This helped. I had to increase to 32 Meg, since dumps from our application needed from 5 - 22 Megs. Now the data really seems to be complete and trustworthy, no drops and no illogical decreases in numbers. Thanks!
I was not aware of such an internal detail that so greatly affects the completeness and trustworthiness of data. Did I miss related documentation somewhere? I guess this may be an issue to many other users as well.
Now, we have to patch internal gperftools code in our build system to increase its buffer size. This is very cumbersome. Is it possible to customize it at run time (e.g. through env variables or via the library API)? That would be much better.

Should be fixed now. Thanks for bringing this up and for a serious attempt at fixing it.

authors: alk sangelovic

repo: gperftools/gperftools


text:
Using faster-whisper-large-v3 model returns an error: Permission denied: 'C:\\Windows\\TEMP\\tmp4nurpm3y'

Steps to reproduce

Deploy a model Hugging Face/Systran/faster-whisper-large-v3
Go to the audio playground.
Upload an audio and generate the text.

Result

Returned an error.

Failed to transcribe audio, [Errno 13] Permission denied: 'C:\\\\Windows\\\\TEMP\\\\tmp4nurpm3y'

No error message in the instance logs.

2024-12-03T10:12:51+08:00 - gpustack.worker.backends.base - DEBUG - Model file size: 3090839273
Fetching 7 files: 100%|##########| 7/7 [00:00<00:00, 6355.01it/s]
2024-12-03T10:12:52+08:00 - gpustack.worker.backends.base - DEBUG - __init__ execution time: 1.298326015472412 seconds
2024-12-03T10:12:52+08:00 - gpustack.worker.backends.vox_box - INFO - Starting vox-box server
2024-12-03T10:12:52+08:00 - gpustack.worker.backends.vox_box - DEBUG - Run vox-box with arguments: start --model C:\Users\seal\AppData\Roaming\models\huggingface\models--Systran--faster-whisper-large-v3\snapshots\edaa852ec7e145841d8ffdb056a99866b5f0a478 --data-dir C:\Users\seal\AppData\Roaming\gpustack --device cuda:1 --host 0.0.0.0 --port 40296
2024-12-03T10:12:56+08:00 - vox_box.cmd.start - INFO - Starting with arguments: [('debug', None), ('host', '0.0.0.0'), ('port', 40296), ('model', 'C:\\Users\\seal\\AppData\\Roaming\\models\\huggingface\\models--Systran--faster-whisper-large-v3\\snapshots\\edaa852ec7e145841d8ffdb056a99866b5f0a478'), ('device', 'cuda:1'), ('huggingface_repo_id', None), ('model_scope_model_id', None), ('data_dir', 'C:\\Users\\seal\\AppData\\Roaming\\gpustack'), ('func', <function run at 0x0000026F16941440>)]
2024-12-03T10:13:03+08:00 - vox_box.server.server - INFO - Starting Speech Box server.
2024-12-03T10:13:03+08:00 - vox_box.server.server - INFO - Serving on 0.0.0.0:40296.
2024-12-03T10:13:57+08:00 - vox_box.utils.log - INFO - Starting transcribe method in FasterWhisper
2024-12-03T10:14:01+08:00 - vox_box.utils.log - INFO - Starting transcribe method in FasterWhisper
2024-12-03T10:14:34+08:00 - vox_box.utils.log - INFO - Starting transcribe method in FasterWhisper
2024-12-03T10:41:27+08:00 - vox_box.utils.log - INFO - Starting transcribe method in FasterWhisper

Environment

GPUStack version: main
OS: Windows 11
GPU: NVIDIA 4080

Additional context
Add any other context about the problem here.

Verified on main 81ac226

repo: gpustack/gpustack


text:
Plugin Development plugin declares inputs with custom equals()

> Task :nebula-code-quality:pluginDescriptors
Using objects as inputs that have a different serialized form but are equal has been deprecated. This is scheduled to be removed in Gradle 8.0. Type 'org.gradle.plugin.devel.PluginDeclaration' has a custom implementation for equals(). Declare the property as @Nested instead to expose its properties as inputs. See https://docs.gradle.org/7.4/userguide/upgrading_version_7.html#equals_up_to_date_deprecation for more details.

Your Environment
Gradle 7.4

Thank you for reporting! It seems like the equals in PluginDeclaration doesn't take displayName and description into account. I wonder why that is. In any case, the GeneratePluginDescriptors task probably shouldn't declare the list of plugin descriptors directly as an input.

@DanielThomas This will be fixed in Gradle 7.5.

Fixes #19029

authors: DanielThomas hegyibalint wolfs

repo: gradle/gradle


text:
Introduce option to print (resolved) runtime classpath dependencies

Gradle should provide native support for listing resolved configuration dependencies (absolute path to jars in ~/.gradle) in different formats, in addition to the existing tree view. It should be possible to list dependencies in a flat format by running Gradle as follows:
$ gradle :myproject:dependencies --configuration runtimeClasspath --format [tree (default),path,module]

This would avoid the need to write custom tasks or init scripts for printing configuration dependencies when working with Java projects (see context below for some use cases).
Ideally the output format would be configurable, printing absolute paths to cached libraries or artifact identifiers (<group>:<module>:<version>).
Expected Behavior
If I run the following
$ gradle :myproject:dependencies --configuration runtimeClasspath --format path

I would expect the following output:
/home/user/.gradle/caches/modules-2/files-2.1/com.company/library/8.7.3/27f66c2f5d3d22d8e37a8bb521e9881642bdc65/library-8.7.3.jar
/home/user/.gradle/caches/modules-2/files-2.1/com.company/thing/0.0.1/27f66c2f5d3d22d8e37a8bb521e9881642bdc65/thing-0.0.1.jar
...

If I run the following
$ gradle :myproject:dependencies --configuration runtimeClasspath --format module

I would expect the following output:
com.company:library:8.7.3
com.company:thing:0.0.1
...

Current Behavior
To list dependencies, I would have to write a task like this (or some variation of this):
    task printDependencies {
        doLast {
            Set<String> deps = new HashSet<>()

            project.configurations.runtimeClasspath.resolvedConfiguration.firstLevelModuleDependencies.forEach { it
                 it.allModuleArtifacts.each { it
                     deps.add(it.id.componentIdentifier.toString())
                 }
            }
            deps.each {
                println it
            }
        }
    }

This solution isn't very flexible, and I have to carry these scripts between all of the Gradle-based projects I maintain. It clutters our build scripts unecessarily. Alternatively we can put this stuff in an init-script, but I believe this is a feature that should be provided natively in Gradle.
Context

I use Gradle in quite a few projects these days, in both professional and personal projects. This is a feature I regularly find lacking in Gradle, the ability to obtain a list of (project) project dependencies that I can use. I often just write a dumb Gradle task or init script that resolves the runtimeClasspath configuration, collects them into a Set and the dumps them out to stdout. This works reasonably ok, but I'm surprised this functionality doesn't exist natively in Gradle. I'm also surprised that there hasn't been much interest in a feature like this, at least from what I've seen.
One example of a real-world use case for a feature like this is when I'm doing software license clearing in my organization. Every release, I am asked to put together a list of all of our project dependencies for export controls and license clearing. I have to do this for a handful of projects, every few months. I usually just hack together a Gradle task that prints the dependencies, but it would be easier if I could just run $ gradle --print-resolved --configuration runtimeClasspath (or something like that).
Another example is when using tools like javac and javap. In my organization, I maintain a project that uses native components so I often have to examine class files and generate C/C++ header files. These tools accept classpath options, so if I could print the compile/runtime classpath natively in Gradle, I could do something like javac -h . -cp $(gradle --print-resolved --configuration runtimeClasspath | tr '\n' ':') src/main/java/.../MyNativeClass.java.
I'm sure there are other areas where this would be useful too. Developers who aren't well versed in Groovy or Gradle APIs sometimes resort to hacking together sed commands to process the output from :dependencies like this or this. Wandering around stack overflow, it looks like this is a pretty common thing people are trying to do (example).
This feature would be handy even in the simple case of trying to find the path to a dependency to peek at it's jar contents.

Is./gradlew buildEnvironment what you are looking for, isn't it?

Is./gradlew buildEnvironment what you are looking for, isn't it?

Negative; buildEnvironment lists the depenencies of the build script.
From the docs:

Running gradle buildEnvironment visualises the buildscript dependencies of the selected project, similarly to how gradle dependencies visualizes the dependencies of the software being built.

Completely agree with this. I'm currently investigating to use the application plugin, just because it puts the classpath in scripts (one unix one windows) in the build/scripts. There are other plugins (like jib) that put the classpath in a file for further use later (and java 9+ allows the classpath to be set by referring to a file thereby avoiding the max command lengths of shells.

This simple task is naive:
task("dependencyList") {
  doFirst {
    println(configurations.runtimeClasspath.get().files.joinToString(separator = ":"))
  }
}

As it does not easily give me a list of file references as I will used them when running: they refer to a gradle cache and that's not what I want.

The classpath variable in here gives absolute paths to JARs:
https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/resources/org/gradle/api/internal/plugins/unixStartScript.txt
Hence also not very/directly useful for my use case.

This feature would be handy even in the simple case of trying to find the path to a dependency to peek at it's jar contents.

language servers would benefit greatly from this, there is a mvn equivalent that does this [1]
[1] https://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html

authors: brandon1024 cies shaneikennedy sockeqwe


text:
Build Init plugin should support adding projects to a build

The Build Init plugin should also allow adding more projects to an already initialized project. For example, one could do something like to add a new project following the template:
gradle init --type cpp-application ...
cd into-project-dir
gradle init --type cpp-library --add-project libfoobar

Would not make more sense to add submodules in that case?

authors: lacasseio xaviarias


text:
Allow a property or file collection to be finalized on next read

Context
Adds HasConfigurableValue.finalizeValueOnRead() which causes the property/file collection value to be finalized the next time the value is queried. This method allows build logic to ensure all reads of a property value see the same finalized value, but when the property value might be expensive to calculate or has not been fully configured yet.
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@melix thanks for the review. I made some changes to the Javadoc which should hopefully make the contract clearer: https://github.com/gradle/gradle/pull/11715


text:
Clarify that collections of files are accepted for SkipWhenEmpty and PathSensitive

Both annotations can be added to single file properties or file collection properties.
Fixes #17592

@bot-gradle test and merge

OK, I've already triggered a build for you.

authors: bot-gradle wolfs


text:
Automatically normalize aliases for find* methods in VersionCatalog API

Fixes #18050
I figured to make it more user friendly, we can just automatically normalize aliases.

@gradle-bot help

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle help

Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
test and merge to trigger a pre-tested commit build
cancel to cancel a running pre-tested commit build or remove it from queue
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.
Specific builds:

AST: AllSmokeTestsReadyForMerge
AFT: AllFunctionalTestsReadyForMerge
ASB: AllSpecificBuildsReadyForMerge
ACC: AllConfigCacheTestsReadyForMerge
ACT: AllCrossVersionTestsReadyForNightly
APTN: AllPerformanceTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

Makes sense, will check it.

New version for proof read:
platforms.html.zip

New version for proof read:
platforms.html.zip

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

authors: asodja bot-gradle


text:
Auto-discover classes with UpgradedProperty annotation

This introduces a new plugin gradlebuild.instrumented-project that sets the project so properties with @UpgradedProperty annotation are automatically discovered.
Annotation processor then generates interceptor classes with unique name per project, e.g. for :language-java project:
org.gradle.internal.classpath.generated.InterceptorDeclaration_PropertyUpgradesGroovyInterceptors_LanguageJava
org.gradle.internal.classpath.generated.InterceptorDeclaration_PropertyUpgradesJvmBytecode_LanguageJava

These classes are then loaded via Java SPI (done in https://github.com/gradle/gradle/pull/26015) for instrumentation.
Fixes https://github.com/gradle/gradle/issues/25990
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


text:
Treat generated API/TestKit jars as immutable

This means they will only be snapshotted once.
Previously we would snapshot them on every build.

@wolfs this is ready for your review

@wolfs No test will show an improvement with just this change. I plan to add a "clean checkout" scenario to our FirstUsePerformanceTest, which should show a significant improvement once all three changes are merged.


text:
First steps towards backporting compile avoidance to current model

Note: this pull request is done against the long living cc-java-library-plugin branch, which will contain the whole Java library compile avoidance plugin and documentation, and will only be merged when it's done. As such, all iterations will be done as pull requests on this branch.
This is the first step towards compile avoidance for the current model. This pull request introduces a new plugin, called java-library, which adds a different type of "component" for the current Java model. Libraries separate API from implementation. Therefore, the compile configuration is not used, and replaced by two distinct configurations holding dependencies: api and implementation.
Consumers of libraries will depend on the apiCompile configuration, so we end up with the following schema:

Adding a dependency to the compile configuration for a library is a failure.
Backwards compatibility works in both directions: a library can depend on a classic, legacy java project. And a java project can consume a library (in which case compile avoidance works as expected).
See: gradle/performance#180

I planned to make sure IDE support, publishing, documentation and such work in separate PRs to keep things small. Is that ok?

Yes, of course. This was just a general comment on what I think the next steps should be. Doesn't have to be in this PR.

LGTM

I'm going to merge this and rework the setup of configurations as discussed in our team meeting yesterday, using a new pull request.

authors: melix oehme


text:
feat(otelcol/connector/servicegraph): add virtual_node_peer_attributes setting to the component

PR Description
Add the virtual_node_peer_attributes setting to otelcol.connector.servicegraph. Thanks @erikbaranowski for creating the foundation already!
The default attributes are reduced to be identical to upstream
Which issue(s) this PR fixes

Closes #861
Notes to the Reviewer
PR Checklist

[x] CHANGELOG.md updated
[x] Documentation added
[x] Tests updated
[x] Config converters updated

waiting for @clayton-cornell feedback on the doc before merging it

All fine by me :D

authors: hainenber wildum

repo: grafana/alloy


text:
OATs build fixes, better HTTP error test

Changes
Updates build for .NET 8 SDK
Improves HTTP GET error controller action to return a 500, and adds OATs test looking for HTTP error span.
Merge requirement checklist

[x] Unit tests added/updated
[ ] CHANGELOG.md file updated for non-trivial changes
[ ] Changes in public API reviewed (if applicable)

Thanks for adding this. I added a few comments, related to the fact that tests aren't consistently defined with new HTTP semantic conventions.
However, even with those changes, I don't get the new error-test to pass.

The Ginkgo --focus parameter was skipping some tests due to how testcase names were being generated. This PR improves name generation.
Running Ginkgo from the OATs yaml directory should show the HTTP tests now working, even without the PR to improve focus filtering.

repo: grafana/grafana-opentelemetry-dotnet


text:
[Bug] Security context for grafana containers (use fsgroup instead in PVC example)

Describe the bug
The example to create a Grafana deployment with PVC does not follow security best practices. It requires writeable root file system and privilege escalation, which is in fact how, by default the operator sets the security context for the container if none is specified.
That causes the volume mou nt grafana-data to be read-only.
This issue #1439 identified this problem, however, it may have been misinterpreted and was closed as not planned.
I believe that was a mistake and in fact, if this was documented, it would have saved me a ton of time to find a solution that did not require a compromise on security and that was clean (without requiring running chown on an init-container, for example).
Version
v5.9.0
To Reproduce
Deploy the example grafana with PVC, but remove the lines:
securityContext:
  allowPrivilegeEscalation: true
  readOnlyRootFilesystem: false

The output from the container will be:
GF_PATHS_DATA='/var/lib/grafana' is not writable.
You may have issues with file permissions, more information here: http://docs.grafana.org/installation/docker/#migrate-to-v51-or-later
mkdir: can't create directory '/var/lib/grafana/plugins': Permission denied

Expected behavior
The expected behavior is that there are no permission issues in the file system.
Suspect component/Location where the bug might be occurring
Grafana CRD
Runtime (please complete the following information):

OS: Linux
Grafana Operator Version v5.9.0
Environment: AKS v1.28.13
Deployment type: Helm

Additional context
Deploying the Grafana with these security settings instead, resolve the issue. I'd suggest to replace the current example with something like this, or provide an additional example that includes this:
securityContext:
  fsGroup: 1001
containers:
  - name: grafana
    image: "grafana/grafana:9.4.3"
    securityContext:
      runAsUser: 1001
      runAsGroup: 1001
      runAsNonRoot: true
      allowPrivilegeEscalation: false
      capabilities:
        drop: ["ALL"]

However, we do set sensible security settings by default.

Yes, it was precisely for this reason I raised the issue.  I knew defaults were doing the way it should be so I immediately associated the explicit security context as a requirement for it to work.
In my case the pod just uses Azure Disk csi driver (no nfs or host path).
But I realize something now, grafana default runAs is 10001, whereas by default we use 1001. It think this may have been lost in translation. And I am assuming this is the cause of my issue (haven't validated yet) .
These nuances can make a difference between a minute and a day.
It would be nice to see something noting this specifically in the PVC doc (commented section would be good enough) as defaults are, by design, hidden behavior and connecting A to B in cases like this is far from obvious.
Nevertheless thank you for looking into this. I will try validating the case of runAs 1001 vs 10001. In case issue is not that, shall I create a new issue?

I've updated the docs to hopefully avoid this confusion for future users. https://github.com/grafana/grafana-operator/pull/1773
If you have more ideas on how we can communicate this better, I'll adapt the docs accordingly

@theSuess I just noticed that in your PR you use an example like my case (1001), but also allows for root. This can lead to a similar confusion where it may look like it is required to use root if you define runAs specifically.

authors: fabio-s-franco theSuess

repo: grafana/grafana-operator


text:
Broken prometheus endpoint

Hello on the latest chart: 0.4.1 I'm now getting a failure with extraConfig scraping
    extraConfig: |-
      prometheus.scrape "router_scrape" {
        job_name   = "router_scrape"
        targets = [
          {"__address__" = "192.168.1.1:9100", "instance" = "router"},
        ]
        forward_to = [prometheus.remote_write.grafana_cloud_prometheus.receiver]
        metrics_path    = "/metrics"
      }

This now claims the forward_to doesn't exist
Error: /etc/agent/config.river:409:17: component "prometheus.remote_write.grafana_cloud_prometheus.receiver" does not exist

408 |   ]
409 |   forward_to = [prometheus.remote_write.grafana_cloud_prometheus.receiver]
    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
410 |   metrics_path    = "/metrics"
Error: could not perform the initial load successfully

I'm trying to read the docs but kind of confused where that forward_to even comes from
All other metrics are flowing to grafana cloud but this appears to have started in this in my upgrade from 0.2
  values:
    cluster:
      name: my_custer
    externalServices:
      prometheus:
        host: https://prometheus-prod-36-prod-us-west-0.grafana.net
        basicAuth:
          username: "XXXX"
          password: XXXXXX

That's on me. I see in the changelog it got updated to prometheus.relabel.metrics_service in the 0.3 release

All good! Sorry for the momentary confusion.

authors: djtecha petewall


text:
Allow secret specification via environment (#102)

Adds the following environment variables:

GCLOUD_PDC_SIGNING_TOKEN
GCLOUD_HOSTED_GRAFANA_ID
GCLOUD_PDC_DOMAIN
GCLOUD_PDC_CLUSTER

These are already described as environment variables in these docs

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

Thanks for this PR @neomantra ! There's an existing WIP PR here to tackle this issue, we'll continue with that one unless it goes stale.

authors: CLAassistant dafydd-t neomantra

repo: grafana/pdc-agent


text:
Add Grafana Faro

On the Faro Grafana UI, please follow the instructions listed here to set it up on your own Grafana instance.
You can find the URL on the Web SDK configuration view:

Then, before running the docker container, add the PUBLIC_FARO_WEBSDK_URL env var to the pkg/web .env file
Here's an example session:
https://github.com/grafana/quickpizza/assets/10811379/927194b2-c207-4d13-9db4-598a9777586e

@mdcruz @dgzlopes I've pushed https://github.com/grafana/quickpizza/pull/21/commits/141d79f60b14a4ee41f8c1abbcc273f5ef45545b, that makes a small change to the init code to fetch the faro_url. I totally have no idea of what I'm doing with svelte, so please feel free to point out any javascript war crimes I might have commited.

@roobre I can't approved it since I opened the PR. Feel fee to approve and merge it  😊

authors: mdcruz roobre

repo: grafana/quickpizza


text:
No charts add-repo command available

Version
0.13.0
Problem
Official docs states that I can add chart repository into the chartfile.yaml
# Add the official Grafana repository
$ tk tool charts add-repo grafana https://grafana.github.io/helm-charts

Well... That's in contradiction to what I have experienced using Tanka:
$ tk tool charts
Declarative vendoring of Helm Charts

Usage:
  tk tool charts [command]

Available Commands:
  init        Create a new Chartfile
  add         Adds Charts to the chartfile
  vendor      Download Charts to a local folder
  config      Displays the current manifest

Flags:
  -h, --help   help for charts

Use "tk tool charts [command] --help" for more information about a command.

If I try to run the command anyways I get the error:
$ Error: unknown subcommand `add-repo`

Hey, good spot. The website is built from current master, and the commit that adds this functionality has not yet been included in any release.
Please wait for the next release, or built it yourself from master :)

Hey, good spot. The website is built from current master, and the commit that adds this functionality has not yet been included in any release.
Please wait for the next release, or built it yourself from master :)

Oh... But wait... Isn't that a matter of pointing to the right tag to build the docs? :smile:

Oh... But wait... Isn't that a matter of pointing to the right tag to build the docs? :smile:

Agreed, this leads to slight inconsistencies, but these don't appear frequent enough to justify the extra complexity it imposes on our build pipeline. If this happens a lot in the future, we might reconsider it :)
Closing as 0.14 is released, so this feature is generally available

repo: grafana/tanka


text:
Add benchmark function for getSnippetHash

This will be used to compare performance in a future PR
I also added a workflow that posts a comparison of all benchmarks in the project. If we want to improve performance elsewhere, it'll be easier to do so

Benchstat (compared to main):

The benchstat is empty because we have nothing to compare with in the main branch. However, once this is merged, the future PRs will look like https://github.com/grafana/jsonnet-language-server/pull/74#issuecomment-1243654036


text:
Odd auto formatting

If I create a jsonnet file with:
local asd(
  x=1
) = {
  hello: x,
};
asd(x=4)

It gets auto-formatted to:
local asd(
  x=1
      ) = {
  hello: x,
};
asd(x=4)

Which is really weird.
Version: 0.3.1

This is unfortunately an issue with the native jsonnet formatter:
$ echo "local asd(
  x=1
) = {
  hello: x,
};
asd(x=4)" | jsonnetfmt -

local asd(
  x=1
      ) = {
  hello: x,
};
asd(x=4)

An issue here: https://github.com/google/go-jsonnet would be better targeted

Ah, OK. Thanks! I'll file an issue there.

authors: goodspark julienduchesne

repo: grafana/vscode-jsonnet


text:
error while building docker image

Yesterday everything was fine, today when I launched the project in Jenkins I got the following error:
go.buf.build/grpc/go/prometheus/prometheus: unrecognized import path "go.buf.build/grpc/go/prometheus/prometheus": https fetch: Get "https://go.buf.build/grpc/go/prometheus/prometheus?go-get=1": dial tcp: lookup go.buf.build on 10.1.5.5:53: **no such host**
09:26:53  #12 11.31 2023/08/04 06:26:53 [INFO] Cleaning up temporary folder: /tmp/buildenv_2023-08-04-0626.2242724175
09:26:53  #12 11.31 2023/08/04 06:26:53 [FATAL] exit status 1
09:26:54  #12 ERROR: process "/bin/sh -c xk6 build --with github.com/grafana/xk6-output-influxdb=. --output /tmp/k6" **did not complete successfully**: exit code: 1

I see we have an incorrect link to: buf.build

Hi @boykoai, thanks for reporting it. We are actively working on a patch for it.

In the meantime, you should be able to use the -replace directive as a workaround:
xk6 build --with github.com/grafana/xk6-output-influxdb --replace go.buf.build/grpc/go/prometheus/prometheus=buf.build/gen/go/prometheus/prometheus/protocolbuffers/go@latest --replace go.buf.build/grpc/go/gogo/protobuf=buf.build/gen/go/gogo/protobuf/protocolbuffers/go@latest

A patch has been released the following command should now build successfully. I close, feel free to re-open in case of unexpected results.
xk6 build --with github.com/grafana/xk6-output-influxdb@latest

Thanks It works!

authors: boykoai codebien


text:
Bugfix: Decode got error while #EXT-X-PROGRAM-DATE-TIME exists in media playlist

fix: #120

Coverage increased (+0.5%) to 71.845% when pulling 55ed9468382dba0d32c5bf5e4018ec291c91384c on lei-pub:master into 6ab8f28ed427e7ab787340596709e27ecc4b32db on grafov:master.

authors: coveralls lei-pub


text:
🛑 Grambling State University is down

In b83c338, Grambling State University (https://www.gram.edu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grambling State University is back up in 875ed15 after 1 hour, 18 minutes.

repo: gramblingstatewebmaster/upptime


text:
Buttons with link end with "?" on mobile apps

It probably is the telegram app mobile bug (on iPhone) but if I try to add InlineKeyboard with a link on mobile automatically adds the ? symbol at the end.
Bad (mobile)Correct (desktop)

Why this is a problem?
Links like https://open.spotify.com/playlist/2vU2GttfgSOGsnmFZuKRK4?si=cc86ded6f77b4e4c with two ? don't open Spotify app. Give the error "playlist not found".

Are you sure this ? character isn't just shown in the popup as part of the question? Try opening it, it should point to the correct URL.

Closing because of inactivity.

authors: KnorpelSenf ptkdev

repo: grammyjs/grammY


text:
Clarification: Startup projects

Fantastic work! I have been messing around with these areas for about 2 months and still stuck. A quick question on the readme document. I have downloaded the project as-is, set the database connections, and run the migrations.

Which projects should be set in as startups for debugging?
Is the IdentityServer already part of the solution or do I download the link to it you provided in the readme?

Thanks again!

Thanks @VR-Architect.
If you haven't already it is probably worth taking a look at my blazor solution setup repository, on which Headway is based.

Startup projects
Section 9 of the blazor solution setup readme talks about running the solution with multiple startup projects.

Authentication
The Headway solution is currently configured to use Auth0 as the identity provider.  The readme of my blazor auth0 repository walks through the Auth0 setup and configuration steps.
There is also the option to switch to IdentityServer4 instead. This is covered under Identity Providers of the Headway readme. The project for IdentityServer4 is already available in the Utilities folder of the Headway solution and details of how to integrate it can be found in Section 3 of the my blazor solution setup repository.

Further to above, when using Auth0 as the authentication provider the startup projects will include the following:

authors: VR-Architect grantcolley

repo: grantcolley/headway


text:
Upgrade to react-router-v4

What changes here when using declarative routing?

+1 on updating this example to v4

Thanks to @sebasibarguen for the update 🙂

authors: arrygoo marktani mvanlonden


text:
Create standalone package graphql-playground-middleware

To make it easier/faster to install a middleware as part of a GraphQL server there should be a standalone package for graphql-playground-middleware which embeds a pre-built minified GraphQL Playground version.

It's released and documented in the Readme.

authors: schickling timsuchanek

repo: graphcool/graphql-playground


text:
Create subgraph from existing contract failed on ABI

I had an issue creating a subgraph from an existing deployed contract.
Following this command:
graph init \
  --from-contract <CONTRACT_ADDRESS> \
  --network rinkeby \
  --abi 'path/to/.json' \
  <GITHUB_USER>/<SUBGRAPH_NAME> [<DIRECTORY>]

I received the error: ✖ Failed to fetch ABI from Etherscan: Unexpected token C in JSON at position 0
and quit the process.
I then ran:
graph init \
  --from-contract <CONTRACT_ADDRESS> \
  <GITHUB_USER>/<SUBGRAPH_NAME> [<DIRECTORY>]

which allowed me to setup the project directory as I answered the prompts successively.
I thought it was the abi file at first, but when I walked through the prompts, the process finished.

I could reproduce something similar when trying to use an ABI from a path by following the graph init interactive prompt, failing with TypeError: abi.filter is not a function.

Fixed by #255.

authors: Jannis leodasvacas tobyjaguar

repo: graphprotocol/graph-cli


text:
graphnode onluy accepting connections from localhost

BUG
I deployed the graph-node docker container to a server.
However, it seems that docker-node is only accepting connections from localhost and producing the following error:
2022-01-19 02:53:39.51 UTCgraph-node-f5bff88b-vgmvngraph-nodeJan 19 02:53:39.514 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer

Is there a way, I can change this for graph-node's docker container to accept connections from 0.0.0.0?
A setting somewhere?

It would be helpful if you could share which commands you are using to run that container, so we can better understand what is going on.
Can you confirm that the container ports are being exposed to the host when you run that container?
Also, the log line you showed is not an error, it's just an info message telling that the admin server is up.

authors: RongxinZhang tilacog

repo: graphprotocol/graph-node


text:
lifetime may not live long enough

error: lifetime may not live long enough
--> chain/substreams/src/trigger.rs:191:50
|
179 |       async fn process_trigger(
|       ----- lifetime 'async_trait defined here
...
182 |           : Box<dyn Iterator<Item = &T::Host> + Send + '>,
|           - has type Box<(dyn Iterator<Item = &<T as graph::prelude::RuntimeHostBuilder<chain::Chain>>::Host> + std::marker::Send + '1)>
...
191 |       ) -> Result<BlockState, MappingError> {
|  _____________________________________________^
192 | |         for entity_change in block.changes.entity_changes.iter() {
193 | |             match entity_change.operation() {
194 | |                 Operation::Unset => {
...   |
286 | |         Ok(state)
287 | |     }
| |^ associated function was supposed to return data with lifetime 'async_trait but it is returning data with lifetime '1
error: could not compile graph-chain-substreams due to previous error

use cargo update. , will get this question issues

Closing since the issue seems to be resolved and compilation passes for all developers AFAIK. If it's not solve, check your Rust version.

authors: maoueh supermigo


text:
Update all links to October 2021 spec (#1000)

Solution
Last step of transition to the new spec is updating all the links.
Checklist

Created PR:

[x] In draft mode
[x] Name contains Draft:  prefix
[x] Name contains issue reference
[x] Has assignee

[x] Documentation is updated (if required)
[x] Tests are updated (if required)
[x] Changes conform code style
[x] CHANGELOG entry is added (if required)
[ ] FCM (final commit message) is posted

[ ] and approved

[ ] Review is completed and changes are approved
Before merge:

[ ] Milestone is set
[ ] PR's name and description are correct and up-to-date
[ ] Draft:  prefix is removed
[ ] All temporary labels are removed

FCM
Update all links to October 2021 spec (#1075, #1000)

repo: graphql-rust/juniper


text:
Add example for theming

After releasing the updated UI in graphiql@2 users will be able to override our CSS variables to create their own theme (colors, spacing, etc.) for GraphiQL. We should also add an example to the examples folder that demonstrates how to make this happen.

We can add to one of the webpack/vite/etc examples, but ideally a bundler-free config as well. From rough estimates from CDN stats and NPM stats, about half our users still don't even use a bundler to configure/ship their custom graphiql implementation!

it would be cool if we linked to open source framework implementations of graphiql with custom 2.x themes. We can work with the authors of the implementations in this list to improve if needed
@patrick91 would you and @benjie like for your frameworks to be on this list? Do you do or need much more style customization? @lekoarts would love to make the gatsby custom theme implementation a point of reference as well! Let us know what improvements we can make

@patrick91 would you and @benjie like for your frameworks to be on this list? Do you do or need much more style customization? @LekoArts would love to make the gatsby custom theme implementation a point of reference as well! Let us know what improvements we can make.

I haven't done any custom theme yet, but I think we might do something at somepoint 😊, so yes!

I'll be releasing a new PostGraphiQL along with PostGraphile V5 sometime next year, so no point linking to our old one since it's way out of date. Will definitely be in touch for help at the relevant times though - thanks!

@acao I've been playing a bit with theming and the way it is currently setup makes it quite difficult to customise things, if I understood correctly we should be able to use the following variables:
.graphiql-container,
.CodeMirror-info,
.CodeMirror-lint-tooltip,
reach-portal {
  --color-primary: 52, 99%, 57%;
  --color-secondary: 243, 100%, 77%;
  --color-tertiary: 188, 100%, 44%;
  --color-info: 208, 100%, 72%;
  --color-success: 158, 100%, 42%;
  --color-warning: 30, 100%, 80%;
  --color-error: 13, 100%, 58%;
  --color-neutral: 253, 82%, 30%;
  --color-base: 219, 29%, 18%;

  --popover-box-shadow: none;
  --popover-border: 1px solid hsl(var(--color-neutral));
}

to customise the colors, but they are usually used in combination with hsla, which makes it difficult to have a specific color for a specific section, for example both the background and the text color depend on --color-neutral
maybe we can have more granular variables, that default on the current values?

Having separate variables to control font and background colors make sense to me! @patrick91 Would you mind opening a dedicated issue for that? Do you run into more problems where you'd need more control?

authors: acao benjie patrick91 thomasheyenbrock

repo: graphql/graphiql


text:
Ronak/update graphcms

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 250 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~10 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

LGTM

Thanks @brianwarner 🙌

repo: graphql/graphql-landscape


text:
Let teams decide for themselves how money is split.

Right now you've got a lot of very ideological and complicated code in how teams get paid out.

Please note that no one, not even the team account owner, can change a member's take. The team account owner can only add or remove members.

That's simply not practical for a lot of projects.
I'd suggest having a bunch of different methods for managing team payments, including what you have now and completely central management by the team owner.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

+1 @elliottw at https://github.com/gratipay/gratipay.com/issues/3480#issuecomment-106038415:

instead of the kids eat first/double your income each week,
team decides on distribution, if team is size=1 then it's a no brainer
if no one makes a decision funds are split equally?? or some slightly smarter algorithm
I think the algorithm with which teams distribute funds has more social impact than most other parts of the app. I'd be curious about a model like "older kids look after younger kids" which I guess would be little like trickle down economics, but now that I type it, it doesn't sound so great.

Closing in light of our decision to shut down Gratipay.
Thank you all for a great run, and I'm sorry it didn't work out! 😞  💃


text:
revise team application

Now that we have received 79 applications, let's think about some tweaks to the application to make sure it's doing what we want.
I think the product or service question is pretty straightforward and I think is fine.
Revenue model tends to see these three responses:

"We ask people for money."
"We have no revenue model."
@wout's answer :)

This question is controversial, but I think that means it's working as intended. The point of this question is to filter out people who are thinking in terms of building a viable open business from those who aren't.
For Contributing I think we can drop back from an open-ended textarea to a link to contributor documentation or at least an issue tracker. We should specify that this is where we expect to find a list of available open work that's ready to start without having to explicitly apply first.
Paying contributors really comes down to "kids eat first" or "parents eat first." I think we should allow both when we bring back payroll (#3433), and this part of the application will simply be a select between those two options. One pattern we're seeing is that nobody is making any revenue, so they aren't at a place where they can really think about sharing it. They're reluctant to make promises to share revenue when they themselves are not receiving enough yet. I think we want to keep "everyone sets their own take" but allow for "parents eat first."

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/25709058-revise-team-application?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

The point of this question is to filter out people who are thinking in terms of building a viable open business from those who aren't.

This implies that you only want people who have any sort of business sense and are focused on that area rather than doing whatever it is that they do.  If the goal of Gratipay is to help push open projects (meaning minimum barrier to contribution), why are we setting a barrier to entry of "treating this project as a moneymaking endeavor"?
That's not to say we shouldn't ask about revenue model, but maybe it should be phrased in such a way as "Many teams currently have no revenue stream.  If your team started generating revenue through Gratipay, how would you spend it?"  But what is the answer that "fits" with Gratipay's mission and brand guidelines?
Contributing looks good, and I think the criteria of "Does this team have a well-documented method for new people to contribute" is much stronger for accept/close team choices.
(The TechRaptor model of "Send us your contribution and we'll decide whether it fits" is, IMHO, within the bounds of Gratipay in the same way I can submit a PR to any project on GitHub--although not all GitHub projects have documentation explaining how people can get involved.)

Darn it, here I am mixing policy discussions into the technical side of things.  Didn't mean to do that.

Darn it, here I am mixing policy discussions into the technical side of things. Didn't mean to do that.

No! Your comment is fine here. The proposal on this ticket is to modify code, specifically our application form, and of course that does get us into some policy questions.

Actually, you're right. Let's close this as a dupe of #3677.

Sorry. :)


text:
Document types of available channels

It's hard to discover the types of channels (triggers) available to force. It would be great to include them in the docs.

this is done at least for MVP in plugins section

authors: klizhentas pierrebeaucamp

repo: gravitational/force


text:
Add gravity to release tarball.

Add gravity binary to the release tarball users download from our Downloads page.
I also added it to the enterprise installer script - I realize this won't actually have effect until we somehow manage to upgrade our get.gravitational.io, but I figured I'd add it there anyway.
About https://github.com/gravitational/gravity/issues/1189.

Should terraform-provider-gravity also be included too?  It seems to be treated in a similar manner elsewhere in our Makefiles:
https://github.com/gravitational/gravity/blob/229a0f96774a4f052bfd3062c79bd24a9568c249/Makefile#L203
I'm not familiar enough with the use of these different binaries to be sure, just pattern matching after spending lots of time looking at the Makefiles.

I'm not sure I understand why this is changing?

We need to add gravity binary to our release tarballs because our new quickstart cli flows are going to use it for certain things (like, installing apps into existing clusters) and otherwise users have no idea where to get it from.

authors: knisbet r0mant wadells

repo: gravitational/gravity


text:
Issue/8071 store i18n dictionary

:id:
Fixes #8071
:pencil2: A description of the changes proposed in the pull request
All of the work required to create, read, update and delete i18n dictionaries and their translations:
Backend
REST resource, service and mongo/jdbc repository implementations, testcontainer test, Jest integration testing.
All the files under gravitee-am-test/api/management have been generated by the OpenApi generator tool and can be ignored for review purposes.
Frontend
New form added to Domain settings for CRUDing dictionaries and adding/removing translations.
:computer:

Few comments on the UI:
We can add two languages with the same code, this will probably lead to unexpected behaviour as the underlying i18n mechanism will probably take care of the first one (or last one). Also we may provide a dropdown list of supported code filtered based on the user input like proposed in figma.
The screen doesn't match the one provided in figma:

there is a "SAVE CHANGES" button in the language section that is missing in your version
the "SAVE CHANGES" button in the Translation section use the wrong background color and when there are no new entries, it should be deisabled.
the "Edit in a File" tab visible in figma is missing, so the user can't upload a properties files with all the translation at once.

About the default language, I wondering if we should enable the defaultLocale option by default for the first language created and when a language with the default flag is deleted, maybe we should enable this flag on the first language of the list to be sure that there will be a default language? wdyt ?

Yes I think that's a good idea. What about Audrey's suggestion that a sole language can't be deleted?
If we're going to provide a list of codes, don't you agree that we should provide a list of display names as well? There are libraries that can provide this, I believe. The only snag is that the lists will need to be language specific (e.g. "Deutsch" for ger when the user's browser settings are in German).

When a domain is deleted, we do not clean the related dictionaries. We should clean all of them to avoid orphan data https://github.com/gravitee-io/gravitee-access-management/blob/master/gravitee-am-service/src/main/java/io/gravitee/am/service/impl/DomainServiceImpl.java#L371

Done.

UI comments :

Default locale checkbox is useless in the table list
Do not push the package-lock.json file

I'm working against the figma screens designed by Audrey and agreed by John and Eric which feature a toggle for default_locale. I thought the plan was to move default_locale to the Domain but that still needs the toggle in order to set it, surely?

repo: gravitee-io/gravitee-access-management


text:
chore: disable turbosnap on chromatic

Description
Remove only-changed turbosnap option
Additional context

🧪  Gravitee.io Automatic Prerelease @gravitee/ui-policy-studio-angular
npm install @gravitee/ui-policy-studio-angular@12.0.0-disable-chromatic-turbosnap-636dfd5

yarn add @gravitee/ui-policy-studio-angular@12.0.0-disable-chromatic-turbosnap-636dfd5

🧪  Gravitee.io Automatic Prerelease @gravitee/ui-particles-angular
npm install @gravitee/ui-particles-angular@12.0.0-disable-chromatic-turbosnap-636dfd5

yarn add @gravitee/ui-particles-angular@12.0.0-disable-chromatic-turbosnap-636dfd5

📚  View the storybook of this branch here

:tada: This PR is included in version 12.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: Okhelifi graviteeio

repo: gravitee-io/gravitee-ui-particles


text:
Feature points

added point plotting

Codecov Report

Merging #17 into master will increase coverage by 1.26%.
The diff coverage is 98.11%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
+ Coverage   57.42%   58.69%   +1.26%
==========================================
  Files          35       36       +1
  Lines        2551     2600      +49
==========================================
+ Hits         1465     1526      +61
+ Misses       1086     1074      -12

Impacted Files
Coverage Δ

gbmgeometry/spacecraft/fermi.py
54.92% <ø> (ø)

gbmgeometry/utils/plotting/sky_point.py
97.14% <97.14%> (ø)

gbmgeometry/test/test_plotting.py
100.00% <100.00%> (ø)

gbmgeometry/utils/array_to_cmap.py
88.88% <100.00%> (+55.55%)
:arrow_up:

gbmgeometry/utils/plotting/space_plot.py
40.78% <100.00%> (+1.60%)
:arrow_up:

gbmgeometry/utils/gbm_time.py
60.60% <0.00%> (+12.12%)
:arrow_up:

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 2bbb407...44b4a2b. Read the comment docs.

authors: codecov-io grburgess

repo: grburgess/gbmgeometry


text:
Figure Tweaks

I converted figures for my paper into panels so it will be easier to read. This PR is huge; HOWEVER, you do not need to review anything except this notebook link below:
figure_generation/manuscript_figure_generation.ipynb
figure_generation/manuscript_figure_generation.py

wow, svg utils looks awesome... I wish I had formatted everything this way for my manuscript. I love the organization of the repo.
fyi, pathlib overloads the "/" operator so you can do nifty things like
panel_one = sg.fromfile(publication_delay_path / "article_distance_vs_publication_time.svg")

instead of:
panel_one = (
    sg.fromfile(f"{str(publication_delay_path)}/article_distance_vs_publication_time.svg")
)

and it will probably work (depending on if sg does anything goofy with opening files)
for figure aesthetics, I might also sort figure 4c to make it easier to compare them.
I also wouldn't mind tweaking or making some alternatives of some of figure 4's panels if you'd be ok with it.

for figure aesthetics, I might also sort figure 4c to make it easier to compare them.

Sounds good! Will do.

I also wouldn't mind tweaking or making some alternatives of some of figure 4's panels if you'd be ok with it.

Sure go for it! Just please keep the color theme consistent. Feel free to commit to this branch or make a separate pull request. Up to you!

repo: greenelab/annorxiver


text:
breakfix: id_token signed with unsupported algorithm

Describe the issue
Attempting OIDC integration with Fusion Auth. Previously successful setting up with Keycloak. Getting the following error:
{"level":"warn","ts":1679792857.4263055,"logger":"security","msg":"Authentication failed","session_id":"k7BE2j8WU85wfLSuH8C85WbxrxNFjTDtqvt2FxPoAi2","request_id":"d6c479e7-1776-4540-904f-35ee764c69c4","error":"failed validating OAuth 2.0 access token: OAuth 2.0 failed to parse id_token: OAuth 2.0 id_token signed with unsupported algorithm: HS256"}

Configuration
{
	# do not attempt to install certs on the docker container
	skip_install_trust

	# security settings
	order authenticate before respond
	order authorize before basicauth

	security {
		oauth identity provider <mydomain> {
			delay_start 5
			driver generic
			realm <mydomain>
			client_id 3e6c5bd0-e0fa-431d-b588-c06c10062578
			client_secret <redacted>
			scopes openid email profile
			metadata_url https://login.<mydomain>/.well-known/openid-configuration/a17c408d-98d6-2805-711d-03f6fcd191cd
		}

		authentication portal defaultAuth {
			crypto default token lifetime 3600
			crypto key sign-verify <redacted>
			enable identity provider <mydomain>
			cookie domain *.<mydomain>.com.au
			ui {
				links {
					"dev.<mydomain>.com.au" https://dev.<mydomain>.com.au/?folder=/mnt/containers icon "las la-star"
					"dev-hs-ui.<mydomain>.com.au" https://dev-hs-ui.<mydomain>.com.au/ icon "las la-star"
					"My Identity" "/whoami" icon "las la-user"
				}
			}
			transform user {
				match origin <mydomain>
				action add role authp/user
			}
		}

		authorization policy defaultPolicy {
			set auth url https://sso.<mydomain>.com.au
			allow roles authp/user
			crypto key verify <redacted>
		}
	}
}

Version Information
Provide output of caddy list-modules -versions | grep git below:
dns.providers.cloudflare
http.authentication.providers.authorizer
http.handlers.authenticator
security

  Non-standard modules: 4

Expected behavior
Successful Login

As a note it does appear (as the error code implies) that fusionauth defaults to HS256 for signing its tokens. By downgrading to RSA256

repo: greenpau/caddy-security


text:
breakfix: Injected headers not present

I'm trying to inject headers following the forward_auth / Trusted Header SSO pattern with a local users.json, but some of the headers are not present.
Configuration

Expand to see full Caddyfile configuration:

{
	security {
		local identity store localdb {
			realm local
			path ./users.json
		}

		authentication portal myportal {
			enable identity store localdb
			ui {
				links {
					"App" "http://127.0.0.1:8080" icon "las la-user"
					"My Identity" "http://127.0.0.1:8081/whoami" icon "las la-user"
				}
			}
		}

		authorization policy maybe_authorized {
			set auth url http://127.0.0.1:8081/
			allow roles authp/admin authp/user
			# inject headers with claims
			enable strip token
			inject header "Remote-Name" from "name"
			inject header "Remote-User" from "username"
			inject header "Remote-Email" from "email_address"
			inject header "Remote-Groups" from "roles"
		}
	}
}

:8081 {
	route {
		authenticate with myportal
	}
}

:8080 {
	route /assets/* {
		file_server {
			root context/
		}
	}

	route {
		authorize with maybe_authorized

		respond "custom responder that prints headers"
	}
}

Expand to see users.json:

Note: password is password
{
    "version": "1.1.2",
    "policy": {
        "password": {
            "keep_versions": 10,
            "min_length": 8,
            "max_length": 128,
            "require_uppercase": false,
            "require_lowercase": false,
            "require_number": false,
            "require_non_alpha_numeric": false,
            "block_reuse": false,
            "block_password_change": false
        },
        "user": {
            "min_length": 3,
            "max_length": 50,
            "allow_non_alpha_numeric": false,
            "allow_uppercase": false
        }
    },
    "revision": 3,
    "last_modified": "2023-08-24T01:57:05.436695797Z",
    "users": [
        {
            "id": "39555452-454e-4c85-829b-8195a8dd8c81",
            "username": "Correct1596",
            "name": {
                "first": "John",
                "last": "Smith"
            },
            "email_address": {
                "address": "jsmith@example.com",
                "domain": "example.com"
            },
            "passwords": [
                {
                    "purpose": "generic",
                    "algorithm": "bcrypt",
                    "hash": "$2a$10$oBl7f1PCSi7mqlzOKEjFNeXisAnikYBhasiyl8RcpPgVT4L1t4tWe",
                    "cost": 10,
                    "expired_at": "0001-01-01T00:00:00Z",
                    "created_at": "2021-10-25T17:04:58.4251263Z",
                    "disabled_at": "0001-01-01T00:00:00Z"
                }
            ],
            "created": "0001-01-01T00:00:00Z",
            "last_modified": "0001-01-01T00:00:00Z",
            "roles": [
                {
                    "name": "admin",
                    "organization": "authp"
                }
            ]
        }
    ]
}

Version Information
./caddy list-modules --versions | grep security
security v1.1.20

Expected behavior

✔ I do see Remote-Name = "Smith, John" and Remote-Groups = "authp/user" as I expect
❌ I don't see Remote-Email or Remote-User at all. I guess from "username" and from "email_address" are trying the wrong fields to select, but I don't know what the right fields are or how to identify them.

@infogulch , did you try experimenting with the following? https://authp.github.io/docs/authorize/headers#custom-headers

@infogulch , please provide the decoded claims of the token.

custom headers url

Yes that's where I started from.

decode the token

Ah thank you for the pointer, I was able to solve it with that hint.

✔ From this I was able to get username with inject header "Remote-User" from "sub", now I see Remote-User: Correct1596
✔ I had to use inject header "Remote-Email" from "email", and add "email_addresses: [ { "address": "jsmith@example.com", "domain": "example.com" } ] to users.json, and now I see Remote-Email: jsmith@example.com

✔ I now understand that the selector portion of inject header "x" from "selector" comes from jwt fields.
❓ What is the point of the "email_address": {"address": "..", "domain": ".."} field? At least it does not interact with jwt fields.
❌  I still don't understand how users.json data is mapped jwt fields.

authors: greenpau infogulch


text:
Enforce type on queries

If:

Entity_ would be a a generic type like Entity_<Entity>
each property would also be a generic type like Property<Entity>
the QueryBuilder#equal method (and others) would take Property<Entity> as arguments

then the IDE would warn in case of the following statement:
boxForA.query().equal(propertyForB, 42L).build()

(mixing a property of entity B against the box for A)
What do you think?

As long as we use classes/objects/types that are strongly tied with entities, I'm fine.
I want to go away from Active Android because of the queries that use static column names (.where("column_name = ?", 42L)), it's so prone to errors that I want to avoid that. The IDE needs to be aware of what we're doing so it can help us identify issues.
So, either solution would be fine for me!

repo: greenrobot/ObjectBox


text:
Issue: can't convert nil into Hash (TypeError) during active admin insdtall

I'm on ruby-1.9.3-p0
Rails 3.2.1
Pretty vanilla install...
When I run the rails generate active_admin:install, I get an error:
/Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:217:in `merge!': can't convert nil into Hash (TypeError)
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:217:in `block in revive_hash'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:211:in `each'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:211:in `each_slice'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:211:in `revive_hash'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:123:in `visit_Psych_Nodes_Mapping'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:16:in `accept'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:226:in `block in revive_hash'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:211:in `each'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:211:in `each_slice'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:211:in `revive_hash'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:123:in `visit_Psych_Nodes_Mapping'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/visitor.rb:15:in `visit'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/visitor.rb:5:in `accept'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/visitors/to_ruby.rb:16:in `accept'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/nodes/node.rb:35:in `to_ruby'
	from /Users/xxx/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych.rb:113:in `load'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/application/configuration.rb:115:in `database_configuration'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activerecord-3.2.1/lib/active_record/railtie.rb:75:in `block (2 levels) in <class:Railtie>'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/lazy_load_hooks.rb:26:in `on_load'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activerecord-3.2.1/lib/active_record/railtie.rb:74:in `block in <class:Railtie>'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/initializable.rb:30:in `instance_exec'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/initializable.rb:30:in `run'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/initializable.rb:55:in `block in run_initializers'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/initializable.rb:54:in `each'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/initializable.rb:54:in `run_initializers'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/application.rb:136:in `initialize!'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/railtie/configurable.rb:30:in `method_missing'
	from /Users/xxx/Development/doctors-tool-ruby/config/environment.rb:5:in `<top (required)>'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:251:in `require'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:251:in `block in require'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:236:in `load_dependency'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/activesupport-3.2.1/lib/active_support/dependencies.rb:251:in `require'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/application.rb:103:in `require_environment!'
	from /Users/xxx/.rvm/gems/ruby-1.9.3-p0@heroku-cedar/gems/railties-3.2.1/lib/rails/commands.rb:25:in `<top (required)>'
	from script/rails:6:in `require'
	from script/rails:6:in `<main>'

Your stack trace clearly shows that it's a problem with psych.

authors: dgdosen latortuga


text:
A .AeonConfig sample file will be welcome

Basically, to know how to set "virtual" disks or how to mount a drive using a local path.
And other usual things.
Looking at the classes AeonConfiguration and AeonDriveConfiguration I can guess, but to be sure :-)
Thanks in advance.
Guillermo

I'll publish some examples soon. That format started out as xml, then was yaml, and now is finally json. I probably won't change it again... :)
I had planned to add some configuration UI back in too, eventually.
-Greg

I've added a few basic examples in https://github.com/gregdivis/Aeon/tree/master/examples - I'll document the format more as I get time. Is that enough for now?

I've added a few basic examples in https://github.com/gregdivis/Aeon/tree/master/examples - I'll document the format more as I get time. Is that enough for now?

Yes, thank you! 😃

authors: elGuille-info gregdivis

repo: gregdivis/Aeon


text:
Internal vs External SEC Geometry

I've noticed some unexpected behavior while trying to decompose ground magnetic field observations into a combination of external and internal SECS (as in the Pulkkinen et al. EPS 2003 paper). With two sets of SECS, one external shell (at say R_Earth + 100km) and one internal shell (at say R_Earth - 30km), I would expect the resulting current vectors to be generally pointing in the opposite direction (since currents have to move in the opposite direction across the observation plane in order to produce magnetic fields pointing in the same direction on that plane). However, the SECS decomposition algorithm returns currents that point in the same direction regardless of the shell height with respect to observations (so regardless of whether the shell is positioned above or below the Earth's surface).
This synthetic example (adapted from the notebook example) demonstrates the problem:
import numpy as np
from pySECS import SECS
import matplotlib.pyplot as plt
import cartopy
import cartopy.crs as ccrs
import cartopy.feature as cfeature

R_E = 6371.e3
sec_height = -30.e3

# place current system under Golden CO
sec_loc = np.array([39.7555, -105.2211, R_E + sec_height])

# set up divergence-free current system
system_df = SECS(sec_df_loc=sec_loc)
system_df.fit_unit_currents()
system_df.sec_amps *= 10000.

# prediction grid
lats = np.arange(30.5, 50.5, 1.)
lons = np.arange(-125.5, -85.5, 1.)
lat_secs, lon_secs = np.meshgrid(lats, lons)
lat_secs = lat_secs.flatten()
lon_secs = lon_secs.flatten()

secs_current_coords = np.column_stack((lat_secs, lon_secs, (R_E + sec_height) * np.ones(lat_secs.size)))
secs_bfield_coords = np.column_stack((lat_secs, lon_secs, R_E * np.ones(lat_secs.size)))

# predict stuff
j = system_df.predict_J(secs_current_coords)
b = system_df.predict_B(secs_bfield_coords)

# plot
scale = '10m'
coast = cfeature.NaturalEarthFeature(category='physical', scale=scale, edgecolor='k',
                                     facecolor='none', name='coastline')
countries = cfeature.NaturalEarthFeature(category='cultural', scale=scale, edgecolor='k',
                                         facecolor='none', name='admin_0_countries')

projection = ccrs.LambertConformal(central_longitude=-96.0, central_latitude=39.0,
                                   standard_parallels=(33., 45.))
proj_data = ccrs.PlateCarree()

fig = plt.figure(figsize=(20., 14.))

ax_j = fig.add_subplot(121, projection=projection)
ax_j.set_title("Currents @ {:.0f} km".format(sec_height/1.e3))
ax_j.add_feature(coast)
ax_j.add_feature(countries)
ax_j.set_xlim([-3.e6, 3.e6])
ax_j.set_ylim([-2.e6, 2.e6])
ax_j.quiver(secs_current_coords[:, 1], secs_current_coords[:, 0], j[:, 1], j[:, 0],
            transform=proj_data, regrid_shape=30, color='r', zorder=9)

ax_b = fig.add_subplot(122, projection=projection)
ax_b.set_title("Surface Magnetic Fields")
ax_b.add_feature(coast)
ax_b.add_feature(countries)
ax_b.set_xlim([-3.e6, 3.e6])
ax_b.set_ylim([-2.e6, 2.e6])
ax_b.quiver(secs_bfield_coords[:, 1], secs_bfield_coords[:, 0], b[:, 1], b[:, 0],
            transform=proj_data, regrid_shape=30, color='b', zorder=9)

plt.subplots_adjust(hspace=0.01, wspace=0.01, top=0.95)
plt.show()

The resulting output looks like this:

For counter-clockwise current loops underneath the observer (so within the Earth, r < R_Earth), the magnetic fields should be pointing radially outward, the opposite of what the algorithm returns. The output at the Earth's surface makes sense when SECS are placed outside the Earth (r > R_Earth), as the predicted magnetic fields point radially inwards. But B still points radially inwards for SECS placed inside the Earth. In general, for this single SEC example, B points radially inwards regardless of where the SEC is placed with respect to the observation shell.
I think the problem might have to do with the last few lines of the T_df function in secs.py (lines 295-297):
https://github.com/greglucas/pySECS/blob/198d8151791c9910c302b1fbba85eb61bf971c87/pySECS/secs.py#L292-L297
Since the equations for B_theta are in a spherical coordinate system with respect to the SEC pole, you have to do something to get B_theta into the observation (global, geomagnetic) coordinate system, hence these few lines of code. It looks like the factor of -1 in lines 295 and 296 (on the Bx and By components) are intended to flip the decomposed B_theta to point towards the SEC pole. This will be correct for SECS above observation locations (e.g., above the Earth's surface) but will not be correct for SECS below the observation locations.
I might be misunderstanding what's going on in the code and therefore be wrong about this, but I do get results that look correct (with the radial direction of B changing when moving the SECS from outside to inside the Earth) when I change this geometry factor in my copy of the code. I think the change at the end of the T_df function should be fairly simple:
geometry_factor = - np.ones(Btheta.shape)
under_locs = sec_r < obs_r
geometry_factor[under_locs] = 1.

# Transform back to Bx, By, Bz at each local point
T = np.empty((nobs, 3, nsec))
# alpha == angle (from cartesian x-axis (By), going towards y-axis (Bx))
T[:, 0, :] = geometry_factor * Btheta * np.sin(alpha)
T[:, 1, :] = geometry_factor * Btheta * np.cos(alpha)
T[:, 2, :] = -Br

(Br should still be multiplied by -1 to swap between r being radially outward from the Earth and geomagnetic Z pointing towards the center of the Earth.)
If you think I'm correct about all this, happy to take out a PR with the fix. And thanks for nicely coding up this algorithm -- it's been wonderfully quick and easy to get this working.

@bmurphy-usgs, that is an excellent write-up! Admittedly, I have not used interior SECS, so I did not pay as much attention to that use case (other than putting the flag in). I think you are correct that due to my "simplifying" angle transforms with the directions that the factors should change when going through the plane of data.
It would be most excellent if you could make a PR with this change. Note that @erigler-usgs might be interested in this update as well and have comments about it. I know he was in the process of making an official release of pySECS through the USGS.

I would only suggest that, prior to accepting @bmurphy-usgs's PR, we test against my original code at https://github.com/usgs/geomag-imp. Not because I trust my own ability to do spherical geometry properly, but because I did at least test against Antti Pulkkinnen's original Matlab code, which I'm pretty sure was once checked thoroughly by Olaf Amm, the original author of this technique. I'm happy to help make this happen.

@erigler-usgs, that sounds good, I'll work on getting your original version working with my test cases and let you know if I have any questions

I just went through and checked the equations from the original paper
a little more thoroughly and if you look at equation A.8, I am missing the minus sign in that calculation:
https://github.com/greglucas/pySECS/blob/198d8151791c9910c302b1fbba85eb61bf971c87/pySECS/secs.py#L284
So, rather than needing a geometry factor, I think the negative just needs to be put on that line. Ben could you test that fix out and make that small PR if that solves the issue? Then we can address other tests of codes into a separate PR if more errors are found. But, after reading through the paper again I'm pretty sure I just mistyped that equation...

Sure enough, that fix will probably have the same effect as my hack-y -1 multiplication. Thought I had checked equations A.7 and A.8, but I guess I just didn't pay close enough attention. I'll try this and see how things look.

Yep that seems to have fixed it. And a better fix than my hacky work around. I'll take out a PR to update this. Should I also update the version tag to 0.0.2?

Yes, please feel free to update the version tag. Then once we get some more concrete tests added in we can make a 0.1 release.

@bmurphy-usgs I just pushed a lot of new stuff up so you will need to rebase when making the PR. I added a test that is currently failing and will hopefully pass with your change to close this issue.

@bmurphy-usgs just pinging you to see if you've had a chance to look into the PR any more?

@greglucas, quick PR (#3) fixes the missing minus sign issue, which does seem to fix this internal vs external problem. If the PR looks OK, we can close this issue. But I'd also like to get in some more rigorous tests comparing @erigler-usgs's original SECS code to this code sometime soon under an additional PR. Haven't really looked at the tests you've implemented yet, but this could go along with those (I'm envisioning some direct comparison of output between the two codes).

authors: bmurphy-usgs erigler-usgs greglucas

repo: greglucas/pySECS


text:
coverage on CI

This is pending due to https://github.com/codeclimate/test-reporter/issues/418.
How hard can it be to re-format some json into this?

@fede-moya My badge still shows questions marks. Can you see why? I’m merging to see how the coverage badge looks on main brach.

Oh… it works for the main branch, yay!

repo: gregorw/discriminable


text:
notifications without shelling out

Hi there, awesome tool.
I saw that you check for local tools like notify-send and osascript to produce notifications. There is actually already a crate for that :D
This is what it would look like.
cheers

@hoodie Hey, thanks for the pull request!
I've seen that crate, but I was under impression that it does not support Mac, the description says Send Desktop Notifications on linux and bsd.
Hm..By some reason the PR breaks the build.

Tests pass locally for me.
Looks like notify-rust uses dbus

@hoodie  The version with notify-rust shows only title without message:

sorry, I didn't check the CI on this PR - I just added the required config to the .travis.yml

@hoodie  Thank you!)

authors: greyblake hoodie

repo: greyblake/cargo-testify


text:
flask-restful

那位佬把这个todoism的api用flask-restful重写了，遇到了很大的kong难

先关闭了，这类问题发到 HelloFlask 论坛或交流群更容易获得回应。

只是换个扩展，参考文档，应该不至于这么难吧

repo: greyli/todoism


text:
Specify argument number for substitution

xpanes supports a -n argument, which lets you tell it you're going to be passing more than one argument per pane. Great! However... it doesn't appear like this does anything more than concatenate arguments.
Example:
xpanes -n 2 -c "echo -e {} and {}" "a" "b" "c" "d"
results in two panes with the following outputs: a b and a b and c d and c d
Given the -n 2, I would have assumed I'd get an output of a and b and c and d
I can use -I to change the {}, but it looks like multiple -Is are not allowed. So I can't go
xpanes -n 2 -I{1} -I{2} -c "echo -e {1} and {2}" "a" "b" "c" "d"
Additionally, trying to pass a bash array doesn't seem to work, either:
xpanes -n 2 -c "echo -e {} and {}" ("a" "b") ("c" "d")
I get: zsh: number expected

Hi,
Thank you for using tmux-xpanes deeply!
What you reported is current limitation of -n option.
It cannot handle multiple placeholder {} bound to different argument.
Unfortunately, we do not have any plans to support separated placeholder like {1}, {2}...
Because I believe such the field separation procedure should be implemented in the user-defined script.
For example, I recommend you to use -B option with alias.
It seems that this is what you expected.
https://github.com/greymd/tmux-xpanes/wiki/Alias-examples#behaves-like-awk

alias xpanes='xpanes -B "set {}"'
$ xpanes -c 'echo $1-$2-$3' 'A B C' 'E F G' 'H I J' 'L M N'

If above workaround is not what you expected, please re-open this issue.
Thanks!

authors: FFdhorkin greymd

repo: greymd/tmux-xpanes


text:
refactor: upgrade sharp for ~2x faster image processing

Hello, I hope this small change can help make gridsome a bit more awesome.
The features of imagemin-mozjpeg and imagemin-pngquant are now directly available via sharp (the use of imagemin-webp is unnecessary as it produces the same output as the input).

Removes imagemin decode/encode roundtrip per image, effectively doubling throughput and reducing peak memory usage
Reduces node_modules filesystem size by ~10%, improving installation time by a similar amount
Removes no longer required libxml 'warmup'
Updates test snapshots that demonstrate smaller PNG output

Upgrading also provides support for M1 users.

Thank you so much, @lovell! This is a really great upgrade :)

authors: hjvedvik lovell

repo: gridsome/gridsome


text:
Argument "name" should be validated according to the JS naming rules

Since React components/contexts are actually functions, we should conform on JS naming rules (ie alphanumerics, underscore, dollar sign, but no numerics as first char)

Maybe a regex like this one is fine.

@grigorischristainas maybe we should export the validation function for dev use as well!

repo: grigorischristainas/react-add-new