Not downloading anything using latest version

Hi there,
rTorrent doesn't download anything using latest version of script (even with reverted ip6 thing) on my raspberry pi; fresh install, only changed the download folder in settings and added speed limit.  It seems they are connected since other completed torrents are "seeding" mode (but not actually seeding, at least getting points for them on the site).

Installing 0.13.6/0.9.6 version works on Ubuntu 18.04

Previously had issues with 0.13.6/0.9.6 on Debian 9 and Ubuntu 18. Will look into this.
For now updated latest version will install  0.13.6/0.9.6 as default on Ubu 16 and Debian 8.

I am on Raspberry Pi 3; should've probably specify that.

Installing 0.13.6/0.9.6 version works on Ubuntu 18.04
sudo apt install rtorrent
rt restart

It works in Debian 9. Thank you very much :D

I just reinstalled Debian 9 in other dedicated and rtinst v1.7.7 (0.13.7/0.9.7)
The issue has been fixed! Everything is working fine now.
Many thanks

Now installs 0.13.8/0.9.8 as default on ubu18+ and deb9+ . This seems less problematic than older versions on these OS's.
For older OS versions it installs 0.13.6/0.9.6 and you can update to later versions using rtupdate


Photo flashes when mousing over blog entry blerb

When mousing over the blog entry blerbs on the right of the landing page, the image on the left hand side flashes. Observed using OSX 10.12.6 and Chrome Version 59.0.3071.115 (Official Build) (64-bit).

It does that because posts should have an image set, that it would switch between. However, not all blog posts have images, so it's reloading the default for each post.


Google Maps/Maps Util: Problems with GMSMarker title & Cluster Renderer

Environment details

Specify the API at the beginning of the title (for example, "Places: ...")
OS type and version: iOS 13
Library version and other environment information Google Maps 3.8.0, Google Maps Utils 3.1.2

Steps to reproduce

Download the binaries via Carthage github "googlemaps/google-maps-ios-utils"       ~> 3.1.2
Create a GMSMarker
Try to set the title. You'll get the error: Cannot assign to property: 'title' is immutable
Remove instances where the title for markers is being set since this can't be done in the late version (apparently?)
Attempt to render a cluster, and the app will crash

Code example
Crashing here in GMUDefaultClusterRenderer, specifically inside the conditional:
        if (item.title && item.snippet) {
          marker.title = item.title;
          marker.snippet = item.snippet;
        }

Stack trace

Weird that title is immutable. This obviously is wrong. The crash might be because the title is nil since I removed all instances where it was being set in my code, or there is something behind the scenes I'm unaware of that's causing a crash when accessing this property.

I was able to avoid the crash by adding a "title" property to my POIItem class that implements GMUClusterItem. UNLESS I do marker.setValue("hi", forKey: "title") which feels dirty.

Confirmed the crash. Will have a patch in a few. Thanks for reporting!

That was quick, thanks! Also will the patch fix the issue preventing me from setting the marker title by doing “marker.title = ...”?

No—the upcoming patch will address the crash but it will not allow you to do that as all of the properties within GMUClusterItem are deliberately defined as readonly. This is much safer and it's a pretty consistent pattern across this library. If you do need to change the title after it has been added into the GMUClusterManager, I recommend removing it and adding it back.

Sorry I wasn’t more explicit in my question. I am actually referring to setting the title in GMSMarker. According to the example in the docs here https://developers.google.com/maps/documentation/ios-sdk/marker I should be able to set the title.
If this is not related to the above issue, please let me know and I can instead submit a new issue on google maps repo.

Ah, yes you should be able to. Can you send a larger snippet so I'm able to understand the context?

@arriolac Yep.
So let's say you are doing some basic set up with a marker.
            let marker = GMSMarker(position: coordinate)
            marker.title = "Home"
            marker.map = self.mapView

This will fail to build as Xcode gives an error Cannot assign to property: 'title' is immutable.
This happens regardless of what constructor is used when instantiating a GMSMarker.

@michael-mckenna I see what you mean now. Looks like the readonly keyword on the GMSMarker+ClusterItem is what's causing that. Will have a fix shortly.

@michael-mckenna can you confirm that 3.1.4 addresses the bug you were seeing?

@arriolac LGTM. Thanks for the swift responses!


sql: allow directions specifications on PK/UNIQUE constraints

Jesse Seldess (jseldess) commented:
PR: https://github.com/cockroachdb/cockroach/pull/13924

We have closed this issue because it is more than 3 years
old. If this issue is still relevant, please add a comment and reopen
the issue. Thank you for your contribution to CockroachDB docs!


feat(core): local signin, signout, and central jwt token storage

stores username and jwt tokens in ConfigDB via a SignIn and SignOut internal core methods
exposes methods for get getting username and tokens to RN
runs all tests together, core + mobile node doing signup + signin to local running central api

Dang, didn't mean to approve, I meant to request one change:
Please update line 176 in textile.go to reflect the new NewNode call signature.
node, err := core.NewNode(dataDir, false, logging.DEBUG)

haha, was more involved than I imagined!

ok, updated that call signature, also exposed a SignOut method which just ditches the local username and tokens

@asutula @andrewxhill some changes to Mobile.framework:

NewNode requires the central api url as a second param ("https://api.textile.io") - needed to do that for testing the whole shabang
signup/in methods only return error, not the response object

SignUpWithEmail(username string, password string, email string, referral string) error
SignIn(username string, password string) error

you can get username via GetUsername, returns (string, error)
you can get the access token via GetAccessToken, returns (string, error)
you can see if we're logged in with IsSignedIn, returns bool
you can sign out with SignOut, returns error

okay @carsonfarmer - fixes the tests. In the future, if tests are failing no need to even start the review, I can see what's failing and will just be working on fixing those issues... will expect the same from you guys!

Ok, so I really do think it'll go better to merge #69 before merging this one, particularly given the changes to Mobile.framework to come as a result...


Is it possible to use a multicam configuration in RealSense Viewer with s6 D415 cameras?

Also, is it possible to use a multicam configuration in RealSense Viewer using one D415 and one D435? Why does not work the Sync option in Viewer? How can I bring together the streams from all cameras in one image in RealSense Viewer?
Hello,
I would like to build a multicam system with 6 D415 cameras, and I would like to join, combine the images from these 6 cameras in one image, to get a larger field of view. I read the white paper about multicam configuration and I saw the example-demo at the and of the paper in ROS (I think). How can I do this with RealSense Viewer in Windows? Is it possible? First, I want to try it with 2 cameras, one D415 and one D435 (I have them at home), then I will build a system with 6 cameras. Is it possible to test this functionality with these 2 cameras? Also, I have one USB3 port, the others are USB2, is this a problem when I want to use a multicam mode?
Thank you in advance.
Best regards.

@TDVL hello,
I reformatted the topic to make it in line with the forum convention by moving the bulk of the questions into the designated description part.
With regards to the questions raised -

Q. is it possible to use a multicam configuration in RealSense Viewer using one D415 and one D435 ?

Yes. Realsense viewer is capable stream multiple Realsense devices simultaneously.
The first device will always be automatically added to the viewer. In order to add additional devices press the "Add Source" button in the upper left and select the devices from the list.

In addition to realsense devices it is also possible to add non-Realsense UVC devices (Webcams) as well as recorded sessions (playback devices).

Q. Why does not work the Sync option in Viewer?

It is not clear what do you exactly by "not working" - is it the UI appearance or the actual frames being out of sync?
Feature-wise the Viewer's syncer is controlled by a toggle button and can be altered at any time. There are use-cases that the viewer will toggle it on/off internally, e.g. switching to 3D view that requires synchronized Depth+Color framesets.

Q. How can I bring together the streams from all cameras in one image in RealSense Viewer?
The viewer redirect each frame to a separate viewport for rendering. Each viewport manages its own OpenGl render texture. There is an additional demo that provides a similar functionality - rs-multicam  - it is also more accessible as it is organized as a tutorial.

Combining (or stitching)  multiple depth sensors into a single coherent scene is an advanced use-case that has already been demonstrated with a dedicated demo that you mention, but it is not in the SDK's portfolio (#3222, #3498)

Q. Also, I have one USB3 port, the others are USB2, is this a problem when I want to use a multicam mode?

Using USB2 instead of USB3 limits the data bandwith, though it can be partially compensated by providing Depth High-Res with low (6,10,15) fps rates.
Even in today's most modern PCs it is hard to find more than two USB3 controllers (don't confuse with ports). An in case you're planning to use more than two devices, then multiplexing the USB3 port with an external self-powered USB hub(s) is highly envisaged.

Hello ev-mp,
Thank you for your help. I have set the two camera mode, here is the screenshot.

But, I need to stitch, put together images from two cameras now for testing, later 6 cameras. Depth and RGB streams are important to me for image processing. I need a solution like on this screenshot. Naturally, I will need the XYZ coordinates too.

Can I do this in the RealSense Viewer? In this demo the cameras were set geometrically appropriate in space to get the images well?
Also, the software sync. is used for synchronize what? RGB and depth streams of the same scene?
The USB is OK, I reduced the resolution and the fps rate.
Thank you in advance.
Kind regards

@TDVL hi,
Librealsense provides the infrastructure required to query data from multiple devices. And in the current SDK's hierarchy, a device is the highest abstraction available.
Arranging the devices geometrically to provide a specific depth coverage (as in the attached demo screenshot), and later stitching them to produce a continuous (panoramic) scene is an advanced feature that requires additional software layer to manage the extrinsic parameters
Syncer-wise - the SDK implementation work best with the frames being timestamped by synchronized clocks, e.g. Depth/Color/IMU streams for D435i model. In the case of multiple depth devices this constrain could be temporally replaced by removing the metadata patch, thus  enforcing Host-generated timestamps for all incoming streams.
Note that the devices are built with a provision for inter-cam Depth acquisition HW sync since v2.13
You may find more info in the multi-cam white paper.
Also see #3504

Hello ev-mp,
Thank you for your help.
Hence, the demo is not available for testing (multi-cam demo)? The GUI of that demo is in ROS (or in something else)? I see the controls, options for viewing, transform, the active cameras, depth preset,the joined RGB and Depth images, etc.
Can I manage everything like on this screenshot (from the white paper) in the Win10 RealSense Viewer, in the GUI? If not, where can I do this, is there a GUI for this? My goal is to get the images with some RealSense software (for example with Viewer, because I am a Win10 user, this is the easiest way for me) from camera, or from multiple cameras and process them in Matlab (this is the best way for signal and image processing) or in other programming language.
I am using SDK2.19.1. I saw there is a new release. Is there anything new in latest release about this?
I think the stitching was done with feature based panorama stitching like in Matlab. Is it?
Thank you in advance.
Best regards

@TDVL hi, the full solution for what you're looking is currently not covered by the SDK's demos.
I'll try to break the referenced white paper prerequisites into blocks so you'd be able to assess the gaps:

Streaming of multiple devices ✔
Displaying depth data from multiple devices ✔
API for Depth&RGB coordinate system transformation (align) ✔
Pointcloud generation and coordinate system transformation ✔
Cables for inter-cam HW sync ❌
Mechanical fixture to position and calibrate the cameras ❌
Stitching multiple depth streams/pointclouds into a single 3D scene  ❌

Hope it  makes it clear now

I've been working on a project involving stitching depth information. According to this paper (https://journals.sagepub.com/doi/pdf/10.1177/1729881417695560) a way to do it would be to align depth and color images, then use a homography solving method on the color images (such as those used for panoramas: like this openCV example) (https://www.pyimagesearch.com/2016/01/11/opencv-panorama-stitching/) to create a larger FOV output.

@FlyingSpringrol Hey, any luck?
I can stitch the RGB image only but can't stitch the depth images came straight from RealSence as .png extension.
if you have a solution in code please share, I am working with python and OpenCV
Looking to hear from you
Thanks

Hi @ TDVL This change request is approved. We will implement this.


Apache breakout to own recipe

I know this is a large change, but I believe these changes are a good move to split out the actual rundeck installation from the other external installs that can be optional as part of a rundeck server install.
Changes:

Split out server.rb into three recipes:

server_dependencies.rb - moved install of java to here, so you have the opportunity to use your own java install cookbook.  It is possible to have more than one install of java on a machine, or you might have a java cookbook that does a lot more than just install java.
server_install.rb -  core install of just rundeck
apache.rb - moved all apache install steps to own recipe. If you don't use apache, it does not get installed

New ['rundeck']['grails_server_url'] variable that in conjunction with ['rundeck']['grails_port'] allows you to run grails on non standard port, if needed
Updated rundeck version to 2.5.3-1.10.GA

I meant to rebase this..


Updated all ASP.NET 4.x Identity topics to include ASP.NET 4.x in tit…

…le metadata

 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.:x: wadepickett sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Updated the ASP.NET 4.x Identity topics to include ASP.NET 4.x in their title.  Per branding discussion with Product Unit and this helps clarify what version these are for which was causing some SEO issues.  Part of april seo effort.


Add vertical and horizontal handle bars

Summary
Could you please add vertical and horizontal handle bar user interface components? These user interface controls are grab-able, adjustable bars that allow users to change the amount of displayed space in a panel.

Justification
These features allow users to quickly, easily, and intuitively resize the amount of information shown in a panel to meet task needs or individual preferences. Vertical and horizontal handle bars are particularly popular in information-dense enterprise applications.
Desired UX and success metrics
The page displays multiple panels. The user wants to see more information in one panel. The user grabs the vertical handle bar and drags it to the left to see more information in the right panel. Or, the user grabs the vertical handle bar and drags it to the right to see more information in the left panel. The same user interface styles apply to horizontal handle bars.
"Must have" functionality
The grab affordances must be obvious and visible, either passively or when the user hovers on the bar.
Specific timeline issues / requests
My enterprise application uses multiple horizontal application. Do you think you could add vertical and horizontal handle bars to a release in the next six months?
Available extra resources
What resources do you have to assist this effort?
I can iterate the design with you and may be able to show it to prospective users.

@IBM/carbon-designers Do you think a "splitter" described above fits well in Carbon design ecosystem? Thanks!

This might be too specific to a domain or application for the core Carbon library and could be better suited as an add-on component. It can be difficult for the Carbon team to support more specific components since we aren't as close to those user's needs as the product team. That makes it difficult for the Carbon team to build, maintain, and offer a component that's equally valuable for all users of Carbon.
One thing to be aware of when exploring the designs is that there is a draggable icon available in 16px, 20px, 24px, and 32px sizes in Carbon's icon elements package.
Here's the reference library
https://carbon-elements.netlify.com/icons/examples/preview/#32%2Fdraggable
And elements repo for icons https://github.com/IBM/carbon-elements/tree/master/packages/icons

Closing as the use case/component doesn't represent Carbon's use case in general (more specific). Thanks @designertyler for your response!


Auto reload on error

Fixes #13

Sorry, I was not aware of that. Should be good now

Still needs the same check as a few lines above. So you can
GameLoadError = function() {
    if (typeof unsafeWindow !== "undefined")
	unsafeWindow.location.reload();
    else
        window.location.reload();
}

This allows use of the script by pasting into console

Ok, so it tries to use unsafeWindow and falls back to window. Based on the browser + script extension one of those will be available.


Create DB Schema + easy deployable dev DB

pg in docker with provision script?

this done in https://github.com/technologiestiftung/giessdenkiez-de-postgres-api/tree/master/test/sql
It does not contain a full clone of the original data. This is another thing to takl


[Persistence][Core] Implement Save Points

Objective
Implement the TODOs and placeholders throughout the persistence module codebase related to save points.
Origin Document
There are various situations that require an ephemeral state to be rolled back:

Failure of block application
Pacemaker skips to the next step
Node crashed mid-round
Etc...

For this reason, there needs to be a smooth & clean mechanism to create save points and have rollbacks spanning across all the modules (consensus, utility, persistence, etc...).
The existing context management and empty interfaces are a starting point but must be implemented.
For example, in persistence/context.go, the following functions exist:
func (p PostgresContext) NewSavePoint(bytes []byte) error {
	log.Println("TODO: NewSavePoint not implemented")
	return nil
}

func (p PostgresContext) RollbackToSavePoint(bytes []byte) error {
	log.Println("TODO: RollbackToSavePoint not fully implemented")
	return p.GetTx().Rollback(context.TODO())
}

In consensus/hotstuff_replica.go, the following needs to be verified:
	txResults, err := m.applyBlock(block)
	if err != nil {
		m.nodeLogError(typesCons.ErrApplyBlock.Error(), err)
		m.paceMaker.InterruptRound()
		return
	}

Goals

Identify all points in the persistence module codebase where save points, rollbacks and ephemeral code blocks need to be implemented
Implement the missing logic to have a save point that can be rolled back to in https://github.com/pokt-network/pocket/issues/435

Deliverable

[ ] A PR with implementation tending to the tests above
[ ] Deterministic unit tests to verify the logic above
[ ] Fuzzed tests with some chaos to stress test this business logic

Non-goals / Non-deliverables

An end-to-end testing/automation framework
Implementation of Save Points in other V1 modules
Implementation of Roll Backs as part of the Save Points

General issue deliverables

[ ] Update the appropriate CHANGELOG
[ ] Update any relevant READMEs (local and/or global)
[ ] Update any relevant global documentation & references

Testing Methodology

All tests: make test_all
LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @jessicadaugherty
Co-creator: @Olshansk

@jessicadaugherty Updated the description. Please review

@jessicadaugherty Is it worth looking into using pgx's builtin subtransaction savepoints and rollbacks? As far as I know, the tx.Begin() command will automatically create a savepoint and then you can call tx.Rollback() at any point before tx.Commit() to revert to the most recent savepoint.
See: pgx rollback implementation
And: pgx Tx docs
This way we could have NewSavepoint(pgx.Tx) (pgx.Tx, error) and use this functionality across the board for subtransaction rollbacks calling RollbackToSavepoint(pgx.Tx) error
I would be interested in tackling this issue - might need to be pointed in the right direction if this is too far from the desired implementation however. I am not super clear on how another form of rollbacks could be implemented as Postgres doesn't support them outside of transactions (I believe). Unless it were to be a DB incremental backup and restore scenario?

Hi @h5law ! I have received a notification since the issue is assigned to me so I'll try to answer your question on @jessicadaugherty's behalf :)
You might be on the right path on the Postgres side of things but I think it's worth clarifying that savepoints and rollbacks have to also consider blockStore, txIndexer and stateTrees:
type persistenceModule struct {
	bus          modules.Bus
	config       *configs.PersistenceConfig
	genesisState *genesis.GenesisState

	blockStore kvstore.KVStore
	txIndexer  indexer.TxIndexer
	stateTrees *stateTrees

	// TECHDEBT: Need to implement context pooling (for writes), timeouts (for read & writes), etc...
	writeContext *PostgresContext // only one write context is allowed at a time
}

Essentially, we need to implement whatever is necessary so that everything we persist can have Savepoints and Rollback functionality. The whole thing has to work in unison across all the datastores.
Any ideas or pointers from your point of view are more than welcome.
Please let me know if this makes sense, happy to answer any further questions you might have.

@deblasis

Any ideas or pointers from your point of view are more than welcome.

My knowledge of SMTs is very very limited but from a little reading
func (s *SMT) Revert(toOldRoot []byte) error {

"When Revert is called, the trees to rollback (between the current tree and toOldRoot) are deleted from the database. This process can be slow so for a quick rollback, manually set the Root to the state you want to revert to and reload the cache."
Resetting the root seems to be a fast implementation.
BlockStore and txIndexer are both using kvstore.KVStore for their internal db, again I will keep looking into it as I am not super familiar with this yet but it seems the savepoint/rollback functionality extends as far as the KVStore and SparseMerkleTree types as well as PostgreSQL.
If this is correct I'll try to find out more on each of these and see what comes up.

To add to what @deblasis said, you're definitely on the write part w.r.t the Postgres piece.
In shared/modules/persistence_module.go, the first few functions of PersistenceWriteContext are:
type PersistenceWriteContext interface {
	// Context Operations
	NewSavePoint([]byte) error
	RollbackToSavePoint([]byte) error
	Release() error

	// Commits the current context (height, hash, transactions, etc...) to disk (i.e. finality).
	Commit(proposerAddr, quorumCert []byte) error

	// ...
}

And the last few lines current implementation of Commit are:
func (p PostgresContext) Commit(proposerAddr, quorumCert []byte) error {
    //...

	// Commit the SQL transaction
	ctx := context.TODO()
	if err := p.getTx().Commit(ctx); err != nil {
		return err
	}
	if err := p.conn.Close(ctx); err != nil {
		log.Println("[TODO][ERROR] Implement connection pooling. Error when closing DB connecting...", err)
	}

	return nil
}

There's still some work to make the postgres part work correctly (if you navigate the code you'll understand what I mean), but most of the piece are setup to enable that. It's "easy" because we can leverage rollbacks in a SQL db, which we use for state storage.
For state commitment (i.e. computing the hash), the hard part is that we have to make the change (i.e. update the key-value stores) after validating the transactions, and verify that the root is what we expect it to be.
In essence, here's what we need to do:
for tx in transactions:
   // Start a postgres transaction
   // Create "ephemeral" version of our key-value store (which are the one's backing our trees)
   if tx is valid:
      pgx.Tx.Apply(stateChange)
      tree.Apply(stateChange) // update key value || delete existing key || insert new key
   else: // exception, error, invalid tx, etc...
      pgx.Tx.rollback()
      tree.Revert() // revert updated keys to old value || re-insert deleted keys || delete new keys

if new_state_hash != proposed_state_hash:
    // same rollback logic as above

The hardest part of what I described above is // revert updated keys to old value || re-insert deleted keys || delete new keys because it either requires one of the following:

looking for functionality in the KV stores that enables this OR
Maintaining some sort of in-memory cache that allows rolling these OR
Having logic that loops through the transactions in the block being reverted and determines the proper logic to revert

I haven't thought through the details here deeply so the above is just where I would start thinking/looking if I were to implement it myself. There are still some open questions and we'll need to properly design this piece.

Likely need to split into multiple issues:

storage in postgres and badger.db - review separately to avoid huge PR
common entrypoint for save points and rollbacks

@deblasis @Olshansk please rescope this ticket based on outcome of review of https://github.com/pokt-network/pocket/issues/493


ONBUILD variant deprecation, remove dead Ruby link

Removes a link to the Ruby ONBUILD Dockerfile variant, which was burniated in https://github.com/docker-library/ruby/commit/b9e495c8e400363e6cc2d4db6d944235b7989584 .  Most ONBUILD variants of base library images are deprecated/removed per https://github.com/docker-library/official-images/issues/2076 .  Maybe the doc on the use of BUILD could have more warnings on its limitations, so a second commit here with a note on the deprecations in base images.

Deploy preview for modest-edison-79d82e ready!
Built with commit 5d1bc32e34c1d6492e2e170210696f66820ba9ae
https://deploy-preview-7204--modest-edison-79d82e.netlify.com

Review requested - the current description and links to ONBUILD are misleading.

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Spawning a new terminal (powershell) results in a blank window with unexpected behavior

Starting today after I updated my Windows 10 from 1803 to 1809, if I spawn/start a new terminal or add a new terminal, I see only a blank window/prompt. Please refer to the following pictures.
imgur 1
imgur 2
imgur 3
imgur 4
Additionally Ctrl + L is also resulting in strange/unexpected behavior. It does clear the screen/terminal but after you start writing again, it retains the previous output. please refer to this image below:
imgur 5

VSCode Version: 1.29.0
OS Version: Windows 10, 1809 (Version 10.0.17763.134)

Steps to Reproduce:

Press Ctrl + '  to open the Terminal.

Does this issue occur when all extensions are disabled?: Yes

Removed and reinstalled the latest VSCode, the issue still persists.

#57803


feat(front): 专有名词「云区域」调整为「管控区域」(closed #1545)

Codecov Report

Merging #1564 (3d9d6c6) into v2.3.2-dev (f5abf2f) will increase coverage by 0.02%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           v2.3.2-dev    #1564      +/-   ##
==============================================
+ Coverage       73.37%   73.40%   +0.02%
==============================================
  Files             387      387
  Lines           26070    26070
==============================================
+ Hits            19130    19136       +6
+ Misses           6940     6934       -6

see 4 files with indirect coverage changes


Releasing Code

Hi @HengyiWang,
Thank for your excellent work!, It's so impressive.
Any plan to release code for us to evaluate you model or provide a simple code for video real-time inference ?
Look forward to your reply!

Hi @Lilyo ,
Thanks for your interest in our work. I am currently in the process of cleaning up the code base and I will try to release the code by the end of next week:)

Hi @HengyiWang ,
Thanks again for the great work, I'm also visualizing the output mesh live and it looks great!

你好@HengyiWang,
再次感谢您的出色工作，我还以实时方式可视化输出网格，它看起来很棒！

你好，如何得到可视化网格，可以提供一下代码参考吗


Simplification for Websites that only use technically necessary cookies

Would be nice to have an option to simplify the output /popup for simple websites without thirdparty and other non-necessary cookies
Same box with text, but only one or two buttons : Akknowledge, (optional) Link to Cookie-Page
Thanks for looking into this
Hendrik

Great idea! I'll have a look into this when I have time. Happy to accept PRs in the meantime.


Ci18 117 - Make redraw on repayment

Description
This PR allows making redraw on repayment, and also allows applying a redraw payment
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

This PR has the wrong base. Please close this and create the right PR @jumba2010


Files aren't appearing in s3 bucket as expected, even though I get success message

Hi,
Everything is running through the code as a success in Lambda and the SFTP side of things is working, however the new files don't appear in S3 bucket.  I've included the bucket name, access key id, secretAccessKey and region, I wondered in there was anything that need to be included in the putBatch function in uploadToS3.js?
I've also noticed that the Put Function isn't returned in the sftp-to-s3, am I missing something?
Thanks

Let me investigate this.

I've taken a look today and the files are appearing, thank you @txssseal

Great news :)
Please feel free to contribute to the package!


Trying to get Unifi cams rtsps to work with webrtc - how?

Hi All
I've gotten my unifi cams integrated to Home Assistant lovelace by using the rtsp stream instead of the rtsps stream.
I would like to use only rtsps, but when I try to configure that, it just says 'loading'.
The Unifi Protect is v4.0.33
I've tried experimenting with gortc to test the streams, but so far no luck with rtsps...

https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#source-rtsp

Thankyou @AlexxIT, the rtspx worked perfectly!


Css namespacing

@ldhertert  this is here to show what I did on the namespacing, this pull request needs pruned down to just that but gives us a chance to talk over what I did.
The Changes.md file in the root of the filesystem of this branch shows the css changes needed for this.

this is no longer needed as a pull request


Document database connection usage

Summary
Documents database connection pool usage in the README.
Solid Queue, by default uses 2 connections more than the what Rails apps are configured with by default. Documenting this can help minimize confusion.

@rosa What do you think about this? I feel it's important enough to include it in the README.

@matteeyah yeah, I think it makes sense to have this in the README, but not like this in its own section and advising to lower the number of threads (because in most cases you'd want to increase the number of connections instead). I'd like to have Solid Queue warn you when you have a too low number of connections, using
https://github.com/basecamp/solid_queue/blob/7e8b0ec53fd8edfd19fa31da6b707b919fc7afab/lib/solid_queue/configuration.rb#L51-L54
So I'll close this one and will try to address the two together, warning and documenting.


Why not use Color struct instead of byte[] in color parameters?

Type of issue
[ ] Bug
[x] Question (e.g. about handling/usage)
[ ] Request for new feature/improvement
Expected Behavior
In the GetGraphic method from the QRCoder.PngByteQRCode class, the darkColorRgba and the lightColorRgba use byte[] to represent RGBA color. I expected to use Color struct. It's much easier.
// QRCoder.PngByteQRCode
public byte[] GetGraphic(int pixelsPerModule, byte[] darkColorRgba, byte[] lightColorRgba, bool drawQuietZones = true)
{
	using (PngBuilder pngBuilder = new PngBuilder())
	{
		int num = (base.QrCodeData.ModuleMatrix.Count - ((!drawQuietZones) ? 8 : 0)) * pixelsPerModule;
		pngBuilder.WriteHeader(num, num, 1, PngBuilder.ColorType.Indexed);
		pngBuilder.WritePalette(darkColorRgba, lightColorRgba);
		pngBuilder.WriteScanlines(DrawScanlines(pixelsPerModule, drawQuietZones));
		pngBuilder.WriteEnd();
		return pngBuilder.GetBytes();
	}
}

Current Behavior
The byte[] is not convenient on the usage.
Possible Solution (optional)
Provide pleomorphism that accept Color struct.
Your Environment

Version used:  1.4.3
Compiled from source or NuGet package?:  NuGet
Payload/Encoded text:  123
Used payload generator:  N/A
Used ECC-level:  Q
Used renderer class:  Default
Environment (.NET 3.5, .NET 4.X, .NETCore, ...):  .NET 7

I decided to pass colors as byte[] to keep the PngByteQRCode free from any Windows dependencies. By adding System.Drawing just for the Color-class we had a dependency that isn't available on all platforms/in all environments. This would add another layer of complexity - in the codebase as also on the documentation side.
You can see in the compatibility matrix, that PngByteQRCode is one of the few renderers that works on all platforms and I really want to keep this feature:
https://github.com/codebude/QRCoder/wiki/Advanced-usage---QR-Code-renderers#2-overview-of-the-different-renderers


[Feature]: Multiple entries for SHOPIFY_FLAG_STORE and SHOPIFY_CLI_THEME_TOKEN

What area(s) will this request affect?
Theme
What type of change do you want to see?
New feature
Overview
I have a CI pipeline that currently works for a staging store to automatically build out a preview theme. Ideally, I would like to specify multiple stores given we have multiple production stores for different regions e.g. US and EU so two stores.
Within a github action we have something along the lines of:
# production-us.yml
name: 'Deploy live (Production - US)'

on:
  workflow_dispatch:

env:
  GH_TOKEN: ${{ github.token }}
  SHOPIFY_FLAG_STORE: ${{ secrets.SHOPIFY_PRODUCTION_STORE_URL }}
  SHOPIFY_CLI_THEME_TOKEN: ${{ secrets.PRODUCTION_SHOP_ACCESS_TOKEN }}
  SHOPIFY_CLI_TTY: 0

What I currently have to do is define the above file again and call it production-eu.yml and this is because I can only point to one store for SHOPIFY_FLAG_STORE and one access token for SHOPIFY_CLI_THEME_TOKEN each time. The downside to my approach is that I have to manually click to run the workflow as it is of type workflow_dispatch which is easily forgotten when you have two or more stores to update each time.
Motivation
Solving for multiple stores to push out preview themes for CI actions in github

Hey @Jay-Plumb, if I'm understanding this correctly you can also different envs for each command in a github action. For example you could have:
steps:
  - name: My first step
    run: echo "This is my secret $MY_SECRET"
    env:
      MY_SECRET: ${{ secrets.MY_SECRET }}
  - name: My second step
    run: echo "This is my secret $MY_SECRET"
    env:
      MY_SECRET: ${{ secrets.MY_OTHER_SECRET }}

@Arkham That's a great idea. I didn't think to re-assign so thanks for calling out. Will give this a try tomorrow morning and will close out the above

@Arkham That's a great idea. I didn't think to re-assign so thanks for calling out. Will give this a try tomorrow morning and will close out the above


input_source_share() crashes

I think it's because __INPUT_VERIFY_PLAYER_INDEX is accidentally placed at the start of the function.
local variable _player_index(101304) not set before reading it.
 at gml_Script_input_source_share (line 11) -     __INPUT_VERIFY_PLAYER_INDEX

Yes, it seems to work fine if the line is removed.

Lovely, thanks.

https://github.com/JujuAdams/Input/commit/cf9c1dfbd7de4a5c1ec455da5af2243457492314


HexDocs links to GitHub are broken

To reproduce:

Visit https://hexdocs.pm/guardian/Guardian.html#encode_and_sign/4.
Click on the </> link, it returns 404.

The generated HexDocs documents point to v1.1.0 branch, which is missing.

@ueberauth/core missing release v1.1.0 on Github.


additional arrow styles?

it's great library. thank you.
can you make additional arrow styles? like a dotted, dashed and so on.
please let me know as you possible.

Hi @returner,
did you try applying a CSS class or style to your link? E.g. <StraightLink style="stroke-dasharray: 8 8;" ... />.
Stefan

ok, it works. thank you.


chore: remove hack for materializing keys

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 50.27%. Comparing base (4487398) to head (cb8b848).

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #2211       +/-   ##
===========================================
- Coverage   82.87%   50.27%   -32.61%
===========================================
  Files         327      327
  Lines       16705    16705
  Branches     1501     1501
===========================================
- Hits        13845     8398     -5447
- Misses       2860     8307     +5447

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


arm64 builds for linux/mac

It would be great to have arm64 builds for linux/mac since arm64 machines are getting popular.

Hi @andyli !
Thanks for writing. I completely agree, arm64 builds are on our bucket list for the near term. We are constantly adding support to more platforms in our build. For example, you can expect an announcement on an official Docker image in the next release!
R

+1

Hey @andyli , @Akshay-Thakare ,
arm builds for linux have been available for a while:

Closing.


Add Large Boat Parts Pack from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of Laythe, to add Large Boat Parts Pack to CKAN.
Please direct questions about this pull request to Laythe.

This wasn't previously indexed.


Handle undefined node._def in edit stack title.

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

When attempting to open a custom typeEditor the ui will error with node._def is undefined, this commit fixes that error.
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[x] I have added suitable unit tests to cover the new/changed functionality

Hmmm, didn't commit with my email so I can't show the accepted CLA, closing this one and fixing the commit.

Coverage remained the same at 76.376% when pulling c1d1589f8d24ecd63807d7920c31fa1238f04554 on teastman:master into 8bb7b2e88b550ea05b2bfd58d9219ee7db44fe5a on node-red:master.


Fix ListBucket in S3 API to return correct values

Examples in action in S3Browser after the commit.

Because S3Browser only supports ListObjectsV1 API. continuationToken changed to Marker. I'll be introducing ListObjectsV2 back soon so that it can support both when list-type=2

test failure:
S3ClientRestApiTest.putBucketUnderNonMountPointDirectory:189 create bucket under non-mount-point directory should fail

test failure:
S3ClientRestApiTest.putBucketUnderNonMountPointDirectory:189 create bucket under non-mount-point directory should fail

Yeah the removal of that restriction was intentional. Let me remove that test.

Yeah the removal of that restriction was intentional. Let me remove that test.

@bradyoo was the previous implementation the v2 listing api, and the new code is the v1 api?

@bradyoo was the previous implementation the v2 listing api, and the new code is the v1 api?

the old one wasn't really a v2 api either. It had v2 parameters but it wasn't actually giving the correct results for those v2 parameters. This is a more correct implementation of v1 api.

the old one wasn't really a v2 api either. It had v2 parameters but it wasn't actually giving the correct results for those v2 parameters. This is a more correct implementation of v1 api.

@bradyoo I see. So is it fair to say that the old implementation was not a correct implementation for v1 nor v2, so this is now a more correct implementation of v1?

@bradyoo I see. So is it fair to say that the old implementation was not a correct implementation for v1 nor v2, so this is now a more correct implementation of v1?

That is correct. I will have to also support/copy some parameter names around to support v2.

That is correct. I will have to also support/copy some parameter names around to support v2.

Feedback addressed

Feedback addressed

@gpang Oops. Now addressed.

@gpang Oops. Now addressed.

alluxio-bot, merge this please

alluxio-bot, merge this please


IGNITE-16280 [Native Persistence 3.0] Implement B+Tree-based storage

https://issues.apache.org/jira/browse/IGNITE-16280

@ibessonov Please make code review.

@ibessonov Please make code review.

@ibessonov Please make code review.

@ibessonov Please make code review, also please see at TableDataIo#putValue

@ibessonov Please make code review.

@ibessonov Please make new code review, visa is not green due to [ERROR] Killed by OOM killer


Failure to list Wifi networks on configuration ui

Using homie-esp:
63fb96d (HEAD -> develop, origin/develop, origin/HEAD) Update updater script addressing quirks (#461)
I connect to the homie AP with the device in configuration mode, I get the proper device information, select next to get to the wifi page and see the attached page, nothing to select to move on or configure network.

I've diagnosed this to an AP within range of me with the following SSID:
"DIRECT-A2-HP DeskJet 3630 series ⸮"
(quotes added)
If I make the following debugging change, wifi scanning works normally:
diff --git a/src/Homie/Boot/BootConfig.cpp b/src/Homie/Boot/BootConfig.cpp
index 4fd4412..60a8f1f 100644
--- a/src/Homie/Boot/BootConfig.cpp
+++ b/src/Homie/Boot/BootConfig.cpp
@@ -206,6 +206,10 @@ void BootConfig::_generateNetworksJson() {
   JsonArray& networks = json.createNestedArray("networks");
   for (int network = 0; network < _ssidCount; network++) {
     JsonObject& jsonNetwork = generatedJsonBuffer.createObject();
+    if (WiFi.SSID(network).startsWith("DIRECT-A2-HP DeskJet 3630 series")) {
+      Interface::get().getLogger() << F("Dropped: \"") << WiFi.SSID(network) << F("\"") << endl;
+      continue;
+    }
     jsonNetwork["ssid"] = WiFi.SSID(network);
     jsonNetwork["rssi"] = WiFi.RSSI(network);
     switch (WiFi.encryptionType(network)) {

Which results in the following output on each scan:
Dropped: "DIRECT-A2-HP DeskJet 3630 series ⸮"
I don't own this rogue AP, so I can't simply disable it or try to fix this SSID, but this clearly represents a bug in homie-esp8266's handling of interesting SSIDs, making it difficult or impossible to configure devices.

Perhaps the issue is not the special characters, but the length of this rogue AP.  This also resolves the issue:
diff --git a/src/Homie/Boot/BootConfig.cpp b/src/Homie/Boot/BootConfig.cpp
index 4fd4412..0ff83ad 100644
--- a/src/Homie/Boot/BootConfig.cpp
+++ b/src/Homie/Boot/BootConfig.cpp
@@ -206,7 +206,7 @@ void BootConfig::_generateNetworksJson() {
   JsonArray& networks = json.createNestedArray("networks");
   for (int network = 0; network < _ssidCount; network++) {
     JsonObject& jsonNetwork = generatedJsonBuffer.createObject();
-    jsonNetwork["ssid"] = WiFi.SSID(network);
+    jsonNetwork["ssid"] = WiFi.SSID(network).substring(0,32);
     jsonNetwork["rssi"] = WiFi.RSSI(network);
     switch (WiFi.encryptionType(network)) {
     case ENC_TYPE_WEP:

Very odd, since the max SSID length should only be 32 char. not sure if this should be handled better with the Arduino core or here. Will look into more.

Similar issue: https://github.com/homieiot/homie-esp8266/issues/351


Add known backlink select example

Adds an example of using a backlink to select an item such as during an update (see the Stackoverflow question inside https://github.com/edgedb/edgedb/issues/6118 )
This one is a bit tricky as selecting via a backlink is probably not the first thing that comes to a user's mind, and we also don't want this example to give the impression that you should prefer using backlinks to filter as opposed to any other method that might come to mind - which is why there is a sentence mentioning that there are other ways to filter. It should just be a neat example of something you can do.

I feel like this is more likely to be tripped over if we move it to the select documentation (docs/edgeql/select.rst). It's tangentially related to paths, but I think it's more directly related to selecting. This could be a new section under filtering alongside "Filtering by ID" and "Nested filters" — maybe "Filtering by known backlink" or something similar. Content is good though.
I do wonder if we should add a note that in practice, you would probably want to achieve this owned property as a computed property of the instrument that checks to see if a backlink exists (I think this would work.), just so readers don't try to replicate this example in their projects. Or maybe there's another example that wouldn't have a tidier alternative you could use in practice… 🤔

I feel like this is more likely to be tripped over if we move it to the select documentation (docs/edgeql/select.rst). It's tangentially related to paths, but I think it's more directly related to selecting. This could be a new section under filtering alongside "Filtering by ID" and "Nested filters" — maybe "Filtering by known backlink" or something similar. Content is good though.
I do wonder if we should add a note that in practice, you would probably want to achieve this owned property as a computed property of the instrument that checks to see if a backlink exists (I think this would work.), just so readers don't try to replicate this example in their projects. Or maybe there's another example that wouldn't have a tidier alternative you could use in practice… 🤔
Update: You know, this change could be as simple as adding some other arbitrary property that you change on the instrument besides owned. Something like color. "I saw Bert perform recently and noticed his ukelele is , so I'm going to go back and update the object with that information."

One tough part about moving to select.rst is that that page has its own schema with the superheroes. Select is also a bit over three times the size of the page on paths. I'll move it over somewhere inside select though if you're feeling adamant about it.
As for the example, I've put it together to follow this answer on Stackoverflow as closely as possible:
update Bar
filter .<bar.id = 'df492862-80aa-11ed-832e-e72d12452736'
set { baz := false };
And I guess in that case too a backlink in the schema would be recommended.
Your color suggestion works I think (and have changed the example to match), since it's just a property you could quickly tack on and doesn't feel too 'linky'.

I think select much more closely matches what a user is trying to do here, and alongside the other "Filtering" sub-sections seems like the more natural home. In my head, this information is about filtering and merely uses a path rather than being about a path and merely using filtering. I'm open to arguments going in the other direction though. We can poll in Slack if you want to see what the others think.
I don't think balancing the length of the two pages better is the right consideration here for deciding where to place it. It seems natural to me that the select page is much longer than path since it's such a fundamental thing people are doing with their database. Paths are fundamental too, but you could get a long way with EdgeDB without reading that page by intuiting what's happening. (You're certainly better off reading it, but it doesn't feel like required reading to the same degree as the select documentation.)

Meant to add we could adapt the query to the schema on the select page by selecting a Movie based on one of its characters.

Meant to add we could adapt the query to the schema on the select page by selecting a Movie based on one of its characters.

Yeah, I was going to say that I have an idea for a nice query that should work for the select page schema. I'll give it a shot and see how it feels.

Meant to add we could adapt the query to the schema on the select page by selecting a Movie based on one of its characters.

Okay, second attempt is now up using the schema inside the select page. Made sure to end it with a note that you don't need to use backlinks for such an operation, just another tool in one's belt that can make a query pretty concise.

Content is 🤌. Just some very minor suggestions.
I think I still feel like this should go under "Filtering" instead of "Backlinks" though since "filter" will be the verb the user wants to do. Same reason we probably wouldn't want to take our "Filtering by ID" sub-section and move it to wherever we talk about IDs.

Tough to say, because it would be nice to have everything filtering-related inside the filter section but conceptualizing and working with backlinks tends to take the most mental effort and would feel odd to make a quick mention of them in the filtering section before finally waiting four more sections to get around to just what this backlink actually was. Especially since it's the backlink section on this page that leads to the larger reference inside paths.rst, and a user wondering just what a backlink is would have to first make their way down the page to find out. To sum up:
Order of operations for a reader with this PR as is:

Read about filtering
Read about backlinks, see quick note about how backlinks work for filtering too, neat. Immediate link to more backlink info

Order of operations for reader if moved up to filtering section:

Read about filtering
See backlink example, may or may not be clear what a backlink is
Hopefully continues reading down to the backlink section where more info and link to paths.rst is

Does that change your mind at all? If not then I'll move it up to filtering.

Order of operations for a reader with this PR as is:

Read about filtering
Read about backlinks, see quick note about how backlinks work for filtering too, neat. Immediate link to more backlink info

Order of operations for reader if moved up to filtering section:

Read about filtering
See backlink example, may or may not be clear what a backlink is
Hopefully continues reading down to the backlink section where more info and link to paths.rst is

Does that change your mind at all? If not then I'll move it up to filtering.

I feel like this assumes a user is reading the docs versus referencing them, which I think will be the exception not the rule. (This could be my bias because I never "read" docs from front to back. I may read a tutorial of a "getting started" guide, but I reference almost everything else.) If they're referencing this, organizing around the verbs become more important than a logical progression. I still vote for organizing this with other "filtering" sections, but I'm open to other arguments against.

I think I'm going to have to agree with this now. I'm a top-to-bottom reader myself 90% of the time but this select page is so weighty that I found my eyes drifting to the slider on the right where the category selector is. So up it goes to the filtering section..


drivers: defined battery driver api's.

Defined API's header file for new battery driver.
These API defined for TI Fuel Gauge based SBS battery. These API are defined as per the current application usage.
Please note that we have defined battery and charger as separate drivers.
Signed-off-by: Ramesh Kotabagi<EMAIL_ADDRESS>

It would be OK to add this as a specific driver for a specific battery management capability, but a generic API needs to be developed taking into account #2542.

please be specific with what you are asking for or summaries the relevant part of #2542.

This looks very interesting. However, I don't fully understand the target of this driver. Looking at the code, it seems to be based on a specific I2C-connected chip and not targeting a generic battery API. Can you please give a bit more background?

This looks very interesting. However, I don't fully understand the target of this driver. Looking at the code, it seems to be based on a specific I2C-connected chip and not targeting a generic battery API. Can you please give a bit more background?

This looks very interesting. However, I don't fully understand the target of this driver. Looking at the code, it seems to be based on a specific I2C-connected chip and not targeting a generic battery API. Can you please give a bit more background?

These battery API's defined for TI Fuel Gauge based SBS battery. These API's are defined as per the current application usage.
Please note that we have defined battery and charger as separate drivers.

#5554 is particularly relevant to drivers for existing subsystem APIs like gpio or sensor, where the specific driver implementation is not being upstreamed.
This is different, because there is no existing subsystem API.  Defining what it might look like is what #2542 is about.
Drivers don't have to be based on a subsystem abstraction.  It seems likely both the drivers that motivate the proposed APIs exist already out of tree; if not, they certainly could be implemented without an abstraction, or with an out-of-tree abstraction.  So if the drivers are expected to remain out of tree I'd suggest just doing that.
If you want drivers for these systems in upstream Zephyr then your fastest path forward is to do them without an abstraction.  Then they could be used as a basis for identifying what a generic API should look like by comparing them with other specific drivers to identify the common capabilities.
It's possible that you could get an API for a charger subsystem accepted if the drivers that implement the API were part of the PR, but I'm not the only one who insists that any new API be validated by the presence of at least two accompanying implementations from different vendors that show the API provides the desired functionality and isn't too tightly bound to the details of a specific driver.
As I noted there is an existing TI Fuel Gauge driver in-tree that is exposed as a sensor.  That also would be a path to follow that's more likely to be successful than creating a new API.
If you do want to create a new API:

It should take into account the requirements discussed in #2542
The work should include a discussion of how the TI BQ27421 could be converted to the API
It should combine the battery and charger APIs or explain why they should be kept separate
It will likely be delayed until additional drivers have been written to validate the API https://github.com/zephyrproject-rtos/zephyr/issues/2542#issuecomment-606706804

but I'm not the only one who insists that any new API be validated by the presence of at least two accompanying implementations from different vendors that show the API provides the desired functionality and isn't too tightly bound to the details of a specific driver.

This is not a requirement for introducing a new API, this is a requirement for making an API stable. We need to start somewhere and we need at least one implementation to get an API into an experimental state.
See https://docs.zephyrproject.org/latest/development_process/api_lifecycle.html#experimental
https://github.com/zephyrproject-rtos/zephyr/issues/2542#issuecomment-606706804 is not a zephyr requirement. A driver can be added with an API and considered experimental, more drivers implementing this API would then move it to a different state after 2 releases.

btw, #2542 is about energy management and hardware independent APIs, this here is about support for peripherals and device drivers that would feed into such framework.

It should take into account the requirements discussed in #2542

Would be great if you could list those here as specific requirements, it is not clear to me which requirements are you referring to.

@rkotabag are you planning to add an implementation of this driver? This is a requirement for any new API:

The API introduction should be accompanied by at least one implementation of said API (in the case of peripheral APIs, this corresponds to one driver)

https://docs.zephyrproject.org/latest/development_process/api_lifecycle.html#experimental

@rkotabag are you planning to add an implementation of this driver? This is a requirement for any new API:

The API introduction should be accompanied by at least one implementation of said API (in the case of peripheral APIs, this corresponds to one driver)

https://docs.zephyrproject.org/latest/development_process/api_lifecycle.html#experimental

Up streaming the driver implementation for defined battery API's is currently dropped after discussing with our internal team, due to the following reasons,

Defined API and driver implementation are specific to particular chip and we are not sure w.r.t NDA and IP regarding same to open source the implementation.
Defined API's does not  meet 100% expectations of #2542
So its decided internally that we will modify the current API for charger and battery driver to meet the requirement #2542

So this pull request will be closed and will be working on to meet the requirement of #2542 .

Up streaming the driver implementation for defined battery API's is currently dropped after discussing with our internal team, due to the following reasons,

Defined API and driver implementation are specific to particular chip and we are not sure w.r.t NDA and IP regarding same to open source the implementation.
2.Defined API's does not meet 100% expectations of #2542

So its decided that we will be working on to meet the requirement of #2542  and close this pull request.
I am closing the this pull request as commented above.
I thank everyone for there valuable inputs and exposure to #2542 requirement.


feat: adding Azure Load Balancer module

Adding the following module and releated tests and examples

loadbalancer.go

NOTES:

includes external Load Balancer with Public IP, which is its own resource
includes internal Load Balancer with Private IP, attached to a subnet in a VNET (separate resource)
Fixes #653

CI Passed: https://github.com/rguthriemsft/terratest/runs/1178701025?check_suite_focus=true

CI Pass: https://github.com/rguthriemsft/terratest/runs/1188923805?check_suite_focus=true

I left feedback and have requested changes.  @davesee @shahedc

CI: https://github.com/rguthriemsft/terratest/runs/1191338779?check_suite_focus=true
Changes for review available @rguthriemsft

https://github.com/rguthriemsft/terratest/runs/1195201008?check_suite_focus=true

https://github.com/rguthriemsft/terratest/runs/1199502907?check_suite_focus=true

Look good to me

CI for latest changes https://github.com/rguthriemsft/terratest/actions/runs/284890992

CI Pass: https://github.com/rguthriemsft/terratest/runs/1299447267?check_suite_focus=true

Look good to me, merged master and kicked off a CI run.

[Microsoft CI Bot] TL;DR; success :thumbsup:
You can check the status of the CI Pipeline logs here ; https://github.com/rguthriemsft/terratest/actions/runs/324911013


Optional guess type

Is your feature request related to a problem or area of OpenRefine? Please describe.
Guessing type is long and sometime don't work fine (see example below).
Describe the solution you'd like
I suggest to add a button to guess the type manually.
Describe alternatives you've considered
An "Manual/automatic guess type" option in Preferences could be added.
See also Saveable reconciliation mappings #75.
Additional context
Reconciliation from NOM_SC column (scientific name) to Wikidata suggest only scholarly article Q13442814.
The appropriate type is taxon (Q16521).

Related:

introduce a dedicated API method to guess types (which could be faster): https://github.com/OpenRefine/OpenRefine/issues/1547
we could also just have a spinner in the area of the reconciliation dialog that shows the suggested types - such that the user could configure the rest of the dialog while this is being fetched.

I would also appreciate the ability to input the URI for the desired type manually. Doing so would also save significant load on the endpoint, I think.
Use case: I teach my metadata students to reconcile in OpenRefine. When I design assignments, I always figure out in advance what I want them to reconcile against!

I think this can likely be closed since https://github.com/OpenRefine/OpenRefine/issues/4877 was implemented, no? A type can be input manually underneath the area where guessed types are displayed.


Hide 'Subtitle & Caption' tab when not supported (shinyjs)

The idea is to hide the 'Subtitle & Caption' tab when these features are not supported by ggplot2 to avoid hassle for users that do not use the latest version of ggplot2 (e.g. CRAN version).
One could check is.null(ggplot2::theme_get()$plot.subtitle) and thus hide the panel.
I tried with using shinyjs::toggle() but did not get it run...
Following the example in the documentation I tried:
ui <- miniPage(
    useShinyjs(),
    ...,
    miniTabPanel(id = 'subcap', 'Subtitle and Caption',
    ...
)

server <- function(input, output, session) {
    oberve({
        toggle(id = 'input$subcap', condition = is.null(ggplot2::theme_get()$plot.subtitle)
    })
    ...
}

Check out the dev branch, it's already done. :-)

Seems like a missed quite a few commits...


Respect system proxy settings for WebSocket

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[ ] I am making a fix / change for the macOS implementation of react-native
[x] I am making a change required for Microsoft usage of react-native

Summary
This brings a solution discussed in this issue into react-native-macos.
Test Plan
Verified via a downstream client.

For merge conflict reduction sake, can we under the changes to the lock files?


when rails an exception with http://localhost:3000/swagger, can not reload again, restart rails server will works

I think this has something to do with rails engines and reloading config/routes.rb. I have the same problem with my mounted Grape API without Swagger.

@TangMonk @whatasunnyday Can you help me understand the problem? Is it "Rails reloading doesn't reload GrapeSwaggerRails configuration?

I also wanted to know what exactly this error is Please explain ......

I've actually fixed the problem for myself. I think it only occurs if you have the wrong auto loading directory. Suppose you've file path looks something like this:: /app/models/api_engine/api.rb
My original config/application.rb looked like this:
    config.paths.add File.join('app', 'api_engine'), glob: File.join('**', '*.rb')
    config.autoload_paths += Dir[Rails.root.join('app', 'api_engine')]

This fixed it:
    config.paths.add File.join('app', 'api_engine'), glob: File.join('**', '*.rb')
    config.autoload_paths += Dir[Rails.root.join('app', 'api_engine', '*')]

Thanks @whatasunnyday this would make sense.
@TangMonk @wonderer007 care to try this in your projects?

@whatasunnyday its not working for me
config.paths.add File.join('app', 'api_engine'), glob: File.join('**', '.rb')
config.autoload_paths += Dir[Rails.root.join('app', 'api_engine', '')]
still same error

@wonderer007 What is the name of the directory that your api lives in? It only makes sense to use api_engine if you have a folder called api_engine in apps.

Seeing as the original poster hasn't responded in quite a while, I'm going to assume a solution was found.  If one was not, ping me here and I'll open this issue again or feel free to just open a new issue.


[Docs]: Disabling hash router breaks the build

Type
Bug report
What do you want to report?
Running npm run build with the hash router disabled (default setting) causes the build to break.
[ERROR] Error: Unable to build website for locale en.
    at tryToBuildLocale (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:54:19)
    at async /Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:65:9
    at async mapAsyncSequential (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/utils/lib/jsUtils.js:20:24)
    at async Command.build (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:63:5) {
  [cause]: Error: Docusaurus found broken links!

  Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
  Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

  It looks like some of the broken links we found appear in many pages of your site.
  Maybe those broken links appear on all pages through your site layout?
  We recommend that you check your theme configuration for such links (particularly, theme navbar and footer).
  Frequent broken links are linking to:
  - /docs/category/getting-started

  Exhaustive list of all broken links found:
  - Broken link on source page path = /404.html:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /category/api-specification:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /category/getting-started:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /category/reference:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /category/using-semaphore:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/about-semaphore:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/changelog:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/experiments:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/faq:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/guided-tour:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/migration/bitbucket:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/migration/circleci:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/migration/github-actions:
     -> linking to ./circle (resolved as: /getting-started/migration/circle)
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/migration/jenkins:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/migration/overview:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/migration/travis:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/tour/continuous-delivery:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/tour/continuous-integration:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/tour/hello-world:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /getting-started/tour/sign-up:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/dashboards-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/dashboards-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/dashboards-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/dashboards-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/dashboards-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-activate:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-deactivate:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-history:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/deployment-targets-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/notifications-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/notifications-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/notifications-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/notifications-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/notifications-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/pipelines-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/pipelines-describe-topology:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/pipelines-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/pipelines-partial-rebuild:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/pipelines-terminate:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/pipelines-validate-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/project-secrets-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/project-secrets-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/project-secrets-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/project-secrets-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/project-secrets-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/projects-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/projects-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/projects-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/projects-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/projects-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/secrets-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/secrets-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/secrets-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/secrets-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/secrets-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agent-types-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agent-types-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agent-types-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agent-types-disable-all:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agent-types-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agent-types-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agents-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/self-hosted-agents-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/semaphore-public-api:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-create:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-delete:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-replace:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-trigger:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/tasks-update:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/workflows-describe:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/workflows-list:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/workflows-reschedule:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/workflows-schedule:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /openapi-spec/workflows-terminate:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/agent-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/api:
     -> linking to /essentials/parameterized-promotions/#setting-the-values-via-the-api
     -> linking to /reference/sem-command-line-tool/#sem-logs
     -> linking to /reference/artifact-retention-policies
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/audit-events:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/conditions-dsl:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/dashboard-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/deployment-target-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/env-vars:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/jobs-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/machine-types:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/notifications-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/openid:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/os-apple:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/os-ubuntu:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/pipeline-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/project-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/resources-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/secret-yaml:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/self-hosted-config:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/semaphore-cli:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /reference/toolbox:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/artifacts:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/connect-bitbucket:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/connect-github:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/connect-github-oauth:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/github-sso:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/insights:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/jobs:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/android:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/c-cpp:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/clojure:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/databases:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/elixir-erlang:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/go:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/java:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/javascript:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/php:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/python:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/ruby:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/rust:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/scala:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/languages/swift:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/monorepo:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/notifications:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/observability:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/okta:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/openid:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/optimization:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/optimization/cache:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/optimization/container-registry:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/optimization/docker:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/org-health:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/org-preflight:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/organizations:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/pipelines:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/projects:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/promotions:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/rbac:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/secrets:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/self-hosted:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/self-hosted-aws:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/self-hosted-configure:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/self-hosted-install:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/tasks:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/tests/flaky-tests:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/tests/test-reports:
     -> linking to /docs/category/getting-started
  - Broken link on source page path = /using-semaphore/workflows:
     -> linking to /docs/category/getting-started

      at throwError (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/logger/lib/index.js:79:11)
      at reportBrokenLinks (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/server/brokenLinks.js:250:47)
      at handleBrokenLinks (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/server/brokenLinks.js:282:5)
      at executeBrokenLinksCheck (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:200:47)
      at /Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:146:66
      at Object.async (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/utils.js:36:47)
      at buildLocale (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:146:30)
      at async tryToBuildLocale (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:47:13)
      at async /Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:65:9
      at async mapAsyncSequential (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/utils/lib/jsUtils.js:20:24)
      at async Command.build (/Users/tom/r/semaphore/docs/node_modules/@docusaurus/core/lib/commands/build.js:63:5)
}
[INFO] Docusaurus version: 3.4.0

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed on #218. The main problem was a broken links in the footer.


Support multiple async_block! returns

Trying to build a function of the form
fn DoSomething() -> impl Future<Item=(), Error=Error> {
  match Some(1) {
    Some(x) => async_block! { Ok(()) }
    None => async_block! { Ok(()) }
  }
}

Fails with an error that looks like:
error[E0308]: match arms have incompatible types
  --> src/main.rs:38:5
   |
38 | /     match Some(1) {
39 | |         Some(x) => { async_block! { Ok(()) } }
40 | |         None => { async_block! { Ok(()) } }
41 | |     }
   | |_____^ expected generator, found a different generator
   |
   = note: expected type `impl futures::__rt::MyFuture<<[generator@src/main.rs:39:22: 39:45 _] as futures::__rt::Generator>::Return>`
              found type `impl futures::__rt::MyFuture<<[generator@src/main.rs:40:19: 40:42 _] as futures::__rt::Generator>::Return>`
note: match arm with an incompatible type
  --> src/main.rs:40:17
   |
40 |         None => { async_block! { Ok(()) } }
   |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

I was using this (when matching against an enum representing the RPCs a server could handle) to pick everything off of self that I needed, and then wrap the heavy lifting in an async_block!... but it appears I can't?  (A similar error occurs if one instead moves the two async_block!s into their own #[async] functions, and call them instead.)

Thanks for the report! This is a result of closures and generator and such in Rust though which have unique types. To do something like this you'll want to return boxed futures or something like Either in the futures crate.


Cannot use WebContents.emit

https://github.com/skpm/sketch-module-web-view/blob/099fe8cb3d3685606c93e0c9009954def992f89e/lib/set-delegates.js#L241
I think this line need to be changed like browserWindow.webContents.emit(...arguments).
When i use postMessage
window.postMessage('nativeLog', 'Called from the webview')

like this, the argument is array(? NS_Array?). So, I think using spread is correct.
Maybe other argument has same problem.

you are right 2.1.4 should fix it


Add ForwardDiff to deps

We currently don't have ForwardDiff in the deps.

And UnPack.jl (for the tests)

Oh, these are just part of the test environment. I'm still having trouble running julia --project] test locally though, due to CUDA/CUDAKernels. We should fix this to work out of the box.


Support default handler for python

From @dturanski on February 22, 2018 14:43
Support a default handler name if no --handler argument specified. Likely,  the name of the function is a good choice, e.g.,
upper.py
def upper(word):
    return word. upper()

_Copied from original issue: projectriff/riff-cli#54_

Fixed via #343


Failed to publish events to analytics gRPC server

Description:
gRPC server implemented using the following message and rpc call fails to receive data.
service AnalyticsService {
  rpc PublishEvent(stream EventList) returns (google.protobuf.Empty) {}
}

message EventList {
  repeated Event events = 1;
}

message Event {
    string nodeId = 1;
    string applicationConsumerKey = 2;
    string applicationName = 3;
    string applicationId = 4;
    string applicationOwner = 5;
    string apiContext = 6;
    string apiName = 7;
    string apiVersion = 8;
    string apiResourcePath = 9;
    string apiResourceTemplate = 10;
    string apiMethod = 11;
    string apiCreator = 12;
    string apiCreatorTenantDomain = 13;
    string apiTier = 14;
    string apiHostname = 15;
    string username = 16;
    string userTenantDomain = 17;
    string userIp = 18;
    string userAgent = 19;
    string requestTimestamp  = 20;
    bool throttledOut = 21;
    int64 responseTime = 22;
    int64 serviceTime  = 23;
    int64 backendTime = 24;
    bool responseCacheHit = 25;
    int64 responseSize = 26;
    string protocol = 27;
    int32 responseCode = 28;
    string destination = 29;
    int64 securityLatency = 30;
    int64 throttlingLatency = 31;
    int64 requestMedLat = 32;
    int64 responseMedLat = 33;
    int64 backendLatency = 34;
    int64 otherLatency = 35;
    string gatewayType = 36;
    string label = 37;
    string subscriber = 38;
    string throttledOutReason = 39;
    string throttledOutTimestamp = 40;
    string errorCode = 41;
    string errorMessage = 42;
    string regionId = 43;
    string apiUUID = 44;
    string customerID = 45;
}

The following error was observed in the gRPC client. (The client was implemented using Java)
io.grpc.StatusRuntimeException: UNKNOWN: HTTP status code 499
invalid content-type: text/plain
headers: Metadata(:status=499,content-type=text/plain,grpc-status=CANCELLED,grpc-message=Failed to dispatch inbound message. null,server=ballerina,date=Thu, 22 Oct 2020 10:55:13 +0530)
DATA-----------------------------
failed to dispatch inbound message. null
        at io.grpc.Status.asRuntimeException(Status.java:533)
        at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478)
        at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:413)
        at io.grpc.internal.ClientCallImpl.access$500(ClientCallImpl.java:66)
        at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:742)
        at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:721)
        at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
        at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Affected Versions:
Ballerina slp3
Related Issues (optional):
A similar issue seem to have been reported and fixed in https://github.com/ballerina-platform/ballerina-lang/issues/20888
Suggested Assignees (optional):
@daneshk

@ruwiniwj does this failure happen again?.

I tested the standardised use case provided by gRPC using Java and Ballerina which is the route guide example[1]. I checked the following cases using Ballerina implementation[2] and Java implementation[3].

Java client against Ballerina service
Ballerina client against Java service

Both the cases work without any issue, hence, closing this issue. Please reopen if you have any further queries.
[1] Route guide use case
[2] Route guide Ballerina implementation
[3] Route guide Java implementation


[5.3/5.4] Default value for explicit bindings proposal

Laravel Version: 5.3 or 5.4
PHP Version: any
Database Driver & Version: any

Description:
I wish to have a change to Explicit bindings in routes.
If I understand it correctly. Implicit bindings hits the following code, which results in a first or firstOrFail, which means if I set a default value. I would expect to hit the method no matter, if the model is found or not.
https://github.com/laravel/framework/blob/f880e093dfbfc80a2ab0797d2056580e47e6888d/src/Illuminate/Routing/Router.php#L805
On route bindings (explicit bindings) it hits somewhere else, where it does not check if the method has a default value. This means it always will throw a 404 exception, if the model is not found.
https://github.com/laravel/framework/blob/f880e093dfbfc80a2ab0797d2056580e47e6888d/src/Illuminate/Routing/Router.php#L949
Steps To Reproduce:
Create a explicit binding with a default value.
RouteServiceProvider.php
public function boot()
{
    parent::boot();

    Route::model('user', App\User::class);
}

routes.php
Route::get('profile/{user}', function (App\User $user = null) {
    //
});

Notice:  = null
I would expect it to hit the route, and not throw a 404 exception (ModelNotFound), because  = null is set.

Thank you, but for suggestions and feature requests please use the https://github.com/laravel/internals repo.

Sorry


Get config defaults from config file

Since commit pouchdb/express-pouchdb#103, app.couchConfig exists and is set by express-pouchdb. Now some command line options match 'couchdb' settings. How about using the config file as defaults for the command line options? This allows a second convenient and persistent way of setting them. Candidates would be:
[cors]
methods = ...
credentials = ...
headers = ...
origins is probably also specifyable in 'corser'?
[httpd]
port = ...
bind_address? (would be new, but nice)
[couchdb]
database_dir = ...

The last bit of this landed: e1611e6ce656f1b85a5dd03d257ea96004811828. Fixed now.


Translations don't get picked up.

The translation files, even if generated, don't work in game. It might be an issue on my end, but when I find out what it is we should show proper error messages because there doesn't seem to be anything wrong with the CSV files.

Would like this to be tested again, because I reworked/improved translations again since this was created.


Ambassador should support generic header matching in mappings

We currently support header matching only for the method specialization. It would be easy to support a more general form, so let's do it.

Done in 0.17.0.


Auto-slide animation too fast on android

Hi @alexrainman ,
first of all, many thanks to you for making this awesome carousel. It was very easy to integrate to my application.
I defined an auto-slide feature on the carousel, and it works fine.
The only problem is that the position-changing animation is too fast on android. It's like lightning-fast and not trackable with human eyes.
Is there any possibility to slow down the animation on android side?

I am back! Releasing new version in the next 2 weeks. This will be supported.


First tests on XN - Unable to rename and some peculiarities

Reaching out here with the same message on the XN forum:
https://www.xigmanas.com/forums/viewtopic.php?p=14297#p14297
I've installed the Extension on a recently-updated version XN 13.3-RELEASE-p4.
Created a first jail and noticed that:
a) starting it from the UI does not populate the ip address and leaving the network interface "auto" at creation, it did not select what I thought would be the auto selection: "cbsd0". My available ones due to my tests with other jail managers are: vmx0, lo0, cbsd0, bridge1, epair1a.
b) modification of the jail settings via the UI is not possible, regardless of the jail being running or stopped. The change is made on the UI, then after starting, it reverts to previous setting.
c) I can see activity at a shell that I have not seen evidence of it happening from the UI when using #cbsd j"command" ie jstop

I was able to rename via "cbsd jrename" command to achieve the change of fqdn . Great.
However that change seems to have caused loss of network connectivity and on the UI the gateway ip has defaulted to "1". Changing it to what it should be (in my case <IP_ADDRESS>) again does not save.
Can you please tell me the location of the file in XN where the setting needs to be changed? The documented method in https://www.bsdstore.ru/en/13.0.x/wf_jconfig_ssi.html for jconfig does not work in XN. Just loads of errors "inc_menu_index: not found) types.


Set default encoding to UTF-8 for json

This PR changes the default encoding for response with the type application/json to be UTF-8 by default, instead of binary.
Implements https://github.com/httprb/http/issues/714.

Rubocop failures are unrelated - I'll fix them separately.

Merged as https://github.com/httprb/http/commit/09848c262992d9b87ae64089a62b8ae1122b6ba2