Idle Mode Doesn't Work

Operating system
Xubuntu 22.10 with Linux 5.19 kernel
Neovim/Vim version
Neovim 0.7.2
CoC version
0.0.82
Discord version
official
Reproduce step
I set the rpc.checkIdle to true and i waited for 10 seconds and nothing happens on discord. Is this a bug? Here's my CocConfig:

Expected result
Expecting the neovim icon changed to moon emoji or something but nothing happens.
Actual result
This is what it shows:

I minimized my terminal but the icon still using the wrench emoji which I set if I'm still editing a file.
Relevant log output
No response

I don't know why but now it works. Issue closed by myself. Thanks.


how to update cmake version in catkin_make

The current cmake version is <IP_ADDRESS> and I want to update the version to 3.6; What should I do for catkin_make?

I am not sure if you have seen the ROS support guidelines but we kindly ask to raise questions like this on answers.ros.org instead.
The rational for asking all kind of questions in a single place is:

There are many more people reading questions there so your chances on getting an answer and in a timely manner are much higher.
In the future other users will search there for similar problems and can find your question and the potential answers.
The issue tracker in this repo is used to track bugs, feature requests, etc. But your question is not such an action item.

Therefore I will close this ticket here for now. If you have asked your question on answers.ros.org please feel free to add a link to the question to this ticket so that future readers can find the related question.


Add connected state to turbo-cable-stream-source

see recent hotwired/turbo-rails PR: https://github.com/hotwired/turbo-rails/pull/430

Thanks for reporting! We'll add shortly.

Added in 0.3.1.

Awesome, thank you!


Copy Title Page, Team Bios, Solution Approach, and Test Plan to Prototype Report document deliverable

These sections require very little revision for the Prototype Report. Just copy them over and make sure they're good enough.

Include an entry in a narrative form for each of your team members. The goal is to demonstrate the team’s skills and project coverage. This is not just a pasted in resume, but a summary of your involvement in the project, and your technical interests. Feel free to lift from your Team Inventory to include:
● Name
● Degree plan
● Project role - which aspects you’re responsible for
● General areas of experience and technical interests
Example:
Aaron Crandall is a computer science student interested in artificial intelligence, satellite development, and clock making. His prior projects have included smart homes, radio controlled dirigibles, and programming clocks. Aaron’s skills include C/C++, Python, RabbitMQ, Genetic Algorithms, and delinting. For this project, his responsibilities include developing the Gamma Module, leading user experience feedback, and delivering sandwiches.
Lift materials from your solution approach document. This should demonstrate to the reader what your project shall include, at least according to the current design. Just like the Requirements section, ensure you look over the Solution Approach document and take what fits in this narrative and update details as needed.
Bring in your test plan materials. These should demonstrate how you will validate your solution to determine whether it works and if it satisfies the requirements of the project. Look over the plan to ensure your requirements all have at least some kind of unit or functional test that addresses them.

Added Title Page to Responsibilities.

Moved Team Bios into its own issue ( #78 ) after discovering the significant rewriting needed to adapt the Team Inventory content to the report's format.


Unexpected mdev removal in v0.59.0-alpha.2

What happened:
A clear and concise description of what the bug is.
We have an external device plugin for KubeVirt (previously we tested against v0.58.0 and everything works great), the KubeVirt CR configurations are configurated as follows:
spec:
  certificateRotateStrategy: {}
  configuration:
    developerConfiguration:
      featureGates:
      - HostDevices
      - GPU
    permittedHostDevices:
      mediatedDevices:
      - externalResourceProvider: true
        mdevNameSelector: gpu-1g
        resourceName: domain.com/vgpu-1g

But after switching to the latest pre-release (v0.59.0-alpha.2), the mdev instances created by our node provisioner are removed by virt-handler. Please see the logs:
{"component":"virt-handler","level":"info","msg":"Successfully removed mdev 2343a48c-7cca-45f1-99ba-f482591dda42","pos":"common.go:168","timestamp":"2023-01-06T09:49:21.491612Z"}
{"component":"virt-handler","level":"warning","msg":"failed to remove mdev type: 2343a48c-7cca-45f1-99ba-f482591dda42","pos":"mediated_devices_types.go:269","timestamp":"2023-01-06T09:49:21.491716Z"}
{"component":"virt-handler","level":"info","msg":"Successfully removed mdev 592334de-1568-4b43-86cf-1f0580fdb559","pos":"common.go:168","timestamp":"2023-01-06T09:49:21.532028Z"}
{"component":"virt-handler","level":"warning","msg":"failed to remove mdev type: 592334de-1568-4b43-86cf-1f0580fdb559","pos":"mediated_devices_types.go:269","timestamp":"2023-01-06T09:49:21.532082Z"}
{"component":"virt-handler","level":"info","msg":"Successfully removed mdev 9e65262d-9b80-4667-be40-a3f79bf8a2b6","pos":"common.go:168","timestamp":"2023-01-06T09:49:21.570059Z"}
{"component":"virt-handler","level":"warning","msg":"failed to remove mdev type: 9e65262d-9b80-4667-be40-a3f79bf8a2b6","pos":"mediated_devices_types.go:269","timestamp":"2023-01-06T09:49:21.570106Z"}
{"component":"virt-handler","level":"info","msg":"Successfully removed mdev e1255b54-f06f-4f2b-91ba-2b261ffeb780","pos":"common.go:168","timestamp":"2023-01-06T09:49:21.600754Z"}
{"component":"virt-handler","level":"warning","msg":"failed to remove mdev type: e1255b54-f06f-4f2b-91ba-2b261ffeb780","pos":"mediated_devices_types.go:269","timestamp":"2023-01-06T09:49:21.600813Z"}

What you expected to happen:
A clear and concise description of what you expected to happen.
virt-handler should not remove the mdev instances previously created.
How to reproduce it (as minimally and precisely as possible):
Steps to reproduce the behavior.

A external device plugin (mdev) is running
KubeVirt CR is configurated to use the external device plugin
Create mdev instances on a certain node
Check the node resources (capacity and allocable), the resource number should not be zero
Check virt-handler logs, there should be no mdev instance removal logs

Additional context:
Add any other context about the problem here.
Environment:

KubeVirt version (use virtctl version): v0.59.0-alpha.2
Kubernetes version (use kubectl version): v1.23.9
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

@vladikr could you please have a look?

@yeahdongcn could you please check if the KubeVirt CR was modified after the upgrade? Are the permitted devices still listed?

@yeahdongcn could you please check if the KubeVirt CR was modified after the upgrade? Are the permitted devices still listed?

Yes. The above YAML snippet of KubeVirt spec is copied from ❯ kubectl edit kubevirt -n kubevirt.

I just tried to reproduce this, except that I did not use external plugin, for lack of access to the right hardware + plugin combo...
However, the issue did not reproduce, so I suspect this is limited to external plugin use-cases.
I will try to find the right setup to investigate this.

I just tried to reproduce this, except that I did not use external plugin, for lack of access to the right hardware + plugin combo... However, the issue did not reproduce, so I suspect this is limited to external plugin use-cases. I will try to find the right setup to investigate this.

Thanks for looking into this issue. It looks this PR (https://github.com/kubevirt/kubevirt/pull/8481/) might be suspicious...


log4j cve-2021-44228 vulnerability

Hi All,
I wonder if you guys have heard about this vulnerability https://www.randori.com/blog/cve-2021-44228/ affecting log4j v1 and v2.
any thoughts?
Thanks!

https://github.com/lightbend/kafka-lag-exporter/issues/300


'Pocket Cast In Progress' in favorite list, does not throw URI

I am trying to play from the favorite list, using the get_sonos_favorites and the play_uri methods. Both Spotify playlists and TuneIn stations give me title, uri and meta from the favorite list, but Pocket Casts´ In Progress does not. Hence I cannot use it to play my current podcast.

Hi @knudsvik. The play_uri method is really only for playing items, that are only available as URI's like e.g. if you want to single play a streaming URI that hasn't been added to your Sonos. If you really need this, you can use the play uri method, but be aware of the note on HTTP and HTTPS in the http://docs.python-soco.com/en/latest/api/soco.core.html#soco.core.SoCo.play_uri
However, as you mention playing something from your Sonos favorites, you should really just add it to the queue and play it from there.
added_at_index = zone.add_to_queue(some_favorite)
zone.play_from_queue(added_at_index)

Let me know if this fixes your problem.

Closing due to inactivity.


bump awssdk version for a bugfix on http conn leakage

bugfix
The latest aws sdk version 2.20.83 includes a critical bugfix https://github.com/aws/aws-sdk-java-v2/pull/4066 to avoid http conn leakage when aws requests, like S3 getObject, get interrupted.

can't we extract the aws.sdk.version somewhere less verbose

I'll let the PR pass tests and then polish

Codecov Report

Merging #10898 (86ae279) into master (24b50ed) will decrease coverage by 70.23%.
The diff coverage is n/a.

:exclamation: Current head 86ae279 differs from pull request most recent head d63ca52. Consider uploading reports for the commit d63ca52 to get more accurate results

@@              Coverage Diff              @@
##             master   #10898       +/-   ##
=============================================
- Coverage     70.22%    0.00%   -70.23%
=============================================
  Files          2174     1650      -524
  Lines        116871    86162    -30709
  Branches      17702    13570     -4132
=============================================
- Hits          82078        0    -82078
- Misses        29058    86162    +57104
+ Partials       5735        0     -5735

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests1temurin11
0.00% <ø> (?)

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2077 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

error seems related to the s3mock package with the latest aws lib:
 Tests run: 17, Failures: 1, Errors: 0, Skipped: 16, Time elapsed: 7.534 s <<< FAILURE! - in org.apache.pinot.plugin.filesystem.S3PinotFSTest
Error:  org.apache.pinot.plugin.filesystem.S3PinotFSTest.setUp  Time elapsed: 7.309 s  <<< FAILURE!
software.amazon.awssdk.services.s3.model.S3Exception: null (Service: S3, Status Code: 405, Request ID: null)


Add Reuse Action to scan license header

Is your feature request related to a problem? Please describe.
k2s codebase should be scanned for license header in the source files.
Describe the solution you'd like
Use github actions to trigger license header.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Check https://github.com/marketplace/actions/reuse-compliance-check

Done with https://github.com/Siemens-Healthineers/K2s/issues/447.


hook .net winapi calls

can I use this library in c++ or c# to hook api calls from .net . for example : a winapi function is called from c# code can I hook it from another program and check its parameters then continue the function work ?
if I can't do this with easyhook library , is there a library for that

Yes you can, take a look at the remote hooking tutorials.


New iPhone not listed correctly in Device menu

when plugging in an iPhone XS, the device menu in Android Studio fails to display the correct name for the device and instead show an error message from libidevice.

Libidevice have recently been updated to work with new iPhones (UDIDs): https://github.com/libimobiledevice/libimobiledevice/pull/705/commits

Merging with #22147


Golang: Descriptive JWT verification errors

Is your feature request related to a problem?
When verifying signed JWTs with tink for Golang, a verification failure returns a generic "verification failed" error, without specifying the reason why (for example: token has expired, issuer is incorrect). It would be useful to be able to examine the failure reason, both for testing/debugging purposes and to provide useful information to any clients requesting token validation.
What sort of feature would you like to see?
Specific error types for different failure conditions (for example, like the jwx library would be great.
Alternatively, wrapping the underlying cause of the failure and returning a wrapped error would also be sufficient.
Have you considered any alternative solutions?
Alternate solutions:

not exposing/using detailed error information (sufficient for current usage but not optimal)
using a separate library for token verification - not ideal since the number of dependencies increases, and there is additional complexity in converting from tink keyset representations to others
not using tink - aside from this minor problem tink is excellent, so it is not worth switching away for this alone

Thank you!

Thanks for bringing this up. I agree that this not ideal. The error string should be more descriptive
We already do this in Java, and I think we can do something similar in Go.
But I think (at least for now) we don't want to introduce specific error types. The reason for this is that the user should usually not take different actions on the error output, the JWT should always be rejected. Also, distinguishing errors often does not work as well as one would expect. For example, if we want to distinguish an expiration error from a invalid signature error, then this works fine until the verification key gets rotated and removed. Then, the expiration error will suddenly become an invalid signature error. This might cause unexpected and hard to debug problems if the user depends on this.

Hi again @juergw, I've been thinking about this some more and looked back at your initial reply (which I'm afraid I missed at the time - apologies).
Given that verification now returns different error strings, it is possible for users to distinguish failure cases by parsing the error string. Since this is possible, would it be cleaner to formalise it with error types after all?
I think there are some legitimate use cases for being able to easily distinguish them - for example, being able to log attempted verification of tokens with bad signatures vs expired (the latter being an expected case).
Thanks again for looking into this.

Parsing the error is certainly not what we want the user to do.
We will think about it.

I have now added this function in Golang:
https://github.com/google/tink/commit/23005cee999d0ac23b145735b6b5153e0f684322


Grid projections need to be handled correctly

The NAM and RUC grids used in the tutorial have LCC projection coordinates. What is confusing is that the coordinates that are extracted from the grids are latitude and longitude, which typically means you are working with geographic coordinates; however, the latitude and longitude values are simply converted from projection space. In order for the regridding to be done correctly, the latitude and longitude must be converted back to projection space and ESMF.CoordSys.CART must be used instead of ESMF.CoordSys.SPH_DEG.

This was a misunderstanding on my part. The latitude and longitude values are geographical coordinates. To make them look "pretty" on a map you have to convert them back to the correct projected coordinates. The ESMF library assumes that the coordinate system for the source and destination grids are the same (see ESMF Requirements Document in source distribution). In our case, we have latitude and longitude values which are a type of spherical coordinates. If we were to do this using the projected, Cartesian coordinates from the NAM and RUC grids, this would also work as the projections are exactly the same (see the PROJ.4 strings). However, projections are typically not the same between grids and care must be taken to get both source and destination on the same projection in those cases. The ability of ESMF to be projection agnostic is both useful and potentially confusing.
The take home message here is: always make sure both source and destination grids are in the same coordinate system/projection space.


improve SQLAlchemy session management in models.py

the optional creation and closing of local session in case no main_session is present is now encapsulated in a class that can be invoked via a simple with statement
local sessions are now correctly closed in case of Exception during the method execution: previous load of try/except statement could potentially lead to un-closed sessions
4 supplementary UT to validate all that
slightly more concise code :D

I just realise there existe a convenient @provide_session annotation that overlaps with this PR
=> I'll re-use that one instead of instroducing something new


Modpings Improvements

Fixes BOT-1RG
Fixes BOT-1RD
Closes #2002
Closes #2003
Changes:

Add a better datetime converter that allows passing time in 12/24 hour format, the previous method of parsing start and end time is removed (8h, 16h, etc).

Make modpings schedule message more verbose.

Fixes:

Make 16 hours as the max off time i.e. make 8 hours the minimum on time.
Since discord.py moved to timezone aware datetimes, the discord timestamp converter failed, therefore giving no confirmation message, this has now been fixed.
add_roles is a method on a member object, thus calling add_roles on a user object would fail, this has now been fixed and it uses get_or_fetch_member utility function.

@mbaruh do we still want the 8h limit?

Added the do-not-merge because I accidentally approved instead of requesting changes.

Per this message from the author, this PR is now up for grabs.

Sorry about all the additions/deletions for requests reviews, I forgot how to GitHub for a minute

Hi @kosayoda, are you still able to work on this?

Hi @kosayoda, are you still able to work on this?

Feel free to work on it!

@kosayoda Hello. What's your status on this PR?
Thanks!

I wanted to merge it as-is considering the source branch doesn't exist anymore, but it still contains bugs. This will need to be properly re-implemented.


New package: WebalexEU.WinBGP version 1.1.0

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

2024-12-20 13:35:21.680 [FAIL] Installer failed security check. Url: https://github.com/webalexeu/WinBGP/releases/download/v1.1.0/WinBGP-1.1.0-amd64.msi Result: 0x80004005

(Automated response - build 931.)

@wingetbot run


Searching is broken for every Haskell compiler except GHC801

Issue description
With the following command, I am able to browse a list of available Haskell packages:
nix-env -f "<nixpkgs>" -qaP -A haskellPackages

However, when I specify an older compiler like this…
nix-env -f "<nixpkgs>" -qaP -A haskell.packages.ghc7103

…I am met by the following error:
error: attribute ‘Glob_0_7_9’ missing, at /nix/store/brv5102ay5lkp4b0idfxyf0nw30pdd2l-nixpkgs-16.09pre88195.26d2577/nixpkgs/pkgs/development/haskell-modules/configuration-ghc-7.10.x.nix:212:32

According to Freenode IRC user kmicu, the same is true of any compiler version older than GHC 8.0.1.
Technical details

System: Ubuntu 12.04 LTS
Nix version: 1.11.2
Nixpkgs version: 16.09pre88195.26d2577

This is intended behavior and it's clearly stated in the Nixpkgs manual.

nix-env -f "<nixpkgs>" -qaP -A haskell.packages.ghc7103 works for me. (As well as for haskellPackages.)


depthmaps/merged.ply inconsistent (broken?) format [PCL]

ISSUE
Running opensfm/bin/opensfm compute_depthmaps to generate a point cloud in opensfm/depthmaps/merged.ply.
When trying to read the PLY file with PCL, receiving the following error:
[pcl::PLYReader] opensfm/depthmaps/merged.ply:1465336: parse error
[pcl::PLYReader::read] problem parsing header!
[pcl::PLYReader::read] problem parsing header!

The file itself looks normal:
ply
format ascii 1.0
element vertex 1465323
property float x
property float y
property float z
property float nx
property float ny
property float nz
property uchar diffuse_red
property uchar diffuse_green
property uchar diffuse_blue
end_header
25.5590 58.7498 -43.8184 0.029 0.102 0.994 112 102 100
...
merged.ply lines 1-44/1465336 byte 1982/81468783 0%  (press RETURN)

"QUICK FIX"
After some Internet search, the issue is in newline formatting: dos vs unix style. Apparently, PCL is quite sensitive to that and recognizes only the former.
Easy fix can be done by vi +":w ++ff=unix" +":q" merged.ply.
Looks like when OpenSfM writes the PLY file, it misses one character on the last line.
The size difference between the generated and converted files is just one byte:
81468783  merged.ply           (converted with vi)
81468782  merged.ply-orig      (generated by OpenSfM)

PS
Though it's still questionable what shall be fixed:

OpenSfM for proper writing, or
PCL for proper reading.

IMHO both.

If there is only one byte difference, i would guess that only a final \n has been added by vi.
In this case replacing this line https://github.com/mapillary/OpenSfM/blob/f80abbcb09a0ec6b016b967f291aa09f6567c39f/opensfm/dense.py#L314
with
    return '\n'.join(header + vertices + [''])

should fix the problem.
Could confirm that this fixes the PCL reading problem?
thanks!

Tested and confirmed. Your change to dense.py#L314 fixes the PCL reading issue.


FIPS TLS sending v1 frame for tlsv1.2 client hello

We are seeing an issue where bc-fips tls client hello is rejected (connection closed) because in the client hello, the client version is TLSv1, even though the protocol version is 1.2.  We have specifically disabled tlsv1 and tlsv1.1 in java.security, but it still sends v1 in the client hello.

In java.security:
jdk.tls.client.protocols="TLSv1.2"
jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, DH keySize < 1024, EC keySize < 224, DES_EDE_CBC, anon, NULL
Jars: bc-fips-1.0.2.jar    bcpkix-fips-1.0.4.jar       bctls-fips-1.0.10.jar bcpg-fips-1.0.4.jar  bcpqc-addon-fips-1.0.0.jar
I know that this is not the latest version, however, the code looks the same in <IP_ADDRESS>. (TlsClientProtocol.java line 1749). I've tried updating but get other errors related to incompatible trust/key store algorithms.
The RFC for TLSv1.2 states that the client version should be 1.2, even for negotiating different versions (IETF RFC5246 appendix E.1). https://datatracker.ietf.org/doc/html/rfc5246#appendix-E
Is there a work-around or a fix for this?

I think you are confused between TLSPlaintext.version, which is in this example set to 0x0301 (TLSv1), and ClientHello.client_version, which is set to TLS 1.2 per the screenshot you provided. I call your attention particularly to these paragraphs of RFC 5246 Appendix E.1:

Earlier versions of the TLS specification were not fully clear on
what the record layer version number (TLSPlaintext.version) should
contain when sending ClientHello (i.e., before it is known which
version of the protocol will be employed).  Thus, TLS servers
compliant with this specification MUST accept any value {03,XX} as
the record layer version number for ClientHello.
TLS clients that wish to negotiate with older servers MAY send any
value {03,XX} as the record layer version number.  Typical values
would be {03,00}, the lowest version number supported by the client,
and the value of ClientHello.client_version.  No single value will
guarantee interoperability with all old servers, but this is a
complex topic beyond the scope of this document.

Therefore a TLS 1.2 server MUST accept {03,01} as the record layer version number.
I assume you are seeing handshake failures of some kind. Are you sure that it is the version number causing the problem? What type of alert is the server raising? Do you know what software is running on the server and is it under your control so that you could collect logs?

Thanks for the reply. We have confirmed your analysis.  You nailed it. The client hello included a hostname extension which caused the server to drop the connection. That it correlated exactly with the plaintext.version was a red herring.


Does not generate nested serialized objects

The generated json code does not add .toJson to serializable objects inside serializable objects.
Map<String, dynamic> _$FullTrackToJson(FullTrack instance) => <String, dynamic>{
<... omitted>
      'editSuggestions': instance.editSuggestions,
<... omitted>
    };

editSuggestion is a list of FullEditSuggestion objects, which are also serializable and have their own .toJson.
The package does not know to do this:
      'editSuggestions': instance.editSuggestions.map((edit) => edit.toJson()).toList(),

Turns out this is off by default
  /// If `true`, generated `toJson` methods will explicitly call `toJson` on
  /// nested objects.
  ///
  /// When using JSON encoding support in `dart:convert`, `toJson` is
  /// automatically called on objects, so the default behavior
  /// (`explicitToJson: false`) is to omit the `toJson` call.
  ///
  /// Example of `explicitToJson: false` (default)
  ///
  /// ```dart
  /// Map<String, dynamic> toJson() => {'child': child};
  /// ```
  ///
  /// Example of `explicitToJson: true`
  ///
  /// ```dart
  /// Map<String, dynamic> toJson() => {'child': child?.toJson()};
  /// ```
  final bool explicitToJson;


auth: use quorum get for GetUser/GetRole for mutable operations

GetUser would not propagate to the minority node, causing TestCtlV2GetRoleUser to
run CreateUser instead of UpdateUser. Instead, use a quorum get to fetch the
current state of auth.
Fixes #7069

@heyitsanthony to the best of my knowledge, the change works fine for the problem. It will make GetRole and GetUser a little bit heavier, but the cost is unavoidable for resolving the issue.

lgtm


Unable to synchronize the azure redis instance status while it is being created

Describe the bug

Steps to reproduce

Add a template with source https://github.com/walrus-catalog-sandbox/terraform-azure-redis.
Using the template to create a  resource.
Go to the resource details page and check the component list.

Result

The run status was succeed. But it didn't show the  component while the redis instance was being created.

Component was synchronized successfully only when it was created successfully.

Expected behavior

Environment

Walrus version:  v0.6.0-rc1

Additional context
Add any other context about the problem here.

This seems to be a bug of the Azurerm provider. The Redis instance information inside the state file is not updated when deploying Redis directly through Terraform as well.


How to import bom files for all configurations

So far I have been using Spring Dependency Management plugin. But as the gradle 5.0 will be released soon I started to play with those gradle native dependency management features. Its nice that gradle finally integrates them to core. But the documentation is lacking and I it seems that its also not that intuitive. For example, lets say that you are using Spring Boot 2 and have multi module project. What you would want to do is apply Spring Boot plugin at root project and import springs bom file for all projects and all configurations. I don't think this can be done right now.
This works at root project:
plugins {
    id 'org.springframework.boot' version '2.0.5.RELEASE'
}
allprojects {
    afterEvaluate {
        dependencies {
            implementation org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES

But I have a lot more configurations like runtimeOnly, testImplementation, testRuntimeOnly, integTestImplementation, integTestRuntimeOnly, annotationProcessor, compileOnly, providedCompile, provdidedRuntime. Adding this bom import line for every configuration seems redundant. Whats even worse, providedCompile and providedRuntime are not available on every project, only those that are packaged as war. Yet, it would be nice to set it up at the root project level so that spring boot versions would be aligned. I do understand that sometimes you would prefer to add separate bom files for different configurations but more than likely you want to align the versions for all configurations. Maybe we should add "all" configuration?
So I could write
allprojects {
    afterEvaluate {
        dependencies {
            all org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES

Hi @remy-tiitre ,
First of all, the configuration inheritance model of Gradle makes it so that in most cases you only need to declare the BOM in a few configurations. For example if you add it to implementation, you will get the effect in compileClasspath, runtimeClasspath, testRuntimeClasspath and more. It makes therefore no sense to also declare it to testImplementation. You'd only have to do so if your test runtime dependencies need a different platform, which is exactly why it is designed as intended.
Now, should you really want to use a hammer and apply the BOM to all possible configurations, then you only need to apply it to the resolvable configurations. And it can be achieved quite simply. First, define a configuration for the platforms you want to apply everywhere:
configurations {
    globalPlatforms {
       canBeResolved = false
       canBeConsumed = false
    }
}

then add your dependency to this configuration:
dependencies {
      globalPlatforms platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
}

And eventually, make it so that all configurations that can be resolved will inherit from this global platform configuration:
configurations.all {
    if (canBeResolved) {
       extendsFrom(configurations.globalPlatforms)
    }
}

which gives, in the end:
configurations {
    globalPlatforms {
       canBeResolved = false
       canBeConsumed = false
    }
}
configurations.all {
    if (canBeResolved) {
       // configurations like compileClasspath, runtimeClasspath, ... will inherit global platforms
       extendsFrom(configurations.globalPlatforms)
    }
}
dependencies {
      globalPlatforms platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
}

Ok, thanks for this guide. I admit, that my initial example was a little bit misleading. You do not need to apply it to every configuration. Yet, extract from my current configuration:
allprojects {
    plugins.withId('war') {
        dependencies {
            providedCompile org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES

            constraints {
                providedCompile('javax.servlet:javax.servlet-api:3.1.0') { because 'We use Tomcat 8.x' }
            }
        }
    }

    plugins.withId('java') {
        dependencies {
            compile org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES

            constraints {
                annotationProcessor('org.projectlombok:lombok:1.18.2') { because 'Gradle 4.9+ does not work with 1.16.22 version' }
                compileOnly('org.projectlombok:lombok:1.18.2') { because 'Gradle 4.9+ does not work with 1.16.22 version' }
                integTestCompileOnly('org.projectlombok:lombok:1.18.2') { because 'Gradle 4.9+ does not work with 1.16.22 version' }
            }
        }
    }
}

So to be fair, its not that much of a limitation with bom import than with constraints. I would rather write something like this:
allprojects {
        dependencies {
            all org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES

            constraints {
                all('javax.servlet:javax.servlet-api:3.1.0') { because 'We use Tomcat 8.x' }
                all('org.projectlombok:lombok:1.18.2') { because 'Gradle 4.9+ does not work with 1.16.22 version' }
            }
        }
    }
}

But I think with the examples you provided I can archive something like that if the logis is added to gradle wrappers init scripts

I understand. Even with constraints the logic is the same: if you have shared configuration, you can design it using a dedicated configuration and make resolvable configurations inherit from it.

One more thing, if I don't want to detect that some plugin has been applied before I set the version configuration then I have to use afterevaluete, right? Like so:
allprojects {
    afterevaluate {
        dependencies {
            ....
            constraints {

I'm not sure I follow you. A plugin can contribute versions, constraints, anything. You can detect a specific plugin application by using https://github.com/gradle/gradle/blob/master/subprojects/core-api/src/main/java/org/gradle/api/plugins/PluginManager.java#L103

Ok, let me explain my usecase. I have multi project configuration. Most subprojects are generating jar libraries, some are generating war files. Its not a huge one, lets say 1 root project + 3-4 subprojects. Now, fixing dependency versions is reasonable to be done at the root project with allprojects scope. That way, if I update Spring Boot version for example, it will be updated in all subprojects as well. Having said that, I can't configure providedCompile scope dependencies at allprojects closure without checking that this plugin is applied or not. But with the examples you provided I can now create a configuration recommendedVersion and apply that without checking that java or war plugins are applied. These dependencies are inherited automatically by providedCompile and compile configurations. But I already checked that I do have to use afterEvaluate if I want to set constraints to "implementation" configuration or any other configuration added by some plugin. But for reference to other people who might be interested in doing something similar, here is the configuration that works in root project:
allprojects {
    afterEvaluate {
        configurations {
            recommendedVersion {
                canBeResolved = false
                canBeConsumed = false
            }
        }

        configurations.all {
            if (canBeResolved) {
                extendsFrom(configurations.recommendedVersion)
            }
        }

        dependencies {
            recommendedVersion org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES

            constraints {
                recommendedVersion('javax.servlet:javax.servlet-api:3.1.0') { because 'We use Tomcat 8.x' }
                recommendedVersion('org.projectlombok:lombok:1.18.2') { because 'Gradle 4.9+ does not work with 1.16.22 version' }

                recommendedVersion('org.mockito:mockito-junit-jupiter:2.18.3') { because 'Not in Spring Boot' }
            }
        }
    }
}

There is no need for the afterEvaluate in this case. That requirement probably came from trying to reference configurations by name before they were created.
However in this case, the only configuration you reference explicitly is the one you create, recommendedVersion.
The configurations.all is what enables this to work. It will effectively applying the block to any configuration, already existing or created later.
I believe with these exchanges, the issue can be closed. Unless there is further activity in the next 12 hours, I will close it.

You do need afterEvaluate. Even the configurations and configurations.all have to be inside afterEvaluate. Tried without and it failed.

Can you share the exception you get? Cause it really should not be needed. That's the whole point of the .all constructs in the Gradle DSL.

Well, I tried to move this block out of afterEvaluate

Nope, the problem is still there. Adding this code will generate error:
    configurations {
        recommendedVersion {
            canBeResolved = false
            canBeConsumed = false
        }
    }

    configurations.all {
        if (canBeResolved) {
            extendsFrom(configurations.recommendedVersion)
        }
    }

    pluginManager.apply(nebula.plugin.resolutionrules.ResolutionRulesPlugin)

When I put first 2 block inside afterEvaluate it will work

@remy-tiitre I have created a sample project that uses the code above and it builds without problem. Would you mind opening up a PR against it that shows the issue?
Repository: https://github.com/ljacomet/after-evaluate

Closing as the initial issue has been answered and there is no plan to have a dedicated construct in Gradle core for this.
The conversation on the afterEvaluate can move to the forums if it is not resolved at this point.

Well I found the reason, if (canBeResolved) matched my recommendedVersion as well and that caused issues. Will post my final solution here for other people who want to accomplish the same thing:
    configurations {
        recommendedVersion {
            canBeResolved = false
            canBeConsumed = false
        }
    }

    afterEvaluate {
        configurations.all { configuration ->
            if (configuration.canBeResolved && !['checkstyle', 'jacocoAgent', 'recommendedVersion', 'resolutionRules', 'spotbugs', 'spotbugsPlugins'].contains(configuration.name)) {
                extendsFrom(configurations.recommendedVersion)
            }
        }
    }

Just add those configurations in the list that you don't want to extend from the recommendedVersion


mern-mui

Hi
I noticed talk about the mern cli cloning different repositories, with that in mind I took the mern-starter and kept as much as possible and implemented mern-mui starter blog can submit a pull request if you just want to see how much has changed.
Anyway it would need review but it is there for you if you want to start a hashnode mern-mui-starter

Why did you close this? I think this is a great idea

@hounded Awesome! You are fast. We are yet to modify mern-cli to allow cloning of variants. We are looking to completing it within this week. I surely will get back to you after that. Meanwhile, keep an eye on the v2 branch. We are changing a lot of things there.

Yeah hi guys closed it as it is based of v1 and looking at v2 the file structure has changed, started working on a passport authentication for v2. Material Ui is giving me unmet dependencies on webpack in mern v2

ok so I built a mern-mui branch for v2 using what you have come up with so far.

@hounded look forward to checkin this out :+1:

@hounded MERN v2 is released. Check out the docs to find out how to submit your version of MERN to mern-cli.

Is there any progress on that?

I gave up, and fell back to symfony as the mern framework is imo not quite all there for a average/morderate programmer to provide a robust production application.
Show me a package that can plug in to MERN and provide the same user functionality as symfony's
FOSUserBundle and I will swap back to MERN,
but for now there is only some half ass projects that implement passport in an isomorphic application.
Password resetting?
Remember me cookies?
Security around routes?


feat: modernize codebase

This pr:

migrates to TypeScript
adds shadcn ui
partially addresses #500

Note: making changes to tailwind.config.ts or adding shadcn components requires a rebuild

Changes so far:

new mobile navbar

Status page

PR page

some tables now scroll horizontally for small screens instead of bunching up together

This PR also breaks json rendering on the /macrobench/queries/compare route. Root cause is most likely not having access to the json class from ReactJson
before:

after:

On Safari the website does not render well at all. It, almost, only shows white pages when the dark mode is turned on. I would advise you to test the PR on different browsers and see how they behave.

This has been fixed, the issue was a typo in tailwind.css
.dark {
-    --background: 0 0% 0;
+    --background: 0 0% 0%;

The page "Daily" causes a few issues. The background of the graphs are not showing up, and the summary cards (when selected) are highlighted with a dark/white color.

graphs are visible now on hovering summary cards

After:

I've just pushed a potential fix for this but I'm going in blind. I can't see graphs yet on my dev build but the fix involves just using the correct css color variable.

I've just pushed a potential fix for this but I'm going in blind. I can't see graphs yet on my dev build but the fix involves just using the correct css color variable.

It looks great now:


Migrate away from using actions-rs

We are updating to latest node versions in https://github.com/project-akri/akri/pull/548; however, actions-rs actions (audit-check and toolchain) don't have node16 compatible versions available and the maintainer is gone. @jbpaux advises to switch to other actions-- for example the toolchain: the dtolnay/rust-toolchain one but none for the audit-check.

I just saw https://github.com/rustsec/audit-check is a maintained fork for audit-check so we can switch to that.


Quote evtx field names with spaces in FIELDALIAS props

The FIELDALIAS entries with spaces such as "Event.EventData.Category ID" fail to parse in Splunk without quotes, throwing errors into _internal

Good catch, thanks for the fix 👍


Update hdinsight-hadoop-compare-storage-options.md

Fixed the doc error. HDInsight 4.0 does not support ADLS Gen 1

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

#sign-off


OPENCAST-2741 - Update capture agent URL

Update capture agent URL from capture-admin/agents.json to admin-ng/capture-agents/agents.json

I can't think why we'd ever need inputs and flavor info for CAs (basically just need the name), but seems it was there before and doesn't matter really, so if this change works go ahead and merge.


Sync multiple GDrive folders

Thank you for this! I was wondering whether it's possible to sync multiple folder in my GDrive with the reMarkable? I can put them as subdirectories into the synced folder, but can I also sync multiple top-level directories? I tried changing gdFolderSearchParams to a or condition "(title = 'Books' or title = 'Papers') and mimeType = 'application/vnd.google-apps.folder'" but that only syncs one of the two. I have the sync mode set to mirror.

Currently, it uses gdFolderSearchParams to search for a single matching folder. As a workaround you should be able to call syncGoogleDriveWithRemarkableCloud twice in your run_sync function. One for each folder. I haven't tested this yet but I can't foresee any issues with calling it twice.


Error renaming series in iBEAt_HarmonizedDataLeeds.py

Line 21 in iBEAt_HarmonizedDataLeeds.py triggers this error:
Error in InterfaceDICOMXMLFile removeSeriesFromXMLFile: renameSeriesinXMLFile()
missing 1 required positional argument: 'xmlSeriesName'
After completing the calculations, the series names on the treeview have not changed and asking for the MetaData gives an empty field and generates this error:
Error in : ViewMetaData.buildTableView'NoneType' object is not iterable
QLayout: Cannot add a null widget to QVBoxLayout/
Error in : ViewMetaData.buildTableView'NoneType' object is not iterable
QLayout: Cannot add a null widget to QVBoxLayout/
After reloading the DICOM data, the new sequences names are now shown and the metadata are visible

@plaresmedima this should be resolved in the new commit. Please test and close as the code breaks on my side because of missing DICOM tags during anonymisation (I have old Leeds data that probably doesn't fit with the script).

This seems to be working now so I am closing the issue


perf(semantic): reduce storage size for symbol redeclarations

Most symbols don't have redeclarations.
So instead of storing Vec<Span> directly in redeclare_variables (32 bytes per symbol), store Option<RedeclarationId> (4 bytes).
RedeclarationId indexes into redeclarations where the actual Vec<Span> is stored. But for symbols with no redeclarations (the vast majority), it takes 4 bytes per symbol only.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4463  👈
#4461
#4460
#4459
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Regression in semantic[cal.com.tsx] benchmark is unrealistic.
 So it contains e.g. import React from "react"; 18 times - which are treated as redeclarations. That fixture is not valid JS, and is not a good real world example, so I think we can safely ignore the regression.


⚠ Bofrost.be has degraded performance

In 3bf3809, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1650 ms

Resolved: Bofrost.be performance has improved in e52351b after 7 minutes.


But AsciidocFX , include full contents of  HelloWorld.java.
Test Result
AsciidocFX preview or save to html is same result : include full contents of  HelloWorld.java.
FAIL: include full content of file.

Other Test - A
sciidoctor and AsciidoctorJ
I also test the adoc file using :

Docker image asciidoctor/docker-asciidoctor (Asciidoctor 2.0.20)
AsciidoctorJ 2.5.10 (same version as AsciidocFX 1.8.6)
AsciidoctorJ 3.0.0-alpha.2

It OK , only include HelloWorld.java only line 3 to line 5.
My Test Code
.
├── code
│   ├── HelloWorld.java
│   └── index.html
├── demo-code-include.adoc
└── docinfo.html

demo-code-include.adoc
= Demo Source Codes Include
:imagesdir: img
:source-highlighter: rouge
:docinfo: shared

Demo Source Codes Include

'''

[source,java]
.HelloWorld.java
----
include::code/HelloWorld.java[lines=3..5]
----

[%linenums,java]
.HelloWorld.java - show line numbers
----
include::code/HelloWorld.java[lines=3..5]
----

'''

[source,html]
.index.html
----
include::code/index.html[lines=8..10]
----

[%linenums,html]
.index.html - show line numbers
----
include::code/index.html[lines=8..10]
----

<<<

code/index.html
<!DOCTYPE html>

<meta charset="utf-8">
<title>Hello World</title>

Hello World

code/HelloWorld.java
public class HelloWorld {

    public static void main(String[] args) {
        System.out.println("Hello World!");
    }

}

docinfo.html

Other Test Code - Asciidoctor and AsciidoctorJ
# Use Asciidoctor Docker
$ docker run --rm -u $(id -u):$(id -g) -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -o demo-code-include-docker-asciidoctor-2.0.20.html demo-code-include.adoc

# Use asciidoctorj-2.5.10
$ TOOLS/asciidoctorj-2.5.10/bin/asciidoctorj -o demo-code-include-asciidoctorj-2.5.10.html demo-code-include.adoc

# Use asciidoctorj-3.0.0-alpha.2-SNAPSHOT
$ TOOLS/asciidoctorj-3.0.0-alpha.2-SNAPSHOT/bin/asciidoctorj -o demo-code-include-asciidoctorj-3.0.0-alpha.2.html demo-code-include.adoc

Test OK
Only include  Content by Line Ranges

Using AsciidocFX 1.8.5 works as expected.
However, using AsciidocFX 1.8.6 results in nonfunctional behavior.

Thanks for reporting, it is in progress to resolve that issue

Hi, you can see the fix in https://github.com/asciidocfx/AsciidocFX/releases/tag/v1.8.7

Test OK.


Add Partner content

[ ]  Gather content @VonSub
[ ] Create foldout window like team @ehab-hassan (see mockup)

https://invis.io/DFQGT12TES6#/346310438_Artboard

https://invis.io/DFQGT12TES6#/346310438_Artboard

can u send me the foldout content as text so I can copy and past

yes, but there is some difference to what I designed. I would like it to stay inside the "container" just like the team foldouts. If you prepare the .md's i will put in the content myself. But make sure the style is the same as the team foldouts pls.


Test against Ruby 2.7 and fix a warning

Fixes the following warning, which is the only 2.7 warning actually coming from state_machines-audit_trail:
/tmp/bundle/ruby/2.7.0/gems/state_machines-audit_trail-2.0.1/lib/state_machines/audit_trail/backend/active_record.rb:8: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/tmp/bundle/ruby/2.7.0/bundler/gems/rails-a47e0c19e60b/activerecord/lib/active_record/associations.rb:1425: warning: The called method `has_many' is defined here

cc @rafaelfranca @seuros @olleolleolle @smudge

👋 can I ask for a new 2.0.2 release?

@casperisfine done.

Thanks a lot!


Learner Credential Issuer - token/DID exchange handling

Build a module (call it Learner Credential Issuer - LCI for ease of reference ) that simplifies issuing to the LCW, most specifically by managing a token/DID exchange between wallet and server, thereby removing the need to directly tie an issuer's OAuth system into the wallet.
The LCI could also optionally handle all the other bits like constructing the VC, signing, logging, revocation allocation, thereby making it quite a bit simpler for a new issuer to get up and running.
The LCI could be set up as a simple http server (e.g., Node Express) with two endpoints:
/issueCredential  (called by issuer)
/collectCredential  (called by wallet, passing holder DID)
The fundamental flow (see the diagram below) is that a request for a credential is made from a web page behind the issuer's standard authentication system (e.g., Azure), i.e, after the student has logged into the campus system.  When the credential is requested, the issuer retrieves the student's data from the database and then redirects the initial http request to the 'issueCredential' endpoint of the LCI , passing along the data needed to populate the credential.  The endpoint receives the data and stores it as the 'value' in a simple in-memory key-value store, with the key a new UUID.  The endpoint then redirects to a deeplink that opens the LCW, passing along the UUID.  The wallet opens, prompts the user to accept the credential and choose a profile/DID, then submits that DID (as a DIDAuthResponse) back to the /collectCredential endpoint where the LCI receives the DID, adds it to the VC as the subject, signs the VC and returns it.
Note: could split out the piece that handles the DID exchange with the wallet, to make it easier for projects to just use that piece - basically to provide a 'standard' non-OAuth way to collect the holder's DID.
Note that a lot of this is probably already part of sign-and-verify and so this could simply be adding two endpoints to sign-and-verify.

Thanks for submitting this @jchartrand!
(I asked James to add to this repository because it was related to the wallet but this suggestion could easily be its own repo or in the sign and verify.
Ideas to make the issuing flow easier are worth exploring. Would these remove did auth from the issuing flow which ensures that the issuer is able to verify that the subject does have control of that DID.  What are the drawbacks to that?

@kayaelle
The holder/subject would still use DIDAuth to submit their DID.  In other words, when the LCW submits the subject's DID, it would demonstrate control by signing with the private key.
This part of the flow wouldn't change from what the LCW currently does.  In fact, I suspect very few - if any - changes would be needed to the LCW.  I think the LCW already accommodates this flow.
The point of this is just to simplify the token/DID exchange on the issuer's side.

@jchartrand  So the LCI would be the software that does the DID resolution? Would you see the LCI being used predominantly as a service endpoint or one an issuing org would install as a helpful library?

@kayaelle I suppose the LCI would have to resolve the submitted holder's DID, so as to know that a valid private key was used to sign the DIDAuth.  But, that resolution would be done by some other library/service (e.g., https://github.com/decentralized-identity/universal-resolver).
I could see the LCI being used either way - as an npm library or as a service endpoint.  Much like sign-and-verify-core and sign-and-verify.  I could also imagine the service endpoint being run either locally by an issuer, or as a DCC hosted endpoint.

Thanks @jchartrand Looking forward to discussing it more with @dmitrizagidulin

@jchartrand What would you like to do with this issue?

@alexfigtree This has been effectively implemented in the exchange coordinator, so can be closed

Closing per @jchartrand


[Search] new documentation to microsite sidebar

Signed-off-by: Emma Indal<EMAIL_ADDRESS>Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

nvm, that was weird, already exist!


Placeholder {tenantDomain} is not replaced with SPFX_SERVE_TENANT_DOMAIN

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx version 1.17.3
Node.js version 16.20.0

Describe the bug / error
When I run gulp serve the placeholder {tenantDomain} in serve.json is not replaced with SPFX_SERVE_TENANT_DOMAIN environment variable.
If I correctly understood the issue happens because placeholder case-sensitive.
In the file SpfxServeTask.js in the method _getPlaceHolderDomainName expression placeHolderDomainName.includes(TENANT_DOMAIN_PLACEHOLDER) retruns false because

placeHolderDomainName is https://{tenantdomain}/SitePages/myPage.aspx?...
but TENANT_DOMAIN_PLACEHOLDER is {tenantDomain} (different case).

Placeholder is changed  from {tenantDomain} to {tenantdomain} in the method _convertServeConfigurationToPageUrl.
Steps to reproduce

$env:SPFX_SERVE_TENANT_DOMAIN = "mydomain.sharepoint.com"
gulp serve

Expected behavior
Placeholder {tenantDomain} is replaced with SPFX_SERVE_TENANT_DOMAIN environment variable value.

@DenisChimbor - thanks for reporting the issue.
I've just tested it. (using 1.17.4) and I can't repro the issue: the default scaffolded solution is working as expected, the {tenantDomain} is replaced with the variable.
Do you have any extra customizations that can lead to such behavior?

@AJIXuMuK, thank you for the feedback!  I don't have any customizations. But I use spfx 1.17.3. I will try with 1.17.4.

@AJIXuMuK, I downloaded latest generator npm install @microsoft/generator-sharepoint@latest --global and just created a new project (v 1.17.4). Sorry, forgot to mention that I use application customizer. I still have the same issue.
After executing gulp serve it opens me https://%7Btenantdomain%7D/SitePages/myPage.aspx?... Note, that  tenantdomain contains lowercase letter "d".
I have the following gulp version:
gulp --version
CLI version: 2.3.0
Local version: 4.0.2

@DenisChimbor - thanks for extra details!
I can repro it for Application Customizer and we will be working on a fix!

fixed in 1.18.0-beta.3


Compose convertCodeToTile

Pull Request Test Coverage Report for Build 148

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 90.713%

Totals

Change from base Build 147:
-0.02%

Covered Lines:
305

Relevant Lines:
325

💛  - Coveralls


Improve pixi.toml schema syntax for human and machine consumption

Problem description
After using the pixi.toml format some, there are some concrete things that would make it more precise in both editors and in programmatic use:

things like project have no description

fill out more of the docstrings, etc. to make their way into the generated schema

publish the schema as e.g. https://pixi.sh/v0.20.0/schema/manifest/schema.json

this would allow for future schematizing of other things (e.g. lock, various CLI outputs, etc)

declare that URL as the $id

technically it's just a URI, but...
this is generally better than re-inventing something with a version field...

... unless that actually drives some backwards-compatibility mechanism

declare the (meta) $schema of the schema

pydantic claims https://json-schema.org/draft/2019-09/schema, but last i checked taplo doesn't support that
as long as it (meta)validates, staying on http://json-schema.org/draft-07/schema# is a quite safe choice

allow "$schema" in pixi.toml to point to that URL

while taplo has magic a # schema:  directive used in a few of the examples, allowing "$schema" (also supported by taplo) would make it more portable

apply a custom JSONEncoder, so that the document at rest is easier to consume, and changes between versions are easier to inspect

for example:

$schema
$id
title
description
properties

sort these recursively by the same scheme

$defs

sort these recursively by the same scheme

And thanks again for pixi!

Just for reference (for people finding this issue), the schema is declared as Python pydantic model here: https://github.com/prefix-dev/pixi/blob/main/schema/model.py
Contributions are, of course, welcome! :)


Ability to sort search results

From uservoice:

Search results should be sorted by relevance by default, and alternate options to sort them by tenancy, date added etc. should be present.

This is kind of a follow-up to https://github.com/oaeproject/Hilary/issues/1162.

I've been looking into this and some of the sorting options are more difficult than others, so we should list which ones are desirable... For example, sorting by name or tenancy is much easier than by date added since we don't currently store that data in elasticsearch (or even in Cassandra for every type of content if I recall correctly). I'd also want clarification on whether this task includes sorting in a user's library as well as search results.

Okay, so let's list the types of sorting that would make sense and go from there. Based on your description, we've got:

[ ] Sort by name (asc / desc)
[ ] Sort by tenant (asc / desc)
[ ] Sort by date (newest / oldest)
[ ] ...

Any others?
Then, which of those are feasible in the short term / medium term? According to that, we'll edit this issue's title and create another issue for later, depending on how things go.

Sort by name and sort by tenant are relatively easy. Sort by date - which date do we mean, date created or date modified? We don't seem to have date created for anything in elasticsearch, and only have date modified for some types and in a difficult-to-reach format. I'd probably start with sort by name since it's easier and can be applied to both searches and library, then move to sort by tenant and leave sort by date for later.

Let's do that then 👍
Please include a reference for the complementary issue to be created in a comment.


Update mockito-core to 3.12.2

Updates org.mockito:mockito-core from 3.8.0 to 3.12.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito", artifactId = "mockito-core" } ]

labels: library-update, semver-minor

Superseded by #290.


[WIP] chore (api!): removal of capabilites module and all references to it.

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Opening review to trigger E2E


Fix imps

fixes #896

Codecov Report

Merging #902 (8d680c2) into master (4c45650) will decrease coverage by 0.00%.
The diff coverage is 96.87%.

@@            Coverage Diff             @@
##           master     #902      +/-   ##
==========================================
- Coverage   98.13%   98.12%   -0.01%
==========================================
  Files         129      129
  Lines       22739    22771      +32
==========================================
+ Hits        22314    22345      +31
- Misses        425      426       +1

Impacted Files
Coverage Δ

tensornetwork/backends/abstract_backend.py
91.35% <50.00%> (-0.52%)
:arrow_down:

tensornetwork/backends/jax/jax_backend.py
98.86% <100.00%> (+<0.01%)
:arrow_up:

tensornetwork/backends/jax/jax_backend_test.py
99.27% <100.00%> (+<0.01%)
:arrow_up:

tensornetwork/backends/numpy/numpy_backend.py
98.05% <100.00%> (+0.01%)
:arrow_up:

tensornetwork/backends/numpy/numpy_backend_test.py
99.30% <100.00%> (+<0.01%)
:arrow_up:

tensornetwork/backends/pytorch/pytorch_backend.py
99.50% <100.00%> (+<0.01%)
:arrow_up:

...ornetwork/backends/pytorch/pytorch_backend_test.py
100.00% <100.00%> (ø)

...sornetwork/backends/symmetric/symmetric_backend.py
99.30% <100.00%> (+<0.01%)
:arrow_up:

...twork/backends/symmetric/symmetric_backend_test.py
100.00% <100.00%> (ø)

...rnetwork/backends/tensorflow/tensorflow_backend.py
98.24% <100.00%> (+0.02%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #902 (8d680c2) into master (4c45650) will decrease coverage by 0.00%.
The diff coverage is 96.87%.

@@            Coverage Diff             @@
##           master     #902      +/-   ##
==========================================
- Coverage   98.13%   98.12%   -0.01%
==========================================
  Files         129      129
  Lines       22739    22771      +32
==========================================
+ Hits        22314    22345      +31
- Misses        425      426       +1

Impacted Files
Coverage Δ

tensornetwork/backends/abstract_backend.py
91.35% <50.00%> (-0.52%)
:arrow_down:

tensornetwork/backends/jax/jax_backend.py
98.86% <100.00%> (+<0.01%)
:arrow_up:

tensornetwork/backends/jax/jax_backend_test.py
99.27% <100.00%> (+<0.01%)
:arrow_up:

tensornetwork/backends/numpy/numpy_backend.py
98.05% <100.00%> (+0.01%)
:arrow_up:

tensornetwork/backends/numpy/numpy_backend_test.py
99.30% <100.00%> (+<0.01%)
:arrow_up:

tensornetwork/backends/pytorch/pytorch_backend.py
99.50% <100.00%> (+<0.01%)
:arrow_up:

...ornetwork/backends/pytorch/pytorch_backend_test.py
100.00% <100.00%> (ø)

...sornetwork/backends/symmetric/symmetric_backend.py
99.30% <100.00%> (+<0.01%)
:arrow_up:

...twork/backends/symmetric/symmetric_backend_test.py
100.00% <100.00%> (ø)

...rnetwork/backends/tensorflow/tensorflow_backend.py
98.24% <100.00%> (+0.02%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

@alewis review appreciated! thanks!

@alewis review appreciated! thanks!

@jacksonwb @alewis ping for review

@jacksonwb @alewis ping for review

@mganahl isn't this pretty much already done in #901 ?

@mganahl isn't this pretty much already done in #901 ?

Thanks @jacksonwb, I think I actually forgot to commit the changes :0

Thanks @jacksonwb, I think I actually forgot to commit the changes :0

Changes are pushed, would be great if you could have a quick look. Thanks!

Changes are pushed, would be great if you could have a quick look. Thanks!


[web]: How can we use javascript in flutter web

We need to  lead into some third-party components, which do not have flutter version , only the web version can be used. Most of these components interact through javascript. How can we use them? How do I interact with Flutter here?

@pouledodue  Thank you. I'm learning about dart: js, but there's a little information. Here's a question to see if there are any other suggestions or samples.

@wedcel As flutter web is in pre-release it looks like the official way is not completed yet. Usually You would use WebView widget. However this Widget is not available for flutter web yet.

As @pouledodue points out you can use dart:js. There's a more ergonomic package:js (https://pub.dev/packages/js - this package is the recommended way of doing JS-interop).


[Enhancement] Add winter:deploy command

This will be a collection of various ideas around static file generation & deployment of assets to CDNs.
Ideas:

Add support to the winter:mirror command to publish a filtered list of assets (i.e. only assetExtensions and potentially excluding local file storage folders)
Build caching plugin that generates static files that the server software can then handle the routing for with 404 falling back to Winter for any dynamic routes

Further ideas and discussion welcome

Personally, I believe deployment is too opinionated to be something we can truly include in core, so perhaps this command should be something along the lines of winter:static?

Yeah, I'm pretty flexible about what it would be called, @jaxwilko was working on making Winter work on Laravel Vapor and as part of their deployment process they copy everything from the public folder to a S3 bucket and change the asset_url to the CDN URL for the bucket and I thought that would be a pretty nice thing that we could potentially do in the core as well.
The static file generation for caching of route responses is something else that I've been thinking about for a while so thought I'd include it here for discussion.

Both great ideas definitely, I just personally don't want it to sound like the "one true method"(tm) of deployment.


Fix compile-time-constants command

Testing

[ ] @shimkiv to confirm command works

!ci-build-me

mina.exe advanced compile-time-constants
{"genesis_state_timestamp":"2020-09-16T10:15:00.000000Z","k":290,"coinbase":"720","block_window_duration_ms":180000,"delta":0,"sub_windows_per_window":11,"slots_per_sub_window":7,"slots_per_window":77,"slots_per_epoch":7140}


lasot dataset

Hello, is the lasot data set to be divided into training and testing sets？

The dataset is officially divided into a test set and a training set. The training set is used automatically when the code is trained and the test set is used when it is tested.


Game update possibly broken the plugin

I spawned to the new scenario latest DLC added, tried to load toolbar I always use in vanilla worlds.
The game crashed right when it should load, then errored out when the game restarted.
Since I can't re-enable it, can't confirm if it's dependant on the scenario.

I did the new update, when loading the error and it doesn't run, I tried deleting everything and installing everything again, but nothing. Looks like it's the new version of the game.

A new version will be released soon, which will fix the issue. It already works here, just tested it.

Toolbar Manager 1.3.4

Compatibility with game version 1.203.022: Decorative Pack #3
Harmony 2.2.2


Cannot connect to placement service

In what area(s)?
area placement
What version of Dapr?

1.1.x

Expected Behavior

No error in dapr sidecar logs
Actual Behavior

I keep getting the following log entries:

time="2021-06-28T07:57:13.1754689Z" level=debug msg="try to connect to placement service: dns:///dapr-placement-server.dapr-system.svc.cluster.local:50005" app_id=shippingprocessing instance=shippingprocessing-76f9dcd864-gm5fs scope=dapr.runtime.actor.internal.placement type=log ver=1.2.2
time="2021-06-28T07:57:13.2010765Z" level=debug msg="error connecting to placement service: rpc error: code = Unavailable desc = last connection error: connection closed" app_id=shippingprocessing instance=shippingprocessing-76f9dcd864-gm5fs scope=dapr.runtime.actor.internal.placement type=log ver=1.2.2
time="2021-06-28T07:57:13.7028606Z" level=debug msg="try to connect to placement service: dns:///dapr-placement-server.dapr-system.svc.cluster.local:50005" app_id=shippingprocessing instance=shippingprocessing-76f9dcd864-gm5fs scope=dapr.runtime.actor.internal.placement type=log ver=1.2.2
time="2021-06-28T07:57:13.7334305Z" level=debug msg="error connecting to placement service: rpc error: code = Unavailable desc = last connection error: write tcp <IP_ADDRESS>:35834-><IP_ADDRESS>:50005: use of closed network connection" app_id=shippingprocessing instance=shippingprocessing-76f9dcd864-gm5fs scope=dapr.runtime.actor.internal.placement type=log ver=1.2.2
time="2021-06-28T07:57:14.2337911Z" level=debug msg="try to connect to placement service: dns:///dapr-placement-server.dapr-system.svc.cluster.local:50005" app_id=shippingprocessing instance=shippingprocessing-76f9dcd864-gm5fs scope=dapr.runtime.actor.internal.placement

Steps to Reproduce the Problem

dapr init -k
Run a dapr injected pod that subscribes to a component. Look at its logs. Here is a little more info:
kubectl get svc -n dapr-system

kubectl describe svc dapr-placement-server -n dapr-system

kubectl get pod dapr-placement-server-0 -o wide -n dapr-system

kubectl -n dapr-system logs dapr-placement-server-0
time="2021-06-28T08:06:32.0123863Z" level=info msg="starting Dapr Placement Service -- version 1.2.2 -- commit 8aabc2c" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=unknown
time="2021-06-28T08:06:32.0125424Z" level=info msg="log level set to: info" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
time="2021-06-28T08:06:32.0147043Z" level=info msg="metrics server started on :9090/" instance=dapr-placement-server-0 scope=dapr.metrics type=log ver=1.2.2
time="2021-06-28T08:06:32.0180356Z" level=info msg="Raft server is starting on <IP_ADDRESS>:8201..." instance=dapr-placement-server-0 scope=dapr.placement.raft type=log ver=1.2.2
time="2021-06-28T08:06:32.0180869Z" level=info msg="mTLS enabled, getting tls certificates" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
time="2021-06-28T08:06:32.0183574Z" level=info msg="tls certificates loaded successfully" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
time="2021-06-28T08:06:32.0190689Z" level=info msg="placement service started on port 50005" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
time="2021-06-28T08:06:32.0192518Z" level=info msg="Healthz server is listening on :8080" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
time="2021-06-28T08:06:33.9448884Z" level=info msg="cluster leadership acquired" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
time="2021-06-28T08:06:33.9451607Z" level=info msg="leader is established." instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.2.2
The dapr-placement-service seems up and running but seems to reject connections.  There is no network policy and no service mesh involved. It's a plain vanilla Docker Desktop K8s (version 1.21.1)

@stephaneey Docker Desktop k8s is an untested distro as far as Dapr is concerned. personally, I've heard people having trouble using it with Dapr (and other projects with some non-trivial network setup) due to how it treats IP addresses from the local machine.
Can you kindly try KiND or Minikube?

Hi @yaron2 ,
Thanks for your reply. Note that everything else (Istio, KEDA, etc.) is working perfectly fine in the cluster. I'll close this issue and I'll check if I encounter the same problem with AKS.
Thanks
Best regards

Hi @yaron2,
As I told you, I would also check with AKS (K8s 1.19.11) and I have the exact same issue.

Hi @yaron2 ,
I have some news. It seems that I found the culprit...I forgot that I had injected the dapr-system namespace with Istio. However, I noticed that the culprit came from the TLS setting for the dapr-placement container:
    - --tls-enabled

When the istio-proxy tries to connect to it, it keeps failing with the errors depicted before. If I remove this line, it works like a charm.
Could you please share your thoughts about this?
Thanks

Closing this one and created a new issue #3399


feat: blog: Create a custom rule to disallow underscores

This blog post explains how to create an ESLint custom rule, which disallows underscores.
Note: partials/author_bios file not generated if bio is missing from GitHub profile (script generates an error due to empty / null result).

Note: partials/author_bios file not generated if bio is missing from GitHub profile (script generates an error due to empty / null result).

Thanks for the heads up on that. We will get it fixed.

Thanks so much for these updates. I left a handful of suggestions.
The team and I will be reviewing this over the course of the next week and get back to you.

@nzakas No problem. I pushed a few updates on Tuesday that incorporates your notes. If you have any questions, feel free to comment or email. Have a good Labor Day weekend!

Thanks so much! I've sent you a follow up email.


Describe barrier=yes as "Unspecific barrier value" and complain about it in validator

triggered by https://www.openstreetmap.org/note/3264943
See also #399 ("Describe shop=yes as "Unspecific shop"")

Note that “unspecified” is a more natural word than “unspecific”.
I’m not sure that there’s a readily available validator rule that could be defined in this repository for barrier=yes, unless you mean that this tag should be deprecated in favor of… something. I think there would need to be a change downstream in iD to implement a new validator rule for nonspecific tags, if it’s really so urgent to choose a tag other than barrier=yes. (From a routing standpoint, at least, a much more urgent task would be to set access tags. Routers don’t assume the default access tags that most mappers intuitively expect.)

barrier=yes is a valid tag to use and should not be deprecated, but replacing it with more specific values is very useful.

ea34244 adds a preset for barrier=yes called Barrier (Unspecified Type) following the case of shop=yes in #399.

but replacing it with more specific values is very useful.

can you open a new feature request for a validator message on the iD repo, please?

Thanks!


#63: Add self to find_with_closure closure arguments

Codecov Report

Merging #70 (d3a7462) into master (8bbc202) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##           master      #70   +/-   ##
=======================================
  Coverage   65.31%   65.31%
=======================================
  Files          17       17
  Lines        1782     1782
=======================================
  Hits         1164     1164
  Misses        618      618

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 3min)


language_subtag_registry: fix hash

Motivation for this change
fix hash

@GrahamcOfBorg build liblangtag

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: liblangtag
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: liblangtag
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1
shrinking /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1/lib/liblangtag-gobject.so.0.3.0
shrinking /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1/lib/liblangtag/liblangtag-ext-ldml-u.so
shrinking /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1/lib/liblangtag/liblangtag-ext-ldml-t.so
shrinking /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1/lib/liblangtag.so.1.4.0
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1/lib
patching script interpreter paths in /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1
checking for references to /build in /nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1...
/nix/store/5x3dlsrbjck9kvzg4y0r2vifw4gbmy5w-liblangtag-0.6.1

Success on x86_64-linux (full log)
Attempted: liblangtag
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1
shrinking /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1/lib/liblangtag/liblangtag-ext-ldml-t.so
shrinking /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1/lib/liblangtag/liblangtag-ext-ldml-u.so
shrinking /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1/lib/liblangtag-gobject.so.0.3.0
shrinking /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1/lib/liblangtag.so.1.4.0
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1/lib
patching script interpreter paths in /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1
checking for references to /build in /nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1...
/nix/store/lm8chrpm8si2c3yraxxy96ixjpbpx7x8-liblangtag-0.6.1

backported to 18.09 because it had the same broken hash: a3e5e6e792858d075902448d9354633b92b47308


Upgrade Yew to 0.21

#31
You must run cargo update.

I tried your branch but I have an error I cannot explain for now, when launching trunk serve from the example/basics directory.
   Compiling yew v0.21.0
error[E0277]: the trait bound `implicit_clone::unsync::IMap<_, _>: From<indexmap::IndexMap<K, V>>` is not satisfied
   --> /home/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/yew-0.21.0/src/html/conversion/into_prop_value.rs:216:20
    |
216 |         IMap::from(self)
    |         ---------- ^^^^ the trait `From<indexmap::IndexMap<K, V>>` is not implemented for `implicit_clone::unsync::IMap<_, _>`
    |         |
    |         required by a bound introduced by this call
    |
    = help: the following other types implement trait `From<T>`:
              <implicit_clone::unsync::IMap<K, V> as From<indexmap::map::IndexMap<K, V>>>
              <implicit_clone::unsync::IMap<K, V> as From<std::rc::Rc<indexmap::map::IndexMap<K, V>>>>
              <implicit_clone::unsync::IMap<K, V> as From<&'static [(K, V)]>>

For more information about this error, try `rustc --explain E0277`.
error: could not compile `yew` (lib) due to previous error
2023-10-01T16:23:43.328224Z ERROR ❌ error
error from HTML pipeline

I am using Rust 1.72.1
What is strange is that I do not have this error if I create a new yew project and launch it, so it might be due to some dependency, but I don't know how to find it.

I am using Rust 1.72.1
What is strange is that I do not have this error if I create a new yew project and launch it, so it might be due to some dependency, but I don't know how to find it.

I did, but I executed {{cargo clean}}, I thought it would do the job. I agree that {{cargo update}} does the job !


Improve handling of built-in packages

Use straight-built-in-pseudo-packages in straight--convert-recipe.
Gather and check list of packages found to be built-in with
straight--found-built-in-packages.
This improves my startup time significantly.

What is the bottleneck that this change alleviates?
If the issue is that straight-recipes-retrieve takes nontrivial time to execute, we should look into caching the result of straight-recipes-list from each recipe repository when inside a transaction.
Just inhibiting lookup for the common dependency cl-lib is not really appropriate, given that some package repositories (e.g. GNU ELPA) actually do provide the package cl-lib.

I can see removing cl-lib from the list. I just did that.
I was doing some profiling, and straight-recipes-retrieve was getting called for cl-lib, let-alist, and seq many times at startup. Excluding these using one of these lists gets me half a second now (it seemed to be getting me closer to a second earlier).
At the very least, I'd like to be able to use straight-built-in-pseudo-packages. It was defined, but I couldn't find a place it was used in the code. I don't care if the variable that automatically records the built-in packages is added, since I can use the one that's already there.

My goal was to match my el-get startup time, and this is one way for me to get there. It's roughly the same amount of savings as setting straight-check-for-modifications to livefor me.

Whoops, you're indeed right that straight-built-in-pseudo-packages was not used anywhere. I think I meant to check it with memq instead of just checking for emacs, but then forgot. I've fixed that now.
My concern with your current idea, though, is that it introduces a potentially surprising corner case: let's say that someone tries to install cl-lib and straight.el doesn't do anything, because it's detected to be built-in. But what they really meant was to install cl-lib from a custom recipe repository, so they register that recipe repository and try again. This will still fail, because cl-lib will remain in straight--found-built-in-packages forever (unless the user specifically evaluates a setq for it).
I think it may be possible to fix this pretty easily. Instead of adding the package name to straight--found-built-in-packages, how about we make it so that straight--convert-recipe will store a nil value in straight--recipe-cache for that package, and then return it on further requests? That way, when the user reloads their init-file the cached value will be re-set.

Yep, seems reasonable. It's more work to use the cache. Just using nil won't work with the existing code, because there would be no distinction between a found nil and gethash not finding a key.
For now, I just fixed the straight-built-in-pseudo-packages issue. That's sufficient for my purposes at the moment. I reverted the other changes.

You can use straight--checkhash to determine if the hash has a key. It will be a bit of control-flow refactoring, though.

The original issue is fixed on develop. Didn't notice that's where the main development was happening


Generate static site.

Please could a function be made that allowed an export of a static site, as this would be brilliant addition to ghost, as security-wise, this would be a very safe option.
Direct sync with Github Pages/Amazon S3/FTP would be a nice improvement to this feature, to.

I would love to have static site generation too. I am hosting on S3/CloudFront. My editors need something non-technical. Currently I use Jekyll and its its not perfect for them. With Ghost being able to export the full thing to a specific directory I would certainly use it.

I use HTTrack to generate the static site from my blog on localhost and then upload that to S3 as a static website. Here is a tutorial explaining the steps http://codingfundas.com/ghost-blog-on-aws-s3-as-a-static-website

I recently created a static site generator for my own blog that uses ghost. You can check it out here.
https://github.com/Fried-Chicken/ghost-static-site-generator

https://fdezromero.com/how-i-host-this-static-ghost-blog-on-github-pages-with-wget/


cbuild setup USB_Device.csolution.yml --context-set does not evaluate configurations

Describe the bug
cbuild setup USB_Device.csolution.yml --context-set does not evaluate layer configurations when the file *.cbuild-set.yml exists already.
To Reproduce
To duplicate use MDK-Middleware example as described here:
https://github.com/Open-CMSIS-Pack/Create-Scalable-SW/blob/main/Demo/MDK-MW_RefApp.md
(see also issue #1562)
Steps to reproduce the behavior:
Content USB_Device.csolution.yml:
  target-types:
    - type: B-U585I-IOT02A
      board: STMicroelectronics::B-U585I-IOT02A
#      variables:
#        - Board-Layer: $SolutionDir()$/../../../../ST_B-U585I-IOT02A_BSP/Layers/usbd/Board.clayer.yml

Content USB_Device.cbuild-set.yml
cbuild-set:
  generated-by: csolution version 2.5.0-devint1
  contexts:
    - context: HID.Debug+B-U585I-IOT02A

Using cbuild setup USB_Device.csolution.yml --context-set no configurations: in cbuild-idx.yml are present.
Expected behavior
Using cbuild setup USB_Device.csolution.yml the configurations: are correctly evaluated, this is also the expected behavior in above case. The evaluation of layers should consider all context, even when a specific context-set is used.
Environment (please complete the following information):

Windows
cbuild 2.5.0-devint1

cbuild 2.5.0-devint3 delivers this output with --verbose and --debug

It is a user error or my end.


Visual Plugin Manager needed for Spyder

A simpler visual GUI for managing plugins is needed in Spyder...   a GUI plugin for managing plugins (8^)).
Right now I have to hack the command line with conda to get information about installed plugins and it is tedious.
Perhaps put another menu under the "Tools... Preferences" menu and/or as another panel inside the Preferences dialog as a "Plugins" menu item in the left-hand navigator.
This will let people see what their current configurations are for Spyder plugins.  It will help for reporting on installed plugins too, because a "send to Spyder team" button could be added right there to do context-sensitive reporting.
It will also help to extend the Spyder architecture to accommodate more plugins more easily.
Please consider enhancing the plugin interface to include a better GUI for managing plugins.
Thank you.

Hey @richdevboston, thanks for reporting. Thanks a lot for the suggestion, we also agree with you and are discussing about how to add such an interface for Spyder 6, to be released next year.

I'm going to move your issue to this repo
https://github.com/spyder-ide/ux-improvements/
because that's where we discuss interface improvements.


Document Testing Strategy

Where should we document this?
(i.e. README.md, this issue, loodse/docs, someplace else?)

@nmiculinic Updated the description


How to retrieve messages after re-login

Hey guys, I hope it is a plain question.
After TDLib LogOut, some messages were posted to my account/chat, when I am LogIn/Authorize back with TDLib - none of these messages retrieved/handled.
How to retrieve these messages? Thx.

You can't get these messages through updates. You can try to call getChats and getChatHistory to fetch the messages from the message history.

Understood, thx @levlam


Support for more than one certificate from the same secret/configMap in bundle source

closes: https://github.com/cert-manager/trust-manager/issues/458
This is a first attempt to implement support for including in a bundle not just one PEM file referenced by a key, but all of them which match a regular expression.
This is how we currently include a bundle a source PEM from a secret referenced by key:
apiVersion: trust.cert-manager.io/v1alpha1
kind: Bundle
metadata:
  name: my-org.com
spec:
  sources:
  - secret:
      name: "my-certs"
      key: "ca.crt"

And this is how we could reference more than one using a regular expression with these changes:
apiVersion: trust.cert-manager.io/v1alpha1
kind: Bundle
metadata:
  name: my-org.com
spec:
  sources:
  - secret:
      name: "my-certs"
      matchKey: ".*"

Happy to get any feedback since this is my first contribution to the project :)

/ok-to-test

Summarising discussion from standup on 2024-10-22:

We'll instead add a new key for Secrets and ConfigMaps which allow users to include all keys in the target Secret and ConfigMap
We'll add a special case where this new key is disallowed for tls type Secrets

Thanks for raising this Julio!


Idea to merge viroconcom and WDRT's ESSC module

We are thinking about merging viroconcom and WDRT's ESSC.py module.
Current classes diagram of viroconcom:

Possible future classes diagram:

This classes diagram shows how ESSC's principle component analysis and copula-based probabilistic models could be integrated into viroconcom.

As of virocon 2.0 the class diagram has changed and there are currently no concrete plans to merge with the ESSC module such that I am closing the issue.


Icon links should be evenly distributed

I think the icon links feature would look better with justify-content: space-evenly:
Before:

After:

I'm not sure what this looks like with multiple rows of icon links, and maybe someone else knows a better CSS way to do this than I do. But I found that this CSS makes things look better:
.navbar-icon-links {
  justify-content: space-evenly;
}

seems like a good idea to me. @gabalafou @12rambau any reason you can think of why we might not want that?

In what context fdo you see these lines ? Is it in the right sidebar on small screen or on the top navbar on big ones ?
For me these things are always on 1 line and here I see 2.

I don't know what lines you're referring to? This proposal is about spacing between icon links

I believe @12rambau refers to the display shown in your images where the icons and the search field are presented in a two row layout (icons on top of search)

It is the primary sidebar, on the left.

if it's the left sidebar then I prefer to have them left align as th text. If its the top navbar I'm don't have strong opinion. You'll note that I have no other argument than "I prefer" so if any a11y justification comes in, please do as if I wasn't there ;-)

one thing that occurs to me is that spacing buttons farther apart makes them easier to hit on a touch device with big or shaky fingers --- so that's maybe an argument in favor of spreading them out when they're in the sidebar (which by default happens on small screens, which are usually touch devices).

I think they are indeed easier to target on mobile this way. But, if you all don't want to go this way, I'm ok with that, we can keep our own CSS customization too.

I think we have one usability argument in favor, and one "just my opinion, feel free to disregard" vote against. So I'd say please go ahead with a PR @leifwalsh

Will do, just need to wait for approval to contribute from $work, so probably next week. Thanks!

I am not sure, whether this might already solve my issue, but I came across a similar problem, when looking at the version-switcher. We are currently preparing multi-version documentation and in this process discuss where to best place the version switcher. One option is to put it into navbar_end next to the icon links. However, then it ends up in the same line as the logos in the primary sidebar on small dveices:

As you can see they do not align nicely. While I do not know, whether that would be easy to fix, I would like to suggest to put the version-switcher into a separate line. Again, I have no idea, whether that can ebe easily achieved.

One more point: when you look carefully, you also realsie, that the font size is different for the version switcher and the other navigation items.


ERROR - this language feature is only supported in es6 mode: arrow function

How to fix the below error created while "grunt build"
`:~/apprtcserver/apprtc$ sudo grunt build
Running "shell:buildAppEnginePackage" (shell) task
Running "shell:genJsEnums" (shell) task
src >>> src/web_app/js
Running "closurecompiler:debug" (closurecompiler) task
Compiling node_modules/webrtc-adapter/out/adapter.js,src/web_app/js/analytics.js,src/web_app/js/enums.js,src/web_app/js/appcontroller.js,src/web_app/js/call.js,src/web_app/js/constants.js,src/web_app/js/infobox.js,src/web_app/js/peerconnectionclient.js,src/web_app/js/remotewebsocket.js,src/web_app/js/roomselection.js,src/web_app/js/sdputils.js,src/web_app/js/signalingchannel.js,src/web_app/js/stats.js,src/web_app/js/storage.js,src/web_app/js/util.js,src/web_app/js/windowport.js -> out/app_engine/js/apprtc.debug.js
Warning: node_modules/webrtc-adapter/out/adapter.js:2370: ERROR - this language feature is only supported in es6 mode: arrow function. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT to enable ES6 features.
var shimError_ = e => ({
^
node_modules/webrtc-adapter/out/adapter.js:2443: ERROR - this language feature is only supported in es6 mode: arrow function. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT to enable ES6 features.
e => onError(shimError_(e)));
^
node_modules/webrtc-adapter/out/adapter.js:2489: ERROR - this language feature is only supported in es6 mode: arrow function. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT to enable ES6 features.
navigator.mediaDevices.getUserMedia = c =>
^
node_modules/webrtc-adapter/out/adapter.js:2490: ERROR - this language feature is only supported in es6 mode: arrow function. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT to enable ES6 features.
origGetUserMedia(c).catch(e => Promise.reject(shimError_(e)));
^
4 error(s), 0 warning(s)
Use --force to continue.
Aborted due to warnings.`

Please do npm update again which should fix adapter.js.

Build succeeded after removing all arrows '>' from where error is pointing out.
`:~/apprtcserver/apprtc$ sudo grunt build
[sudo] password for kasadmin:
Running "shell:buildAppEnginePackage" (shell) task
Running "shell:genJsEnums" (shell) task
src >>> src/web_app/js
Running "closurecompiler:debug" (closurecompiler) task
Compiling node_modules/webrtc-adapter/out/adapter.js,src/web_app/js/analytics.js,src/web_app/js/enums.js,src/web_app/js/appcontroller.js,src/web_app/js/call.js,src/web_app/js/constants.js,src/web_app/js/infobox.js,src/web_app/js/peerconnectionclient.js,src/web_app/js/remotewebsocket.js,src/web_app/js/roomselection.js,src/web_app/js/sdputils.js,src/web_app/js/signalingchannel.js,src/web_app/js/stats.js,src/web_app/js/storage.js,src/web_app/js/util.js,src/web_app/js/windowport.js -> out/app_engine/js/apprtc.debug.js

Complete: 155638

Running "grunt-chrome-build:apprtc" (grunt-chrome-build) task
Chrome packaged app build.
Deleting buildDir: out/chrome_app
Creating empty buildDir: out/chrome_app
Copying resources to buildDir: out/chrome_app
src/web_app/chrome_app/manifest.json-->out/chrome_app/manifest.json
out/app_engine/js/apprtc.debug.js-->out/chrome_app/js/apprtc.debug.js
out/app_engine/js/loopback.js-->out/chrome_app/js/loopback.js
out/app_engine/css/main.css-->out/chrome_app/css/main.css
out/app_engine/images/apprtc-128.png-->out/chrome_app/images/apprtc-128.png
out/app_engine/images/apprtc-16.png-->out/chrome_app/images/apprtc-16.png
out/app_engine/images/apprtc-22.png-->out/chrome_app/images/apprtc-22.png
out/app_engine/images/apprtc-32.png-->out/chrome_app/images/apprtc-32.png
out/app_engine/images/apprtc-48.png-->out/chrome_app/images/apprtc-48.png
src/web_app/js/background.js-->out/chrome_app/js/background.js
src/web_app/js/appwindow.js-->out/chrome_app/js/appwindow.js
Running "grunt-chrome-build-transform" task
Transforming files using jinja.
Running "jinja:chrome-build" (jinja) task
Using context web_app/html/index_template
File "out/chrome_app/appwindow.html" created.
Running "grunt-chrome-build-compress" task
Creating zip file:out/chrome_app/apprtc.zip
Running "compress:chrome-build" (compress) task
Created out/chrome_app/apprtc.zip (67511 bytes)
Running "grunt-chrome-build-package" task
Skipping creation of Chrome package.
Done, without errors.`

npm update is also solved as you said...


Fix GitHub source code links for decorated functions

Copy of https://github.com/Qiskit/qiskit-addon-utils/pull/42

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

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

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
2408

Relevant Lines:
2408

💛  - Coveralls


Add "DisableTrimmingLeadingSlash" flag to CopyObject / CopyPart requests

Description
Another attempt at Fix S3 Copy not working with "/" (DOTNET-4410), but this time using a flag so customers must opt in to the new behavior.
Testing

Dry-run: DRY_RUN-908e18a7-4077-4ea2-816d-c45561112a63
Manually tested the PowerShell changes:

Cloned the PowerShell repository (https://github.com/aws/aws-tools-for-powershell/)
Downloaded assemblies from dry-run and placed them in the Include\sdk\assemblies folder
Ran dotnet msbuild ./buildtools/build.proj /t:preview-build /p:RunTests=true /p:CleanSdkReferences=false

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)

Checklist

[X] My code follows the code style of this project
[X] I have added tests to cover my changes
[X] All new and existing tests passed

License

[X] I confirm that this pull request can be released under the Apache 2 license

@dscpinheiro May be should also add test case for customer's scenario with DestinationKey set to just /!

@dscpinheiro May be should also add test case for customer's scenario with SourceKey and DestinationKey set to just /.

That makes sense, I added test cases for / as a destination key here: https://github.com/aws/aws-sdk-net/pull/3091/commits/df912d8ca9c7c60265454e0f730c297b7a6fa7d8


IconSize don't change the size if iconLiteral is used

Hi , I found a bug or it's just because we have to use iconSize only with iconCode
iconSize="24" iconLiteral="ion-android-volume-off" don't change the size
 iconLiteral="ion-android-volume-off:24" set the size to 24 px
Thanks

I figured out that happen when IconSize is before iconLiteral. I will make a pull request later to fix this.