Pop up to select option is not opening

Not reproducible in latest DP. I can see the pop opening at the bottom by scrolling down. @AnandiKulkarni

@ravikp7  confirmed with Bharat Pop up should be always on viewport
CC - @bharath31


Method colors not consistant.

trying to get methods color'd yellow.  Not all methods are working correctly, not sure if this is CoCo or something else.  Both methods and extension methods are colored exactly the same.
I have attached my screenshot.

and..  i noticed a pattern,  the variables that are working,  are explicitly typed.  The others are declared as var.

this is due to the cs file being opened independent of the solution/project.  It looks completely different otherwise.

@escofield You are right, this is due for files were opened independent. I have an opened issue for it. You can track #2.


Add System.transpiledSources

This pull request let access the dynamically transpiled module sources. The main goal is to support source map in nodejs error stack trace.
If you want to see how we could support source map in nodejs check my repo at https://github.com/dmail/system-node-sourcemap.

Nice work! Do you really need to run your own project at https://github.com/dmail/node-sourcemap or could you not merge the undefined prepareStackTrace work with https://github.com/evanw/node-source-map-support?
Also perhaps a better than API than a readSource callback would be the expectation that the Error object contains an originalSource string? If such a thing was supported, I'd happily output that from SystemJS itself as it could form a neater protocol for this sort of use case. Let me know your thoughts?

I'm very glad you like it :)
Concerning my own project, I'm not especially attached to it, but it was easier than doing a pull request to node-source-map-support. I would even prefer to merge with them but I have to take the time to understand their more numerous use case.
I love your idea of an originalSource property on the error object, if it comes to SystemJS I would immediatly change my code to get source from there. For information, the readSource API is inspired by the behaviour of node-source-map-support.
To conclude, I think that adding System.transpiledSource is still relevant even if I don't see an other use case at the moment.

Moreover node-source-map-support used Error.prepareStackTrace to catch all errors and I cannot polyfill this behaviour. It makes me unconfident to send a pull request.

I must admit I'd be far more inclined to accept a PR to this project that adds the full node source maps support you have than I am to accept this System.transpiledSources API.
Also do you have any idea when projects like this won't be needed to get source maps support in future?

Or even the error.originalSource type protocol would be preferable.

a PR to this project that adds the full node source maps support you have

You want an other PR including node source map support in your code base?

do you have any idea when projects like this won't be needed to get source maps support in future?

I hope as soon as possible but I don't have information

Or even the error.originalSource type protocol would be preferable.

I'm ok to rely on this, but we need to know the transpiled sources to populate error.originalSource. We could make System.transpiledSources private but we need something it, no?

Imagine the following code :
test.js
export function test(){
   throw new Error();
}

index.js
var System = require('es6-module-loader');

System.import('./test.js', function(exports){
  exports.test();
}).catch(function(error){
   // your code cannot detect this error but you may still want to support sourcemap here
the developper have to manually wrap the error
   // you have to manually add it like so
   require('system-node-soucemap')(error);
   throw error;
});

The response

Ah right, I see what you mean.
Ok, well then I'd suggest instead of a protocol or including the code in the module loader, it may be worth having a source maps tool that injects itself into the module loader:
function injectIntoLoader() {
  var transpiledSourcesStore = {};
  var systemTranslate = System.translate;
  System.translate = function(load) {
    return systemTranslate.call(this, load)
    .then(function(source) {
      transpiledSourcesStore[load.name] = source;
      return source;
    });
  }
}

Adding a hook for System.translate was my first intent from the very beginning.
"Unfortunately", transpilation occurs after translate, during the instantiate phase, as you can see here : https://github.com/ModuleLoader/es6-module-loader/blob/master/src/loader.js#L260.

@dmail what about just setting System.trace = true and using the trace API then?

@guybedford If each load.source is the transpiled source it seems like a nice way to do it.
I'm not sure of how to combine trace API, module instantiation & the call to the function makeErrorSupportSourceMap. Can you provide a short example to help me?

Yes load.source is the transpiled source in the trace. Then you just lookup the load in System.loads via the address just like you would have done in transpiledSources. See https://github.com/ModuleLoader/es6-module-loader/blob/master/docs/tracing-api.md for more info.

Thank you, we are almost done here but load.source returns the untranspiledSource, see https://github.com/ModuleLoader/es6-module-loader/blob/master/src/loader.js#L597.
Could we  add transpiledSource property on each load record ?

I'd consider adding it. Note though that the internal transpilation of the module loader here is not a production workflow and is only for experimentation. For example, SystemJS would support source maps in Node work against load.source exactly as you have currently without this change.

Note though that the internal transpilation of the module loader here is not a production workflow and is only for experimentation.
Under which conditions you would remove transpilation from module loading ?

For example, SystemJS would support source maps in Node work against load.source exactly as you have currently without this change
How could they do it ?

My last commit moves transpiledSource from transpiler.js to loader.js. Thank you for you time and your amazing work @guybedford

SystemJS does the ES6 -> ES5 transpilation within the transpile hook. The transpilation layer in this project is only really for experimental dev workflows and not recommended for use in production. To support SystemJS you would need to make sure you support load.transpiledSource || load.source as it wouldn't set load.transpiledSource as this code wouldn't ever run.
I'd prefer to stick with the SystemJS route and not encourage source maps for this workflow. Let me know if that is a possibility for you at all?

SystemJS does the ES6 -> ES5 transpilation within the transpile hook

Indeed, as the following line shows : https://github.com/systemjs/systemjs/blob/a38da7ed4c1c66e853c20d83375d35100f3453f8/lib/esm.js#L31.

I'd prefer to stick with the SystemJS route

I think like you, transpilation should occur during the translate hook.

Let me know if that is a possibility for you at all?

At first, I wanted to avoid systemjs because it's more high level than es6-module-loader but it's totally ok for me.
I've updated my module to rely on the translate hook (SystemJS). SystemJS can now have nice error stack on node, oh joy !

Awesome, thanks for understanding. Can I close this then?

Let's close this, thank you very much for your time


Levels For When It Goes Wrong With Git

How to Reproduce:

Look at the LearnGitBranching

What Should Happen:

It has levels covering "normal" git operations
It also has levels covering git operations when something has gone wrong

What Happens:

It has levels covering "normal" git operations
It does not have the "gone wrong" scenarios

Notes

There possible scenarios as I see them are: "merge conflict", "cherry-pick not possible", or "rebased local when remote is already pushed". I believe there could be much more of them.
If you read it and you like the idea, please feel free to vote the idea up and suggest some nice "gone wrong" scenarios in the comments :)

Merge conflicts are hard to teach about since those involve staging files
(and modifying files) where this app only teaches the higher level
operations (above staging).
It would be awesome to teach how to get out of bad scenarios though --
those are the scariest in git!
On Fri, Jun 30, 2017 at 10:58 PM Daniil Belyakov<EMAIL_ADDRESS>wrote:

How to Reproduce:

Look at the LearnGitBranching

What Should Happen:

It has levels covering "normal" git operations
It also has levels covering git operations when something has gone
wrong

What Happens:

It has levels covering "normal" git operations
It does not have the "gone wrong" scenarios

Notes

There possible scenarios as I see them are: "merge conflict",
"cherry-pick not possible", or "rebased local when remote is already
pushed". I believe there could be much more of them.
If you read it and you like the idea, please feel free to vote the
idea up and suggest some nice "gone wrong" scenarios in the comments :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pcottle/learnGitBranching/issues/430, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABFRn6_VLoNv6Br_n5qh0gw9-j5vumnqks5sJeAUgaJpZM4OLOks
.

--
-Sent from Gmail Mobile

So, there's no way in the current structure to talk about the state of the working directory or files in it, is that accurate?

Nope :-/ thatd be a big infra build to get that working
On Wed, Aug 9, 2017 at 3:58 PM, Liam Newman<EMAIL_ADDRESS>wrote:

So, there's no way in the current structure to talk about the state of the
working directory or files in it, is that accurate?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pcottle/learnGitBranching/issues/430#issuecomment-321404287,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFRn9s2yE8OvKxP0_QZXJjSzG8JZ8Izks5sWjmvgaJpZM4OLOks
.

--
Peter M Cottle
UC Berkeley 2012
UC San Diego 2011

(closing out old issues)

(closing out old issues)


Refresh: Move ONNX model validation into its own Stage

No need for it to take up RAM and time in the main PyTorch export stage.
cc @ramkrishna2910

Closed by #177


Introduction

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

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

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

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

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

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

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

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

Hi @ruchiD ,
We are looking for Mifos developers in a full-time role or internship who can work with us on a large-scale project and can extend or modify the core application, let us know if you are available, or anybody in reference.
Thanks.


stuck when going 'up' too much

Thank you for this library.
When going up above '/storage/emulated/0/' the picker behaves in strange ways.
It's probably related to the way android created these 'virtual paths'
possible solution: add an extra to the intend (max_height, top_reach)
eg. /storage/emulated/0/ > /storage/emulated/0/*
eg. /storage/emulated/0/DCIM/ > /storage/emulated/0/DCIM/*
eg. /storage/emulated/0/DCIM/Camera > /storage/emulated/0/DCIM/Camera*
Testdevice: Huawei p9 lite

It's my pleasure, it'll be fixed in the next version Insha Allah.
Thank you very much for your feedback,

Thank you for this library.
I avoid this bug by judging whether it contains files.
`public void goBack(View v) {
    if( location!=null && !location.equals("") && !location.equals("/") ) {
        int start = location.lastIndexOf('/');
        String newLocation = location.substring(0, start);
        // fix stuck when going 'up' too much
        File folder = new File(newLocation);
        if( !folder.isDirectory() )
            return;
        File[] files = folder.listFiles();
		if (files == null) {
			return;
		}

        location = newLocation;
        loadLists(location);
    }

}`

Thanks for posting this issue, it has been resolved in the recent commit b73b1757387e312ad2fd2a24f41f75c8c0981fe7


Velociraptor does not privide .msi package with its 5.8 release (breaks install-velociraptor.ps1)

Beginning with 5.8 Velociraptor does not provide a .msi package. As the download URL is hard coded to "https://github.com/Velocidex/velociraptor/releases/download/$tag/velociraptor-$tag-windows-amd64.msi" this will break the install-velociratpro.ps1 script.
As a workaround I've hardcoded the 5.7 msi package: https://github.com/Velocidex/velociraptor/releases/download/v0.5.7/velociraptor-v0.5.7-windows-amd64.msi
Additionally they have tagged the rc2 version of 5.8 with rc1 by mistake which also breaks the logic of determining the latest version. So this script is kind of "double-broken" by external circumstances.

@cyb3rwr3ck thank you for the heads up! Worked around this in https://github.com/clong/DetectionLab/commit/57583938e5d5cadeb72fb940425df12875394a1a

I think the long term fix here is to just grab the most recently released .msi. Rather than assume the tag has an associated .MSI, just find the MSI with the latest release version. I think I'm already doing this for the server.

Should be fixed here: https://github.com/clong/DetectionLab/commit/af0bd42fda0d9aa82fb80a7892058eac0758da42


Add sct and cert verification

Add sct and cert validations

Rename CertificateResponse to SigningCertificate
Add more testing around parsing
Add example fulcio/ctfe public keys and sct/cert examples for testing
Exceptions are still kinda just passed along

@di here is working sct/cert validation. There are sample in src/test/resources. They are generated off of my email, so it does feel weird to include them in a python client, but you could get away using them to test your code for now.


2 problems.

Hi,
Salesman disappear after reboot.
Character delete for no reason. (It's not a lua script)

For anyone experiencing this, please try updating to the latest version of Clockwork.


WaitForListItemsAction with Specified Element Count?

Hi, we have a couple of pages whose lists of data are rendered by AngularJS.  Testing these pages has been tricky because SpecBind is only able to examine the top parts of the lists.  In one case a search result page had 25 items but it was only ever able to see the top 4.  In another page with a list of 2 items only the first item was able to be examined.  The tests are running in FireFox.
This sort of feels like a Selenium interaction issue where as soon as the list is found in the DOM it's returned and never examined again.  I made a WaitForListElementToContainANumberOfItems POC waiting step but I don't understand the guts of SpecBind/Selenium well enough to make it work.
Can you point us in the right direction on this?

I am seeing a similar issue, where an Ajax call is populating a list.  If a "I wait for  to contain items" step starts executing before the Ajax call returns and populates the list, the step will continue to wait until it times out.  It never gets an updated copy of the DOM while it continues waiting.  If I put a breakpoint at my waiting step and let the Ajax call return and populate my list, even though it is well within the timeout, if I then continue execution in the debugger, since the DOM is now updated on its first check, it finds the list populated just fine and the test passes.


SD: Refactor AttnBlock, CrossAttention, CLIPAttention to share code

Changes made:

compute attention with Tensor.scaled_dot_product_attention
remove self.scale as they are no longer used

Results:

a horse sized cat eating a bagel

tinybox in a living room, vaporwave, volumetric light, octane render, hyperrealistic

Had to revert. Caused failure of hosted tests.


Very slow under Ubuntu

Hello guys,
I am using Ionide FSharp under Ubuntu 16.04. And the intelliseence and linter process is very slow.
It take around 15-20 sec to update.
I have a really small project has I just started it yesterday.
Any idea ?

it sounds like a problem with FSAC. CC: @rneatherway

Can't reproduce on any of my machines


Check Numba functions

Numba makes a huge difference to performance -- 10x. Yay! But:

[ ] What is the reason for this?
[ ] Would any functions benefit from being numbafied that aren't?
[ ] Are any functions numbafied that are just as fast without?

Seems OK from looking at the profiling results. Most of the slow functions are already either jitted or are pure Numpy.


Current status of dep-graph patcher?

Description
We've been running into some latency issues on some peoples machines with the postinstall script, and I was curious about the status of this workaround.
I went to check on the issue referenced in the docs and the issue appears to have been closed, with a note announcing support for depgraph extension API.

This feature landed a while back, in Nx 12.X. With support for the dep-graph extension documented, implemented, and released I'm going to close out this issue.
Here's a link to the docs: https://nx.dev/extending-nx/project-graph-plugins
If there is part of the extension api that needs further changes, feel free to open a new feature request detailing what is missing in the current implementation.

Motivation
Would be sweet to avoid the added install latency and utilize the Nx project graph extension API
Suggested Implementation

Example plugin
Nx Docs | Extending the Project Graph of Nx

Thanks!

I've setup a monorepo at work without nx-plus, and after some test nx seems to work without any change on .vue files
So maybe they can drop the patch entirely

@jordan-boyer thanks for the intel.
Your comment inspired me to investigate a little more.
Looking at the patch code, it seems like the nx logic it's modifying is still around.
Seem like that Nx code is used to register "explicit" workspace dependencies.
So I think the gap would be if you import a workspace lib from a .vue file the dep graph won't necessarily know about it -- but if you're not running into that issue, maybe those dependencies are being registered via other Nx logic?
If you're feeling curious you could test by identifying a .vue file that's importing from some project in libs/ then find that file and see what dependencies are listed.
yarn nx affected:graph --file=output.json

Example
Here's an example of how I think that logic registers in the graph
graph.nodes > $project > $project.files > $file.dependencies > e.g. my-cool-workspace-lib

Even if it doesn't register via the file it might be registering through other means, eg implicitDependencies cache inputs or something.
We're getting around this issue with implicitDependencies for our vue projects -- which works okay since our vue footprint is minimal -- but it's not very scalable. Hopefully as the project graph plugin api matures we will be able to use it to support vue files a little more easily.


Not working on Ubuntu 16.04 as specified in the howto

Thanks for the project, I've just tried to follow the howto, but get a
$ sudo python3 setup.py install
Traceback (most recent call last):
  File "setup.py", line 1, in <module>
    from setuptools import setup, find_packages
ImportError: No module named 'setuptools'

$ python3 --version
Python 3.5.2

I did not change the configuration - does it need any changes to work?
Are python modules missing?
Thanks

Prerequisites need to be documented - fixed by the pull request.


async/await

Update to pull request: This external IResponseHandler #84

So I can just close #84?

I believe so. I think I got everything out of it.

Wish you would have done the summary additions/edits in another PR, it is a bit hard to see your other changes in this PR now.

Yeah, I didn't mean to do it all in one
Let me try to revert it then re make the other changes

Not sure if reverting will fix it the "Files changed" view, might have to just remake the whole PR. But give it a try.
Sorry I didn't notice this sooner, could have saved you some work that way, I have just been kinda busy.


(nucleus): add NSS key log support

Feature Description
Support logging of SSL/TLS session keys in NSS key log format for nucleus external communications.
Use Case
This is an essential feature for auditing and deeper troubleshooting of IoT device traffic.
Proposed Solution
Many applications support this behavior via SSLKEYLOGFILE environment variable, others have their own mechanisms, like an upstream s2n-tls library which accepts a callback function. This might require changes from several upstream aws libraries which might be neglecting that capability at this point.
Other
https://github.com/aws/s2n-tls/pull/2584
https://datatracker.ietf.org/doc/draft-thomson-tls-keylogfile/

Hello,
Greengrass itself (the stuff in this repository) does not perform any cryptographic operations. It instead relies on both Java and the AWS IoT Device SDK. I would request that you make an issue in the device SDK to support this here: https://github.com/aws/aws-iot-device-sdk-java-v2/issues.
For the Java based operations, I do not see that Java itself supports NSS right now however there do seem to be some third party options that can convert Java's debug format into NSS; this is certainly something which you can use today with Greengrass if you enable Java's TLS debugging.

It instead relies on both Java and the AWS IoT Device SDK.

Yeah, that's what I mean with "This might require changes from several upstream aws libraries which might be neglecting that capability at this point.". Since when it comes to the meaningful aws-greengrass-nucleus external communications the aws-iot-device-sdk-java-v2 is just a wrapper for AWS Common Runtime in it of itself, which in-turn forms a graph of dependencies

out of which the cryptographic operations are done by the s2n library(which does support NSS key logging), hence projects like https://github.com/neykov/extract-tls-secrets are of no help(that was the first thing I've tried before realizing all of the above), that information is just not in the Java's debug at this point. I'm afraid issues that would need to be opened to all of those upstream repos would end up as stale without an overarching commitment to the NSS support on the amazon side, but I don't know if you are willing to make such a commitment.

Thank you for your reply. I certainly cannot speak for all of Amazon at this point, but Greengrass would be happy to expose the necessary hooks if our upstream dependencies had them. As you said, S2N does have the capability. Following up with the device SDK repository will be the best way to move this forward.

Thank you for a quick reply. That does look like the most sensible course of action, I will do that, mentioning this issue.

Closing until functionality is available in device SDK.


Enable building tracing in chip-tool by default

Problem

Transport and other tracing is useful for both test automations based
around chip-tool and for debugging.
Enabling tracing in chip-tool is already conditional at runtime based on command
line flags, but requires building with the tracing enabled
Tracing is very low-touch and is zero cost when disabled at runtime, so having it
enabled by default in chip-tool build makes it easier to access/use.

Issue #11552
Change overview

This PR enables the build to always include tracing feature
enabled in chip-tool since it's generally useful.

Testing
Testing done:

Unit tests and integration pass with no change
Tested that with --trace_file XXX and --trace_log 1, the tracing works as intended

/rebase


chore: Remove unused dependencies

Similar in arrow - https://github.com/apache/arrow-rs/pull/6792


Reproducible Builds

First thanks for making your app available freely under a FOSS license! I just took the freedom to have it added to the IzzyOnDroid repo, where it will show up with the next sync in about an hour from now. Be welcome to pick a badge to link there e.g. from your Readme here!
A few questions I'd have concerning the requested permissions. android.permission.READ_MEDIA_AUDIO and android.permission.READ_MEDIA_VIDEO are clear of course (and thus already have been added to the app's "green list" with the corresponding explanations). But is the app also intended as photo gallery, that android.permission.READ_MEDIA_IMAGES is requested? And what for is the "old" android.permission.READ_EXTERNAL_STORAGE (minimum Android version required is 5, so I assume you're using Storage Access Framework) – and what does the app write so it needs android.permission.WRITE_EXTERNAL_STORAGE?

At IzzyOnDroid we support Reproducible Builds (see: Reproducible Builds, special client support and more in our repo). Trying for yours, I was able to successfully generate the APK using ./gradlew assembleRelease, but the resulting APKs were not identical. That is a.o. because you insert timestamps at build-time, in at least 2 places.  So let's look at that:
 |: new-instance v7, Ljava/lang/StringBuilder;
-|: const-string v10, "\n    App version: 0.1.0 (97b945b/2024-08-29T06:18:45)\n    Android version: "
+|: const-string v10, "\n    App version: 0.1.0 (97b945b/2024-08-31T17:03:05)\n    Android version: "
 |: invoke-direct {v7, v10}, Ljava/lang/StringBuilder;.<init>:(Ljava/lang/String;)V
 |: invoke-virtual {v7, v0}, Ljava/lang/StringBuilder;.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
 |: const-string v0, " ("
@@ -905152,7 +905152,7 @@
 |: const-string v0, "0.1.0"
 |: const/4 v5, #int 1 // #1
 |: aput-object v0, v6, v5
-|: const-string v0, "2024-08-29T06:18:45"
+|: const-string v0, "2024-08-31T17:03:05"
 |: aput-object v0, v6, v2

There are your timestamps. Last, M7.json is what AboutLibraries creates – and which can be cured easily by adding the following to your build.gradle.kts:
aboutLibraries {
    excludeFields = arrayOf("generated")
}

We'd appreciate if you could help making your build reproducible. We've prepared some hints on reproducible builds for that.
Looking forward to your reply!
cc @obfusk

A few questions I'd have concerning the requested permissions. android.permission.READ_MEDIA_AUDIO and android.permission.READ_MEDIA_VIDEO are clear of course (and thus already have been added to the app's "green list" with the corresponding explanations). But is the app also intended as photo gallery, that android.permission.READ_MEDIA_IMAGES is requested? And what for is the "old" android.permission.READ_EXTERNAL_STORAGE (minimum Android version required is 5, so I assume you're using Storage Access Framework) – and what does the app write so it needs android.permission.WRITE_EXTERNAL_STORAGE?

tbf, mpvKt currently does not make use of any of these permissions. They're kind of left overs from the mpv-android lib I am using.
I've been planning on removing them by making my own fork of the library but haven't done so cause it didn't seem that important.
There is also some optimizations i'd like to make to the mpv-android lib i am currently using like removing some unused classes and such, I'll be looking into making these changes soon.

At IzzyOnDroid we support Reproducible Builds (see: Reproducible Builds, special client support and more in our repo). Trying for yours, I was able to successfully generate the APK using ./gradlew assembleRelease, but the resulting APKs were not identical. That is a.o. because you insert timestamps at build-time, in at least 2 places. One is here (I'd suggest to leave the timestamp out there, the commit hash should be totally sufficient) – the other is with AboutLibraries: ...

I've already found these and found solutions for it recently, as you can see from the screenshot, I got reproducible builds work successfully and i will be committing my changes soon
2024-08-31 18:43:20,444 INFO: ...successfully verified
2024-08-31 18:43:20,444 INFO: compared built binary to supplied reference binary successfully
2024-08-31 18:43:20,588 DEBUG: Using APK Signature v2
2024-08-31 18:43:20,599 WARNING: AllowedAPKSigningKeys missing but reference binary supplied
2024-08-31 18:43:20,602 DEBUG: skip deploying full build logs: not enabled in config
2024-08-31 18:43:20,602 INFO: success: live.mehiz.mpvkt
2024-08-31 18:43:20,602 INFO: Finished
2024-08-31 18:43:20,602 INFO: 1 build succeeded
2024-08-31 18:43:20,602 DEBUG: skip deploying full build logs: not enabled in config
2024-08-31 18:43:20,603 DEBUG: skip deploying full build logs: not enabled in config

And last, thank YOU for taking your valuable time to put this project of mine on your repositories. this means a lot to me.

I've been planning on removing them by making my own fork of the library but haven't done so cause it didn't seem that important.

Ah, thanks! So you'll do so with the next release then? In that case we can ignore them for now.

I've already found these and found solutions for it recently, as you can see from the screenshot, I got reproducible builds work successfully and i will be committing my changes soon

Wonderful, much appreciated! As soon as a release with APK is available, please give me a ping and I start verification again. If you want to have it checked in advance of the release, all I'd need would be the APK and the commit it was built from.

@IzzySoft I have released a version that supports reproducible builds!
and committed the necessary changes to Gitlab merge request

Thanks, taking a look now. But it seems like you're confusing something here: F-Droid.org has nothing to do with my issue here, we're talking about the IzzyOnDroid repo here :wink:
Eh, and no, that won't work. Hardcodded URL (with the version inside) to fetch the timestamp from during build? You'll have a lot of fun with that, like each new release will be broken and take more than a week to show up at F-Droid after manual adjustments.
What for are those timestamps needed at all? Can't you simply remove them? What makes them so important to risk breaking things? And just for that the need to install multiple extra packages (jq, curl).  Couldn't you do entirely without them?
Got it to work now, though:
---
repository: https://github.com/abdallahmehiz/mpvKt.git
updates: releases
versions:
  - tag: v0.1.1
    apks:
      - apk_pattern: mpvKt-arm64-v8a.*\.apk
        apk_url: https://github.com/abdallahmehiz/mpvKt/releases/download/v0.1.1/mpvKt-arm64-v8a-v0.1.1.apk
        build:
          - sed -r '/abi \{/,/}/ { s/include\(.*\)/include("arm64-v8a")/ ; s/isUniversalApk = true/isUniversalApk = false/ }' -i app/build.gradle.kts
          - timestamp="$(curl -sL https://github.com/abdallahmehiz/mpvKt/releases/download/${APP_TAG}/build-metadata.json | jq -r '.timestamp' | tr -cd 0-9)"
          - echo -e "\ntimestamp=$timestamp" >> gradle.properties
          - chmod +x gradlew
          - ./gradlew assembleRelease
          - mv app/build/outputs/apk/release/*unsigned.apk /outputs/unsigned.apk
        build_home_dir: /build
        build_repo_dir: /build/repo
        build_user: build
        provisioning:
          android_home: /opt/sdk
          build_tools:
          cmake:
          cmdline_tools:
            version: '12.0'
            url: https://dl.google.com/android/repository/commandlinetools-linux-11076708_latest.zip
            sha256: 2d2d50857e4eb553af5a6dc3ad507a17adf43d115264b1afc116f95c92e5e258
          extra_packages:
            - jq
            - curl
          image: debian:bookworm-slim
          jdk: openjdk-17-jdk-headless
          ndk:
          platform:
          platform_tools:
          tools:
          verify_gradle_wrapper: true

That's the recipe for the verification builder here. At IzzyOnDroid, the two are separate: we ship the APKs provided by the developers, and have them verified independently. Currently there are 2 builders running publicly, we hope for more in the future – especially for some run by people not on our team, to have them really independent. Details, as linked from the initial post: Reproducible Builds, special client support and more in our repo :wink:
And here's your welcome toot:

If you now want to read the first two lines of the initial post, maybe you will pick and add the badge? :star_struck:

What for are those timestamps needed at all? Can't you simply remove them? What makes them so important to risk breaking things? And just for that the need to install multiple extra packages (jq, curl).  Couldn't you do entirely without them?

Putting it that way, yea, tbh they're kind of a nuisance...

@IzzySoft I've updated the release workflow and removed the timestamp logic. Can you update it on your end too?

Will take care for it with the next release then. The current recipe has already been committed, so too late to change that (logs are intentionally append-only).


Immersive Spell Learning - DESTified

It's compatible out of the box and ends the eat book to learn spell mechanic.
https://www.nexusmods.com/skyrimspecialedition/mods/45514

This looks really good! I have been planning to integrate one of the more expansive spell research mod at some point, but this looks like the perfect solution. I will see to integrating this in the next version :)


Error in sideloadManifest() not displayed to user

Summary: I am trying to sideload an manifest file named manifest.xml on macOS when my /wef/ directory already has a manifest.xml from another addin. office-toolbox notices that they are two different files (because they have different dev/inodes) and refuses to sideload my manifest file.
Expected behaviour: office-toolbox should alert the user that the manifest file was not sideloaded.
Actual behaviour: office-toolbox acts as if the manifest file was sideloaded.
Relevant source code:
https://github.com/OfficeDev/office-toolbox/blob/f3fbfad849c47ec2abccc70faaf87261ab83afa8/src/util.ts#L140-L147
Suggested change: I believe that the two manifest files are different if stat.dev and stat.ino are different. This lines checks BOTH are different. This should be changed.

@TCourtneyOwen Did your recent changes happen to fix this?

@akrantz Yes, I believe my change should resolve the problem and obviate the need to even check for a duplicate manifest since we will now generate a unique manifest file name to put in the wef cache (e.g guid.manifest.xml)

OK this should be fixed now.


hello i can write data but i can't read how can i read data can you help me

For example, how can I read the data in the 40001 register, I wrote a code but it didn't work, how can I read the data?
void loop()
{
static uint32_t i;
uint8_t j, result;
uint16_t data[6];
result = node.readHoldingRegisters(0x40000, 6);
if (result == node.ku8MBSuccess)
{
for (j = 0; j < 6; j++)
{
data[j] = node.getResponseBuffer(j);
}
}
delay(100);
node.writeSingleRegister(0x40000, 1506);
delay(100);
node.writeSingleRegister(0x40001, 100);
delay(100);
node.writeSingleRegister(0x40002, data);
delay(100);
}

i have same issue did u solve?


bug:

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
NixOS 24.11
Describe the bug
Since upgrading I get warnings about upgrading my which-key spec. However, I have an issue with this mapping, which still gives me a checkhealth warning:
        require("which-key").register({
          { "<F11>", "<cmd>GuiFullScreenToggle<cr>", desc = "Toggle Full Screen" }
        })

Checking for issues with your mappings ~
- WARNING You're using an old version of the which-key spec.
  Your mappings will work, but it's recommended to update them to the new version.
  Please check the docs and suggested spec below for more info.
  Mappings: >
  { { "<F11>", "<cmd>GuiFullScreenToggle<cr>",
      desc = "Toggle Full Screen"
    } }

  -- Suggested Spec:
  {
    { "", "<F11>", desc = "<cmd>GuiFullScreenToggle<cr>" },
  }
- WARNING overwriting desc: >
  { "<F11>", "<cmd>GuiFullScreenToggle<cr>",
    desc = "Toggle Full Screen",
    prefix = ""
  }

Steps To Reproduce

Include single key <F11> mapping.
There is an error.

Expected Behavior
No warning
Health
No response
Log
No response
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/which-key.nvim", opts = {} },
    -- add any other plugins here
  },
})

you need to use add instead of register for the new spec...

My mistake. Thanks for the hint. Fixed now.


[Table]  Table headers text no longer left-align with cell text

What package is this for?

[ ] React

Describe the bug
Table headers text no longer left-align with cell text
To Reproduce
Visible on all versions of table
https://carbon-addons-iot-react.com/?path=/story/watson-iot-table--simple-stateful-example

Specific timeline issues / requests
Blocks https://jsw.ibm.com/browse/GRAPHITE-25130, required for graphite sync by Friday, Nov 13

:tada: This issue has been resolved in version 2.141.0-next.12 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.141.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Plugin fails on Xamarin.Android with vague error message ("Something went wrong on our end. Please try again.")

If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
Failure to fill out this information will result in this issue being closed. If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Generally speaking, I have an adversity to requesting assistance on GitHub; however, this issue has completely confounded me and the author of this plugin seems to be willing to take questions here.
Detailed information can be found here: https://stackoverflow.com/questions/57936383/in-app-billing-plugin-fails-on-xamarin-android-with-a-vague-error-message-some
Version Number of Plugin: v2.0.0
Device Tested On: Galaxy S9 (SM_G960U)
Simulator Tested On: N/A
Version of VS: Community 2019: 16.1.6
Version of Xamarin: <IP_ADDRESS>
Versions of other things you are using:
Steps to reproduce the Behavior
Expected Behavior
Actual Behavior
Code snippet
Screenshotst

I am having this same issue

Make sure you use my guide to android testing: https://jamesmontemagno.github.io/InAppBillingPlugin/TestingAndTroubleshooting.html


Upgrade to support Django3.2

Hello,
Thank you for your valuable contribution.
Are there going to be an upgrade/support Django3.2 soon? hence #14
Open-edx is using this pacakge. And given open-edx is in the process of upgrading all dependencies to support Django>3.2  (for context)
Let me know if you need to suggest changes (assuming you are willing to devote some time for review).

Should be fixed with version 3.0.2


Bug: @lexical/markdown text-format combination

When hydrating a lexical editor with the following markdown **Bold *Italic*** calling $convertFromMarkdownString should properly format this as bold & and bold italic text. However, for some reason, it doesn't, and the rendered result is Bold *Italic*
This seems to work when switching between editor content and markdown in the playground, but it does not work when initializing the playground with this content.
Lexical version: 3.8
Steps To Reproduce

Have a lexical instance with initialEditorState that invokes $convertFromMarkdownString('**Bold *Italic***')
See the content be rendered in editor as Bold *Italic* rather than the expected Bold Italic

Link to code example:
https://codesandbox.io/s/many-lexical-autofocus-forked-efq8sq?file=/src/App.js

The current behavior
Content is Bold and asterisks are rendered in editor
The expected behavior
Content should be Bold and Italic text should be italicized
--
Happy to share any more information if it's useful

Narrowed the issue down to a bug in this function, where when splitText is called, it can break up markdown format syntax so it's not formatted...
i.e. the following markdown syntax will never be imported correctly:
*Foo **Bar***
**Foo *Bar***
_Foo __bar___
__Foo _bar___

When findOutermostMatch is called on the above pieces of markdown, it wrongly identifies the outer most pieces of markdown, causing the other contents to then be "split" and subsequent formatting is never formatted correctly
In the first case, *Foo **Bar***, findOutermostMatch wrongly returns **Bar**, then splitText is called, and the leadingNode and remainingNode are *Foo and * respectively, causing lexical to then render

@hanford Thanks for digging into it! Was suspecting findOutermostMatch is not working correctly but didn't get a chance to play with regExp. The question is if it's even possible with regExp only. Especially for cases like above when *** is a closing tag for separate * and **. So the logic would be if we have * and ** opened, then the next *** is their combined closing tag, and we don't need to look for any * or ** further.
Maybe getting all tags matches (with its corresponding matching indices) and then walking through that list, so that we have info of currently started tags which can be used to distinguish between *** being a single tag or two combined closing tags

refs https://github.com/facebook/lexical/issues/2303

I'm having this same issue when using bold and italics, however, in your case bold was still working but not italics, and now, none of them is working, seems like something broke in the latest version, here is a reproduction:
https://codesandbox.io/s/lexical-bold-and-italics-not-working-99cg7q

Looks like there's also an issue when you apply bold/italic on a line that has a a space character after an emoji in the end:

Not sure if it's a new issue or related

For anyone running into this issue, here's a workaround you may be able to use.
For me, this was manifesting as the following:

Create some bold/italic text in an editor as part of a paragraph
Export to markdown, using the provided plugin utilities ($convertToMarkdownString)
Reload the editor
The text is now gone because it was parsed incorrectly using the provided utility ($convertFromMarkdownString)
Subsequent auto-save would wipe the text from the document

To workaround this, I used the alternate markdown syntax for bold/italics (___ instead of ***) and implemented it in a custom transformer.
import { Transformer } from "@lexical/markdown";
import { $createTextNode, $isTextNode, LexicalNode, TextNode } from "lexical";

function $createBoldItalicNode(text?: string) {
  const node = $createTextNode(text);
  node.toggleFormat("bold");
  node.toggleFormat("italic");
  return node;
}

function $isMarkdownBoldItalicNode(node: LexicalNode): boolean {
  return $isTextNode(node) && node.hasFormat("bold") && node.hasFormat("italic");
}

export const BOLD_ITALIC_TRANSFORMER: Transformer = {
  export: (node) => {
    if (!$isMarkdownBoldItalicNode(node)) {
      return null;
    }

    return `___${node.getTextContent()}___`;
  },
  dependencies: [TextNode],
  regExp: /___(.+?)___/,
  importRegExp: /___(.+?)___/,
  trigger: "___",
  replace: (parentNode, match) => {
    const [, text] = match;
    parentNode.replace($createBoldItalicNode(text));
  },
  type: "text-match",
};

Then registered this as the first transformer:
export const TRANSFORMER_COLLECTION = [
  BOLD_ITALIC_TRANSFORMER,
  ...TRANSFORMERS,
];

This fixed the editor issue, you just need to ensure everything else in your pipeline supports the ___ syntax for the formatting.

Should be fixed by #5758


See only output related to endpoint -> endpoint communication

As a user, I would like to specify which endpoint pair (pod pair in k8s case) I would like to watch and see only information that is related to this pair.
I would also like to provide tool with pod name, and the tool would infer endpoint ids automatically.

Partially solved by #6 but monitor output related only to a pair of pods remains to be implemented.

Depends on https://github.com/cilium/cilium/pull/2727

It seems like this is more or less done on microscope side, but is blocked by https://github.com/cilium/cilium/issues/1488 and https://github.com/cilium/cilium/issues/2552 so that all monitor events will have both endpoints available.


Storing a session in ajax call

I am aware that we need to add routes in middleware 'web' group to set and get sessions.
How do we do the same using ajax?
When I add the ajax route in the middleware 'web' group the ajax call is not executed.
And when its route is outside this group it works. But then I cannot set or get sessions when its outside.

Please ask on the forums.


WIP: Add lots of code comments and hint sheets

This PR will go over all previous solution sheets and add extra detailed comments to the code. It will also add hint sheet notebooks. For now it's WIP.

Closing for now as there are a lot of higher priority things to work on.


Nested transactions with step arguments fail with ArgumentError

When calling a transaction from another transaction the call fails if step_args are provided.
Error message:
ArgumentError:
       wrong number of arguments (given 2, expected 0..1)
     # ./lib/dry/transaction/instance_methods.rb:25:in `call'

pseudocode:
nested = Class.new do
 include Dry::Transaction
 step :process
 def process(input, *args); Success; end
end.new

# register nested in container C

root = Class.new do
  include Dry::Transaction(container: C)
  step :root, with: nested
end.new

root.call # ok
root.with_step_args(root: 'foo').call # error

The issue seems to be that the arguments can't be passed down to the nested transaction but the lib tries to.
I've prepared a test case that demonstrates this in the pull request. It does not provide any solution to the issue yet.
Short discussion on discourse:
https://discourse.dry-rb.org/t/nested-transactions-with-step-arguments-buggy/757

See issue #124


Adding Pantos Token

Adding the Pantos Token with address and logo

EIP-55 address format is required
I would advice to have transparent background in SVG, it would be better handled in darkmode but it is optional

Git it. Let me fix that :)

What do we do in the case of an overlapping symbol? Seems like there is another entry which has the same symbol as we do @MRabenda ?

@jacekv After internal discussion - I removed that test, Can you rebase your PR with master? Then I should be able to merge it

Done :) I hope that it passes this time @MRabenda

Thanks @jacekv


Signal.sigalrm failure on Windows with local invoke

Traceback (most recent call last):
  File "C:\Program Files (x86)\Python36-32\lib\unittest\case.py", line 59, in testPartExecutor
    yield
  File "C:\Program Files (x86)\Python36-32\lib\unittest\case.py", line 601, in run
    testMethod()
  File "C:\Users\mikk.laos\PycharmProjects\api\background-check-request\test\integration\test_app.py", line 28, in test_whenNoJSONBOdy_shouldReturnJsonNotParsebleError
    body='')
  File "C:\Program Files (x86)\Python36-32\lib\site-packages\chalice\local.py", line 486, in handle_request
    response = self._app_object(lambda_event, lambda_context)
  File "C:\Program Files (x86)\Python36-32\lib\site-packages\iopipe\agent.py", line 120, in wrapped
    signal.signal(signal.SIGALRM, self.handle_timeout)
AttributeError: module 'signal' has no attribute 'SIGALRM'

@kolanos there's a user blocked on this, if we can get it squeezed in. Thanks!


SQLite provider seems to ignore |DataDirectory|

Moved from https://github.com/aspnet/EntityFrameworkCore/issues/12767 posted by @bdongus
Unlike the SQLserver provider the SQLite provider seems to fail at resolving the placeholder "|DataDirectory|".
Microsoft.Data.Sqlite.SqliteException
  HResult=0x80004005
  Nachricht = SQLite Error 14: 'unable to open database file'.
  Quelle = Microsoft.Data.Sqlite
  Stapelüberwachung:
   bei Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   bei Microsoft.Data.Sqlite.SqliteConnection.Open()
   bei Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenDbConnection(Boolean errorsExpected)
   bei Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
   bei Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteRelationalConnection.Open(Boolean errorsExpected)
   bei Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteDatabaseCreator.Create()
   bei Microsoft.EntityFrameworkCore.Storage.RelationalDatabaseCreator.EnsureCreated()
   bei Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureCreated()
   bei idee5.Globalization.Test.WithSQLiteBase.MyTestInitalize() in C:\Users\xyz\Source\idee5 intern\idee5.Globalization4netcore\idee5.Globalization.Test\WithSQLiteBase.cs: Zeile23

Steps to reproduce
var contextOptions = new DbContextOptionsBuilder<GlobalizationDbContext>();
contextOptions.UseSqlite("data source=|DataDirectory|idee5.Resources.db3");
context = new GlobalizationDbContext(contextOptions.Options);
context.Database.EnsureDeleted();
context.Database.EnsureCreated();

The exception occurs in EnsureCreated.
Further technical details
EF Core version: 2.1.1
Database Provider: Microsoft.EntityFrameworkCore.Sqlite 2.1.1
Operating system: Windows 10
IDE: Visual Studio 2017 15.7.5

From @bricelam:
Microsoft.Data.Sqlite just passes the filename directly to the native SQLite engine--it doesn't process the |DataDirectory| replacement string. You can do it yourself:
var builder = new SqliteConnectionStringBuilder(connectionString);
builder.DataSource = builder.DataSource
    .Replace(
        "|DataDirectory|",
        AppDomain.CurrentDomain.GetData("DataDirectory") as string);
connectionString = builder.ToString();

From @bdongus:
@bricelam Thank you for your quick and helpful answer. Currently I do something similar. As it should be no big deal to do it in UseSQLite itself, I hope the team considers including it in the next releaase. That way noone needs to do it on his own or write a wrapper if used frequently.

Moved to https://github.com/aspnet/Microsoft.Data.Sqlite/issues/542


torch shape error

Hello, after setting up the environment locally, I tested using the fasta files in the Data directory without any issues. However, when I run it with my own fasta files, I encounter some errors：
Traceback (most recent call last):
File "./Active_sites/main.py", line 14, in
predict(model_class, args)
File "/tools/GraphEC/Active_sites/utils.py", line 84, in predict
outputs = [model(data.X, data.node_feat, data.edge_index, data.seq, data.batch).sigmoid() for model in models]
File "/tools/GraphEC/Active_sites/utils.py", line 84, in
outputs = [model(data.X, data.node_feat, data.edge_index, data.seq, data.batch).sigmoid() for model in models]
File "/conda_envs/esmfold/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/tools/GraphEC/Active_sites/model.py", line 151, in forward
h_V = torch.cat([h_V, h_V_geo], dim=-1)
RuntimeError: Sizes of tensors must match except in dimension 1. Expected size 1 but got size 213 for tensor number 1 in the list.

This error occurred when utilizing the torch.cat function. please verify the data dimensions.

Hello, please, I would like to ask you how the loss of active sites is calculated?

我也在处理NEW392第355个id时出现了相同的问题，我通过补充了一个维度全为1再进行拼接。我在使用预测NEW392过程中遇到了line 279, in _get_direction_orientation
t = F.normalize(X[:, [0, 2, 3, 4]] - X_Ca.unsqueeze(1), dim=-1)
RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.


Autostart and activate adb after boot

Is it possible to run this app and activate wireless adb automatically after a new boot? Everything works fine until a reboot is done.

Hello, any news about it ?

Hello I vote for this feature !

Does the Wireless ADB mode and .apk work with Meta Quest 3 headsets??  Perhaps a full demo of how to set all this up might alleviate the questions people have.  I know I am very interested in having this work.  This means I won't have to connect to my computer each and every time I load certain programs in my Meta.

Is it possible to run this app and activate wireless adb automatically after a new boot?

AFAIK That's not possible unless you have root perms.

Everything works fine until a reboot is done.

That happens because ADBs don't persist through reboots.

Does the Wireless ADB mode and .apk work with Meta Quest 3 headsets??

It works with any android device.

Perhaps a full demo of how to set all this up might alleviate the questions people have.

Paraphrasing the README:

Download the APK
Open command prompt and use cd to change your directory to the place where you downloaded it
Connect your Quest to your PC through USB
Execute the following commands:

adb install app-debug.apk
adb shell pm grant tdg.oculuswirelessadb android.permission.WRITE_SECURE_SETTINGS
adb shell pm grant tdg.oculuswirelessadb android.permission.READ_LOGS

That's it

To enable the tcpip 5555 mode:

adb tcpip 5555
Go into the app, turn the tcpip 5555 mode on
You're done.

ok thanks @ShockedCoder, at least for USB connected adb it works fine after reboots.

This app only tells the system to enable the native ADB wireless functionality, so if triggered after boot (assuming you're already automatically connected to a WiFi network, which is a requirement to enable the service), it would show the system prompt to accept running the service in the current WiFi network, which would require wearing the headset anyway.
I therefore don't see a valid need for this feature, especially considering that a long USB-C cable would work a lot better for use cases where frequent reboots are needed.


Load the SSDP component only when it's needed

Description:
Load the SSP module only when it's necessary. This change broke all Home-Assistant with the hue component without the discovery/ssdp.
Related issue (if applicable): fixes #24419
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the development checklist

I've also added the fix for the deconz component.

Thanks, good catch!

Good to merge?

@balloob any idea when this will find its way into a release? I am currently on 0.94.2 and cant use Hue anymore ...

0.94.2 is the next release so unless you're on dev

You mean 0.94.1? 0.94.2 was not released yet. It should be available in the next few days. In the meantime you can downgrade to the latest 0.93 version.

I expect to release 94.2 in the next 8 hours


Collective yearly budget: add a GraphQL loader

Fetching yearlyBudget for multiple collectives has a huge cost because of N+1. We must:

Add a loader for the field
Revert https://github.com/opencollective/opencollective-frontend/pull/2606

Should we also cache it on API side somehow?

Let's ANALYZE the SQL query that will serve the yearly budgets for the loader. If the complexity is above ~500 for 1500 collectives (number of collectives OSC is a contributor to) then we should indeed add a cache to the specs.

Fixed in: https://github.com/opencollective/opencollective-api/pull/8319
Should we close @Betree ?

Good for me; I don't think updating the frontend (as suggested in the issue) is really that important.


[lit-html] How to spread SVG attributes?

Description
I want to pass svg attributes like following:
function svgIcon(paths: TemplateResult<2>[], props: Props) {
  return svg`
    <svg class="my-icon-svg" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024" ${spread(props)}>
      ${paths}
    </svg>
  `;
}

I searched in the issues but did not find any solution.
The spread directive is still under discussion.
Is there a workaround?

I'm working on the spread directive now. I'll make sure it works with SVG.

Dupe of #923


Microsoft.Security/integration/* action needs to be modified to Microsoft.Security/integrations/*

I have confirmed in the Azure Activity log, that following does not appear in the logs.
Microsoft.Security/integration/read
Microsoft.Security/integration/write
Microsoft.Security/integration/delete
Instead following actions appears in the Azure Activity logs, which has "s". Could you confirm the behavior and fix the documentation?
Microsoft.Security/integrations/read
Microsoft.Security/integrations/write
Microsoft.Security/integrations/delete

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

ID: 47c90c57-4ed5-8ae3-9477-0a3a1e13f2b5
Version Independent ID: f3da651c-f7c1-60c5-968b-699d76dcc085
Content: Azure permissions for Security - Azure RBAC
Content Source: articles/role-based-access-control/permissions/security.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@yoichimu
Thanks for your feedback! We will investigate and update as appropriate.

@yoichimu
Thank you for bringing this to our attention.
I've delegated this to content author, who will review it and offer their insightful opinions.

Hi @yoichimu
Thanks your feedback about these actions. These permissions in the docs are autogenerated based on the Microsoft.Security resource provider. I will contact you separately.
thanks

#please-close


Browse collection object

I am really struggling to figure out what I've achieved so far with importing.  After a record is imported using the DWC importer,  the first thing a user needs to do is validate if the fields were correctly parsed to the TW fields  The only option given is to click on Browse for those that were successfully imported:
https://sandwich.taxonworks.org/tasks/collection_objects/browse?collection_object_id=1273169
From this page, however, there is little information provided. I don't see what the browse tool is providing.  It should provide a clear listing of all data fields for that record.
The tool should allow one to check if the fields imported were mapped. For example, was the determiner and date of determination correctly imported?  It is not clear to me in the example above.
Each value should also be hotlinked so if you click on an otu, locality, or determiner, you are taken to that particular page.
If I click on edit object: https://sandwich.taxonworks.org/tasks/accessions/comprehensive?collection_object_id=1273169
I see that the determiner is not included and also the added attributes are not present for editing.

@bpescador not sure what you mean about determiner. In the first link it shows:

Determined
2020-11-30
TaxonDetermination
Pheidole navoatrensis Salata & Fisher, 2020 ✓ by Salata on 2020-11-30 by Salata on 2020-11-30

* Looks the display is duplicating the determiner

(Also visible in second link in Determinations panel)
As for the hotlinks you mean that for instance if I click on "Imported" link I'm given a manifest of what was imported/re-used and if I click on each I'm redirected to a page specific to that kind of information? (e.g. going to https://sandwich.taxonworks.org/taxon_determinations/1230992 when clicking on determination)

If the determiner and date is correctly imported, I thought it would fill in the appropriate fields here: https://sandwich.taxonworks.org/tasks/accessions/comprehensive?collection_object_id=1273169
I don't understand where I should look for the data to verify it was correctly imported;

By hotlink I mean: from the browse window, https://sandwich.taxonworks.org/tasks/collection_objects/browse?collection_object_id=1273169
if I click on by Salata it takes me here: https://sandwich.taxonworks.org/otus/290434
but why not to:  https://sandwich.taxonworks.org/taxon_determinations/1230992 [I could not figure out how to get to that page until you provided the link]

@bpescador I'm (thinking out loud) wondering if a "report" of sorts would be something we might generate that could help. I would say
As a result of your import to TW [on such-and-such date] you have

XX new collection objects
XX new collecting events
XX new people
XX new OTUs
etcetera

The report may be able to have links to those objects?
As you (and I) learn TW, it's clear we'll both know more about where to look for our uploaded information, but I can understand what you are looking for. A way to suss out if all has gone well, all data is in and where expected.

We could have a task: Summarize
Which would count types of objects, and provide links to them.
A sort of summary dashboard of what's in the datastore.

So I typed out a long response and promptly closed the tab.
We have three things:
A - Data represented by DwC incoming
B - Data represented in TW
C - Data represented by DwC outgoing
The current Browse OTU task is 1) a super simple stub, albeit useful according to @tmcelrath, that is really a placeholder in my mind that 2) presents B, with a superficial refernce to C.  This clearly doesn't meat the needs of @bpescador.
I think @debpaul is precisely right that what we  need is a new task that specifically seeks to validate the input.  For example you could imagine three columns one each for A, B, C, with visual groups on each column, and links between those groups to help you trace the flow of data between the columns.  Tricky, but not impossible.
I'm not as sold on counts to be honest.  In some cases, with simple datasets, they may be useful as validators, but in the scale of @bpescador's data they quickly become not particularly informative beyond min/maxes.  Those might be useful, but not "guiding", i.e. they won't tell you where to go look for problems.
It's important to remember, I think, that our importer is a new paradigm- you don't have to import everything at once, nobody else has this type of functionality, where you can piecemiel fix this issues, this is huge, and eliminates some of the all/nothing issues.  I.e. first it's important to know that the data are in OK, but after that you can tease out the remaining issues, right in the interface, rather than having to go check counts, for example, and re-do everything from scratch.
So, quick counts, super nice, we can make an endpoint for that, but I think @debpaul suggestion for a new task is really the way to go to address the underlying issue.
@LocoDelAssembly what we somewhat need is a metadata map b/w A->B.  I haven't looked at your code in depth, but if we had a constant, or hash that did much of this map, then we could perhaps expose that for use in the comparative interface.  We may just have to hard code the linkages b/w the 3 columns as well.  For example this field in DwC (date) maps to these 6 fields, potentially, in TW.

I think these are all good suggestions, but I would suggest following GBIF's lead.  Compare how GBIF shows how they mapped imported data for the same specimen:
TW: https://sandwich.taxonworks.org/tasks/collection_objects/browse?collection_object_id=1273163

Compare with GBIF:  https://www.gbif.org/occurrence/865078905
I think this would also work for the showing what I expected for Browse collection object:


Documentation link invalid

line 65 of the docs/getting-started/install/kubernetes.rst suggests to use this command:
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v0.11.0-alpha.0/cert-manager.yaml
which is a:
server reported 404 Not Found
The only yaml files in the repo are found in /charts/
Please update the docs, or reinstate the non-helm solution.
Thanks!

Hi @StephanX !
Apologies about that, there was an issue with the release pipeline to get that yaml out.   Thank you!


fix: link to docs, instead of readme

Overview
This PR links to the Celestia docs pages, instead of to the docs in the orchestrator-relayer repository.
The reasoning is that if we use relative links for docs i.e. ../qgb-binary.md, it will break the links in the docs on the repository.

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

I'll re-run the automation once the docs site has been built, so that the link exists


Preview on task hover

This was a really convenient feature in 0.4.22 and I'd like it back. Ideally I'd like the link icon. But if the new design is firmly something else preview on Ctrl + hover is still an intuitive option. If I recall correctly the preview used to be of the nearest heading in the hierarchy, not the whole note.

Yes, the preview effect is gone. But the link icon is unnecessary to actual behavior, because if you click in the task text you jump directly to the place of the task.

I will have to see if it is possible to replicate/steal the hover preview functionality; if not, I'll just add an option for an explicit link.

Could there be a query or piece of dataviewjs code I can write that approximates this effect? As in, listing tasks and also another field with a link to the heading/section the task is in?

hmm, you can group by sections, but the result can be confused...

This was a really convenient feature in 0.4.22 and I'd like it back. Ideally I'd like the link icon. But if the new design is firmly something else preview on Ctrl + hover is still an intuitive option. If I recall correctly the preview used to be of the nearest heading in the hierarchy, not the whole note.

I find this feature very useful as well. I use it almost every day when using 0.4.22 until a few days ago.
This feature can be used during, for example, weekly review where one can hover to go to the original task location and check sub-tasks, notes, etc. After this is done, one can continue reviewing the query results and do the same for other tasks.
It would be great if this feature can be somehow added back!

With version 0.5, one can click and go to the specific line of the original task. It would be even better if this can be combined with the hover feature. That is, one click Cmd/Ctrl and then it would open the note in a hover editor and go to the specific line of the task.

But the link icon is unnecessary to actual behavior, because if you click in the task text you jump directly to the place of the task.

As for link icons, an alternative solution would be to add a link icon if the original task has a block link at the end. Otherwise, there is no link icon.

The hover behavior was actually Obsidian's native behavior. I suspect if you add a Link by modifying task text, it'll achieve the same thing.

I suspect if you add a Link by modifying task text, it'll achieve the same thing.

Do you mean one can achieve this by using the implicit field link for tasks? Can you elaborate how to add a link, e.g., block link, to the end of the task text? Maybe this way all tasks would have a link at the end and one can hover to go to the original task location.

But modifying task text we get stuck in an older issue: the loss of interactivity with the original task, i.e., the check/uncheck is reduced to a visual effect without consequence in the original task.

You can use the visual field on tasks to override the visual representation of the task while still being able to modify it.

visual field? 😳
sorry for my ignorance, what's field is that?

Thanks @mnvwvnm, GROUP BY section and GROUP BY link works pretty well for what I wanted!
That said, I didn't know this option existed and what it meant from the docs. Is there any documentation on all the ways you can GROUP BY?
Also, is this visual field a dataviewJs thing, @blacksmithgu?

visual is part of DVJS since it's a task attribute. The idea behind group by is really to group things, just as in SQL.

The issue is kinda old, and the group bys solved my underlying issue. I can reopen if there's still demand for this.


Allow letsencrypts .well-known folder

This PR allows access to letsencrypts .well-known folder to allow domain verification

This should be added on a per-site bases in the vhost configuration as an include.
Also for security reasons and to not leak any information I use the following config usually:
    location ^~ /.well-known/acme-challenge/ {
        default_type "text/plain";
        root         /var/www/letsencrypt;
    }

    # Hide /acme-challenge subdirectory and return 404 on all requests.
    # It is somewhat more secure than letting Nginx return 403.
    # Ending slash is important!
    location = /.well-known/acme-challenge/ {
        return 404;
    }


Kalendae not working for October

Kalendae appears to be not working for the month of October. I think this may have something to do with daylight savings.
Refer to attached screenshot

This issue also happens in Adelaide, Australia. In Adelaide our day light savings time starts the first Sunday of October at 2:00 am. This is the date this problem occurs in the Kalendae calendar each year.
From my testing this issue occurs in Safari on Mac, iPad, iPhone and the iPod. This problem does not occur in Chrome on these devices, or any device other device.
Here are some examples of the issue on the Kalendae demo page:

In October 2017 our daylight savings day is October 1st. When using a single year view of Kalendae October 2017 is completely skipped.
Is there any simple fix for this?

I think the only real to fix this is for Kalendae to completely ignore javascripts Date implementation and use a custom one like Moment for all of its calculations.
Either that or its doing exceptions for browsers, and that never ends well

Kalendae is using Moment.

The problem is rooted in a bug in JavaScriptCore's implementation of Date (JSC is the runtime Safari uses). I could try to work around it, but only if I could reproduce it, and I can't.  I'm afraid the only way this bug is ever going to be fixed is if someone who has this problem debugs it and submits a pull-request.

If you set your computer timezone to Adelaide - Australia this should recreate the issue.

I've tried setting my timezone to every single location every person has reported this problem from, and it still never duplicates for me. I've even tried changing localization settings in OSX and restarting the computer.

Just published v0.5.4 with @Turnerj's fix for this (hopefully).

PS, this video may explain things in better detail
https://www.youtube.com/watch?v=-5wpm-gesOY


Missing image size conversion for vx-disparity

Describe the bug
Image size from vx-disparity is taken from the base class defaulted at (640 x 480), with no way of modifying them in either base or derived class.
For rectified images at other image size the disparity image returns empty for vx. It doesn't show any error messages either as the copy into and from openvx image hides such error status.
To Reproduce
Run vx disparity computation from different image size.
Expected behavior
Should work.
Machine (please complete the following information):

OS and version: Ubuntu 18.04
ROS version  melodic
Version or Commit melodic devel

Additional context
one workaround i did now is adding a image_size setter and getter in the sgbm_processor base class. When imageCb gets called in vx, it detects for image size mismatch, resize the image and reapply config.

Hi JD-ETH, thank you very much for your comment.
I will take a look.

Should be fixed by #5 .


Without validation dataset,how can i conduct the step3 to calculate polygenic risk score?

Hey Bjarni,
Appreciate for your LDpred,here is my question when i run my summary data.
We only got reference genotype file,and conducted the first step successfully.But,when we run the step3 to calculate polygenic risk score,the warning messeage informed me:cannot find the phenotype from our file.
We want to kown where is the problem located,or how to solve it and run step3 successfully.
Thanks a lot.

Hi,
You cannot run the 'score' step without validation/target genotypes.  However, if you don't care about the prediction accuracy, and only want the scores, then you can run it without a dummy phenotype, or the --only-score flag (which I just added).
Regarding the phenotype format, you can use standard plink FAM phenotype file format.
I hope this helps.
Best,
Bjarni

Hey Bjarni,
Under your patient help,i have got the score successfully.But there is doubt still perplexing me.The prediction is consistent with our GWAS results,but the correlation coefficient is negative.How could i explain it.Or where is the problem which result in the phenomenon.
Thanks.

Hi,
The negative correlation is possibly an old bug that I had fixed, but now seems to have come alive again.  For now, just ignore it.  I'll get to it in a future version.  Thanks for reporting this!
Best,
Bjarni

Dear Bjarni,
Thanks your reply,I appreciate that you have helped me so much on my current work.
Thank you!


[Feature Request] Remove sources from Default English/All after they are added to a custom category

Why/User Benefit/User Problem
Users will not see duplicates of source in English/All after it's added to a custom category.
What/Requirements
Remove source from Default English/All category when source is added to a new Category, just like how Categories for manga work in Library.

Added in https://github.com/jobobby04/TachiyomiSY/commit/4bd88fa19412a1eed99b801b8e0c75df0d2e170c


custom metrics not work(http2: stream closed)

I'm running the adapter with the following command .
git clone https://github.com/coreos/kube-prometheus.git
cd kube-prometheus/
kubectl create -f manifests/setup
kubectl create -f manifests/
cd experimental/custom-metrics-api
sh deploy.sh
kubectl apply -f sample-app.yaml

when i try to run kubectl get --raw "/apis/custom.metrics.k8s.io/v1beta1", i got the error Error from server (ServiceUnavailable): the server is currently unable to handle the request
and i check the adapter log, i found the following error.

apiserver was unable to write a JSON response: http2: stream closed
apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http2: stream closed"}

what should i do to make the metrics api start up?
My k8s version is

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:20:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:12:17Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}

In my case, the server works well but I get those same errors. Not sure what it is related to ?
The code where the error originate have these comments
            // Log errors that were not converted to an error status
            // by REST storage - these typically indicate programmer
            // error by not using pkg/api/errors, or unexpected failure
            // cases.

Maybe prometheus-adapter does not handle correctly when the http2 stream closed and output this error. I have no idea if we should we worried or not.

Same here, all is working as it should, but those errors are still being thrown.

I noticed that when you reduce/remove the numbers of custom metrics, it removes the error.
Could this be caused by the overwhelming number of custom metrics provided by the adapter ? The default metrics in the helm release looks like this :
    - seriesQuery: '{__name__=~"^container_.*",container!="POD",namespace!="",pod!=""}'
      seriesFilters: []
      resources:
        overrides:
          namespace:
            resource: namespace
          pod:
            resource: pod
      name:
        matches: ^container_(.*)_seconds_total$
        as: ""
      metricsQuery: sum(rate(<<.Series>>{<<.LabelMatchers>>,container!="POD"}[5m]))
        by (<<.GroupBy>>)
    - seriesQuery: '{__name__=~"^container_.*",container!="POD",namespace!="",pod!=""}'
      seriesFilters:
      - isNot: ^container_.*_seconds_total$
      resources:
        overrides:
          namespace:
            resource: namespace
          pod:
            resource: pod
      name:
        matches: ^container_(.*)_total$
        as: ""
      metricsQuery: sum(rate(<<.Series>>{<<.LabelMatchers>>,container!="POD"}[5m]))
        by (<<.GroupBy>>)
    - seriesQuery: '{__name__=~"^container_.*",container!="POD",namespace!="",pod!=""}'
      seriesFilters:
      - isNot: ^container_.*_total$
      resources:
        overrides:
          namespace:
            resource: namespace
          pod:
            resource: pod
      name:
        matches: ^container_(.*)$
        as: ""
      metricsQuery: sum(<<.Series>>{<<.LabelMatchers>>,container!="POD"}) by (<<.GroupBy>>)
    - seriesQuery: '{namespace!="",__name__!~"^container_.*"}'
      seriesFilters:
      - isNot: .*_total$
      resources:
        template: <<.Resource>>
      name:
        matches: ""
        as: ""
      metricsQuery: sum(<<.Series>>{<<.LabelMatchers>>}) by (<<.GroupBy>>)
    - seriesQuery: '{namespace!="",__name__!~"^container_.*"}'
      seriesFilters:
      - isNot: .*_seconds_total
      resources:
        template: <<.Resource>>
      name:
        matches: ^(.*)_total$
        as: ""
      metricsQuery: sum(rate(<<.Series>>{<<.LabelMatchers>>}[5m])) by (<<.GroupBy>>)
    - seriesQuery: '{namespace!="",__name__!~"^container_.*"}'
      seriesFilters: []
      resources:
        template: <<.Resource>>
      name:
        matches: ^(.*)_seconds_total$
        as: ""
      metricsQuery: sum(rate(<<.Series>>{<<.LabelMatchers>>}[5m])) by (<<.GroupBy>>)

Those default rules seems to be very intensive. It fetches almost all metrics from prometheus and execute sum/rate on all of them to provide custom metrics. Maybe it shouldn't be the default ? Why this specific configuration the default ?
@tallongsun Make sure the api is correctly being served by kubernetes. You can check it out with kubectl get apiservices.apiregistration.k8s.io | grep metrics.k8s.io. You should see an output like so v1beta1.metrics.k8s.io                 monitoring/prometheus-adapter   True        96d. You can then check if your service actually runs with kubectl -n monitoring get svc prometheus-adapter (make sure you change the namespace and the service name to correspond to what you retrieved with kubectl get apiservices).

Can this be re-opened? Doesn't seem like the issue is resolved, and what @nvanheuverzwijn is suggesting seems legitimate.

/reopen


Long-term Forecasting Target

Thanks for your great work!
In the ETT datasets, the target shoule be the oil temperature (OL), but in the repo I find that Time-LLM seems to predict all 7 features in a single-to-single manner. Also the feature category is not part of the input. So Time-LLM seems to hypothesize that all 7 features are from the same distribution. Is this the same setting with other baseline methods? Your paper claim that OL is the only target feature.

Hi, currently the ETT dataset is primarily a multivariate prediction dataset, which predicts all 7 values including oil temperature (OL). Additionally, for the sake of operational efficiency, we have employed channel-independent techniques in the dataloader to split it into univariate predictions for processing.


getInvites() and createInvite() are missing return types, and the types they do return are not compatible with Invite.

Fixed in #2395.


Add READMEs, simplify instructions (fixes #34)

Reopening PR, the other one was merged prematurely and reverted.
We need to make sure that everyone is aware on how to deal with these PRs. Let's wait until next Tuesday this time ;-)

Fixed comments in https://github.com/mozilla-l10n/appstores/commit/edf62ac333603895acfe361b11ab1f0015f2ee5c


enable float8 CI on sm89

Float8 was moved to torchao in https://github.com/pytorch/ao/pull/551, and currently the CI that we have for float8 is running on:
a. CPU nightly (skips all cuda related tests)
b. CUDA nightly (skips all cuda related tests which require torch._scaled_mm, because the default machines used for this do not have a high enough CUDA capability version.
We should enable float8 CI on sm89 machines, which have cuda capability 8.9.  The performance will not be representative, but we can at least test correctness.
Pointers:

https://github.com/pytorch/pytorch/pull/129608 is an example of adding github CI worklows on sm89
float8 tests currently test for H100s with capability 9.0 (https://github.com/pytorch/ao/blob/00b76c4291cdb6c5563f83936341afb9bac39f25/test/float8/test_base.py#L57), we should update that everywhere to test for capability 8.9, something like below:

# old
is_H100 = torch.cuda.is_available() and torch.cuda.get_device_capability() >= (9, 0)

# new
is_cuda_8_9 = torch.cuda.is_available() and torch.cuda.get_device_capability() >= (8, 9)

cc @drisspg @msaroufim , @jainapurva

@seemethere we could also alternatively move our CI jobs to use L4 instances which are cheaper than A10G and also support fp8. Last I tried to move our CI to use L4 i got timeouts while looking for runners so I suspect the L4 pool isn't big enough but this feels like a free efficiency win. wdyt?

One small note is that we will still need the skips on any rowwise tests since they currently require 9.0 +


Remove deprecated @types/rimraf

Per the npm install message:

npm warn deprecated<EMAIL_ADDRESS>This is a stub types definition. rimraf provides its own type definitions, so you do not need this installed.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on remove-types-rimraf at 96.03%

Totals

Change from base Build<PHONE_NUMBER>:
96.0%

Covered Lines:
4045

Relevant Lines:
4144

💛  - Coveralls


version to not consistent

Hi there
I am quite new to gradle and trying to use the semantic build versioning in our project, but having problem when try to  publish a zip file to nexus server in the child project
In the parent project, I publish the parent jar file to Nexus
..
        classpath "gradle.plugin.net.vivin:gradle-semantic-build-versioning:2.0.2"
...

apply plugin: 'net.vivin.gradle-semantic-build-versioning'
    project.version.with {
        startingVersion = '1.6.0'
}

uploadArchives {
    repositories {
        mavenDeployer {
            repository(url: NEXUS_RELEASE_URL) {
                authentication(userName: NEXUS_USER, password: NEXUS_PASSWORD)
            }
            snapshotRepository(url: NEXUS_SNAPSHOT_URL) {
                authentication(userName: NEXUS_USER, password: NEXUS_PASSWORD)
            }
        }
    }
}

In one of its child project, I tried to use maven publish plug to publish its zip distribution to nexus.
publishing {
    repositories {
        maven {
            url NEXUS_SNAPSHOT_URL
            credentials {
                username NEXUS_USER
                password NEXUS_PASSWORD
            }
        }
    }
    publications {
        mavenJava(MavenPublication) {
            from components.java

            artifactId 'content-aws-lambda'
            artifact buildZip
        }
    }
}

My current git tag is 1.5.0.
When try to run the version build
gradle clean bumpMinor build publish printVersion
It complains file not exist
_
Execution failed for task ':endpoints:amazon-lambda:publishMavenJavaPublicationToMavenRepository'.
Invalid publication 'mavenJava': artifact file does not exist: '/Users/xxx/xx/amazon-lambda/build/libs/amazon-lambda-1.5.1-SNAPSHOT.jar'_
I can see the files was built at libs/amazon-lambda-1.6.0-SNAPSHOT.jar, (I can also see amazon-lambda-1.6.0-SNAPSHOT.zip file was built in the distribution folder, which is the one I actually want to publish) but not sure why the publish still trying to find 1.5.1 version. It looks like it can only understand as a patch bump rather than minor bump.
I saw someone mentioned about the compatibility issue with Maven publish plugin, but not sure whether it is the case for me. Could you please advise how to solve this issue. Many thanks.

Yes, unfortunately this is a problem with the maven-publish plugin in some cases. Since marker tasks control version numbering, this is not done until after the task-graph is ready. It looks in some situations, the maven-publish plugin will use the initial version that it gets to decide the name of the artifact file. I haven't identified the particular situation because I've used this plugin with maven-publish without issue (the plugin uses itself for versioning and uses maven-publish as well).
One thing you can do is reset the version for the publication in a whenReady block. Something like:
project.gradle.taskGraph.whenReady {
    project.tasks.jar.version = project.version // You may need this to set the version on the jar properly
    project.publishing.publications.mavenJava.version = project.version
    project.publishing.publications.mavenJava.artifacts = [
        project.tasks.jar // reset the artifacts
    ]
}

One thing you may also have to do is reset the version in the buildZip task inside whenReady, if the task also uses the version number.

Hi,  thanks for the reply. Your code does help to solve the version issue for the jar dependency (publish the jar to nexus with correct version). However, I am not sure why the publish ignore the zip file created in the distribution.
Without implementing the version plugin, the zip file published together with jar correctly.
task buildZip(type: Zip) {
    from compileJava
    from processResources

    println "buildZip run"

    into('lib') {
        from configurations.runtime
    }
}

Do I need to update the zip version like what have been done in the whenReady? It seems that project.tasks.zip is not allowed. Please advise. Many thanks

@brolinuk Yes, you would have to do the same thing with the buildZip task. Instead of project.tasks.zip however, you would have to use project.tasks.buildZip.

Thanks. I have figured that out. Really appreciate your help
    project.publishing.publications.mavenJava.artifacts = [
            project.tasks.jar, buildZip]

Glad to help!


added back to home page link

Related Issue

Closes: #507
Description of Changes

I have added back to home icon on the following pages:

blog page
contact page
about page

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[ ] I have included comments in areas that may be difficult to understand.
[ ] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

Please provide any necessary screenshots to illustrate the changes made.

@AKD-01 Please review and merge :)


Fix flaky CLI tests

Describe changes

Fixes the CLI server tests
TODO: Fixes the docker prune fail during integration tests

Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@schustmi I guess these are the same failing tests? https://github.com/zenml-io/zenml/actions/runs/4605709310/jobs/8143515643?pr=1462

@schustmi I guess these are the same failing tests? https://github.com/zenml-io/zenml/actions/runs/4605709310/jobs/8143515643?pr=1462

Nah I think these are unrelated. Maybe I fixed those in #1470. Let's see.

@schustmi #1470 fixed the other issue, if you merge develop you can check whether all tests now pass on your branch


ClickListener -component can be exposed to user as a direct Component.

Currently ,ClickListener component is exposed to user as an internal component.It is a useful component which can be used in many scenarios.
It can be imported as  import ClickListener from 'carbon-components-react/cjs/internal/ClickListener';
From the recent folder structure change to the carbon-components-react, upgrading to latest version, breaks our code as we are using absolute path in import.
If we are exposing these components in internal to user, why not as direct components.
It would be nice if we can import this as a  import ClickListener from 'carbon-components-react'

Hi @sandhya-r-reddy! Thanks so much for taking the time to make this issue 😄
Totally agreed that internal utilities can potentially be useful to consumers, I think the group hesitates to expose some in an official capacity until they have more eyes on them to make sure they're prod-ready.
Regardless, you can still rely on the path to the internal component by using lib instead of cjs. We moved to supporting lib in a recent release, and this structure will always be present as an output of our build step. This makes sure that we don't tie in the format of our generated code to the folder name, so it should help with your specific use-case. e.g., import ClickListener from 'carbon-components-react/lib/internal/ClickListener.

Closing this for now, unfortunately dealing with the additional surface area of internal components is too much for the group to take on right now. Groups can 100% still use them if they are useful, but they won't follow the same guarantees that using the publicly available components have 👍


Error happened after enable auto download + upload

Visual Studio Code Version : 1.5.3
Code Sync Settings Version : 2.3.1
Operating System : Windows 10 x64
Occurs On: Upload
I have enabled auto download and upload on my Macbook and Windows desktop. I'm pretty sure the gist access token and gist ID is correct since I re-generate the token and reset sync settings. I can use the new access token to download settings from gist but issue happened again after I enable auto download and upload. Shouldn't I enable auto upload on 2 computers?
Console error
keybindingsRegistry.ts:109Ctrl+Alt+ keybindings should not be used by default under Windows. Offender:  40995  for  PowerShell.ExpandAlias
threadService.ts:217[Extension Host] Spell and Grammar checker active...
threadService.ts:217[Extension Host] Default Settings
threadService.ts:217[Extension Host] Code Actons Registering for: markdown
threadService.ts:217[Extension Host] Code Actons Registering for: plaintext
4threadService.ts:217[Extension Host] Windows_NT
2threadService.ts:217[Extension Host] GIST Object - [object Object]
threadService.ts:217[Extension Host] {"message":"Server Error","documentation_url":"https://developer.github.com/v3/gists/#edit-a-gist"}(anonymous function) @ threadService.ts:217
threadService.ts:217[Extension Host] false(anonymous function) @ threadService.ts:217
messageService.ts:119Error Logged In Console (Help menu > Toggle Developer Tools). You may open an issue using 'Sync : Open Issue' from advance setting command.e.doShow @ messageService.ts:119
threadService.ts:217[Extension Host] {"message":"Server Error","documentation_url":"https://developer.github.com/v3/gists/#edit-a-gist"}(anonymous function) @ threadService.ts:217
threadService.ts:217[Extension Host] false(anonymous function) @ threadService.ts:217
messageService.ts:119Error Logged In Console (Help menu > Toggle Developer Tools). You may open an issue using 'Sync : Open Issue' from advance setting command.e.doShow @ messageService.ts:119
threadService.ts:217[Extension Host] Windows_NT

+1

Is there any limitation of query times or APIs calling times in gist? I can upload the settings now.

For requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour.

Does this occur when you save the setting file multiple time in 5 seconds ? this error is due to GIST

It's possible since I enable auto upload on two computer within a short period. If this is GIST's limitation, should I close this issue?

Yes, because it downloads the old GIST and change the GIST. Both computers download the older version of GIST and update to their own , first one updated first and second one failed.

Got it. Thanks for the answer~ 😄


Fix dandiset navigation

Depends on #403.
Fixes a bug I found where clicking on a dandiset from the dandiset listing page would display the version of that dandiset that was previously selected (instead of starting with draft) due to publishDandiset not being set to null after leaving the DLP.

@AlmightyYakob Can you fix up this PR and then we can try to get it merged?

@AlmightyYakob Can you fix up this PR and then we can try to get it merged?

This should be good to go now.

@dchiquit Can you review when you get a chance?

@dchiquit discovered that this bug doesn't seem to be occurring anymore, and when #410 is addressed these changes will be moot anyway, so I'm closing this PR.


Error installing gem with version '~> 0.4.0'

I get this:
Could not find gem 'webpacker-react (~> 0.4.0)' in any of the gem sources listed in your Gemfile.
just webpacker-react works

https://github.com/renchap/webpacker-react/releases
Looks like 0.4 hasn't been released yet.

Yes, it has not been pushed to rubygems yet: https://rubygems.org/gems/webpacker-react/

@renchap Is it possible to release 0.4 already as it's stated in the version file? I got confused by the README as on one hand this library is probably ready to work with Webpack 4 (source) and on the other hand also not (source).

Sorry for the delay, it took me a long time to get back to maintaining this gem properly.
I just pushed version 1.0.0-beta.1 to Rubygems & NPM, feel free to test it!


fix: handle ESM-style config file

Fixes https://github.com/happo/happo-e2e/issues/50
Note that this PR doesn't change how the file itself is loaded to completely settle ESM compat, but it at least makes the CLI work properly when used in conjunction with NODE_OPTIONS='--experimental-require-module'

This is the quick & dirty patch I made via yarn patch to fix this + get rid of the need for the NODE_OPTIONS override:
--- a/build/loadUserConfig.js
+++ b/build/loadUserConfig.js
@@ -14,10 +14,12 @@ function _interopRequireWildcard(obj, nodeInterop) { if (!nodeInterop && obj &&
 function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }
 async function load(pathToConfigFile) {
   try {
-    let userConfig = (0, _requireRelative.default)(pathToConfigFile, process.cwd());
+    let userConfig = await import(process.cwd() + pathToConfigFile.slice(1));
     // await if the config is a function, async or not
     if (typeof userConfig === 'function') {
       userConfig = await userConfig();
+    } else if (userConfig?.default) {
+      userConfig = userConfig.default;
     }
     return {
       ...defaultConfig,

Probably need to pull in path.resolve for the import to fix it properly.

@quantizor would you be interested in working on a PR to handle the rest of the ESM compat?

@quantizor would you be interested in working on a PR to handle the rest of the ESM compat?

Last few work days before winter vacation, this is my contribution for now 😊


server: Update Cargo.lock

Fixes nightly builds that were running into inference errors in time.
Re. license: The unicode.org FAQ describes it as a "permissive MIT type of license" and it is OSI approved. We need this because several new dependencies with this license are now being pulled in by the url crate (through idna).

Finally, CI passed!


Expected relation between text size and time to run animation?

I've been testing the "waves" effect, and noticed it seems to slow down significantly as the text gets bigger. On a 26x67 text similar to the one you use in the showroom, it time tte waves takes 12 seconds; when I copy its contents to make a 52x139 text, it takes 46.5 seconds, or about 4x longer. 26x139 and 52x67 versions both took the original 12 seconds though.
Is this expected?

Based on some preliminary profiling, there may be something going on with this particular effect that is resulting in especially poor performance as the dimensions increase. I'll dig into it when I get the opportunity as it will likely improve performance across the library. Thanks.


Can the threshold for slow queries work accurately?

Question
Confirm the accuracy of slow query threshold, and whether there is any deviation in actual production.
For example, if the default is 300ms, will it only record at 301ms?

@mornyx PTAL

The calculation method for cost time is using the native time package in Go. We assume that the StartTime recorded in the session is accurate and do not consider the impact of goroutine scheduling on the clock. The margin of error is at the microsecond level and theoretically will not be perceived by our use case.
Ref: https://github.com/pingcap/tidb/blob/master/executor/adapter.go#L1439


Console error at startup: Invalid Function for Setter: ColorPicker::set_pick_color

Seems like a regression from bb0aeb48741033f80f7576bd138189931ffbaa62

CC @KoBeWi

Uh, I didn't notice that it's a setter and ClassDB complains about additional argument.

You can add
void ColorPicker::_set_pick_color(const Color &p_color) {
	set_pick_color(const Color &p_color, true);
}

as new binding.