Fix kubelet and apiserver templates to use dash instead of underscore

I have fixed templates to use - as word separator, but I am not sure what to do with KUBELET_HOSTNAME="--hostname-override. It is specified in two places in the same template.

Right. The second invocation of hostname-override (from KUBELET_ARGS) should disappear.

I have removed hostname_override parameter entirely

Thank you @KarolisL


Stp/cmake refactor to merge

Updates to cmake to export itself in "modern" way
can be used as submodule or package now
Is a breaking change, have to update NESO (see https://github.com/ExCALIBUR-NEPTUNE/NESO/compare/stp/cmake_refactor_to_merge?expand=1)

Thanks for this:
Could you rebase from the "dev" branch instead of "main". Sorry for this - we moved to having an dev branch to be periodically merged into main. There should not be any conflicts in the cmake files between dev and main.
There will be conflicts in the code formatting between dev and main. Do you know why there are updates happening e.g. to the particle loop implementation?
This is my clang-format version, is there a behaviour change between versions?
$ clang-format --version
Ubuntu clang-format version 14.0.0-1ubuntu1.1

You don't change any C++ source right? Backup option would be to not run clang-format for this PR.


should use sqlite for local development

after PR #15 - we will switch to Knex
we should also support using Sqlite for local development
this greatly simplifies the new developer setup process

Totally agree - this was a big issue dealing with mysql as a new developer setup process

+1


Docker: Dependabot ignores all versions when multiple FROMs reference the same image

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
docker
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
I recreated the issue here: https://github.com/dsp-testing/docker-only-patches
You can reproduce this issue in the CLI by running dependabot update -f cli.yml in a cloned copy of that repo.
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
I expected to see one or two PRs bumping minor versions of Go. Instead it just doesn't do anything. (It's actually throwing AllVersionsIgnored, but that's a different issue)
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

It seems related to https://github.com/dependabot/dependabot-core/issues/6700.

Oh you're right, the setup looks almost identical, just a different outcome.

Dockerfile.txt
dependabot.txt
@jakecoffman I have a customer who reported a similar issue


Fix for Modal scrolling out of bottom while keyboard hide performed in iOS

This is a fix for resolving keyboard hide performed while editing content in Modal, in iOS, keyboardHide and keyBoardChange triggered both, the calculation of keyboard height in keyboardChange action gets a negative value which make the Modal scroll out of screen bottom.

+1 Works Great! Thank you

This issue happens in android. Please provide a fix for android.

use this fix in index.js:-
keyboardOffset: this.props.position === 'top' || keyboardHeight > 0 ? keyboardHeight : 0

@maxs15 Hello, I've been facing this issue on iOS where the  modal scroll down when the opened keyboard is closed inside it. How can I use your solution here?


Issue #4047 - retention and bucket creation

Fix for Issue #4047 for /v2/ (better links between retention info and bucket creation info).
In addition, fixes also the following issues:
1. Wrong indentation
Issue 1.1 (before):

Issue 1.1 (now):

Issue 1.2 (before):

Issue 1.2 (now):

2. Issue with bold
As it was before:

As it is now:

3. Adds missing comma

Describe your proposed changes here.

[ ] Signed the InfluxData CLA
(if necessary)
[ ] Rebased/mergeable

@jstirnaman FYI


Folds executors

Codecov Report
Base: 90.72% // Head: 89.84% // Decreases project coverage by -0.87% :warning:

Coverage data is based on head (a65f70a) compared to base (6af975f).
Patch coverage: 80.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #31      +/-   ##
==========================================
- Coverage   90.72%   89.84%   -0.88%
==========================================
  Files           5        5
  Lines         248      266      +18
==========================================
+ Hits          225      239      +14
- Misses         23       27       +4

Impacted Files
Coverage Δ

src/squared_euclidean.jl
77.19% <80.00%> (+0.10%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


maint: Update AWS regions we publish to

Which problem is this PR solving?
Updates the list of AWS regions we publish the lambda extension to. Also adds docs to how we source the list of regions and how we determine which platforms it supports.
Short description of the changes

Update publishing.sh with new regions
Add section to README on how to get list of regions including supported platforms

Created the following PR to add the missing regions, though not sure what of those regions have been enabled

https://github.com/honeycombio/honeycomb-lambda-extension/pull/123


cardano-node: Fix IPv4/6 parse error message to make it more guiding

Close #2492

bors merge

bors merge


How to get the layer depths and total size by parent layer id?

As mentioned above,I want to get the layer depths and size of a image by its parent layer id.
Considering the following situation:
I have a image in the registry v2 called xxx/busybox, and i want to get its layer depths and total size from registry v2. i will perform the following steps:

get the image xxx/busybox layer id  and its parent layer id.
get the image xxx/busybox layer size by its layer id
perform the 1,2 steps for its parent layer id until reaching the top layer
4. the total size of this xxx/busybox is the sum of its layer size and its parents layers size;
the layer depths are the loop times of performing 1,2 steps.
but as far as i know,there are not valid apis on the side of registry v2 for me to achieve the above steps.
Is there any way to meet my goals?urgently!!!

You are correct in your assessment.  Distribution treats the data it stores opaquely objects and therefore there are no APIs for dealing with the contents.  Doing so would restrict the extensibility of the registry.
You can use the current APIs to download distribution content and perform any actions on those that you wish.

But, How can i know the depths of a image,you know,it is the quite important information in the practical application,especially when the image has big layer depths.
I want to merge the layers to one when the layer depths reach the upper limit !

And could you answer the following question about the image layer parents?
https://github.com/docker/distribution/issues/1575#issuecomment-213364009
If i know the numbers of the iamge parents,that means i will get the depths of its layers.
And I can get the layer size by HEAD /v2/<name>/blobs/<digest>

@duyanghao the manifest formats are specified here and here.  Given this information and the registry APIs for fetching and stat-ing manifests and layers, why can't you achieve your goals?

Could you answer the following question?
Why there are exist the same digest in the /v2//manifests/ http response?
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
   "config": {
      "mediaType": "application/octet-stream",
      "size": 2398,
      "digest": "sha256:55d1ee70345b7190b59311fc9e783ac7329aeab3478fdea18c521ff9de95565c"
   },
   "layers": [
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 66390854,
         "digest": "sha256:3b231ed5aa2f1631b3189f15f215fad43e35ec4aa56ee7bb92b9dd1b73ca94cb"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      }
   ]
}

Why there are exist the same digest in the /v2//manifests/ http response?

This digest is represents a layer diff, the same diff can occur multiple times in an image especially in the case of empty layers. We have tried to remove empty layers from the configs but many are kept in older images for compatibility. The layer identifier used within the engine will end up being a sum based on the current layer and all previous layers, leading to a unique identifier per layer.

what is the base layer digest of this image?

The first layer in the list is the base layer, as common with many Docker files, the base layer ends up not having any data as it only add metadata. We have made changes to ensure these don't need to be included but that is not always the case.

where are all layers of this image?

 Information about each layer can be found in the manifest you listed, as well as in the image configuration under the "config" key.

Could you list them from top layer digest to base layer digest? Is the order of the valid digests from bottom to top in accordance with the order of the layers generated?

The layers are ordered from base layer to top most layer. The ordering with the json manifest are important and will not be reordered as it would cause the layers to applied in the incorrect order, causing a validation failure.

So,you means,in this example,the parent layers from base to top is below:
"digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
"digest": "sha256:3b231ed5aa2f1631b3189f15f215fad43e35ec4aa56ee7bb92b9dd1b73ca94cb" "digest": "sha256:55d1ee70345b7190b59311fc9e783ac7329aeab3478fdea18c521ff9de95565c"

and the latest top parent layer digest for this image is:
"digest": "sha256:3b231ed5aa2f1631b3189f15f215fad43e35ec4aa56ee7bb92b9dd1b73ca94cb"
Is that right?

And Could i understand that the actual top most layer digest is the nonredundant digest in

the end of layers list

?

[root@cn-sh-radosgw-test1 ~]# docker images|grep xxx
xxx/fightingdu/test_for_parent   2.0                 2b701a9b707a        24 minutes ago      190.6 MB
xxx/fightingdu/test_for_parent   1.0                 2df000769c4e        30 minutes ago      190.6 MB
xxx/fightingdu/centos            centos6             55d1ee70345b        8 months ago        190.6 MB

the top most parent of the image xxx/fightingdu/test_for_parent:1.0  is xxx/fightingdu/centos:centos6,that means the top most parent layer digest of xxx/fightingdu/test_for_parent:1.0 should be the image id of xxx/fightingdu/centos:centos6 as below:

sha256:55d1ee70345b7190b59311fc9e783ac7329aeab3478fdea18c521ff9de95565c

here is the manifests result for image xxx/fightingdu/test_for_parent:1.0  :fs
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
   "config": {
      "mediaType": "application/octet-stream",
      "size": 2740,
      "digest": "sha256:2df000769c4eb688ca4b20f219c09aff024d0dd6ba4af9ac82c7a02f38a61e5d"
   },
   "layers": [
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 66390854,
         "digest": "sha256:3b231ed5aa2f1631b3189f15f215fad43e35ec4aa56ee7bb92b9dd1b73ca94cb"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 155,
         "digest": "sha256:9b422f3b209a319fb52601838416533a9a5f51625f63b08cf6292e9204a1f476"
      }
   ]
}

but the problem is that there is no digest:sha256:55d1ee70345b7190b59311fc9e783ac7329aeab3478fdea18c521ff9de95565c
in the layers list!

I understand the confusion, since we moved to content addressable identifiers for images, the parent image id can not longer be seen in the manifest.
The image id refers to an image configuration, the spec for that can be seen here https://github.com/docker/docker/blob/master/image/spec/v1.1.md. Each image will have it's own configuration and does not refer to its parent configuration. Rather it refers to its layers which will include the layers from the parent. The image configuration may be derived from the parent, but it is not directly inherited like the layers are.
The manifest that you pointed to is a schema 2 manifest described here https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md. The schema 2 manifest refers to a single image configuration, and the hash of the distribution artifacts for the layers (gzipped tars in this case). These artifacts when unpacked into the storage driver must produce the content hashes referred to by the image configuration. Since multiple distribution artifacts can represent the same on disk content (due to differences in the way content is packed or compressed), the best way to establish the parental hierarchy of an image is to match based on the layers as specified in the image configuration (rootfs.diff_ids).
Please let us know how we can make these answers more accessible since this is a common source of confusion. The documentation has been written, but it is not easy to find.

Sorry, i am afraid that i have not gotten your meanings,but could you directly tell me how to get the top most parent layer digest of one specified image from the docker/distribution?
And, could you tell me how to get the layer depths of one specified image from docker/distribution?
I need to know the layers depths of one specified image,when the layers depths reach the top limit,I will merge all layers of that image into only one layer,that is important in the practical application of my company!

Layer depth can be found in the image manifest as the length of the layers array (https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md). Additionally the layer depth can also be found in the image config as the length of the rootfs.diff_ids array (https://github.com/docker/docker/blob/master/image/spec/v1.1.md). I encourage you to ask these sort of questions on irc.

There is no rootfs.diff_ids in the image config of docker(1.10+),
Additional,Could you answer the following question?
How to get the top most parent layer digest of one specified image from the docker/distribution?
And as you said,the layer depth is length of layers array,in my example the depth of this image is six,right?
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
   "config": {
      "mediaType": "application/octet-stream",
      "size": 2740,
      "digest": "sha256:2df000769c4eb688ca4b20f219c09aff024d0dd6ba4af9ac82c7a02f38a61e5d"
   },
   "layers": [
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 66390854,
         "digest": "sha256:3b231ed5aa2f1631b3189f15f215fad43e35ec4aa56ee7bb92b9dd1b73ca94cb"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 32,
         "digest": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 155,
         "digest": "sha256:9b422f3b209a319fb52601838416533a9a5f51625f63b08cf6292e9204a1f476"
      }
   ]
}

As mentioned previously, the digests just represent a diff to create the layer. If the layers are empty, they will have the same digest since there is no content to differentiate them. This image has 6 layers, the manifest represents the source of truth for it. These layers can be squashed but please take a look at the image configuration (has the digest sha256:2df000769c4eb688ca4b20f219c09aff024d0dd6ba4af9ac82c7a02f38a61e5d). This will have the  key rootfs.diff_ids. After you squash the image id will be different and it will be considered a different image since the number of layers would not longer be 6.
As for top most layer, the array is ordered from base layer to top most layer as the documentation says. Therefore the top most layer is sha256:9b422f3b209a319fb52601838416533a9a5f51625f63b08cf6292e9204a1f476 and you could consider the parent of that layer the one immediate before it sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4.

@duyanghao Hey! How did you manage to get the manifests for v2? Tried something like  https://registry.hub.docker.com/v2/repositories/shipyard/shipyard/manifests/latest with the proper Accept header, but got nothing. Any insights? TY!

@borzamircea  you can change the http head as belows:
Accept: application/vnd.docker.distribution.manifest.v2+json
refer to:
https://github.com/docker/distribution/issues/1575#issuecomment-213364009


Cannot build crate with ['Inline-asm"] feature

Hello all, I'm trying to get into embedded development with rust.  I'm trying to use the inline-asm feature, but it will not compile.
the cargo.toml line is:
cortex-m = { version = "0.7.6", features = ["inline-asm", "critical-section-single-core"] } (note, I tried 0.7.7 as well as 0.7.6)
The generated error is as follows:
error[E0425]: cannot find function `__basepri_r` in module `crate::asm::inline`
 --> /Users//.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/register/basepri.rs:6:15
  |
6 |     call_asm!(__basepri_r() -> u8)
  |               ^^^^^^^^^^^ not found in `crate::asm::inline`

error[E0425]: cannot find function `__basepri_w` in module `crate::asm::inline`
  --> /Users//.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/register/basepri.rs:22:19
   |
22 |         call_asm!(__basepri_w(basepri: u8));
   |                   ^^^^^^^^^^^ not found in `crate::asm::inline`

error[E0425]: cannot find function `__basepri_max` in module `crate::asm::inline`
  --> /Users//.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/register/basepri_max.rs:19:19
   |
19 |         call_asm!(__basepri_max(basepri: u8));
   |                   ^^^^^^^^^^^^^ not found in `crate::asm::inline`

error[E0425]: cannot find function `__faultmask_r` in module `crate::asm::inline`
  --> /Users/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/register/faultmask.rs:29:28
   |
29 |     let r: u32 = call_asm!(__faultmask_r() -> u32);
   |                            ^^^^^^^^^^^^^ not found in `crate::asm::inline`

error: invalid register `r0`: unknown register
   --> /Users//.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/../asm/inline.rs:197:24
    |
197 |     asm!("bkpt #0xab", inout("r0") nr, in("r1") arg, options(nomem, nostack, preserves_flags));
    |                        ^^^^^^^^^^^^^^

error: invalid register `r1`: unknown register
   --> /Users//.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/../asm/inline.rs:197:40
    |
197 |     asm!("bkpt #0xab", inout("r0") nr, in("r1") arg, options(nomem, nostack, preserves_flags));
    |                                        ^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0425`.
error: could not compile `cortex-m` (lib) due to 6 previous errors
warning: build failed, waiting for other jobs to finish...

is this a simple dependency I'm missing? or is this an issue?  I couldn't find any issues that seemed related.

Are you definitely building for a thumb target? I think this error often occurs if you try and build for a target like x86; you should use --target thumbv7em-none-eabi or similar, or set it in your .cargo/config.toml to avoid needing to write it every time.

ah, you are correct, my rust-toolchain.toml had a type in the target line 🤦


Add Rocket Rewards Tree Informational RPIP

Confirmed that the assets are the same. rewards-calculation-spec.md has 2 links changed from relative to absolute external. The external links point to a specific commit and are non-essential. While they may conceivably get broken by external repo actions, it won't mislead users.


chore: Reconfigure metrics that are duplicated

Fixes #N/A
Description
Reconfigured Karpenter metrics that are duplicated (workqueue metrics, renames of existing metrics).
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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.03%) to 78.101%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
8784

Relevant Lines:
11247

💛  - Coveralls

Would it be possible to add a list of the metrics that are being dropped or renamed in the description? Just so it easier to track while reviewing


Examples rpt 2

Two RPT examples were created:

Count calculation (displays how the Monte Carlo method is used in photon count calculation)
Parameter tuning with NOMAD (tuning to get values for the 3 unknown parameters)

Documentation

Parameters for RPT

[x] parameters/rpt/rpt.rst

[x] parameters/rpt/rpt_parameters.rst

[x] parameters/rpt/detector_parameters.rst

[x] parameters/rpt/parameter_tuning.rst

Comments

Had some issues when rebasing the other branch

Last unresolved comment from the other PR (#509)
@ghazalemir

I think the axis titles in figure doc/source/examples/rpt/tuning-parameters-with-nomad/images/results.png are inverted :). I'll gladly check the PR monday morning otherwise :).

On my side this is good. @ghazalemir  is it good on your side?

Good morning
I will finish reviewing this morning :)
Ghazaleh
Bruno Blais @.***> a écrit :

On my side this is good. @ghazalemir  is it good on your side?
--
Reply to this email directly or view it on GitHub:
https://github.com/lethe-cfd/lethe/pull/522#issuecomment-1181651234
You are receiving this because you were mentioned.
Message ID: @.***>


fix broken links, add links check to sanity

Can one of the admins verify this patch?

@tensorflow-jenkins test this please.

some unrelated fails

@tensorflow-jenkins test this please

Jenkins, test this please

There seems to be a newly introduced broken link in export.md and it is fixed now. Could any of the admin let Jenkins rerun the test?

Jenkins, test this please


Consider a minimal program that involves at least two cgo packages, both of which with Objective-C code:
cd $(mktemp -d)
go mod init test
mkdir p1 p2
echo 'package p1; import "C"' > p1/p1.go
echo 'package p2; import "C"' > p2/p2.go
touch p1/p1.m p2/p2.m
echo 'package main; import (_ "test/p1"; _ "test/p2"); func main() {}' > main.go

I tried to build it on macOS Sonoma 14.5 with Xcode 15.4 without custom flags:
go build

What did you see happen?
A warning is printed:
# test
ld: warning: ignoring duplicate libraries: '-lobjc'

What did you expect to see?
No warning printed.

I believe this is a minified reproduce for an issue like https://github.com/fyne-io/fyne/issues/4502.
The duplicate library outcome for 2+ cgo packages with Objective-C has likely been happening for a while, but what's changed recently is that the new linker in Xcode 15 causes the duplicate library to be printed as a warning unless -ldflags=-extldflags=-Wl,-no_warn_duplicate_libraries is used to disable duplicate library warnings. See [1], [2].
[1]: issue #61229 ("cmd/link: issues with Apple's new linker in Xcode 15 beta")
[2]: https://indiestack.com/2023/10/xcode-15-duplicate-library-linker-warnings/
CC @matloob, @cherrymui.

In the general case we can't drop duplicate libraries, because traditional Unix linkers search the library at a specific point on the command line.  It's normal for people to write things like -lgcc -lc -lgcc, which would perhaps generate a warning with this new linker.  So while it would be fine to change -lobjc -lobjc to just -lobjc, I'm inclined to pass the option to disable the warning.

Okay, sounds like on darwin hosts we should pass in the flags to disable the warnings. Is this something that would need to be done by the next release?

Note that if the linker in older Xcode 14 doesn't support the same flag to disable the warning, such that passing it causes an error (as mentioned in [2]), then that needs to be taken into account.
This is a warning that doesn't prevent successful compilation of programs, and it's been around since last year (Xcode 15 was publicly released in September of 2023). I think this would be good to fix when possible, since go build printing warnings on valid programs isn't a good experience, but it doesn't need to block the next release.

We can pass the flag in the Go linker to the C linker only when the flag is supported.
That said, as -lobjc is passed from cmd/go, can it just pass it once? That is, only add -lobjc if not already added.

Is that the preferred solution? To just pass in -lobjc once?

Personally I would prefer passing -lobjc just once, for a more targeted fix, if that isn't too complicated.
The duplicate libraries warning doesn't seem to be really helpful anyway. But as the Apple linker decides to emit it, if we don't have a strong reason to suppress it, we may well just keep it. If there is a reason that it is hard for us to avoid passing a -l flag multiple times, I'd be also happy to just suppress it.

If I'm understanding this correctly, this seems like something we'd have to fix in cmd/link, right?
My understanding is that the go command passes in -lobjc to the ldflags flag when invoking the cgo command. cgo in turn places its ldflags into a //go:cgo_ldflag directives in a generated go file. They in turn end up in the object files and are collected by the linker to pass to the host linker. To fix this in the go command we'd essentially have to not pass in the ldflag to each of the cgo invocations but just pass it in once at the end to the linker? I'm not too familiar with the guts of cgo but leaving that ldflag out seems wrong to me? So it seems the correct thing to do is for the linker would to see if it's about to pass in -lobjc more than once and remove the duplicates when it's calling the host linker?


Simplify ssa builder

[x] This has been discussed in issue #1259
[x] A short description of what this does, why it is needed;
Fixes #1259

Update info

Remove redundant structs/fields/methods/functions from cranelift/frontend/src/ssa.rs
Adapt FunctionBuilder to updated SSABuilder
Update docs
Update tests

[x] This PR contains test cases, if meaningful.
[x] A reviewer from the core maintainer team has been assigned for this PR.
r? @bnjbvr  @eqrion

Could you please add Fixes #1259 to the PR description? That way github will automatically close the issue when this PR is merged.

The CI failure here is likely due to running out of disk space. Would you mind rebasing this on master, which has several fixes to reduce the size of the build directory?

Thanks!


Remove possiblity of semi-remote work for python-dev position

Can you make this PR to dev branch?

FYI, I think you can change the merge target branch directly in Github if you click on the "Edit" button of an open PR in the top right. I will create a new PR nonetheless.


Unhighlighted button text UNDER the background image?

I had to just do a minimal information input to see what it is supposed to look like when you are on a screen to play and episode.  Apparently now when viewing an episode's info the Play/Continue Playing button is highlighted and you can see an icon and text, but the button next to it has text only and no button icon.  The text goes from unhighlighted being white to black when the button is highlighted.
So I can now see why I never say the text in the button when it was highlighted, because I set all fonts to white, BUT I also see no text for the unactive button (which ought to be white and visible, since I have a dark background).  But there is just empty space.
So is is all unactive/not highlighted button text being written before (or under) the background image?
I can see it when there is no background image specified.  (???)
These are the 3 views when the 3 different buttons are highlighted and I have my dark background image that the white text of inactive buttons ought to be visible on.
Also, is one of the Font entries specifically for these buttons and nothing else?

I guess I should also note that I changed all of the fonts to system fonts, except for the only 12K "genericons.regular.otf" and I think is just used for the round dot between video info/characteristics on that line under the title.
So if there is something in those buttons that won't work with system fonts that would be good to know.

Just testing again with the original ZIP from the wizard it has to be the font and something not liking to use the System Fonts rather than what it was from the wizard.  Because I can see the white text when not highlighted and black text in the the highlighted button with my selected background image.
Which of the fonts in the list is for those buttons and it is ONLY for those buttons?  (???)
I don't know about for anybody else, but for me it would be extremely helpful to have a comment associated with each font setting that says what labeling/text that font name is used for in the channel.

I just remembered something else that came to mind when first viewing the latest arrangement of things. . . .
Is there a reason why the icon for the Play or Play all or anything else isn't visible along with the text description even when the button isn't highlighted?  It seems clearer to me to have everything applicable (not Continue if nothing has been played yet, for example) visible initially and then just put a box around the active/selected button.  The way it is now the text appears but the icon for the button is only visible when it is highlighted.  (???)
I also liked the top to bottom (vertical)  listing/display of buttons better than the current horizontal version.

This issue is caused by the changes you've made.  The button font is set in the DetailsScreen.brs file in the function SetButtonFont.  The code uses a Roku ButtonGroup object.  As such,  the rendering of the buttons is handled by that object.
I also liked the top to bottom (vertical) listing/display of buttons better than the current horizontal version.
Keep in mind, I cannot design the code for a specific user's specifications.  I'm trying to keep the code as generic as possible so that each user can make any changes that meet their own needs.

Keep in mind, I cannot design the code for a specific user's specifications. I'm trying to keep the code as generic as possible so that each user can make any changes that meet their own needs.

Obviously, at some point somebody decided to change the "generic" - because the current (active on Roku) channel (based on "beta2" has things in vertical arrangement and not the current horizontal one.  :))

This issue is caused by the changes you've made. The button font is set in the DetailsScreen.brs file in the function SetButtonFont. The code uses a Roku ButtonGroup object. As such, the rendering of the buttons is handled by that object.

OK, I found the location that lists the font it wants to use for the button.  I'm guessing it has to be a font that allows size adjustment and that is why the simple system font doesn't work right.
It appears (based on a search for "pkg:/fonts/" and going through all the files) that those 2 font settings are the only ones that are somewhere OTHER THAN in the "fontsupport.brs" file.

I'm fine with the White and Black font colors, but where are those set, since I don't see the colors specified in there.
Oh, you can see I set the font to 24 (after I pasted the "Gotham-Medium.otf" back in the fonts subdirectory) and it is much nicer.  I (and presumably everybody else) can see it now and the buttons don't look like an afterthought, kind of hidden.  :)

Oh, I was also going to say if you put the button font setting in the file with all the other ones I would suggest calling it "ButtonFont" or something so people can easily adjust just those and not have to worry about changing everything else associated with the font names already in there.

Font issues resolved in version <IP_ADDRESS>.  This update should make it easier to manage screen field fonts, colors, etc.


Get sha of the image after Container.From

References https://github.com/dagger/dagger/issues/4516
The following PR contains the proposal for https://github.com/dagger/dagger/issues/4516

introduced imageRef field to the container payload
exposed the imageRef as "sha" in the api
logic is to get the image ref in From() and set it to the container payload and if there are any modifications to the container with* methods, then make it empty and when it is empty, throw an error as suggested in the issue.
introduced a new method containerFromPayload(payload) as it can be reused in multiple places.
Generated sdk for node, go and python
Tested the following scenarios:
I/P:

        {
               container {
			from(address:"alpine-latest") {
				sha
			}
		}
	}

O/P:
 {
    "container": {
        "from": {
            "sha": "7cd52847ad775a5ddc4b58326cf884beee34544296402c6292ed76474c686d39"
        }
    }
}

I/P:
        {
		container {
			from(address:"hello-world") {
				exec(args:["/hello"]) {
				  sha
				}
			  }

		}
	}

O/P:
Error: failed to solve: Image sha can only be retrieved immediately after the 'Container.From' call. Error in fetching sha as the container image is changed

@sipsma if you get some time, can you review this PR. Thanks.

@sipsma if you get some time, can you review this PR. Thanks.

@LokeshN As an FYI, @sipsma is on vacation this week.
@vito / @aluzzardi: Could one of you take a look?

@sipsma if you get some time, can you review this PR. Thanks.

@LokeshN As an FYI, @sipsma is on vacation this week.
@vito / @aluzzardi: Could one of you take a look?

Thanks @jlongtine for the help!

Thanks for starting on this, and sorry for the wait! Left some feedback inline. We'll also need a test for this, which can be added to core/integration/container_test.go.
It looks like our contributing docs could use some updates, so here's a quick primer:
It looks like you already figured out how to regenerate the SDK, but for posterity it's ./hack/make sdk:all:generate.
This command will build and run a local engine with your latest changes and run the integration tests:
./hack/dev go test ./core/integration

There are a lot of tests, so you might want to focus yours:
./hack/dev go test -v ./core/integration -run TestFooBar

Thanks @vito 🙏 . Fixed the issues and added tests.


add \oiint from esint package

https://ctan.org/tex-archive/macros/latex/contrib/esint

\oiint is also available in mathdesign, mathabx, MdSymbol, MnSymbol, txfonts, pxfonts, stix, fdsymbol, and fourier.

Also \otint, which is available in mathdesign, MdSymbol, txfonts, pxfonts, stix, fdsymbol, and fourier.

Partially addressed by https://github.com/Khan/KaTeX/pull/1430, though @ronkok says

comes at the cost of several exceptions cluttering up the code. I would be happy to see someone come along and replace this with font glyphs.

So perhaps we should leave this issue open.


Expose Lookup gate

I realised the gate of the Lookup gate was not exposed in berkeley. It will be needed in some gadgets of Keccak+ECDSA, so we should have it for Berkeley. This PR addresses it.
This was part of https://github.com/MinaProtocol/mina/pull/13606, making it now a separate PR for ease of review.

!ci-build-me


vCenter:snapshot+poweron=disk metadata is corrupted and you have snapshots

I'm using OpenNebula 5.8.5 to provide console and power control to a vCenter cluster.
All VMs are imported from Wilds.
Once imported, I've found that I can take a VM snapshot (Snapshots->Take snapshot).
However, following this it is not possible to poweron the VM from within OpenNebula due to the following error:

Mon Oct 14 14:01:38 2019 [Z0][VMM][I]: Command execution failed (exit code: 255): /var/lib/one/remotes/vmm/vcenter/deploy '/var/lib/one/vms/71/deployment.1' 'vfcc1' 71 vfcc1
Mon Oct 14 14:01:38 2019 [Z0][VMM][E]: deploy: Deploy of VM 71 on vCenter cluster vfcc1 with /var/lib/one/vms/71/deployment.1 failed due to "disk metadata is corrupted and you have snapshots"on the attempt #1.

It has happened on both VMs which I tested so far.
The same problem happens for snapshots taken from vCenter and from OpenNebula.
Are there any particular logs or information which might help?

Can you provide the "onevm show -x" of the VM in a gist?

Here you go: onevm show -x 72

Thanks a lot. We need to check now the .vmx of the VM, can you also provide that?

Here is the VMX: colm-ubuntu1.vmx

The "opennebula.disk.*" attribute is missing from the .vmx, this is what is triggering the error. Can you import a new Wild, and check if the .vmx file has these parameters?

I've imported a wild which was turned off and this resulted in the addition of the following attributes to the vmx file:

remotedisplay.vnc.enabled = "TRUE"
remotedisplay.vnc.port = "5974"
remotedisplay.vnc.ip = "<IP_ADDRESS>"

If I turn that VM on and off from OpenNebula and check the vmx, I see the addition of the following attributes:

opennebula.vm.running = "yes"
guestinfo.opennebula.context = "IyBDb250ZXh0IHZhcmlhYmxlcyBnZW5lcmF0ZWQgYnkgT3Blbk5lYnVsYQpE|0ASVNLX0lEPScyJwpFVEgwX0NPTlRFWFRfRk9SQ0VfSVBWND0nJwpFVEgwX0RO|0AUz0nJwpFVEgwX0VYVEVSTkFMPScnCkVUSDBfR0FURVdBWT0nJwpFVEgwX0dB|0AVEVXQVk2PScnCkVUSDBfSVA9JycKRVRIMF9JUDY9JycKRVRIMF9JUDZfUFJF|0ARklYX0xFTkdUSD0nJwpFVEgwX0lQNl9VTEE9JycKRVRIMF9NQUM9JzAwOjUw|0AOjU2Ojg0OjZlOmU4JwpFVEgwX01BU0s9JycKRVRIMF9NVFU9JycKRVRIMF9O|0ARVRXT1JLPScnCkVUSDBfU0VBUkNIX0RPTUFJTj0nJwpFVEgwX1ZMQU5fSUQ9|0AJycKRVRIMF9WUk9VVEVSX0lQPScnCkVUSDBfVlJPVVRFUl9JUDY9JycKRVRI|0AMF9WUk9VVEVSX01BTkFHRU1FTlQ9JycKTkVUV09SSz0nWUVTJwpTU0hfUFVC|0ATElDX0tFWT0nJwpUQVJHRVQ9J2hkYicK|0A"
uuid.location = "56 4d ee bd 81 d8 d2 6e-d3 8e df 20 9d d6 97 3b"

No sign of any opennebula.disk.* attributes.

We believe we have found the error in the code.
We will send you a patch as soon as we can so you can try.

Check documentation

[ONE]

https://github.com/OpenNebula/one/pull/4055

[DOC]

https://github.com/OpenNebula/docs/pull/961

[DEV]

https://github.com/OpenNebula/development/pull/853


Update restore.md

This change is

Fixes: https://github.com/cockroachdb/docs/issues/8992

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/91eeca12747f7096d8edef094b8d2b5e14e2ed92/
Edited pages:

v20.2/restore.md


[P4_Symbolic] Modified conditional_sequence.smt2

Keyword Check:
~/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/tools/keyword_checks.sh .
Keyword check Passed.
Build Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
Starting local Bazel server and connecting to it...
INFO: Analyzed 529 targets (251 packages loaded, 22556 targets configured).
INFO: Found 529 targets...
INFO: Elapsed time: 88.447s, Critical Path: 15.39s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
Test Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 529 targets (0 packages loaded, 330 targets configured).
INFO: Found 353 targets and 176 test targets...
INFO: Elapsed time: 182.786s, Critical Path: 120.31s
INFO: 185 processes: 220 linux-sandbox, 18 local.
INFO: Build completed successfully, 185 total actions
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 0.8s
//gutil:proto_ordering_test                                              PASSED in 1.2s
//gutil:proto_test                                                       PASSED in 0.6s
//gutil:status_matchers_test                                             PASSED in 0.6s
//gutil:test_artifact_writer_test                                        PASSED in 0.7s
//gutil:testing_test                                                     PASSED in 0.5s
//gutil:timer_test                                                       PASSED in 5.0s
//p4rt_app/tests:role_test                                               PASSED in 1.6s
//p4rt_app/tests:state_verification_test                                 PASSED in 3.4s
//p4rt_app/tests:vrf_table_test                                          PASSED in 2.6s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.1s
//p4rt_app/utils:table_utility_test                                      PASSED in 1.1s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.9s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.1s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 0.6s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.9s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 1.4s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 1.0s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 3.3s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 0.9s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.8s
//thinkit:bazel_test_environment_test                                    PASSED in 0.6s
//thinkit:generic_testbed_test                                           PASSED in 1.1s
//thinkit:mock_control_device_test                                       PASSED in 0.5s
//thinkit:mock_generic_testbed_test                                      PASSED in 1.1s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.7s
//thinkit:mock_ssh_client_test                                           PASSED in 0.1s
//thinkit:mock_switch_test                                               PASSED in 0.8s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 1.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 63.3s
Stats over 5 runs: max = 63.3s, min = 1.3s, avg = 45.2s, dev = 22.3s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.9s
Stats over 5 runs: max = 0.9s, min = 0.7s, avg = 0.8s, dev = 0.1s
Executed 176 out of 176 tests: 176 tests pass.
INFO: Build completed successfully, 185 total actions

Co-authored-by: kheradmandG<EMAIL_ADDRESS>


Game Only Recognizes Gyro Controls

When I try to configure my controller on Resident Evil 3, The game always puts "X Rotation (-)", I tried disabling gyro controls but can't find the option to do so

need option to disable gyro. very annoying, and utterly useless for most direct input mapping systems.


Add initial support for hppa-unknown-linux-gnu

Add libc-files to allow rust to be used on the hppa/parisc platform.
Signed-off-by: Helge Deller<EMAIL_ADDRESS>

Is there an opening request to add hppa-unknown-linux-gnu as an official target? I'd like to accept if the target is accepted on rust-lang/rust because official targets have explicit maintainers, e.g. https://github.com/rust-lang/rust/blob/master/src/doc/rustc/src/platform-support/fuchsia.md#target-maintainers, and we can know if a target is still active or not, i.e. when rust-lang/rust drops the support we could follow that. This helps our maintenance work.

On Dec 12, 2022, at 7:13 PM, Helge Deller @.***> wrote:Similar to pull request #2414 (which is from @glaubitz for m68k), I helped Adrian @glaubitz to fill in the pieces for hppa (this pull request). Both arches are planned to use the Libgccjit codegen (rust-lang/rust#87260) but to be able to continue on this we need the libc merged first.That’s not quite correct. m68k does actually have a LLVM backend and if my memory serves right, the Rust compiler part was merged first and then came the libc part.

Repeating https://github.com/rust-lang/libc/pull/3032#issuecomment-1345420118, but I'm not talking about technical requirements but maintenance burden. It'd be quite hard to maintain the crate if we accepted all the targets unconditionally (actually, we have received some requests about an unofficial target and decisions were very difficult to make about who to contact, how much use this target is getting, and whether it is safe to delete it, etc.).

On Dec 14, 2022, at 12:41 PM, Yuki Okushi @.***> wrote:
Repeating #3032 (comment), but I'm not talking about technical requirements but maintenance burden. It'd be quite hard to maintain the crate if we accepted all the targets unconditionally (actually, we have received some requests about an unofficial target and decisions were very difficult to make about who to contact, how much use this target is getting, and whether it is safe to delete it, etc.).
What about adding a MAINTAINERS file?I’d be happy to take responsibility of m68k, powerpc, ppc64be and sparc64, for example.Helge would take responsibility for hppa.

Yes, I'd be happy to maintain the hppa part.

It still adds maintenance burden to the libc maintainers to make the list up-to-date. I'm also not sure why forked libc repo doesn't work while they use a custom target, so I'd still prefer following the rustc's target support.

It still adds maintenance burden to the libc maintainers to make the list up-to-date. I'm also not sure why forked libc repo doesn't work while they use a custom target, so I'd still prefer following the rustc's target support.

Because Linux distributions don't use forked packages. There is one version of every package.
If individual Rust crates refuse to add support for architectures that are supported by other Rust compilers, I'm not sure what the point of additional Rust compilers with broader architecture support is.
I also don't think there is really a huge burden of maintenance when adding new architectures to the libc crate. It's not that the SysV ABI of a given architecture is a moving target.

I didn't think of Linux distribution packages, could you give me to think about adding a new target? I believe we definitely establish a policy for that.

We can postpone this until support for hppa has been added through the rustc_codegen_gcc backend since then support for this architecture will also be part of the official Rust compiler.

There has been an intention to establish a policy for "candidate targets" for some time. These would be essentially a way of defining targets that we (as in rustc) does not have support for, nor even expect to add support for soon, but would consider adding, without actually defining them in-code. It would be a way of essentially, openly discussing, "if we could add this target, roughly what would it look like?" so that other Rust compilers could come to agreement with us, so that software would be portable, and so that future possible targets could inform design decisions. This wouldn't necessarily e.g. handle cross-compiler ABI issues, since repr(Rust) remains unspecified for now.
This policy hasn't been formalized yet, it's still something people are kicking around, but it would likely alleviate the pressure here.

:umbrella: The latest upstream changes (presumably #3525) made this pull request unmergeable. Please resolve the merge conflicts.

What's the status of this?
What is blocking this PR from being merged?

Oops... I rebased that pull request and updated the branch, but hppa-devel3 (the updated patch) is again available at
https://github.com/hdeller/libc/tree/hppa-devel3
Can this branch be included here in this pull request again?

Shall I open a new pull request, or what is the best way?


herwig: 7.2.1 -> 7.2.2

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114205 at 116108e2 run on aarch64-linux 1

1 package marked as broken and skipped:

herwig

1 package built:

thepeg

2 suggestions:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/libraries/physics/herwig/default.nix:31:5:
   |
31 |     license = licenses.gpl3;
   |     ^

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/libraries/physics/thepeg/default.nix:25:5:
   |
25 |     license = licenses.gpl3;
   |     ^


[windows] Key Events Not Working

Steps to Reproduce

App Code

import 'dart:io';

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Focus(
        focusNode: FocusNode(),
        onKey: (_, __) {
          print("Key Pressed>> $_ $__");
          return KeyEventResult.ignored;
        },
        child: Listener(
          behavior: HitTestBehavior.translucent,
          onPointerSignal: (_) {
            print("pointerSignal>> $_");
          },
          onPointerHover: (_) {
            print("__>> $_");
          },
          onPointerPanZoomStart: (_) {
            print("onPointerPanZoomStart>> $_");
          },
          onPointerPanZoomUpdate: (_) {
            print("onPointerPanZoomUpdate>> $_");
          },
          onPointerPanZoomEnd: (_) {
            print("onPointerPanZoomEnd>> $_");
          },
          child: Center(
            // Center is a layout widget. It takes a single child and positions it
            // in the middle of the parent.
            child: Column(
              // Column is also a layout widget. It takes a list of children and
              // arranges them vertically. By default, it sizes itself to fit its
              // children horizontally, and tries to be as tall as its parent.
              //
              // Invoke "debug painting" (press "p" in the console, choose the
              // "Toggle Debug Paint" action from the Flutter Inspector in Android
              // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
              // to see the wireframe for each widget.
              //
              // Column has various properties to control how it sizes itself and
              // how it positions its children. Here we use mainAxisAlignment to
              // center the children vertically; the main axis here is the vertical
              // axis because Columns are vertical (the cross axis would be
              // horizontal).
              mainAxisAlignment: MainAxisAlignment.center,
              children: <Widget>[
                const Text(
                  'You have pushed the button this many times:',
                ),
                Text(
                  '$_counter',
                  style: Theme.of(context).textTheme.headline4,
                ),
              ],
            ),
          ),
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Now, flutter run -d windows
flutter doctor -v

[√] Flutter (Channel stable, 3.3.0, on Microsoft Windows [Version 10.0.19044.1889], locale en-IN)
    • Flutter version 3.3.0 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ffccd96b62 (35 hours ago), 2022-08-29 17:28:57 -0700
    • Engine revision 5e9e0e0aa8
    • Dart version 2.18.0
    • DevTools version 2.15.0

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\ashut\AppData\Local\Android\sdk
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.3.1)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.3.32811.315
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2021.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[√] VS Code (version 1.70.2)
    • VS Code at C:\Users\ashut\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.46.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19044.1889]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 104.0.5112.102
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 104.0.1293.70

[√] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

 logs

__>> _TransformedPointerHoverEvent#f3e71(position: Offset(749.0, 74.0))
flutter: __>> _TransformedPointerHoverEvent#f617c(position: Offset(725.0, 107.0))
flutter: __>> _TransformedPointerHoverEvent#5764e(position: Offset(696.0, 124.0))
flutter: __>> _TransformedPointerHoverEvent#8bf21(position: Offset(663.0, 134.0))
flutter: __>> _TransformedPointerHoverEvent#7c506(position: Offset(630.0, 145.0))
flutter: __>> _TransformedPointerHoverEvent#701ce(position: Offset(606.0, 149.0))
flutter: __>> _TransformedPointerHoverEvent#ab9fe(position: Offset(598.0, 151.0))
flutter: __>> _TransformedPointerHoverEvent#910a4(position: Offset(597.0, 152.0))
flutter: __>> _TransformedPointerHoverEvent#4eb01(position: Offset(597.0, 155.0))
flutter: __>> _TransformedPointerHoverEvent#8c1d1(position: Offset(597.0, 163.0))
flutter: __>> _TransformedPointerHoverEvent#1b975(position: Offset(601.0, 173.0))
flutter: __>> _TransformedPointerHoverEvent#dd68e(position: Offset(607.0, 187.0))
flutter: __>> _TransformedPointerHoverEvent#231c4(position: Offset(610.0, 201.0))
flutter: __>> _TransformedPointerHoverEvent#6ac46(position: Offset(614.0, 214.0))
flutter: __>> _TransformedPointerHoverEvent#20837(position: Offset(614.0, 224.0))
flutter: __>> _TransformedPointerHoverEvent#22dcd(position: Offset(614.0, 233.0))
flutter: __>> _TransformedPointerHoverEvent#4f13d(position: Offset(612.0, 242.0))
flutter: __>> _TransformedPointerHoverEvent#71156(position: Offset(608.0, 251.0))
flutter: __>> _TransformedPointerHoverEvent#92564(position: Offset(602.0, 260.0))
flutter: __>> _TransformedPointerHoverEvent#e17d0(position: Offset(598.0, 264.0))
flutter: __>> _TransformedPointerHoverEvent#b0e6d(position: Offset(590.0, 272.0))
flutter: __>> _TransformedPointerHoverEvent#0aaaf(position: Offset(585.0, 279.0))
flutter: __>> _TransformedPointerHoverEvent#a6f7f(position: Offset(582.0, 285.0))
flutter: __>> _TransformedPointerHoverEvent#7e3bb(position: Offset(580.0, 290.0))
flutter: __>> _TransformedPointerHoverEvent#145e8(position: Offset(579.0, 294.0))
flutter: __>> _TransformedPointerHoverEvent#adc45(position: Offset(579.0, 298.0))
flutter: __>> _TransformedPointerHoverEvent#10fff(position: Offset(579.0, 299.0))
flutter: __>> _TransformedPointerHoverEvent#cbcb4(position: Offset(579.0, 300.0))
flutter: __>> _TransformedPointerHoverEvent#b56cf(position: Offset(579.0, 301.0))
flutter: __>> _TransformedPointerHoverEvent#d942b(position: Offset(581.0, 303.0))
flutter: __>> _TransformedPointerHoverEvent#83297(position: Offset(584.0, 303.0))
flutter: __>> _TransformedPointerHoverEvent#48c60(position: Offset(588.0, 303.0))
flutter: __>> _TransformedPointerHoverEvent#302d7(position: Offset(591.0, 305.0))
flutter: __>> _TransformedPointerHoverEvent#f372e(position: Offset(596.0, 305.0))
flutter: __>> _TransformedPointerHoverEvent#748d5(position: Offset(601.0, 306.0))
flutter: __>> _TransformedPointerHoverEvent#9c8ea(position: Offset(604.0, 308.0))
flutter: __>> _TransformedPointerHoverEvent#70723(position: Offset(606.0, 308.0))
flutter: __>> _TransformedPointerHoverEvent#7dcf2(position: Offset(608.0, 309.0))
flutter: __>> _TransformedPointerHoverEvent#0ea6c(position: Offset(609.0, 310.0))
flutter: __>> _TransformedPointerHoverEvent#d9665(position: Offset(609.0, 311.0))
flutter: __>> _TransformedPointerHoverEvent#06a45(position: Offset(611.0, 314.0))
flutter: __>> _TransformedPointerHoverEvent#16ed3(position: Offset(613.0, 316.0))
flutter: __>> _TransformedPointerHoverEvent#d7656(position: Offset(616.0, 317.0))
flutter: __>> _TransformedPointerHoverEvent#7f58b(position: Offset(621.0, 320.0))
flutter: __>> _TransformedPointerHoverEvent#9ae5c(position: Offset(625.0, 322.0))
flutter: __>> _TransformedPointerHoverEvent#3cd02(position: Offset(628.0, 322.0))
flutter: __>> _TransformedPointerHoverEvent#2c26a(position: Offset(630.0, 322.0))
Unable to parse JSON message:
The document is empty.
Unable to parse JSON message:
The document is empty.
Unable to parse JSON message:
The document is empty.
Unable to parse JSON message:
The document is empty.
Unable to parse JSON message:
The document is empty.

======== Exception caught by services library ======================================================
Unable to parse JSON message:
The document is empty.

 KeyRepeatEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in `HardwareKeyboard`. This was the event: KeyRepeatEvent#d2858(physicalKey: PhysicalKeyboardKey#700e0(usbHidUsage: "0x000700e0", debugName: "Control Left"), logicalKey: LogicalKeyboardKey#00100(keyId: "0x200000100", keyLabel: "Control Left", debugName: "Control Left"), character: null, timeStamp: 42:02:34.697007)
'package:flutter/src/services/hardware_keyboard.dart':
Failed assertion: line 432 pos 16: '_pressedKeys.containsKey(event.physicalKey)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      HardwareKeyboard._assertEventIsRegular.<anonymous closure> (package:flutter/src/services/hardware_keyboard.dart:432:16)
#3      HardwareKeyboard._assertEventIsRegular (package:flutter/src/services/hardware_keyboard.dart:443:6)
#4      HardwareKeyboard.handleKeyEvent (package:flutter/src/services/hardware_keyboard.dart:535:5)
#5      KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:881:37)
#6      BasicMessageChannel.setMessageHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:197:49)
#7      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:387:35)
#8      _invoke2 (dart:ui/hooks.dart:186:13)
#9      _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5)
#10     _Channel.push (dart:ui/channel_buffers.dart:132:31)
#11     ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17)
#12     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:599:22)
#13     _dispatchPlatformMessage (dart:ui/hooks.dart:89:31)
(elided 2 frames from class _AssertionError)
====================================================================================================

I'm having this issue too. Happened when I upgraded to 3.3. Apparently, someone posted about it here: https://stackoverflow.com/questions/73469047/flutter-desktop-on-long-press-returns-error-windows
It happens when you hold down Ctrl, Alt, or Shift.

@ashutosh2014 @impure
I believe this is same issue as https://github.com/flutter/flutter/issues/108646 which was fixed and merged to Master branch. https://github.com/flutter/flutter/issues/108646#issuecomment-1200947402, I am not sure if the fix made it to stable because the cherry-pick request was closed without being completed, so the issue could still be in stable version.
I suggest you both to switch to latest master and try again to see if you still get same error or not.
flutter channel master
flutter upgrade

Hi @darshankawar, thanks for sharing theses cherrypick commits.
For repeat Keys, it is fixed in master, but I'm trying to pinch-zoom from trackpad it is crashing.

======== Exception caught by services library ======================================================
The following assertion was thrown during a platform message callback:
A KeyUpEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in `HardwareKeyboard`. This was the event: KeyUpEvent#ccc70(physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x1600000000", debugName: "Key with ID 0x1600000000"), logicalKey: LogicalKeyboardKey#00100(keyId: "0x200000100", keyLabel: "Control Left", debugName: "Control Left"), character: null, timeStamp: 16:55:20.187883)
'package:flutter/src/services/hardware_keyboard.dart':
Failed assertion: line 432 pos 16: '_pressedKeys.containsKey(event.physicalKey)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      HardwareKeyboard._assertEventIsRegular.<anonymous closure> (package:flutter/src/services/hardware_keyboard.dart:432:16)
#3      HardwareKeyboard._assertEventIsRegular (package:flutter/src/services/hardware_keyboard.dart:443:6)
#4      HardwareKeyboard.handleKeyEvent (package:flutter/src/services/hardware_keyboard.dart:535:5)
#5      KeyEventManager.handleRawKeyMessage (package:flutter/src/services/hardware_keyboard.dart:954:37)
#6      BasicMessageChannel.setMessageHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:197:49)
#7      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:387:35)
#8      _invoke2 (dart:ui/hooks.dart:183:13)
#9      _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:40:5)
#10     _Channel.push (dart:ui/channel_buffers.dart:130:31)
#11     ChannelBuffers.push (dart:ui/channel_buffers.dart:326:17)
#12     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:610:22)
#13     _dispatchPlatformMessage (dart:ui/hooks.dart:86:31)
(elided 2 frames from class _AssertionError)

Thanks for checking and confirming the original use case.

pinch-zoom from trackpad it is crashing.

I believe you are hitting https://github.com/flutter/flutter/issues/95496#issuecomment-1013891281, so please follow-up in that issue for further updates.
If you are okay with that, you can close this issue as your original report is fixed on master.
Unable to parse JSON message:
The document is empty.


Chocolatey support for Paket.PowerShell

Testing locally can be done like so:
choco install Paket.PowerShell -s C:\Projects\Paket\temp --pre -y --force

Installing from NuGet can be done like so:
choco install Paket.PowerShell -s http://www.nuget.org/api/v2 -y

Once it is uploaded to or mirrored on Chocolatey, then just this will work:
choco install Paket.PowerShell -y

Should we push this to chocolatey during the build?

I think so. That is what I do for SourceLink.exe. You could also do that same for paket.

cool. It's uploaded to https://chocolatey.org/packages/Paket.PowerShell/1.14.0, but await moderator approval.

I'm pretty sure Paket's release cycle will annoy the hell out of the choco guys.

After the installation, it cannot be used in the PS console, like path is not added.

@alexeyzimarev Are you trying to use it from the Package Manager Console in Visual Studio? Are you able to use it from normal PowerShell? It worked for me with this simple test:

Did the path get added correctly to the PSModulePath?
(Get-Item Env:\PSModulePath).Value -Split ';'

The PSModulePath allows the module to be imported on demand. If that is not working, are you ale to import it manually?

@alexeyzimarev It looks like some output doesn't show up. Is that what you mean? I logged this bug and will look into it.
https://github.com/fsprojects/Paket/issues/874

No, for me it was just saying that "Paket" is not a valid command. I tried from the PS shell. Will check the path later.

This is what I got after cinst
PS D:\GitHub\Paket.VisualStudio> (Get-Item Env:\PSModulePath).Value -Split ';'
C:\Windows\system32\WindowsPowerShell\v1.0\Modules
C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\

Import gives this:

Hi @alexeyzimarev, I'm not sure why you get that error message. Can you provide the output of these commands?
$PSVersionTable
choco --version
choco list --localonly
Get-FileHash C:\ProgramData\chocolatey\lib\Paket.PowerShell\tools\Paket.PowerShell\Paket.PowerShell.dll -Algorithm SHA1 | fl

Unless I coded something wrong, C:\ProgramData\chocolatey\lib\Paket.PowerShell\tools should get added to your $PSModulePath. I've tested it on a couple of computers. Start a new PowerShell session after installing.

https://github.com/fsprojects/Paket/blob/master/src/Paket.PowerShell/Install-PSModulePath.ps1
https://github.com/chocolatey/choco/pull/327

@alexeyzimarev did you close and reopen your shell?

So forcing the import worked for me.

I did notice that you are adding a bunch of unapproved verbs, which might be why it didn't automatically import?

This might be helpful as well.

Dumb question. Does a module automatically load without a psd1/psm1 file?

Actually the dumbest possibility, did you need the trailing back slash at the end of your custom module path?

@ferventcoder There is not Paket command. If you open a new PowerShell instance and type Paket- or just pak and hit tab, do you see a list? PowerShell will import it as soon as your try running one of them. If so, the $env:psmodulepath is doing its job. I've now tried successfully on 3 computers.

I didn't, but this may be helpful
WMF 5 by the way. I added the trailing back slash and

Seems to work without the trailing backslash as well. With Paket- {tab}

so should be good to approve. :)

Approved.
With the project owners building the package, we move things to a trusted status after a few good approvals @forki.

Awesome! Thank you! Sometime this week, I hope to get a blog about how I used F# + Chocolatey + PowerShell. :-)

:)


Update lsst-login.rst

Move development documentation into lsst-login page, remove references to documentation under lsst-dev page.

(Also, would you mind using a u/billglick/...-style user branch, please?)

Yes, this is preparing for moving the documentation from the lsst-dev section over to lsst-login. Instead of linking to the lsst-dev documentation, we want the lsst-login documentation to be the default place for this, and will update the lsst-dev documentation to reference it on the lsst-login page.
Should I update the lsst-dev page along with this change?

I think it would be great to update the lsst-dev documentation in lock-step with this — so yes please!


crawl_from_commoncrawl crashes when attempting to parse the date from warc.paths.gz

Mandatory

[x] I read the documentation (readme and wiki).
[x] I searched other issues (including closed issues) and could not find any to be related. If you find related issues post them below or directly add your issue to the most related one.
[x] I confirm that this bug report does not report on a specific news site where news-please does not work. Please keep in mind that news-please is a generic crawler so it is expected that it will not work for all sites well or even at all.

Describe the bug
crawl_from_commoncrawl crashes when attempting to filter warc files by date using the timestamp at the end (inside __extract_date_from_warc_filename). This appears to be because it loops through all warc files for each month using, e.g.:
aws s3 ls --recursive s3://commoncrawl/crawl-data/CC-NEWS/2022/04/ --no-sign-request

This will return something like:
2022-04-01 03:05:03<PHONE_NUMBER> crawl-data/CC-NEWS/2022/04/CC-NEWS-20220401000546-00192.warc.gz
2022-04-01 05:05:03<PHONE_NUMBER> crawl-data/CC-NEWS/2022/04/CC-NEWS-20220401012435-00193.warc.gz
....
2022-04-05 11:05:03<PHONE_NUMBER> crawl-data/CC-NEWS/2022/04/CC-NEWS-20220405090411-00275.warc.gz
2022-04-05 11:05:12        698 crawl-data/CC-NEWS/2022/04/warc.paths.gz

which includes the filename "warc.path.gz" and when it attempts to parse it as a date, it crashes.
Traceback:
Traceback (most recent call last):
  File "bug_script.py", line 29, in <module>
    log_level=logging.INFO)
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 330, in crawl_from_commoncrawl
    cc_news_crawl_names = __get_remote_index(warc_files_start_date, warc_files_end_date)
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 181, in __get_remote_index
    p for p in lines if __date_within_period(
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 182, in <listcomp>
    __extract_date_from_warc_filename(p),
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 118, in __extract_date_from_warc_filename
    return datetime.datetime.strptime(dt, '%Y%m%d%H%M%S')
  File "/usr/local/lib/python3.6/_strptime.py", line 565, in _strptime_datetime
    tt, fraction = _strptime(data_string, format)
  File "/usr/local/lib/python3.6/_strptime.py", line 362, in _strptime
    (data_string, format))
ValueError: time data 'warc.paths.gz' does not match format '%Y%m%d%H%M%S'

To Reproduce
Run this script:
import os
import logging

from datetime import datetime, date, timedelta
from newsplease.crawler import commoncrawl_crawler as cc

def empty_callback(*args):
    pass

today = date.today()
today_date = datetime(today.year, today.month, today.day)

end_date = today_date - timedelta(days=1)
start_date = end_date - timedelta(days=1)

os.makedirs("./warcs/", exist_ok=True)

cc.crawl_from_commoncrawl(
    valid_hosts=["bbc.co.uk"],
    warc_files_start_date=start_date,
    warc_files_end_date=end_date,
    callback_on_article_extracted=empty_callback,
    callback_on_warc_completed=empty_callback,
    continue_after_error=True,
    local_download_dir_warc="./warcs/",
    number_of_extraction_processes=1,
    log_level=logging.INFO)

Expected behavior
crawl_from_commoncrawl should automatically ignore "warc.path.gz" and only parse the other filenames.
Log
INFO:newsplease.crawler.commoncrawl_crawler:executing: aws s3 ls --recursive s3://commoncrawl/crawl-data/CC-NEWS/2022/04/ --no-sign-request >> /tmp/tmppydqzsib && awk '{ print $4 }' /tmp/tmppydqzsib
Traceback (most recent call last):
  File "bug_script.py", line 29, in <module>
    log_level=logging.INFO)
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 330, in crawl_from_commoncrawl
    cc_news_crawl_names = __get_remote_index(warc_files_start_date, warc_files_end_date)
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 181, in __get_remote_index
    p for p in lines if __date_within_period(
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 182, in <listcomp>
    __extract_date_from_warc_filename(p),
  File "/usr/local/lib/python3.6/site-packages/newsplease/crawler/commoncrawl_crawler.py", line 118, in __extract_date_from_warc_filename
    return datetime.datetime.strptime(dt, '%Y%m%d%H%M%S')
  File "/usr/local/lib/python3.6/_strptime.py", line 565, in _strptime_datetime
    tt, fraction = _strptime(data_string, format)
  File "/usr/local/lib/python3.6/_strptime.py", line 362, in _strptime
    (data_string, format))
ValueError: time data 'warc.paths.gz' does not match format '%Y%m%d%H%M%S'

Versions

OS: MacOS 12.2, but the script is running in a Docker container with amazonlinux:latest as the base image.
Python Version: 3.6.15
news-please Version: 1.5.22

Intent

[ ] personal
[x] academic
[x] business
[ ] other
Some information on your project:
We're processing articles using CC-NEWS to create a brand sentimenting tracking system

This issue is addressed in #226.


Unsigned right shift

PHP supports only signed integers and does not have unsigned right shift operation (>>>). As a result this implementation may produce different results than other murmur3 implementations. If I replace all >> operations with a function that performs unsigned right shift, then the results are back to normal.
One of the implementations for the shift may be found on StackOverflow, I copy it here for convenience:
function uRShift($a, $b)
{
if($b == 0) return $a;
return ($a >> $b) & ~(1<<(8*PHP_INT_SIZE-1)>>($b-1));
}
Thanks.

Can you make a pull request? Thanks.


deprecate (append) in favor of (concat)

The function for joining a list of lists together is currently called (append). It should be called (concat) for consistency with Clojure.
Also the name (append) feels more like (conj).

I would be interested to give a try at this. What's a good way to start? Also would append need to stick around as deprecated until something like v1.0.0 to avoid a breaking change or is fully replacing it already the goal?

Great! The best way to start is just regular old find and replace. Some key searches: defn append for the definition and (append for any uses. Technically there could be higher-order calls too like (apply append lists).
Here's the definition: https://github.com/vito/bass/blob/b280ab3a3ee752957fe7f8a9cad192a5294db8f8/std/root.bass#L217-L227
re: deprecation - it's probably worth trying out a real deprecation flow here for the sake of exercise. There are some usages of (append) in the wild so it'd be nice to avoid breakage. I can add an issue for removing (append) and put it in the v1.0 milestone.
Side note: if you have bass --lsp set up for your editor's LSP integration (bass.vim if you use vim) you can also go-to-definition on append in any Bass script, though it'll take you to a copy of the embedded source rather than the file in your local repo. Mostly useful for read-only introspection.

@vito I saw this is still open, it can be closed right or was there still an open point to tackle?

Oh yep, closing! I already split out a separate issue for removing (append) so this part is done. Thanks for the ping.


Theme.Sherlock.Light does not work on Android 3.1

I ran the samples app on Galaxy Tab 10.1 (Android 3.1) and changed the style to Sherlock.Light but it appeared like this:
http://dl.dropbox.com/u/1008889/ActionBarSherlock001.png

Thanks for letting me know!


[Portfolio] Validate INJ withdrawal address

Case:

Try to withdraw some INJ over Injective Protocol network.
Enter incorrect address (aka random string).
Confirm

Maybe we could add a validation there, so that user doesn't see a raw error message?

Resolved in commit https://github.com/InjectiveLabs/injective-dex/commit/2e7db049339971f13dd91015ded377dbcb6caa89

Fixed!


Add reserve form page

Summary

Added a reserve page with a form and a background image.
Added validation for the form.
Added ability to show error messages through snackbars.

Changes log

[x] Added Field.js.
[x] Added form in ReservationForm.js.
[x] Added notistack, react-day-picker, and tailwind-merge libraries.
[x] Updated App.js to include Reservation page.

Acceptance criteria

[x] It should contain car dropdown ( List of all available cars)
[x] It should contain city
[x] It should contain starting date and ending date
[x] It should have a button to confirm reservation
[x] It should have a background image of some random car
[x] The user should only pick a date >= current date and <= 30 days from current date

@Kweeka1 can you please resolve the conflicts since we pushed into the dev branch, the new changes :+1:


feat(DeferredRender): port from monolith

Overview
Ports DeferredRender from our monolith.

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.2.47-alpha.651b70.0@codecademy/gamut-labs@13.2.10-alpha.651b70.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6065e5ebd277ba55c45f4212--gamut-preview.netlify.appDeploy Logs


Update link

Update broken libxc_name link

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
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 80.04%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
1989

Relevant Lines:
2485

💛  - Coveralls


GitMoveRenameTests.GitStatusAfterRenameFileIntoRepo test failed in Mac CI build

I've just had this fail on the functional test run for #887; the changes in that PR can't possibly be causing that failure.
Errors, Failures and Warnings

1) Failed : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests(GVFS.FunctionalTests.FileSystemRunners.SystemIORunner).GitStatusAfterRenameFileIntoRepo()
  Expected substring 'Untracked files:' not found in 'On branch FunctionalTests/20180214
nothing to commit, working tree clean
'
  Expected: True
  But was:  False
   at GVFS.Tests.Should.StringShouldExtensions.ShouldContain(String actualValue, String[] expectedSubstrings) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.Tests/Should/StringShouldExtensions.cs:line 19
   at GVFS.FunctionalTests.Tools.GitHelpers.CheckGitCommandAgainstGVFSRepo(String virtualRepoRoot, String command, String[] expectedLinesInResult) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tools/GitHelpers.cs:line 55
   at GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests.GitStatusAfterRenameFileIntoRepo() in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tests/EnlistmentPerFixture/GitMoveRenameTests.cs:line 197

Run Settings
    Number of Test Workers: 16
    Work Directory: /Users/gvfsadmin/agent/_work/4/s
    Internal Trace: Off

Possibly related to #847, but probably not if this is testing that we're handling a FILEOP_RENAME event correctly?
The build is here: https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=8730781 and I have retained it.

Added additional logging in #1006 to help diagnose this issue if it happens again.  Closing the issue for now, it can be re-opened if/when the issue hits again.


Fix CreditAmount

Fix for #461

I know this: 0.0018893955352 looks ugly but I think the app should be transparent about prices

https://github.com/lbryio/lbry-app/issues/461#issuecomment-321442168

Any feedback / review would be helpful... ^^

Merged, but made some additional changes so not auto-closed by GitHub.


Disallow selecting a directory for the R executable

I just installed the R plugin and was happy that you already did all the work that comes with such a plugin. Of course, as users are, I am lazy and don't read UI text. Therefore, when I had to select an R interpreter, I chose the base directory of the R installation, which was wrong.
This triggered an exception in IntelliJ:

`java.lang.Throwable: Cannot run program "C:\Users\rillig\Program Files\R-3.6.1": CreateProcess error=5, Zugriff verweigert

In the Settings > Languages > R > R Interpreter dialog, it should only be possible to select an executable file, not a directory.

Great suggestion.


[QUARKS-165] [AWAIT-CODE-MERGE] parallel analytics recipe

await merge of https://github.com/apache/incubator-quarks/pull/104

@dlaboss, can you update the recipe to use single spaces between sentences?


Test Data Generation Script

In preparation for scale, we should have script that generates thousands of test listings.

@DanielVF feel free offer your thoughts on this.

Probably a simple node script that loads origin.js as a library and then goes to town making data.

The listings generation doesn't necessarily need to be complex either,
since any difference in a piece of content creates a different content
hash. If things like upload sizes or geolocation/geosearch have to be
tested, then specific types of test data will be required.
On Wed, Aug 22, 2018 at 6:41 AM, Daniel Von Fange<EMAIL_ADDRESS>wrote:

Probably a simple node script that loads origin.js as a library and then
goes to town making data.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OriginProtocol/origin-js/issues/360#issuecomment-415035476,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJiZ7uZjJJo1NqpYAyY0flKf0q1_5Lyks5uTV9sgaJpZM4WGsDv
.

Yay! We've got a basic version of this going in #448


pt_BR Translations fix and add.

Fixed and added some missing pt_BR translations.

Fixed a type and last minute missing translation in pt_BR.

Thanks for the extra pair of eyes in reviewing @waldyrious! Looks like this is ready to go out in its current state?

Went ahead and pushed the site with these changes but we can always update them later!

Looks like this is ready to go out in its current state?

Went ahead and pushed the site with these changes but we can always update them later!

Sorry @pcottle but I think it would have been more appropriate to give me at least a few hours (!) to react before merging the changes. As you can see from my responses above, I still disagree with some of the changes that were merged. Please hold for me and @maxoliverbr to reach a consensus before applying further changes — thanks! :pray:

Apologies! reverted for now :P

Unfortunately PRs can't be un-merged and re-merged, so I'm afraid either @maxoliverbr, you or I would need to submit a new PR. In any case, it seems like agreement has been reached in all the threads above — but if you could chime in on the first thread above, that'd be appreciated :)

Hi ! Just submitted a new PR with the rolledback translations  :)

Sorry both, I've been quite busy in the past few days. I just saw PR #1114, but I'm a bit confused — hadn't all of this PR's changes been reverted in #1113 already?
Hmm, it seems like the merged diff of #1114 is indeed empty; it's a little puzzling that the diff in the PR actually showed changed content, though.
In any case, it seems like the remaining changes from this PR (minus the reversals done in #1114) still need to be re-submitted as a new PR, right?

@waldyrious ah yes it looks like you're right -- git-dummy-msg is still the string before this pull request (Vai Timão!) rather than the string after.
there were definitely changes in #1114:
https://github.com/pcottle/learnGitBranching/pull/1114/files
but it wasn't a complete revert.
Let me know how we should proceed -- we can revert-my-revert if necessary 😅

No worries, I'll resubmit those changes as a new PR to make things easier :) I'll retain @maxoliverbr's authorship of the commit, of course.

Ok, done: #1119.


Endpoint for getting question answer details

Endpoint for getting question answer details.
GET /api/room-questions/answer
Params - RoomId, QuestionId
{
  "question": {
    "codeEditor": {
      "content": "string",
      "lang": "string"
    },
    "answerCodeEditor": { // last code editor state on this question
      "content": "string", // May be return last non empty code editor value
      "lang": "string"
    }
  },
  "transcription": [ // all transcriptions for this question
    {
      "id": "guid",
      "payload": "string",
      "createdAt": "2024-08-03T10:47:04.331Z",
      "user": {
        "id": "guid",
        "nickname": "string"
      }
    }
  ]
}

Actual response from the backend:
{
  "codeEditor": {
    "content": "string",
    "lang": "string"
  },
  "details": [
    {
      "answerCodeEditorContent": "string",
      "transcription": [
        {
          "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
          "payload": "string",
          "createdAt": "2024-09-05T11:46:30.699Z",
          "user": {
            "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "nickname": "string"
          }
        }
      ],
      "startActiveDate": "2024-09-05T11:46:30.699Z",
      "endActiveDate": "2024-09-05T11:46:30.699Z"
    }
  ]
}

@VladislavPetyukevich
Changed Payload in events in WebSocket:

AddRoomQuestion (State property)
ChangeRoomQuestionState (OldState, NewState properties)


Design and implement a keyboard trigger library

This library would receive a stream of keyboard presses and trigger a callback on the configured key or key combination.
This would ease the development of widgets or code that uses keyboard input and wants to support multi-key shortcuts.

Made obsolete, we now do what termbox does and define separate Key types for shortcuts like Ctrl-A.
Support for the Alt modifier is outstanding, but can come later.


Using asChild should not clone parent styling

When using asChild the styling from "default" component should not bleed over to the child component.
Example of bug: https://codesandbox.io/p/sandbox/frosty-architecture-39tkw4?file=%2Fsrc%2FApp.tsx%3A16%2C30

I would not call this a bug, but rather a decition we need to make.
As discussed on slack: We will make a rule that only "low level" component such as `Button, will keep their stylings (and other props).
If we make a component using a lower level component, we remove the underlying element and only render the element the user sends in, with the props we have added.
If they want i.e. a DropdownMenu trigger to be a link, they need to use asChild deeply:
<DropdownMenu.Trigger asChild>
  <Button asChild>
    <Link />
  </Button>
</DropdownMenu.Trigger>

I would not call this a bug, but rather a decition we need to make. As discussed on slack: We will make a rule that only "low level" component such as `Button, will keep their stylings (and other props). If we make a component using a lower level component, we remove the underlying element and only render the element the user sends in, with the props we have added.
If they want i.e. a DropdownMenu trigger to be a link, they need to use asChild deeply:
<DropdownMenu.Trigger asChild>

</DropdownMenu.Trigger>

Good point!
*.Trigger is more of a utility component that renders as a Button as default. If its changed using asChild it changes the underlying default rendered component (to Slot).


update procdump.md

Update punctuation.

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

File
Status
Preview URL
Details

sysinternals/downloads/procdump.md
:bulb:Suggestion
View
Details

sysinternals/downloads/procdump.md

Line 33, Column 0: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines. NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

sysinternals/downloads/procdump.md
:bulb:Suggestion
View
Details

sysinternals/downloads/procdump.md

Line 33, Column 0: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines. NOTE: This Suggestion will become a Warning in late September, 2020.

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