text:
Breadboard recipe gallery

Let's build a thing that allows standing up a public or private gallery of recipes, with an easy way to contribute recipes to it.
A scaffolding for a simplest-possible service that could be hosted publicly and privately. We will likely host one for all the cool recipes we've made.
Also, any team should be able to just stand up their own private gallery where they can safely exchange recipes amongst themselves.

I imagine that we could spin this up as an 11ty service, like what @aomarks was talking about with the docs site.
Some thoughts about management (at least to start with), I imagine we could use github to accept recipes. That way they can be reviewed, there might also be meta data from the commits too that we can use.

Some thoughts about management (at least to start with), I imagine we could use github to accept recipes. That way they can be reviewed, there might also be meta data from the commits too that we can use.

I like this idea! Start really simple. We can set up auto-deployment so that after we merge a PR with a new recipe, it goes live automatically.

Another advantage of breadboard: it's just JSON files. If someone wanted to federate recipes, it's really just a matter of pointing to a JSON file, like this one: https://raw.githubusercontent.com/breadboard-ai/breadboard/main/packages/breadboard-web/public/local-boards.json

We might want to elevate local-boards.json to its own concepts, like a manifest file.

Duping this against #1853

authors: PaulKinlan aomarks dglazkov

repo: breadboard-ai/breadboard


text:
Could runCode allow async functions?

It seems like the runCode node currently crashes with I make my function async. Could it... not? Or is that an intentional constraint?

It used to work! Broke recently, probably.

source: gharchive/issue

authors: dglazkov surma

license_type: permissive

license_source: github-api


text:
Google drive connect

Expected Behavior
sign in to connect, Connect, then hit save and it saves
Actual Behavior
sign in to connect, Connect, then hit save and it disconnects google drive
Steps to Reproduce the Problem
1.Connect to google drive

sign in to connect and connect
press save button

Specifications

Version:
Platform:

Good bug. Not a great user experience.

authors: DubGNFT dglazkov


text:
fix build Issue found with podman

…podman

Thank you!

source: gharchive/pull-request

repo: breard-r/acmed

license: MIT


text:
Update output when project not found

Closes #131 and #213.

Although in #213, I suggested exiting with an error code if a package wasn't found, I didn't implement this, as I thought it would change the behavior of this tool unexpectedly.

Please only open PRs when you're ready for them to be reviewed, otherwise it generates a lot of noise in my GitHub notifications which are already a bit overwhelming. :/

Thought it was.
Just needed to fix the tests.

authors: brettcannon proinsias

license_source: bigquery


text:
add read_TLE, update SAT_scenario Link Intervals

add read TLE file and convert to orbit parameter elements
for following experiment, read TLE files then get there orbit elements
also update SAT_scenario Link Intervals output as csv,
then will try to fetch from TLE files which contain lots of satellite

nice one !
keep going~


text:
There is an error message of {"cod":"400","message":"wrong latitude"}

Networking _networking = Networking();
const apiKey = '***********************************';
getWeatherData() async {
var latitude = await _networking.latitude;
var longitude = await _networking.latitude;
Response response = await http.get(
Uri.parse(
'http://api.openweathermap.org/data/2.5/weather?lat={$latitude}&lon={$longitude}&exclude=hourly,daily&appid=$apiKey'),
);
print(response.statusCode);
print(response.body);
}
The networking class does it job at return my current lattitude and longitude

I'm not sure this is the repository you're looking for. This repo is for the Go client. I removed your key from the post.

I'm not sure this is the repository you're looking for. This repo is for the Go client. I removed your key from the post.

Okay thanks, well I’m sorry

repo: briandowns/openweathermap


text:
lulz im in ur PRz

lulz im in ur PR descriptionz

lulz im in ur PR commentz

license: Unlicense


text:
Maven Build Error when compiling YCSB: "Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures."

My maven version is 3.6.3.
YCSB git:(master) ✗ mvn --version Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /users/bshi/Downloads/apache-maven-3.6.3 Java version: 1.8.0_212, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.15.5", arch: "x86_64", family: "mac"
The build errors are as follows:
[INFO] TableStore DB Binding .............................. SUCCESS [  1.166 s]
[INFO] VoltDB Binding ..................................... SUCCESS [  1.719 s]
[INFO] Yugabyte Cassandra 2.1+ DB Binding ................. FAILURE [  8.400 s]
[INFO] Yugabyte JDBC DB Binding ........................... SKIPPED
[INFO] Yugabyte JDBC DB Binding ........................... SKIPPED
[INFO] YCSB Release Distribution Builder .................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  06:32 min
[INFO] Finished at: 2020-06-19T17:00:29-07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.8:test (default-test) on project yugabyteCQL-binding: There are test failures.
[ERROR]
[ERROR] Please refer to /Users/bshi/code/YCSB/yugabyteCQL/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.8:test (default-test) on project yugabyteCQL-binding: There are test failures.
Please refer to /Users/bshi/code/YCSB/yugabyteCQL/target/surefire-reports for the individual test results.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
Please refer to /Users/bshi/code/YCSB/yugabyteCQL/target/surefire-reports for the individual test results.
at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution (SurefireHelper.java:74)
at org.apache.maven.plugin.surefire.SurefirePlugin.writeSummary (SurefirePlugin.java:644)
at org.apache.maven.plugin.surefire.SurefirePlugin.executeAfterPreconditionsChecked (SurefirePlugin.java:640)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute (AbstractSurefireMojo.java:103)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :yugabyteCQL-binding

MojoFailureException says "As a rule of thumb, plugins use this error to signal a failure of the build because there is something wrong with the dependencies or sources of a project, e.g. a compilation or a test failure", so this might be a problem of yugabyteCQL-binding itself. Could you take a look?

I think maybe you're using a fork of our project? Afaict YCSB does not contain any modules that start with "yugabyte"

Have any details on the specific repository this code is from?

Even I am getting the same error. Could anyone help me out

YCSB has no yugabyte modules. if you are running into this problem please take it up with whatever fork you are using.

authors: Srija2000 binshi-bing busbey

repo: brianfrankcooper/YCSB


text:
issue creted from python

Default Description

Automated comment - Wed Dec 27 14:07:11 2023

repo: bridge-demo/petstore-orders-api


text:
Async recursive function produces StackOverflowException where as .Net doesn't.

Expected
run indefinitely.
Actual
Uncaught RangeError: maximum call stack exceeded
Steps To Reproduce
Live Bridge
Dot Net Fiddle
/// <summary>
/// Creates a simple class
/// </summary>
public class App
{
    // Use the [Ready] attribute to automatically
    // run this method when the page is ready.
    [Ready]
    public static async void Main()
    {
        Main();
    }
}

@michaelcheers,
The Dot Net Fiddle sample gives the same recursive problem:
[DotNetFiddle.Infrastructure.LimitExceededException: Execution time limit was exceeded]

Closes #1398.

authors: LeonidVeriga michaelcheers

repo: bridgedotnet/Bridge


text:
Array $set seems to be pointlessly cloning the input indexes (which makes it slow)

Doing some more performance profiling for TwistNTurn - I see that $set in Array.js is calling slice on its input indicies.  This causes an allocation while just trying to set a value in an array.  My javascript skills are weak, but the slice call does appear pointless at first glance...
I've tried removing it locally to good effect.

@Tilps, Can you give a line number for this and a reference to the file as a link?

https://github.com/bridgedotnet/Bridge/blob/master/Bridge/Resources/Array.js#L59

@Tilps, can you give a C# sample using that function

@Tilps, I think it is unnecessary and that you are right.

TwistNTurn is committed to github so I can easily point you at my source - https://github.com/Tilps/TwistNTurn/blob/master/TwistNTurnBridge/Mesh.cs#L867 is one of the many lines which generates a call to the $set implementation. (Which gets made a member method called set.)

@Tilps, it does not look like it could have been written by accident, so I do not know what to think.

Thanks for pointing out the issue. We'll take a look.

authors: Tilps geoffreymcgill michaelcheers


text:
Post-checkout failure

This just happened, I'm not sure what's going on:
± [matijs@bean master+] git co -b rails-5-2
Switched to a new branch 'rails-5-2'
Directory not empty @ dir_s_rmdir - /home/matijs/Projects/playdate/.git/hooks/old-hooks
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `rmdir'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `block in rmdir'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `each'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `rmdir'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/overcommit-0.43.0/lib/overcommit/installer.rb:142:in `preserve_old_hooks'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/overcommit-0.43.0/lib/overcommit/installer.rb:58:in `update'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/overcommit-0.43.0/lib/overcommit/installer.rb:20:in `run'
.git/hooks/post-checkout:67:in `<main>'
Report this bug at https://github.com/brigade/overcommit/issues

I think overcommit made old-hooks in the first place, so it shouldn't be surprised to find stuff there.
Update: This happens on regular branch checkout as well.

Hey @mvz, this issue should have been fixed by 7c85c6651b7249cecf92f2cfa848bbd16a488f03 (reported in #554).
Would really appreciate if you temporarily modified lib/overcommit/installer.rb:142 to add Dir.entries(old_hooks_path).inspect before that line on your system. Thanks!

Hi @sds, the result of that puts is:
[".", "..", "commit-msg", "pre-rebase", "pre-commit", "post-commit"]

Apologies @mvz. I thought we had released the fix already.
Please update to Overcommit 0.44.0 to avoid this issue. Thanks!

authors: mvz sds

repo: brigade/overcommit


text:
Added module entry point in package.json

Webpack2+ and rollup will understand this out of the box when importing from the lib, no need to import from 'react-waypoint/es'

Thanks @Andarist! We used to have module in the package.json file, but it was causing issues for people. This commit removed it: https://github.com/brigade/react-waypoint/commit/0e791c0a71b01918319fcf7875552a3ceb1e0974. Here's the issue that was filed after we added it: https://github.com/brigade/react-waypoint/issues/221
I'm not going to close this PR just yet. If you or someone else can come up with a few workarounds for people who will run into trouble from this, I'm okay merging this and releasing it as v8 (so that people will have to make a manual upgrade + migration).

The problem described in the other issue was caused by using .mjs extension. Merging this PR as is wouldn't case any trouble.
Using .mjs as extension for module's entry wouldn't give any benefits, .mjs is node's thing and module is targeting web bundlers.

I am a huge :+1: to this change as long as our build configuration outputs the right files.
This is what I do on personal libraries as well as libraries at work, and it works out amazingly. Furthermore, numerous other widely-used JS libraries do this, too, such as Redux. This configuration is the de facto way to support tree shaking with webpack without any side effects caused by unsupported extensions such as .mjs.
I discouraged us from using .mjs in the original PR where we introduced module, and, perhaps unsurprisingly, that decision caused problems for our users. The problem has never been the module field (which is widely supported); it’s the extension (which has very little/nonexistent ecosystem support).
tl;dr, I am strongly in favor of this change, and holding off on .mjs until it is more widely supported :+1:

I agree with James. Let's ship module field and go to .js instead of .mjs
Although by now I think create react app supports mjs
On Fri, Dec 22, 2017, 10:49 PM James, please notifications@github.com
wrote:

I am a huge 👍 to this change as long as our build configuration outputs
the right files.
This is what I do on personal libraries as well as libraries at work, and
it works out amazingly. Furthermore, numerous other widely-used JS
libraries do this, too, such as Redux. This configuration is the de
facto way to support tree shaking with webpack without any side effects
caused by unsupported extensions such as .mjs.
I discouraged us from using .mjs in the original PR where we introduced
module, and, perhaps unsurprisingly, that decision caused problems for
our users. The problem has never been the module field (which is widely
supported); it’s the extension (which has very little/nonexistent ecosystem
support).
tl;dr, I am strongly in favor of this change, and holding off on .mjs
until it is more widely supported 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/brigade/react-waypoint/pull/234#issuecomment-353710701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL7zvLUJnMBqqBaBk8exzXVfO_lUiOmks5tDKKRgaJpZM4RLAAr
.

authors: Andarist jmeas lencioni trotzig

repo: brigade/react-waypoint

license: mit


text:
Update data_management.md

Update How do I change my data directory in a conda environment - for Unix
The method in the current docs doesn't work or is outdated, the files need to be in etc/conda/, not at the root of the env directory. I also added what the files should look like to make it clearer and added the commands to ensure script execution permissions.

Thank you, @Haitham-ghaida for your contribution! I have now merged it into the main branch 🎉

authors: Haitham-ghaida michaelweinold

repo: brightway-lca/brightway-documentation


text:
Typo fix

Fixed in Resulting route table section

👌

authors: brillout jobarah

repo: brillout/vite-plugin-ssr


text:
panic: reflect.Set: value of type *ast.Cast is not assignable to type zed.Any

Repro is with Zed tagged v1.1.0.
I encountered this stack trace via accidental typo. The following works as expected:
$ zq -version
Version: v1.1.0

$ echo '{greeting:"hello"}' | zq -z 'yield "bigtext = ${upper(greeting)}"' -
"bigtext = HELLO"

However, if I introduce a typo to yield, it dumps a stack trace rather than showing an error message.
$ echo '{greeting:"hello"}' | zq -z 'yiel "bigtext = ${upper(greeting)}"' -
panic: reflect.Set: value of type *ast.BinaryExpr is not assignable to type zed.Any

goroutine 1 [running]:
reflect.Value.assignTo({0x1682a00?, 0xc0002e4c80?, 0x0?}, {0x1767724, 0xb}, 0x16a5440, 0xc0002feb90)
	/usr/local/opt/go/libexec/src/reflect/value.go:3062 +0x2ac
reflect.Value.Set({0x16a5440?, 0xc0002feb90?, 0x163619a?}, {0x1682a00?, 0xc0002e4c80?, 0x16a5440?})
	/usr/local/opt/go/libexec/src/reflect/value.go:2088 +0xeb
github.com/brimdata/zed/pkg/unpack.convertStruct({0x1683780?, 0xc0002feb70?, 0xc0003bf468?}, 0x1013cf9?)
	/Users/phil/work/zed/pkg/unpack/reflector.go:230 +0x277
github.com/brimdata/zed/pkg/unpack.Reflector.unpack(0xc0003bf4d0?, {0x1690240?, 0xc0002fe6c0?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:151 +0x105
github.com/brimdata/zed/pkg/unpack.Reflector.unpackObject(0x1e5f108?, 0x30?)
	/Users/phil/work/zed/pkg/unpack/reflector.go:172 +0xb0
github.com/brimdata/zed/pkg/unpack.Reflector.unpack(0xc0002faac0?, {0x1690240?, 0xc0002fe630?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:140 +0x6e
github.com/brimdata/zed/pkg/unpack.Reflector.unpackObject(0xc00000f260?, 0x1c?)
	/Users/phil/work/zed/pkg/unpack/reflector.go:172 +0xb0
github.com/brimdata/zed/pkg/unpack.Reflector.unpack(0x203000?, {0x1690240?, 0xc0002fe600?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:140 +0x6e
github.com/brimdata/zed/pkg/unpack.Reflector.unpackArray(0x0?, {0xc0002fac60, 0x1, 0x1013cf9?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:184 +0xc5
github.com/brimdata/zed/pkg/unpack.Reflector.unpack(0xc0003bf888?, {0x165e9c0?, 0xc00000f488?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:164 +0x1ce
github.com/brimdata/zed/pkg/unpack.Reflector.unpackObject(0x16?, 0x1656240?)
	/Users/phil/work/zed/pkg/unpack/reflector.go:172 +0xb0
github.com/brimdata/zed/pkg/unpack.Reflector.unpack(0xc000202240?, {0x1690240?, 0xc0002fe5d0?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:140 +0x6e
github.com/brimdata/zed/pkg/unpack.Reflector.Unmarshal(0x1690240?, {0xc000202240, 0x227, 0x240})
	/Users/phil/work/zed/pkg/unpack/reflector.go:83 +0x107
github.com/brimdata/zed/pkg/unpack.Reflector.UnmarshalObject(0x1?, {0x1690240?, 0xc0002f9f20?})
	/Users/phil/work/zed/pkg/unpack/reflector.go:101 +0x5a
github.com/brimdata/zed/compiler/ast.UnpackMapAsOp({0x1690240?, 0xc0002f9f20?})
	/Users/phil/work/zed/compiler/ast/unpack.go:112 +0x37
github.com/brimdata/zed/compiler.ParseOp({0x7ff7bfeff9ce?, 0x160ed88?}, {0x0?, 0x3?, 0xc0000899c0?})
	/Users/phil/work/zed/compiler/compiler.go:164 +0x50
github.com/brimdata/zed/cli/queryflags.(*Flags).ParseSourcesAndInputs(0xc00022eed8, {0xc0000320a0, 0x2, 0x2})
	/Users/phil/work/zed/cli/queryflags/flags.go:48 +0x2de
github.com/brimdata/zed/cli/zq.(*Command).Run(0xc00022eea0, {0xc0000320a0, 0x2, 0x2})
	/Users/phil/work/zed/cli/zq/command.go:132 +0x25b
github.com/brimdata/zed/pkg/charm.path.run({0xc0000100c0?, 0x1, 0x1}, {0xc0000320a0?, 0x2, 0x0?})
	/Users/phil/work/zed/pkg/charm/path.go:11 +0x8b
github.com/brimdata/zed/pkg/charm.(*Spec).ExecRoot(0xc0000021a0?, {0xc000032090, 0x3, 0x3})
	/Users/phil/work/zed/pkg/charm/charm.go:63 +0x4a
main.main()
	/Users/phil/work/zed/cmd/zq/main.go:11 +0x5e

#3899 fixes the panic but provides an uninformative error, so I don't consider that a fix.
$ echo '{greeting:"hello"}' | zq -z 'yiel "bigtext = ${upper(greeting)}"' -
zq: JSON field "value": value of type "*ast.BinaryExpr" not assignable to interface type "zed.Any" in struct type "ast.Term"

FWIW, I found a similar crash when investigating the relevance of #3452 and it appears to be semi-fixed by the #4084 branch in the same way. If it turns out to require separate treatment I can open a new issue.
The repro:
$ zq -version
Version: v1.2.0-49-g9c0f0973

$ echo '{"addr": "192.168.0.1", "port": 80}' | zq -z 'type socket = {addr:ip,port:port=<uint16>} yield shape(socket)' -
panic: reflect.Set: value of type *zed.TypeValue is not assignable to type zed.Type

goroutine 1 [running]:
reflect.Value.assignTo({0x16f0e60?, 0xc0000d3260?, 0x0?}, {0x17b071f, 0xb}, 0x16e6ca0, 0xc00039b7c0)
	/usr/local/opt/go/libexec/src/reflect/value.go:3145 +0x2a5
...

Then with the fix branch:
$ zq -version
Version: v1.2.0-50-g613256db

$ echo '{"addr": "192.168.0.1", "port": 80}' | zq -z 'type socket = {addr:ip,port:port=<uint16>} yield shape(socket)' -
zq: JSON field "type": value of type "*zed.TypeValue" not assignable to interface type "zed.Type" in struct type "zed.TypeDef"

I discovered during an issue scrub that this became fixed at commit 183e432, which is associated with the changes in #5108.
Starting at that commit, instead of the "uninformative error" @nwt previously observed, now we get a helpful parse error.
$ zq -version
Version: v1.15.0-16-g183e432f

$ echo '{greeting:"hello"}' | zq -z 'yiel "bigtext = ${upper(greeting)}"' -
zq: error parsing Zed at column 36:
yiel "bigtext = ${upper(greeting)}"
                               === ^ ===

Of course, in a commit even more recent, this would now be implemented instead with f-strings, and a similar error message is reported there as well.
$ zq -version
Version: v1.17.0-37-g4360baf9

$ echo '{greeting:"hello"}' | zq -z 'yield f"bigtext = {upper(greeting)}"' -
"bigtext = HELLO"

$ echo '{greeting:"hello"}' | zq -z 'yiel f"bigtext = {upper(greeting)}"' -
zq: error parsing Zed at line 1, column 36:
yiel f"bigtext = {upper(greeting)}"
                               === ^ ===

Regarding this other symptom cited above in https://github.com/brimdata/zed/issues/3899#issuecomment-1247007116, I can see that became a parsing error as of commit b58a6d7 which is associated with the changes in #4996.
$ zq -version
Version: v1.12.0-36-gb58a6d7a

$ echo '{"addr": "192.168.0.1", "port": 80}' | zq -z 'type socket = {addr:ip,port:port=<uint16>} yield shape(socket)' -
zq: error parsing Zed at column 34:
type socket = {addr:ip,port:port=<uint16>} yield shape(socket)
                             === ^ ===

Thanks @mattnibs!

authors: nwt philrz

repo: brimdata/zed


text:
Improve top operator

The top operator is limited to field references. It should should accept arbitrary expressions like the sort operator does.
It should also allow selection of either ascending or descending order for each expression.

As of Zed commit 4290afd, it looks like top does take arbitrary expressions like sort does, e.g., modifying an example from the sort docs:
$ echo '{word:"hello"}{word:"Hi"}{word:"WORLD"}' |   zq -z 'top 2 lower(word)' -
{word:"WORLD"}
{word:"Hi"}

However, it remains true that top lacks the per-key ordering of sort like was added in #5203.


text:
spawn zeek on windows with new hidden subcommand

This adds a hidden zqd subcommand "winexec", that executes a command
using the same job object based spawned process termination we are
already using in the windows zeek-launcher utility. Use this subcommand
when we launch zeek on windows. This is a first step to treating zeek as
more of a black box from inside zqd, so that users can run their own
zeek setup.

Rather than use a subcommand like this, it might be a little cleaner and clearer to

start the Zeek process with CREATE_SUSPENDED,
create and configure the job object (including adding the Zeek process to it) in zqd,
use DuplicateHandle to give the Zeek process a handle to the job object,
close the job object handle in zqd, and finally
call ResumeThread on the Zeek process's thread.

Rather than use a subcommand like this, it might be a little cleaner and clearer to

So, funny story, I tried that first. :) And though it worked, I didn't like the solution, because of what it took to get the thread to resume:
If you create the process with CREATE_SUSPENDED, when you want to resume it, you have to resume the processes main (only) initial thread, via ResumeThread. To call ResumeThread, you need a handle to the thread, and for a handle, you need the thread id.
To get the thread id, the only option I found is to use the win32 api CreateToolhelp32Snapshot, and then iterate through all threads in the system (!), looking for the one with the correct parent process. Even if you specify only the process id you're interested in, the CreateToolhelp32Snapshot will always take a snapshot of the state of every system thread, and give you a handle to that snapshot, which you then need to iterate on with other calls.
I implemented all of this myself, both the create suspended & resuming the thread, and got it working. I later found that there's a test utility in the go source code that implements the resume handling:
https://github.com/golang/go/blob/master/src/runtime/syscall_windows_test.go#L828
If it were possible to get the created processes thread id through the exec.Cmd calls, this would be much easier. But that information is thrown away in syscall.StartProcess, which is near the bottom of the chain of exec.Cmd.Start().
Overall, I thought that needing to have all the extra syscall definitions, and then creating a snapshot of all system threads & iterating on it, felt pretty complex to have around. So that led me to this PR's approach.
So with more knowledge about the implementation, let me know what you think between the two approaches.

authors: alfred-landrum nwt

repo: brimsec/zq


text:
Be more selective when printing default values in usage

Don't print the default value when it is None or a boolean.  These cases
are already clear in the usage output.  The default value ends up being
either gratuitous, or confusing for options with negative names, like
--no-validate.
To do this, we copy the code from argparse.ArgumentDefaultsHelpFormatter
and do nothing if we detect either case.
$ ./brkt aws encrypt -h
usage: brkt aws encrypt [-h] [--encrypted-ami-name NAME]
                        [--guest-instance-type TYPE] [--pv] [--no-validate]
                        --region NAME [--security-group ID] [--subnet ID]
                        [--tag KEY=VALUE] [-v] [--ntp-server DNS_NAME]
                        [--proxy HOST:PORT | --proxy-config-file PATH]
                        [--status-port PORT] [--token TOKEN]
                        ID

Create an encrypted AMI from an existing AMI.

positional arguments:
  ID                    The guest AMI that will be encrypted

optional arguments:
  --encrypted-ami-name NAME
                        Specify the name of the generated encrypted AMI
  --guest-instance-type TYPE
                        The instance type to use when running the unencrypted
                        guest instance (default: m3.medium)
  --no-validate         Don't validate AMIs, subnet, and security groups
  --ntp-server DNS_NAME
                        Optional NTP server to sync Metavisor clock. May be
                        specified multiple times.
  --proxy HOST:PORT     Use this HTTPS proxy during encryption. May be
                        specified multiple times.
  --proxy-config-file PATH
                        Path to proxy.yaml file that will be used during
                        encryption
  --pv                  Use the PV encryptor
  --region NAME         AWS region (e.g. us-west-2)
  --security-group ID   Use this security group when running the encryptor
                        instance. May be specified multiple times.
  --status-port PORT    Specify the port to receive http status of encryptor.
                        Any port in range 1-65535 can be used except for port
                        81. (default: 80)
  --subnet ID           Launch instances in this subnet
  --tag KEY=VALUE       Set an AWS tag on resources created during encryption.
                        May be specified multiple times.
  --token TOKEN         Token that the encrypted instance will use to
                        authenticate with the Bracket service. Use the make-
                        token subcommand to generate a token.
  -h, --help            show this help message and exit
  -v, --verbose         Print status information to the console

👍

authors: bburtin krishnanrs

repo: brkt/brkt-cli


text:
Different results on same search

I used the link from Alamut to get to the right variant site in gnomAD. The first search resulted in "Variant not found" (https://gnomad.broadinstitute.org/variant/19-10939832-C-T). However, as there were frequencies in Alamut from gnomAD, I retried it and got to the site where the variant is present in 74 alleles in total (https://gnomad.broadinstitute.org/variant/19-10939832-C-T (the same link as before)).
This is not the first time we have seen this discrepancy in gnomAD.

When querying Elasticsearch for a variant or other data, it looks like we are not handling the case where ES may return partial results.
This can happen when some shards fail or timeout. ES 6.3 added an allow_partial_search_results option to consider partial results a failure. The version we use does not support this, but we should be able to use the _shards field in the search response to check for partial failures.

Assuming the issue is caused by partial search failures in Elasticsearch, 772d4a51bffaf79ec6630fa5e30b0417bb22b8aa should resolve it.

authors: ejarh nawatts

repo: broadinstitute/gnomad-browser


text:
Add script for generating gnomAD trio pedigree

There is one remaining TODO that I left in. The current code is based off of v3, and in v3 the trio kept for families with multiple trios was just the first one in the pedigree. Should we add options for how to handle multiple trios in a family? I think v2 removed all trios with more than one offspring in the family. I don't like how it was handled for v3 though, instead I would prefer keeping a random one from each family instead of only grabbing the first one. Thoughts?

4/20/23 - Connected PR is being reviewed by Qin and Kristen. Kristen will wait to submit her first review of the code until after Qin has finished her first round of review. Qin and I quickly went over the code together on Tuesday during our 1:1.


text:
load .gtf and .reg files

From @cseed on August 26, 2015 14:14
Copied from original issue: cseed/hail#8

Add as needed.

repo: broadinstitute/hail


text:
[JN-719] Delete pages

DESCRIPTION
Not much to say about this one. You can delete pages now 🥳 You can't delete a landing page, but that doesn't seem like a desirable option anyway.
The modal in the video is not current and has been updated to look like this:

https://github.com/broadinstitute/juniper/assets/7257391/da19941a-98f3-40fc-8b2a-cfacd54d9876
TO TEST:  (simple manual steps for confirming core behavior -- used for pre-release checks)

Launch admin API + UI
Populate ourhealth
Go to the site content editor: https://localhost:3000/ourhealth/studies/ourheart/env/sandbox/siteContent
Try deleting pages (and note that you cannot delete a landing page)
Save and confirm that the pages are deleted

looks good, and works well when I tested it locally.  I think the requirement to type the name is unnecessary given that the change won't take effect unless/until they hit "Save" (and since they can go back to prior versions as you note).  And it might be worth calling that out in the confirmation dialog that they need to save before the deletion will take effect.

@devonbush that's a good point. I went back and forth with it... Initially I felt like the UX without it wasn't great because you'd hit the delete button and sometimes it was hard to tell that anything happened. But I realize that both approaches incur  UX-debt. Maybe the one that involves committing less code is the lesser evil...
In general, I think we need to adopt better visual patterns for drawing attention after certain types of events occur (re-ordering survey pages/questions is another example)

Removed the modal in the latest commit

@denniscunningham it's possible, but it introduces some inconsistency into how certain editor actions behave. We can assume intent on behalf of the user for each action, and I think your suggestion about deleting pages is accurate, but I have a preference for treating everything as a draft until "Save". I think it's an easier UX to understand because saves aren't happening piecemeal. It's also cleaner from a versioning standpoint because we aren't splitting multiple changes across multiple versions, even if they're part of one single update.
I'll ultimately defer to the reviewers for this, but I'd propose leaving the save behavior as-is and removing the text that talks about hitting the Save button in order to persist the changes. It was originally added because the first version of the PR (see video) had a confirmation input that implied that the modal did save immediately, so the clarification was needed. But that's gone now.

@MatthewBemis Perhaps we can chat with @devonbush about this? Whatever the group decides is fine by me.
My POV as a user deleting the page is a meta action. As a user, I am past committing incremental changes, I'm done with the page, get rid of it. It's odd to have to save a delete unless, it is an immediate "do you really want to do that" action.
But I could be misunderstanding, so we can probably talk this through quickly f2f.

Let's merge as-is--that will make sure this is up in time for team testing.  And then we can get feedback from Whitney, who is currently the most experienced site content editor, about what she'd expect and/or prefer.

I removed the note at the bottom of the modal, so the final version I'm proposing looks like this:

authors: MatthewBemis denniscunningham devonbush

repo: broadinstitute/juniper


text:
fire all torpedos implemented and tested locally

Fix #1

OK


text:
Add alpine support when layering sshd on top

This change makes it possible to layer sshd on top of an alpine image.
e.g https://github.com/csabapalfi/hello-alpine-node can now be deployed with clocker.
I tested locally and using the SshdDockerfile results in an SSHable alpine image.

onbox.base.dir.skipResolution: true is required (and potentially some more changes around runtime directory setup)

repo: brooklyncentral/clocker


text:
Support for Node 20 due to Github deprecation of Node 16

Github has announced that they will be deprecating the use of actions based on Node 16. All such actions should be migrated to use Node 20 before the sunset date in 2024.
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

Node 16 has reached its end of life, prompting us to initiate its deprecation process for GitHub Actions. Our plan is to transition all actions to run on Node 20 by Spring 2024. We will actively monitor the migration's progress and gather community feedback before finalizing the transition date. Starting October 23rd, workflows containing actions running on Node 16 will display a warning to alert users about the upcoming migration.

Hi Adam - Thanks for the heads up! Our team will be taking the necessary actions before the deprecation.

Hi Ganesh,
Just checking if there is any recent update on this issue.

Hi @officialtpss,
It will be migrated to Node v20 before April'24 within the timeline of Github's transition to Node 20 by Spring '24.

@ganesh-gsk Any updates on getting this updated?

Hi, I was wondering if your team has an updates or estimated time for completion for this?

Hi @asnodgrass-nid, @officialtpss, @michael-graves-dojo, @mikemorioka,
Migration to Node v20 is completed, please let us know in case of any issues.

authors: asnodgrass-nid ganesh-gsk michael-graves-dojo mikemorioka officialtpss

repo: browserstack/github-actions


text:
Closure advanced mode externs

https://github.com/browserstate/history.js/pull/102 suggests that history.js was once compatible with google closure advanced mode, but I can find no trace of current support. Has support for this been removed?

Here's the externs I just created, "works on my machine", I am probably missing some things. Pasting here as a starting point for the next guy who comes along.
/**
 * @type {Object}
 * @const
 */
var History = {};

History.pushState = function () {};
History.replaceState = function () {};

/** @interface */
function HistoryState() {}
/** @type {Object|null} */
HistoryState.prototype.data;
/** @type {string|null} */
HistoryState.prototype.title;
/** @type {string} */
HistoryState.prototype.url;
/** @type {boolean|number|undefined} */
HistoryState.prototype.queue;
/** @type {boolean|undefined} */
HistoryState.prototype.internal;
/** @type {string} */
HistoryState.prototype.cleanUrl;

/**
 * @return {HistoryState}
 */
History.getState = function () {};

/**
 * @return {HistoryState}
 */
History.getStateByIndex = function () {};

History.getCurrentIndex = function () {};
History.getHash = function () {};

History.back = function () {};
History.forward = function () {};
History.go = function () {};

History.log = function () {};
History.debug = function () {};

History.options = {};
History.options.hashChangeInterval = function () {};
History.options.safariPollInterval = function () {};
History.options.doubleCheckInterval = function () {};
History.options.disableSuid = function () {};
History.options.storeInterval = function () {};
History.options.busyDelay = function () {};
History.options.debug = function () {};
History.options.initialTitle = function () {};
History.options.html4Mode = function () {};
History.options.delayInit = function () {};

History.state = function () {};
History.length = function () {};

/**
 * @type {Object}
 * @const
 */
History.Adapter = {};

History.Adapter.bind = function () {};
History.Adapter.trigger = function () {};
History.Adapter.onDomLoad = function () {};


text:
请问打印日志的问题

log模块的性能怎么样？ 担心打印日志太多会不会塞住。看现在生产环境一小时产生3.4G的日志。
有方式可以根据时间打印到不同的日志文件吗？

@jamesge 请问在百度内部，是通过什么方法来解决多线程环境下频繁写日志的锁竞争的？ 这部分不方便开源吗？ 用POSIX的O_APPEND模式的::write(2)函数可以解决吗？

同步写就是O_APPEND，这不用加锁就可以保证原子，但磁盘卡还是会卡的。异步写的话就是常规的队列+独立的写线程，也没有完全规避锁，只是临界区小很多。最好的办法是用类似这里的方法异步写，同时在crash时刷出还未写完的日志以避免丢失，不过出于精力所限，我们并没有把这套方法用于日志。

authors: gydong jamesge wclin88

repo: brpc/brpc


text:
Brunch doesn't include my module

Description
In my project, I have several js files, and when I modify a file, brunch detect changes, but the module is empty in my app.js. Example:
require.register("search.js", function(exports, require, module) {

});

I need to stop the watcher, and lauch it again. I don't have compilation issue in the terminal... :
$ brunch w
22 Mar 15:48:29 - info: compiled in 1.1 sec
22 Mar 15:48:30 - info: compiled 10 files and 2 cached into app.js, copied 87 in 655ms
22 Mar 15:48:56 - info: compiled search.js and 11 cached files into app.js in 104ms
^C

$ brunch w
22 Mar 15:49:07 - info: compiled in 1.1 sec
22 Mar 15:49:08 - info: compiled 10 files and 2 cached into app.js, copied 87 in 620ms

Environment

Brunch: 2.5.2 but tested with 2.4.2
Node: v5.9
NPM: 3.7.3
Operating system: Debian jessie

package.json contents
{
    "name": "morpheus-ui",
    "description": "",
    "private": true,
    "scripts": {
        "start": "brunch watch",
        "prod": "brunch build --production"
    },
    "devDependencies": {
        "brunch": "~2.5.0",
        "clean-css-brunch": "~2.0.0",
        "css-brunch": "~2.0.0",
        "javascript-brunch": "~2.0.0",
        "uglify-js-brunch": "~2.0.0"
    }
}

brunch config contents
'use strict';

exports.config = {
    "paths": {
        "watched": ["app", "src"],
        "public": "web"
    },
    "files": {
        "stylesheets": {
            "joinTo": "main.css",
        },
        "javascripts": {
            "joinTo": "app.js",
        }
    },
    "modules": {
        nameCleaner: function path(path) {
            return path.substring(path.lastIndexOf("/") + 1);
        }
    }
}

Interested in your brunch build -d output.

Here the output : http://pastebin.com/s8Ev7MPD

Could also be related to the race condition between the editor and the fs watcher. See this thread https://github.com/brunch/brunch/issues/1219#issuecomment-191782948

I don't know, but I use Sublime text 3 over sshfs.

@Surfoo can you test whether editing it in vim for example over ssh produces that same issue?
Also with ST over sshfs, can you try adding to your config awaitWriteFinish: true (and see if it helps), or usePolling: true (and see if it helps), or both and see if it fixes it.

I added these 2 settings and also atomic_save: true in my ST config. It's maybe overkill, but I don't have the problem right now. I'll let a comment if the problem reappears in the next few days.
Thanks for your help!

Great, please do report how that works for you :)

Adding this to the FAQ: https://github.com/brunch/brunch/pull/1361

authors: Surfoo goshakkk paulmillr

repo: brunch/brunch


text:
Include file-based aliases for main files

#1186

Can we make a temp option that reverts the new behavior?

@paulmillr #1191

authors: goshakkk paulmillr


text:
Problemas no login

Primeiramente quero parabenizar pelo frame, muito bom mesmo.
Segui seu curso de sistema de login completo com o HXPHP e fiz algumas alterações, no meu ambiente local funciona perfeitamente porém quando subo pro servidor de produção a parte de login não funciona, quando coloco $this->auth->redirectCheck() ele fica redirecionando direto para o login, como se não armazenasse a sessão do login. Pode me ajudar?

Olá @wtcosta, tudo bem?
Qual versão do framework você está usando?
Seu código está semelhante ao repositório da série?
Fico no aguardo.
Forte abraço e sucesso sempre!

authors: brunosantoshx wtcosta

repo: brunosantoshx/hxphp


text:
HXPHP - Ops! Nada encontrado! .../usuarios/listar/

Já revisei tudo e ainda não estou conseguindo acessar nada além da página inicial(uhu). Quando tento acessar por exemplo 127.0.0.1:8080/site/usuarios/listar/  Apresenta a mensagem: Ops! Nada encontrado!
Cheguei a testar numa versão antiga do HXPHP e funcionou, mas na atual não.
Uso: Linux, porta apache 8080, HXPHP Versão 2.5.8, e já testei mod_rewrite if (in_array("mod_rewrite",apache_get_modules())) print "Ok";

se chega a essa tela não é problema de mod_rewrite, veja os arquivos, se estão bem escritos a função que deseja usar, veja se declaro o controller de forma correta e a action tb

Vou refazer novamente, mas mesmo uma saída como o código não reconhece.
<?php
class UsuariosController extends \HXPHP\System\Controller
{
	public function listarAction()
	{
		print 'Testando ...'; exit;
	}
}

skay1994, está funcionando agora, mas sem explicações até o momento pois não alterei nada. Acredito que o problema tem relação com minha instalação do PHP, algo tipo opcache nas configurações.
Obrigado!

Olá @coutofx, como vai?
Configurar um servidor local em sistemas Linux é sempre problemático. Existe a questão das permissões e também a edição dos arquivos de configuração do Apache e do PHP.
Se lembrar da solução é importante postar aqui para ajudar outros que possam enfrentar a mesma dificuldade.
Forte abraço e sucesso sempre!

O problema é que mesmo modificando conteúdo dos scripts as paginas não atualizavam no navegador, repetindo assim um erro já corrigido, então pesquisando solucionei esta questão desabilitando o Op Cache do PHP(php.ini) tornando-os igual a zero:
opcache.enable = 0
opcache.enable_cli = 0

authors: brunosantoshx coutofx skay1994


text:
Stream encryption API

Something that i would like to see in this library is an API for encrypting a stream of messages.
This is for example useful if a file is too large to be encrypted at once.
It is impotent for such an API that messages can not be modified , dropped or reordered. This means the complete stream needs to be authenticated.
Its also a requirement, that the same message, if encrypted repeatedly, produces different ciphertexts.
Libsodium provides such a functionality based on XChaCha20Poly1305.
https://download.libsodium.org/doc/secret-key_cryptography/secretstream
This functionality can also easily implemented for orion. (I already have a working, hazardous implementation for it )
The main problem that i see is that this algorithm isn't standardized.
If you want this functionality  i can submit a pull request for this

Something that i would like to see in this library is an API for encrypting a stream of messages.
This is for example useful if a file is too large to be encrypted at once.

This is a great idea! I'm curious whether you plan on using such a feature anywhere specific?

The main problem that i see is that this algorithm isn't standardized.

XChaCha20Poly1305 is in the process of being standardised and is used quite a few other places as well. I see no issue with basing a streaming encryption API upon this. However, we could just as well add support for streaming ChaCha20Poly1305 encryption, should the non-standardisation cause concern to anyone.
The libsodium secretstream is a good baseline for implementing it in orion.

If you want this functionality i can submit a pull request for this

Yes, this definitely seems worthwhile to provide. I have looked into it before, but not thought about specific requirements for such an implementation, which means we might need to re-iterate over its design a few times. Since you mentioned you already have a working implementation, you could open it as WIP while we work through it?

authors: brycx snsmac

repo: brycx/orion


text:
Remove the useless code

Why do you even need that, i just want to 8 ball in peace.

The sentry_sdk code is implemented to report errors back to me so that I am able to diagnose them and fix them for everyone, and I don’t have to worry about users not reporting issues by themselves.  Whenever there is any kind of error thrown, I get an email and can see how many users have encountered the same error.

It shouldn’t have any effect on regular users, as they have the same experience as they would without it, but when they encounter an error, I can solve it and improve the program.

In fact, with some of these errors, I add them as GitHub issues.  I’m guessing #53 and #54 were caused when you played around in the code.

But how would it even break, its just random.choice from a list. Its not necessary and wont break...

I agree, it is fairly simple, however Sentry is used.  Thanks for the PR, but I would like to keep Sentry installed on this program.  Have a great day.

authors: TheRockettek bsoyka

repo: bsoyka/magic-py-ball


text:
HTTP 503 when enabling a zone

Unable to control a zone
Steps to reproduce the behavior:

Turn off zone on Master Controller
Select 'Heat' option for zone accessory in Home app
Observe errors in HB log:
[Actron Neo] Maximum retries exceeded -> Actron Neo API returned a server side error: http status code = 504
[Actron Neo] API Error when attempting command send:
{"command":{"UserAirconSettings.EnabledZones[0]":true,"type":"set-settings"}}
[Actron Neo] Failed to send command, Actron Neo Cloud unreachable

Homebridge Version: 1.6.1
Plugin Version: 1.2.13

Resolved in release 0.0.16

authors: andrew-burgher bstillitano

repo: bstillitano/homebridge-actron-neo


text:
Fix tiny bug in tx.go

Tiny bug fixed in tx.go, easy diff.

Superceded by #165.

OK Thanks. Closed

repo: btcsuite/btcutil

license: isc


text:
pysm.Instrument seems not working properly in some cases

Hello,
I have a problem using pysm.Instrument.
I use this standard sky configuration:
nside = 128
sky_config = {
'synchrotron': models('s1', nside),
'dust': models('d1', nside),
'freefree': models('f1', nside),
'cmb': models('c1', nside),
'ame': models('a1', nside)}

then I create a sky with:
sky = pysm.Sky(sky_config)

Now, I create the two following different instruments:

instrument_mono_noiseless = pysm.Instrument({
    'nside': nside,
    'frequencies' : np.array([143]),
    'use_smoothing' : True,
    'beams' : np.array([7.1]),
    'add_noise' : False,
    'noise_seed' : None,
    'sens_I': None,
    'sens_P': None,
    'use_bandpass' : False,
    'channel_names' : ['143_GHz'],
    'channels' : None,
    'output_units' : 'uK_RJ',
    'output_directory' : "./",
    'output_prefix' : "noiseless_mono",
    'pixel_indices' : None})

instrument_mono = pysm.Instrument({
    'nside': nside,
    'frequencies' : np.array([143]),
    'use_smoothing' : True,
    'beams' : np.array([7.1]),
    'add_noise' : True,
    'noise_seed' : 0,
    'sens_I': np.ones(1),
    'sens_P': np.ones(1),
    'use_bandpass' : False,
    'channel_names' : ['143_GHz'],
    'channels' : None,
    'output_units' : 'uK_RJ',
    'output_directory' : "./",
    'output_prefix' : "mono",
    'pixel_indices' : None})

I observe the sky through these two instruments with instrument_*.observe(sky) and then I read the corresponding maps that have been produced.

In the first case the created map does not have the polarization components but only the intensity one. In fact, you will get an error message if you try:
hp.read_map('noiseless_mono_nu0143p00GHz_total_nside0128.fits', field=(0, 1, 2))

while the right command would be:
hp.read_map('noiseless_mono_nu0143p00GHz_total_nside0128.fits', field=(0))

but this means that Q and U maps have not been generated.

In the second case, the three maps (I, Q, U) are generated but in a wrong way since the Q and U maps are in the same order of magnitude of the I map:
hp.read_map('mono_nu0143p00GHz_total_nside0128.fits', field=(0, 1, 2))

array([[-36.27698898,  14.9692564 ,  25.86756897, ...,  76.63456726,
         81.74451447,  67.1904068 ],
       [-36.27647781,  14.91915131,  25.87987328, ...,  76.58881378,
         81.76040649,  67.25320435],
       [-36.32805252,  14.94966221,  25.84389114, ...,  76.66394043,
         81.7594986 ,  67.2399292 ]])

Is there something I'm doing wrongly somewhere?

Hi, I think the problem is related to the number of frequencies passed to pysm.Instrument. When only one frequency channel is given the smooth function doesn't work properly, if more frequencies are given then everything appears to work well.

authors: NicolettaK fincardona


text:
在ubuntu17.10下编译zimg时失败

/bin/sh: 1: autoreconf:not found
/bin/sh: 1: ./configure :not found
make[1]:Entering directory 'home/zimg/deps/libjpeg-turbo'
make[1]:**** No targets specified and no makefile found.stop
Leaving directory 'home/zimg/deps/libjpeg-turbo'
Makefile:30:recipe for target 'deps/libjpeg-turbo/.libs/libjpeg.a' failed.
make:*** [deps/libjpeg-turbo/.libs/libjpeg.a] Error 2.

百度搜索之后，按照提示安装autoconf automake libtool包
apt-get install autoconf automake libtool之后 再执行make，发生如下错误：
GEN jccolor-sse2-64.lo
...
libtool: error:ignoring unknow tag NASM

忽略错误继续执行
Successfully built LuaJIT
cd build/zimg;cmake /home/zimg/src ;make -j 4;cp zimg /home/zimg/bin
/bin/sh:1:cmake:not found

cmake我是安装过了的，为什么现在提示找不到呢？

repo: buaazp/zimg


text:
No events provided

Please provide color picker events like, onchange, onselect, onopen,onclose

There is ready to use emitEvent function to handle this. Now only 'colorpicker-closed' (onclose) event is emitted. I don't think we need to emit onchange or onselect within the color picker. You can handle this in your controller. I'm fine with onopen, so any PRs are welcome.

thanks to  #85 we can close this issue.

authors: buberdds dlinx

repo: buberdds/angular-bootstrap-colorpicker


text:
Fly v1.x is Out!

Fly v1.x is not had Babel :persevere:

Oh... Test failed, but Fly doesn't support Node 0.11.x now ?
https://github.com/bucaran/fly/blob/master/.travis.yml

@bucaran @lukeed Whould you review this PR ?

LGTM
@lukeed I think we should be able to drop the --harmony flag soon along with support for Node 0.12.
Thoughts?

@pine613 looks fine to me
@bucaran Can't drop harmony without all these plugins breaking... const, let, for of, arrows... all require it.
Also can't/shouldn't drop 0.12. It's still nearly (or at least) 25% of commercial usage. Node v3 through 5 is barely 20% combined.

@lukeed Is anyone really using Fly in 0.12? Seems kind of incredible. BTW originally, the harmony flag was used only to support generators, the ES6 syntax came later.

@bucaran Unfortunately I don't think we have a way of measuring that. But as a whole, NPM's active percentage of 0.12 is pretty shocking.
Re: harmony. Right, but now with the 'downgrade' to ES5, we'd have to keep harmony around for all the plugins that are using minor ES6 syntax bits.... at least until fly-esnext and fly-plugins are out. I havent had time to work on those lately.

Hi @bucaran @lukeed.
Whould you like to resolve --harmony flag problems in another new issues ?
I want you to use fly-mocha with Fly v1.x :pray:
Thank you.

:pray:

Hi @lukeed. How about this…? :pray:

@lukeed I think what @pine613 is saying is that we should close the issue :laughing:
@pine613 Is that correct?

@pine613 @bucaran still looks good to me! Not sure why/if you guys were waiting on me?
Sorry for any confusion.

Thank you!!!

authors: bucaran lukeed pine613

repo: bucaran/fly-mocha


text:
Reduce excessive logging

Bazel-remote is pretty verbose logging all access information.
In particular it becomes problematic for findMissingBlobs call, which may have thousands of entries, and each entry cases a single line to be logged here: https://github.com/buchgr/bazel-remote/blob/6aa66a2b6098fb38823990d16915f05b12d1bd18/server/grpc_cas.go#L45
Note, the bazel calls this for all actions it processes, causing huge amount of logs - in our case it caused some issues on kubernetes when processing was stalled.
Workaround was to just remove the most problematic logs, but possibly logging could be improved - e.g. in this case just don't log all singular CAS HEAD requests but a summary of those for single findMissingBlobs.
In general maybe accessLogger could log into limited list of entries, and this list could be accessible through some web-point on demand instead of logging those to stdout.

Can you describe the issues you encountered? Was there a bottleneck in bazel-remote, or did it simply flood your log daemon?

Symptom was that bazel-remote started to work very slowly after a few hours of working. Note, that it's used as a backed in build-barn setup.
The actual root cause is not very well understood by me - whether it was just that bazel-remote become very slow because of logging, or it triggered some threshold on docker / kubernetes side. One thing that was clear was that checking logs I was getting at least 5M logs for each second - actually because of log trimming was not able to get more than that, so it could be even more than 5M/sec. After disabling some logs it just came back to normal and had no issues for the following days.

Missed one important detail: when investigating the issue, found out in bazel stack traces that bazel client was hanging on findMissingBlobs. Reproducing the RPC call manually, was working very long - like for reduced call from 2k to 100 entries it was still taking 20 sec. This lead to above investigation.
Vanilla 1.3 bazel remote was used (with no proxy).
While checking it, also considered changing locking around cache.Contains - currently mutex is hold for each call of contains, but this call should be fast, so having single lock hold for whole findMissingBlob could be also beneficial - although it's speculative at this point, need to do some measurements.

authors: glukasiknuro mostynb

repo: buchgr/bazel-remote


text:
Experiment: Superoptimization

Overview
FormaK aims to combine symbolic modeling for fast,
efficient system modelling with code generation to create performant
code that is easy to use.
The Five Key Elements the library provides to achieve this user experience are:

Python Interface to define models
Python implementation of the model and supporting tooling
Integration to scikit-learn to leverage the model selection and parameter tuning functions
C++ and Python to C++ interoperability for performance
C++ interfaces to support a variety of model uses

This design focuses on experimenting with the possible performance benefits from the straightforward (common subexpression elimination) to the magical: super-optimization.
The performance is relevant in two key ways:

Evaluating the runtime of the output program vs the current system
Evaluating the compile time of the super-optimizing program to see if it is sufficiently fast to be usable

This design is experimental in nature, so the end goal is only to collect this data to establish a data point from which future work can proceed. There is no goal to have this design be a full feature of the project.

docs-diff is ok (documentation changes focused on design+retro for the experiment)

repo: buckbaskin/formak


text:
pub for ObjectSignsHelper

I need the ObjectSignsHelper::merge

Expose ObjectSignsHelper now
6f89c0123d6f828cd85273f804555280325647cc

authors: lurenpluto streetycat

repo: buckyos/CYFS


text:
GNOME Shell: XEmbed vs D-Bus for system tray

С версии GNOME Shell 3.16 стал доступен трей на основе D-Bus.
http://www.webupd8.org/2015/03/gnome-316-released-with-new.html
http://www.tennhud.com/fedora-22-gnome-3-16-tray-notifications/
Надо бы протестировать и поддержать.

С другой стороны Xembed протокол работает так же.
Причем пока не ясно что лучше.
Если Xembed то нет нормального ресайза иконки, зато поведение привычное.
Если D-Bus то поведение как в Unity (нет левого клика), зато иконка масштабируется и GNOME Shell работать с ним проще.
Нужно подумать еще:)

я если и пользуюсь там, то только для выхода.

authors: buglloc skomaroh

repo: buglloc/brick


text:
Update MMM-Tools.js

danish line insert "da: "translations/da.json","

push to master ;)
thx for your purpose

You welcome
Assassins from you Forum here 😉

authors: The-Exterminator bugsounet

repo: bugsounet/MMM-Tools


text:
SWE002 No mirroring

@civilx64 @Ghesselink I had a bit of a nasty regression here that took me some time to figure out, see https://github.com/buildingSMART/ifc-gherkin-rules/commit/ee42006e63dcf6bc31e7500c0426d7d52fce7731 (tests still failing though...)
I added a 'shortcut' to "The value of attribute {attribute} must be ... " because I wanted to reuse the operators we have defined there. However I don't want to apply it to an attribute value, but to the result of some calculation (matrix determinant) so I had to alias out the "of attribute {attribute}".
https://github.com/buildingSMART/ifc-gherkin-rules/blob/ee42006e63dcf6bc31e7500c0426d7d52fce7731/features/steps/thens/attributes.py#L64-L90
In doing so the step became ambiguous with the following:
https://github.com/buildingSMART/ifc-gherkin-rules/blob/ee42006e63dcf6bc31e7500c0426d7d52fce7731/features/steps/thens/values.py#L109-L117
However, Behave never warned me about the ambiguous step (maybe because we have more complex custom parse types??) so all of a sudden a large amount of tests started failing and it took me a long time to figure out that this was because the steps got directed to another implementation.
What didn't help was that I felt there was a bit of a gap in the feature file I first looked at, because we directly compare the value of an entity instance to the expected type, I would have expected something with "its entity type".
https://github.com/buildingSMART/ifc-gherkin-rules/blob/ee42006e63dcf6bc31e7500c0426d7d52fce7731/features/ALS004_Alignment-segment-shape-representation.feature#L31-L32
So we kind of saw this coming, we have the same functionality in a bunch of permutations:

With or without attribute resolution or direct application to preceeding value
With or without explicit binary predicates
With or without ability to add Expression
With or without automatic entity type resolution

This was expected because we keep adding adhoc things and because we can only match full sentences.
Another problem I have is with the cognitive load of the attributes.py impl I referenced first here. It's not very consistent, with all the branches: there is the expression, the empty / not empty handling and now my regex with binary operands. All have different behaviour, functionality and assumptions.
I think this would be a good candidate to clean up a bit. For example by uplifting the inline binary operators to a new implementation function with those binary ops as a full blown parse type. As a guideline (not strict rule) I think we should aim for no top-level branches in the implementation functions with different functionality. I know this can be tricky with making unique sentences.

Consistently apply the attribute access in a separate step, before the then step (is that possible??)
Consistently apply the is_a() step in a separate step before the then step (is that possible??)
Make sure all steps consistently support different value types: str, number etc.
Break down complex implementation functions into separate syntax patterns.

@Ghesselink as the most familiar person with all the rules and the most eager cleaner upper, is this something you'd like to tackle in the new year?

Thanks for doing the dirty work to get to a resolution.  I am trending in the same direction of adding to this step implementation to handle comparison on results of a calculation with my current WIP for linear placement in LIP002.  I like the change to The resulting value and will plan to follow that pattern as well.
Also thanks for pointing out the dissonance on ALS004.  I agree that the step should involve a check of entity type and not of attribute value.  I've captured that as a to-do for the backlog.
In terms of the larger clean up - yes, I can certainly agree that this implementation is a prime candidate for refactoring and housekeeping.  I agree that @Ghesselink is the best candidate to lead but I will be happy to help if and where I can.
@aothms do you think this PR is ready for review as-is or is there the possibility that resolution of the failing tests (looks like IFC102 and SPS007) will affect your work here on SWE002?

Well as you said, so far not really a resolution. It seems I've coded myself in a corner that's hard to get out. Simplest was to adapt the quotes in the IFC102 feature text so that the implementation logic could be a bit further simplified.
Not sure if you were already on board at that time @civilx64 but Geert and I have long discussed whether we should make the separation between parameters and control language more clear in the scenarios.
Something like:
Then [its type] is not .IfcProductRepresentation. (excluding subtypes)

Or some other permutation of brackets/parens/quotes/backticks/tildes to consistently indicate whether something is:

prose used for matching
schema constructs -> .ADDED.
freeform literal values -> 1.0 / "hi"
'modifiers' -> excluding subtypes / A *required* relationship

I don't know how far we would go there, maybe distinguishing between datatypes is a bit overkill, but anyway.

This provides clarity for the end user and rule writer because it is more clear what words can be alternated to form different scenarios.
It helps in step disambiguation a bit like preventing SQL injection, if your pattern is something should be [{x}] without subtypes then the matching of x can never overflow into "without subtypes" because it is constrained by the square brackets.

Maybe also something to formalize and think about as a new year resolution.

repo: buildingSMART/ifc-gherkin-rules


text:
Integrate Renovate into the SSF as part of the pre-build step

Current Behavior
Currently there is no automated dependency update mechanism in the SSF. Without automated dependency updates the pipeline and the application use unmanaged, outdated dependencies which exposes it to ever-increasing technical debt and risk over time. In addition, this results in missing out on new features and bug fixes, lower agility for handling unexpected issues (including zero-day vulnerabilities), and an increased risk of being exposed to publicly known vulnerabilities.
Expected Behavior
We want to implement an automatic dependency update mechanism into the SSF to ensure that pipelines and applications are effortlessly kept up-to-date with the latest functionality and minimal exposure to vulnerabilities
Possible Solution or Alternative
We want to integrate Renovate as a step in one of our example pipelines to automatically include secure steps in the build.
Context
Renovate is part of the OpenSSF. It works out of the box and leverages a mix of crowdsourced data and your test suite to smartly detect when a dependency (or group of) can be updated without human intervention, and when a quick review is recommended to ensure the update is smooth. Also, Renovate can be easily and seamlessly into any workflow with its CLI tool which has an extremely high level of configurability.
Here is an example of a dependency update PR that Renovate automatically opens:

This looks really good. I think there are a few questions to answer here in the short and long term.

Can folks use Renovate to also verify that a particular new release was signed by trusted keys and/or has valid attestations? It's ok if the answer is "no" today but would be useful in the future. For example integrate with sigstore.
What access should Renovate have in the pipeline? I've used renovate before to create PRs, but how should Renovate's credentials or secrets be secured?
Does it make sense to have Renovate as part of the pipeline itself or as part of a separate step?

I haven't used Renovate a ton, but I think there are a few separate options we have in including it as either a step in SSF or as a component in SSF

I am still new to this project and to Renovate. Please take this into consideration when reading my following feedback.
Establishing an automated dependencies update is a good idea when the project has a solid CI which can validate that the update is not breaking anything.

Thanks Michael, my answers to your questions below:

Can folks use Renovate to also verify that a particular new release was signed by trusted keys and/or has valid attestations? It's ok if the answer is "no" today but would be useful in the future. For example integrate with sigstore.

At the moment Renovate doesn't look into this.

What access should Renovate have in the pipeline? I've used renovate before to create PRs, but how should Renovate's credentials or secrets be secured?

Renovate typically runs in a one-to-many fashion (i.e. it's not common to set it up once in every repo's pipeline, but rather once centrally for an org / group of orgs). Renovate only needs permissions to create branches and PRs. The credentials or secrets can be configured in the pipeline using environment variables.

Does it make sense to have Renovate as part of the pipeline itself or as part of a separate step?

Renovate is easier to set up and maintain in one central location rather than per repo, and it runs independently of whether a commit was made. With that in mind I think it makes more sense to run Renovate as a separate step rather than as part of the pipeline itself, although it can also potentially be run within the pipeline itself.
Importantly, Renovate's execution should not be linked to commits in a repository alone. Even if a repo has no commits for a month, Renovate should still be executing regularly to notify when newer versions of dependencies are available.

Establishing an automated dependencies update is a good idea when the project has a solid CI which can validate that the update is not breaking anything.

I agree with your statement, and each project needs to evaluate their risk independently. Inadequate tests is one form of risk (including for security) because it doesn't allow projects to fix problems nimbly. On the other hand, having outdated dependencies is an additional risk because they tend to have more vulnerabilities and reduce your agility for fixing urgent problems.

I think it would be valuable to have Renovate through SSF generate attestations that a project's dependencies have gone through appropriate updates.

authors: GuyBarGil lmilbaum mlieberman85

repo: buildsec/ssf


text:
parameter installedBy should be optional

according to the README the username is optional. so installedBy should be nullable but
Exception in thread "main" java.lang.IllegalArgumentException: Parameter specified as non-null is null: method com.builtamont.cassandra.migration.internal.metadatatable.AppliedMigration.<init>, parameter installedBy
       	at com.builtamont.cassandra.migration.internal.metadatatable.AppliedMigration.<init>(AppliedMigration.kt)
       	at com.builtamont.cassandra.migration.internal.dbsupport.SchemaVersionDAO.findAppliedMigrations(SchemaVersionDAO.java:238)
       	at com.builtamont.cassandra.migration.internal.info.MigrationInfoServiceImpl.refresh(MigrationInfoServiceImpl.kt:58)
       	at com.builtamont.cassandra.migration.internal.command.Migrate.run(Migrate.kt:71)
       	at com.builtamont.cassandra.migration.CassandraMigration$migrateAction$1.execute(CassandraMigration.kt:357)
       	at com.builtamont.cassandra.migration.CassandraMigration$migrateAction$1.execute(CassandraMigration.kt:342)
       	at com.builtamont.cassandra.migration.CassandraMigration.execute$cassandra_migration(CassandraMigration.kt:265)
       	at com.builtamont.cassandra.migration.CassandraMigration.migrate(CassandraMigration.kt:131)
       	at com.builtamont.cassandra.migration.CommandLine.main(CommandLine.kt:73)

it seems I have an older schema, destroyed the keyspace and recreate made this error go away.

repo: builtamont-oss/cassandra-migration


text:
Problems with passing a local path to bin/hack

$ bin/hack --link ../bullet_train-core/
bullet_train is directly present in the `Gemfile`, so we'll update that line.
bullet_train-api is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-fields. Adding to the end of the Gemfile.
Could not find bullet_train-has_uuid. Adding to the end of the Gemfile.
bullet_train-incoming_webhooks is directly present in the `Gemfile`, so we'll update that line.
bullet_train-integrations is directly present in the `Gemfile`, so we'll update that line.
bullet_train-integrations-stripe is directly present in the `Gemfile`, so we'll update that line.
bullet_train-obfuscates_id is directly present in the `Gemfile`, so we'll update that line.
bullet_train-outgoing_webhooks is directly present in the `Gemfile`, so we'll update that line.
bullet_train-scope_questions is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-scope_validator. Adding to the end of the Gemfile.
bullet_train-sortable is directly present in the `Gemfile`, so we'll update that line.
bullet_train-super_scaffolding is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-super_load_and_authorize_resource. Adding to the end of the Gemfile.
bullet_train-themes is directly present in the `Gemfile`, so we'll update that line.
bullet_train-themes-light is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-themes-tailwind_css. Adding to the end of the Gemfile.

/Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:106:in `parse':  (Bundler::Dsl::DSLError)
[!] There was an error parsing `Gemfile`: Illformed requirement ["../bullet_train-core/"]. Bundler cannot continue.

 #  from /Users/jgreen/projects/bullet-train-co/bullet_train/Gemfile:100
 #  -------------------------------------------
 #  # Core packages.
 >  gem "bullet_train", "../bullet_train-core/"
 #  gem "bullet_train-super_scaffolding", "../bullet_train-core/"
 #  -------------------------------------------

        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:138:in `block in initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:138:in `map!'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:138:in `initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:63:in `new'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:63:in `create'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/dependency.rb:56:in `initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dependency.rb:31:in `initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:101:in `new'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:101:in `gem'
        from /Users/jgreen/projects/bullet-train-co/bullet_train/Gemfile:100:in `eval_gemfile'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:49:in `instance_eval'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:49:in `eval_gemfile'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:12:in `evaluate'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/definition.rb:37:in `build'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler.rb:217:in `definition'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler.rb:165:in `setup'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/setup.rb:23:in `block in <top (required)>'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/ui/shell.rb:159:in `with_level'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/ui/shell.rb:111:in `silence'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/setup.rb:23:in `<top (required)>'
        from <internal:/Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems.rb:1370:in `<top (required)>'
        from <internal:gem_prelude>:2:in `require'
        from <internal:gem_prelude>:2:in `<internal:gem_prelude>'
/Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:106:in `parse': Illformed requirement ["../bullet_train-core/"] (Gem::Requirement::BadRequirementError)
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:138:in `block in initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:138:in `map!'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:138:in `initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:63:in `new'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/requirement.rb:63:in `create'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/dependency.rb:56:in `initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dependency.rb:31:in `initialize'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:101:in `new'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:101:in `gem'
        from /Users/jgreen/projects/bullet-train-co/bullet_train/Gemfile:100:in `eval_gemfile'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:49:in `instance_eval'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:49:in `eval_gemfile'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/dsl.rb:12:in `evaluate'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/definition.rb:37:in `build'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler.rb:217:in `definition'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler.rb:165:in `setup'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/setup.rb:23:in `block in <top (required)>'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/ui/shell.rb:159:in `with_level'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/ui/shell.rb:111:in `silence'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/bundler/setup.rb:23:in `<top (required)>'
        from <internal:/Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /Users/jgreen/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems.rb:1370:in `<top (required)>'
        from <internal:gem_prelude>:2:in `require'
        from <internal:gem_prelude>:2:in `<internal:gem_prelude>'

It does modify the Gemfile, but not in the correct way. All of the BT lines look like this:
gem "bullet_train", "../bullet_train-core/"
gem "bullet_train-super_scaffolding", "../bullet_train-core/"

But they should look like this:
gem "bullet_train", "../bullet_train-core/bullet_train"
gem "bullet_train-super_scaffolding", "../bullet_train-core/bullet_train-super_scaffolding"

Interesting, it's working fine for me against main, so I'll have to dig and see where the bug is.

bin/hack --link ../bullet_train-core/
> git log -1
commit 556030da0b39e8721acd338e0b04da2d1a71221a (HEAD -> testing, origin/main, origin/HEAD, main)
Author: Jeremy Green <jagthedrummer@gmail.com>
Date:   Mon Aug 28 14:02:10 2023 -0700

    Show BulletTrain gems in stack traces by default (#933)

    * Show BulletTrain gems in stack traces by default

    Fixes https://github.com/bullet-train-co/bullet_train/issues/681

    * heckin linter
> bin/hack --link ../bullet_train-core/
bullet_train is directly present in the `Gemfile`, so we'll update that line.
bullet_train-api is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-fields. Adding to the end of the Gemfile.
Could not find bullet_train-has_uuid. Adding to the end of the Gemfile.
bullet_train-incoming_webhooks is directly present in the `Gemfile`, so we'll update that line.
bullet_train-integrations is directly present in the `Gemfile`, so we'll update that line.
bullet_train-integrations-stripe is directly present in the `Gemfile`, so we'll update that line.
bullet_train-obfuscates_id is directly present in the `Gemfile`, so we'll update that line.
bullet_train-outgoing_webhooks is directly present in the `Gemfile`, so we'll update that line.
bullet_train-scope_questions is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-scope_validator. Adding to the end of the Gemfile.
bullet_train-sortable is directly present in the `Gemfile`, so we'll update that line.
bullet_train-super_scaffolding is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-super_load_and_authorize_resource. Adding to the end of the Gemfile.
bullet_train-themes is directly present in the `Gemfile`, so we'll update that line.
bullet_train-themes-light is directly present in the `Gemfile`, so we'll update that line.
Could not find bullet_train-themes-tailwind_css. Adding to the end of the Gemfile.

  Fetching gem metadata from https://rubygems.org/.......
  Using rake 13.0.6
  Using minitest 5.19.0
  Using builder 3.2.4
  Using erubi 1.12.0
  Using racc 1.7.1
  Using concurrent-ruby 1.2.2
  Using crass 1.0.6
  Using nio4r 2.5.9
  Using websocket-extensions 0.1.5
  Using marcel 1.0.2
  Using mini_mime 1.1.5
  Using rack 2.2.8
  Using date 3.3.3
  Using timeout 0.4.0
  Using ast 2.4.2
  Using public_suffix 5.0.3
  Using aws-partitions 1.812.0
  Using jmespath 1.6.2
  Using aws_cf_signer 0.1.3
  Using base64 0.1.1
  Using awesome_print 1.9.2
  Using bindex 0.8.1
  Using debug_inspector 1.1.0
  Using aws-eventstream 1.2.0
  Using bcrypt 3.1.19
  Using msgpack 1.7.2
  Using chronic 0.10.2
  Using http-accept 1.7.0
  Using unf_ext 0.0.8.2
  Using mime-types-data 3.2023.0808
  Using netrc 0.11.0
  Using bundler 2.4.10
  Using thor 1.2.2
  Using zeitwerk 2.6.11
  Using cancancan 3.5.0
  Using bullet_train-scope_validator 1.3.18 from source at `local/bullet_train-core/bullet_train-scope_validator`
  Using phonelib 0.8.3
  Using method_source 1.0.0
  Using thread-local 1.1.0
  Using orm_adapter 0.5.0
  Using commonmarker 0.23.10
  Using pwned 2.0.2
  Using email_reply_parser 0.5.11
  Using fastimage 2.2.7
  Using hiredis 0.6.3
  Using charlock_holmes 0.7.7
  Using http_accept_language 2.1.1
  Using mini_magick 4.12.0
  Using ffi 1.15.5
  Using possessive 1.0.1
  Using pagy 6.0.4
  Using htmlentities 4.3.4
  Using faraday-net_http 3.0.2
  Using ruby2_keywords 0.0.5
  Using multipart-post 2.3.0
  Using connection_pool 2.4.1
  Using unicode-version 1.3.0
  Using xxhash 0.5.0
  Using hashie 5.0.0
  Using jwt 2.7.1
  Using multi_xml 0.6.0
  Using hashids 1.0.6
  Using version_gem 1.1.3
  Using matrix 0.4.2
  Using stripe 9.0.0
  Using regexp_parser 2.8.1
  Using chunky_png 1.4.0
  Using sexp_processor 4.17.0
  Using coderay 1.1.3
  Using colorize 1.1.0
  Using io-console 0.6.0
  Using rotp 6.2.2
  Using docile 1.4.0
  Using erubis 2.7.0
  Using honeybadger 5.2.1
  Using foreman 0.87.2
  Using json 2.6.3
  Using knapsack_pro 5.6.0
  Using language_server-protocol 3.17.0.3
  Using lint_roller 1.1.0
  Using rails_autoscale_agent 0.12.0
  Using require_all 3.0.0
  Using ruby-progressbar 1.13.0
  Using rainbow 3.1.1
  Using parallel 1.23.0
  Using pg 1.5.3
  Using rexml 3.2.6
  Using rqrcode_core 1.2.0
  Using websocket 1.2.9
  Using simplecov-html 0.12.3
  Using unicode-display_width 2.4.2
  Using rubyzip 2.3.2
  Using simplecov_json_formatter 0.1.4
  Using minitest-retry 0.2.2
  Using websocket-driver 0.7.6
  Using nokogiri 1.15.4 (x86_64-linux)
  Using puma 6.3.1
  Using tzinfo 2.0.6
  Using net-protocol 0.2.1
  Using parser 3.2.2.3
  Using i18n 1.14.1
  Using rack-test 2.1.0
  Using addressable 2.8.5
  Using binding_of_caller 1.0.0
  Using sentry-ruby 5.10.0
  Using rack-cors 2.0.1
  Using warden 1.2.9
  Using sprockets 4.2.0
  Using aws-sigv4 1.6.0
  Using mime-types 3.5.1
  Using unf 0.1.4
  Using figaro 1.2.0
  Using ruby-vips 2.1.4
  Using faraday 2.7.10
  Using faraday-multipart 1.0.4
  Using rack-mini-profiler 3.1.1
  Using bootsnap 1.16.0
  Using redis-client 0.16.0
  Using unicode-emoji 3.3.2
  Using omniauth 1.9.2
  Using snaky_hash 2.0.1
  Using code_analyzer 0.5.5
  Using pry 0.14.2
  Using reline 0.3.8
  Using postmark 1.24.0
  Using selenium-webdriver 4.11.0
  Using simplecov 0.22.0
  Using rqrcode 2.2.0
  Using net-pop 0.1.2
  Using net-smtp 0.3.3
  Using activesupport 7.0.7.2
  Using css_parser 1.14.0
  Using launchy 2.5.2
  Using net-imap 0.3.7
  Using rubocop-ast 1.29.0
  Using aws-sdk-core 3.181.0
  Using domain_name 0.5.20190701
  Using loofah 2.21.3
  Using image_processing 1.12.2
  Using xpath 3.2.0
  Using ruby-openai 5.1.0
  Using simpleidn 0.2.1
  Using sidekiq 7.1.2
  Using pry-stack_explorer 0.6.1
  Using redis 5.0.7
  Using irb 1.7.4
  Using rails-dom-testing 2.2.0
  Using globalid 1.1.0
  Using mail 2.8.1
  Using activemodel 7.0.7.2
  Using active_hash 3.2.0
  Using premailer 1.21.0
  Using factory_bot 6.2.1
  Using indefinite_article 0.2.5
  Using letter_opener 1.8.1
  Using oauth2 2.0.9
  Using rubocop 1.56.1
  Using rails_best_practices 1.23.2
  Using aws-sdk-kms 1.71.0
  Using http-cookie 1.0.5
  Using rails-html-sanitizer 1.6.0
  Using capybara 3.39.2
  Using debug 1.8.0
  Using activejob 7.0.7.2
  Using activerecord 7.0.7.2
  Using bullet_train-roles 1.3.18
  Using extended_email_reply_parser 0.5.1
  Using sentry-sidekiq 5.10.0
  Using valid_email 0.1.4
  Using omniauth-oauth2 1.7.3
  Using rubocop-performance 1.19.0
  Using standard-custom 1.0.2
  Using aws-sdk-s3 1.134.0
  Using actionview 7.0.7.2
  Using rest-client 2.1.0
  Using microscope 1.1.1
  Using capybara-email 3.0.2
  Using pagy_cursor 0.6.0
  Using standard-performance 1.2.0
  Using omniauth-stripe-connect 2.10.1
  Using actionpack 7.0.7.2
  Using nice_partials 0.9.3
  Using jbuilder 2.11.5
  Using cloudinary 1.27.0
  Using activestorage 7.0.7.2
  Using actionmailer 7.0.7.2
  Using actioncable 7.0.7.2
  Using omniauth-rails_csrf_protection 0.1.2
  Using railties 7.0.7.2
  Using sprockets-rails 3.4.2
  Using standard 1.31.0
  Using premailer-rails 1.12.0
  Using postmark-rails 0.22.1
  Using cable_ready 5.0.1
  Using actionmailbox 7.0.7.2
  Using actiontext 7.0.7.2
  Using responders 3.1.0
  Using doorkeeper 5.6.6
  Using cssbundling-rails 1.2.0
  Using factory_bot_rails 6.2.0
  Using jsbundling-rails 1.1.2
  Using sentry-rails 5.10.0
  Using turbo-rails 1.4.0
  Using web-console 4.2.0
  Using stimulus-rails 1.2.2
  Using devise 4.9.2
  Using rails 7.0.7.2
  Using devise-pwned_password 0.1.10
  Using bullet_train-fields 1.3.18 from source at `local/bullet_train-core/bullet_train-fields`
  Using devise-two-factor 5.0.0
  Using bullet_train-has_uuid 1.3.18 from source at `local/bullet_train-core/bullet_train-has_uuid`
  Using bullet_train-routes 1.0.0
  Using bullet_train-super_load_and_authorize_resource 1.3.18 from source at `local/bullet_train-core/bullet_train-super_load_and_authorize_resource`
  Using bullet_train-themes 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-themes`
  Using showcase-rails 0.4.6
  Using jbuilder-schema 2.2.0
  Using bullet_train-integrations 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-integrations`
  Using bullet_train-integrations-stripe 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-integrations-stripe`
  Using bullet_train-obfuscates_id 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-obfuscates_id`
  Using bullet_train-outgoing_webhooks 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-outgoing_webhooks`
  Using bullet_train-scope_questions 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-scope_questions`
  Using bullet_train-sortable 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-sortable`
  Using magic_test 0.0.9
  Using bullet_train 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train`
  Using bullet_train-api 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-api`
  Using bullet_train-super_scaffolding 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-super_scaffolding`
  Using bullet_train-themes-tailwind_css 1.3.18 from source at `local/bullet_train-core/bullet_train-themes-tailwind_css`
  Using bullet_train-incoming_webhooks 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-incoming_webhooks`
  Using bullet_train-themes-light 1.3.17 (was 1.3.18) from source at `../bullet_train-core/bullet_train-themes-light`
  Bundle complete! 58 Gemfile dependencies, 229 gems now installed.
  Use `bundle info [gemname]` to see where a bundled gem is installed.

> git diff
diff --git a/Gemfile b/Gemfile
index a677d6b9..a6878f22 100644
--- a/Gemfile
+++ b/Gemfile
@@ -97,20 +97,20 @@ end
 # This section is the list of Ruby gems included by default for Bullet Train.

 # Core packages.
-gem "bullet_train"
-gem "bullet_train-super_scaffolding"
-gem "bullet_train-api"
-gem "bullet_train-outgoing_webhooks"
-gem "bullet_train-incoming_webhooks"
-gem "bullet_train-themes"
-gem "bullet_train-themes-light"
-gem "bullet_train-integrations"
-gem "bullet_train-integrations-stripe"
+gem "bullet_train", path: "../bullet_train-core/bullet_train"
+gem "bullet_train-super_scaffolding", path: "../bullet_train-core/bullet_train-super_scaffolding"
+gem "bullet_train-api", path: "../bullet_train-core/bullet_train-api"
+gem "bullet_train-outgoing_webhooks", path: "../bullet_train-core/bullet_train-outgoing_webhooks"
+gem "bullet_train-incoming_webhooks", path: "../bullet_train-core/bullet_train-incoming_webhooks"
+gem "bullet_train-themes", path: "../bullet_train-core/bullet_train-themes"
+gem "bullet_train-themes-light", path: "../bullet_train-core/bullet_train-themes-light"
+gem "bullet_train-integrations", path: "../bullet_train-core/bullet_train-integrations"
+gem "bullet_train-integrations-stripe", path: "../bullet_train-core/bullet_train-integrations-stripe"

I think the next step is to write tests for this and ensure everything's working properly. I plan on taking the contents of the Gemfile, placing them in a temp file, then using bin/link --hack [custom-path] to manually point to where the gems are using bundle show

Weird. I just tried again and it worked as expected. It's very likely something about my setup or repos. I may have been on a weird branch or something. If it happens again I'll try to dig in a little to see what I can figure out. Closing this for now.

No problem!

authors: gazayas jagthedrummer


text:
🛑 VODA-SA is down

In 4ede0ff, VODA-SA ($SECRET_SITE2) was down:

HTTP code: 403
Response time: 1090 ms

Resolved: VODA-SA is back up in b802c27.

repo: buluma/uptime


text:
Issues With yarn cron commands

Hi,
Having issues with crons run through command, example:
yarn run cron:masternode
Returns:
Error: 401     at rpc.call (/home/user/blockex/lib/rpc.js:51:18)     at IncomingMessage.<anonymous> (/home/user/blockex/node_modules/node-bitcoin-rpc/lib/index.js:70:7)     at IncomingMessage.emit (events.js:187:15)     at endReadableNT (_stream_readable.js:1094:12)     at process._tickCallback (internal/process/next_tick.js:63:19)
Note: I am actually using this for another project which is VerticalCoin.
Daemon is running and configured like:
`rpcuser=user
rpcpassword=pass
txindex=1
daemon=1
Daemon was compiled and binaries moved to /usr/bin,also I am using snapd for node, yarn, npm. Node version is 10.13.0.
path of /scripts/cron_block.sh has been adjusted to:
/snap/bin/node
also tried full path:
/home/user/snap/bin/node
401 to me is saying there is an authorization issue but I am not sure why. The rpc info in config.js and the daemon config file match.
See something I am missing or can give me a kick in the right direction?

There may be some compatibility issues caused by the difference between vnode and masternode usage in the RPC commands.  Have you verified that https://github.com/bulwark-crypto/bulwark-explorer/blob/master/cron/masternode.js#L25 has been converted to use vnode and other related areas? There can also be some differences in the format returned between coins.

That makes sense, thanks. Will fork and get needed changes made and see if I can get it going.

No problem, anytime, thanks.

authors: dustinengle virtopiarvn

repo: bulwark-crypto/bulwark-explorer


text:
Compact Layout

How can we minimise the distance between nodes when both of the nodes are expanded.
Please find below link for the better illustration of the problem.
@bumbeishvili could you please help me resolving this issue.
https://user-images.githubusercontent.com/77266357/115682028-b39de200-a372-11eb-9443-e2c7f7d22d44.mp4
and sample code pen is https://codepen.io/rajat-sf/pen/ZELmmLr?editors=1010
Thanks for this wonderful repository having almost ready to use code.

That's the default behavior of d3.tree, which this org chart uses.
It's possible to modify this code and force it to have a different layout, but it's a pretty complex task and currently won't be able to do it. I am only doing updates to the org chart when I have a corresponding project which involves d3 tree.
I plan to have this layout option in the v2 version, but as I said, I don't know when it will be ready

FYO above mentioned compact layout is in the development phase, it will land to development branch in 1-2 weeks time

Here is a comparison for vertical version
Normal

Compact

You can check the example of the new version from now on. I expect to publish a new version by the next week
https://user-images.githubusercontent.com/6873202/128749314-c58a20fb-f863-4dc0-8e65-78f94445d929.mp4

The new version is published, closing this.
You can get more info about the new org-chart version in this Medium article

authors: bumbeishvili rajat-sf


text:
Force remote resolution for GitHub repo usage.

In installer.rb, this branch dictates the definition of the local variable:
      if Bundler.default_lockfile.exist? && !options["update"]
        local = Bundler.ui.silence do
          begin
            tmpdef = Definition.build(Bundler.default_gemfile, Bundler.default_lockfile, nil)
            true unless tmpdef.new_platform? || tmpdef.missing_specs.any?
          rescue BundlerError => e
          end
        end
      end

On normal runs, it appears that the Definition.build line results in this error:
The git source git://github.com/neo/rails_setup.git is not yet checked out. Please run `bundle install` before trying to start your application

Which makes local set to nil, and triggers remote resolution a few lines later:
      unless local
        options["local"] ? @definition.resolve_with_cache! : @definition.resolve_remotely!
      end

Remote resolution is required for checkout of GitHub repos, since the requires_checkout? method in source/git.rb relies on allow_git_ops?, which in turn relies on @allow_remote, which is only set to true when resolve_remotely! is called.
There's probably a healthier way to fix this bug, but I am not sure what it is!

Please add test coverage for the actual bug you've fixed? Forcing it to resolve remotely when not necessary will make using it a lot slower than necessary?

@segiddins On second thought, I think I should just report the bug!

authors: mcantor segiddins

repo: bundler/bundler


text:
plugin uninstall

Fixes https://github.com/bundler/bundler/issues/5447

I will add test cases soon.

I have added --all option. So bundle plugin uninstall --all will uninstall all the installed plugins. If no plugin is installed then it does nothing.
I will add test case for the new options in next commit.

@Shekharrajak ping on the comments?

I will look into this soon.

ping @Shekharrajak

If anyone trying to work on this issue, then feel free to take. If I see no one is currently working on this issue, I will do required changes after few weeks (I am really not able to manage time for this, because of college exams and gsoc project).

Hey @Shekharrajak, do you still intend to work on this PR?

Closing as superseded by #7409.

authors: Shekharrajak colby-swandale deivid-rodriguez esasse segiddins