[BUG] CopeCop error - Rule139DoNotAssignToStringWithSmallerCapacity

Describe the bug
The CodeCop analyzer often results in following error:
Analyzer 'Microsoft.Dynamics.Nav.CodeCop.Design.Rule139DoNotAssignToStringWithSmallerCapacity' threw an exception of type 'System.NullReferenceException' with message 'System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Dynamics.Nav.CodeCop.Design.Rule139DoNotAssignToStringWithSmallerCapacity.CalculateStrSubstNoMethodResultLength(IInvocationExpression invocation, Boolean& isError) in C:\a\998\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule139DoNotAssignToStringWithSmallerCapacity.cs:line 279
at Microsoft.Dynamics.Nav.CodeCop.Design.Rule139DoNotAssignToStringWithSmallerCapacity.CalculateMaxExpressionLength(IOperation expression, Boolean& isError) in C:\a\998\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule139DoNotAssignToStringWithSmallerCapacity.cs:line 176
at Microsoft.Dynamics.Nav.CodeCop.Design.Rule139DoNotAssignToStringWithSmallerCapacity.AnalyzeConversion(OperationAnalysisContext ctx) in C:\a\998\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule139DoNotAssignToStringWithSmallerCapacity.cs:line 48
at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.<>c__DisplayClass53_1.b__1() in C:\a\998\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 766
at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock(DiagnosticAnalyzer analyzer, Action analyze, Nullable`1 info) in C:\a\998\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 1080'
To Reproduce
Using AL vsix from Partner Preview 04

@fvet, this looks like a duplicate of #4422. It should have been fixed in the latest AL extension from the marketplace. Can you verify that the issue does not reproduce anymore?

I am closing this issue because it appears that it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.


DNS Search Domain not applying

The DNS Search Domains field is not included in the generated configuration file despite being set (and applied) in the interface defaults and per client config.
Expected behaviour:
Search domain included in .conf: DNS = <IP_ADDRESS>, lan
Actual behaviour:
Search domain not included in .conf: DNS = <IP_ADDRESS>
The DNS Servers field works as expected, even with multiple entries setting , as necessary
Editing the generated .conf on the client manually to add the search domain works as expected (the core functionality appears to work without issues, just the .conf file generation needs some fixes)
I am aware of issue #46, but that discussed the viability of adding that option and also affected the UI (labeled "enhancement"), this is a bug report for an "existing" but broken feature
I am happy to provide more information and do some testing, but sadly was not able to find/fix this myself.
Versions/Configuration:
Running the Version 2 :latest docker image (hash: 9726fd3f1912f43f69aa591e5628d6e3590a2eb075cf217a96d3b715972ef28a)
config.yml is minimal:
advanced:
  log_level: trace

core:
  admin_user<EMAIL_ADDRESS>  admin_password: passwd
  import_existing: false

web:
  external_url: https://my.domain
  request_logging: true

Defaults:

Client:

File:

same issue here

I found the solution. Here is the fix:
diff --git a/internal/app/configfile/tpl_files/wg_peer.tpl b/internal/app/configfile/tpl_files/wg_peer.tpl
index 79c9643..8a4bae4 100644
--- a/internal/app/configfile/tpl_files/wg_peer.tpl
+++ b/internal/app/configfile/tpl_files/wg_peer.tpl
@@ -25,7 +25,7 @@ Address = {{ CidrsToString .Peer.Interface.Addresses }}

 # Misc. settings (optional)
 {{- if .Peer.Interface.DnsStr.GetValue}}
-DNS = {{ .Peer.Interface.DnsStr.GetValue }}
+DNS = {{ .Peer.Interface.DnsStr.GetValue }} {{- if .Peer.Interface.DnsSearchStr.GetValue}}, {{ .Peer.Interface.DnsSearchStr.GetValue }} {{- end}}
 {{- end}}
 {{- if ne .Peer.Interface.Mtu.GetValue 0}}
 MTU = {{ .Peer.Interface.Mtu.GetValue }}
@@ -62,4 +62,4 @@ PresharedKey = {{ .Peer.PresharedKey }}
 {{- end}}
 {{- if and (ne .Peer.PersistentKeepalive.GetValue 0) (eq .Peer.Interface.Type "client")}}
 PersistentKeepalive = {{ .Peer.PersistentKeepalive.GetValue }}
-{{- end}}
\ No newline at end of file
+{{- end}}

should be fixed now


How can I code this android imagery app from scratch?

How can I code this android imagery app from scratch?

The Android camera demo in tensorflow/examples/android may be relevant as an example implementation for you.
For further assistance please refer your questions to Stack Overflow as this is neither a bug nor a feature request.


32bit?

Just wanna know if it's possible to make it 32bit compatible.

Normally that's just a matter of changing build flags in https://github.com/dannyvankooten/browserpass/blob/master/makefile#L26

To answer the question: yes, it is possible, as was suggested above.
However, I don't see a point in keeping this request open, especially as nobody :+1: it as of today. We have nowhere to even test the binary 🙂
So, I'll close this issue for cleanup purposes, and if someone needs this, please create a PR.


Validate only one non-negated namespace for treeSelect

If multiple non-negated namespaces are set for treeSelect, this object
will not be propagated to anywhere, in which case the user should use
none selector instead.
Tested: make test

/assign @adrianludwin
/assign @yiqigao217

/lgtm

Oh right - Thanksgiving in the USA.
/hold cancel


"End time cannot be before start time" from Quartz during getting trigger that have EndTime in past

I am using Quartz.NET. and Quartz.Spi.MongoDbJobStore v 3.1.0
I run into the following issue: imagine Job that have triggers in past. To be more specific: today is 1/20/2022, so lets say trigger
StartTime 2021-12-27 01:00:00.000Z
EndTime 2021-12-27 01:00:00.000Z
NextFireTime 2021-12-27 01:00:00.000Z
This case is possible if for some reason my server was turned off (or down) at the time the trigger should fire.
Once I turn the server on back (after EndTime 2021-12-27 01:00:00.000Z) I want Quartz puck up the missed trigger and fire it right away.
So Quartz.Spi.MongoDbJobStore calls Quartz.Spi.MongoDbJobStore.Models.CalendarIntervalTrigger.GetTrigger() (for Cron triggers there is similar flow)
The method creates new CalendarIntervalTrigger() and then tries to FillTrigger().

As we see StartTime for new CalendarIntervalTrigger is not provided. So by default Quartz thru getter returns SystemTime.UtcNow() - let it be as of today 2022-01-22 03:55:00.000Z

Later when in FillTrigger() we assign EndTime (which is 2021-12-27 01:00:00.000Z) before we assing StartTime (2022-01-22 03:55:00.000Z)

then Quartz throws an exception with message "End time cannot be before start time" because of the logic it has in setter

So in FillTrigger() we need assign first StartTime then EndTime

Fixed with 4.0.0-preview.2


Suite count is off?

Using the BDD reporter on https://github.com/IgniterHQ/overmind-github reports the following:
Overmind-Github
✓ should accept POST requests to valid projects github push endpoint
✓ should not accept POST requests to invalid projects github push endpoint
✓ should not accept POST requests without a token
✓ should create an event in the proper container
✔ 4 tests complete (56ms)
the json reporter is showing
{"stats":{"suites":2,"tests":4,"passes":4,"failures":0,"start":"2012-01-18T04:38:09.224Z","end":"2012-01-18T04:38:09.272Z","duration":48}, ...

Unless I'm missing something...

oh you know what, it's probably counting the root suite, we should decrement it i guess since that's not really desired haha


Is using values instead of pointers is by design?

I noticed that gen-go-pugin generates code which uses values, so the code looks like:
// The greeting service definition.
// go:plugin type=plugin version=1
type Greeter interface {
	SayHello(context.Context, GreetReq) (GreetResp, error)
}

While gRPC plugin generates this code from the same *.proto definition:
// GreeterClient is the client API for Greeter service.
//
// For semantics around ctx use and closing/ending streaming RPCs, please refer to https://pkg.go.dev/google.golang.org/grpc/?tab=doc#ClientConn.NewStream.
type GreeterClient interface {
	SayHello(ctx context.Context, in *GreetReq, opts ...grpc.CallOption) (*GreetResp, error)
}

This also makes gopls complain about copying of sync.Mutex:

If it's by design, I would like to learn more about it.

personally, I doubt this is by design and unless someone screams you can raise a PR to change it, worst case we can revert if get a late scream. This is a detail important to finalize before any 1.0

Looks like we should change it to pointers.


Transport formatter options schema

When writing my own custom formatter it would very useful to know the schema for the options object that is passed to the formatter. Does this exist already or would it be possible to be made?

weird, just ran it on a project of mine and got the expected:
formatter options: { colorize: true,
  json: false,
  level: 'debug',
  message: 'App setup done, loaded layers: [...]',
  meta: {},
  stringify: undefined,
  timestamp: [Function: tsFormat],
  showLevel: true,
  prettyPrint: false,
  raw: false,
  label: null,
  logstash: false,
  depth: null,
  formatter: [Function: formatter],
  align: false,
  humanReadableUnhandledException: false }

perhaps you sent in an object with recursive references?
And well, I guess there might be some enumerable: false property (even if currently looking for then in winston's codebase is an empty set: https://github.com/winstonjs/winston/search?q=enumerable&type=Code).
But even in that case:

If it's hidden hardly will be reported in an eventual schema
You'll still be able to see/access them in a debugger anyway.

@Nokel81 are you using winston@2 or winston@3?

I am using winston@3

Interesting – just to be clear if you are talking about filter or rewritersfromwinston@2` please see the Upgrade Guide.
Defining and documenting the schema of info objects in winston@3 (and what formats add what properties) would be very useful documentation. Will leave this open as a way to track those docs.

Related to https://github.com/winstonjs/logform/issues/9


Update index.asciidoc

I think the term for adding or replacing data is usually enrichment, not enhancement.

@karenzone mind reviewing this one? should be a quick one. :)

@DanRoscigno can you rebase this PR?

Remaining changes picked up  in #41


update sidestream to latest version with fixes and per IP logging

This change is

LGTM

Merging myself to trigger the travis build now.


Add deprecation notice to passing "" to CMAKE_CUDA_ARCHITECTURES

Description
Deprecate usage of CMAKE_CUDA_ARCHITECTURES="" in preference of CMAKE_CUDA_ARCHITECTURES=NATIVE which is significantly more clear on intention.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The cmake-format.json is up to date with these changes.

/merge


Add comment box & save comment functionality on task details modal

A box at top of the comments list, when press enter should make a post request. similar to the code resources/assets/js/components/partials/discussiondetails.vue

I can do this one!


[BEAM-10607] [WIP] Support micro-second ZetaSQL TIMESTAMP in BeamSQL

ZetaSQL TIMESTAMP type is matched with BEAM Logical type TIMESTAMP.
ZetaSQL TIMESTAMP type microsecond precision supported.
ZetaSQL Tests related with TIMESTAMP type updated.
ZetaSQL StreamingSqlTest fixed.
CalciteSQL logic and tests need to be fixed.

cc: @robinyqiu @apilloud

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

cc: @robinyqiu Would you please take a look at test cases BeamSqlDslAggregationTest.testSessionWindowWithBounded() and BeamSqlDslStdOperatorTest.testAvg() if possible. Thanks in advance.

Thanks Zijie for this great prototype. I will continue this work based on this PR.
There are four things that we need to finish before this feature can go into production:

Fix the current tests breaking on CalciteSQL dialect side
Map to a new logical type that represents microsecond instant (cc: @TheNeuralBit )
Add an option to choose either throw an error or truncate as discussed in the comment above
Add support to reading and writing the microsecond instant type in IOs (BigQuery/PubSub)

Thank you Zijie! and thanks for the plan @robinyqiu!
I have a PR up for item (2): #12764 - it adds a micros_instant type in Java and Python and verifies compatibility.


cordova_plugin_media problems in android 5.0.2

We are using the cordova_plugin_media in androids apps. We use the plugin with audios that are load in remote server, with an url. It´s functioning perfect in almost all the devices that we tested. We have a problem with android 5.0.2 in a MOTO E (the only device that we have with this version of android)
The problem is that the audio start and jump to differents points. We haven´t a continuos playback. We have to push stop, play, stop and play to have a continuos playback. He have this issue, only en android 5.0.2. We tested in a 5.1 in a Nexus device, and works perfect..
Can you help us with this?
Thanks

We will have to track down a device with this OS.


Casting Code Completion Doesn't Detect Inherited Members

Godot version:
3.1 alpha
OS/device including version:
Windows 10
Issue description:
When casting a reference, autocompletion doesn't account for inherited members.
extends Node2D
class_name Space

var row:int
var col:int

func _ready():
	pass

Note how you don't see any help for Node2D members, which Space inherits, only the members for Space itself.

Works in 3.2


Transform custom-metrics into an addon

Instead of keeping the custom-metrics-api separate and experimental https://github.com/coreos/kube-prometheus/tree/master/experimental/custom-metrics-api, move it into jsonnet and use the same already deployed k8s-prometheus-adapter. The adapter supports custom-metrics (and also external-metrics) for awhile now and we are using it in production without issues.
What do you think?
I'm happy to re-generate the manifests if this looks reasonable.

Thanks for your PR.
cc @s-urbaniak as you might know more about this.

I don't think we're ready to do this yet. None of the scalability limitations around the custom/external metrics adapter part of it have been solved, that were the reason for us not including it by default.

yes, agreed. I share the same assertion that prometheus-adapter is not production ready yet regarding custom and external metrics.

I share the same assertion that prometheus-adapter is not production ready yet regarding custom and external metrics.

Do you have further details on what is currently missing / a list of open items? Are they affecting both custom/external metrics or just one of them?

Some plans for the future were mentioned in our talk at KubeCon:
https://youtu.be/cIoOAbzhR7k?t=1396
But hopefully, there are some issues for people to start with.

I believe @s-urbaniak started writing a design doc for these improvements. Can we maybe publish it in the state that we have it even if incomplete?

I’m happy with this especially as it’s an opt in. Giving @lilic and @s-urbaniak also a chance to review.

Friendly ping to @lilic and @s-urbaniak :-)
No idea why travis says this is pending as clicking on details actually says it passed 🤔

No idea why travis says this is pending as clicking on details actually says it passed 🤔

We have been seeing this with travis lately, it does not report the status back.

Thanks a ton for bearing with us! :) :tada:


[Fastlane.swift] generate documentation

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
The goal of this PR is to make it easier for developers to use Fastlane swift by providing documentation for functions and protocol variables. The docs will also appear in Xcode Quick Help:

Description
This PR updates the swift_fastlane_api_generator to pass Action documentation attributes into Fastlane::SwiftFunction to be used for generating Swift documentation. The documentation is added to the swift_code method. This PR also adds unit tests for the new documentation functions.
Testing Steps
To run new unit tests:
bundle exec rspec ./fastlane/spec/swift_fastlane_function_spec.rb

@googlebot I signed it!

Oh wow, this is pretty awesome!

This is amazing!


@mui/x-date-pickers v 7.17 cause "Attempted import error: 'validateDate' is not exported from '@mui/x-date-pickers/internals'"

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
In a NextJS project, when using the latest @mui/x-date-pickers package v 7.17 and then build, the following warning message is raised
Attempted import error: 'validateDate' is not exported from '@mui/x-date-pickers/internals'
Honestly, I don't know what the actual impact when testing it, but the warning message is a bit concerning whereas last week it wasn't there.
See https://github.com/mui/mui-x/pull/14486 that moves the validateDate export from @mui/x-date-pickers/internals to @mui/x-date-pickers/validation
I suppose an easy fix is to use the new import path, but since that PR introduces a new validation hook, I'll leave it up to your discretion how to fix import issue.
For now, to avoid the error, I can use older version of @mui/x-date-pickers
Expected behavior 🤔

Steps to reproduce 🕹
Steps:

Create a NextJS project (probably can use vanilla React project, but I haven't test)
Install<EMAIL_ADDRESS>Add <DatePickerElement>
Build
Warning message in console

@dohomi we may be able to support older versions using try catch and dynamic import.

Load validateDate from new path i.e. import { validateDate }  from '@mui/x-date-pickers/validation'.
If imports fails then fallback to '@mui/x-date-pickers/internals'.

The other way, if we are not keeping backward compatibility, then we can go with the new import path and change the minimum version for '@mui/x-date-pickers'

Ok thanks for pointing this out.

Hi! Any workaround?

npm install<EMAIL_ADDRESS>


Increase portability

Hi, would it be possible to separate the config that makes this work from the other config so that we can more easily incorporate into our own installations? Such as making the base config files includeable from our own larger config. Many thanks for your hard work on this.

nice one, thank you for the idea
how is yazelix working for you?

thanks for your hard work on this

You're welcome!
we'll create a portability strategy here and improve on that..

I should note that both yazi's and zellij's configs wont touch your default configs
because they stay in a non-standard place for the configs
so that's a plus for safety and out-of-the-boxness
but it won't integrate into your personal config like you mention

we should

[ ] understand what we want to do here in a general level: do yazi or zellij support importing configs?
[ ] how to get there
[ ] implement it

Interesting, sounds like a good plan
yazelix is opinionated by nature, but if portability is increased, that would be a plus.
if we follow this approach, it would be probably be a nushell script.
One that generates the default config file for each program (zellij, nushell etc) then appends / overrides the yazelix stuff
I think we should split this issue into multiple ones, one for each program, because we might have to deal with this in a case-by-case scenario
yazi for instance has this: https://yazi-rs.github.io/docs/flavors/overview
so we'll turn this into a meta issue and split it up.

https://github.com/luccahuguet/yazelix/issues/29
https://github.com/luccahuguet/yazelix/issues/28
https://github.com/luccahuguet/yazelix/issues/27

thank you Rob!

I agree with you, what we want is something like what we have here in my nushell config files
https://github.com/luccahuguet/nu-files
at the end of the default config.nu and env.nu, I just append an import to my actual configs (called my_env.nu and my_config.nu)
too bad the nushell config is not really needed for yazelix haha
but it's a nice example of what we are looking for


Add Sniper Mode

Description
This pull request adds a "sniper" mode to ffuf. This lets you specify payload locations using template characters, and ffuf will then run through each one. TLDR, this now works:
./ffuf -w wordlist -u http://<IP_ADDRESS>:8000/test?feature=§aaa§&thingie=§bbb§&array[§0§]=§baz§ --mode sniper

ffuf will hit each of the payload locations above, one after the other, while preserving the other values.
Here's some background before delving into the details.
The main issue is that using ffuf to hunt for vulnerabilities rather than do content discovery can be rather clunky. What I'd like to do is take a single request that I'm interested in, highlight the locations I want to attack, and then have ffuf go through and smash my word-list at each value, one after the other, while preserving the legitimate values in the other fields I've highlighted.
Currently, a single request would need multiple command line runs and multiple request files (if you use ffuf with request files instead of building out every request by hand with flags), one for each fuzzing location. For example, the following request (an attempt to log in to GitHub):
POST /session HTTP/1.1
Host: github.com
...snip...

commit=Sign+in&authenticity_token=...redact..&login=foo&password=bar&trusted_device=&webauthn-support=supported&webauthn-iuvpaa-support=unsupported&return_to=..redact..&allow_signup=&client_id=&integration=&required_field_9b00=&timestamp=..redact..&timestamp_secret=..redact..

This would need a 14 different request files for just value side of the POST parameters, each with a FUZZ parameter. When looking at an entire application this becomes problematic. With the sniper mode that this pull request implements, instead of using 14 different request files, there is just one:
POST /session HTTP/1.1
Host: github.com
...snip...

commit=§Sign+in§&authenticity_token=§...redact..§&login=§foo§&password=§bar§&trusted_device=§§&webauthn-support=§supported§&webauthn-iuvpaa-support=§unsupported§&return_to=§..redact..§&allow_signup=§§&client_id=§§&integration=§§&required_field_9b00=§§&timestamp=§..redact..§&timestamp_secret=§..redact..§

The section sign characters can be added in vi using ctrl-k followed by shift+S+E. There are key combos for windows/macos/linux/whatever detailed here
This pull request touches a fair bit of ffuf's internals, which I'll try go over in some detail.
General arch
I tried to integrate these changes with the existing ffuf design without changing the internals too much wherever possible. The new sniper mode is a thin veil over the clusterbomb mode. It generally works like this:

The user specifies sniper mode, and the options parser does some checks to make sure the arguments are sane.
The input word-list is loaded as per the clusterbomb mode, with FUZZ used as the keyword
The job runner logic starts (Start()) and if sniper mode is configured, then the requests are parsed for template characters (§)
An array of requests is returned by SniperRequests, with one location specified by the user replaced by FUZZ in each request.
A queue job is created per request
The job runner continues as-per usual

Change summary

main.go - minor changes for new mode string
input/input.go - minor changes to support the new mode string
interactive/termhandler.go - Queue jobs are no longer just for recursion jobs, so the language has been changed in the termhandler to reflect that.
runner/simple.go - Prepare() has been modified to take a Request parameter, rather than build a new Request struct from the global config.
ffuf/config.go - InputProviderConfig now includes a Template string field which holds the payload locator symbol used by sniper mode.
ffuf/interfaces.go - RunnerProvider has been tweaked such that Prepare now requires a base request.
ffuf/job.go - QueueJob structs now hold a Request field, this is the base request used by each QueueJob when it's running. Start() has been modified to implement the sniper request parser when necessary, and additional changes made to the other methods to support pulling the base request for each job out of the queue struct.
ffuf/optionsparser.go - Changes for the additional mode and a validator for sniper configuration. This now handles the modes prior to dealing with wordlists/input commands.
ffuf/optionsparser_test.go - New file, implements test logic for the sniper validator.
ffuf/request.go - New methods to generate requests from the current config, copy requests and handle sniper request parsing logic.
ffuf/request_test.go - New file, tests for the new Request functions

Heya, definitely still keen to get this merged. I'll take a look at the merge conflicts during the week and see if i can sort it out.

Looks like the merge conflict was just the language changes in the termhandler. Easy fix

Righto, I've updated sniper mode to use the InputProvider for the template character. Currently its pulling it from the first InputProvider, which given that the section sign character is currently hard-coded shouldn't be a big deal.
Changing the job-start message is a good idea, I've made that change so the user can see how far through the sniper job queue they've progressed

Heya, keen to get this merged. Was there any other info or changes you needed from me?

I saw sniper in ffuf -h and read through this PR to understand what it does. This might come in handy!
@denandz Just a suggestion, but it might be useful to add it to https://github.com/ffuf/ffuf/wiki as well.


Update to 1.12

Updated to 1.12
Please let me know if this is good.

Thanks so much for working on this. Unfortunately I know nothing of coding so hopefully someone else can take a look at the update.

The mantle update did solve the guava problems. I took your and @gudenau's changes and updated it manually quickly, since it was faster that way. And less changes.


Update request: lightburn 1.6.04 → 1.7.02

Package name: lightburn
Latest released version: 1.7.02

Current version on the unstable channel: 1.6.04
Current version on the stable/release channel: 1.6.00

[ x ] Checked the nixpkgs pull requests

Notify maintainers
@q3k

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Note that the camera plugin is not working and it seems quite difficult to fix.
Setting camera to  "/dev/video0"
Error: cannot create camera service, the 'camerabin' plugin is missing for GStreamer 1.24.
Please install the 'bad' GStreamer plugin package.

Full log: errormessage.txt


[Plugins] Splitting into separate repos

Use case
Reporting searching and tracking bugs on plugins is really hard if all of it is in the same flutter/flutter repo.

Proposal
Please break flutter/plugins into flutter/plugin_xyz repos for each plugin, with their own issue tracking systems.
In gitlab, we could just have a separate flutter/plugins group where we could better organise repos.
While the current system is optimised for a smaller number of issues and a yet smaller number of contributors, it is not scaling well especially on the pace of official plugins development, and keeping track of plugin related issues.
Even as we develop, it is hard to search the current issues for the specific issue we are facing.

@Hixie @chinmaygarde @sethladd @eseidel I guess this is one of the most needed change. We struggle a lot because of this.

Especially that now there are around 40+ plugins whose issues are being reported in the main Flutter repository (according to the labels). It makes things a lot harder to maintain.

It's making finding and tracking specific plugin bugs/feature request harder. I would be a great change to improve the plugin's tracking.

We intentionally did the opposite to reduce the confusion around our repos. To find bugs for a particular plugin, use the labels to filter for bugs relating to that plugin.

I would also like to give my vote for splitting up the plugins into separate repos, the main reason being i would like to examine every commit made to a spesific plugin, e.g the in_app_purchase plugin. As of now you would have to search for commit messages and filter on commits in flutter/plugins, this is not a good solution, with a difficult ui and easy to miss certain commits. There is also not possible to watch and get notifications on a spesific plugin change/release. Also handling issues to a single plugin repo sounds alot simpler than having to deal with one massive repository with 5k+ issues and counting, i think. Please give this a second thought. Thanks! 😄


fix: repo description view and save

added textarea to ui/components
description truncated for repo list
description view and edit/save for repo summary

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


Make application bundle smaller using Angular v17 APIs

Is your feature request related to a problem? Please describe.
Formly is taking a big chunk of my application bundle.
Describe the solution you'd like
Mayby with newest features that Angular V17 gives we can make field types lazy using dynamic imports, NgComponentOutlet and @defer.
Describe alternatives you've considered
I can write dummy shells for field type components and use @defer inside to lazily load real component, but it's complex and time consuming task.
Additional context
None.

Hi, could you please check the following solution: https://github.com/ngx-formly/ngx-formly/issues/3064#issuecomment-1179810546 ?

@aitboudad We are not using NgModules anymore. We shifted to standalone APIs and build-in control flow. I think it's time to modernize also Formly.

I agree, I may see first if we can provide support of standalone  Api with the current version else  we'll try to provide it in v7.

I think v7 would be nice because compatibility problems of Angular v13. As standalone API's where introduced in Angular v14.

Apart from possibly dropping support for old Angular versions, the standalone migration should work in a backwards compatible way. Instead of declaring and exporting the components and directives in the modules, they can be imported and exported. A new project can directly work with the components & directives, while existing projects can continue to use the modules. Angular Material recently re-worked their code base in this way. See also: https://angular.io/guide/standalone-components#standalone-components-for-library-authors

For example my whole application and things on top of Formly that we build are using standalone APIs. But we cannot do anything about Formly Core which is reason of bloated 2mb bundle in our case.

IMO v7 should bump the minimum Angular to 17 and support standalone api. Maybe a RFC could be started to for v7.

In Angular v18 there will be even more breaking changes like new change observables for status, pristine, dirty etc. So it would be hard and super limiting to avoid introducing them also here. Especially that there is also angular material v3 migration coming.


Add file uploader component

@bengolder has requested a file uploader component or reference for use on Workforce.
We currently have a couple of different file uploader patterns present in GCF, Colorado, and (soon) Alaska. @racheledelman and @norrishung are meeting soon to see if they can converge on a design, and that's what we should pull into the styleguide.
An open question: the file uploader may be opinionated about backend implementation, depending on how much of it we bring into the styleguide. How should we handle?

Hi! Bump on this one. Since it's already built and live - let's add it to the styleguide.

@rustyritz there's some work to extract and generalize the component once it's built in a project. Luigi had already started in doing this for the file uploader, so just checked in with him about that progress. https://github.com/codeforamerica/cfa-styleguide-gem/pull/92
In the meantime, is someone wanting to use this right now? If so, are they looking for the design reference, HTML reference, or Ruby code that could be used in a Rails project? Want to know how we can be helpful.

@hartsick Thanks! We are planning on using this component for the AB 1793 document uploader (Rap Assist). Eng work hasn't begun yet but will next (?) week.

We have an immediate need on EITC for a simple, admin-facing file upload. Putting an HTML file input and giving some default styling currently results in something less than desirable.
            <%= f.cfa_input_field(:document_bundle, 'Documents bundle', type: 'file', classes: ["file-input"]) %>

Documents bundle

<input autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false" type="file" class="file-input text-input" id="intake_site_drop_off_document_bundle" value="#<ActiveStorage::Attached::One:0x00007feab123b3a8>" name="intake_site_drop_off[document_bundle]">


Smart mini-batch for node level tasks

🚀 Feature
I would appreciate a feature that implements smart minibatching algorithms like https://arxiv.org/pdf/1905.07953.pdf for node level tasks.
Motivation
I see currently batch_size and batch tensor are only concatenating graphs in the minibatch and records which graph the node corresponds to for all graphs in the batch. This works for graph level tasks very well but not a huge graph that we want to implement mini-batches by sampling the nodes and edges.

We have integrated such a feature with the NeighborSampler. You can see the reddit.py script for an example.

Is there a way to use the NeighborSampler for sampling small graphs from multiple large graphs?
For now my workaround is to concatenate a list of large graphs with the DataLoader and then simply get a first batch from the DataLoader and feed it into a NeighborSampler. However, what I cannot do anymore now is to apply a train/test mask on the subgraphs from the NeighborSampler. Is there any better way to achieve what I want to do?

This is interesting, and your solution should already work quite well. You can still use train/test masks the same as you filter your node features.

Indeed the train/test masks still work the same of course. My bad. Thank you!

Is there a way to use the NeighborSampler for sampling small graphs from multiple large graphs?
For now my workaround is to concatenate a list of large graphs with the DataLoader and then simply get a first batch from the DataLoader and feed it into a NeighborSampler. However, what I cannot do anymore now is to apply a train/test mask on the subgraphs from the NeighborSampler. Is there any better way to achieve what I want to do?

I am still not sure about some of the behaviour of my pipeline. How do I do a correct normalization in this scenario (separately for train and test split)? If I understand the NeighborSampler correctly it will also sample nodes n_id which are in num_hops distance of my initial starting nodes b_id, but may not be in the train_mask, correct?
In other words:
data.train_mask = some_mask_defined_over_all_nodes_of_all_graphs loader = NeighborSampler(data, size=5, num_hops=2, batch_size=10, shuffle=True, add_self_loops=True)  batch_1 = loader.__get_batches__(data.train_mask)[0]  sub_graph_1 = loader.__produce_subgraph__(batch_1)
sub_graph_1 now includes nodes where data.train_mask = false, and thus I did not normalize these node features.


⚠ Minecraft has degraded performance

In eab2ab9, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1249 ms

Resolved: Minecraft performance has improved in 24b9977.


2nd order administrative divisions also for Brazil?

Feature or enhancement
Currently in TW only the USA have 2nd order AD. Given that Brazil is a megadiverse country, with continental dimensions, it would be important to also have its subdivisions, not only the states, which in many cases are huge.
I am aware that we can pinpoint precise localities with coordinates, but in most cases, the NAME of the "county/province/municipality/parish/whatever" is far easier to access.
This could be eventually extended to some countries with complex biogeography, which lie in the crossroads of realms such as China or Mexico.
Location
probably "Browse OTUs" but also "Browse nomenclature and classification"
Screenshot, napkin sketch of interface, or conceptual description
No response
Your role
curator of project

could be tricky. We need a gazetteer with shape files

@proceps -- hm... aren't those suitable?
https://www.diva-gis.org/gdata

That data is GADM, which is what we already use as a base-map.  It looks like there is some new movment to curate GADM, which is good.  https://gadm.org/data.html.  I suspect our solution will be to write a generic updator against GADM files.

Is there a way that TW recognizes alternative names for areas?
For example if I use "Toscana" and someone else uses "Tuscany", both should point to the same area.

Is there a way that TW recognizes alternative names for areas? For example if I use "Toscana" and someone else uses "Tuscany", both should point to the same area.

Hm. @mjy could we use wikidata? for all possible transliterations?

I also want alternative values on geographic areas: #2506

@debpaul -- not only transliterations, but rather translations for well-known place names.
Examples:
Bavaria versus Bayern.
North Sulawesi versus Sulawesi Utara.

@debpaul that would help certain use-cases, yes.  It may resolve #2506 too, since we would have a single source of truth (not us, wiki-data).

BTW all - let's keep one issue per issue :).

I would like just have an option to put few alternative values on the name. Like Formosa = Taiwan, Ceyloy = Sri Lanka

this is not the issue for alternative values, please keep that conversation on #2506


Nominate @maresb as recurrent contributor

I'd like to nominate @maresb to be a recurrent contributor at ArviZ for all his help with the conda feedstock.

Sorry about the delay in answering. The nomination has been accepted!


creating course02 page

create a page called
btech-mechanical-engg.html under src/studies/
with headers and footers from
src/studies/btech-computer-science-engg.html
and include that in webpack.js

@darrenrector91 I'll accept your PR.

I created the new btech-mechanical-engg.html page under 'studies' and modified the webpack.config file.  This is my first open source contribution.  How should I go about testing?

I submitted a pull request

Did you need the dropdown changed too in order to reflect the new page added?

The link you gave me is dead

It's merged now
Wait upto 2min for travis bot to push to github pages

Thank you!  It feels really nice to contribute for the first time!

Thank you! It feels really nice to contribute for the first time!

here's the commit you did link
Thanks


adding 2 tests of long untagged specs

thanks. this looks fine, though tests like these are difficult to manually validate.
maybe a name like "tests_with_invalid_cvldoc" would be more clear than "untagged_tests"?

Thanks for the comment Yuval, I renamed the dir like you suggested.


Maximum size of memory cache is by default 1

MemoryPolicyBuilder defaults to 1 as the max-size. Is this a mistake? Or does this get overridden somewhere else?

You can pass in a new Max-Size in the builder https://github.com/NYTimes/Store/blob/feature/rx2/store/src/test/java/com/nytimes/android/external/store3/base/impl/MemoryPolicyBuilderTest.java#L55

True, but when a MemoryPolicy is built with an expiry policy, the max-size defaults to 1 unless specified by the user:
https://github.com/NYTimes/Store/blob/d182147d65df3d9a8e1e0718b84c89ff72838c69/store/src/main/java/com/nytimes/android/external/store3/base/impl/MemoryPolicy.java#L91

That seems like a bug. Want to pr a fix?

Sure. What value should we default to?

@pavlospt offered to get the fix in. If no progress in few days I'll ping you 🙂
Great find btw! I guess I just always set all the policy flags explicitly in personal use.

Hey @digitalbuddha & @Saketme, I opened a PR https://github.com/NYTimes/Store/pull/328. LMK if this is ok or you need any other modifications!

Oh nice. Thanks @pavlospt!

#328 Merged, closing issue


[stable/prometheus-pushgateway] Fix persistence support

What this PR does / why we need it:
It fix the persistence storage volumeMounting
Which issue this PR fixes
#16040
Special notes for your reviewer:
For some reason a very important part for the persistence PR https://github.com/helm/charts/pull/16040 was missing. I now fixed it.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Hey @cstaud,
I am sorry to bother you again but while ensuring to avoid break of existing behaviour I removed a bit to much code.
https://github.com/helm/charts/pull/16040/commits/a333ee3b7b8d019449e51fc436a701eb040616ff#diff-9ea22c362c923b40b134920415d8e7b1L52
This PR add it back again.

/assign
/ok-to-test

/lgtm


chore: update index

after https://github.com/chaos-mesh/charts/pull/4 merged, we should also update the index for this helm repo.

/cc @cwen0


Lambda Data source failed with the following error {}

Describe the bug
Unable to get error message from resolvers in pipeline
Lambda Data source failed with the following error {}
To Reproduce
create a pipeline functions, throw exception in first function of the pipeline, try to catch error message in VTL template or the response from appsync
Expected behavior
Should be able to capture error message in VTL
Screenshots

Additional context
Getting empty error object in Lambda dataloader exception block

@chaitanya11 Thank you for logging this issue.

create a pipeline functions, throw exception in first function of the pipeline, try to catch error message in VTL template or the response from appsync

Could you show us how you try to catch the error in VTL?

sure @bboure
here is my response mapping template for the first function in pipeline
#if( $context.result && $context.result.errorMessage )
    $util.error($context.result.errorMessage, $context.result.errorType, $context.result.stack)
#elseif( $context.result && $context.result.errors )
	$util.error($context.result.error, 'Error', $context.result.errors)
#else
    $util.toJson($context.result)
#end

here is my request mapping template for the second function in pipeline.
#if( $context.result && $context.result.errorMessage )
    $util.error($context.result.errorMessage, $context.result.errorType, $context.result.stack)
#elseif( $context.result && $context.result.errors )
	$util.error($context.result.error, 'Error', $context.result.errors)
#end
{
    "payload": { "query": $utils.toJson($context.prev.result) }
}

@chaitanya11  the error you see in the logs is just for debugging purpose.
According to the doc, it is up to you to handle the errors in the response template.
Looking at your response template I think there is either a typo, or you are missing an if
Try adding:
#elseif($context.error)
  $util.error($context.error.message)

@bboure since the error object is empty this condition will not occur, and program will try to convert the empty object to json which will cause unable to convert to <template> to class com.amazonaws.deepdish.transform.model.lambda.LambdaVersionedConfig error.

@chaitanya11 ok I understand. Looks like the Error thrown is Empty.
Now that I think about it, I have noticed this issue too in the past.
I think the issue is here (and here for the current version of the package)
_.assign gets rid of the message part of the Error object.
I discussed it recently in this comment, but I did not think of this use-case you are having.
I will try to confirm this is the issue and fix it.
thank you for the details!

@bboure  this scenario is working fine in aws with template version 2018-05-29 but not in simulator. With 2017-02-28 version we are facing problems in both aws and in simulator.

There is an open PR that fixe this issue:
https://github.com/aws-amplify/amplify-cli/pull/4418

thank you for your efforts @bboure 👍

Fixed with https://github.com/aws-amplify/amplify-cli/pull/4418


UnicodeEncodeError ascii

Issue Type

Bug report

Ansible and Ansible Lint details
$ ansible --version
ansible <IP_ADDRESS>
  config file = /home/user/ansible/ansible.cfg
  configured module search path = ['./library']
$ ansible-lint --version
ansible-lint 3.4.12

ansible installation method:  pip and OS package
ansible-lint installation method: pip and OS package

Desired Behaviour
$ ansible-lint main.yml > log
should works properly even if playbook contains russian symbols
Actual Behaviour (Bug report only)
If playbook contains russian symbols, output will failed
$ cat main.yml
---
- hosts: all
  tasks:
    - name: тест
      command: uname

$ ansible-lint main.yml > log
Traceback (most recent call last):
  File "/usr/bin/ansible-lint", line 11, in <module>
    load_entry_point('ansible-lint==3.4.12', 'console_scripts', 'ansible-lint')()
  File "/usr/lib/python2.7/site-packages/ansiblelint/main/__init__.py", line 126, in main
    print(formatter.format(match, options.colored))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 94-97: ordinal not in range(128)

$ ansible-playbook main.yml --syntax-check
 [WARNING]: provided hosts list is empty, only localhost is available
playbook: main.yml

I can't reproduce this I'm afraid (there have been plenty of unicode fixes in the last few releases, I'd hope most unicode issues should be fixed)
I copied your playbook into examples/unicode.yml and then ran
$ ansible --version
ansible <IP_ADDRESS>
  config file =
  configured module search path = Default w/o overrides
$ ansible-lint --version
ansible-lint 3.4.12
$ ansible-lint examples/unicode.yml
[ANSIBLE0012] Commands should not change things if nothing needs doing
examples/unicode.yml:3
Task/Handler: тест

Can you confirm your python version?

Hello, @willthames
python.x86_64                   2.7.5-48.el7
Can you try to output the log into lint.log?
ansible-lint examples/unicode.yml > lint.log
The same error is reproduced in the Bamboo when I try to print the build log

Oh yes, so it is.
From https://stackoverflow.com/a/31110377:
PYTHONIOENCODING=utf-8 bin/ansible-lint examples/unicode.yml > lint.log

works. I'm not sure if there's a better way to do it by default in python without setting that environment variable.

@willthames thanks! It's really works)))
close


perf(ui): use persistent tabs in channel management

Description:
Improve performance of channel management tab view

Motivation and Context:
Currently we unmount current tab when switching between card and list view, which results in some significant delay upon that action. This PR introduces persistent tab control component which hides inactive tabs without unmounting them.

How Has This Been Tested?
Manually

Types of changes:
Perf improvement

Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.04%) to 18.87% when pulling 332e47f8858b2f012caa0ecedb7ba12478ffff41 on korhaliv:perf/improve-channel-management into b4cc532eee878f1373a89560b5edd134c6337c01 on LN-Zap:next.


Log errors from the FastAuth frontend

Currently we get really useful error messages from clients like "HTTP response not OK". This isn't super helpful and we don't really know what's causing them. Some of the error messages make it as far as far as the recovery service where we have logging, but we have trouble working out what request came from the user in question.
We need to send these errors somewhere and have a way of associating them with a user's crash.
It's been suggested (by @MaximusHaximus) that the right way would be to attach a unique ID to all logs and server requests, displaying them in any error message shown to a user.
This is a relatively large ticket so feel free to break it up a bit.
### Tasks
- [ ] Discuss which service/tool we want to use to collect errors
- [ ] Listing out possible errors from MPC service

@DavidM-D Totally agree with this ticket. Most of the errors are surfaced through our users which is not good. Was thinking of an idea of setting up error monitoring tool like sentry or raygun to retrieve the errors.  (I personally vote for sentry)
We could potentially integrate with our slack channel so that we will have the visibility around the error on near real time.

@DavidM-D So this ticket is more about surfacing the error to our users? or more about making it easier for engineers to debug the issue?

Just to chip in from the backend side on this, we are already using tracing so from our perspective as long as you can provide us with a unique tracing id we can easily integrate it into our logs. Will require adding a new field to all user-facing APIs, but shouldn't be a big deal. Let's agree on what this will look like before we roll out other breaking changes.
CC @volovyks

So this ticket is more about surfacing the error to our users? or more about making it easier for engineers to debug the issue?

It's sort of a bit of both, we want to record errors and later we want to be able to connect user reported errors to our recorded errors.

(I personally vote for sentry)

Well then that makes sense unless @MaximusHaximus strongly objects

@DavidM-D got feedback from @MaximusHaximus on this. Concluded that we want to avoid using sentry.

What should we use then?

For failures that are coming from the FastAuth backend service, they should be logged by that service into our existing logging infrastructure.  In those cases, we should print a request ID somewhere on the error the user receives that we can use to query the backend service's logs and identify what went wrong in a more verbose manner.

For errors that are generated by services that we don’t control, we can add error tracking using Sentry to the frontend.

The main thing is that don’t want the frontend trying to track exceptions that should be generated, logged and actioned on by our backend service that we own and monitor

@DavidM-D just to clarify, is this ticket targeted on setting sentry on existing near-discovery repo to capture error logs right now? or setting up sentry on upcoming fast-auth-signer repo? (or potentially both?)

Apart from the error itself, what are the metrics that we want to capture?
(eg. Account id? Email? Device? Browser? )
CC @diogoortega @DavidM-D


Fix transparency problem when converting 32-bit images to WebP

Fixes #8729

The patch itself i rather small. The second commit, the regen of the golden test data, comes from incrementing the version numbers on PNG and Webp to make sure they get cache busted in the wild.

Thank you guys


Project/Cluster Membership lists show system members

We sometimes show system members when lists membership on both projects and clusters.

Hit another one of these today on a cluster

On refresh i got the following, which was missing admin/cluster owner

I never managed to see this behavior in projects. So I'm going to re-title the issue.

Verified on master-head 01665d0

From explore cluster --> project --> edit config no system members are seen
From RBAC --> cluster members --> verified no system members are seen.
Added user1 as a cluster member as well as project member and system is not seen in both pages


[AAP-18613] Add message attribute to AuditAction

Add status_message attribute to AuditAction model to store error messages.
The output of http://<IP_ADDRESS>:8000/api/eda/v1/audit-rules/43/actions/:
{
  "count": 1,
  "next": null,
  "previous": null,
  "page_size": 20,
  "page": 1,
  "results": [
    {
      "id": "a2935947-8ca6-4bd2-bb39-592a88681cd5",
      "name": "run_job_template",
      "status": "failed",
      "url": "",
      "fired_at": "2023-11-29T21:05:10.682933Z",
      "rule_fired_at": "2023-11-29T21:05:10.056370Z",
      "audit_rule_id": 43,
      "status_message": "Job template Hello, New  World in organization Default does not exist"
    }
  ]
}

Resolves: AAP-18613

@hsong-rh Can you create an e2e test for it we might have to add a rulebook with some bad rulebook name and see if the message shows up. I think we would have to merge this PR before the e2e test.

Changed to Draft to wait for the refactor PR to be merged first


fix: honor .global.postgresql.auth values

Description of the change
Our dependency - bitnami/postgresql chart has an option to configure auth via global scope variables. We do not consider that option when we infer secret name and key for the Backstage deployment volume mounts.
This PR adds support for:

.Values.global.postgresql.auth.existingSecret which overrides .Values.postgresql.auth.existingSecret
.Values.global.postgresql.auth.secretKeys.userPasswordKey which overrides .Values.postgresql.auth.secretKeys.userPasswordKey and (either of these) gets applied only if
.Values.global.postgresql.auth.existingSecret or .Values.postgresql.auth.existingSecret is defined

I'm using () chaining Helm ?. pipeline notation/workaround so I can avoid declaring those variables as '' in values.yaml
Existing or Associated Issue(s)

Additional Information

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
[x] JSON Schema generated.
[x] List tests pass for Chart using the Chart Testing tool and the ct lint command.

cc @vinzscam @sabre1041 @ChrisJBurns
Can you please take a look and let me know what you think? 🙂

@tumido will take a look on Tuesday Nov 28

I get scared when I see postgres auth secret values getting changed 😆, mainly because of past stress of trying to satisfy all of the scenarios that tend to cause regression to other values if not done right. Do we have good tests to ensure that when certain values are set, the correct Deployment yaml is generated? Be good to get these in if possible. Will allow us to change any code in this area with increased confidence in future.
I will add though, changes lgtm 👍

I don't have any tests at this time @ChrisJBurns . I've logged an issue to address this in future. I fully agree. 🙂


[REVIEW] Debbie's porfolio

Portfolio link
https://dann.digital

On the contact side you mention your email twice think only one time is needed. Otherwise I really like the portfolio.

On the contact side you mention your email twice think only one time is needed. Otherwise I really like the portfolio.

Thank you Tom. I've removed the duplicate email.


[BEAM-12942] Validate pubsub messages before they are published in PubsubIO

This is done in a manner that is effective both for standard beam publishing
as well as specialized Dataflow streaming pubsub publishing.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @reuvenlax

LGTM

closing/reopening to trigger tests again. Failures look unrelated and not sure how to trigger those runs speciifically.

@reuvenlax tests are passing, please merge. thanks!


*: add a API to clear tombstone store

What problem does this PR solve?
#1468
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has configuration change
Has HTTP API interfaces change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update the tidb-ansible repository
Need to be included in the release notes

@bradyjoestar Can you add a command like
store clear [id]

in tools/pd-ctl.
and add some test in tests/cmd/pdctl_test.go

@nolunch sure.
I am a newbie so it may takes some time to read the testcode.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f72cc23). Click here to learn what that means.
The diff coverage is 6.25%.

@@            Coverage Diff            @@
##             master    #1472   +/-   ##
=========================================
  Coverage          ?   67.48%
=========================================
  Files             ?      158
  Lines             ?    15338
  Branches          ?        0
=========================================
  Hits              ?    10351
  Misses            ?     4061
  Partials          ?      926

Impacted Files
Coverage Δ

server/core/store.go
77.35% <0%> (ø)

server/cluster.go
77.37% <0%> (ø)

server/api/store.go
62.79% <0%> (ø)

server/api/router.go
100% <100%> (ø)

Continue to review full report at Codecov.

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

/rebuild

/rebuild


Questions about running powershell

Trying to execute a powershell script from oemcustomizations.cmd. Haven't been able to get it working. Either the powershell script isn't executing, or we don't have elevated enough permissions to execute the script.
A lot of examples show people using net user Administrator to authenticate as admin. My question is, on a retail image where there isn't an administrator account, how does this all work?
Our end goal is that we need to execute a powershell script on first boot to query/edit registry values in HKLM:\System\CurrentControlSet\Enum\
Please advice on best approach.
Also, your link to Custom.cmd gives a 404 error.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ab5535f5-3b3e-503a-ebee-6c79c2af142c
Version Independent ID: b571e2a2-3ea8-134f-a7c5-f09e2280280c
Content: OS Customizations - Windows IoT
Content Source: windows-iotcore/build-your-image/OSCustomizations.md
Service: windows-iot
GitHub Login: @parameshbabu
Microsoft Alias: pabab

Hi @JeffMushmo - we are looking into this. Stay tuned.

@JeffMushmo I dont think the oemcustomizations.cmd runs in PowerShell but command line environment...

@JeffMushmo OEMCustomizations.cmd is invoked by IoTCore Shell (not PowerShell) on every boot with system privileges
reg.exe is the supported way to access the registry Windows 10 IoT Core Command Line Utils


Executors not spinning up successfully: Unknown host for jenkins-ui.jenkins.svc.cluster.local

Hi there,
I set up a relatively basic k8s jenkins installation using the howto guide.
It's all working fine, I only have problems with the executors not really spinning up.
Following output in the pods:

jnlp | 2017-11-24T16:32:47.268129607Z |
-- | -- | --
jnlp | 2017-11-24T16:32:47.268127569Z | ... 2 more
jnlp | 2017-11-24T16:32:47.268125423Z | at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:158)
jnlp | 2017-11-24T16:32:47.268123183Z | at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
jnlp | 2017-11-24T16:32:47.268121053Z | at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
jnlp | 2017-11-24T16:32:47.268118150Z | at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
jnlp | 2017-11-24T16:32:47.268104092Z | at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
jnlp | 2017-11-24T16:32:47.268101937Z | at sun.net.www.http.HttpClient.New(HttpClient.java:357)
jnlp | 2017-11-24T16:32:47.268099912Z | at sun.net.www.http.HttpClient.New(HttpClient.java:339)
jnlp | 2017-11-24T16:32:47.268097429Z | at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
jnlp | 2017-11-24T16:32:47.268095293Z | at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
jnlp | 2017-11-24T16:32:47.268092845Z | at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
jnlp | 2017-11-24T16:32:47.268084923Z | at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
jnlp | 2017-11-24T16:32:47.268082800Z | at java.net.Socket.connect(Socket.java:589)
jnlp | 2017-11-24T16:32:47.268080662Z | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
jnlp | 2017-11-24T16:32:47.268078609Z | at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
jnlp | 2017-11-24T16:32:47.268076247Z | Caused by: java.net.UnknownHostException: jenkins-ui.jenkins.svc.cluster.local
jnlp | 2017-11-24T16:32:47.268073853Z | at hudson.remoting.Engine.run(Engine.java:447)
jnlp | 2017-11-24T16:32:47.268071457Z | at hudson.remoting.Engine.innerRun(Engine.java:495)
jnlp | 2017-11-24T16:32:47.268068627Z | at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:161)
jnlp | 2017-11-24T16:32:47.268063800Z | java.io.IOException: Failed to connect to http://jenkins-ui.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins-ui.jenkins.svc.cluster.local
jnlp | 2017-11-24T16:32:47.268060303Z | SEVERE: Failed to connect to http://jenkins-ui.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins-ui.jenkins.svc.cluster.local
jnlp | 2017-11-24T16:32:47.268028122Z | Nov 24, 2017 4:32:47 PM hudson.remoting.jnlp.Main$CuiListener error
jnlp | 2017-11-24T16:32:27.117789622Z | INFO: Locating server among [http://jenkins-ui.jenkins.svc.cluster.local:8080/]
jnlp | 2017-11-24T16:32:27.117739627Z | Nov 24, 2017 4:32:27 PM hudson.remoting.jnlp.Main$CuiListener status
jnlp | 2017-11-24T16:32:26.962365373Z | WARNING: No Working Directory. Using the legacy JAR Cache location: /root/.jenkins/cache/jars
jnlp | 2017-11-24T16:32:26.962338983Z | Nov 24, 2017 4:32:26 PM hudson.remoting.Engine startEngine
jnlp | 2017-11-24T16:32:26.956628981Z | INFO: Jenkins agent is running in headless mode.
jnlp | 2017-11-24T16:32:26.956588789Z | Nov 24, 2017 4:32:26 PM hudson.remoting.jnlp.Main$CuiListener <init>
jnlp | 2017-11-24T16:32:26.948584652Z | INFO: Setting up slave: jnlp-ljlvs
jnlp | 2017-11-24T16:32:26.948522265Z | Nov 24, 2017 4:32:26 PM hudson.remoting.jnlp.Main createEngine
jnlp | 2017-11-24T16:32:26.323005364Z | Warning: AGENT_NAME is defined twice in command-line arguments and the environment variable
jnlp | 2017-11-24T16:32:26.323001581Z | Warning: SECRET is defined twice in command-line arguments and the environment variable
jnlp | 2017-11-24T16:32:26.322932987Z | Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior

I assume that " Failed to connect to "... is the key problem.
I opened a bash shell on the master pod and did
curl http://jenkins-ui.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/
and got back "Jenkins".
So it seems to be working?
Did I miss anything?
Update: Okay, it can't resolve the hostname on the jnlp nodes. But Why?
It also seems to work in around 10% of the cases. Puzzled.
Tobias

we are seeing something very similar atm, our jenkins deployment suddenly regressed and started showing this error on every slave start.
have you been able to solve it, @tobsch?

I gave up on this for now. But I had similar problems with "connecting to the outside world".
What solved this on those cases was running the container as root.
You could try that?
Funny but it worked.

right ok, another amusing thing is that this all of a sudden appeared first with a couple of builds and then with all builds… maybe this is the time to seriously look into replacing Jenkins :)
for the record — filed https://issues.jenkins-ci.org/browse/JENKINS-48368 upstream

I guess it's rather a GCP issue?

I managed to fixed this by changing the master to have 1 executor, then it would properly spin up slaves.
(Manage Jenkins > Configure System > # of executors)

I don't think this helps the original issue, but I had a similar problem that led me here - in my case I had configured Jenkins to run in the /jenkins/ folder so needed to modify the Jenkins URL to include that e.g. http://jenkins-ui.jenkins.svc.cluster.local:8080/jenkins/tcpSlaveAgentListener/

Thanks folks and apologies for these issues. We are now using the upstream Helm chart which should have resolved these issues and/or provides customization options for these config changes:
https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml

I am still running into this issue with a near stock Jenkins helm install on K8s 1.11. @viglesiasce What was the change made?


ASPNetCore MVC interferes with Let's Encrypt installation/automatic renewal

See this post :: http://www.westerndevs.com/Tools/Lets-Encrypt-ASPNET-Core/
The developer had to create a "WellKnownController" to be able to handle Let's Encrypt Installation.
My issue :: I can't use System.IO to access the challenge key, because my web host has aliased the directories, meaning I have no physical /.well-known/* folder.
Currently, I cannot use the Let's Encrypt with AspNetCore.
The only solution I can think of is to have AspNetCore explicitly NOT handle a route, and just let the web server handle the request.
If there is another way, I could really use some help.

Hi, so the issue here as I can tell is that you don't have access to these files - is that correct?
Are you running behind a reverse proxy? Should the proxy be serving these files?

The only solution I can think of is to have AspNetCore explicitly NOT handle a route, and just let the web server handle the request.

Generally this works the other way around, if the server doesn't handle the request then ASP.NET gets a chance to process it.
/cc @davidfowl

So this was resolved by some IIS configuration magic.
inside /.well-known/ folder, create web.config
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <handlers>
            <remove name="aspNetCore" />
        </handlers>
    </system.webServer>
</configuration>

I don't know exactly what this does, but I guess this can be closed since the web server configuration fixed it.

The only solution I can think of is to have AspNetCore explicitly NOT handle a route, and just let the web server handle the request.

OK, I'll stick my foot in my mouth. This is doing what you suggested exactly. You're putting a file in that folder that says "don't let ASP.NET run for this folder".
Glad you were able to get this solved.


Add ChainforgeLabs pool

Add ChainforgeLabs pool

How are you what time can the mempool - testnet. Fractalbitcoin. IO see the name of the new submissio @slient-coder

Hello, @slient-coder
I also submit the Logo https://github.com/fractal-bitcoin/mining-pool-logos/pull/5
Please help update the tag and logo of chainforgelabs to mempool as soon as possible,Thanks


commit url of admin password

Coverage remained the same at 100.0% when pulling 579d3f20ca148baba460016ad704c1a98b25d3a2 on PandaMino:master into 791ab69670347ce460a178b33ec1072cce00b758 on rugao-web-fullstack:master.


Misskey support

Misskey is another federated blogging platform that can interact with Mastodon. I want to follow some RSS accounts on Misskey but it stuck in Processing ...
PS: Misskey doesn't have a documentation about federation, you may need to read the source code to fix it. And here is a reference on how they handle Pleroma federation: https://git.pleroma.social/pleroma/pleroma/issues/259

Unfortunately I can't personally take the time to support projects that don't have documentation about federation. You may wish to contact Misskey and ask them to document their federation compatibility.


Sprint 69 changelog update

[skip ci]

@miq-bot add_label documentation

Looks like Travis got stuck (not sure why it was running, but ok).  Merging.


Port QuantumCircuit.count_ops() to rust

What should we add?
Right now the QuantumCircuit.count_ops() method is written in Python by iterating over the circuit data and collecting counts in a dictionary, sorting it by gate name and returning that dictionary. However, the underlying data is stored in rust's CircuitData struct and it would be much more efficient to do the counting and in rust. We should port this utility method to rust to provide and provide a significant speedup for the method.

@mtreinish I can work on this issue

Cool, thanks I've assign the issue to you.

Implemented by https://github.com/Qiskit/qiskit/pull/13050


Making pom point to defined version

stream-registry PR
Moving explicit versioning out of dependency in infra-provider-kafka pom.
PR Checklist Forms

[ ] CHANGELOG.md updated
[ ] Reviewer assigned
[ ] PR assigned (presumably to submitter)
[ ] Labels added (enhancement, bug, documentation)

https://github.com/homeaway/stream-registry/commit/e390e41e782


Wrong Jib output directory in Maven multi-module build

Description
For a multi-module Maven build the Jib output directory is wrong.
Given the following Maven multi-module setup:
.
|— a
|— b

Actual behavior; The Jib Docker tarballs are created in ./target:
.
|— a
|— b
|— target
   |—docker
     |— a.tar
     |— b.tar

Expected behavior; , The Jib Docker tarballs are created in ./a/target and ./b/target
.
|— a
   |— target
      |—docker
        |— a.tar

|— b
   |— target
      |—docker
        |— b.tar

Info

f-m-p version : 4.3.0 (and HEAD of master 17.10.2019)
Maven version (mvn -v) : 3.5.3

I can create a sample project if that would be helpful, but I think the bug is quite easy to fix. I suspect this line: https://github.com/fabric8io/fabric8-maven-plugin/blob/f75d09b1466c5e005a455b381151bdab7b2398eb/core/src/main/java/io/fabric8/maven/core/util/JibBuildServiceUtil.java#L149

@rohanKanojia : Can do. When is the cutoff for version 4.3.1? ;-)


Development

Hii there, I saw this request on good first issues. I think it's a great project. I am a currently learning python. I would appreciate if you could provide me some feedback on this. Working on this issue has helped me learn more python and also flask-mail. Thank you!


Upgraded to eslint 0.24.0 with default new rule settings

This PR upgrades to eslint 0.24.0 with all the new rules with the default settings from eslint, except for linebreak-style which I enabled as an error.
Here is the default eslintrc file from eslint/eslint as a reference:
https://github.com/eslint/eslint/blob/b09484adab0e73e41bb9be28d8423b3295e4d5ff/conf/eslint.json
A second PR will turn a lot of these rules on.
@raynos @jcorbin

lgtm.


TuyaAccessory constantly having socket errors, ECONNRESET bringing Homebridge to a grinding halt (Related to #233)

Had posted issue #233 previously, and closed it as I thought it was fixed by a Node.js update.
Turns out it is not. It was stable for a day, but had returned.
There is still repetitive errors such as this:
"[TuyaAccessory] Socket had a problem and will reconnect to ShedBulb (ECONNRESET)
[TuyaAccessory] Socket had a problem and will reconnect to ShedBulb (Error: ERR_CONNECTION_TIMED_OUT)"
This happens for every device using this plugin, and ends up freezing Homebridge.
I viewed debug logs, and now have this output:
"(node:413) UnhandledPromiseRejectionWarning: Error: getaddrinfo EAI_AGAIN app.ring.com
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
(node:413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 118)
(node:413) UnhandledPromiseRejectionWarning: Error: The onCancel handler was attached after the promise settled.
at onCancel (/homebridge/node_modules/homebridge-ring/node_modules/p-cancelable/index.js:48:12)
at makeRequest (/homebridge/node_modules/homebridge-ring/node_modules/got/dist/source/as-promise/index.js:38:13)
at Request. (/homebridge/node_modules/homebridge-ring/node_modules/got/dist/source/as-promise/index.js:143:17)
at Object.onceWrapper (events.js:422:26)
at Request.emit (events.js:315:20)
at Timeout.retry (/homebridge/node_modules/homebridge-ring/node_modules/got/dist/source/core/index.js:1264:30)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
(node:413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 119)"
I am really not sure what is happening. Any help is appreciated. TIA.

Update: My Homebridge has become completely unstable. The UI freezes so much (ERR_CONNECTION_REFUSED) that I cannot even modify the config or enter terminal commands adequately. Home app either says it cannot update devices, or it shows devices but commands to turn on/off don't work.

Update 2: I setup a Virtual Box VM with the same config, and it has been working well. I added all the Tuya devices one by one, with no issue. Then added my Ring alarm, again without issue. Since these both worked, I added my IP Cameras, which again went without issue. This just serves to further confuse me, other than I suppose there is something with how I have Hyper-V setup that is causing the failure.


Fix device sleep issue for jankbench workload

Sleeping device when waiting for workload to end was causing workload
to occasionally freeze. Changed device sleep to host sleep.
Panda dataframe.ix() is deprecated so changed to .loc()

The sleep on target is quite deliberate -- this allows the workload to be used with simulations, where on-target time might proceed at very different rate from wall-clock time. Could you provided a bit more detail regarding the freezes you're encountering when waiting on target? E.g. is it target specific? does the workload actually freeze, or is it running but the sleep not returning? or does the entire target crash for some reason? etc.

It happens on quite a few of the devices, reproducible 100% on a mate20 and pixel 4. I thought it was the sleep not returning properly but now not so sure. The workload just seems to hang after stop_event.set() and self.join() is called in JankbenchRunMonitor::stop() and the logcat stream process isn't being terminated.

A few things to check:

Is there anything abnormal in the logcat for the device that may indicate the problem?
Is this a locally connected device?
Are you able to set a breakpoint to determine where the code is getting stuck?


fix: full-results-with-wait-flag

What does this PR do?
Fixes output when the wait flag is specified.
What issues does this PR fix or reference?
@W-9346875@
Functionality Before
After running, user was told to run a second command to open the report.
Functionality After
The report is now displayed.

nit: the convention we use for branch names is developername/topic ie. aj/waitFlag :)

nit: the convention we follow for branch names is developername/topic ie. aj/waitFlag

I attempted to rename the branch but ended up closing this PR.  I created a new PR at https://github.com/forcedotcom/salesforcedx-apex/pull/242 and the branch is named, jb/waitFlag


Adding support for .env hierarchy of files to supply environment configuration

This is not the ultimate long-term goal. In the long term I'd like to have an actual configuration file that properly merges with supplied environment variables. However, due to some limitations in the existing Elixir libraries, I'm going to pass on implementing the configuration file and, to get us to MVP, add the support for .env , .env.local, .env.{ENV}, and .env.{ENV}.local files.

The PR looks good so I approved, we just went through a few iterations on slack so I wanted to confirm the behavior

The regular environment variables will override anything in a .env file. This is basic standard design for .env files.


New Patch not working , not able to download backup

Hi @horrorho  Thanks for your last patch, but that seem to be working for some time only. Currenty we are not able to download the backup of icloud.
We know like you have less time and this project is now we all need to run ourselves. We are trying but need some time and meanwhile, we request you to kindly update any new patch if needed.
Current issue: once we select specific backup to download it automatically terminate the session.

Hi. Kindly refer to #87


Update set-up-scaling-script.md

Changed Run "6. Run Get-StoredCredentials -List" to Get-StoredCredential no S on the end

Thanks for the testing and feedback @TomHickling .

#sign-off

@ChristianMontoya: I'm sorry - only the author of this article, @Heidilohr, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@Heidilohr : Please sign off on this, as Tom's PR is an accurate fix.


removed markdownShortcutPlugin, but the shortcuts are still enabled

I removed the shortcut plugin, but I can still use cmd + b to enabled bolding.

These shortcuts (cmd+*) don't come from the plugin, but are actually built-in in the core of Lexical. It's possible to disable them manually through the lexical API.


Forgot password broken

browserRedirectForgotPassword seems to be broken.
It generates an invalid url.

If I remove the client_id parameter from the url, it works and opens in safari. However, I never get a callback to my app with the url scheme that I set up.
Is it suppose to open the app after a successful forgot password request have been done? Or was that just wishful thinking from me?

You can try for yourself in your native app example

This works for me in the native client with our test client. What does your url look like and which client are you using?

Did you register your redirect uri? The redirect is supposed to redirect the user back to the login screen.

Could you send an email to<EMAIL_ADDRESS>including your logs and what client you're using?


Automated cherry pick of #2994: fix: fail to search opslog by obj_name

Cherry pick of #2994 on release/2.10.0.
#2994: fix: fail to search opslog by obj_name

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@f3d03d1). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #2995   +/-   ##
================================================
  Coverage                  ?   7.46%
================================================
  Files                     ?     414
  Lines                     ?   66018
  Branches                  ?       0
================================================
  Hits                      ?    4931
  Misses                    ?   60664
  Partials                  ?     423

Flag
Coverage Δ

#aFlag
7.46% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/opslog.go
1.94% <0%> (ø)

Continue to review full report at Codecov.

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

/approve
/lgtm


Opening a modal fails when triggering anchors are programatically created

Hi Humaan,
Greetings from another Perth frontender.
I've noticed an annoying bug with Modaal: I have a project where I dynamically add/create or remove elements to a list based on user filtering. A very basic webapp.
Some of these elements contains anchor links that are supposed to open modals. So because these links are not in the markup on page load, I have to use JavaScript to open the modals rather than using the data attributes. I also have to delegate the click handlers like this:
$(document).on('click', 'selector', e => {
    e.preventDefault();
     $(e.currentTarget).modaal();
  });

And well, that doesn't work, I have to click twice for it to open the modal. The first click does some modal initialisation stuff, but doesn't go as far as opening it.
I've found a workaround that looks like:
$(document).on('click', 'selector', e => {
    e.preventDefault();
    if(!$(e.currentTarget).data('modaal-scope')) {
      $(e.currentTarget).modaal();
      setTimeout(()=> $(e.currentTarget).trigger('click'), 20);
    } else {
      $(e.currentTarget).modaal();
    }
  });

And it works, but it lacks elegance.
I think a static method to open a modal, one that doesn't rely on an anchor/modal coupling, could solve this. Something like Modaal.open('selector'). Or you might want to investigate the way your register your events handlers.
Anyway, thanks for your great plugin.

Hey @rkgttr thanks for raising the issue and sharing your findings. I think this will be a pretty quick fix, so we'll try to prioritise it for the next milestone release.

I second this request :-)

I third this request, over a year later. Is it going to be fixed? I use delegated event binding for everything else. Seems like it ought to be just as easy for triggering Modaals.
Thanks very much, rkgttr, for the workaround.

Thanks all for your patience. Since the ticket was raised, we have implemented a new open method which will become available in the next release, but have some direction to provide on how we recommend programatically created links can be triggered to open both now, and in the next release.
As it stands, any new modaal link created programatically can be triggered to show using:
$('.my-link').modaal({ start_open: true });

The start_open: true option can be used at doc ready, or programatically to ensure it launches straight away once initialised. In the next release, we recommend using the same approach to opening programatically creating new links as it will allow you to define any other options you would like that modaal to have.
Once a modaal has been initialised, be it programatically or on doc ready, our next release will make it possible to call $('.my-link').modaal('open'); to trigger it to open. Note, this will only work if the modaal has already been initialised through $('.my-link').modaal();
We have not invested time into providing calls that look like Modaal.open() as we feel establishing any calls like that would ultimately be calling the previously outlined open methods anyway.
The other, less recommended, approach which will also works in the next release is to call $('.my-link').modaal().modaal('open');. It's not clean, or recommended because it can be simplified down to the first .modaal() with options, including start_open: true;
Please keep an eye out for the next release when the .modaal('open') becomes available.


Removal of boost::asio dependency

This PR replaces the boost::asio and boost::system dependencies with standalone asio and std::system_error and std::error_code. This allows us to completely remove any Boost dependency. This ideally shouldn't break the code in any way, but this would still require testing with the hardware to confirm (cc @nocoinman).
Fixes #15.

I tested the PR by using a TCP connection through a docker container (as specified in https://github.com/nocoinman/mosaicgnss-dev). And from the results, it seems to work fine, i.e. it is able to connect and get data from the specified IP and port, and then parse the data.


feat(circuits): add a noir circuit for merkle tree membership and JS tests for poseidon2 and pedersen

Follow-up to #234, this PR:

Adds a merkle tree membership circuit in Noir.
Adds an abstraction layer to both MTs to make it easier to simply call for example mt.add to prove addition. Sweet Noir traits!

Abstracts tree sizes away by making the libs use slices instead. This makes them useable with any array size.
Merges all the Merkle Trees implementations and tests into one single lib. This makes most of the code reusable, and makes the interface look similar.
Adds READMEs with instructions

Seems like I cannot merge, can you do it please @vplasencia ?

Hey @signorecello! At least two people should review the PR before merging. When another of the reviewers reviews it, we will merge it. Thanks.


pthreads not  found

Hello,
I tried to compile the interfaces with the rocrand back end. I keep getting this error:
intel/oneapi/compiler/2024.0/bin/icpx  -DCHECK_FUNCTION_EXISTS=pthread_create -rdynamic CMakeFiles/cmTC_87608.dir/CheckFunctionExists.cxx.o -o cmTC_87608  -lpthreads
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -lpthreads: No such file or directory

How can I fix this?
Apart from may I comment that the building instructions seems a little outdated.  It was a little bit of a struggle to get to compile the interfaces on rocm architectures with the oneAPI + codeplay plugin.
Thank you in advance,
Cristian AChim

Hello, @csccva, I see that you are trying to build Rocrand backend with Intel oneAPI compiler (icpx), but it works only with open source compiler oneAPI DPC++ Compiler or
AdaptiveCpp Compiler (formerly known as hipSYCL). Could you, please, try to take intel/llvm compiler with hip amd support and build with -DCMAKE_CXX_COMPILER=clang++ (or as alternative use AdaptiveCPP compiler)?
Thank you for pointing out on outdated rocm build info, we will check and update it.

Hello, @csccva, I see that you are trying to build Rocrand backend with Intel oneAPI compiler (icpx), but it works only with open source compiler oneAPI DPC++ Compiler or AdaptiveCpp Compiler (formerly known as hipSYCL). Could you, please, try to take intel/llvm compiler with hip amd support and build with -DCMAKE_CXX_COMPILER=clang++ (or as alternative use AdaptiveCPP compiler)?
Thank you for pointing out on outdated rocm build info, we will check and update it.

Hello,
Thank you for your reply.
I just tried the same with the clang from the intel llvm project and get similar error (related to pthreads)
cmake .. -DCMAKE_CXX_COMPILER=/scratch/project_462000007/cristian/NEW/apps/sycl_workspace/llvm/build/bin/clang++  -DCMAKE_C_COMPILER=/scratch/project_462000007/cristian/NEW/apps/sycl_workspace/llvm/build/bin/clang -DENABLE_ROCRAND_BACKEND=True -DENABLE_MKLCPU_BACKEND=False -DENABLE_MKLGPU_BACKEND=False -DHIP_TARGETS=gfx90a

/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: CMakeFiles/cmTC_6d7b1.dir/src.cxx.o: in function `main':
src.cxx:(.text+0x25): undefined reference to `pthread_create'
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: src.cxx:(.text+0x2e): undefined reference to `pthread_detach'
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: src.cxx:(.text+0x37): undefined reference to `pthread_cancel'
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: src.cxx:(.text+0x44): undefined reference to `pthread_join'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

....

Building CXX object CMakeFiles/cmTC_371cc.dir/CheckFunctionExists.cxx.o
/scratch/project_462000007/cristian/NEW/apps/sycl_workspace/llvm/build/bin/clang++   -DCHECK_FUNCTION_EXISTS=pthread_create -MD -MT CMakeFiles/cmTC_371cc.dir/CheckFunctionExists.cxx.o -MF CMakeFiles/cmTC_371cc.dir/CheckFunctionExists.cxx.o.d -o CMakeFiles/cmTC_371cc.dir/CheckFunctionExists.cxx.o -c /scratch/project_462000007/cristian/NEW/oneMKL/build/CMakeFiles/CheckLibraryExists/CheckFunctionExists.cxx
Linking CXX executable cmTC_371cc
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_371cc.dir/link.txt --verbose=1
/scratch/project_462000007/cristian/NEW/apps/sycl_workspace/llvm/build/bin/clang++  -DCHECK_FUNCTION_EXISTS=pthread_create -rdynamic CMakeFiles/cmTC_371cc.dir/CheckFunctionExists.cxx.o -o cmTC_371cc  -lpthreads
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -lpthreads: No such file or directory

Though it isn't stricktly supported by oneMKL Interface Library, the oneAPI base toolkit with Codeplay's plugins for AMD seems to be able to build the rocRAND backend fine for me.
The CMake for rocRAND does import the threads package as find_package(Threads REQUIRED). To me it looks as if you're having the issue at configure time, not when actually trying to build oneMKL Interface library, and that this issue occurs in find_package(Threads REQUIRED). Is that right? In which case, this isn't an issue with the rocRAND backend. To confirm this, it might be worth using the --debug-output and --trace cmake flags. Its also worth noting that the linking error appears to come from /usr/x86_64-suse-linux/bin/ld, not part of the oneAPI base toolkit.
 Is it installed somewhere that the compiler would be looking for it? On Ubuntu I think it is at /lib/x86_64-linux-gnu/libpthread.so - I don't know about SUSE.
We're aware that the build documentation could do with improvement. There is an issue for it here. I've started rewriting some of the documentation, although it isn't ready for a PR yet.

Though it isn't strictly supported by oneMKL Interface Library, the oneAPI base toolkit with Codeplay's plugins for AMD seems to be able to build the rocRAND backend fine for me.
The CMake for rocRAND does import the threads package as find_package(Threads REQUIRED). To me it looks as if you're having the issue at configure time, not when actually trying to build oneMKL Interface library, and that this issue occurs in find_package(Threads REQUIRED). Is that right? In which case, this isn't an issue with the rocRAND backend. To confirm this, it might be worth using the --debug-output and --trace cmake flags. Its also worth noting that the linking error appears to come from /usr/x86_64-suse-linux/bin/ld, not part of the oneAPI base toolkit.
 Is it installed somewhere that the compiler would be looking for it? On Ubuntu I think it is at /lib/x86_64-linux-gnu/libpthread.so - I don't know about SUSE.
We're aware that the build documentation could do with improvement. There is an issue for it here. I've started rewriting some of the documentation, although it isn't ready for a PR yet.

Hello,
Thank you for your reply. And thank you for trying to improve the documentation. I am trying to compile it on a supercomputer and in general the system libraries are not suitable for hpc, so I have to figure out what modules are needed to be loaded

Hey @csccva, do you need more help with this issue?
We have updated the build documentation if that helps.

Hello,
I thnk it i sok to close it. I will try again to compile it and test it and  we will how it goes.


How to access exports?

I know that you can use the following syntax to export data from an mdx file:
export const meta = {
  title: "Post Title"
}

But I am not sure how to access that data in Gatbsy in order to make use of it. Can I query for it in GraphQL? How can I pass the contents of my file to a component in order to render it?
In the example in the README, when the Gatsby node is created, the absolutely path is passed as the component, but I want to wrap my mdx component in a custom component in order to control how it is rendered. How would I do this?

@chasemccoy I don't have any idea. TBH I don't have much experience with both gatsby and MDX

Hi
I've tried to make it work yesterday and couldn't figure it out.
The thing is, the Gatsby Remark plugin works in a very different way as it transform the markdown file to a HTML string, while MDX does transform your .mdx to a JSX component.
The thing is you should pass the JSX component path to Gatsby, but there's no way to tell Gatsby to extract the metadatas related to this component and inject them as context params. I tried to do this before calling createPage using mdx-js directly in node part, but ended up with a jsx component source as a string.
Also didn't find any way to provide the "components" prop of MDX to customize the md style. Tried using Gatsby layout to provide the components prop but the children() is not the MDXTag component unfortunately. This could probably be solved if MDX did support providing these components with react context instead of prop, will open an issue for that.

Note I didn't find the NextJS example helpful, this is probably not only related to Gatsby integration: https://github.com/mdx-js/mdx/issues/152

I too am trying to wrap my markdown files in a template but it seems mdx will only work when passed directly into CreatePage. Is that correct?

@jennasalau @avigoldman has a working example here: https://github.com/gatsbyjs/gatsby/issues/312#issuecomment-398225446

Since gatsby 2.0 is on the horizon, we're doing work to support it in https://github.com/ChristopherBiscardi/gatsby-mdx which has support for mdx layouts, default layouts for different sources and querying export values via GraphQL. I believe this satisfies all of the original requests in this thread so I would also encourage anyone looking for these features to upgrade to gatsby v2 and the gatsby-mdx plugin.
For example, in the original issue, the query to find the title field in the meta export is something like:
query MDXQuery {
  allMdx {
    edges {
      node {
        exports {
          meta {
            title
          }
        }
      }
    }
  }
}

Also didn't find any way to provide the "components" prop of MDX to customize the md style

You can use the MDXProvider component in a layout to do this.


Missing Git tags

Hi! Thanks for creating this.
The only Git tag I see in this repo is for 1.0.2, however versions 1.0.3 and 1.0.4 have been pushed to PyPI. Could tags be pushed for this and releases going forwards? This will make it easier for people to reproduce and verify that the published PyPI package matches what is in Git.
P.S. I'm planning to package this for Debian as well: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068354

Unfortunately building from master (what should be 1.0.4) using python setup.py sdist gives me a different tarball:
user@dev ~/g/b/p/dist (master) [2]> tar -tf github-webhook-1.0.4.tar.gz
github-webhook-1.0.4/
github-webhook-1.0.4/LICENSE
github-webhook-1.0.4/PKG-INFO
github-webhook-1.0.4/README.md
github-webhook-1.0.4/github_webhook/
github-webhook-1.0.4/github_webhook/__init__.py
github-webhook-1.0.4/github_webhook/webhook.py
github-webhook-1.0.4/github_webhook.egg-info/
github-webhook-1.0.4/github_webhook.egg-info/PKG-INFO
github-webhook-1.0.4/github_webhook.egg-info/SOURCES.txt
github-webhook-1.0.4/github_webhook.egg-info/dependency_links.txt
github-webhook-1.0.4/github_webhook.egg-info/requires.txt
github-webhook-1.0.4/github_webhook.egg-info/top_level.txt
github-webhook-1.0.4/setup.cfg
github-webhook-1.0.4/setup.py
github-webhook-1.0.4/tests/
github-webhook-1.0.4/tests/test_webhook.py

Now here's what I downloaded off of PyPI:
user@dev ~/tmp> wget https://files.pythonhosted.org/packages/1f/53/5f7bd98be1dfc4a1b0e202195b41bb8b6062496bc5e5aedea3e30aa38b07/github-webhook-1.0.4.tar.gz
--2024-04-04 16:27:15--  https://files.pythonhosted.org/packages/1f/53/5f7bd98be1dfc4a1b0e202195b41bb8b6062496bc5e5aedea3e30aa38b07/github-webhook-1.0.4.tar.gz
Resolving files.pythonhosted.org (files.pythonhosted.org)... <IP_ADDRESS>, 2a04:4e42:b::223, 2a04:4e42:200::223, ...
Connecting to files.pythonhosted.org (files.pythonhosted.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4031 (3.9K) [application/x-tar]
Saving to: ‘github-webhook-1.0.4.tar.gz’

github-webhook-1.0. 100%[===================>]   3.94K  --.-KB/s    in 0s

2024-04-04 16:27:15 (112 MB/s) - ‘github-webhook-1.0.4.tar.gz’ saved [4031/4031]

user@dev ~/tmp> tar -tf github-webhook-1.0.4.tar.gz
github-webhook-1.0.4/
github-webhook-1.0.4/PKG-INFO
github-webhook-1.0.4/README.md
github-webhook-1.0.4/github_webhook/
github-webhook-1.0.4/github_webhook/__init__.py
github-webhook-1.0.4/github_webhook/webhook.py
github-webhook-1.0.4/github_webhook.egg-info/
github-webhook-1.0.4/github_webhook.egg-info/PKG-INFO
github-webhook-1.0.4/github_webhook.egg-info/SOURCES.txt
github-webhook-1.0.4/github_webhook.egg-info/dependency_links.txt
github-webhook-1.0.4/github_webhook.egg-info/requires.txt
github-webhook-1.0.4/github_webhook.egg-info/top_level.txt
github-webhook-1.0.4/setup.cfg
github-webhook-1.0.4/setup.py

Note how the PyPI tarball is missing the tests, while my build from master does. I don't think anything nefarious is happening here, but it would be good to get it straightened out.


Deploy storage controller to the rest of the prod regions

In prod, we only have a storage controller deployed in us-east-1.
Deploy it to the rest of the regions and update the notion page.

This is done now. Reflected in the storage controller dashboard: https://neonprod.grafana.net/goto/dNXKjPbSR?orgId=1