Feature Discussion: targetElement to scroll to

For non scrollElement configs, It would be great to scroll to a y coordinate that is not window (y: 0).  Perhaps a config called targetElement and window.scrollTo(x,y) would take the x & y coordinates from the targetElement.offsetTop.
Also, the reason why scrollElement does not work is that the target element may not be scrollable, thus it's content not generating a scrollbar (and it's scrollTop == 0 all the time).
I can submit a PR if this sounds good to everybody!

@snewcomer this sounds logical to me. Would be great to get some input from some of the other collaborators though. @briangonzalez any thoughts?

I'll start working on this now...


SVD can fail when features are duplicates

for example, if we add a column of ones to our input data and pyGAM has fit_intercept=True, then we can get a SVD error.
There should be 2 checks:

no 2 columns of X are the same
if there is a constant column, then set fit_intercept=False

https://stackoverflow.com/questions/21827594/raise-linalgerrorsvd-did-not-converge-linalgerror-svd-did-not-converge-in-m

check for nans and infs, and remove those rows

cool!
figured it out!
this was failing because the edge_knots where [1, 1] and the we tried to scale the feature in the basis creation we were dividing by 0.
now basis creation checks for
if scale == 0:
    scale = 1


Scala211 doesn't support inline modifiers when printing tree with inline modifier

Issue type: Bug/Inconsistency
Scala version: 2.13.12
Scala meta version: 4.8.14 (latest)
Reproduction snippets:

Straightforward: https://gist.github.com/majk-p/f64713be5e910475e2e8c3ea03ee3e77
In weaver use case: https://gist.github.com/majk-p/cbceb0125b2083e3a10dac6abcfdfb23

Workaround exists: true
Context
I'm using Scala Meta to generate Scala 3 source code and test the code with weaver. Here's a simplified version of a test, where object Codegen is something that would be defined by my library.
Problem
import scala.meta._
import scala.meta.contrib._
import scala.meta.dialects.Scala3
import weaver._

object Codegen {
  def codeWithInline =
    source"""
    object Generated {
      inline def dummy = scala.compiletime.error("this method shuold not be invoked")
    }
    """

}

object SampleSpec extends FunSuite {

  val result = Codegen.codeWithInline

  test("Should generate code with inline") {
    val expectation = source"""
    object Generated {
      inline def dummy = scala.compiletime.error("DIFFERENT MESSAGE TO FAIL TEST")
    }
    """
    assert(result.isEqual(expectation))
  }
}

Expected behavior: Test fails with an error saying that the values are not equal, printing out both sources and highlighting the difference.
Actual behavior: Test fails with runtime error: UnsupportedOperationException: Scala211 doesn't support inline modifiers. For full stacktrace run scala-cli test https://gist.github.com/majk-p/cbceb0125b2083e3a10dac6abcfdfb23.
Root cause
In the example above weaver finds out that the assertion is failed and tries to print out the code. Unfortunately it attempts to do it using toString (rather than using syntax) which is defined as override def toString = internal.prettyprinters.TreeToString(this). TreeToString then does select the dialect, builds TreeSyntax and calls it.
object TreeToString {
  def apply(tree: Tree) = {
    val dialect = tree.origin match {
      case x: Origin.Parsed => x.dialect
      case Origin.None if tree.isInstanceOf[Quasi] => QuasiquoteTerm(Scala211, multiline = true)
      case Origin.None => Scala211 // this dialect is as good as any as a default
    }
    val prettyprinter = TreeSyntax[Tree](dialect)
    val code = prettyprinter(tree).toString
    tree match {
      case _: Quasi => code
      case Ctor.Primary(_, name, _) => s"def this$code"
      case _ => code
    }
  }
}

(please note that tree.origin is private, not controlled by end user)
The TreeSyntax then inspects the code within the context of the dialect and in case the default dialect is used it throws an error in case inline is used:
      case _: Mod.Inline =>
        if (!dialect.allowInlineMods)
          throw new UnsupportedOperationException(s"$dialect doesn't support inline modifiers")
        kw("inline")

At this point I doubt that the comment Origin.None => Scala211 // this dialect is as good as any as a default is still true :wink:
I'm not sure what's the proper solution at this point, there are definitely a few, including:

Changing the default dialect to Scala3
Defining an optional dialect on the tree root
Allowing the end user to modify the tree.origin

Workarounds
To make the test work without a runtime error, one can extract the expectation outside the test body like this:
object SampleSpec extends FunSuite {

  val result = Codegen.codeWithInline
  val expectation = source"""
    object Generated {
      inline def dummy = scala.compiletime.error("DIFFERENT MESSAGE TO FAIL TEST")
    }
    """

  test("Should generate code with inline") {
    assert(result.isEqual(expectation))
  }
}

The test works again, though the resulting error is not very informative.
- Should generate code with inline 51ms
  assertion failed (../../../../Code/personal/scalameta-inline-codegen/weaver.test.scala:31)

  assert(result.isEqual(expectation))
                |      |
                false  scala.meta.contrib.equality.Structurally$$anon$1@7c3023ea

A better solution might be invoking expect.eql directly and providing your own Show and Eq instances like this:
object SampleSpec extends FunSuite {

  val result = Codegen.codeWithInline

  test("Should generate code with inline") {

    val expectation = source"""
    object Generated {
      inline def dummy = scala.compiletime.error("DIFFERENT MESSAGE TO FAIL TEST")
    }
    """
    implicit def catsKernelEqScalaMetaTree[T <: Tree]: Eq[T] =
      (a: T, b: T) => a.isEqual(b)
    implicit val showTree: Show[Source] = _.syntax
    expect.eql(result, expectation)
  }
}

This fixes the error output:
SampleSpec
- Should generate code with inline 350ms
  Values not equal: (../../../../../../tmp/1197344035151293164/.scala-build/1197344035151293164_130f04a371_df73862be1-d8851bd2fa/src_generated/test/weaver.test.scala:38)

  object Generated { inline def dummy = scala.compiletime.error("[this] [method] [shuold] [not] [be][ ][invoked]") }  |  object Generated { inline def dummy = scala.compiletime.error("[DIFFERENT] [MESSAGE] [TO] [FAIL] [TEST]") }

Full example in a gist: https://gist.github.com/majk-p/2ce290d9dfd0dc9f56960bddbde4c41e

Thanks for reporting! Changing the default from 2.11 is probably a good idea, but I guess there is not perfect dialect that will work in all the cases.
To fix it permanently in Scalameta I think we would need to add a public withDialect method that would set a special Origin.Generated which would only contain the dialect. So when you create a tree you would be able to set which dialect this tree needs. Maybe we could just add it to the InternalTree or have it as public extension method if mima is not too happy.
As a workaround you could use TreeSyntax directly on the tree:
val expected = ...
val prettyprinter = TreeSyntax[Tree](Scala3)
val code = prettyprinter(tree).toString
assertNoDiff(code, expected)

or something along these lines

agreed with @tgodzik. TreeToString should perhaps be deprecated as it guesses the dialect of trees without origin, and cannot do it anymore.
unfortunately, quasiquote-generated code loses origin, so I don't know if we can fix it in scalameta. i am not even sure how the rest of the tree is actually preserved post-compilation :)
another idea is to use this, instead of quasiquotes:
val input = scala.meta.inputs.Input.String("...")
val tree = scala.meta.parsers.Parse.parseSource(input, dialect).get


Add styling for  options

When using a single <select>, the dropdown menu is generated by the browser, and thus the options cannot be styled. However, when using a <select multiple>, the options are actually part of the page content, and can be styled with CSS.
So, can styling for options of <select multiple> be added to Bootstrap?
CodePen

However, when using a , the options are actually part of the page content, and can be styled with CSS.

Not always, mobile browsers don't show these for example.

Actually, the browser decides how this is rendered, it could be risky to provide theming for this, because implementations of the browsers can change over time

However, when using a <select multiple>, the options are actually part of the page content, and can be styled with CSS.

Not always, mobile browsers don't show these for example.

Actually, the browser decides how this is rendered, it could be risky to provide theming for this, because implementations of the browsers can change over time

I'm talking about <select multiple>, not just a plain <select>.

@techboyg5 Those are screenshots of multiple select on iOS and Android :)

@techboyg5 Those are screenshots of multiple select on iOS and Android :)

OK, got it! Let's still add the styling because Firefox and Chromium (desktop) support it.

OK, got it! Let's still add the styling because Firefox and Chromium (desktop) support it.

"Support it" is a dangerous term to use here. I know Chrome and Firefox can handle colors differently on single selects for example which introduced this bug:

As I said before, the browser decides how the options are rendered. We can't know for sure what the effects on all OS/browser combinations with (dark & light modes) will be now and in the future.

OK, got it! Let's still add the styling because Firefox and Chromium (desktop) support it.

"Support it" is a dangerous term to use here. I know Chrome and Firefox can handle colors differently on single selects for example which introduced this bug:

As I said before, the browser decides how the options are rendered. We can't know for sure what the effects on all OS/browser combinations with (dark & light modes) will be now and in the future.

But with multiple selects, everything works. Color, background color, margin, padding and cursor all work.

Safari, Firefox, and Chrome on macOS.

Safari, Firefox, and Chrome on macOS.

Safari is known for doing things a bit differently. Like transparent black. But on Firefox, Chrome, Edge, Opera, and Vivaldi they all look right.


[privacy] Add generated privacy keys to GroupDataProvider.

Problem
In order to support future roll-out of privacy, v1.0 nodes need to minimally be able to parse messages that have privacy enabled.
Change overview
This PR adds support for deriving the privacy keys associated with a KeySet and adding them to the data store.
Testing
Added new coverage for all group credential derivations when an epoch key is added to a KeySet:

encryption key
privacy key
session id (group key hash)

[x]  Privacy nonce computation is not spec compliant. It also does not have a test.
Fixed

[ ]  GroupKeyContext::PrivacyEncrypt should be GroupKeyContext::PrivacyObfuscate
We discussed this here, and switched the names to PrivacyEncrypt to match Ch03 naming (Crypto_Privacy_Encrypt): Originally posted by @rcasallas-silabs in https://github.com/project-chip/connectedhomeip/pull/21555#discussion_r940391448

These tasks are left for a follow on PR (issue #21559):

[ ]  Need to explain why AES_CCM_encrypt/AES_CCM_decrypt is satisfactory to use when spec calls for AES_CTR
(Plan is to add formal AES_CTR crypto primitives.  If calling AES_CCM w/o tags is sufficient, then that will be used.)
[ ]  Missing unit tests for privacy obfuscation. This would have caught the above
Yes addition of CTR will come with unit tests.

These tasks are also left as a follow on PR:

[ ] Add privacy decoding to receive pipeline and packet parsing
[ ] Add privacy encrypt to transmit pipeline when P flag is enabled (always false for 1.0)
[ ] Add unit vectors for packet encode / decode with privacy


[SPARK-49932][CORE] Use tryWithResource release JsonUtils#toJsonString resources to avoid memory leaks

What changes were proposed in this pull request?
The pr aims to use tryWithResource release JsonUtils#toJsonString resources to avoid memory leaks.
Why are the changes needed?
Avoiding potential memory leaks.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.

GA passed. Merged into master for Spark 4.0. Thanks @panbingkun @MaxGekk @HyukjinKwon @yaooqinn

GA passed. Merged into master for Spark 4.0. Thanks @panbingkun @MaxGekk @HyukjinKwon @yaooqinn

Thanks all!


⚠ ClamAV has degraded performance

In b32f7af, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 455 ms

Resolved: ClamAV performance has improved in 7c8160a after 5 minutes.


[VMSS] az vmss create should build a NSG

Description
When creating a VMSS, I'd expect the instances to reside within a subnet protected by a network security group similar to az vm create.

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: source
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here: master
OS Version: What OS and version are you using?
Answer here: OS X
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

Supported now through --nsg


add check to stop diseases like this from rising up to the top

'regional odontodysplasia'
'segmental odontomaxillary dysplasia'
these should not be top level classes
is there a way to check for this and put up a warning?

What do you mean by "rising to the top"? Higher than "Disease or Disorder"? Can you show a screenshot?
A test like this would be easy to make. We could say: all classes must be under one of the three Mondo root classes.

I meant it is a child of 'disease or disorder'

I wonder if it's doing this because they're declared like that statically, or by some inference. Still a little new to this. I'm assuming these are mendelian diseases coming from OMIM? Do you think this should be an issue that I should add to OMIM repo, or is something likely to be fixed here in the mondo repo?

I think this has been addressed with our recent reclassification efforts. I don't know if we really need a check for this, this is something that @sabrinatoro and I can keep an eye on.
I vote to close this issue.
cc @sabrinatoro

@nicolevasilevsky
I agree that this has been addressed with the reclassification efforts and we can close this issue.
The issue occurs when we obsolete a class/parent term and the children do not have any other parent. The only way to avoid such terms appearing at the high-level classification is to check what happens to the children when obsoleting a term. In other words, it is the curator's responsibility.

Agreed, I will close.


Path Substitution Not Properly Escaped

Windows/DOS paths in the pathSubstitutions configuration attribute are not escaped before being sent to the debugger.  Thus on Windows, a typical path cannot be used as-is, but instead must be escaped again within the launch.json:
"pathSubstitutions": { "C:\\\\test1": "C:\\\\test2" }

Not only is it a nuisance to have to do this (or switch to POSIX style paths), but it is also problematic when attempting to use predefined variables (e.g., ${workspaceFolder}) in the substitution paths.  The predefined VSCode variables use the path format of the host OS, so become unusable in this context.

It sounds like you could open a PR to fix that, what do you think?

Fixed with #295 thanks to @brownts.


Bump detect-port-alt

This should include some error handling that would work around https://github.com/facebookincubator/create-react-app/issues/3690.
I haven't verified it works yet, but the last time I tried to do similar edits locally, and then inserted a throw in the same place the error was reported, detect-port said the ports were taken and jumped to a high port. I'm not sure why it didn't give me an error instead but this seems edge casey enough that I don't care strongly how it works as long as it doesn't crash.

my problem was similar, install firebase and when executing npm start, this error came out

react-scripts start

I had to reinstall the dependencies with

npm install
then
npm i npm

I went back to execute npm start and solved the problem


Fixed tool names snake_case

#16396
Fixed

golden_query
google_lens
memorize
merriam_webster
open_weather_map
pub_med
stack_exchange
generate_image
wikipedia

It makes sense to standardize but I don't see a point to make a PR this short. This doesn't fix anything the only thing causing issues was spaces in the tool names

@Lord-Haji, Thanks for review. So do I revert the changes?
I have validated the names, but I don't see any tool names with space.
Ideally, I thought standardizing it would make more sense to avoid future errors when someone is creating a tool while referring to this tool's code.

I believe duckduckgo and google search tools have spaces and need to be fixed. but we can also include the current changes, most tools have snake_cased names and it'd be nice to be consistent about that.

thanks @baskaryan, Sure I will fix that too.

thank you @jatinchawda1503!


latest

Probably needs an updated reference to AspNetCore.Debugging package if we decide to increment major version

Oops, didn't see this one. Fixed it myself a few days ago 😞


Incorrect Date Conversion in nodered, moment.js works fine.

From Home Assistant, I get the following data:
entity_id: "binary_sensor.garage_camera_motion"
last_changed: "2018-06-01T18:13:03.909192+00:00"
Then using this project, i am taking that last_changed value and converting to "dddd, MMMM Do YYYY, h:mm:ss a"  the result I get is Tuesday, June 19th 2018, 11:13:03 am.  Which is off by 18 days.  The time is correct as I have it converting from UTC to US/Pacific time.
If I take that exact time string and use https://codepen.io/widmoser/pen/NNOQEx?editors=1111 to test moment.js using the following, its correct.
const time = moment('2018-06-01T18:13:03.909192+00:00').format("dddd, MMMM Do YYYY, h:mm:ss a");
alert(time);
Am I doing something wrong using the plugin?

Well, it's definitely not a problem in the output (formatting) -- even if I use the default ISO-8601 formatting, the UTC "timestamp" returned is 2018-06-19T18:13:03.909Z
However, if I use plain JavaScript to parse that date string, it is correctly interpreted:
> new Date("2018-06-01T18:13:03.909192+00:00")
2018-06-01T18:13:03.909Z

So what is happening inside the moment node? Well, here's the relevant section of code:
  default:
        node.log(node.inTz.split('/')[0]);
        var prefOrder = {preferredOrder: {'/': 'DMY', '.': 'DMY', '-': 'YMD'} };
        if ( (node.locale.toLowerCase().replace('-','_') === 'en_US') || (node.inTz.split('/')[0] === 'America') ) {
          prefOrder = {preferredOrder: {'/': 'MDY', '.': 'DMY', '-': 'YMD'} };
        }
        inpFmt = parseFormat(inp, prefOrder);

So the next question is... what input format is being determined by the moment-parseformat library?
> var parseFormat = require('moment-parseformat');
> parseFormat("2018-06-01T18:13:03.909192+00:00"):
'YYYY-MM-DDTHH:mm:ss.SSSD2Z'

Interesting -- but also clearly wrong! So the six digits representing microseconds were interpreted as 3-digits (SSS), followed by the day of the month (D), followed by a literal number (2), followed by the UTC timezone (Z). Removing the extra 3 decimals of precision does fix the problem:
> parseFormat('2018-06-01T18:13:03.909+00:00')
'YYYY-MM-DDTHH:mm:ss.SSSZ'

So this is clearly a bug in the underlying dependent library, which according to package.json is version 2.2.1 -- let's see if the new version 3.0.0 from 11 days ago has the same issue:
C:\NODE\node_red>npm install moment-parseformat@3
+<EMAIL_ADDRESS>added 1 package and updated 1 package in 1.907s

C:\NODE\node_red>node
> var parseFormat = require('moment-parseformat')
> parseFormat('2018-06-01T18:13:03.909192+00:00')
'YYYY-MM-DDTHH:mm:ss.SSSD2Z'

Yep, no better -- time to open an issue against that library. As you are the one who found the bug, I'll leave that up to you. Good catch!
--Steve

Steve,
Thanks for that excellent diagnosis. I will get this issue created on the library.
--Brian

This issue is going to come up again as the Home Assistant/Node Red combo becomes more and more popular I think.
I have a relative time moment node converting my timestamps to "fromNow". Mostly they work, occasionally they are in the future, and sometimes they are way too far in the past. Some examples:
"2019-02-27T11:02:04.709227+00:00" --> "2019-02-27T11:02:52.887109+00:00"
These dates were considered "5 days" apart.
"2019-02-27T11:04:23.209098+00:00" --> "2019-02-27T11:05:40.271300+00:00"
This was "in a month".
"2019-02-27T11:03:06.609682+00:00" --> "2019-02-27T11:03:09.012704"
This was correctly interpreted as "a few seconds ago".
I will strip the precision from the timestamp and hopefully the issue will be resolved.


Visual studio cache issue

/.vs/ do not catch the visual studio cache folder but .vs/ do
Reasons for making this change:
TODO
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

/.vs/ do not catch the visual studio cache folder but .vs/ do

This is because a leading / forces the check to only ignore from the root folder. I suspect you have a nested solution and the .vs directory being generated in a nested directory.


[FEATURE] enable hillshade layer in storymap for each chapter

Feature Description
We need a feature to enable hillshade mode for each chapter in storymap

Feature Implementation
we also need another column to save the state of hillshade mode in database.
Feature Alternatives
No response
Feature Impact
No response
Feature Rationale
No response
Feature Considerations
No response
Feature Requirements
No response

I am thinking this can be implemented by adding new query param at style endpoint to enable hillshade in serverside other than adding new database field.


[ENH] - Improved checks on projectname during init stage

Feature description
My qhub projectname that I used when I ran qhub init included an underscore. This was the error that was generated when I went on to qhub deploy:
[terraform]: │ Error: "name" can only contain lowercase letters, numbers and hyphens
[terraform]: │
[terraform]: │   with module.kubernetes.google_container_cluster.main,
[terraform]: │   on modules/kubernetes/main.tf line 5, in resource "google_container_cluster" "main":
[terraform]: │    5:   name     = var.name
[terraform]: │
[terraform]: ╵
[terraform]: ╷
[terraform]: │ Error: "account_id" ("this_deployment-dev") doesn't match regexp "^[a-z](?:[-a-z0-9]{4,28}[a-z0-9])$"
[terraform]: │
[terraform]: │   with module.kubernetes.google_service_account.main,
[terraform]: │   on modules/kubernetes/service_account.tf line 2, in resource "google_service_account" "main":
[terraform]: │    2:   account_id   = var.name
[terraform]: │
[terraform]: ╵

the error comes from a subsequent step in the project (init vs deploy)
the error mentions name but the variable that I set was projectname

These things make it misleading for users to debug.
I recommend that the init stage have a check to ensure that it passes the required restrictions and provides reasonable feedback when it doesn't
Value and/or benefit
users who are not confused at failures.
Anything else?
No response

Related: https://github.com/Quansight/qhub/issues/1267

@iameskild  and @asmijafar20  this should be good to implement in the CLI work

Hi @trallard, this check has now be incorporated into the init command 🙌

This issue is a subset of the items that need to be validated during when initializing the qhub-config.yaml.
See this issue for more details:
https://github.com/Quansight/qhub/issues/1267

Completed as part of new Nebari CLI 🤘


spelling fixes

patch contains some spelling fixes ( just in comments ) as found by a bot ( http://www.misfix.org, https://github.com/ka7/misspell_fixer ). Any upcoming License changes (e.g. GPL2 to GPL3+) are hereby granted.

@ka7 thanks for your contribution!


[docs] Global at rule is called font-face

Fixes #15699

Can we merge this to the master branch

Since this is my first pull request, it is quite intimidating. But surely I'm learning and I'll try my best to further contribute to this project. :-)

Since this is my first pull request, it is quite intimidating. But surely I'm learning and I'll try my best to further contribute to this project. :-)

Everything was perfect so far. That's what maintainers are for. To get the bigger picture and point to affected parts.

@aditya1906 Thanks!

Thanks @eps1lon and @joshwooding. Looking forward to contribute further.


[Preprocess #2] Instructions for setting up Airflow

Closes https://github.com/opentargets/issues/issues/3102.

Note
This is ready for review, but please do not merge. The base branch is not main, but the previous PR in the series, Preprocess #1. This is done so that only changes which are related to this specific PR are displayed. I'll handle merging myself once this is approved.

Docs

Added comprehensive, reproducible instructions on how to install and set up Airflow.
Created a new “Development” section in the docs, which now contains:

Airflow
Contributing
Troubleshooting

Fixed the command to spin up the docs server.

Airflow

Removed .env and .docker-compose.yaml, which are best populated during each individual installation.
Made Dockerfile build less noisy.
Updated requirements.

There's an issue with issue-PR linking. I'll close this PR and reopen to fix it.


Update to latest Skia APIs

It seems that the current Skia port doesn't work anymore due to changes to Skia's API. These changes worked for me. Please review.

@dirkschulze You can merge this one too. Thanks for reviewing. 👍


CC Deployment is getting failed in a peer added in an existing hyperledger fabric network(v2.2.0) using baf

Describe the bug
I tried to add a new peer in the existing org in an existing network (Fabric v2.2.0) using baf. It was successful and the new peer has also joined the channel. But the chaincode deployment is throwing error in new peer. I am able to package the chaincode and install the chaincode, but the "approvemyorg" is throwing error like below,
Error: timed out waiting for txid on all peers
So, I did the approvemyorg step from the peer which was there from the initial network deployment. There the approval was successful. Then I used "peer lifecycle chaincode checkcommitreadiness" command to check the orgs those who have got approved in the new peer, it is showing the below result,
{
"approvals": {
"abcMSP": false,
"defMSP": false
}
}
But if I try the same command in an old peer, it says the right result,
{
"approvals": {
"abcMSP": true,
"defMSP": true
}
}
Also, the invoke or query in the new peer is throwing,
Error: endorsement failure during invoke. response: status:500 message:"make sure the chaincode fabcarv3 has been successfully defined on channel intainchannel and try again: chaincode fabcarv3 not found"
Error: endorsement failure during query. response: status:500 message:"make sure the chaincode fabcarv3 has been successfully defined on channel intainchannel and try again: chaincode fabcarv3 not found".
To Reproduce
Steps to reproduce the behavior:
Deploy an hyperledger fabric network (v2.2.0) using blockchain-automation-framework. Once the network deployment is completed, add a new peer using baf using the steps in the documentation - https://blockchain-automation-framework.readthedocs.io/en/develop/operations/adding_new_peer_fabric.html.  Once the new peer is added to an existing org and joined the channel, deploy the chaincode in the new peer.
Expected behavior
Chaincode is successfully deployed and invoke and query are working as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: Ubuntu
Version: 18.04

Additional context
Add any other context about the problem here.

i have the same issue.

Additional info, the following channel info is from old peer of the org,
bash-5.0# peer channel getinfo -c mychannel
2021-02-19 09:32:10.533 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Blockchain info: {"height":9,"currentBlockHash":"3JWXNwGt9rhGldFcUyBqjWizsOKRbQBKY3KNvBl6rA8=","previousBlockHash":"oIlDSVnCj4fOkozTjN2BDDLIs16RwooQy59qI1P9Eu4="}
The below result is from the new peer,
bash-5.0# peer channel getinfo -c mychannel
2021-02-19 09:40:59.093 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Blockchain info: {"height":1,"currentBlockHash":"3WnnD9/ZMu56urG8Mdzw4/VHvCZOkCssCf+AyyWATGs="}
This difference is the cause for the CC to not work in the new peer. I guess this info gives some more view on the issue.

Thanks for the finding @SoundaryaA3098 . This surely helps.


Entries not found

I can login and see doujins I've favorited, but cannot see any other doujin. I can look in my history and find doujins, but cannot read those. The home page and search function provide nothing, except for a pop-up at the bottom saying "No entries found." I've updated from 2.8.something to 2.9.1 and reinstalled, but only the site itself is showing me any doujins.

Same here

Happen to me when using cloudflare warp client. Using other vpn works

None of these answer anything and do we fix it or can we?

Unfortunately, we haven't found any alternatives other than webscraping their main site for data. We need a direct API for the app to use, which is currently unobtainable. many APIs similar to these are also down due to cloudflare but I am hearing some applications have a secret API access from the dev.

Change to some mirror site (xxx/io) ,same structure ,will it work?

Tachiyomi still works. Maybe you could take inspiration by looking at how they bypassed Cloudflare. I'm not 100% sure but maybe here there is something useful.

one way to fix entries not found simply for me all i do is log out check for updates if it has update it the login in back should work

This issue was fixed actually in the latest releases. It was a cloudflare ddos protection problem


proposal: Go 2:

¿Really Generics?
Don't get me wrong but.... i once stated
"As a reflection that I do... golang does not provide generics and this does not imply that we lack a tool, in fact with interfaces we already have all the genericity that we want... so the 'tool' to model exists... the issue is to get the hang of it!"
For me there was no need.
Okey, i guess to move on and try a new tool, but i don't know how much many time from now i start to see more messy code rather than simple (but i litttle longer perharps, and that open the ways to talk about the tradeoffs...).
Anyway!
Greetings to all and keep the good work.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


unable to download vgg_normalized.pth

I get message "File is in owner's thrash" from Google drive.

Thanks for your remind! Since we use the same pretrained model as AdaIN, you can download vgg_normalized.pth under this link: 'https://github.com/naoto0804/pytorch-AdaIN/releases/download/v0.0.0/vgg_normalised.pth' I have modified the link in README as well. Hope it helps you.


🌱 Use cached informers in scheduling controllers

Summary
Use cached informers in scheduling controllers.
Related issue(s)
Fixes #2900

/test e2e-shared

/lgtm
/approve

/lgtm


Update ocm, aap and keycloack versions

Plugins should be upgraded to a version that includes https://github.com/janus-idp/backstage-plugins/pull/827 to make sure that users can configure the scheduler in the app-config.yaml

We're missing the 3scale plugin in our dynamic-plugins directory since it was never statically installed into the showcase at any point in time.

There is anotehr fix for keycloack, ocm, and app that we need to pick for the showcase:
https://github.com/janus-idp/backstage-plugins/pull/945
https://github.com/janus-idp/backstage-plugins/pull/938


Expense - unexpected join button and double thread creation when deleting expense.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.17-4
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to [staging.new.expensify.com].
Create a new workspace by navigating to the workspace picker and clicking the plus button.
Navigate to the workspace chat.
In the compose box, click on the plus icon.
Select "submit expense."
Add an amount, then click "next."
Add a merchant name, then submit the expense.
Navigate to the expense detail page.
Click on the header and select "hold."
Write any reason and hold the expense.
Click on the header once again and delete the expense.

Expected Result:
When deleting an expense, no "join" button should appear, Clicking on the subtitle link after an expense deletion should not create an additional message thread; it should navigate back to the original thread without duplicating it.
Actual Result:
A "join" button appears when deleting an expense, which is not the expected behavior and Clicking on the subtitle link after deleting an expense creates a new message thread, resulting in double threads for the same deleted message.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/8bd9c50a-3014-403c-8ded-ec75178bdd38

View all open jobs on GitHub

We think this issue might be related to the #collect project.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Expense: Unexpected issue with join button and double thread creation while deleting expense.
What is the root cause of that problem?
For join button issue, after the deletion, the report type will be replaced from expense to standard chat type and it will skip this check.
What changes do you think we should make in order to solve the problem?
We should check for deleted parentReportAction to prevent anyone from joining it.
src/libs/ReportUtils.ts
canJoinChat
    if (ReportActionsUtils.isDeletedParentAction(parentReportAction)) {
        return false;
    }

For issue with duplicate thread, I think that's a BE issue, I can't reproduce it while offline.
What alternative solutions did you explore? (Optional)
N/A

Hey @akinwale - can you take a look at the proposal we received?

@wildan-m's proposal works here, but the duplicate thread issue is from the BE. We can go ahead if we want to fix only the issue with the join button in the frontend.
🎀👀🎀 C+ reviewed.

I'm no longer able to reproduce this, I think this has been fixed in the BE. @sakluger or @akinwale do you think you could verify and if so we can close out this issue.
https://github.com/user-attachments/assets/10100b56-cf42-4b2f-b8b7-81578c64f1ac

@srikarparsi it's reproducible in the latest staging
https://github.com/user-attachments/assets/ed868ae7-7085-4cbb-9025-c710b075c54d

I see what you're saying. I looked into this and I think it's entirely a BE issue. A duplicate thread should not be created when an expense that is on hold is deleted. That is also why we see the join button. I don't have time to look into this currently but @sakluger do you think you could help fit this into a wave and see if there's any volunteers. I can try to pick this back up the week after next week if no one's available.

I posted in #wave-collect to see if we can find any volunteers to help.

I'm also going to add another BZ member to manage the issue while I'm OOO through 8/30.

Another one for eyes from @robertjchen related to Held requests.

Agreed, this may be related to how DeleteMoneyRequest / DeleteReport handles the deletion of held items on the BE- I'm guessing it's not finding and moving the thread over (hence the Join button and the duplicate [deleted] item, one of which is a thread)

I'm back so I will take over management of this issue again.

Taking this one over

Thanks @robertjchen! Commenting for melvin.

Was able to reproduce the issue locally, looking in the backend.

Making some fixes elsewhere to the hold flow, will revisit after

Same, fixing hold flow elsewhere before revisiting this week

Looks like it's down to the way the chat thread is created on the held expense. We're creating a thread one-level down:
Normal Expense (deleted)

Held Expense (deleted)

Major BE fixes in progress/testing. A few issues were found and will need to be addressed together:

The transactions threads are not being created in the proper location (duplicate thread)
The transaction threads are not initialized properly as to set the notification preference (join button)
While debugging the above, discovered that the participants list was not being properly generated, so the proper Onyx updates were not going out (potentially related to the other other open issues).

So, after testing this in-depth, it appears that the issue is actually not hold specific- the same "duplicate thread" and "join button" issue exists for non-held reports with just comments on them:
https://github.com/user-attachments/assets/c48677d2-7d77-4f6e-accf-34977117ae70

Un-assigning my self to focus on actual hold-related issues. @sakluger could you please find another engineer to look into this? It's a bit of a corner case, so I made it a Weekly for now.
Notes for the next person taking this on:
I think we just need to set the notification preference of the chat thread to always and that should make the Join button disappear. That's what worked for me locally at least.

@robertjchen and I were chatting about this in thread here.
The bug report is a bit misconstrued, and it really just comes down to the delete expense report case that's converted to a chat report to preserve any comments on it in thread has a join button at the top of it if you visit it again. It's a pretty minor point, and doesn't prevent you from commenting on it or what not, so we're just going to close it out.
No duplicate expenses or messages or stuff like that is happening. 👍


EIP-6963 connectors are not announced becuase of Bitski wallet

Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Describe the bug
If you install Bitski wallet and get this view:

The other EIP-6963 connectors will not get announced unless you disable the Bitski wallet extension.

Link to Minimal Reproducible Example
https://github.com/magiziz/wagmi-eip6963-repro
Steps To Reproduce

Install Bitski wallet and have other wallet extensions installed
Refresh the page and you'll see no EIP-6963 connectors getting annoucned. It's probably because of this error:

What Wagmi package(s) are you using?
wagmi
Wagmi Version
2.10.7
Viem Version
2.16.3
TypeScript Version
5.5.2
Anything else?
No response

Looks like this is because Bitski decided to not follow EIP-6963 for some reason, using walletId instead of rdns. Show follow up with them!

Looks like Bitski is shutting down in three days so probably not worth even following up.


PickLists inside Components have missaligned popup menus

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
When creating a PickList inside a Component their popup menu is misaligned when the widget is not in the top left corner.

I created a small repository to reproduce the error:
https://github.com/DoomDuck/iced_picklist_in_component
What is the expected behavior?
I expect the popup to be aligned with the button.
Version
crates.io release
Operating System
Linux
Do you have any log output?
No

I believe this is fixed in 25006b9
You can pull the fixed version of iced by replacing the dependency in your Cargo.toml with:
iced = { git = "https://github.com/iced-rs/iced.git", rev = "25006b9c6f2ae909d86871d3a13631d518c07158", features = ["lazy"] }

or to pull the latest version:
iced = { git = "https://github.com/iced-rs/iced.git", rev = "f5c6fa7338713a0430dcdfc5bd53f72103144f22", features = ["lazy"] }

and then running
cargo update

Thank you ! This has indeed been fixed !
The suggested tags do fix the problem thank you :+1:


How to wait for 2 actions and join their results in redux-saga

Hi,
in my application I'd like to define a saga that will handle either LEFT_CHANGED or RIGHT_CHANGED actions and continue with new action SOURCES_CHANGED with payload consisting of payloads of the two aforementioned actions.
export function* watchLeftRightChanged() {
  const left = null;
  const right = null;
  while (true) {
    const result = yield take(['LEFT_CHANGED', 'RIGHT_CHANGED'])
    switch (result.type) {
      case 'LEFT_CHANGED':
        yield put({ type: 'SOURCES_CHANGED', result, right })
        continue;
      case 'RIGHT_CHANGED':
        yield put({ type: 'SOURCES_CHANGED', left, result })
        continue
    }
  }
}

The problem is that left and right properties of the action are null when SOURCES_CHANGED action is emitted and their value is not kept (I believe dut to the nature of the iterator).
Thanks for help,
Karel

@kfrajtak you have to either compute state inside your saga (so you can't use const because you need to reassign variables overtime), OR reuse existing Redux store state if you have reducers that compute state
For example:
export function* watchLeftRightChanged() {
  let right;
  let left;
  while (true) {
    const result = yield take(['LEFT_CHANGED', 'RIGHT_CHANGED'])
    switch (result.type) {
      case 'LEFT_CHANGED': left = result.payload; break;
      case 'RIGHT_CHANGED': right = result.payload; break;
    }
    yield put({ type: 'SOURCES_CHANGED', left, right })
  }
}

OR
export function* watchLeftRightChanged() {
  while (true) {
    const result = yield take(['LEFT_CHANGED', 'RIGHT_CHANGED'])
    const left = select(state => state.leftState)
    const right = select(state => state.rightState)
    yield put({ type: 'SOURCES_CHANGED', left, right })
  }
}

Thanks, @slorber, that worked like a charm!

@kfrajtak I had the same need and wrote this lib: redux-saga-combine-latest
It takes @slorber 's first approach of aggregating actions in local state, and only fires the handler when all action types have come in. e.g.
combineLatest(['type1', 'type2'], handleActions)

As soon as an action of type type1 and type2 have been received, it fires the handleActions saga, passing an array of actions. As new actions of each type come in, it fires again with the latest action of each type.

Thanks, @jhewlett, I'll have a look at your lib!


Crashes when used with zsh autosuggestions

This seems to be a working work-around, which may hint at the issue

if ! (( ${+functions[_zsh_highlight]} )); then
    . "$ZSH_CUSTOM/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh"
    . "$ZSH_CUSTOM/plugins/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh"
fi

Known issue, already fixed in z-asug, see #353.


Add support for custom pom.xml names for the child maven modules

Extended on the multi-module review support, allowing for the custom pom.xml names be used for the pom-s in child modules. With that PR they would be able to have various names, with the only limitation being that they must end with .xml.
This PR should, hopefully, address a part of the https://github.com/dependabot/dependabot-core/issues/4425 issue.

Fixed the codestyle issues, now should be all green

Hopefully now that CI has been fixed - everything will pass 😃

This sounds like an improvement over what we have, and it seems we're already special casing parent_pom.xml and extensions.xml anyways.
Can you elaborate a bit on the exceptions? The idea is that those two will never be top-level pom's but only included from other pom's?(Sorry if I use wrong terminology, I know nothing about maven). Could there be other exceptions (say, parent-pom.xml)? How would we handle those now, and how would we handle them after this PR?

Hi David, for sure.
With extensions.xml it is easy. Extensions are used to affect, in some way, the artifact/app build process or how maven itself work. There are core extensions which are loaded early and build extensions which are loaded late (https://maven.apache.org/guides/mini/guide-using-extensions.html#loading-extensions):

Core extensions: defined in extensions.xml file, stored under the ${maven.projectBasedir}/.mvn/ directory (as per the convention), allows to define relevant such extensions for your project. Their dependencies are currently gathered within the separate extensionfiles property, and then checked separately from the pom ones.
Build-time extensions: defined in pom.xml, mostly in the build->extensions path, or in plugins. Both places are already checked (they are included in DEPENDENCY_SELECTOR)

Now compared to that, the paths that we add within the modules part of the pom.xml file define the paths to the child pom modules with their own dependencies. There is also a convention there (https://maven.apache.org/pom.html#aggregation-or-multi-module), that if the path for a module is a directory - it will lookup the pom.xml file inside. But if you specify a path to the file - it will assume that within that file you have your pom structure defined, no matter what name it has (and that is the part added within this PR). Which, in reality, means, that you could, theoretically, specify that you child module is named my-child-module/extension.xml, and this would even properly work with maven... but would bring a lot of confusion overall, as this kind-of mixes two different concepts, and also would be harder to properly support within the dependabot architecture (i.e. Dependabot::Maven::FileFetcher.required_files_in should check, that we have some proper pom files inside, not only extensions files), thus they have been excluded from the places where we expect pom files only.
Switching to the pom_parent.xml file - it is not a standard name in maven and is not mentioned anywhere in the documentation there. From what i get from the code (might also be wrong) is the following:

pom_parent.xml has been used just as a "constant" to "label" a local pom file which has been retrieved as a parent of the base POM file (and then recursively repeated for each fetched parent)
in order for the parent pom to be retrieved by the dependabot - it has to be named pom.xml as well, so no other names are really supported there, even the pom_parent.xml 😃
these files, for the reasons unknown to me, have been assumed to be "read-only" for dependabot purposes, which results in the following:

these files are not checked for the vulnerable dependencies, consequently should not be updated by dependabot in any way
but the information from these files is still used to populate the repositories from which to fetch the dependencies, as well as to populate the available properties files (from which a dependency version is often taken)

So now getting to the question on what changes after the PR for those two cases the answer is simple - nothing 😃 Just to sum it up (as my text above is a bit too long):

Core extensions have already been properly handled and nothing to be changed here
Build-time extensions are properly handled as well, nothing changes here
Parent poms, if they are local poms, and not an artefact from some repo are not being updated on purpose (even though i don't know the reasoning behind this decision), and this also stays as is
Thus the only thing that is changing with this PR is the way child pom files are handled, in order to allow having there wider variety of supported pom file names based on the maven specification

Thanks for the explanation @soulus13, very helpful!
I had a closer look here. Made some bare testing and this seems to work as expected. Also the implementation looks good 🎉.
I think this PR will fix https://github.com/dependabot/dependabot-core/issues/5276 too?
I did notice one difference, on a repo using parent_pom.xml.
With main branch:
$ bin/dry-run.rb maven filip26/titanium-json-ld
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/filip26/titanium-json-ld/
=> parsing dependency files
=> updating 1 dependencies: com.apicatalog:titanium

=== com.apicatalog:titanium (1.3.2-SNAPSHOT)
 => checking for updates 1/1
🌍 --> GET https://repo.maven.apache.org/maven2/com/apicatalog/titanium/1.3.2-SNAPSHOT/maven-metadata.xml
🌍 <-- 404 https://repo.maven.apache.org:443/maven2/com/apicatalog/titanium/1.3.2-SNAPSHOT/maven-metadata.xml
🌍 --> GET https://repo.maven.apache.org/maven2/com/apicatalog/titanium/maven-metadata.xml
🌍 <-- 404 https://repo.maven.apache.org:443/maven2/com/apicatalog/titanium/maven-metadata.xml
 => latest available version is
 => latest allowed version is 1.3.2-SNAPSHOT
 => requirements to unlock: update_not_possible
 => requirements update strategy:
    (no update possible 🙅♀)
🌍 Total requests made: '2'

With this PR:
$ bin/dry-run.rb maven filip26/titanium-json-ld
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/filip26/titanium-json-ld/
=> parsing dependency files
=> updating 0 dependencies:
🌍 Total requests made: '0'

The new behavior seems better since we'll never find any updates for locally pulled dependencies anyways.
I also looked into why we're using the pom_parent.xml trick, and found the PR but not much of an explanation: https://github.com/dependabot/dependabot-core/pull/356. However, it seems like the current implementation relies on this particular name to be excluded and it would be a non trivial refactoring to get rid of it even if we deemed it as not necessary.
I guess we could rename the "magic file" to something less common like pom_parent_just_a_trick_to_properly_parse_parent_poms_recursively.xml 😆. Anyways, not for this PR (or for any PR, probably, but just an idea that came to mind).
Do you have a particular public repository to run more tests against this PR? It looks mostly ready but I'd like it to give it another pass.

Now this comment that you left, @deivid-rodriguez, has really made me think a lot on how that works again, and study a bit deeper the overs logic there, and now i'm ready to discuss that further on!

I think this PR will fix #5276 too?
Yes and no, at the moment 😃 Will get to this part down the line

The new behavior seems better since we'll never find any updates for locally pulled dependencies anyways.
Correct, and this is due to now properly searching for the parent files as well, which i have totally forgotten since the time i made it. So my statement in the comment above was a bit incorrect - this PR indeed adds a logic to allow both alternative names for the child modules and for the parent ones, as i recall that fixing just one part seemed not right to me.

I also looked into why we're using the pom_parent.xml trick, and found the PR but not much of an explanation: #356. However, it seems like the current implementation relies on this particular name to be excluded and it would be a non trivial refactoring to get rid of it even if we deemed it as not necessary.
And that is the main question left, if we still need this exclude. I would really assume that for any pom.xml file we fetch, no matter parent it is or not - we generally have to check its dependencies and bump them, if possible.
But now we come to a fun part 😃 Even though i have tried to preserve the non-update-parent logic (as i did not know if that was for a purpose)  - it now allows parent files to slip through it, in case they have custom names and are not named pom_parent.xml. I have updated my test repo with some additional pom-s to demonstrate it, so feel free to dry run:
bin/dry-run.rb maven soulus13/dependabot-maven-test
There you will see that 2 out of 4 parent poms i have created there have been bumped, and 2 have not been.

So now it would be great if you could, somehow, dig up why were the parent poms blocked from the dependency checker in the first place, if that is possible, for sure! And anyway, depending on what you think would be the best option - i can either go ahead and completely remove the parent pom exclusion from dependency checking (and only then would the #5276 be fully addressed), or i can adjust a bit the logic within Dependabot::Maven::FileFetcher#recursively_fetch_relative_path_parents to properly substitute the parent_pom.name with our "magic file" name, to fall back to the previous behavior for parent poms. My preference would be, for sure, to remove all that "magic" from the code and keep parent poms updated as well, as requested in #5276

Do you have a particular public repository to run more tests against this PR? It looks mostly ready but I'd like it to give it another pass.
I have been mostly playing with my custom repo above, where i have added all the scenarios i could think of, but here is another real-life sample i have found with custom submodule names: https://github.com/EsotericSoftware/kryo. And for the parent custom module name - https://github.com/filip26/titanium-json-ld is still good enough. Especially if you do locally bulk replace of pom_parent.xml to some other magic name, just in case.

That sounds like a good plan. Let me first remove the pom_parent.xml magic and start supporting the first half of this. We'll support pom.xml and pom_parent.xml after this first step.
Then you can rebase this PR and add support for generic names.

That sounds like a good plan. Let me first remove the pom_parent.xml magic and start supporting the first half of this. We'll support pom.xml and pom_parent.xml after this first step.
Then you can rebase this PR and add support for generic names.

Sounds perfect for me, @deivid-rodriguez! If you would like any support from me in this - always willing to contribute into these improvements with whatever i can 😃

Thanks! I tried to patch this locally and it seems fairly simple. I'll open a PR.
I have one more question though. We have learnt so far, and this PR adds support for updating:

Directly linked child poms with arbitrary names via <module>custom/childpom.xml</module>.
Directly linked parent moms with arbitrary names via <parent><relativePath>custom/parentpom.xml</relativePath>.

Does that maven support a "root pom" (not linked from any other file) not named pom.xml. If not, does that mean we still need a file named pom.xml to have a sane maven setup?

Thanks! I tried to patch this locally and it seems fairly simple. I'll open a PR.
I have one more question though. We have learnt so far, and this PR adds support for updating:
* Directly linked child poms with arbitrary names via `<module>custom/childpom.xml</module>`.

* Directly linked parent poms with arbitrary names via `<parent><relativePath>custom/parentpom.xml</relativePath>`.

Does that maven support a "root pom" (not linked from any other file) not named pom.xml. If not, does that mean we still need a file named pom.xml to have a sane maven setup?

In maven, when running it - you can provide any pom file name as an input (i.e. run it like that mvn -f <path>/mycustomfile.xml 😃 Thus the root pom does not have to be named pom.xml. And adding the ability to have a custom-named root pom was exactly the request in the https://github.com/dependabot/dependabot-core/issues/4425.
Unfortunately, in the current dependabot implementation i could not see any easy approach with a reasonable amount of effort to make it customizable, as this name(s) then will have to be provided as a part of dependabot yaml configuration https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#maven-repository, so that users can specify either one or an array of file names with or without paths as the entrance points to their maven project(s) within the repo, so that we know what to look for. And after that - refactor the code to not require pom.xml file to be present in all the places.
Thus to sum up, i would, indeed, agree, that within the existing limitations of the current dependabot checker implementation for maven - repo must have a file named pom.xml to be treated as a valid maven project.

Great, I created #6491 as the first step, what do you think?

Great, I created #6491 as the first step, what do you think?

Have checked it - looks good to me! And then after rebase i will get rid of all the leftover magic names, and will, maybe, look a bit in the specks, to see if i can add any additional valuable checks for dependency checking of parent poms, as that surely would not hurt :)

Rebased the branch on the updated main, and will follow-up with some extra tests within a day or two, to cover how the parent validation now works after the magic has been removed 😃

Added extra tests for the parent pom updates (including parent pom-s with custom name), so should be ready for the final review, @deivid-rodriguez!

Guess it is good to merge now? :)

Yes, I'll merge this soon :)

Quick question since I don't know much about the maven ecosystem and also haven't deep-dived in this code...
Since this PR will now treat any file that ends in .xml as a potential manifest file, what will happen to other .xml files in these paths that are not POM files? I didn't see any new test cases covering this...
I suspect we previously didn't worry about them because pom.xml indicates what it's about... Does the code do any sanity checking of the file contents to see if it looks like a manifest file? And if contents turn out to not be a manifest file, will it get silently ignored, or proceed to a point in the code where it blows up with an "unparsable manifest" exception?

Hi @jeffwidman, luckily it does not get that broad with this PR 😃 Summing up the below lines - nothing changes at all with regards to the "rogue" .xml files, compared to the current implementation.
What we have now is that the entry point must be a valid pom.xml file, which can have inside both path to its parent (must be a 'pom.xml' named file) and any number of "child" modules' paths (which also must be named pom.xml). And surely that can be repeated for its children recursively. And these are the only xml files that are validated by Dependabot.
Now what changes within this PR - is just adding the support for custom parent/child names, as per the maven specification, where pom.xml name is the default convention (you may even omit such name and just specify the path - that would suffice), yet there are no restrictions on the naming of parent/children modules.
This, basically, means that these .xml files still have to be listed within the valid "root" pom.xml file as either parent or children modules. So it is really unlikely that in any direction we will meet non-pom.xml file, and in case we do - this would mean that the maven project in this repo would hardly work as well.
So both with this PR and before it could crash in the same way in different places in case of the bad file structure:
If "root" pom.xml is not a valid XML or not a valid pom.xml: could crash in Dependabot::Maven::FileFetcher#fetch_files (when parsing the XML itself or fetching the child modules or parent), Dependabot::Maven::FileParser#pomfile_dependencies (mostly raise DependencyFileNotEvaluatable exception) and i guess could crash somewhere else as well.
If its parent or child modules are not valid XML-s or not valid pom.xml-s: as the logic for them is more-or-less the same with the "root" one, and they are processed close to each other - would crush in the same places and in the same way.
And i guess in case of malformed XML - the whole process would just blow up anyway, or at least i don't see any handling for that on the module level here 😃


Mutation Namespaces

Haven't seen this possibility implemented in Strawberry, nor have I found any existing issues.
The idea of mutation namespaces is basically to make a possibility for this mutation:
mutation {
   likeArticle(id: 15) {
       id
       name
    }
}

To be designed like this:
mutation {
    article {
        like(id: 15) {
            id
            name
        }
    }
}

I have tried to implement this by making types inside mutation, but it didn't work. Maybe I have done something wrong or this is not a part of Strawberry?
Also, here is the link with more info about it

hi @LeaveMyYard this might work in Strawberry, but I have never tried :)
usually nested mutations are discouraged due to how the execution is handled, from the spec:  https://spec.graphql.org/June2018/#sec-Mutation

It is expected that the top level fields in a mutation operation perform side‐effects on the underlying data system. Serial execution of the provided mutations ensures against race conditions during these side‐effects.

relevant: https://discord.com/channels/625400653321076807/631489012632125440/908666876089995284

I have tried to implement this like present below and this code is work under the latest version of strawberry.
@strawberry.type
class Query:
    @strawberry.field
    def hello_world(self) -> str:
        return f"Hello, world!"

@strawberry.type
class MyCollection:
    @strawberry.field
    def action(self, name: str) -> str:
        return f"Hello, {name}"

@strawberry.type
class Mutation:
    @strawberry.field
    def my_collection(self) -> MyCollection:
        return MyCollection()

schema = strawberry.federation.Schema(
    query=Query,
    mutation=Mutation,
)

I'm going to close this issue since there's a way to do this, even if it is not recommended 😊


Clear Cuda Cache

Goal:
I am running alphafold, And I want to clear all cuda memory after model inference. Then I want to find a something like torch.cuda.empty_cache()
Check for duplicate requests:
I search the doc and issue and discuss, I found jax.clear_backend() , (BTW, this method is not in the doc), I Tried to call jax.clear_backends() and gc.collect() after prediction. But jax still occupied memory as it running.

Notice that JAX will preallocate 90% of currently-available GPU memory when the first JAX operation is run. JAX will then sub-allocates from it. See https://jax.readthedocs.io/en/latest/gpu_memory_allocation.html
When you say "jax still occupied memory as it running", maybe that's just the preallocation? To verify this, maybe try setting XLA_PYTHON_CLIENT_PREALLOCATE=false if you don't want JAX to preallocate?

Notice that JAX will preallocate 90% of currently-available GPU memory when the first JAX operation is run. JAX will then sub-allocates from it. See https://jax.readthedocs.io/en/latest/gpu_memory_allocation.html
When you say "jax still occupied memory as it running", maybe that's just the preallocation?

im sure it's not preallocated. i set this env .
process allocate 17g/total 24g GPU memory on 3090 till this process stop.
im developing a inference server. and i want to release all cuda memory  after  prediction .

Can you print jax.devices()[0].client.live_buffers() before and after jax.clear_backend() and see if it made a difference?
One big hammer is [x.delete() for x in jax.devices()[0].client.live_buffers()]

What about [x.delete() for x in jax.devices()[0].client.live_buffers()]? If you know for sure you are done with existing buffers, and won't use them again, the big hammer is something you can use.

Hi, I know it's been a while, but is there any solution to this problem? My GPU memory is not clearing events when there are no live buffers. Once a code fails due to OOM, I have no option but to restart the code because the memory is never released. That's true even if I restart the backends.

Would be interested in a solution for this as well (i've tried x.delete...) - any suggestions @zhangqiaorjc? Thank you!


Enable webchat contact method on Tax Credits page

This pull request enables the HMRC webchat contact method on the Tax Credits contact page.
This will need to be deployed alongside a change in static to disable the original webchat implementation on this page (https://github.com/alphagov/static/pull/829).

This PR is similar to https://github.com/alphagov/contacts-frontend/pull/52, so I'm going to merge it.


Add Metadata field "visualization default" for annotations

This is required to set default annotations to load for neuroglancer annotations.

@uermel In the case where an annotation has multiple shapes, should all of them be considered curator-recommended or visualization-default? Or would we want that to apply to a specific shape?

They should be false by default. We shouldn't recommend entries by default and also only show annotations when selected.

It would be better to apply to a specific shape type (if that's possible).

Yes, we can do that. :)

Blocked by https://github.com/chanzuckerberg/cryoet-data-portal/issues/323

@manasaV3  See here: https://github.com/chanzuckerberg/cryoet-data-portal-backend/pull/9#issuecomment-1936429165


How to continue training a model?

Hi.
I am training a model using CoLab. I reached 40 Epochs until CoLab disconnected, and I would like to use the last best model (which was saved) to continue training. I have looked but can't find advice for how to do this, but it would be really useful, especially for those of us using CoLab rather than a machine with a GPU.
Is this possible? If so, what would I need to load?
Thanks
David

I just pushed a fix for loading models, so this should now work with the latest master branch (which should be installed by default when using colab). There are two things you need to do. First, make sure optimizer=True for the ModelCheckpoint callback. Saving and loading the model with the optimizer intact will take longer, but you need this information to resume training.
E.g.:
model_checkpoint = ModelCheckpoint(
    HOME + "/deepposekit-data/datasets/fly/best_model_densenet.h5",
    monitor="val_loss",
    verbose=1,
    save_best_only=True,
    optimizer=True,
)

Second, when loading the model with load_model make sure to pass the same datapath and augmenter arguments from when you defined your TrainingGenerator. E.g.:
from deepposekit.models import load_model

model = load_model(
    HOME + "/deepposekit-data/datasets/fly/best_model_densenet.h5",
    datapath=annotations[0],
    augmenter=augmenter
)

Depending on the complexity of the model it may take awhile to load with the optimizer. You should then be able to resume training with model.fit, but let me know if you run into trouble.

I'll close this for now. Reopen it if you need more help.


Correct the size of downsampledFrame

Both frameWidth and frameHeight should be considered when determining the size of downsampledFrame.
The previous code only used frameWidth, potentially causing an illegal memory access.

@andrewharp Hi Andrew, could you please spare some time and check if my modification is correct?

Hi @gbaned @andrewharp,
I submitted this patch because the previous code makes an invalid memory access in my application based on the TensorFlow tracker. I found that the problem was due to wrong size allocation of buffer in this file of TesnsorFlow. The previous code calculates the size of buffer using frameWidth * frameWidth, but it should be frameWidth * frameHeight. After changing according to the submitted patches, all illegal memory access issues were resolved even when I used various video resolutions. Therefore, please check my patch again.


CANCEL VARIABLE/NOERROR

Reported by andrew wittenberg on 14 Aug 2014 17:17 UTC
It'd be nice to be able to cancel a list of variables, without having to worry if some of them weren't defined.  For example, in a script that may have defined some variables inside of IF..ENDIF blocks, it'd be handy at the end to have a big cleanup command that just lists all variables defined in the script, without having to test for the existence of each one.
In other words, often I'd like the following not to issue an error:
 	NOAA/PMEL TMAP
 	FERRET v6.923 (beta)
 	Linux 2.6.32-431.20.3.el6.x86_64 64-bit - 07/31/14
 	14-Aug-14 13:13

yes? let a = 1
yes? can var b a
 **ERROR: variable unknown or not in data set: B
yes? sho var
 Created by DEFINE VARIABLE:
 >>> Definitions that replace any file variable of same name:
     A = 1

Note how A is still defined, since CANCEL bailed out as soon as it saw the nonexistent variable.
So I'd suggest adding:
CANCEL VARIABLE/NOERROR

which would step through each variable in the list, and cancel it if it's defined.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2192

Comment by ansley.b.manke on 29 May 2015 01:00 UTC
I wonder if CANCEL should issue NOTES for things not  set or defined, instead of ERRORS.  In addition to the example with variables, it seems canceling things that aren't defined doesn't necessarily rise to the level of an ERROR.
yes? use etopo20
yes? cancel data 1,2
 **ERROR: unknown data set: 2

Comment by steven.c.hankin on 29 May 2015 17:30 UTC
Maybe
CANCEL/CONTINUE   ! or /IGNORE ... to signify continuation following error
as a solution?

Comment by ansley.b.manke on 3 Jun 2015 23:26 UTC
I've implemented CANCEL VAR/NOERROR as suggested.  We already have CANCEL DATA/NOERROR, so that fits right in.


fixed indentation and homepage link bug

when you merge this ti develop please also merge to master

LGTM. Mergin’.


UGameplayStatics class found

Hello,
While testing out UEPython, I noticed I cant load the UGameplayStatics class.
When I do:
gs = ue.load_class('UGameplayStatics')

I get an exception saying it couldn't find the class (the class exists, tho).
Exception: unable to find class UGameplayStatics

Hi, you have to use the Blueprint naming scheme, so just remove the 'U' prefix:
ue.load_class('GameplayStatics')
or better
from unreal_engine.classes import GameplayStatics

Neither seems to work...
Exception: unable to find class GameplayStatistics

Actually, strangely enough, importind directly worked on my mac (I remember it not working on windows, tho I might be wrong here), but the find_class still does not work.


table cant resolve text overflow css

https://www.w3schools.com/cssref/css3_pr_text-overflow.asp
in buefy, it's not resolved in some situation like above link

Did you set max-width on your td ?
And please check this article


chore: add tslib dependency

What I did

add tslib dependency

:facepalm: I wrote it but forgot to stage the file


Icarus Adventure System - Freude schöner Götterfunken

Sheet
Name: Freude schöner Götterfunken
System: Icarus Adventure System
Changes / Comments
First release of the official community sheet.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[Yes] Does the pull request title have the sheet name(s)? Include each sheet name.
[ No] Is this a bug fix?
[ Yes] Does this add functional enhancements (new features or extending existing features) ?
[ Yes] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ No attributes removed] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ Yes] If this is a new sheet, did you follow Building Character Sheets standards ?

Character Sheet Info Roll20 Internal Use only.


Create CHANGELOG.md

This is really helpful for when someone updates dependencies and something breaks.

+1
Changelog is a must IMO.

Either this or you could use semantic-release by @boennemann which will create the changelog for you on the github releases page.

Hey, with the last release I added a changelog to the GitHub releases. We do this with most other webpack repo's too, so this seemed the most consistent to me. We'll try to keep that up-to-date!


CORE-33885 add beforeSend hook to network config

Description
The spec for this feature is very thin.  This PR is a starting point for discussion on how this feature should be implemented.  I'm starting here with the most simple and most broadly applicable implementation.  The user can add a beforeSend function to the configure command.  This function will be called just before the network makes a request to Konductor.  The beforeSend function has one parameter which is the payload that will be passed.  The returned object will be the actual payload that gets sent to Konductor.  Optionally, the beforeSend function can return a promise that resolves to the actual payload.
beforeSend hook implemented in the network component (in this PR)
Pros

User is able to edit the entire payload.
Simple for a user to understand how the passed in JSON maps to the new payload.
This hook will be called for all network ops even idSyncs.

Cons

User can mess up the payload to the point where Konductor rejects it
Can be difficult to use if only a part of the payload needs to be modified
If Konductor changes its expected format and Alloy releases a new version, customers' beforeSend hooks would need to be modified.

Other ideas:

Provide a hook for just the event object
Provide a hook for just the automatically collected values (i.e. the xdm part of the event before it is merged with the xdm part of the user's event)
Provide all of these hooks

Related Issue
https://jira.corp.adobe.com/browse/CORE-33885
Motivation and Context

We want the user to be able to change the data that is automatically collected in Alloy.
We want the user to be able to modify the sent data in one place.

Types of changes

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

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All tests pass and I've made any necessary test changes.
[ ] I have run the Sandbox successfully.

Thanks for writing this up and for the good description. My take is we should wait to hear the use cases before implementing this. I think use cases will provide some important insight into how it's built and I would hate to maintain something that's unnecessary. Some related thoughts:

Once https://github.com/adobe/alloy/pull/186 is merged, customers will be able to overwrite, add to, and delete (by setting values to undefined) the auto-collected data without a beforeSend option. This ability only applies to auto-collected data that gets placed on the event's xdm object, however (in other words, they wouldn't be able modify the identityMap data because that sits at the payload level instead of the event level), so there might still be a need for something like beforeSend.
It might be a bit difficult to do something useful with the payload if beforeSend were called for event data and ID syncs and potentially other types of requests. The plan is that ID syncs will soon be using a different endpoint with a different payload structure. If I, as a customer, wanted to modify event data on every request, I would probably need to add code in my onBeforeSend function to basically duck-type-check the payload to determine if it's related to events or if it's related ID syncs or something else.

I don't know that the approach in this PR is the wrong thing, and I think what you've proposed in your "other ideas" section could also be valid approaches, but I don't think we have the right information to make a good decision.

The more I think about this the more I worry that it could come back to bit us. We will have breaking changes to Konductor in the future. At least for the next year or so as we go through the ramp in Adoption.
The biggest fear is that customers implement some logic that only fires on certain requests then they upgrade the library or we upgrade Konductor and only parts of their implementation fail. Those types of errors are extremely difficult to track down.
I also don't want them to have to become experts on the entire structure of the request. Rather I would like to let them use an interface that looks more like what they use with Event
{
  "viewStart":True,
  "data":{blah},
}

My preference would be two fold. 1- Allow customers to modify the event before it is sent out but before it is merged (I don't want them editing the raw request). 2- In that hook don't provide the raw request but provide the customer variables (e.g. view start, data, xdm, etc) and the auto collected stuff to modify.


CodeQL Analyze GitHub Action fails with Connection timed out for https://repo.maven.apache.org

Both #704 and #707 "consistently" passed the "normal" build on Linux and (new) Windows, but the build of this CodeQL Analyze GitHub Action fails, like this:
Error: 4-17 17:12:52] [autobuild] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project mariaDB4j-core: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: Plugin org.apache.maven.plugins:maven-surefire-plugin:2.12.4 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-project:jar:2.0.9, org.apache.maven:maven-settings:jar:2.0.9: Could not transfer artifact org.apache.maven:maven-project:jar:2.0.9 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.0.9/maven-project-2.0.9.jar: Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] failed: Connection timed out -> [Help 1]
  [2023-04-17 17:12:52] [autobuild] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project mariaDB4j-core: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: Plugin org.apache.maven.plugins:maven-surefire-plugin:2.12.4 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-project:jar:2.0.9, org.apache.maven:maven-settings:jar:2.0.9: Could not transfer artifact org.apache.maven:maven-project:jar:2.0.9 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.0.9/maven-project-2.0.9.jar

I am curious to see if the "dependabot rebase" updated branches of #704 and #707, after a 2h dinner break, now pass, or still fail (build currently running).
If we cannot fix this, I may have to drop the CodeQL Analyze GitHub Action (which seems a shame).
I wonder (but doubt) if #695 would somehow help to avoid this...

I am curious to see if the "dependabot rebase" updated branches of https://github.com/vorburger/MariaDB4j/pull/704 and https://github.com/vorburger/MariaDB4j/pull/707, after a 2h dinner break, now pass, or still fail (build currently running).

Build passed green on both, so this was probably just due to some flaky infrastructure issue; closing!


[ci] Move custom actions to libra/actions repo

This moves all the custom actions aside from land-blocking to the libra/actions repo. This gets rid of all the generated javascript from libra/libra.

/land

@metajack :exclamation: This PR is still missing approvals, unable to queue for landing

@metajack When someone "requests changes" you either have to dismiss their review or have them coming back and approve it

@rexhoffman Changes waiting for your approval :)

/land

@rexhoffman :exclamation: This PR is still missing approvals, unable to queue for landing

Well dismiss wasn't good enough :D

/land

:exclamation: Land has been canceled due to this PR being updated with new commits. Please issue another Land command if you want to requeue this PR.

Missed one action, and remembered that checkout isn't needed anymore since the actions don't live in this repo.
/land


[BUG]: Multi-selection in one facet yields unexpected results

Describe the bug
Multi-selection in one facets shows no results even in cases where there should be some.
To Reproduce
Steps to reproduce the behavior:

Search for 'covid'
Click on github facet first repo
See screenshot: 438 results, and of those, 16 also have the next repo...
Click on the second repo: instead of showing the 16, it shows nothing.

Expected behavior
From World Modelers: selecting multiple members from one facet should do an 'OR'. Selecting across facets should do an 'AND'. Could also check with @chris-dickson what should be expected based on what was done for TellFinder.

That's correct @pascaleproulx.  For example, selecting two publication years and the first github repo should result in the query:
 ( year:2002 || year:2001 ) && (github:CSSEGISandData/COVID-19)
The complications arise when you have to decide what to show in each facet. Because we immediately requery upon clicking a facet, it's desireable to not show values that could lead to zero results when combined. For example, upon filtering to the year 2022 we should only show values in other facet groups that have values in the year 2022, otherwise filtering further would lead to zero results.  But what should be displayed in the year facet in this case? If we show the remaining possible year values it leads to a very non-intuitive situation when display the subcounts (eg/ n / total) where in order to get values from another year the user must click on a facet value that says 0.


Shinyproxy Produces a Warning when Starting if Passing in --spring.config.location via CLI

eu/openanalytics/containerproxy/ContainerProxyApplication.java:127
boolean hasExternalConfig = Files.exists(Paths.get(CONFIG_FILENAME));
if (!hasExternalConfig) {
	app.setAdditionalProfiles(CONFIG_DEMO_PROFILE);
	Logger log = LogManager.getLogger(ContainerProxyApplication.class);
	log.warn("WARNING: Did not found configuration, using fallback configuration!");
}

As far as I understand, Spring can find an application.yml in a great many places, however the current code warns that it is only respected if it's in the same working directory as the containerproxy. Passing it in via the CLI like --spring.config.location=/my/great/path does still work but containerproxy spits out a warning.
Is it possible to only produce this warning if Spring cannot find an application.yml?
Looking forward to hearing from you.

Hi, thanks for reporting this. This is now fixed in the latest release we made. We also updated our documentation to include this option: https://shinyproxy.io/documentation/configuration/#spring.config.location . Please be aware that not all methods provided by spring are fully supported by ShinyProxy.


Keyboard Accessible Functionality availability for keyboard

Hi,
Next and Previous buttons seems to be not keyboard accessible. If a SR or Keyboard user press Shift+TAB then only focus moves to the Next and Previous button
It would be better if SR or Keyboard user can access the Next and Previous button using TAB key instead of Shift + TAB

Hi,
Actually a keyboard only user can press PageUp/PageDown or Alt+PageUp/PageDown to perform the same actions as the Next or Previous buttons, which is easier than trying to set focus to these buttons every time you want to move around the datepicker.
I agree that this is not immediately obvious to a sighted keyboard only user however, so the following technique can be used to add a custom tooltip when the calendar is rendered to clue the sighted user in that such commands are available to them.
Within your page stylesheet, add a pseudo element class that binds a CSS pseudo element to the calendar, like so:
div.calendar[role="dialog"]:after {
display: table;
height: auto; width: auto;
position: absolute; padding: 1px 0;
z-index: 2;
margin-top: 5px;
margin-left: -100px;
background-color: black;
color: orange;
font-size: .9rem; font-weight: 900;
content: ' Press PageUp/PageDown, Home/End, or the arrow keys to navigate. ';
}
You can use the margin-top, margin-left, and z-index properties to position the tooltip relative to any instance of the datepicker when rendered, which may be of help in providing additional help information for sighted keyboard only users.

@accdc
Thanks for your support.
Tooltip is a good option. However there is another observation which I wanted to share with you to provide some ideas.
When I tab to calendar there are two elements that I can focus, one is the navigation arrow buttons and other is the days in the calendar itself.
First time when I come to calendar the focus is on the calendar current day of the browser user is on and I can click to select the different date by tabbing.
However when I shift tab, it moves in the way e.g. it goes to the right navigation arrow (for navigating months and years) and then to left navigation arrow and then out to the element from where it came to calendar.
Is it possible to implement the same navigation behavior as we do when we shift tab. If yes then it would be great and satisfy our accessibility requirement.
Expected behavior:

When I come to calendar the left button should be selectable and focus / highlight should be on the browser current date (the second part is already happening so nothing needs to be done for it)
When I tab again the right button should be selectable and focus / highlight should still be on the browser current date  (the second part is already happening so nothing needs to be done for it)
When I tab again then the days in the calendar should be selectable and I can continue tabbing to navigate to new days

Note - the above 3 steps is the current behavior when the keyboard user does shift + tab to navigate in the reverse direction.

Hi, I'm having trouble understanding what is being asked. So if you open the datepicker and focus is set on the current date as expected, what is supposed to happen when you press Tab at that point?

Hello @accdc
Thanks for your response.
The focus is set on the current date as expected, however when I tab, it should focus on the left navigation arrow and when I hit enter it should go to previous month.
When I navigate using shift Tab to traverse in reverse direction, it actually goes from date to right navigation arrow and then left and then outside calendar. That's the same navigation pattern I am expecting should happen when I enter inside calendar.

Hi,
I've updated all of the calendar module JS files in the archive to support circular tabbing forward and backward as though the datepicker is a modal dialog from a keyboard perspective.
E.G
http://whatsock.com/tsg/Coding Arena/ARIA Date Pickers/ARIA Date Picker (with Disabled Date Ranges)/demo.htm
Regarding the order of which buttons get focus, this is actually following the standard tab order in the browser in the order they appear in the DOM, so the first two buttons that get focus are "Previous Year" and "Next Year", followed by the next two buttons "Previous Month and "Next Month", then focus is set to the focused date in the calendar.
This order seems logical to me because I either want to move by year or month one way or another. Is this an issue from your perspective?

@accdc
Thanks for the updates.
I am checking with new updates and get back to you.

As of this morning, you can also use the arrow keys in the Next/Prev Year and Month buttons as you like as well as the Tab and Shift+Tab keys for better navigation.
Also there is a new helpText property that can be set in the config setup.js file that will announce this content to screen reader users when the calendar opens, and this also adds a data-helptext attribute to the top level div element so you can add a CSS class in your stylesheet to display this for sighted keyboard only users as desired, which will reference the attribute value in the date picker when using content: attr(data-helptext) within the pseudo element CSS statement.

@accdc
Thanks a lot.
testing right now.

@accdc
I tested the changes you made and it seems to be as I was expecting...thanks for your support
http://whatsock.com/tsg/Coding Arena/ARIA Date Pickers/ARIA Date Picker (with Disabled Date Ranges)/demo.htm


Add password reset page

[ ] Reset password (index) page
[ ] Check email page
[ ] Enter new password page
[ ] Password change page


updade amount validation in receive

Codecov Report
Patch and project coverage have no change.

Comparison is base (883a41c) 41.63% compared to head (17acc66) 41.63%.

:exclamation: Current head 17acc66 differs from pull request most recent head a79f2d4. Consider uploading reports for the commit a79f2d4 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #392   +/-   ##
=======================================
  Coverage   41.63%   41.63%
=======================================
  Files          15       15
  Lines        1064     1064
=======================================
  Hits          443      443
  Misses        575      575
  Partials       46       46

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

don in another pr


Update centralized-deployment-FAQ.yml

Added a question about add-in removal as it takes only 24 hours for it to reflect per engg team
Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/9331

Docs Build status updates of commit fbb2d3c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/centralized-deployment-FAQ.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@JohanFreelancer9 Please copy review

@kwekuako Please merge this PR. Thanks

Docs Build status updates of commit b15a014:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/centralized-deployment-FAQ.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fixed build choice

Current check results in -prod always getting used.

Sweet, thank you very much!


Add stale bot github action to handle inactive pr and issues

Description
Adding stale bot GitHub action to handle inactive pr and issues. This will help in handling a large number of inactive issues and PR and will enhance the workflow of the repository.

@smv1999 I want to work on this.


fix EthTransactionValidationBuilder::set_eip4844 and no_eip4844

I didn't create an issue for this since it's a simple fix, sorry about that.
set_eip4844 and no_eip4844 functions of EthTransactionValidationBuilder were modifying  self.eip1559 variables instead of self.eip4844. They now modify self.eip4844.

nice find, ty


Library catt

Ehhmm dude, this one got away from me. One thing led to another, and I ended up with yet another redesign. My apologies for the less than readable diff.
You'll also notice that the code has even fewer docstrings than before. :rofl:
But seriously, let's get the ball rolling with regards to how we can make the very-high level API as straight-forward as possible. I've added a simple example script you can look at.

Jeeeez, what's with the /r/watchpeopledie example? The diff is pretty big, yep, I'll skim it and see if I have any comments and report back, thanks!

I can't say I'm in love with the API. In the simplest case, I'd prefer something like:
cc = Chromecast()
cc.play_url("https://whatever")
cc.wait()

Currently there's a lot of boilerplate just to play a URL, which we should probably abstract behind a nice, sane API and expose the less-frequent cases in other ways

Currently there's a lot of boilerplate just to play a URL

I agree, I just wanted to get things going before the PR got even more unreviewable. I'll log on to Gitter now.

Jeeeez, what's with the /r/watchpeopledie example?

Yeah, using liveleak for this wasn't one of my grandest ideas ever.

Why would flake8 only fail with py3.6?

I'm not sure, but it looks like an easy fix.

I don't know, but the changelog clarifies:

A backslash-character pair that is not a valid escape sequence now generates a DeprecationWarning. Although this will eventually become a SyntaxError, that will not be for several Python releases.

Non-valid escape sequences are deprecated, as they should be (because you thought your code was doing something but it was actually doing something else, i.e. trying to escape that sequence).

Ah, thank you for that info.


improve translate

improve translation:

English: which wait on an AutoResetEvent that was created in the signaled state.  Chinese from 等候AutoResetEvent收到信號的狀態中建立。 improve as 等候以收到信號狀態建立的AutoResetEvent

English: The first thread is released immediately Chinese from 第一次釋放執行緒後立即執行 improve as 第一個執行緒被立即釋放

ok


Packages ready for Debian Buster

Hi, I have successfully build binaries packages on Debian Buster.
I can share it if anyone wants it.
I thank you for the work you have done in this project.

Thanks for the offer, but this is not necessary since the next version of Debian binaries will be built off new code from #651. For now, I plan on testing and building binaries for Debian buster and stretch.


Fix SoftBody contact impulses applied on rigid bodies

Parameters were inverted in apply_impulse and apply_bias_impulse due to a modification on master not taken into account when porting 3.x code (PR #37350).
There was also a typo (inverted sign) on one the impulses applied to the soft body.

Thanks!


CB-12686 - Add docs for  support in config.xml

What does this PR do?
Adds docs for  config.xml support
Checklist

[X] Reported an issue in the JIRA database
[X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.

Dependents: #698


Copying code from Sphinx exercise is wrong 🐛

In https://coderefinery.github.io/documentation/sphinx/#group-exercise-build-sphinx-documentation-using-rst
(file content/sphinx.md)
I added the follwoing note also directly into https://github.com/coderefinery/documentation/commit/81b4b7e84e506dfc812ca92695e6c3538d590abf#r51014089:
Lines 32-36:
The copy button copies the whole content of e.g.
$ python --version

Python 3.7.0

including the '$' and the output, which is less than useful and can rather be confusing because it won't work and may not be clear why.
This applies to all code snippets here.

As a note: we can use "```console"

Changed this to console in a PR long time ago.


Implement propensity score-based analysis from Li et al. (2011)

PDF here: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3202161/pdf/kwr096.pdf The sensitivity function $c(z, e)$ needs to be posited by the user and we should provide three possibilities for function specification

[x] constant (related to #9 and closed by #22)
[x] linear

Closed by #22 and #25


Fix CheckBoxGlyphDisabledFill does not work

Fix #368

The CheckGlyph in the template is a PathIcon rather than a Path, so the selector ^ /template/ Path#CheckGlyph is invalid.
Meanwhile, the property for setting the glyph color should be changed to Foreground.


Add support for multiple DBs

This pertains to issue https://github.com/UTDNebula/nebula-api/issues/31

There is no need to use multiple URIs. Establish a connection with a primary URI and establish connections to the neighboring databases from the single URI. This should help https://mongoosejs.com/docs/api/connection.html#connection_Connection-useDb

There is no need to use multiple URIs. Establish a connection with a primary URI and establish connections to the neighboring databases from the single URI. This should help https://mongoosejs.com/docs/api/connection.html#connection_Connection-useDb

Refactored to useDB


Fix drop table on SQLite when foreign keys are enabled

Fixes https://github.com/flyway/flyway/issues/2417

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