Inconsistent up-to-date checks when using fileTree for task outputs

Expected Behavior
When declaring task outputs I'd expect to be able to use fileTree() with include/exclude patterns.
Current Behavior
After removing an output file and running the first time, the up-to-date check is "false" and the task is executed, as expected. However, sometimes when running the task again, the up-to-date check still considers the task to be out of date.
Steps to Reproduce
The following tasks have been used to reproduce the problem:
task myTask1 {
    group 'build'
    inputs.file file('input.txt')
    outputs.file file('output1.txt')
    doLast {
        new File('output1.txt').text = new File('input.txt').text
    }
}

task myTask2 {
    group 'build'
    inputs.file file('input.txt')
    outputs.files fileTree(dir: '/', include: 'output2.txt')
    doLast {
        new File('output2.txt').text = new File('input.txt').text
    }
}

task myTask3 {
    group 'build'
    inputs.file file('input.txt')
    def outputFiles = fileTree(dir: '/', include: 'output3.txt').files
    outputs.files outputFiles
    doLast {
        new File('output3.txt').text = new File('input.txt').text
    }
}

myTask1 that uses file()
to specify the output never experiences the problem.
myTask2 experiences the problem ~5-10% of the time.
myTask3 also experiences the problem ~5-10% of the time, but only when using the gradle daemon.
Simple do this to reproduce:
rm output2.txt
./gradlew myTask2
./gradlew myTask2

Environment
Windows 7
git-bash
gradle 3.5
JVM 1.8.0_40 (Oracle)

Attaching a small project with a script test.sh to run the task several times.
gradletest-2180.tar.gz

@Loffe Thank you for your bug report.
Could you describe your use case for using fileTrees as output files? Couldn't you just have each of the tasks generate the output into its own directory and then have one Sync task which would copy the outputs to the destination?

Sure! I'm trying to integrate with a legacy CMake project.
I have a gradle task generateCmakeProject, which executes the CMake generator and the output (a VisualStudio project) is generated into a separate directory build/cmake_project. However, this output directory will also contain for example log files. A change to a log file shouldn't make the generateCmakeProject out-of-date.
Unfortunately, I cannot Sync the directory to somewhere else, since many of the generated files contains absolute paths

Are you able to describe the exact file outputs to Gradle? Like adding some single output files and a few output directories which do not contain any log files? What does the generated project structure look like?

Unfortunately, the file output structure from CMake is quite messy: ~100 directories and ~700 files.
The log files end up quite deep in a nested structure, and many of the other files and directories must be included.
Our current fileTree excludes most files based on file extension and some whole directories.
Is is most likely possible to list all outputs to gradle, but that would not be fun to maintain.
Is it supported to specify output files with fileTree?

@Loffe Regarding your example: It seems like you declare / as an output while putting the output file in the current working directory. Is this a problem in your example or of your real build?

The dir: '/' is only part of the example. However, it seems to expand in the current dir only, at least on Windows.
In the real build we use a subdirectory to the projectDir.

I changed dir: '/' to dir: '.' and it made no difference to the observed behavior

@Loffe This problem should be fixed in master and will be included in 4.1. Could you try out with a nightly build which will be released tonight?

@wolfs Thanks, I will try to verify the bugfix soon-ish :)

I am a colleague of @Loffe and we actually reported this issue together. I tested this again using the nightly build, 4.2-20170619235828+0000 and I am happy to report that I was not able to reproduce the issue. I have done a few hundred builds with a similar shell script to the one attached to the original report.
Just to be sure I also tested with gradle 3.5 again and experienced the problem with similar frequency as originally reported.
Many thanks for looking into this!

Just to be clear, I tested this with our product gradle script where I switched back to using fileTree where we changed to several files. This is where we originally experienced the problem and later tried to minimize the example as in the bug report.
We still use fileTree for the CMake case mentioned by @Loffe so it will be nice to get this fix into our build system.


python312Packages.clarifai-grpc: 10.3.0 -> 10.3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.clarifai-grpc is: Clarifai gRPC API Client
meta.homepage for python312Packages.clarifai-grpc is: https://github.com/Clarifai/clarifai-python-grpc
meta.changelog for python312Packages.clarifai-grpc is: https://github.com/Clarifai/clarifai-python-grpc/releases/tag/10.3.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.3.0 with grep in /nix/store/zpadgnzzhg5rp4iws3s4a7zhadxxcnv9-python3.12-clarifai-grpc-10.3.0
found 10.3.0 in filename of file in /nix/store/zpadgnzzhg5rp4iws3s4a7zhadxxcnv9-python3.12-clarifai-grpc-10.3.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.clarifai
python311Packages.clarifai-grpc
python312Packages.clarifai
python312Packages.clarifai-grpc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zpadgnzzhg5rp4iws3s4a7zhadxxcnv9-python3.12-clarifai-grpc-10.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.clarifai-grpc https://github.com/r-ryantm/nixpkgs/archive/2b67edc598a783cbce38de4e5f29ea1b24473841.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2b67edc598a783cbce38de4e5f29ea1b24473841#python312Packages.clarifai-grpc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zpadgnzzhg5rp4iws3s4a7zhadxxcnv9-python3.12-clarifai-grpc-10.3.0
ls -la /nix/store/zpadgnzzhg5rp4iws3s4a7zhadxxcnv9-python3.12-clarifai-grpc-10.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages built:

python311Packages.clarifai
python311Packages.clarifai-grpc
python311Packages.clarifai-grpc.dist
python311Packages.clarifai.dist
python312Packages.clarifai
python312Packages.clarifai-grpc
python312Packages.clarifai-grpc.dist
python312Packages.clarifai.dist

Maintainer pings
cc @natsukium for testing.

@ofborg eval

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.clarifai-grpc is: Clarifai gRPC API Client
meta.homepage for python312Packages.clarifai-grpc is: https://github.com/Clarifai/clarifai-python-grpc
meta.changelog for python312Packages.clarifai-grpc is: https://github.com/Clarifai/clarifai-python-grpc/releases/tag/10.3.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.3.1 with grep in /nix/store/i0ldbw4s2hh8jj7vax54d9wq7qfr6hhz-python3.12-clarifai-grpc-10.3.1
found 10.3.1 in filename of file in /nix/store/i0ldbw4s2hh8jj7vax54d9wq7qfr6hhz-python3.12-clarifai-grpc-10.3.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.clarifai
python311Packages.clarifai-grpc
python312Packages.clarifai
python312Packages.clarifai-grpc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i0ldbw4s2hh8jj7vax54d9wq7qfr6hhz-python3.12-clarifai-grpc-10.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.clarifai-grpc https://github.com/r-ryantm/nixpkgs/archive/abfcfcb72ee33cca43f8c3e7bfbf09bb3a4caed4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/abfcfcb72ee33cca43f8c3e7bfbf09bb3a4caed4#python312Packages.clarifai-grpc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i0ldbw4s2hh8jj7vax54d9wq7qfr6hhz-python3.12-clarifai-grpc-10.3.1
ls -la /nix/store/i0ldbw4s2hh8jj7vax54d9wq7qfr6hhz-python3.12-clarifai-grpc-10.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages built:

python311Packages.clarifai
python311Packages.clarifai-grpc
python311Packages.clarifai-grpc.dist
python311Packages.clarifai.dist
python312Packages.clarifai
python312Packages.clarifai-grpc
python312Packages.clarifai-grpc.dist
python312Packages.clarifai.dist

Maintainer pings
cc @natsukium for testing.

Already on master.


Add Carthage support

Update DFImageManagerKit target to build independently of CocoaPods. Carthage build would be similar as build that is used for Playground (with no dependencies).

Done


How does ns-export pointcloud work?

Describe the bug
I'm trying to export a point cloud from nerfstudio, and I tried 2 methods.

render the depth by ns-render camera-path command, and the camera path is manually created using the outputs of ns-export cameras and convert the depth (with known camera intrinsics) into a point cloud.
just run ns-export command

Expected behavior
I'm not sure, but when I open the 2 point clouds in meshlab, I found desk in method 1's point cloud is not so flat, but the desk in method 2's point cloud is more flat and realistic.
Screenshots

method 1's point cloud:

method 2's point cloud:

So how does the ns-export pointcloud generate the points? Is there a given camera pose or is it fused by many results of different poses?

This is one of the (many) parts of the code I don't know too well, but I did a skim of the point cloud generation function and:

Are you computing 3D points in the same way as the nerfstudio exporter does it?
https://github.com/nerfstudio-project/nerfstudio/blob/6d51af1a24d692d073a9e0cda06278b6a9d44818/nerfstudio/exporter/exporter_utils.py#L154
Notably, the "depth" value looks like it should be a distance from camera origin, as opposed to a traditional Z-depth.

Is there a given camera pose or is it fused by many results of different poses?

From the snippet, it looks like points are generated by rendering from the training views.

by the way, the coordinates of results of ns-export pointcloud are world coordinates or camera space coordinates?

It looks like world coordinates to me! (but the scaled NeRF ones)

thank you for your reply! I dig into the code and agree with what your opinion.


Add command line option for serving assets.

This takes @hone's commits from #6 and supercedes it.
You can run serving assets via:
ember fastboot --serve-assets

Please note: that pre-Glimmer Ember will not be able to start the application where the server rendered data left off.  Currently, this would mean that when the Ember app is booted in the client it will be duplicated in the DOM. To work around this, I have added an instance-initializer that clears the rootElement before initial render.

Thanks to @hone for doing all the hard work on this one....


adding a .bootstraprc to use bootstrap 4

@tsuckow This should fix the bootstrap-sass loading problems.

:+1:


Automatically source latest version of tmuxinator.{ba,z}sh

To ensure I source the latest version of the completion script, I wrote the  following (hopefully robust) {ba,z}sh code.
It's designed to be put in your ~/.bashrcor ~/.zshrc.
function sh_is_zsh { [[ -n $ZSH_VERSION ]]; }
function sh_is_bash { [[ -n $BASH_VERSION ]]; }

# Update "tmuxinator.{z,ba}sh" symlink if needed
tmuxinator_source="$XDG_CONFIG_HOME/tmuxinator/tmuxinator.$(sh_is_zsh && printf zsh || printf bash)"
# If not a regular file or symlink to one
if [[ ! -f $tmuxinator_source ]]; then
    # If doesn't exist or already a symlink
    if [[ ! -e $tmuxinator_source || -L $tmuxinator_source ]]; then
        echo "Creating ${tmuxinator_source##*/} symlink:"
        tmp=$(gem which tmuxinator) && # tmuxinator executable
            tmp=$(readlink -f "${tmp%/*}/../completion") && # completion scripts dir
            ln -fsv "$tmp/${tmuxinator_source##*/}" "$tmuxinator_source"
        unset tmp
    else
      echo "Not creating symlink at at existing:"
      ls -lF "$tmuxinator_source"
    fi
fi
source "$tmuxinator_source"

Would it be worthwhile adding something like this to a FAQ or some such so that users automatically get the latest version of the completion script?

Wouldn't this mess with multiple installations on the same machine ex, you have 0.15 / 0.14 at the same time?


Add shapes & points filtering to maps

Closes #342.
This PR adds an ability to filter geoDimension in the right panel. There was a need for some custom logic for shapes, as they are fetched separately from dimension's values.

[ ] should symbol layer based on the area layer be filterable separately? In such case filtering applies to both areas and symbols

When I go there : https://visualize-ad-feat-add-s-8usxwv.herokuapp.com/en/browse/dataset/https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2FCOVID19VaccPersons_sex_w%2F1%2F?previous={"includeDrafts"%3Atrue%2C"order"%3A"SCORE"%2C"search"%3A"covid"} and start a map viz, I have an unexpected error 🤔 Is this because of the dataset ?

It doesn't work because #364 is not merged yet 😅

I had made a quick fix locally to test it on my machine, but I would have to merge #364 to this PR to enable a correct deployment preview 👀


Collection of data stops after 1-2 hours

I have succesfully configured ruuvi-hass.io with couple of ruuvi tags. Data seems to come in for hour or two. After that data flow stops. Ruuvi tags continue to send out data, but HA -server does not recognize it. Restarting of HA (configuration --> Settings --> Server Controls --> Restart) will fix the issue. Of course rebooting of the entire server helps too. I'm running HASS.io official image on VMWare vSphere. Home Assistant version is 2021.12.10

Ihave also this issue. I will try to check if I could find some information in logs so that it could be useful to this case

After setting adapter: "hci1" the data seems to flow.
In my installation there are two different bluetooth adapters visible, but you could try to set that value.
Remember to change hci1 value to correspond your setup

Worked 10 days for me. Then needed reboot. Can I somehow add watchdog for this?

I created an automation to act as a watchdog. It runs every 5 minutes to check if latest update from a sensor is newer that 1800 seconds. If last update is more that 1800 seconds old host os reboots. Here is tha YAML. Jsut change the entity ID (sensor.outside_temperature) to match your's:
alias: Reboot if no data from ruuvi in 30 min
description: ''
trigger:
  - platform: time_pattern
    minutes: /5
condition:
  - condition: template
    value_template: >-
      {{
      (as_timestamp(now())-as_timestamp(states.sensor.outside_temperature.last_updated))
      | int > 1800}}
action:
  - service: hassio.host_reboot
    data: {}
mode: single

For me, similar issues started, when I upgraded the FWs of my 6 RuuviTags from version 2.X to 3.31.1.
See https://f.ruuvi.com/t/home-assistant-ruuvitags-not-properly-working-after-fw-upgrade/5562.
Any possibility that someone with sufficient skills could have a look at this (I don't have :D)?

Ping @mkauttu @lraty @japekka on this?


Restructure the docs

This PR does the following:

Moves core_components one level up
Renames contrib_components to contrib

This will probably break a lot of URLs (may be possible to add some redirects), but makes the docs easier to browse as subsections of the core components can now be found in the left hand menu.

Thanks, @kaedroho. It looks like RTD supports redirects:
http://docs.readthedocs.org/en/latest/automatic-redirects.html#redirecting-to-a-page

Thanks @tomdyson. Will have a look into that a bit later

A couple more things I'd like to do:

Move "Sites" somewhere else (probably "reference")
Move "using images in templates" out of images index (create new page for this in images section)

It looks like RTDs redirects would do the job. Theres one called a "prefix" redirect that would handle the core components change in one go (tried on another project). We would need to create one redirect for each page in the contrib section.

Actually, the redirects may be tricky as they probably apply to all versions of the docs, meaning 0.8 and before may get a bit screwed up of we create those redirects.


Opened InlineLinkGeneratingProvider to allow link customization

For transparency: the required feature was not to resolve relative links as it's required for generating good HTML for Rust documentation with IDE-readable links to rust symbols. Fixed in https://github.com/JetBrains/markdown/commit/8a997ede611983fce587e1dee3242ba2056b0ff1


Add zeMemPutIpcHandle()

L0 has zeMemGetIpcHandle to obtain the IPC handle for a given allocation. This IPC handle in the exporter is only closed when calling zeMemFree.
This produces a problem, if an IPC handle refers to a file descriptor, which is a finite resource in the system, since if the application wants to reduce the count of file descriptors opened, would have to deallocate the allocation altogether.
So idea here is to have a complementary call zeMemPutIpcHandle, with which application can tell L0 driver that is done with the handle, w/o needing to free the allocation.
We would have then
on the exporter:
zeMemAlloc
zeMemGetIpcHandle
zeMemPutIpcHandle
zeMemFree
and in the importer
zeMemOpenIpcHandle
zeMemCloseIpcHandle

why it is called zeMemPutIpcHandle. It should rather have something with "release" in name. "Put indicates that we put it somewhere". Can we change name to "zeMemReleaseIpcHandle" ?

This one is interesting because the way the handle is obtained is with Get, not Alloc or Create. We might propose a different naming to obtain the handle and coincide the 'release' nomenclature to match?

We already have "get" API, so I wouldn't change that.
For me opposite of getting something is releasing it.

opposite of getting something is releasing it.

Having get in the name of an interface generally implies that the user wishes to obtain an unowned reference. In older platform code, get/put align as malloc/free or create/release, so I can see the relationship.

@MichalMrozek :
@wdamon-intel  is correct,Put is more akin to network terminology,

ok, no objections then from my side.

Fixed with #91


The "shadow-*" classes are not correct when used against a dark background.

Change the opacity color to black, reduce the opacity to 0.4 and increase the shadow spread.

Fixed.


How to utiliize internal templates?

First off, EXCELLENT theme. THank you.
I noticed that my banner wasn't becoming my Facebook image, which eventually led me to see there are internal templates for the likes of og-graph. If I understand right, these are (maybe?) internal to Hugo, or internal to Go? No amount of searching has led me to any documentation that talks about these, though. Where can I learn about the internal templates, especially for social media?

Hello @WorldsEndless,

If I understand right, these are (maybe?) internal to Hugo

You're right. They're built-in to Hugo but currently undocumented (see spf13/hugo#1727). However, you can find the internal templates here.

I'll close this issue since the documentation should be fixed upstream in Hugo.


Bug fixes

Change related to bug fixes for import usfm file and export html.

Tests were run successfully.


Issue

Events not showing in some android devices api level 33

Events not showing in some android devices api level 33


Update integration-defender-for-endpoint.md

Adding anti-malware coverage info to FAQ TOC, adding extension coverage for WIndows 2012 R2 and 2016 in case MDE unified solution integration is enabled.

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

#sign-off


 But, I am having trouble getting RequiredSlots and multi-instance tasks to work.
When I create a batch job it contains thousands of tasks. I would say that 75% of the tasks created are small, and a single node could run 4 tasks concurrently. The remaining 25% are tasks that require many cores with MPI.
I had MPI working, but now need to implement the RequiredSlots feature in order to optimize our node usage.
I've refactored the small tasks to use RequiredSlots, and that seems to be working now.  However, the MPI task that requires multiple nodes no longer executes.
The documentation states that the requiredSlots property be set to 1 if it's a multi-instance task. I have tried setting this to 1, with the multi-instance property requiring 2 nodes, but the task never executes.  I've also tried setting requiredSlots to the pool's TaskSlotsPerNode property (just to check), but of course received a validation exception stating the property value was invalid.
Are there any known issues with running a workflow that consists of tasks that consume just 1 slot (with each node having 4 slots), and other tasks that require multiple nodes with MPI?

Currently, concurrency on the pool must be disabled in order to execute multi-instance tasks, i.e., taskSlotsPerNode must be set to 1. Please examine using multiple pools to accomplish your goal.

Thank you for passing along that URL. I must have missed it because I was searching for "required slots" documentation since I already had MPI working.
I would suggest this documentation being updated, as it implies you can make both work: https://docs.microsoft.com/en-us/rest/api/batchservice/task/add
In regards to the ability to run concurrent tasks and also multi-instance tasks, I hope that this is something the Azure Batch team considers. Multiple pools is not a viable solution, since in most cases, there is a workflow built into the job itself with a very specific task dependency hierarchy. By adding another pool, we'd lose the ability to have task dependencies.
I know that task scheduling would be a little more difficult to implement, since an MPI task would likely require the entire node, but I don't see why this is an issue as long as the end user sets the task scheduling policy to ComputeNodeFillType.Pack.

Hello! Just curious if there are any updates on this feature request? This would feature would definitely cut costs by allowing us to be more efficient with VM resources.

I am just curious, has there been any progress toward resolving this issue? Any updates would be appreciated! Thanks!

The above item is still in Backlog. Do you have a work item created yet?

Thank you for checking. I do not have a work item, what do I need to do to create one?

Hello @prkannap, just curious, has there been any movement this item?


WIP - Add retry logic to sidecar trace flushing

NOT READY FOR REVIEW
What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
Attention: Patch coverage is 94.78673% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 67.24%. Comparing base (e4c1985) to head (e69e958).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #433      +/-   ##
==========================================
+ Coverage   66.28%   67.24%   +0.96%
==========================================
  Files         187      187
  Lines       23118    23350     +232
==========================================
+ Hits        15324    15702     +378
+ Misses       7794     7648     -146

Components
Coverage Δ

crashtracker
19.34% <ø> (-0.97%)
:arrow_down:

datadog-alloc
98.37% <ø> (ø)

data-pipeline
51.45% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
84.94% <ø> (+3.70%)
:arrow_up:

ddcommon-ffi
74.93% <ø> (ø)

ddtelemetry
53.72% <ø> (ø)

ipc
81.27% <ø> (ø)

profiling
76.83% <ø> (ø)

profiling-ffi
60.05% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
36.02% <94.78%> (+6.64%)
:arrow_up:

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.12% <ø> (ø)

trace-normalization
97.79% <ø> (ø)

trace-obfuscation
95.74% <ø> (ø)

trace-protobuf
30.76% <ø> (+5.12%)
:arrow_up:

trace-utils
79.96% <ø> (+11.11%)
:arrow_up:


Make the demo torch-compatible

🚀 The feature
Run the demo with pytorch
Motivation, pitch
This would be great to be able to run the demo with pytorch
Alternatives
No response
Additional context
No response

#1008
temporary solution - should be changed to ONNX same for API if we have a valuable integration


Add option to turn off cheatcodes on Anvil

Component
Anvil
Describe the feature you would like
There are some cases in which cheatcodes are not only unused by undesired.
For example, I'm developing an application called Bug Buster, which aims to be a trustless bug bounty platform. I'd like to use Anvil to deploy smart contracts and check the validity of exploits on them.
However, if we allow cheatcodes, the hacker may perform unwanted operations such as setting smart contract storage slot values, or impersonating accounts. If there were an option to turn off cheatcodes (both by calling a specific address in the EVM and JSON-RPC API calls), then we could use Anvil for our showcase.
Additional context
No response

@mattsse

Marking as duplicate in favor of https://github.com/foundry-rs/foundry/issues/8699 after merging the two tickets


Missing Sourcemaps

When I run 'npm run start' I dont get any sourcemaps in chrome.

@Mattes83, with a clean install I have no problem seeing the source maps. Please see the attached screenshot.


Fix docker build --label when the label includes single quotes and a space

Fixes #31697
Previously labels passed with --labels were converted into a quoted string, and then parsed to create Node objects.  This PR changes the behaviour to create Node objects directly from the map[string]string, and avoids the parsing entirely. The parsing was was failing because the value was being quoted with single quotes.
This PR also includes some refactoring, and additional unit test.
Some single-use functions were moved out of utils.go next to their caller.

ping @tonistiigi since this is about the builder

cc @duglin @simonferquel

I had to add single quotes back to the value stored in the node because of #27174.
I'm thinking a better solution might be to add a new field to parser.Node, something like
AllowEnvReplacement bool

The node would then be the source of truth instead of builder/dockerfile/evaluator.go:replaceEnvAllowed.
As it is right now, we still strip off any quotes, so there is still an inconsistency with docker run labels, as described in #26027.

rebased

Too bad we have to do so much work for this thing. I'm all for AllowEnvReplacement or even just calling the evaluator directly. The other thing we should do is evaluate the AST before execution.
Until then this seems to fix the issue. LGTM

@duglin What do you think? Can we get this merged?


Load raw requests to test env

Load bulk data into test environment

@arielleandrews, I have a small task to load bulk requests to test environment, so we can test the new system with more data. Do you have any suggestions on how many requests that I should add? Thanks.
I created some scripts to load "Intake in progress" requests and added 100 records for now.

@richard-aot I just checked and between our 5 pilot ministries they have 60 open requests total right now, so 100 is sufficient to test what the load will be like for the pilot active requests only. Across all IAO clients, there are 2800 open requests. I leave it to your discretion what load level we need to test at this stage!

Thanks for the information @arielleandrews. I will add more requests next week.


KYLIN-4023 return timestamp and date without timezone in jdbc

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Gcc fixes

Some casts in order to quiet warnings

Thanks for the proposed PR. I think these changes are somewhat platform specific, though. According to this article and this stackoverflow post, "size_t string.size()" might not be the same as unsigned int, at least not in windows. It'd probably be better to initialize i as size_t, .e.g. "for(size_t i; ...)". Anyway, thanks but I will close this one but
I'll consider using size_t or another suitable type to avoid warnings in the future.


Pipe connecting with Clay pit MK 01

Mod source
Factorio Mod Portal
Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[X] Other

What is the problem?
After any changes to mod liast like turining off/on any mod, pipe connected to Clay pit MK 01 (I dont have others tiers to test due to progresion in game, and im lazy). It happens only when https://mods.factorio.com/mod/squeak-through-2 is turned on. No other fluid input is messed up.
Steps to reproduce

Turn on all py mods for 2.0 (with all this mods it working fine)
Have a world with pipe connected to Clay pit MK 01
Turn on https://mods.factorio.com/mod/squeak-through-2
Load game form step 2
Have a disconnected pipe
If you missed step 2 you can create new world connect pipe to Clay pit MK 01
Save game.
Turn on any mod (if you have any other mods than py or ST2 you can turn them off)
Load in game
Have disconnected pipe

Additional context

Log file
factorio-current.log

From the author of SQ2:

your pipe connection offsets are not in the center of the tile

should be fixed for the next update


Content missing on Impact page

At the bottom of https://icaf.org/impact we provide a history of achievements. Photos or pdfs for some years (or part of year) are missing. We need them in a folder with subfolders for each relevant year. Could you please add this content (70Mb) > https://we.tl/t-sxtODCWW47

@kojiro-soooo Are you available to take this one?

@Andrew-Dame Yes, I can take a look here. This was among a few other updates that Ashfaq requested, but I can take this one after addressing some of the other minor updates.

I've finished adding photos/pdfs to any achievements where there was content available, but some achievements still didn't have a corresponding photo/pdf. I've let Ashfaq know and I'm waiting to hear back on how he wants to proceed in case he has other files.


Default region is not working for the image import command

e.g: the following command is not working:
# importing image from default region and using default storage type (service credential will be autogenerated)
pvsadm image import -n upstream-core-lon04 -b <BUCKETNAME> --object-name rhel-83-10032020.ova.gz --image-name test-image

error:
╰─$     go run . image import -v=9 --bucket ocp4-images-bucket --image-name mkumatag-image --instance-name upstream-core-lon04 --object-name rhel-83-11242020.ova.gz
I1203 20:03:47.849039    7088 root.go:30] Using an API key from IBMCLOUD_API_KEY environment variable
Error: required flag(s) "region" not set
E1203 20:03:47.849169    7088 root.go:57] required flag(s) "region" not set
exit status 1

/kind bug
/assign @bkhadars

This is happening because the region flag is made mandatory here:
https://github.com/ppc64le-cloud/pvsadm/blob/ccd6812116e001178f5aa7a492045cdf644b5e7e/cmd/image/import/import.go#L180
and also not set to any default value here - https://github.com/ppc64le-cloud/pvsadm/blob/ccd6812116e001178f5aa7a492045cdf644b5e7e/cmd/image/import/import.go#L170
Region variable is already registered here - https://github.com/ppc64le-cloud/pvsadm/blob/ccd6812116e001178f5aa7a492045cdf644b5e7e/cmd/image/upload/upload.go#L163 this will create the conflict and assignment of the default value to the variable. Better declare a different variable for this subcommand.

Region flag is mandatory for image import sub-command.. updated the examples in the code as well to support the change
PR: https://github.com/ppc64le-cloud/pvsadm/pull/30


watch and multiple @import generates incorrect sources in source map

When --watch is used with multiple @imports, the sources in source map is incorrect.
Note:

I am using macOS.
Not sure if it is a node-sass issue or a libsass issue
Maybe related to #1758
The bug does not seem to happen when there is only one @import.

bash-3.2$ node_modules/.bin/node-sass --version
node-sass	3.13.0	(Wrapper)	[JavaScript]
libsass  	3.3.6	(Sass Compiler)	[C/C++]

bash-3.2$ cat foo/parent.scss
@import "child1";
@import "child2";

bash-3.2$ cat foo/_child1.scss
a {
  width: 25%;
}

bash-3.2$ cat foo/_child2.scss
b {
  width: 25%;
}

# After starting the following command, I modified _child1.scss
# Notice that how the second "changed" (possibly incorrectly) detects and responds to parent.css change.

bash-3.2$ node_modules/.bin/node-sass --watch --source-map true ~/workspace/sofa/foo --output ~/workspace/sofa/foo
=> changed: /Users/Kevin/workspace/sofa/foo/parent.scss
Rendering Complete, saving .css file...
Wrote Source Map to /Users/Kevin/workspace/sofa/foo/parent.css.map
Wrote CSS to /Users/Kevin/workspace/sofa/foo/parent.css
=> changed: /Users/Kevin/workspace/sofa/foo/parent.css
Rendering Complete, saving .css file...
Wrote Source Map to /Users/Kevin/workspace/sofa/foo/parent.css.map
Wrote CSS to /Users/Kevin/workspace/sofa/foo/parent.css
^C

# Notice the wrong "sources"
bash-3.2$ cat foo/parent.css.map
{
	"version": 3,
	"file": "parent.css",
	"sources": [
		"parent.css"
	],
	"mappings": "AAAA,AAAA,CAAC,CAAC;EACA,KAAK,EAAE,GAAI,GAAG;;AAEhB,AAAA,CAAC,CAAC;EACA,KAAK,EAAE,GAAI,GAAG;;AAEhB,sCAAsC",
	"names": []

@nivekz could you please create a small github repo which demos this issue so we can debug it?

I cannot reproduce it any more with the latest version as follows. So I suppose we can close this ticket now.
node-sass	4.1.1	(Wrapper)	[JavaScript]
libsass  	3.4.0	(Sass Compiler)	[C/C++]

Thanks for the confirmation @nivekz


feat: add warning if not part of the nearform-actions org

Closes #114

Ok, had a go as I understand it with this. Do we have anywhere that we can test this action?

No easy way to test this, but I'm confident this works correctly

Just looking into this a little more, is it worth moving the new logRepoWarning into the logActionRefWarning see? Otherwise we will have to update all the repositories and we potentially might miss one as the function is never called?


No make compile with CMake

Issue description
I clone the repo, try build get error.
Environment
Win 10, use VC 19
Issue Screenshot

Code Example
No code, just cmake want make work

This is a duplicate of #1391, please look at https://github.com/raysan5/raylib/issues/1096#issuecomment-699603920 and following comment(s) for the temporary solution.


Update constraints.md

Should we?

General Checks

[ ] the branch is up to date with main/master
[ ] All CI checks pass (if any)
[ ] all conflicts are resolved (if any)
[ ] PR has a descriptive title
[ ] PR has appropriate labels and milestones for easy identification
[ ] PR it is assigned to the owner
[ ] reviewers are assigned
[ ] the PR contributes only one focused change
[ ] It is in the appropriate column in the project board (if necessary)
[ ] has short and clear description
[ ] is linked to an issue (if it is related)
[ ] feedback is addressed (if any and if it is appropriate feedback.)
[ ] the code works when pulled and run locally (if there is code)
[ ] the code works when pulled and run locally (if there is)

I totally agree with changes


Add mtu configuration when creating veth, especially for ip-in-ip

Fixes #610

This isn't how we should fix the issue.

Can there be more of a description to why this PR was closed? I don't see why this solution is bad.

@TrimBiggs Can you add some comments as to why this one was closed.  Ta.

This was originally closed because the backend design had not been fleshed out, so this piece did not make sense to go in without any configuration change being made to the containers.  We are working on designing a solution to this problem now.

thanks for the feedback. I'm mostly affected by this once I start bridging edge nodes in Mantl.io


End of word missing

in https://global.iogt.site/en/sections/youth/your-health/mental-health/stress-and-me/being-a-young-parent/young-parents-scenario/ in the quiz answer the last word miss the last two letters "Ani is in a difficult situation and she should feel safe and that her baby is getting the best care. She should not be pressured to give up breastfeeding nor should she have to suffer insults and blame. It is important that Ani gets some support for herse"

This is related to #954. This is a quiz Feedback field, and right now it's limited to 255 characters. It looks like when content is pasted it's cut off where the length is longer than 255.
@lauriemarkle could you please just the text here to fit 255?

This is related to #954. This is a quiz Feedback field, and right now it's limited to 255 characters. It looks like when content is pasted it's cut off where the length is longer than 255.
@lauriemarkle could you please adjust the text here to fit 255?

@cbunicef Done!


default opts to empty object

To avoid error when opts is not defined.

Would rarely never happen, but if opts === false this would still break
any downsides to opts = extend(opts) since it's already a sheetify dependency?

My rationale behind not adding opts is as browserify is guaranteed to pass it in; that said, if someone wants to run sheetify with alternative bundlers it might break - so no objections to making this more robust. Thanks!

A couple cases where opts might be undefined:

This syntax in package.json (and why I made this PR)

  "transform": [
      [ "sheetify/transform" ]
    ]

If you're using the transform outside the scope of browserify, you might use it like this:

var sf = require('sheetify/transform')
var transformStream = sf('/foo/bar/myfile.js')

Oh, that's an excellent point. I'm sitting in a cafe rn where I can't push to git, will merge once I get home hah

Thanks! Published as v4.0.2


rv32d_fclass_d and rv32d_fclass_s contain non-portable code and might misbehave in default case of switch(class)

rv32d_fclass_d() and rv32d_fclass_s() contain non-portable code and might misbehave in default case of switch(class). @harrysarson, @rjlv2, or @SamuelmsWong, are you interested in looking at this after #132 has merged?

Code is: https://github.com/physical-computation/sunflower-simulator/blob/master/sim/op-riscv.c#L2222-L2270 and https://github.com/physical-computation/sunflower-simulator/blob/master/sim/op-riscv.c#L1628-L1677
And the spec says:

Can we rely on c using  IEEE 754? The spec says it does not have to but in practice all architectures do.


Crunchyroll with username and password gives ERROR: [crunchyroll] G14U422Q4: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
usa
Provide a description that is worded well enough to be understood
When trying to download a video from crunchyroll with a username and password, I get this error: Unable to download JSON metadata: HTTP Error 403: Forbidden
C:\Users\ubers>yt-dlp -u<EMAIL_ADDRESS>-p mypassword "https://www.crunchyroll.com/watch/G14U422Q4/bakugos-start-
line"
[crunchyroll] Extracting URL: https://www.crunchyroll.com/watch/G14U422Q4/bakugos-start-line
[crunchyroll] Requesting token
[crunchyroll] G14U422Q4: Downloading object info JSON (cms)
ERROR: [crunchyroll] G14U422Q4: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)

Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '-u', 'PRIVATE', '-p', 'PRIVATE', 'https://www.crunchyroll.com/watch/G14U422Q4/bakugos-start-line']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds [00dcde728] (win_exe)
[debug] Python 3.10.11 (CPython AMD64 64bit) - Windows-10-10.0.22631-SP0 (OpenSSL 1.1.1t  7 Feb 2023)
[debug] exe versions: ffmpeg N-111626-g0ba719f726-20230726 (setts), ffprobe N-111626-g0ba719f726-20230726
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.40.1, urllib3-2.2.3, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-master-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds)
[debug] Loading<EMAIL_ADDRESS>from cache
[crunchyroll] Extracting URL: https://www.crunchyroll.com/watch/G14U422Q4/bakugos-start-line
[crunchyroll] Requesting token
[crunchyroll] G14U422Q4: Downloading object info JSON (cms)
ERROR: [crunchyroll] G14U422Q4: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)
  File "yt_dlp\extractor\common.py", line 742, in extract
  File "yt_dlp\extractor\crunchyroll.py", line 389, in _real_extract
  File "yt_dlp\extractor\crunchyroll.py", line 149, in _call_api
  File "yt_dlp\extractor\crunchyroll.py", line 140, in _call_base_api
  File "yt_dlp\extractor\common.py", line 1152, in download_content
  File "yt_dlp\extractor\common.py", line 1112, in download_handle
  File "yt_dlp\extractor\common.py", line 962, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 911, in _request_webpage

  File "yt_dlp\extractor\common.py", line 898, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 4162, in urlopen
  File "yt_dlp\networking\common.py", line 117, in send
  File "yt_dlp\networking\_helper.py", line 208, in wrapper
  File "yt_dlp\networking\common.py", line 340, in send
  File "yt_dlp\networking\_requests.py", line 365, in _send
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden

support for this site is broken (see #10207) and the extractor is pending removal


Central Package Management - Transitive pinning with nuget 6.2.0 supported

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched issues to ensure it has not already been reported

Cake runner
Cake .NET Tool
Cake version
2.2.0
Operating system
Windows
Operating system architecture
64-Bit
CI Server
Azure DevOps Server 2017/2020
What are you seeing?
Cake.Tool 2.2.0 is using NuGet 6.1.0 at the moment. This version is not capable of interpreting transitive dependency correct.
There are new tool versions released, which supports this new feature:
Visual Studio 2022 17.2 and later
.NET SDK 6.0.300 and later
.NET SDK 7.0.0-preview.4 and later
nuget.exe 6.2.0 and later
See https://devblogs.microsoft.com/nuget/introducing-central-package-management/
Is it possible to update to nuget 6.2.0 with the upcoming new Cake Version 2.3.0 ?
What is expected?
Cake.Tool should use NuGet 6.2.0, not 6.1.0
Steps to Reproduce
N/A
Output log
No response

You should be able to use any newer .NET 6 SDK with Cake, do you have an example of what you're trying to do with Cake that doesn't work.

There is a known NuGet issue https://github.com/NuGet/Home/issues/6764, which was solved with NuGet 6.2. This version will used by newer .NET6 SDK's and VisualStudio. For a clean build environment and to prevent strange version conflicts, Cake.Tool should be use https://www.nuget.org/packages/NuGet.Versioning/6.2.0
Without this new version, Central Package Management is not working correct for transitive Packages. That means, all companies, which want to use the official release CPM, must update complete tool chain to the new NuGet packages and new NuGet.exe

In develop Cake already uses NuGet client libraries 6.2.1, so that will come out with the next release. Those client libraries are only used internally by Cake to install addins and tools, it doesn't affect the tools orchestrated by Cake.
The develop version is available on our Azure Artifacts Feed
https://dev.azure.com/cake-build/Cake/_packaging?_a=package&feed=cake&package=Cake.Tool&protocolType=NuGet
That said using newer versions of NuGet.exe or .NET CLI is already supported for projects you restore/build/package using Cake.
You can pin the version of NuGet.exe using the tool directive
#tool nuget:?package=NuGet.CommandLine&version=6.2.1

You can use Cake.Tool 2.2 with i.e. .NET SDK 6.0.302, best practice is to have a global.json in your repo to pin the .NET SDK version used, it can look something like
{
    "sdk": {
        "version": "6.0.302",
        "rollForward": "latestFeature"
    }
}

In a clean CI environment like GitHub actions you can ensure the right SDK version is used by using the setup dotnet task, which by default uses global.json to resolve .NET SDK version to install if missing
      - name: Install .NET Core SDK (global.json)
        uses: actions/setup-dotnet@v1

same yaml for i.e. Azure Pipelines would look something like this
- task: UseDotNet@2
  displayName: 'Use .NET Core SDK global.json'
  inputs:
    packageType: sdk
    useGlobalJson: true

Another option is to use the obtain scripts provided by the .NET Team which also supports installing a .NET SDK
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
The scripts have a json file option where you can specify the path to the global json used fetch version to install.

We have switched to internal NuGet usage with Update to Cake.Tool 2.2.0.
If we use the nuget restore plugin, we need to check, if it is working with the new version 6.2.0 then.
(Last time we had problems, when Cake.Tool 2.1.0 was using NuGet 6.0.0 and we had already 6.1.0 in usage. This combination was not working, reason why i ask, if the new Cake.Tool 2.3.0 will updated to NuGet 6.2.0 to prevent same situation)
We working in a medical environment, where tools must be stable and validated. That means, every tool chain is installed or will be downloaded as nuget package. Task with install .NET SDK at runtime is not allowed.
We will test the new tool chain in the next weeks. At the moment, we validate with cake 2.2.0 and .NET 6 SDK V6.0.103.
But i started this issue here, because i dont want to run into a surprise situation (which we had with Cake.Tool 2.1.0 and wrong NuGet version), where we need to wait months, if something is not working correct.


colors.es2015.js and colors.js have different APIs

In Babel, using export var is different than using module.exports = {}. Currently if using the es6 version you need to do import * as colors from 'material-colors' vs import colors from 'material-colors' for es5 (the latter is undefined since there's no default export).

If the es module exports the entire JSON as default export, there is not benefit for tree shaking and no point for the es module. But the file is not so big. Probably we don't need jsnext:main or module for such a small library.

colors.js and colors.es2015.js need to have the same API, otherwise it is going to break down in situations where a dependency expects one version and you expect the other.
For instance, we are using react-color, which uses the UMD version of material-colors when it builds. That means that react-color expects the output:
import colors from 'material-colors'
console.log(colors.red)

// transpiles (more-or-less) to
var colors = require('material-colors') // { default: { red: ...etc } }
console.log(colors.default.red)

However, since we are using webpack 2, this code tries to use colors.es2015.js and fails:
import colors from 'material-colors'
console.log(colors.red)

// transpiles (more-or-less) to
var colors = require('material-colors') // { red: ...etc }
console.log(colors.default.red) // can't read property 'red' of undefined

It would work for us if react-color changed:
import * as colors from 'material-colors'
console.log(colors.red)

But that would break when using webpack 1. Basically if you want to support both es6 and es5, you will need to ensure that your es5 and es6 have the same API. Maybe there's a grunt plugin you could use to generate a compatible umd bundle instead of templates? Otherwise like you said, you could choose not to publish an es6 version.

Sorry, I know this is the annoying nitty gritty of modern javascript bundling. Thanks for the response and I appreciate the work you've put into this!

What does the UMD bundle plugin does for ES module?
Anyway, because CommonJS and ES Module have different interfaces, it is hard to have exactly same API. To achieve it, an ES Module has to export an object with all the exports as props like module.exports, but it misses the point of ES Module. No bundle size reduction for tree shaking.
The ES Module bundlers like Rollup and Webpack 2 works well only when all the intermediate dependencies, react-color in this case, support the tentative ES Module community standard, which will take some time. I will just remove jsnext:main and module.

@echenley No problem! I know this is the way the JavaScript ecosystem evolved, and it's a good learning opportunity for me 😃

jsnext:main and module are removed in<EMAIL_ADDRESS>

Awesome, thank you!

Now I come up with a better idea. We could have a default export in addition to named exports. It's compatible to CommonJS API (thanks to Babel's interop) and also available for tree shaking.
export var red = { ... };
export var blue ={ ... };
export default {
  red: red,
  blue: blue
};

Done in<EMAIL_ADDRESS>


Invisible bottom sheet gets stuck in the center of the screen on Android

Hello,
The panel sometimes gets stuck in the middle of the screen on first app load. And it's invisible. It prevents me from clicking on the map. Android only. iOS is ok.
I noticed that this happens when initialSnap reference to not maximal value.
In my example: initialSnap = 0 works normally. And the panel is in it's max size.
Map and panel components is on one level and wrapped in one flex container with no other params.
Bug occurs more often on slow Android devices, or in debug mode.
const content = ({ children, height }) => (
  <View style={[styles.panel, { height }]}>
    {children}
  </View>
);

const renderHeader = () => (
  <View style={styles.header}>
    <View style={styles.panelHeader}>
      <View style={styles.panelHandle} />
    </View>
  </View>
);

const MapPanel = ({ panelRef, children, height }) => (
  <BottomSheet
    ref={panelRef}
    snapPoints={[600, 300, 0]}
    renderContent={() => content({ children, height })}
    renderHeader={renderHeader}
    initialSnap={2}
  />
);

The same issue, please help

I invented super-crutch :)
make ref of a View in contentRender. I called it contentRef.
this is a try to define if panel is in wrong place and hide it.
function crutch() {
contentRef.current.measure((width, height, px, py, fx, fy) => {
        if (fy < top) {
          return hidePanel();
        }
      });
}

but it not always work, that's why i do this in componentDidMount
      if (Platform.OS === 'android') {
        // SUPERMEGA CRUTCH for Android
        const timerId = setInterval(crutch, 300);
        setTimeout(() => {
          clearInterval(timerId);
        }, 2000);
      }

i know it's terrible :(

@WildSpy  I'm trying to discover if I'm seeing this as well. It's not showing up but I don't know how to see if it's not rendering or if its just behind everything. How did you get it to show up on the inspector?

@pianoman730 As i see it's not behind everything, because i can click on it in inspector. Just very strange behavior.

I had this similar issue, and for me, it was related to the it's location in the hierarchy, such that the bottom sheet had to be placed above all components for which is may overlay. I know this sounds weird, and may not be your problem, but something to consider

I have same issue, how to solve this?

Here's what I ended up doing that has been working consistently so far (YMMV). I set the initial snap to the last snap point index. When the component mounts, I then set the desired snap position.
  componentDidMount() {
    // This is a shim to prevent the bottom sheet from occassionaly not rendering correctly.
    // https://github.com/osdnk/react-native-reanimated-bottom-sheet/issues/51
    this.bottomSheet.snapTo(1);
  }

        <BottomSheet
          ref={ref => { this.bottomSheet = ref; }}
          snapPoints={[420, 210, 40]}
          renderContent={this.renderPanelInner}
          renderHeader={this.renderPanelHeader}
          initialSnap={2}
          enabledInnerScrolling={false} />

Hopefully this will help someone else out until we can get an official fix.

For me, this issue happens also with only two snap points, top and bottom :/

I conditionally render the bottom sheet and @WVandergrift's solution worked for me.

any progress?


Rikke attacks Harrold or Harrold attacks Rikke after Laila surrenders

(I told them that they stole each others Nintendo Switch)

Handling under #95


feat: created article for automated deployment using gh actions

This pull request contains the markdown file for my article on automating application deployments to Okteto Cloud using Okteto actions within a Github Actions Workflow.
The article content in the automated-deployments-using-github-actions.md file follows the approved content outline in this document. It is also available for review in a more readable format in this dropbox paper.
CC: @rberrelleza @Youngestdev

Hi @vickywane, I will be reviewing this blogpost. In the meantime, can you mail the images in a zip file to<EMAIL_ADDRESS>

Alright. I'll do that before the end of the day.

I have just applied your comments within this pull request to the file.
I however would need you to clarify how cingle line commands should be written.
Should they be written with an indented space ( the markdown command syntax )?
  npm test

Or should the command be surrounded with backticks as shown below?
npm test

Hi, @Youngestdev,
I have applied your suggestions and also made the sited adjustments.
I would update the ZIP file containing the images and resend it to you.

Thank you for the article draft and sorry for the long wait too. @rberrelleza will be making a final review this week :-)

Thanks @Youngestdev !
Looking forward to @rberrelleza review of the draft.

Some comments @vickywane from Ramiro:

A good scenario would be to deploy during merge to validate that the changes don’t break, and then many run an end to end test to validate that the app works.

Some comments @vickywane from Ramiro:
A good scenario would be to deploy during merge to validate that the changes don’t break, and then many run an end to end > test to validate that the app works.

@Youngestdev The comment here is quite unclear as i think it has already been covered in the article draft.

Unit tests were written for the API endpoints using httppretty and pytest in step 3.
The .Dockerfile included a command to execute the unit test in line 191 of step 3.
A merge of the pull request opened within the article was done and the tests were executed directly agaisnt the master branch ( including a deployment to the Okteto namespace ) in step 5.

Did @rberrelleza look through the images? ( They were shown in the images )

Hi @vickywane,
Ramiro requested a further review: so for this post, I was thinking about, what if you have a test that you run everything you merge to main? Okteto can be used to deploy an ‘on demand’ copy of the app with the latest code, and then you can run a test to make sure that everything works fine, by calling the application directly, instead of using mocks.
So our CI has two jobs:

Build a copy of the application first
Run the tests on the endpoint of the copy of the application built


feat: Migrate to TrieAccount of alloy-trie

Motivation
Account has been migrated to TrieAccount of  alloy-trie in https://github.com/alloy-rs/trie/pull/65

Solution

PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Breaking changes

@mattsse I just saw your comment. Thank you for handling the genesis account conversion!

thank you!
I quickly pushed this over the line because we needed a new release on reth


Returning ETH

Nice to meet you. I have sent ETH to the Conflux address not deposit address.  Is it possible to return it?

Hi,
The Conflux account can only receive the CFX token or the tokens based on Conflux Chain.
There is a possibility that you can try this way to get your balance back.

Export your private key in ConfluxPortal

Copy your private key and import it to your MetaMask

After you import the private key to MetaMask, you will have a new account in MetaMask. If the balance is shown on this account, it shows that you have already get your balance back, if not, you can not get your balance back.

Thank You!
Private key Import my metamask.
but
Conflux  Address is 0x1e933ca135624f256B7EBe2E663573D953a51E98
Metamask Address is 0xCe933Ca135624F256b7ebE2E663573d953A51e98
Not exactly.
conflux
[image: スクリーンショット 2021-03-04 19.37.13.png]
Metamask
[image: スクリーンショット 2021-03-04 19.38.39.png]
I don't know why.
Please, can you solve it?
2021年3月4日(木) 19:31 Chao Zhou<EMAIL_ADDRESS>
Hi,
The Conflux account can only receive the CFX token or the tokens based on
Conflux Chain.
There is a possibility that you can try this way to get your balance back.

Export your private key in ConfluxPortal

[image: image]
https://user-images.githubusercontent.com/16474758/109946427-2f849200-7d13-11eb-94ad-10fce5de6138.png
[image: image (1)]
https://user-images.githubusercontent.com/16474758/109946433-30b5bf00-7d13-11eb-9ac6-ca843ada46ff.png

Copy your private key and import it to your MetaMask

[image: image (2)]
https://user-images.githubusercontent.com/16474758/109946446-36130980-7d13-11eb-9340-6f211e8f0813.png
[image: image (3)]
https://user-images.githubusercontent.com/16474758/109946472-3b705400-7d13-11eb-9afc-8e4b465fdd92.png
After you import the private key to MetaMask, you will have a new account
in MetaMask. If the balance is shown on this account, it shows that you
have already get your balance back, if not, you can not get your balance
back.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Conflux-Chain/conflux-portal/issues/305#issuecomment-790510752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCTLB2EF76XY4ENJU45LDLTB5OOHANCNFSM4YS2AHVA
.

The address between ConfluxPortal and MetaMask is different, it shows that you can not get the ETH back.
The Conflux account can only receive the CFX token or the tokens based on Conflux Chain.

Thank You!
Private key Import my metamask.
but
Conflux  Address is 0x1C

Thank You!
Private key Import my metamask.
but
Conflux  Address is 0x1C....
Metamask Address is 0x2C

Metamask Address is 0x2C....
Can't I get my eth back


add extension function for azure

This extension function is working for us on MS Azure.
Addresses: #825

@moritz-deissner-turbinekreuzberg thank you very much for the contribution, we will check review asap. 🙏🏽

@moritz-deissner-turbinekreuzberg What's the status on this PR? We have a client that could use the feature soon.

@moritz-deissner-turbinekreuzberg What's the status on this PR? We have a client that could use the feature soon.

Beats me. The is no change since December 16 2021 when @ahmetoz said they would do a review.

Sorry for the late reply @moritz-deissner-turbinekreuzberg,
We've added it to our backlog, checked this PR and opened an internal investigation, the delay here related to that our experience of Azure setup so we could not test it out easily and now it's waiting our tech time investigation first on an Azure Function setup.
I would have some comments for the PR for the major missing points to make it as part of the other deployment examples such as GCP functions or AWS Lambda:

PR covers only the extension, so current change does not cover the notification deployment.
PR does not cover test cases to ensure it's working with normal path or other edge cases.
PR does not have a documentation to describe how it could be deployed to Azure functions.

If you want to consider contribution for this based on the points above, we would like to help on the detail pull request reviews.

Closing this PR. https://github.com/commercetools/commercetools-adyen-integration/pull/993
I have created PR with more detailed documentation and scripts for both extension and notification.
We will release it soon.

https://github.com/commercetools/commercetools-adyen-integration/releases/tag/v9.9.2
Released.


Please add a note about how to build and run

I am getting errors like this:

[ERROR] Failed to execute goal on project drools-lesson1: Could not resolve dependencies for project org.kiegroup:drools-lesson1:kjar:2.0.0-SNAPSHOT: Failed to collect dependencies at org.kiegroup:drools-lesson-pojo:jar:2.0.0-SNAPSHOT: Failed to read artifact descriptor for org.kiegroup:drools-lesson-pojo:jar:2.0.0-SNAPSHOT: Could not find artifact org.kiegroup:AccountProject:pom:2.0.0-SNAPSHOT -> [Help 1]

when you do a maven install the Junit tests are run and are working for me
What did you do to get that message?


[release-v1.11] Bump to Go v1.21

Related to https://github.com/openshift-knative/serverless-operator/pull/2451

/cc @matzew @creydr

/retest


nixos/systemd/initrd: don't allow emergencyAccess to be null

This didn't work previously, due to downstream code not expecting the null case.
30c36b47062f5cab53da07d9ed4ff1bd2b98ce36 added the types from users.users.*.hashedPassword, but probably null shouldn't have been copied over - it doesn't make sense for emergencyAccess to deal with the null case.
Users who want to set this to the value of one of their config.users.users.<user>.hashedPassword options (still) need to check for that to be null, and explicitly decide whether this means enabling emergency access or not (or maybe using another fallback password?), but that leaves this decision to the user.
This is cleaner than just assuming a desirable behaviour, and also means we keep the types for emergencyAccess cleaner.
Closes #334337.
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Wdyt about splitting the option into two instead: .emergencyAccess (type bool) and .emergencyAccessPasswd (type passwdEntry)? (Naming up to you.)

I don't think we should do this.
Other than that, I don't particularly care whether we remove null or have it disable access.

#334337 got merged. Closing.


Clean up logic for encodings, enhance fallback options, add new encoding options

We can simplify the encoding logic so we aren't special casing UTF-8 and ASCII anymore.
Lets provide a cleaner version of the common encoding support.
While here, let's provide transformers for ASCII, ISO-Latin1, and ISO-Latin5.  This should greatly expand the reach of the app, and give more correct results for people actually living in ISO 8859-1 locales (rather than the 8859-15 hack we had.)

Also, we're going to give fallback options, settable, so that if an encoding isn't present, you can have a fallback to ASCII, or even UTF-8, just in case.


Sles for SAP not recognizing some distro commands

I tried install the new pip version
zypper install python3-pip

pip3.6 install --upgrade pip

then i receive the folowwin error
Exception:
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 228, in main
    status = self.run(options, args)
  File "/usr/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 241, in run
    with self._build_session(options) as session:
  File "/usr/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 81, in _build_session
    insecure_hosts=options.trusted_hosts,
  File "/usr/lib/python3.6/site-packages/pip/_internal/download.py", line 339, in __init__
    self.headers["User-Agent"] = user_agent()
  File "/usr/lib/python3.6/site-packages/pip/_internal/download.py", line 102, in user_agent
    zip(["name", "version", "id"], distro.linux_distribution()),
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 120, in linux_distribution
    return _distro.linux_distribution(full_distribution_name)
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 634, in linux_distribution
    self.version(),
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 688, in version
    self.lsb_release_attr('release'),
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 836, in lsb_release_attr
    return self._lsb_release_info.get(attribute, '')
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 522, in __get__
    ret = obj.__dict__[self._fname] = self._f(obj)
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 933, in _lsb_release_info
    stdout = subprocess.check_output(cmd, stderr=devnull)
  File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/site-packages/run/__init__.py", line 145, in __new__
    process = cls.create_process(command, stdin, cwd=cwd, env=env, shell=shell)
  File "/usr/lib/python3.6/site-packages/run/__init__.py", line 121, in create_process
    shlex.split(command),
  File "/usr/lib64/python3.6/shlex.py", line 305, in split
    return list(lex)
  File "/usr/lib64/python3.6/shlex.py", line 295, in __next__
    token = self.get_token()
  File "/usr/lib64/python3.6/shlex.py", line 105, in get_token
    raw = self.read_token()
  File "/usr/lib64/python3.6/shlex.py", line 136, in read_token
    nextchar = self.instream.read(1)
AttributeError: 'tuple' object has no attribute 'read'
Traceback (most recent call last):
  File "/usr/bin/pip3.6", line 11, in <module>
    load_entry_point('pip==10.0.1', 'console_scripts', 'pip3.6')()
  File "/usr/lib/python3.6/site-packages/pip/_internal/__init__.py", line 246, in main
    return command.main(cmd_args)
  File "/usr/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 264, in main
    timeout=min(5, options.timeout)) as session:
  File "/usr/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 81, in _build_session
    insecure_hosts=options.trusted_hosts,
  File "/usr/lib/python3.6/site-packages/pip/_internal/download.py", line 339, in __init__
    self.headers["User-Agent"] = user_agent()
  File "/usr/lib/python3.6/site-packages/pip/_internal/download.py", line 102, in user_agent
    zip(["name", "version", "id"], distro.linux_distribution()),
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 120, in linux_distribution
    return _distro.linux_distribution(full_distribution_name)
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 634, in linux_distribution
    self.version(),
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 688, in version
    self.lsb_release_attr('release'),
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 836, in lsb_release_attr
    return self._lsb_release_info.get(attribute, '')
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 522, in __get__
    ret = obj.__dict__[self._fname] = self._f(obj)
  File "/usr/lib/python3.6/site-packages/pip/_vendor/distro.py", line 933, in _lsb_release_info
    stdout = subprocess.check_output(cmd, stderr=devnull)
  File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/site-packages/run/__init__.py", line 145, in __new__
    process = cls.create_process(command, stdin, cwd=cwd, env=env, shell=shell)
  File "/usr/lib/python3.6/site-packages/run/__init__.py", line 121, in create_process
    shlex.split(command),
  File "/usr/lib64/python3.6/shlex.py", line 305, in split
    return list(lex)
  File "/usr/lib64/python3.6/shlex.py", line 295, in __next__
    token = self.get_token()
  File "/usr/lib64/python3.6/shlex.py", line 105, in get_token
    raw = self.read_token()
  File "/usr/lib64/python3.6/shlex.py", line 136, in read_token
    nextchar = self.instream.read(1)
AttributeError: 'tuple' object has no attribute 'read'

so i went to python

the distro commands returns the id but is not returning the version.
so i think than this is  the problem

i cant execute any command with pip who do install and uninstall.
anny idea how to resolve this problem and have a working pip?
i tried manual install but not work with
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python get-pip.py
python3 get-pip.py

Could you please give the output for lsb_release -a on your system ? Thanks 🙇

So it appears this issue is a duplicate of #222 (see upstream xando/subprocess.run#5 for rationale).
Could you verify that you actually got a subprocess.run Python package installed on your system ?
Also see pypa/pip#5467 & Azure/WALinuxAgent#1705.
Bye 👋


Consider linting

https://github.com/golang/lint

Thanks! I did not know about golint, so it will be a nice addition to gofmt


"error loading tree: ReadFull(<data/22a6ed12a6>): EOF" during backup

I got a screenful of error loading tree:ReadFull() warnings on my first backup since upgrading to the local cache feature in master. The repo is local, 199GB in size, and has around 35 snapshots, dating back to 2017-08-12.
Output of restic version
restic compiled manually
compiled with go1.9 on darwin/amd64

Built from:
git rev-parse HEAD
bff1039e3aac4995580b4cd334576ae1d133f1b2

with no local changes.

Local.
Expected behavior
Backup should complete without warnings.
Actual behavior
On my first backup since upgrading to the local-cache enhancement, I got a screenful of warnings like:
scanned 133964 directories, 511998 files in 1:52
error loading tree: ReadFull(<data/22a6ed12a6>): EOFB  299805 / 645962 items  0 errors  ETA 0:40
error loading tree: ReadFull(<data/22a6ed12a6>): EOFB  299847 / 645962 items  0 errors  ETA 0:40
error loading tree: ReadFull(<data/22a6ed12a6>): EOF

Steps to reproduce the behavior
Not reproducible thus far- subsequent backups to the same repo complete without any warnings. I also tried on a few smaller "test" repos that I had around, and no warnings.
Do you have any idea what may have caused this?
No.
Do you have an idea how to solve the issue?
No.

In https://github.com/restic/restic/pull/1040#issuecomment-331863195 @fd0 asked me to check the size of data/22/22a6ed12a6. It looks fine, I think?
ls -l data/22/22a6ed12a61fda8da3996364c35e87daab758a103f72b1766fedebf57a987915
-r--------  1 armhold  staff  4246570 Sep 22 08:24 data/22/22a6ed12a61fda8da3996364c35e87daab758a103f72b1766fedebf57a987915

I tried cat pack 22a6ed12a6 | strings and that completed without warnings. It does seem to have some valid data in it.

Ah, thanks a lot for the comprehensive report! That verified my hunch, it's a concurrent access problem when the cache is busy downloading a file. It goes like this:
It happens when restic is busy downloading a pack file and a second read request comes in for the same file. The cache then thinks the file is already there (it is, but it's empty) and then the read error happens.
But it won't hurt or anything, the backup progress will worst-case just re-read the files. And as soon as the file download is complete, it's gone anyway.
So, I'll add a bit of code to block the second request until the first is done, then serve the cached content.

"Downloading a pack file"- my report is against a local repo. I'm guessing you mean that in an abstract way, but just want to be clear.

The cache is also used for a local repo (we cannot know if the repo really is something remote), unless disabled with --no-cache. So "downloading a pack file" here means "copying a pack file to the cache".


Test task is not incremental

The test task provided by the plugin does not seem to define inputs and outputs. As a result the task is never up-to-date and re-executes tests even though nothing changes from a previous run.
I get the same output for every run of the task:
$ gradle test

> Task :test
Test for github.com/bmuschko/link-verifier/stat finished, 4 completed, 0 failed
Test for github.com/bmuschko/link-verifier/text finished, 6 completed, 0 failed
Test for github.com/bmuschko/link-verifier/http finished, 3 completed, 0 failed
Test for github.com/bmuschko/link-verifier/file finished, 6 completed, 0 failed

Thank you for reminding that. I should improve it in future releases.

This would shipped in 0.8.0.

@blindpirate When are you planning to ship version 0.8.0? I think it would make sense to release more often to let users benefit from those changes.

This week or next week. Thanks for reminding.

Cool, looking forward to it. Would love to see a version this week to prep a presentation.


MaxPoolWithIndices

This is also going to need a max_pool_with_indices .rst file. I will be making a PR with max_pool.rst soon.

This is a backend-specific/MKLDNN op. Are we documenting those now?

Then you just need something useful to an IA transformer person in the .hpp file.

Agree with @diyessi  My main point is to not duplicate


Secure Supply Chain Analysis violations in samples

Builds of Aspire are causing violations in the Secure Supply Chain Analysis step:
##[warning]Discovered a reference to an image from an unapproved registry that violates the security policies and standards for containers within Microsoft. Reference to image 'localhost:5001/api-gateway' on line 19 of samples/eShopLite/Deployment/api-gateway.yml.
##[warning]Discovered a reference to an image from an unapproved registry that violates the security policies and standards for containers within Microsoft. Reference to image 'localhost:5001/basket-service' on line 19 of samples/eShopLite/Deployment/basket-service.yml.
##[warning]Discovered a reference to an image from an unapproved registry that violates the security policies and standards for containers within Microsoft. Reference to image 'localhost:5001/catalog-service' on line 19 of samples/eShopLite/Deployment/catalog-service.yml.
##[warning]Discovered a reference to an image from an unapproved registry that violates the security policies and standards for containers within Microsoft. Reference to image 'localhost:5001/my-frontend' on line 19 of samples/eShopLite/Deployment/my-frontend.yml.

This seems to be occurring after the Secure Supply Chain Analysis task was automatically upgraded from 0.2.192 to 0.2.193

@davidfowl is this yaml still relevant? I think it was from early experiments of @bradygaster using pre-Aspire azd logic.

Can we get this cleaned up for Preview 1? It's causing Secure Supply Chain Analysis warnings for the VMR builds because this source gets included there.

I wrote this YAML to test Service Discovery in k8s using the SRV provider and to test deployment to k8s in general.

This is now occuring in 8.0.1xx builds. Link to internal build.

@eerhardt - This is now occurring in 8.0.1xx builds. Link to internal build.

What branch of dotnet/aspire is the 8.0.1xx build using? It needs to be updated to include the fix.

Latest the VMR pulled was https://dev.azure.com/dnceng/internal/_git/dotnet-aspire/commit/48e42f59d64d84b404e904996a9ed61f2a17a569 from main on Nov 7, 2023. I'll backport the PR with the fix. Thanks!

Aspire doesn't flow to the release/8.0.1xx branch of installer:
$ darc get-subscriptions --source-repo aspire --target-repo installer
https://github.com/dotnet/aspire (.NET 9) ==> 'https://github.com/dotnet/installer' ('9.0.1xx-preview1')
  - Id: 13b61006-d12e-4279-5e1d-08dc174faa6d
  - Update Frequency: EveryBuild
  - Enabled: True
  - Batchable: False
  - PR Failure Notification tags:
  - Merge Policies: []
https://github.com/dotnet/aspire (.NET 8) ==> 'https://github.com/dotnet/installer' ('main')
  - Id: 70610cde-d4b7-4e3d-336c-08dc11d8c62b
  - Update Frequency: EveryWeek
  - Enabled: True
  - Batchable: False
  - PR Failure Notification tags:
  - Merge Policies: []
  - Last Build: 20240205.1 (5b98bff86e66fe9d5cc19d6b670505fdef25449d)

So the only way to do this would be via a patch in installer.

@eerhardt - What's the plan for servicing in Aspire if there's no dependency flow to 8.0?

I don't know the answer. But @joperezr should. Aspire is on preview3 and we have no plans on servicing preview1 or preview2. Honestly I'm not sure why dotnet/aspire code should even be affecting the 8.0 VMR. Aspire doesn't ship in the .NET box.

Aspire has been declared a toolset dependency as of 8.0.3 release of .NET. The only thing that ships in the product that comes from Aspire is the Aspire's workload baseline manifest, which hasn't really been updated in a while. @marcpopMSFT can explain, but it is normal for workload baseline manifests to not get updated after initial release unless they have to(for instance they changed the IPA targets and need to service them, etc), which we don't. When a user tries to use and install aspire, the SDK is automatically configured to do an update check to see if the manifest is outdated, which it will find that it is, and then it will fetch the latest manifest and install it, which is why it is not necessary to setup dependency flow.

Thanks, that all makes sense.

Following up on what Jose said, only the aspire baseline manifests should be included in the source build and SSCA going forward. The change to move it into toolset dependency section was made net9. That change is probably needed in net 8 as well as I don't think there are plans to continue updating the baseline manifest.
CC @joperezr @mmitche should we port the change to mark the aspire component as a toolset dependency to 1xx and 2xx?
The baseline manifest mostly just tells the SDK that there is a set of workload packs that could be installed and today we always update to the latest manifest before installing any packs (by default). The contents of the manifest are just two targets files and a json and so don't have any of the code that is reviewed by SSCA. It's aspires responsibility to ensure their packs are separately checked before pushed to nuget.org.
Does that all makes sense?


[Suggestion] Change the recipe for raw tortilla to use water bottles instead of water buckets

Right now, it is extremely annoying to craft raw tortillas with water buckets unless you have several of them in your inventory (which is also not ideal since they're unstackable and take up a lot of space), as you will have to keep refilling the bucket each time you make the recipe. For a QoL change, I strongly suggest changing the current recipe to use water bottles instead of buckets, as they are stackable to 16 and are much less of a hassle to craft with as a result.

Most mods dealing with food tend to require buckets of water for crafting the "washed" variants, as water bottles are mostly an alchemy component.


[Feature/Developer] Set the microcontroller into deep sleep state

Is your feature request related to a problem? Please describe.
The battery of the microcontroller would run down very quickly (within a few hours) if the functionalities of the controller are not limited.
Describe the solution you'd like
The microcontroller must be brought into a so-called deep sleep state so that the energy consumption can be reduced. This significantly increases the battery runtime.

https://tutorials-raspberrypi.de/monatelanger-esp8266-batteriebetrieb-mittels-deep-sleep/


CLOUDP-251873: Fix 2.3.0 SBOMs and generation script

This fixes a bug in the SBOM generation when the host machine does not match the arch from the docker sbom requested:
image has unexpected architecture "arm64", which differs from the user specified architecture "amd64"
The only workaround I found was to be explicit about the platform image SHA, so it will not complain and just compute the SBOM properly.
This PR also fixed version 2.3.0 SBOMs affected by this issue earlier.
All Submissions:

[X] Have you signed our CLA?

CLOUDP-251873


chore: use release-it-pnpm

Rather than packing the packages separately and using the hooks (which breaks when used with --dry-run), we can use release-it-pnpm.

@wswebcreation we could eventually use this in the visual-testing repository if we want to get rid of Changeset.