CORE-15964: Add full HSQLDB support to ledger.

Create OSGi component DatabaseProviderType for selecting either Postgres or HSQLDB versions of DBMS-specific functionality. Currently this includes the following:

Some non-ANSI native SQL operations for both Consensual and UTXO ledger.
Custom queries using JSON formatted column data.

Corda selects Postgres by default. The db-testkit module will select either Postgres or HSQLDB, depending on whether it detects a postgresPort system property value.
Integration tests that were previously disabled for in-memory databases (i.e. HSQLDB) have now been re-enabled.
Note: HSQLDB support is provided for unit and integration testing purposes only. It should not be considered to be suitable for Production use.

Corda chooses the correct database-specific components using OSGi service filtering, which are LDAP-style rules applied to a service's properties.
Database-specific components are assigned a @Reference to a particular DatabaseTypeProvider component:
@Component
class PostgresConsensualQueryProvider @Activate constructor(
    @Reference(target = "(database.type=postgres)")
    databaseTypeProvider: DatabaseTypeProvider
): ConsensualQueryProvider {

and
@Component
class HsqldbConsensualQueryProvider @Activate constructor(
    @Reference(target = "(database.type=hsqldb)")
    databaseTypeProvider: DatabaseTypeProvider
) : ConsensualQueryProvider {

By default, the only DatabaseTypeProvider component available in the system is this one:
@Component(service = [ DatabaseTypeProvider::class ], property = [ "database.type=postgres" ])
class DefaultDatabaseTypeProvider : DatabaseTypeProvider {
    override val databaseType: DatabaseType
        get() = POSTGRES
}

which can only satisfy the @Reference for PostgresConsensualQueryProvider and the other Postgres-specific components. However, db-testkit deactivates this default and activates an alternative which can be either Postgres or HSQLDB, depending on the value of DbUtils.isInMemory. The HSQLDB-specific components cannot be activated without a DatabaseTypeProvider that satisfies their (database.type=hsqldb) filter.
The current assumption is that the choice of database is both global and immutable. It does not need to be hard-coded to Postgres, although it currently is.
It would also be theoretically possible for individual PERSISTENCE sandboxes to be able to select their own database type.

The DatabaseType enum is just a convenience so that you can determine which DatabaseTypeProvider has actually been selected more easily e.g.
init {
    LoggerFactory.getLogger(this::class.java).info("Activated for {}", databaseTypeProvider.databaseType)
}

Just a heads up that its entirely conceivable that in the medium term we will need to support different vnode vault DBs (and indeed other DB types) using different database implementations. The description alludes to this being possible in theory. Just wanted to confirm that the service filtering will work on a per-sandbox basis?

The EntitySandboxServiceImpl could set the VirtualNodeContext.serviceFilter to something other than null, which would restrict both the prototype and platform services included inside the PERSISTENCE sandbox. There's slightly more to it than that, but not much.

Just a heads up that its entirely conceivable that in the medium term we will need to support different vnode vault DBs (and indeed other DB types) using different database implementations. The description alludes to this being possible in theory. Just wanted to confirm that the service filtering will work on a per-sandbox basis?

The EntitySandboxServiceImpl could set the VirtualNodeContext.serviceFilter to something other than null, which would restrict both the prototype and platform services included inside the PERSISTENCE sandbox. E.g. a filter requiring that either the service has database.type=postgres or has no database.type property at all.
There's slightly more to it than that, but not much.

Ok, so if it's at the persistence sandbox level, does that mean that all DBs (crypto, vault, uniqueness) must be the same type with this approach?
If so, I don't think that's a problem for us in the short term, nor should we jump through hoops to resolve that now. Just something we will need to keep in mind.

Given that longer term we want to move away from OSGi for DI, do we really want to tie the DB type selection to OSGi specific features?

Given that longer term we want to move away from OSGi for DI, do we really want to tie the DB type selection to OSGi specific features?

I think this also ties in with my comments earlier about selecting based on (vnode) configuration. I think it should be possible to instead use a factory model which doesn't use OSGi, and uses either the Hibernate dialect (simple, but introduces Hibernate dependency) or the JDBC connection metadata (bit more involved, but still do-able) to select appropriate implementations. We could have different factory implementations:

Corda workers: The "real" factory, currently only handles Postgres DBs, throws exception otherwise
Test driver: Always selects HSQLDB (assuming that's all we support?)
Unit / integration test: Has its own implementation based on the provisioned test DB (currently either HSQLDB or Postgres)

Given that longer term we want to move away from OSGi for DI, do we really want to tie the DB type selection to OSGi specific features?

I think this also ties in with my comments earlier about selecting based on (vnode) configuration. I think it should be possible to instead use a factory model which doesn't use OSGi, and uses either the Hibernate dialect (simple, but introduces Hibernate dependency) or the JDBC connection metadata (bit more involved, but still do-able) to select appropriate implementations. We could have different factory implementations:
* Corda workers: The "real" factory, currently only handles Postgres DBs, throws exception otherwise

* Test driver: Always selects HSQLDB (assuming that's all we support?)

* Unit / integration test: Has its own implementation based on the provisioned test DB (currently either HSQLDB or Postgres)

I agree that that would be a simpler, easier to understand, design. We don't need to use OSGi just because it's available.
I'm hoping that soon we can look at removing OSGi from the workers that don't need a sandbox, and this includes the Crypto worker, which will also need multi-DB support.

Given that longer term we want to move away from OSGi for DI, do we really want to tie the DB type selection to OSGi specific features?

Our sandboxes cannot exist without OSGi.
The ledger cannot exist without sandboxes.
There simply is no Corda without OSGi, and trying to pretend otherwise is a ridiculous waste of everyone's time and effort.

The majority of our workers don't need a Sandbox, hence could work without a Sandbox. The crypto worker is a good example. It needs DB access, but doesn't need a Sandbox or OSGi.

The flow-worker and db-worker both need sandboxes, and also need crypto. We also need crypto inside the sandboxes, which requires that the crypto code understands OSGi too. OSGi services also allow different modules to "use" each other without coupling them strongly together. The sandboxes depend heavily on this kind of functionality when they request all PROTOTYPE services that also advertise UsedByFlow, UsedByVerification and/or UsedByPersistence. Anything that isn't OSGi is invisible to this process and hence cannot be used inside a sandbox - and that includes platform services too. AMQP and Kryo serializers are another good example. Do you think that everything with such a serializer is strongly coupled to either AMQP or Kryo? Do you want it to be?
Quasar is now an OSGi WeakingHook implemented inside an OSGi framework extension bundle (i.e. a fragment of the system bundle). This means that Quasar can now only instrument classes that belong to OSGi bundles.
So when you talk about "moving away from OSGi for DI", I think you're really admitting that you don't really understand how much work the OSGi framework is quietly doing for us.

The majority of our workers don't need a Sandbox, hence could work without a Sandbox. The crypto worker is a good example. It needs DB access, but doesn't need a Sandbox or OSGi.

The flow-worker and db-worker both need sandboxes, and also need crypto. We also need crypto inside the sandboxes, which requires that the crypto code understands OSGi too. OSGi services also allow different modules to "use" each other without coupling them strongly together. The sandboxes depend heavily on this kind of functionality when they request all PROTOTYPE services that also advertise UsedByFlow, UsedByVerification and/or UsedByPersistence. Anything that isn't OSGi is invisible to this process and hence cannot be used inside a sandbox - and that includes platform services too. AMQP and Kryo serializers are another good example. Do you think that everything with such a serializer is strongly coupled to either AMQP or Kryo? Do you want it to be?
Quasar is now an OSGi WeavingHook implemented inside an OSGi framework extension bundle (i.e. a fragment of the system bundle). This means that Quasar can now only instrument classes that belong to OSGi bundles within an OSGi framework.
So when you talk about "moving away from OSGi for DI", I think you're really admitting that you don't really understand how much work the OSGi framework is quietly doing for us.

There is a network boundary between the crypto processor and the flow processor. Nothing on the crypto processor side of that boundary needs OSGi, and OSGi leaking into it is hurting us because it means all its dependencies need to be OSGi bundles and it add a lot of friction to our development process.
It is my opinion that if something isn't needed in the Sandbox, it shouldn't be exposed to OSGi. I agree it's something we need to debate and agree on, and hopefully we'll get to that in the next few months.

Changing to the sort of solution I suggested / Dries is advocating for would however I think be simpler, and would put the argument to bed once and for all - a factory approach will definitely work even in the face of this requirement, since it will simply instantiate the correct type based on the database connection information.

We already have DbConnectionManager.getOrCreateEntityManagerFactory(...) for providing EntityManagerFactory instances. What we don't currently have is any means for services like UtxoRepositoryImpl to know (reliably) which kind of database the EntityManager they've been given corresponds to, e.g. for these APIs:
@Suppress("TooManyFunctions")
interface UtxoRepository {

    /** Retrieves transaction by [id] */
    fun findTransaction(
        entityManager: EntityManager,
        id: String
    ): SignedTransactionContainer?

    /** Retrieves transaction component leafs */
    fun findTransactionComponentLeafs(
        entityManager: EntityManager,
        transactionId: String
    ): Map<Int, List<ByteArray>>

    ...
}

Changing to the sort of solution I suggested / Dries is advocating for would however I think be simpler, and would put the argument to bed once and for all - a factory approach will definitely work even in the face of this requirement, since it will simply instantiate the correct type based on the database connection information.

We already have DbConnectionManager.getOrCreateEntityManagerFactory(...) for providing EntityManagerFactory instances. What we don't currently have is any means for services like UtxoRepositoryImpl to know (reliably) which kind of database the EntityManager they've been given corresponds to, e.g. for these APIs:
@Suppress("TooManyFunctions")
interface UtxoRepository {

    /** Retrieves transaction by [id] */
    fun findTransaction(
        entityManager: EntityManager,
        id: String
    ): SignedTransactionContainer?

    /** Retrieves transaction component leafs */
    fun findTransactionComponentLeafs(
        entityManager: EntityManager,
        transactionId: String
    ): Map<Int, List<ByteArray>>

    ...
}

I'm sure it would be possible to create something, but I'm not going to start solutionising now.

I think this bit is the key - it should be entirely possible to determine the database type given access to the database connection manager, which we could either pass in directly (uniqueness already has direct access) or get at it from the EM / EMF. I've had a look online and this is just one way that might work: https://www.baeldung.com/jdbc-database-metadata#database-level-metadata

I think this bit is the key - it should be entirely possible to determine the database type given access to the database connection manager, which we could either pass in directly (uniqueness already has direct access) or get at it from the EM / EMF. I've had a look online and this is just one way that might work: https://www.baeldung.com/jdbc-database-metadata#database-level-metadata

Yeah, I saw that. That's why I said "(reliably)".

It's probably worth having a look at the Corda 5 topology. Nobody has "each other's" JDBC drivers. There is a cluster, and a cluster will need to provide JDBC drivers on all DB and Crypto workers, for all the DBs that Corda supports.

Have you considered how to upgrade any of the cluster's databases, if that upgrade would also require an updated JDBC driver?

Not yet, that's another thing that will need to be considered and another problem that will need solving. Definitely beyond the scope of this work though, but just another case in point for why we don't need to create ourselves more problems, we have enough to worry about as-is :)

..., and OSGi leaking into it is hurting us because it means all its dependencies need to be OSGi bundles and it add a lot of friction to our development process.

There's a saying about OSGi: It tells you when your baby is ugly, and most people don't take that news well.
Unfortunately, shooting the messenger doesn't mean your baby stops being ugly :no_mouth:.
We should have solved most of the technical issues by now anyway. And I've seen what Corda looks like without a DI framework too: It's called "Corda 4".... :scream:

Not yet, that's another thing that will need to be considered and another problem that will need solving. Definitely beyond the scope of this work though, but just another case in point for why we don't need to create ourselves more problems, we have enough to worry about as-is :)

The OSGi framework is a powerful tool, and neither PERSISTENCE sandboxes nor the ledger can exist without it. In which case, Corda 5 is stuck with it and we might as well use it properly instead.
But regardless, as of right now, Corda uses a single database type that is selected at start-up, and that database can be either Postgres or HSQLDB. All this PR is doing is providing HSQLDB support for those few aspects which are currently Postgres-specific. And yes, I am using OSGi for that because OSGi is capable of doing the brunt of the "heavy lifting" for me in a clean and reliable way.
This should be more than sufficient for our requirements as they currently exist. All this discussion about possible future requirements is really just noise. The crypto-worker is still using an OSGi framework, and it can be a fun and educational exercise for someone else to change that at some unspecified later date.

But regardless, as of right now, Corda uses a single database type that is selected at start-up, and that database can be either Postgres or HSQLDB.

Technically right now, we're still hard coded to Postgres (for a real Corda worker), because we haven't implemented the configuration bit.
In practice, my expectation is the configuration bit will not in fact be a fixed configuration setting, the database type will simply be inferred from the DB connection. It should be perfectly possible to do this reliably - Hibernate manages to select a dialect automatically and reliably, and simply using this is one option.
The fact that we will still only support Postgres in practice is simply a consequence of the fact we won't yet be able to provision different DB types. That seems preferable to introducing an artificial configuration setting that will have to be deprecated later.

LGTM - but I'm not the one to approve ledger stuff

I've done the best I can with the tokens as currently implemented, but I suspect that all I've really done here is highlight this implementation's underlying problems :no_mouth:.

In terms of major changes, I still feel we should do as @driessamyn suggested and not use OSGi for DB selection if we can avoid it.

AFAIK the Dev-Ex team (@yarivus) wants to add the driver to Corda 5.1, so unless production databases other than Postgres are also on the roadmap for Corda 5.1 then I wouldn't recommend adding anything more to this PR. Refactoring the UTXO custom query tokens has already taken a month, and we simply do not have another month to spend re-inventing Corda's DB handling as well.

In terms of major changes, I still feel we should do as @driessamyn suggested and not use OSGi for DB selection if we can avoid it.

AFAIK the Dev-Ex team (@yarivus) wants to add the driver to Corda 5.1, so unless production databases other than Postgres are also on the roadmap for Corda 5.1 then I wouldn't recommend adding anything more to this PR. Refactoring the UTXO custom query tokens has already taken a month, and we simply do not have another month to spend re-inventing Corda's DB handling as well.

They are on the roadmap for 5.2, and we have a view to delivering these part of the changes for 5.1 so we don't have to do it as part of this PR, but it just means that this bit potentially becomes immediately redundant.

Hi @aditisdesai, this is in scope for Corda 5.1, it is required as part of the Flow Testing Driver feature that is coupled with Corda 5.1. FYI, the Flow Testing Driver is currently being developed on feature branch off Corda Runtime OS and it will be merged into Corda 5.1 main branch: https://github.com/corda/corda-runtime-os/tree/feature/flow-testing


Guide: NVMe Flash Drive

This one is done.
https://github.com/packethost/docs/blob/master/guides/07-storage/05-nvme-flash-drives.md


Regression between 3.35.0 and 3.35.1

I woke up this morning to find my website's charts all faint, I am using jsDeliver and it was set to deliver the head revision all the time, rolling back your point release fixes the issue.
There are too many commits (which I do not understand well enough to identify the breaking change, however I suspect it could be this one:
https://github.com/apexcharts/apexcharts.js/commit/4d7131bf8e9773501345e68cc886fa8fef898599

My code
	document.addEventListener("DOMContentLoaded", function(event) {
		var s = document.getElementById('periodGraph');
		var blueLine = "#009EF7",
			blueFill = "#F1FAFF",
			greenLine = "#50CD89",
			greenFill = "#E8FFF3",
			purpleLine = "#7239ea",
			purpleFill = "#c8adff",
			redLine = "#ea3939",
			redFill = "#fc7777",
			greyLine = "#EFF2F5",
			greyFill = "#A1A5B7";

		new ApexCharts(s, {
			series: [
				{
					name: "Purchases",
					data: [9,17,22,13,17,13,20,21,15,7,19,24,8,11,12,8,11,10,4,10,8,3,3,5]
				},
				{
					name: "Shenzhen",
					data: [5,13,13,10,11,9,14,15,12,3,17,24,6,6,5,3,7,5,2,4,4,0,1,1]
				},
				{
					name: "Singapore",
					data: [4,3,4,2,5,4,6,5,2,4,2,0,2,5,4,2,3,3,1,3,2,2,1,2]
				},
				{
					name: "DFW",
					data: [0,1,5,1,1,0,0,1,1,0,0,0,0,0,3,3,1,2,1,2,2,1,1,2]
				},
				{
					name: "Shanghai",
					data: [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0]
				}

			],
			chart: {
				type: "area",
				height: 300,
				toolbar: {
					show: false
				}
			},
			plotOptions: {},
			legend: {
				show: false
			},
			dataLabels: {
				enabled: false
			},
			fill: {
				type: "solid",
				opacity: 0.6
			},
			stroke: {
				curve: "smooth",
				show: true,
				width: 3,
				colors: [blueLine, greenLine, purpleLine, redLine, greyLine]
			},
			xaxis: {
				categories: ['12am', '1am', '2am', '3am', '4am', '5am', '6am', '7am', '8am', '9am', '10am', '11am', '12pm', '1pm', '2pm', '3pm', '4pm', '5pm', '6pm', '7pm', '8pm', '9pm', '10pm', '11pm'],
				axisBorder: {
					show: false
				},
				axisTicks: {
					show: false
				},
				labels: {
					show: false,
					style: {
						colors: greyFill,
						fontSize: "12px"
					}
				},
				crosshairs: {
					position: "front",
					stroke: {
						color: blueLine,
						width: 1,
						dashArray: 3
					}
				},
				tooltip: {
					enabled: true,
					formatter: void 0,
					offsetY: 0,
					style: {
						fontSize: "12px"
					}
				}
			},
			yaxis: {
				labels: {
					style: {
						colors: greyFill,
						fontSize: "12px"
					},
					formatter: function(val, index) {
						return (val || 0).toFixed(0);
					}
				}
			},
			states: {
				normal: {
					filter: {
						type: "none",
						value: 0
					}
				},
				hover: {
					filter: {
						type: "none",
						value: 0
					}
				},
				active: {
					allowMultipleDataPointsSelection: false,
					filter: {
						type: "none",
						value: 0
					}
				}
			},
			tooltip: {
				style: {
					fontSize: "12px"
				}
			},
			colors: [blueFill, greenFill, purpleFill, redFill, greyFill],
			grid: {
				borderColor: greyLine,
				strokeDashArray: 4,
				yaxis: {
					lines: {
						show: true
					}
				}
			},
			markers: {
				colors: [blueFill, greenFill, purpleFill, redFill, greyFill],
				strokeColor: [blueLine, greenLine, purpleLine, redLine, greyLine],
				strokeWidth: 3
			}
		}).render();
	});
...

Thanks for bringing this to my attention, fixed it. A patch version will be released soon.

your welcome, thanks for a speedy fix!


upgrade protoc-jar-maven-plugin to 3.8.0

Current protoc-jar-maven-plugin has a problem when building project after a proxy network. The latest release 3.8.0 version fix this issue.
Reporter: Junjie Chen / @chenjunjiedada
Assignee: Junjie Chen / @chenjunjiedada
PRs and other links:

GitHub Pull Request #659

Note: This issue was originally created as PARQUET-1552. Please see the migration documentation for further details.

Junjie Chen / @chenjunjiedada:
v<IP_ADDRESS> does not fix the problem, v3.8.0 fix it.


Enlocale fix

Some typo fixes due to some strings not describing what elements were doing, accurately. While at it, had the chance to also fix the NotifPreviewBuildUsedSubtitle for better clarity.
On a sidenote, maybe if the user is running a preview version, the logo/header could be different? E.g. have a different logo color and the name () could reflect that as well? Just some food for thought.
Quick Paint sketch I did to illustrate what I mean:
, for the text and the logo could either stay the same or look something like this:

Obviously these are just sketches but you get the idea.

I'm not sure if we can change the logo color to indicate the build status at this moment.
Anyway, as an alternative (and as per your suggestion), I'm adding a "mark" to indicate the preview build status.
Here's the current state of the changes from this commit: https://github.com/neon-nyan/CollapseLauncher/commit/0b57c8b82eae7d88aa9d2861672b6c06c77c7f97

Also, I'm adding two more strings for the recent addition to indicate the status if delta-patch format is detected for Pre-load.
Just in case, you can check if it's grammatically correct.

You can go ahead and merge this now. Most of the fixes are contained inside 084e827a6ea62b8c6b76d6b69f4a801c93c134ab, but I did have to force push prior to that to fix the conflicts I had when you pushed your changes earlier today. Let me know if it works for you!

Alright, thank you.
I will check the commit once I'm going back home


Update to React v16

Description
React 16 is officially released:
https://facebook.github.io/react/blog/2017/09/26/react-v16.0.html
It would be amazing if Boilerplate could use it by default.

Enzyme will have to be upgraded to 3.x.
See: Migration Guide for enzyme v2.x to v3.x

Does anybody where should I put the enzyme configuration within a rollup and a react boilerplate project ?
I have no test entrypoint,should I configure these adapter in all my test files ?

Provided every test works with enzyme v3.0, one way to migrate without touching any existing test file is adding a setup file for jest inpackage.json that tells enzyme to use the correct adapter,
import Enzyme from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';

Enzyme.configure({ adapter: new Adapter() });

The thing is, some tests may be broken after upgrading to v3.0. I'm having issues with components wrapped conditional rendering logic, see this issue . It is safer to delay the upgrade until enzyme team sorts out these bugs.

https://github.com/airbnb/enzyme/blob/master/CHANGELOG.md
“Published Enzyme 3.1.0 last night! Some big React 16 issues should be fixed now!”

Can we close this issue?
React successfully updated

Guys, when this will be released?

@mayacode No release dates. You can either wait or use the dev branch as your base.


Problem to export tikz code with a legend

Hi, Thanks for developing such a great tool! I experienced a bug today, which is easy to fix.
In _legend.py, line 81 and 82, obj._ncol should be obj._ncols. Then the figure with a legend can be exported.

This appears to be a duplicate of #557 and has an unmerged fix in #558.

I encounter the same issue:
File ~/Python/lib/python3.11/site-packages/tikzplotlib/_legend.py:81, in draw_legend(data, obj)
     78 if alignment:
     79     data["current axes"].axis_options.append(f"legend cell align={{{alignment}}}")
---> 81 if obj._ncol != 1:
     82     data["current axes"].axis_options.append(f"legend columns={obj._ncol}")
     84 # Write styles to data

AttributeError: 'Legend' object has no attribute '_ncol'

I've merged the fix in my fork, which you can install using pip install git+https://github.com/st--/tikzplotlib@develop.


Unblock sending audio channel

Some deadlock is still happening, causing the app hanging. I think better reuse non-block sending audio first to check if it's really the issue.
I think the audio quality won't get affected much.

I think it should not affect the quality at all, I've tried some games with a skip audio frames counter in the non-blocking branch and I've been getting zero drops.
And what about blocking image channel?
// nanoarch.go:113
NAEmulator.imageChannel <- outputImg

@sergystepanov oh I didn't realize you reply here :D .
I think this is because I was trying to find where is the issue causing deadlock. I figured it out yesterday and fixed in this PR.
https://github.com/giongto35/cloud-game/pull/144/files
The way I'm doing to find deadlock is by running profile. If you access http://localhost:9000/debug/pprof/goroutine?debug=1 you will see where each goroutine waiting on each channel. :D


stb#325  Fix performance issues for category and sorting

Closes https://github.com/fidals/stroyprombeton/issues/325
https://github.com/fidals/shopelectro/issues/603

merge it. It has small amount of code and business waits it


Browserstack fails on first attempt

The first time I run ./features/run/browserstack-memory I see an error like this
WebDriverError: [browserstack.local] is set to true but local testing through BrowserStack is not connected.
...however the browserstack-local-nodejs package has started a local tunnel (and left it running, which seems broken too!):
> ps -x | grep browserstack
46847 ??         0:00.74 /Users/me/.browserstack/BrowserStackLocal --daemon start --log-file /Users/me/projects/todo-subsecond/local.log --key <redacted> -daemonInstance

The second run passes. So it looks to me like browserstack-local calls it's callback before it's actually ready, or something.

Looking at the code, there seems to be a commented out bit that waits for evidence that the tunnel is actually started


onecommander: Update version to <IP_ADDRESS>

This is my first effort at updating anything greater than a URL or a typo for the Scoop project.
If I did a good job, please thank me.
If I did a bad job, please thank me for my attempt and be kind in your help to show me how I can do better in the future!
Please note that I've marked this as "relate to #14342" instead of completely fixing it, because getting the latest version required a manual update of the Scoop manifest.  The Scoop manifest auto-update mechanism is not working.  I'm not sure if that's an oversight of the upstream developer, if the official checkver URL changed, or if another reason applies.
Relates to #14342

[x] I have read the Contributing Guide.

The bot is correct, that the checkver will not match the latest version, as the checkver URL content is woefully outdated.  What to do?  Remove the checkver URL from the Scoop manifest?  Something else?

/verify


Add: jigsaw source path

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit e6217153621875e40d7e1e7d67bcba62e6608d03
https://deploy-preview-1463--netlify-cms-www.netlify.com

Changed what you have requested @erquhart


Azure cloud tutorials/update

Tested MRTK version 2.5.1
Tested Unity Version 2019.4.16
Updated Azure Spatial Anchors SDK to 2.7.1
Minor documentation changes

@varunsiddaraju : Thanks for your contribution! The author(s) have been notified to review your proposed change. @jessemcculloch

@varunsiddaraju : Thanks for your contribution! The author(s) have been notified to review your proposed change. @jessemcculloch


update to 4-bit

Hi, any plan to update to the new version with support for 4-bit?
Thanks,
Leandro

I just tested this project and it worked with 4-bit: https://github.com/Lzy17/bitsandbytes-rocm
Is there any path to merge these 2 repos into the main bitsandbytes repo?


c(M) Ishiyama21 speedup

Addresses #929. I built an RBF emulator to speed up the c(M) computation by 7 times.
The bottleneck of the computation is the _G_inv method so I performed the following steps:

Ran this method locally with a bunch of different cosmologies (some of them extreme), different masses, and different scale factors to see what is the range of the arguments of _G_inv;
I then widened the [vmin, vmax] boundaries of those ranges by 20% to be on the very-safe side;
Picked 1024 training points in the 2-dimensional parameter space of that method, using Latin Hypercube sampling;
Verified that the training data are well-behaved (span one order of magnitude, no need for rescaling);
Fitted the data using a Radial Basis Function interpolant with a modified kernel that only looks at the 20 nearest neighbors in parameter space.

Data live in CCL/pyccl/data, and the emulator is automatically loaded the first time ConcentrationIshiyama21 is instantiated.
I verified that the emulator reproduces very well the _G_inv behavior, and added an additional benchmark test.
Speed comparison for the same likelihood I mention in the quoted issue:
before:
 --> 8.2 s/iteration
after:
 --> 2.3 s/iteration
(= 3.5x speed increase)
c(M)-specific timing benchmark (without and with emu):

(=7x speed increase).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

28 of 28 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 97.066%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
4433

Relevant Lines:
4567

💛  - Coveralls

Code to reproduce the training (uploading this just so it exists in the repo):
""" Trains the Ishiyama21 `_G_inv` emulator. """
import pyccl as ccl
from pyccl import halos as hal
import numpy as np
from scipy.interpolate import RBFInterpolator
from scipy.stats import qmc
from tqdm import tqdm

# First we sample `_G_inv` to see what the range of `arg` and `n_eff` is.
# LatinHypercube here is an overkill; this might as well have been random sampling.
sampler = qmc.LatinHypercube(d=7)
sample = sampler.random(n=128)

# parameters: Oc   Ob    h  n_s sigma8 M   a
lo_bounds = [0.2, 0.02, 0.5, 0.9, 0.6, 6, 0.01]
hi_bounds = [0.5, 0.08, 0.8, 1.1, 1.1, 16, 1.00]
sample = qmc.scale(sample, lo_bounds, hi_bounds)

# These are all the options the Concentration class accepts.
options = {
    "mass_def": [hal.MassDefVir(), hal.MassDef200c(), hal.MassDef500c()],
    "relaxed": [True, False],
    "Vmax": [True, False]}

# For each combination of options, run 128 times in the 7-dimensional param
# space of Omega_c, Omega_b, h, n_s, sigma8, M, a.
for mass_def in options["mass_def"]:
    for relaxed in options["relaxed"]:
        for Vmax in options["Vmax"]:
            try:
                cm = hal.ConcentrationIshiyama21(
                    mass_def=mass_def, relaxed=relaxed, Vmax=Vmax, emu=False)
            except ValueError:
                # some option combinations don't exist (e.g. 500c, vmax=True)
                continue
            for node in tqdm(sample, desc=f"{mass_def}, {relaxed}, {Vmax}"):
                cosmo = ccl.Cosmology(
                    **dict(zip(["Omega_c", "Omega_b", "h", "n_s", "sigma8"],
                               node[:5])))
                try:
                    _ = cm.get_concentration(cosmo, M=10**node[-2], a=node[-1])
                except ccl.CCLError:
                    # C-level error associated with sigmaM splines out of bounds
                    continue

# I hacked `ConcentrationIshiyama21._G_inv` to save [arg, n_eff, root]
# at every function call. This was saved in `Concentration.saved_data`.
data = np.asarray(hal.Concentration.saved_data)
mins, maxes = np.min(data, axis=0)[:-1], np.max(data, axis=0)[:-1]

# Widen the ranges of the sampling parameters by 40%.
lo_bounds = (1 - 0.2 * np.sign(mins)) * mins
hi_bounds = (1 + 0.2 * np.sign(maxes)) * maxes

# Build a Latin Hypercube for `arg` and `n_eff`.
sampler = qmc.LatinHypercube(d=2)
sample = sampler.random(n=1024)
sample = qmc.scale(sample, lo_bounds, hi_bounds)
func = cm._G_inv
d = func(*sample.T)

# Disregard the nans (when `root_scalar` reaches max tries and exits).
sample = sample[~np.isnan(d)]
d = d[~np.isnan(d)]

# RBF Interpolation with thin-plate kernel truncated to 20 nearest neighbors.
rbf = RBFInterpolator(sample, d, neighbors=20)

# Save, reload.
import pickle
with open("Ishiyama21_Ginv", "wb") as f:
    pickle.dump(rbf, f)
with open("Ishiyama21_Ginv", "rb") as f:
    rbfl = pickle.load(f)


Helen : Asynchronous programming, 3 Weeks

Learning Objectives

[x] 🥚 You understand the JavaScript Event Loop, and can demonstrate this by using setTimeout and setInterval to schedule simple tasks.

[x] 🥚 You can explain why Asynchronous Programming is important for programs that have blocking and non-blocking tasks.

[x] 🥚 You can explain the basics of the Client/Server model and HTTP requests and can fetch data from RESTful APIs.

[x] 🐣 You can break down an asynchronous problem into smaller tasks and solve it using promises. This includes identify which tasks depend on each other and which are independent:

dependent tasks: The return value from one task is required to start the next task, these must be completed in a specific order - .then
independent tasks: These tasks do not use each other's return values, they can be completed at the same time - Promise.allsystem.

[x] 🐣 You can fetch data from an API and render it into the DOM using /api-calls, /handlers and async/await syntax.

[x] 🐣 You can write unit tests for functions that return promises using async/await syntax.

[x] - [ ] I have pushed my progress to my fork of exercises repo

Week 1
I Need Help With:

Nothing for now

What went well?

JavaScript Event Loop
SetTimeout
Set Interval
Clear timeout

What went less well?

still didn't complete the exercises and the assignment yet

Lessons Learned

Blocking and Non-blocking programming languages

Sunday Prep Work

on it!

Week 1
I Need Help With:

Nothing for now but with this long brake I sure will have a lot to learn.

What went well?

What went less well?

I keep forgetting what I learnt but motivated to study more.

Lessons Learned

i need to study and practice more.

Sunday Prep Work

Merry x-mas and new year


INSTALLATION FAILED: rendered manifests contain a resource that already exists

I've been seeing this occasionally for the past few days during cluster setup.  Here's the log:
*** STATUS: setup: neon-system-db
START: sudo bash -c 'mkdir -p /var/local/neonkube/setup'
END [OK]
START: sudo bash -c 'if [ -f "/var/local/neonkube/setup/helm-unzip" ] ; then exit 0; else exit 1; fi'
END [OK]
START: sudo bash -c 'mkdir -p /var/local/neonkube/setup'
END [OK]
START: sudo bash -c 'if [ -f "/var/local/neonkube/setup/helm-install-neon-system-db" ] ; then exit 0; else exit 1; fi'
END [ERROR=1]
*** STATUS: helm install: neon-system-db
----------------------------------------
START-BUNDLE: ./script.sh
*** START TEXT FILE: script.sh

set -euo pipefail

cd /lib/neonkube/helm

helm install neon-system-db --namespace neon-system -f postgres_operator/values.yaml --set priorityClassName=neon-data --set metrics.enabled=True --set-string metrics.interval="1m" --set-string resources.requests.memory="128Mi" --set-string resources.limits.memory="256Mi" --set replicas=1 --set-string podPriorityClassName="neon-data" ./postgres_operator

START=`date +%s`
DEPLOY_END=$((START+15))

set +e

until [ `helm status neon-system-db --namespace neon-system | grep "STATUS: deployed" | wc -l` -eq 1  ];
do
  if [ $((`date +%s`)) -gt $DEPLOY_END ]; then
    helm delete neon-system-db || true
    exit 1
  fi
   sleep 1
done
*** END TEXT FILE
*** START TEXT FILE: __run.sh
#!/bin/sh

chmod 700 "script.sh"
./script.sh
*** END TEXT FILE
*** Uploading: /home/sysadmin/.neon/exec/501a5731-f099-4dbb-aaf5-533687b10712/__bundle.zip
START: sudo bash -c 'if [ -f "/home/sysadmin/.neon/upload/__bundle.zip-c2924764-cca8-4d82-aa4b-bd8f8459cf75" ] ; then rm "/home/sysadmin/.neon/upload/__bundle.zip-c2924764-cca8-4d82-aa4b-bd8f8459cf75" ; fi'
END [OK]
STDERR
    Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: PriorityClass "neon-data" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "neon-system-db"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "neon-system"
END [ERROR=1]
END-BUNDLE
----------------------------------------

So the Helm chart installing neon-system-db is failing because it appears to be trying to create the neon-data priority class resource, which we already created along with the other priority classes very early during cluster setup.
It appears that the Postgres Operator Helm chart is trying to create the neon-data priority class even though I've previously commented out the contents of the postgres-pod-priority-class.yaml template file.  I just tried removing that file and we still see this problem.

FIXED


Check files published to npm

Was looking at<EMAIL_ADDRESS>and I was wondering whether all those files need to be published or not.
It looks like only main/versions/full-versions are necessary? can use package.json files or npmignore  https://docs.npmjs.com/files/package.json#files

Didn't know that existed. Yeah I think the following files can go in a .npmignore:

automated-update.js
build.js

This does mean people won't be able to use the npm module to build it themselves, but I suppose that's fine as the git repository takes care of that. Is that a fair estimation @hzoo?

Actually, I just need to add
  "files": [
    "versions.js",
    "full-versions.js"
  ],

to my package.json, since index.js, being main, is already included. Everything else will be ignored.

There we go. README.md, CHANGELOG.md will still be included but I think the other files wont, whenever the next version is released.

Cool sounds good! can watch https://unpkg.com/electron-to-chromium in the next release
can also do https://docs.npmjs.com/cli/pack to test locally I believe

npm pack does the trick, looks great. Next automated release will have the smaller footprint!


Missing abseil find_dependency

Both config file of google_cloud_cpp_common and google_cloud_grpc_utils are missing a dependency to abseil.
These libraries link to abseil libraries but are lacking the required find_dependency(absl) in their config file in order to have self-contained cmake package.
Incomplete files:

https://github.com/googleapis/google-cloud-cpp/blob/master/google/cloud/config.cmake.in
https://github.com/googleapis/google-cloud-cpp/blob/master/google/cloud/grpc_utils/config.cmake.in

Fixing the first one will also fix the second one as the latter depends and use find_dependency on the former. But both should be fixed in case this dependency is remove one day.

Thanks for the bug report. I am on it.


amule: use gtk3

Motivation for this change
Drop gtk2 and use gtk3 instead, bumping wxGTK to 3.0. With this, aMule gets a nicer UI and native wayland support.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 152509 run on x86_64-linux 1

1 package marked as broken and skipped:

amuleDaemon

2 packages built:

amule
amuleGui


Add openssh-client to final container

Terraform modules can be cloned via HTTP, but some use cases (e.g. cloning from an internal Gitlab module) benefit from cloning over SSH.

Hello @Jberlinsky and thanks for opening this PR 🙏
It's an acceptable use-case indeed and only add about 4MB to the final container image, let's add this feature !


Add grouped binary convolution support (1/3): the converter.

What do these changes do?
This is first of a group of PRs to add support for grouped binary convolutions. I've split the work into three PRs to make review easier.
First, this PR adds support to the converter, by adding an attribute groups to the op definition. The correct value for groups is infered by dividing the input channels by the channels_in dimension of the filter. An error is raised if the size of each group (the input channels divided by groups) is not a multiple of 32 -- I have chosen to add this constraint because it significantly simplifies the implementation in the kernels.
How Has This Been Tested?
MLIR file-check tests have been added to check that the attribute is correctly set, and that the error is raised if the group-size is not a multiple of 32.
Benchmark Results
N/A.
Related issue number
#550, #551.

Upon reflection and discussions with @Tombana, there's actually technically no need to have a groups argument, but only because of the constraint that the input-depth-per-group (if the number of groups is greater than one) is a multiple of 32. If we know we'll never see a flatbuffer with a grouped convolution that has a non-multiple-of-32 group size, then we can infer the number of groups from the (bitpacked) filter channels in dimension and (bitpacked) input channels in dimension.
I'm not sure what the right thing to do here is. Conciseness is nice, but I worry that relying on being able to infer the number of groups by relying on that constraint being satisfied might lead to subtle bugs in the future.

Even if we can infer it in theory, I think it's good to have it as a separate parameter, even if only as an extra correctness checksum.

I'm not sure what the right thing to do here is. Conciseness is nice, but I worry that relying on being able to infer the number of groups by relying on that constraint being satisfied might lead to subtle bugs in the future.

I'd actually prefer not to have a dedicated group attribute in the op. TensorFlow does the same for their Conv2DOp (although in their case I probably would've prefered a dedicated groups argument for the user facing code for better validation).
I think we can do all the necessary validation in Prepare even without a group argument, since we already have a channels_in argument and the shapes of the bitpacked input and bitpacked filters, or am I missing something a case that we can't catch that could lead to subtle bugs?
In both cases we should always make sure that the number of filters per group is divisible by 32 in the converter anyway.

I think I'm onboard with that.
In case somebody tries to convert a grouped Larq bconv with non-multiple-of-32 group size, do you think we should throw a converter error (as this PR currently does) or fall back to an emulated bsign + float conv?

In case somebody tries to convert a grouped Larq bconv with non-multiple-of-32 group size, do you think we should throw a converter error (as this PR currently does) or fall back to an emulated bsign + float conv?

I think it's fair to throw an error for now since TFLite doesn't support group convolutions anyway so it would fail during runtime anyway.

@lgeiger I've updated the PR so that it only performs the check, rather than adding the groups attribute.

Do you think it would make sense to move this check into an op verifier for the bconv op as mentioned in #406 instead? This way the check would be op specific instead of limited to this transformation. Although I am not sure if we still have all of the information there since the bconv op will already have bitpacked inputs and migth either have float or binary filters.

I really like this idea in theory, but you're right that it won't be possible once the filters have been bitpacked. E.g. the number of input channels could be 64, and the bitpacked channels in dimension could be 1, and we don't know if that's because it's 32 input channels to the filter (which is valid) or only 1 that's been padded by bitpacking (1 input channel as in a depthwise conv, which would not be valid).

I really like this idea in theory, but you're right that it won't be possible once the filters have been bitpacked.

That's true. In theory I think it woud still work since the filters will be bitpacked in a later pass, but this means that the verifier would be tied to this transformation anyway. Let's keep it like this for now.


May I change the channel number of the pre-trained model for fine-tune?

Thanks for all the sharing!
I have a problem during fine-tune. Does anyone know that can I load the pre-trained model weight to a new model architecture whose input channel has been changed?
For example, I want to test the 2D resNet on 3D data, the previous input shape was (2292293). Now I want to change the input size to (646464), can I load the model weight correctly? If not, does anyone knows how to achieve that aim?
Thanks for the reply!

Hi, you can use model.get_config() to build you own model. I remember there is a similar issue.


PendingStateManager only reads new format

Description
The PendingStateManager will now only read the new pending message format.
This is the final stage in the multi-step process of changing the format of pending local messages read and written by the PendingStateManager.
See https://github.com/microsoft/FluidFramework/pull/16136
AB#4763

i'll merge this once https://github.com/microsoft/FluidFramework/pull/17087 is merged in next


Fix welcome to jekyll post

This change is

BTW, it's okay

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

a discussion (no related file):
Oh, wait wait wait

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, mvlabat (Vladyslav Batyrenko) wrote…
> Oh, wait wait wait

BTW, what?

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, Doimhneacht (Hanna Rosul) wrote…
> BTW, what?

nothing its okei

Comments from Reviewable


[Feature request]: Install with pipx

What do you need?
The very nature of pipx is designed to handle some of the less friendly parts of the installer, like aliases with the full poetry virtual environment in the path. This would also support installing the helpers as first-class citizens/binaries/callables. There would need to be a few dependencies added for the helpers via poetry shell and the helpers directory would need to be installed via the pyproject.toml, but I think it would give a really clean result.
I can work on this feature, but wanted buy-in before formalizing the work and submitting a PR.
Caveat: no access to Windows for testing, but have worked this out for macOS/Linux.
Example:
$ which fabric
fabric not found

$ cd fabric && pipx install .
  installed package fabric 0.2.0, installed using Python 3.12.2
  These apps are now globally available
    - fabric
    - fabric-api
    - fabric-webui
    - save
    - ts
    - yt
done! ✨ 🌟 ✨

$ which fabric
/Users/swalsh/.local/bin/fabric

$ yt https://youtu.be/K9mhIUc_hRk | fabric -p extract_wisdom | save fabric-context -t context -t markdown
## SUMMARY

The content features ... snipped for brevity

$ pipx uninstall fabric
uninstalled fabric! ✨ 🌟 ✨

$ fabric -h
zsh: command not found: fabric

Hey, thanks for the suggestion!
Your pipx trick worked for me over here on Windows 10 as well!
Actually I had fabric working over on my WSL installation & just ended up using the same fabric.
Everything went smoothly possibly partially because I already pipx installed.
Anyway, here are the general steps I took, (post-git clone):

In a VS Code powershell terminal, cd fabric
I think I did run pipx install . once before getting into the shell but was getting pyperclip errors so I did a poetry shell.
From the poetry shell, pipx install . and everything went smoothly there.
fabric --setup (etc.)
yt https://youtu.be/K9mhIUc_hRk | fabric -p extract_wisdom which ran successfully
BONUS: Windows Ollama also seemed to be working with it (though openhermes wasn't great at extracting the wisdom)..

Now I'm assuming everytime I want to run fabric, I'll need to start poetry shell from its dir.
(Maybe not though, I'm new to poetry.)

@invisiblethreat Looks like this has been released if you want to test.  I had some issues getting it to work, but I'll caulk that up to removing the older version and/or installing pipx and getting it working properly. I'm curious how it goes for you!

Does this mean we no longer need to use $> poetry shell?

I didn't need to use that, but I can't say my system is a clean state as far as globally installed python modules go.

Pipx added!


Would you consider publishing to NuGet?

What a lovely project you have here! Really brings back memories. I was considering using this to teach my nieces some basic coding. Was wondering if you could publish to NuGet to make it easier for them to play with the lib (they are 10,9,7 y.o. so we're more in "click here" territory rather than referencing DLLs :) )
I am happy to provide guidance if need be. Cheers!

This. By the way, you can reference them via git submodules and reference the csproj from your project, but nuget is still more convenient.

Yeah, considering what it is, the ease of use is imho high priority. But I am afraid this is not maintained much anymore. Pitty.

Yeah... @ollelogdahl, what do you think? If you need help with something, ask. Just don't leave such a great project! :)


Default sorting does not apply to page result

PHP Version

Shopware Version
6.4*
Affected area / extension
Platform(Default)
Expected behaviour
Our proposal for this issue:
By setting the default sorting in Shopware settings, both category page and search results page are affected and have the same type of sorting or,
Separating default sorting feature – one for category page and the other for search results page.
Actual behaviour
Products are sorted by ascending price on category page, but on search results page, the chosen default sorting is not applied.
How to reproduce
Steps to reproduce:

Go to Shopware Settings→ Products→ Default Sorting
Change to any other option from the preselected one (e.g., Price Ascending)
Go to the Storefront and submit search
On the search results page, compare the selected sorting with the chosen one in Shopware settings
Next, go to any category with products
On the category page, compare the selected sorting with the chosen one in Shopware settings

Expected result:
Products are sorted by ascending price on both search results and category page.
Actual result:
Products are sorted by ascending price on category page, but on search results page, the chosen default sorting is not applied.
As I mentioned, there seems to be a different logic for applying sorting on search results page and category page.
Note:
Plugins we are using:
Nosto: https://store.shopware.com/en/nosto31536044090f/nosto-personalization-for-shopware-6.html
Findologic: https://store.shopware.com/de/fin6494960032131f/findologic-onsite-suche-product-discovery-platform.html

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38120
[created from NEXT-38120, comment 491875]

[public]Thank you for your report. The behaviour you are describing, is intentional. The default sorting option does not apply to the search results. The way how the search results are listed on the search page depends on search score they get based on the settings, that have been defined under Settings -> Search. There is currently no way in altering the sorting of search results other than that. Therefore, we consider your request not as a bug report but as a feature request and would ask you to add your idea to our idea portal. Thank you in advance!
https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas
[created from NEXT-38120, comment 491919]

https://feedback.shopware.com/forums/942607/suggestions/48792095


Open and check updates in all Social media platform at once

Added a script which allows the users to open all the social media and email accounts in google chrome at once making it quicker to check status and have a glance at the updates.
I have checked the following requirements before making this PR.

[x] The script is marked as executable (chmod +x).
[x] I have added/updated the README entry for the script (if applicable).
[x] I have mentioned any outstanding dependencies and OS requirements for the script in the README.
#19

These sites might not be the same for other people. Therefore, I am closing it since it is too specific. Thanks for the PR, @i-shubhamprakash.


Recipes for not-just-offline use cases

Please file one issue per recipe

Now there are some non related recipes with offline cases such as #23, #22, #17, #18 or #19


Suggestion: Menu Entry Swapping option for herbs and fruit

While farming players will want to use herbs and fruit on the Tool Leprechaun to swap them for notes. However, currently 'clean' and in other cases 'eat' will be the left-click option instead of 'use'. Adding this option to the Menu Entry Swapper Configuration could help improve the QoL for this.

Utilise shift click menu swapping.


Added State-Management in Flutter

Hey @GoelVaibhav009 !
Congrats on submitting your pull request.
You PR has been merged and the changes will be reflected on the website in a few minutes,.
Do leave a star, if you liked the repo ;)
Happy hacking ! 🎊

Hey @ishandeveloper !
Excellent Repo bro!!


Can't see Add container button on host page in dark view

Verison - Master 3/2
Steps to Reproduce:

Change theme to dark
Add a new host

Results: The Add container button in the Standalone Containers section is barely visible

Expected:  Should be able to clearly see it

resolved in https://github.com/rancher/ui/pull/496

Version - master UI 3/3
Verified fixed


Add a tool to run individual clspv passes.

This fixes #263.  It adds a wrapper around LLVM's opt that allows
running any of the clspv passes on an LLVM IR module.
In this initial implementation, the developer must:
1- Generate IR using the -print-before= or -print-after= options to
clspv.
2- Run clspv-opt on the generated LLVM IR file.
This required some re-factoring of clspv_core:
1- All the passes are now in a separate shared library (clspv_passes).
This is required by opt.
2- The core library continues to be static.

Note.  This is still WIP.  I need to add some tests.  Additionally, I would like to add the capability of starting from a .cl file, which means running some of clspv::Compile.  But this is minimally functional now.

Note. This is still WIP. I need to add some tests. Additionally, I would like to add the capability of starting from a .cl file, which means running some of clspv::Compile. But this is minimally functional now.

Hm, actually now that I think more about this; perhaps it's best if "starting from a .cl file" was always done from clspv itself.  This tool will always consume and emit LLVM IR.  At most, I'd give it the option to choose clspv_passes and opt from different paths, instead of the hardwired values it now has.
Thoughts?

Hm, actually now that I think more about this; perhaps it's best if "starting from a .cl file" was always done from clspv itself.

Yes. This tool is intended for debugging and testing. If anything, we could add an option to dump the IR from clspv before any optimizations take place (and terminate?).

Hm, actually now that I think more about this; perhaps it's best if "starting from a .cl file" was always done from clspv itself.

Yes. This tool is intended for debugging and testing. If anything, we could add an option to dump the IR from clspv before any optimizations take place (and terminate?).

Yeah, I'm thinking of a --emit-ir to emit the very first generated IR.  And --emit-ir-after=, --emit-ir-before= for fine-tuned control.  Would that cover all the cases you are thinking of?

Yes, I'm also ok with --emit-ir-after and -emit-ir-before coming in a different commit. I'm ok doing some legwork in the interim to get the IR I'm interested in.

Yes, I'm also ok with --emit-ir-after and -emit-ir-before coming in a different commit. I'm ok doing some legwork in the interim to get the IR I'm interested in.

Yes.  I will do this work in a different commit.  I've added support for command-line arguments to clsvp-opt.  PTAL.

Added some tests and addressed review feedback.  PTAL.

I've consulted LLVM developers and I've learned that the LLVM libraries are not really setup for being used this way on Windows.  It boils down to: "LLVM would need explicit export annotations to make loadable modules work well."
There is no support for that, so it's not something we will be able to support easily.  On Mac, I may be able to use the -undefined dynamic_lookup flag to the linker, but I am not sure if that's enough.
My plan is, then, to: (1) Do not build clsvp-opt on Windows (and possibly Mac), (2) only support it on Linux.
I also need to wait for #305 to land so I can re-test with ToT LLVM.

@alan-baker, @dneto0  the current version offers support for MacOS and Linux.  Support for Windows requires implementing opt inside of clsvp-opt.  I will extend clsvp-opt to support Windows in a separate PR (#307).
PTAL.

Ready for another round of reviews.  PTAL.


White background color not working

Hello, I am using the swift version.  I am setting the background color
onboardingVC.view.backgroundColor = UIColor.whiteColor()
however it shows grey instead of white. All other color works except for the white. thoughts?

solved.

@rustanacexd What was the solution? I am having the same issue.

@andrewhavens I had the same issue and solved it. If you are still having the issue, hope this helps.
To set the background color properly, need to turn off background mask BEFORE set the background color.
onboardingVC.shouldMaskBackground = false
onboardingVC.view.backgroundColor = UIColor.whiteColor()


Parameter description of null raises a validation error in Swagger-UI

If you don't provide a desc: field for a parameter, the generated swagger spec has null as the value for description.  This raises a validation error in Swagger-UI
ex:
{
"in": "query",
"name": "force_refresh",
"description": null,
"type": "string",
"required": false
},

Produces the following validation error
schemaValidationMessages": [
{
"level": "error",
"domain": "validation",
"keyword": "oneOf",
"message": "instance failed to match exactly one schema (matched 0 out of 2)",
"schema": {
"loadingURI": "http://swagger.io/v2/schema.json#",
"pointer": "/definitions/parametersList/items"
},
"instance": {
"pointer": "/paths/test/get/parameters/3"
}
},

Recommendation
Based on http://swagger.io/specification/#parameterObject the description is optional and should be omitted when nil

@wleeper have a look on https://github.com/ruby-grape/grape-swagger/pull/399 and give it a try


package.json - dependencies

It really requires dependencies:

chai
mocha
sinon

Would not it be better as devDependencies?

The inclusion of mocha as a dependency rather than devDependency is causing a vulnerability alert on install - I can't believe these are needed at runtime. Happy to provide a PR to fix if you like?

Yeah that would be great, thanks!
On Tue, Oct 23, 2018, 09:50 Matt Keeble<EMAIL_ADDRESS>wrote:

The inclusion of mocha as a dependency rather than devDependency is
causing a vulnerability alert on install - I can't believe these are needed
at runtime. Happy to provide a PR to fix if you like?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/js-data/js-data-adapter/issues/12#issuecomment-432300767,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFsmS5ncO-5DkdhDttl1lYziVADthYDzks5unzqogaJpZM4PuHdj
.

I have opened a PR for this:
https://github.com/js-data/js-data-adapter/pull/14
can someone please approve & merge it any time soon?

Not only will this solve the errors being reported by npm audit, but it should reduce the size of deployed apps a little too - please someone review and merge this soon 😃

@einat-bar It was merged a few hours ago.

Waiting for npmjs publish access on this package and will publish v1.0.1 and update this thread. In the meantime if there's any urgency you can reference the git repo url in your package.json file.

@crobinson42 Thanks!
The security warnings are actually coming from js-data-http which is using js-data-adapter,
since js-data-adapter is using sinon in dependencies.

@crobinson42 I see now that in  js-data-http, you moved js-data-adapter to devDep, is there a reason for that?

@crobinson42 @jmdobry Is it possible to publish soon?

v1.0.1 published


Tests: retry task test not working with prod settings

This is due to the fact that the dev and prod settings are not the same for the retry mechanism.

We don't plan to work on this in the coming weeks.


When using store code in URL's it doesn't mention it properly

This URL gives a 404:
http://local.shopname.com/mymodule/index/index
This module show as if everything is working fine, but the URL should be:
http://local.shopname.com/storename/mymodule/index/index

Confirmed known issue -- guess who doesn't work with store codes in URL much  :)
Open to pull requests to fix -- otherwise I'll add it to the backlog.
Thanks for the report!


Complete root ca cert rotation

Please provide a description of this PR:
Please read the whole test to get the full procedure for root cert rotate.
Following https://github.com/istio/istio/pull/47063, without any need to restart istiod/workload.

cc @zirain

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-multicluster

unit-tests-arm64_istio
e14a1ca5ace13918893405ed5b9993d095079a9b
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-multicluster

unit-tests-arm64_istio
e14a1ca5ace13918893405ed5b9993d095079a9b
link
true
/test unit-tests-arm64

unit-tests_istio
e14a1ca5ace13918893405ed5b9993d095079a9b
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
2a6c9476b55a78e9d55faf1499555baff7bc2788
link
true
/test integ-security-multicluster

unit-tests-arm64_istio
e14a1ca5ace13918893405ed5b9993d095079a9b
link
true
/test unit-tests-arm64

unit-tests_istio
e14a1ca5ace13918893405ed5b9993d095079a9b
link
true
/test unit-tests

integ-security-istiodremote_istio
e14a1ca5ace13918893405ed5b9993d095079a9b
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test lint

gencheck_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test lint

gencheck_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test gencheck

analyze-tests_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test analyze-tests

integ-security-istiodremote_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test lint

gencheck_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test gencheck

analyze-tests_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test analyze-tests

integ-security-istiodremote_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test lint

gencheck_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test gencheck

analyze-tests_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test analyze-tests

integ-security-istiodremote_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-multicluster

integ-security_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

analyze-tests_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test analyze-tests

integ-security-istiodremote_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security-multicluster

integ-security_istio
864a8605dcbb1aaa48f8cba387405217643c4855
link
true
/test integ-security

lint_istio
a3cdc82e733710cfb15ef3dc0f0a77bf6fc4095a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

ping @howardjohn

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
3cdf7beb27b5d9e8d2e0149a43907e8fe27ff89b
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
3cdf7beb27b5d9e8d2e0149a43907e8fe27ff89b
link
true
/test lint

integ-ambient_istio
3cdf7beb27b5d9e8d2e0149a43907e8fe27ff89b
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7050b9e763f285e5bb223ffd651e7540973a540b
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests

/cherry-pick release-1.20


Activity feeds are not recorded for actions against roles / policies and creation of sub-terms in glossary

Affected module
UI
Describe the bug
Activity feeds should show all the creation, maintenance,  deletion activities in OpenMetadata as performed by the user in the UI.
In the below user case, DG policy term was created , along with a few subterms.
Only creation of parent term is visible. Creation of sub-terms is not appearing in the activity feed.
Later, the desc of one of the sub-term was edited and same is appearing in the activity feed i.e. apparently maintenance activity is recorded but not the creation of sub-terms.

use case 2: Policy is created, but same is not appearing in activity feed.

**

use case 3 : role updation against user is not being captured in activity feed.

**
version
13.3

@lailapatel this is intentional, policy action should be minimal and only limited to admins. Activity feed goal is to show the changes that entity is going through and facilitate collaboration among data consumers/producers. Policies and Roles should be rarely changing , even if they change its admin only operation there isn't any benefit or collaboration aspects to policies & roles.
Do you mind explaining how are you using activity feed and why you would like to see roles and policies changes in activity feed.

yes, policy and role actions were performed by Admin User only in the above case. We were considering the activity feed for  Audit log purpose. However, if the purpose is only collaboration then its okay to leave this.
then this is only required for the glossary part.

@mohityadav766 glossary term addition works but deletion is not showing up


Nada/P2PS-3945/fix: remove unused dependencies

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.784%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
6428

Relevant Lines:
6981

💛  - Coveralls


Maintenance Pool Service

If enabled and properly configured, project_detach_node will move the node to the maintenance project and POST to the maintenance service URL.
examples/hil.cfg has been updated with the new config options.pool
docs/maintenance-pool introduces the maintenance pool, shows an example use-case, and describes the configuration process.

Naved and I talked about some options for error checking the POST response.  We suggest that even if the POST fails, the node still be taken away from the user's project and put in the maintenance pool.  Then, an error will be logged for the admin to see.
We also thought it would be helpful to add a configurable for powering off the node when it gets moved into the maintenance pool.  This would be for users who don't want to setup a full-fledged service but still have basic maintenance done.
As for testing, would it be appropriate to have my tests in a new file? The API test is getting rather large.

After some discussion with @naved001, we decided it would probably be more appropriate to add the sample service in a second pull request.
One issue came up when writing the tests: running project_detach_node with maintenance enabled requires a server to POST to.  As a placeholder I put a (real) dummy website that will take the POST.  Since this might not be appropriate for unit tests, we can either keep the POST out of the tests or try using requests_mock.
Are there any other options for the dummy POST that would be worth exploring?

I discovered that my maintenance pool test is causing the cli.py integration test to fail somehow, which I will be investigating.

Works for me, merging.


Bug: BLE Connection Raspberry Pi4 Not working

Describe The Bug
Switch displays as "no response" in home app. Not actually triggering device
To Reproduce
Setup as README BLE connection
Expected behavior
Press in home app and switchbot presses
Relevant log output
[SwitchBot] Bot: `x` failed refreshStatus with BLE Connection

Config for homebridge-switchbot
{
            "name": "SwitchBot",
            "credentials": {
                "notice": "Keep your token a secret!"
            },
            "options": {
                "devices": [
                    {
                        "deviceId": "F0:F0:0F:00:0F:0F",
                        "configDeviceName": "5.1 Toggle",
                        "hide_device": false,
                        "configDeviceType": "Bot",
                        "ble": true,
                        "bot": {
                            "mode": "press",
                            "deviceType": "switch"
                        }
                    }
                ]
            },
            "platform": "SwitchBot"
        }

Screenshots
No screenshots, I assume this is just me reading the README wrong...
Device & Model
SwitchBot
Node.js Version
v14.18.2
NPM Version
v6.14.15
Homebridge Version
v1.3.8
Homebridge Switchbot Plugin Version
v1.4.0
Homebridge Config UI X Plugin Version
v4.41.5
Operating System
Rasberry PI OS (Raspbian GNU/Linux 10 (buster))

Fixed. For anyone seeing the same behaviour, I had to make my MAC address without the colon separators e.g:
F0:F0:0F:00:0F:0F -> F0F00F000F0F


Choosing WarioWare ALT to Wario Land Level freezes game

Choosing WarioWare ALT to Wario Land Level freezes game when using brawlbuilder to build ISO of project m.

I can confirm this as well, @mogzol any idea why this happens?


Investigating test_vulkan issues

While investigating the test_vulkan buffer_single_queue on a recent Android version two problems surfaced:

The usage of Core API functionality not available on the API version the instance is created with.

This can be fixed by either increasing the API version (to VK_API_VERSION_1_1), or by enabling and using the KHR extension function entrypoint (in our case it was vkGetBufferMemoryRequirements2KHR).

Assumptions on supported handle types for VulkanBuffer.

Makes assumptions about VULKAN_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_FD being supported unconditionally.
Misses coverage for VK_EXTERNAL_MEMORY_HANDLE_TYPE_DMA_BUF_BIT_EXT, VK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID, and others depending on availability on a platform.

As the test is not finalized I hope this can be addressed.

Hello!
We recently merged https://github.com/KhronosGroup/OpenCL-CTS/pull/2076, which should solve part (1).
Solving part (2) requires more significant work, and may be moved to a separate issue.


--serverlist differs from vim's output

With vim --serverlist you can test whether there is a running instance of a vim server.
nvr --serverlist seems to always respond with /tmp/nvimsocket even if there's no running server.
I think it would be ideal that nvr --serverlist would emulate the previous behavior of vim --serverlist and not return anything if there are no running nvim sockets.
Testing whether the socket exists with something like [[ -e /tmp/nvimsocket ]] in bash is an easy workaround, but I can't help thinking it'd be nicer if nvr was a more faithful emulation of vim's clientserver functionality.

Maybe nvr -h is a bit misworded here?
It's supposed to print the address to be used, which is always /tmp/nvimsocket if neither $NVIM_LISTEN_ADDRESS nor --servername set it to something else.
Opposed to Vim, there's no central instance that knows about all the clients; there's no way to make it work like in Vim.

This actually clobbers my workflow... I used to use vim like this:

Open vim instances (always as servers) for various tasks
Open additional files from anywhere, at leasure, with --remote, using a script that would find the right vim instance from --serverlist based on the root dir.

That would be hard to do in nvim/nvr.
Couldn't all the vim instances be listed somewhere so that nvr --serverlist works and is actually a list rather than just one variable? It's pretty much a useless flag now. I'm imagining I would have to write a hack that echos the servernames to a file manually to be read later, but that would be too ugly.

Every Neovim instance is a server on its own. But opposed to Vim, they don't know about each other. That's why it can't be done "nicely" from nvr.
Would a hacky oneliner work for your use case as well?
$ lsof -p $(pgrep nvim | paste -sd ',') | grep '\<unix\>' | awk '{ print $NF }' | sort

this worked a bit better for me
lsof -p $(command pgrep nvim | paste -sd ',') | awk '$5=="unix"' | grep -oP '/tmp/nvim[^\s]+'

As of this commit, --serverlist should behave as expected now.


No implementation found for method write on channel plugins.it_nomads.com/flutter_secure_storage

My app is created with fresh install with android embedded v2

Which device are you getting this error on? And which version of the package are you using?

I'm closing this as duplicate of #152

Redmi Note 8 (mobile)  • 17eba2c2   • android-arm64  • Android 10 (API 29)
moto g 7 plus (mobile) • ZY225G7TW3 • android-arm64  • Android 10 (API 29)
flutter_secure_storage: ^4.2.1

Maybe it's a duplicate but i don't see progress in issue 152

I have the same issue.

:/


Update EyeTV to 3.6.8

also fixed homepage and license

Thank you for the contribution. It needed some fixes, so they were made in 97b046fee89fbef01c486be8ea7641426f953746. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Swiper Element drag issue (Nuxt 3)

Check that this is really a bug

[X] I confirm

Reproduction link
https://stackblitz.com/edit/nuxt-starter-6tu6b1?file=components%2Fcarousel.vue
Bug description
Hello, I'm trying to initialize Swiper with the parameters I need but I get a strange behaviour when dragging, the carousel "jumps" uncontrollably.
The parameters i'm trying to use are:

slidesPerView
allowTouchMove
loop
centeredSlides
initialSlide
grabCursor
freeMode

I don't understand which parameter or combination of them breaks the carousel, but having only slidesPerView: 'auto' works correctly.
Any help please?
Matteo
Swiper version
9.0.5
Platform/Target and Browser Versions
macOS Chrome

Hi @nolimits4web ,
it seems the reported behavior is still present also with 9.1.0, after i drag for a while
https://stackblitz.com/edit/nuxt-starter-bf2gbx?file=package.json
Am I doing something wrong?
Thanks,
Matteo

I created an even more basic reproduction test (no Nuxt, no unnecessary paremeters), loop=“true” + slides-per-view=“auto” seems to not work properly, in short: once the user drag and reaches the loop the carousel “jumps/flickr” to the wrong position, it is even more sensible with relative units;
https://codepen.io/fiurboy/pen/ExevaBW?editors=1100
Thanks,
Matteo


Performance regressions on changing netcdf dependency to hdf5 v1.10.8

NetCDF version: 4.8.1
OS: Windows 10 and Debian 10
I am trying to change the dependency of NetCDF from hdf5 v1.8.12 to v1.10.8. I was able to change the dependency successfully (thanks to help from you). After this, when I run our performance suite, we see regressions in several of the netcdf functions. I know that netcdf regressions with hdf5 1.10 is a known thing, but still, I thought I would report this and attach a summary table of some of the regressions that we saw.
For each of the functions below, I am comparing the same workflow in my sandboxes with hdf5 1.8.12 and hdf5 1.10.8. I made several runs and the results below are the average of all the runs.
Function: nc_get_var_string
Workflow: Create a temp file, write an NC_STRING variable to it and read it back
Windows % Regression: 88.48
Linux %Regression: 21.048951
Function: nc_create
Workflow: Create a netcdf-4 file
Windows % Regression: 26.53
Linux %Regression: 115.43
Function: nc_get_var
Workflow: Read a VLEN variable of basetype NC_BYTE from the attached file (/numeric_types/samples_int8)
Windows % Regression: 1561.09
Linux %Regression: 2.11
Function: nc_get_var
Workflow: Read a VLEN variable of basetype NC_STRING from the attached file (/text_types/samples_string)
Windows % Regression: 76.74
Linux %Regression: 36.74
The highest regressions are seen with nc_get_var and nc_get_att with VLEN types. I am still working on getting the performance numbers for nc_get_att and will post them as soon as they are ready.
Even though I have posted results for nc_get_var with basetype NC_BYTE and NC_STRING, I could see regressions with other basetypes as well.
I know that regressions with hdf5 1.10.8 are expected, but still, I would like to get your opinions on the results I posted above.
Are these slowdowns expected? Is there any way to improve performance with hdf5 1.10.8?
Kindly let me know if you want more information regarding the investigation.
Here is the link to the nc file we used for the 'nc_get_var' tests:
https://mathworks-my.sharepoint.com/:u:/p/abaruah/ES2lQMAc0MRJpBOF8huTQ3EB02Y0oynhIY1CYC_mo08j-w?e=Sfb4iz

Hi @abhibaruah thank you for your patience!  The performance regressions with HDF5 1.10.x as compared to 1.8.x is expected, as you point out; I will take a look to see if I observe similar regressions.  I know that the HDF group has put effort into reverting some of these regressions in the 1.12.x branch, have you tried your benchmarks against the latest HDF5 1.12.x release?


[ISSUE #3696]Optimize the query consumer connection display

Make sure set the target branch to develop
What is the purpose of the change
#3696
The optimized display:

Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.1%) to 53.166% when pulling 86f55acdb69733564a9d006ab44caa6d57168eeb on zhangjidi2016:consumerConnection into 6ebb4e40d4943679d5e37dbc96919e8cfc5808f5 on apache:develop.

Codecov Report

Merging #3697 (86f55ac) into develop (6ebb4e4) will decrease coverage by 0.14%.
The diff coverage is 83.33%.

@@              Coverage Diff              @@
##             develop    #3697      +/-   ##
=============================================
- Coverage      47.34%   47.20%   -0.15%
+ Complexity      5037     5021      -16
=============================================
  Files            627      627
  Lines          41349    41347       -2
  Branches        5373     5373
=============================================
- Hits           19578    19518      -60
- Misses         19349    19407      +58
  Partials        2422     2422

Impacted Files
Coverage Δ

...mmand/connection/ConsumerConnectionSubCommand.java
73.68% <83.33%> (+1.18%)
:arrow_up:

...rocketmq/broker/filtersrv/FilterServerManager.java
20.00% <0.00%> (-14.29%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
66.07% <0.00%> (-5.36%)
:arrow_down:

...lient/impl/consumer/DefaultMQPushConsumerImpl.java
39.47% <0.00%> (-2.29%)
:arrow_down:

...rocketmq/client/impl/factory/MQClientInstance.java
51.30% <0.00%> (-2.00%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-1.50%)
:arrow_down:

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
78.21% <0.00%> (-1.49%)
:arrow_down:

...n/java/org/apache/rocketmq/store/ha/HAService.java
70.95% <0.00%> (-1.00%)
:arrow_down:

...nt/impl/consumer/ConsumeMessageOrderlyService.java
43.68% <0.00%> (-0.73%)
:arrow_down:

...ent/impl/consumer/DefaultLitePullConsumerImpl.java
67.99% <0.00%> (-0.52%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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

Have you tested it in half-window, wid-window senario? We could polish it and logger warning problem in the next step.


Serious flicker issue?

System Details

OS: Win 11 pro
Thorium Version 120.0.6099.235

Problem
Whole screen flickers when video is played and get blurry when moving mouse or just randomly, not sure what or how is this caused.
Screenshots
here is a recording-
https://github.com/Alex313031/Thorium-Win/assets/107706560/53c79123-b126-4b64-9310-c080ac2b2fc0
Additional Notes
This started happening to me as recently as yesterday so I am really not sure what is causing this, any help is appreciated.

This is really annoying and harmful to the eyes due to the constant flickering of vide playbacks as you might imagine so it would be nice if the team could give a faster response to it

Update- Disabling hardware acceleration fixes it somehow

seems like it is fixed in latest 37th build


Markdown: Rename Symbol doesn’t update path in Markdown source

![](some-image-path.png)

Place cursor somewhere in some-image-path.png.
Hit F2 (Win), or right-click → Rename Symbol.
Type a new name → Hit Enter.

Expected:

File some-image-path.png is renamed to the new name.
Reference to file in the Markdown source is updated to the new name.

Actual:

The file is updated as expected.
The reference to the file in Markdown source is not updated.

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

Specifically does this still happen in the latest insiders build?

@mjbvz Seems to work OK with the insider build (on macOS, at least).


Video summary

Hey,
Just wondering if there are any plans to add video summaries to tensorboard??
Alex

@danmane can comment further, but there is work to make tensorboard more extensible so that people could add additional summaries on their own.

We're sure to do this eventually, although it's not on the immediate roadmap. As andrew said, we are currently working on a plugin system for TensorBoard.
If any other contributors are interested in working on this, we could get this launched a lot sooner with some help. I'm marking it contributions welcome.

I have done some ad hoc video visualization in the context of video prediction (https://github.com/tensorflow/models/issues/553). I am interested to help implement this as a plugin (much like the embedding visualizer) via GIF (and/or a web-compatible video format).

I've migrated this to the TensorBoard repo.


updated to gw2sharp 0.11.0

I've opened #297 to remind us to switch the rate-limiting method over to using a middleware when we have time.


Add "number of ws away" to upcoming tolerances

Add a number block, similar to the workingsteps view, to the upcoming tolerances to indicate how many workingsteps away that workingstep is.

The workingsteps in that view should also start expanded.


[PE-D][Tester C] Parameter tags are not case-insensitive

This is a minor issue, but if you are considering to improve the usability, the parameter tags can be made case-insensitive :)

Labels: type.FeatureFlaw severity.Low
original: larainezo/ped#13

Closed as this is a suggestion rather than an actual bug

Closed as this is a suggestion rather than an actual bug


Override the podman image storage root directory

By default non-root images are stored in the home directory of the non-root user.  On appliances as the manageiq user this is a very small partition and not many images can be stored here.
Depends on:

[x] https://github.com/ManageIQ/floe/pull/90
[x] https://github.com/ManageIQ/manageiq-rpm_build/pull/415

https://github.com/ManageIQ/manageiq/issues/22640

Backported to quinteros in commit a1ce8bd3340674ab27f580892321c252c64a38b9.
commit a1ce8bd3340674ab27f580892321c252c64a38b9
Author: Keenan Brock<EMAIL_ADDRESS>Date:   Tue Aug 29 12:20:15 2023 -0400

    Merge pull request #46 from agrare/podman_containers_storage_location

    Override the podman image storage root directory

    (cherry picked from commit 047c9b19bd0d2cb753cc8a1ed3083537577c807c)


Hotjar integration

Should we consider integrating Hotjar?
Documentation

Hotjar tracking code
What is Hotjar?

Hello!
Does Hotjar integration still planned?

@dufrenb Thanks for asking!
It's the other way round, though. If you want Hotjar integration please consider placing a pull request. Or bug the Hotjar team to do it for you in this repository. There is no such thing as a free lunch.

@bittner
I was searching to use an analytical service in a web site for a client so I switch to use Clicky.
I think have Hotjar integrated as the others here: https://pythonhosted.org/django-analytical/services.html could be very good idea!

I agree. If you want to have it added to the list, come the repository, look at the code and write your implementation of the integration. It's not difficult to do.
We don't get paid, neither for promoting not for implementing integrations. Hence, it depends on the popularity of a service and the needs of our users (Django developers who like this app). If you feel it's missing add it to the code base. Our ask Hotjar, they may (or may not) care.

Fixed by #137


UI: Text Classification - Record card: improve access to labels list

Describe the bug
When label list is long, there is no way to show all the available labels without having to click the + sign on each records
To Reproduce
Steps to reproduce the behavior:

Go to my dataset  in annotation mode
Click on "+ sign" to view the full label list
Have to click again on the + sign on each records

Expected behavior
"it’s that +4 that I wanted to get rid of and instead just show the 4 labels missing".
View directly the full list
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS [e.g. iOS]:
Browser [e.g. chrome, safari]:
Argilla Version [e.g. 1.0.0]:
ElasticSearch Version [e.g. 7.10.2]:
Docker Image (optional) [e.g. argilla:v1.0.0]:

Additional context
"We have around 25~30 labels"
"we reduced it to around 15 but still we can’t see all the options, and the annotators always have to click the + to see the extra labels"

Hi @davidsbatista,
We would like to check with you if that solution, quickly designed, could resolve the limitation you mentioned: https://www.figma.com/proto/0tm1Cs3ru6nEdF5ddBaXuf/Argilla-UI?node-id=809%3A10822&scaling=min-zoom&page-id=586%3A9553
The idea is to use the "one record/page view" to provide the complete labels list, with no click added.
You could use the arrow keys to move quickly to the next record.

Hi @Amelie-V looks good - thanks for taking the time to look into it.
just another suggestion, would it be possible to assign 0 - 1 keys shortcut to the first 10 labels? as in the named-entities.

@davidsbatista  It's indeed an interesting other suggestion. We will provide the shortcut interaction in the focus mode. The focus mode is on our roadmap and hopefully ready in Q1 2023.  It's an optimized view to able to annotate fastly in every task covered by Argilla. For now we'll implement the improvement we designed.

Update docs for v.1.1 @davidberenstein1957
https://docs.argilla.io/en/latest/reference/webapp/features.html#text-classification
Add a blue Note and explain the following behavior:
When the dataset contains a large list of labels (10 +) we encourage viewing the record one by one (from the footer) and using the arrow keys to move quickly to the next record.


Add CSS processing configuration

See https://github.com/fluid-project/fluidic-11ty/pull/30.

Maybe we can build this in: https://v1-0-0.11ty.dev/docs/languages/custom/#example-add-sass-support-to-eleventy