Option and Has ignore sparse components in transmuted dense queries

Bevy version
e155fe1d86
What you did
Transmuted a QueryState<EntityMut> to either QueryState<Option<&S>> or QueryState<Has<S>>, where S is a sparse set component.
#[derive(Component)]
#[component(storage = "SparseSet")]
struct S;

let mut world = World::new();
world.spawn(S);

let mut query = world
    .query::<EntityMut>()
    .transmute::<(Option<&S>, Has<S>)>(&world);
let (option, has) = query.single(&world);

assert!(option.is_some());
assert!(has);

What went wrong
The matched entity has an S component, but Option<&S> yields None and Has<S> yields false.
Additional information
Option and Has cache whether the component exists in set_table or set_archetype.  To make this work for sparse set components, they set IS_DENSE = false and require sparse iteration.  But EntityMut performs dense iteration, so the transmuted query is dense and calls set_table.  Option and Has don't find the component in the table, since sparse set components are not stored in tables, and return None or false for the entire table.
#14628 is also caused by transmuting a dense query to a sparse one.
#16396 would make this also occur in cases involving FilteredEnittyMut.

I see two basic ways to fix this: either prevent dense to sparse transmutes, or make Option and Has always work on dense queries.
Preventing dense to sparse transmutes could be done by having QueryState::transmute_filtered do assert!(!self.is_dense || (NewD::IS_DENSE && NewF::IS_DENSE)) alongside the other assert.  To support cases where those transmutes are needed, we could provide ways to force the original query to be sparse, like a QueryBuilder::force_sparse() method and a ForceSparse QueryFilter struct.  That would also resolve #14628.
Making Has work on dense queries isn't too bad.  You can store the &ComponentSparseSet in the Fetch when working with a sparse set component and call contains() on each entity.  You could even store an Option<bool> alongside it to cache the result when the query winds up being sparse anyway.  Making Option work is similar, but requires a lot more code since you have to add plumbing to QueryData.
Making Has and Option always be dense might even improve performance, if the better iteration order offsets the per-entity lookups!
I'm happy to make PRs for any of these ideas if those designs sound reasonable!

Looking at this again, I have no idea why I thought #14628 had the same root cause!  That one doesn't involve sparse set components at all.  I'll remove that from the description.
I also missed a few other types with the same issue: AnyOf and Or.  A dense query with AnyOf<(&S)> will always yield None, just like Option<&S>.  And a dense query with Or<(Changed<S>)> or Or<(Added<S>)> will never find rows with a changed or added S.
Those could be made to work with dense queries using the same approach as Option.


Add troubleshooting steps to all network response codes

Problem
It would be helpful to developers to provide a set of instructions on how to troubleshoot the network response code.
Solution
Add trouble shooting steps the network response codes.
Alternatives
No response

Here is an example of what we could have:
https://kinsta.com/blog/http-error-503/#:~:text=The HTTP 503 Service Unavailable error means that a website,which requires a deeper analysis.&text=Running into errors on your site can be intimidating


Remove the operate-source update command

What is changed, added, or deleted? (Required)
Fix https://github.com/pingcap/docs-cn/issues/11439
Which DM version(s) do your changes apply to? (Required)

Since December 23, 2021, the TiDB DM documentation in the master branch has been merged to TiDB documentation by #8042 and #7317. To create a PR for TiDB DM versions later than v5.3, either go to TiDB English documentation repository or Chinese documentation repository.

[x] v5.3 (TiDB DM 5.3 versions)
[ ] v2.0 (TiDB DM 2.0 versions)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s): https://github.com/pingcap/docs-cn/pull/11441

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Need modification after applied to another branch
[ ] Might cause conflicts after applied to another branch

/merge


Adding superagent-retry-delay package to the native library

I'm updating several thousand posts using this API over a WAN connection and received a lot of timeouts in the requests using the native superagent implementations. One way on solving this was to implement a "retry/timeout layer" in the application itself but then I found another package that's an extension of the superagent that is being used.
https://www.npmjs.com/package/superagent-retry-delay
In order to make use of this additional package only minor changes in the wpapi/lib/http-transport.js file is needed.
Added require('superagent-retry-delay')(agent); just after the row const agent = require( 'superagent' );
Changed all "requests" rows from: let request = _auth( agent.put( url ), .... to: let request = _auth( agent.get( url ).retry(5, 3600000, [401, 404]),.....
It works like a charm and I don't need to have logic in the application itself.
Is there any chance that this could be added to the native WP-API?

Love this, I'll give it a shot. I'm facing issues while bulk posting as well.


[mp3lame:x64-osx] build failure

Host Environment

OS: Mac OS Big Sur
Compiler: Xcode 12.5
vcpkg repository on a mounted samba share
Macports installed

To Reproduce
Steps to reproduce the behavior:
./vcpkg install mp3lame
Failure logs
-- Building x64-osx-dbg
… then waiting forever (I interrupted after the week-end).
Additional context
Waits forever for the deletion of a (non-existing!) file.
Last logs in build-x64-osx-dbg-out.log:

/bin/sh ../libtool  --tag=CC   --mode=link gcc  -O3 -Wall -fPIC -g -fno-common -version-info 0:0 -export-symbols .././../src/0844b9eadb-a14cfeb202.clean/include/libmp3lame.sym -no-undefined -L/Volumes/Development/Releases/Mac/vcpkg/installed/x64-osx/debug/lib  -o libmp3lame.la -rpath /Volumes/Development/Releases/Mac/vcpkg/installed/x64-osx/debug/lib VbrTag.lo bitstream.lo encoder.lo fft.lo gain_analysis.lo id3tag.lo lame.lo newmdct.lo presets.lo psymodel.lo quantize.lo quantize_pvt.lo reservoir.lo set_get.lo tables.lo takehiro.lo util.lo vbrquantize.lo version.lo mpglib_interface.lo  ../libmp3lame/vector/liblamevectorroutines.la ../mpglib/libmpgdecoder.la -lm
libtool: link: Waiting for /Volumes/Development/Releases/Mac/vcpkg/buildtrees/mp3lame/x64-osx-dbg/libmp3lame/../libmp3lame/vector/.libs/liblamevectorroutines.a.lock to be removed
libtool: link: Waiting for /Volumes/Development/Releases/Mac/vcpkg/buildtrees/mp3lame/x64-osx-dbg/libmp3lame/../libmp3lame/vector/.libs/liblamevectorroutines.a.lock to be removed
(repeating ad infinitum)

The problem is that libtool tries to create a hard lock across filesystems, with a wrong logic:

while create hardlink(lock file) failed do print "waiting for lock file to be deleted" ; sleep ; done

I found a post describing this problem, but no solution.
I'm new with vcpkg, but I tried to find a workaround to either fix or disable locking for libtool:

force using Macports' libtool instead of the one of Xcode.
adding the option --disable-libtool-lock to configure in portfile.cmake
patching configure to force need_locks=false
patching ltmain.sh to replace ln with cp -n
btw, it does not seems to be used.

None of these attempts had any effect.
If anyone has a better understanding of vcpkg build system, libtool's mechanism or on how to build mp3lame on another filesystem than libtool, a workaround would be welcomed!

I succeeded to install it the following way:

Edit buildtrees/mp3lame/x64-osx-dbg/libtool while vcpkg is still configuring x64-osx-rel, and replace lock_old_archive_extraction=yes with lock_old_archive_extraction=no
Do the same in buildtrees/mp3lame/x64-osx-rel/libtool while x64-osx-deb is building

So the solution is to find the way how to set this variable to no in the vcpkg package.

@Neumann-A Should we also add an option DISABLE_LOCK to vcpkg_*_make to use --disable-libtool-lock? Or add an option DISABLE_PARALLEL?

Should we also add an option DISABLE_LOCK to vcpkg_*_make to use --disable-libtool-lock? Or add an option DISABLE_PARALLEL?

If it is need. But since the option can simply be passed be the OPTIONS parameter in vcpkg_configure_make why add another one? Furthermore the is the new triplet variable which can add those options to all ports if needed.

@Neumann-A If this is a common issue, I think we have enough reasons to add it as an option.

The function vcpkg_build_make already have option DISABLE_PARALLEL.
@Greisby  Can you please modify ports/mp3lame/portfile.cmake line 109
from
vcpkg_install_make()

to
vcpkg_install_make(DISABLE_PARALLEL)

And try again? thanks.

Hi, it did not change anything.

Hi, it did not change anything.
I checked buildtrees/mp3lame/x64-osx-dbg/libtool, it's still lock_old_archive_extraction=yes

Due to parallel construction, there may be a problem that some files are used by multiple build threads or processes at the same time.
If it is disabled, this issue should not occur.
Not sure why.

This issue hasn’t been updated in one month. If someone has new idea, please reopen this issue.


Opening charts using Fullscreen API

Using FullScreen API for chartjs, I'm experiencing what appears to be the chart re-rendering, and then jagged pieces start appearing on the chart momentarily when your mouse is moving across the chart. I mentioned re-rendering because you the lines appears once you stop moving the mouse.
This problem seems to occur on macOS Safari.
It works well in macOS chrome, and Ipad Safari. I don't have a window to test.
I'm not sure whether it's a bug, I wonder if anyone else experienced this issue and can help me to resolve this?

@daveteu are you able to add a fiddle that reproduces this? Depending on the CSS I could see a resize occurring when you fullscreen the page. Did you notice any console errors when this happened?

@daveteu are you able to add a fiddle that reproduces this? Depending on the CSS I could see a resize occurring when you fullscreen the page. Did you notice any console errors when this happened?

I created an sandbox https://codesandbox.io/s/fervent-mountain-xv2bx?file=/src/App.js

I created sandbox
I figured out that the shaking appears when I set higher resolution ( text smaller ), but I'm not sure whether that's supposed to be the correct behavior I should experience.

Maybe you are hitting the canvas element size limits:

The maximum size for a canvas element is 3 megapixels for devices with less than 256 MB RAM and 5 megapixels for devices with greater or equal than 256 MB RAM.The height and width of a canvas object is 150 x 300 pixels if not specified.

ref

Maybe you are hitting the canvas element size limits:

The maximum size for a canvas element is 3 megapixels for devices with less than 256 MB RAM and 5 megapixels for devices with greater or equal than 256 MB RAM.The height and width of a canvas object is 150 x 300 pixels if not specified.

ref

you referenced a iOS limit.

Can you try, it that makes a difference:
https://github.com/chartjs/Chart.js/issues/8309#issuecomment-774519223

Closing as stale


Sorry, but I really to know what function this line of code do

Sorry, but I really want to understand what this code do
curr_img[1:, 1:] - curr_img[:-1, 1:] - curr_img[1:, :-1] + curr_img[:-1, :-1]
in persim/images.py _transform
pers_img += wts[i]*(curr_img[1:, 1:] - curr_img[:-1, 1:] - curr_img[1:, :-1] + curr_img[:-1, :-1])

This implements an integral image:
https://computersciencesource.wordpress.com/2010/09/03/computer-vision-the-integral-image/
On Thu, Nov 10, 2022 at 10:38 PM Qihe Huang @.***>
wrote:

Sorry, but I really want to understand what this code do
curr_img[1:, 1:] - curr_img[:-1, 1:] - curr_img[1:, :-1] + curr_img[:-1,
:-1]
in persim/images.py _transform
pers_img += wts[i]*(curr_img[1:, 1:] - curr_img[:-1, 1:] - curr_img[1:,
:-1] + curr_img[:-1, :-1])
—
Reply to this email directly, view it on GitHub
https://github.com/scikit-tda/persim/issues/61, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJWDZSO5YHIZ6RXZLDOPG3WHW5SZANCNFSM6AAAAAAR5GRO7M
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Initial Snapshotting Implementation

Summary
This is an initial implementation of snapshot based recovery, where snapshots of each materialized node's state is persisted locally at each domain.
Most of this was done before Christmas, but I hadn't gotten around to pulling in the latest controller (ZooKeeper etc.) changes until now. Sorry about the big pull request - this probably should've been done in smaller steps!
Snapshotting
The snapshot process is initiated by a specific packet, TakeSnapshot, tagged with a numeric snapshot_id. The packet is sent to each base node and forwarded through the entire query graph.
Whenever a domain receives a TakeSnapshot packet, it immediately clones the state of all its materialized nodes and its readers. This is gathered up into a PersistSnapshotRequest, which is then sent to the domain's snapshotting worker. The TakeSnapshot packet is also forwarded through each domain's egress nodes.
Each worker pool has a single snapshotting worker, a SnapshotPersister. These are responsible for serializing and persisting each node's cloned state to disk. The serialization is currently done using bincode.
Finally, each SnapshotPersister notifies the controller after completing a snapshot, through a CoordinationMessage. The controller keeps track of the latest snapshot_id for each domain shard, making sure to only consider a snapshot as completed when all shards have taken a snapshot. Whenever this happens, the latest snapshot_id is persisted to a file (this should probably be stored in ZooKeeper though).
Recovery
Recovery is still initiated with a StartRecovery packet, which now also includes the ID of the latest fully completed snapshot - if there is one. Whenever a domain receives such a packet it attempts to read and deserialize the previously snapshotted state of each of its materialized nodes or readers. This packet is then forwarded through the entire graph, instead of just the domains containing base nodes.
Each log entry now also includes the latest snapshot ID of its domain. This is used during recovery to ensure that log entries contained in completed snapshots are ignored. In the future Soup should probably garbage collect these entries somehow, e.g. by creating a new log file for each incremented snapshot ID and deleting old files.
Benchmarks
So far I've primarily benchmarked two areas: the difference in recovery time using snapshots compared to logs, and the impact snapshotting has on write performance. The benchmarks were run on a server with an Intel Xeon E5-2620 CPU (6 physical and 12 logical cores) and 64GB RAM.
Recovery benchmark
vote-recovery populates the database with a set of articles and votes, and then measures the recovery time from scratch. The benchmark relies on either logs or snapshots in isolation, to clearly see the difference between the two methods.
Two numbers are measured: the time it takes for .recover() to complete and the total time until all recovery writes have propagated through the graph. The latter is measured at the point when readers no longer return stale data, by continuously polling using getters. This is far from optimal, and improvement suggestions are more than welcome. I do think the number is interesting to measure in general however, as it highlights the improvement from snapshotting every materialized node in the graph.
Logarithmic graphs measuring initial and total recovery time:

The initial results are pretty decent: snapshot recovery spends about 40% of the time blocking .recover() compared to using only logs, while also completely propagating recovery updates 10 times faster than with log based recovery.
Write-throughput benchmark
The existing vote benchmark was used to measure the penalty induced by performing periodical snapshots, with a newly added --snapshot-timeout option. The benchmark was run with --avg --mixers=1 --runtime=60, while increasing the snapshot-timeout value in steps of 5 seconds, from 0 to 30.
Write throughput measured with different snapshot timeouts:

As the graph shows, the different snapshot timeouts do not results in wildly different results, with snapshotting in general introducing a ~2% decrease in throughput. This makes sense since the bulk of the snapshotting work is performed by a single snapshotting worker, regardless of the timeout.
To simulate the case where the snapshot worker would have to compete with other threads for CPU cores, I also ran the same benchmark with a gradually increasing amount of parallel writers. This also didn't have too much of an impact on the throughput though, so might need further investigation:
Write throughput measured with increasing parallel writers:

Benchmark improvements
I think it would be interesting to look at how long it takes to complete a snapshot, and at what point a single snapshotting worker becomes overloaded: i.e. what combination of data size, query graph node count and snapshot timeout would prevent the snapshotting worker from completing a snapshot before the next one is initialized? I'm sure there are other cases that should be investigated as well - let me know! There are probably also other benchmarks that should be run to better measure the penalty induced by simultaneous snapshots across the graph.
TODOs
As we've talked about before this is mostly a baseline implementation of snapshotting, and probably not the method that will end up being used. Regardless it'd be nice to get this merged so that future work can be done on top of it. There's a few things that should be fixed before that however:

[x] The latest snapshot ID should be persisted in ZooKeeper, not in a file locally at the controller.
[ ] Snapshots should be initialized in a better way. It's currently done in a separate thread on the controller (from initialize_snapshots), where a ControlEvent::InitializeSnapshot message is sent each timeout tick.
[x] The way snapshot workers notify their controller of a completed snapshot is pretty hacky, as it's done using CoordinationMessages. This works, but feels a bit weird in the local case where there's no source address to be used.
[ ] Diamond cases where a domain might receive two snapshot packets need to be handled, as described in this TODO.

@ekmartin  Do you think we should work towards merging this to avoid continual rebasing onto master, or is it too likely to break things at the current point in time?

@ms705: I think it'd be nice to get it reviewed, and possibly merged. The snapshotting is completely turned off by default, so hopefully it shouldn't introduce bugs in the core functionality. As we've discussed previously there's definitely still issues to resolve in terms of diamonds and snapshot consistency, but I'm not sure if that should be a blocker.
I've made a few minor changes since my last comment:

TakeSnapshot packets are now forwarded through sharders as well (instead of just through egress/ingress nodes).
The latest snapshot_id is now stored in ZooKeeper instead of on the file system of the controller (should maybe store more of the snapshot state here, such as the currently received ACKs).
Snapshot recovery is now initiated in parallel by sending a StartRecovery packet directly to each domain containing a materialized node, instead of propagating it through the graph. Log recovery is then initiated after snapshots have been recovered, as before.
When Soup is run locally, the SnapshotPersister sends ACKs to the controller directly with ControlEvents, instead of going through the TCP coordination layer. There's probably still improvements to be made here, but it should be less hacky than before.

After discussion, we decided not to merge this for now. However, we'll still want to merge it into a branch under mit-pdos/distributary.

Adopted in https://github.com/mit-pdos/distributary/tree/snapshotting


Fix binidng precedence to install proper datanode package versions

This pull request fixes the issue identified in Issue #531 with bad binding precedence for the datanode.rb recipe.

LGTM


feat: Extract Alert Engine WS connector from the main repository

closes gravitee-io/issues#7778

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 1.0.0-issues-7778-extract-ae-connector-SNAPSHOT
download it from Artifactory here

I could review the pom and distribution part, but need someone else to review the code

I've tested locally. It's ok for me

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

1.0.0
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


cut 0.88.0

Wait for all CI before merge.

Looks good to me.
I think there was some confusion on osx with the last release, where the default virt driver was hyperkit rather than vbox, maybe it would be better to change it before releasing?

@cfergeau that was what we thought before but @gbraad was having a strong opinion not to do this way since we want to have default hypervisor from beginning to set user exceptions.


403 Error debugging Core 2.1 MVC with IIE Express

I think this is a bug but am not entirely sure. I have created an ASP.NET Core 2.1 MVC Web app with the default template. I have changed nothing with the default application save for updating the IIS Express applicationhost.config to enable SSL by changing the access sslFlags to sslFlags="Ssl, SslNegotiateCert, SslRequireCert". When I debug from Visual Studio 2017 I get the following error:
Unable to start process C:\Program Files\dotnet\dotnet.exe. The web server request failed with status code 403, Forbidden.
From the HttpFailure and the IIS Express TraceLogFile files it seems as though IIS Express is trying to open the http url rather than the https url. The launchsettings.json has an SSL port defined but it is not using it.
If I run the application without debugging (ctrl + f5) the site opens using the https url and prompts for a client certificate. Is this a bug or am I missing something?
To reproduce this
create a new ASP.NET Core 2.1 Web MVC Applicationproject enabling https with no authentication.
Update the applicationhost.config file in the .vs/config folder of the project and replace access sslFlags="None" with access sslFlags="Ssl, SslNegotiateCert, SslRequireCert".
Debug with IIS Express (f5).

@BillHiebert

If I'm not mistaken, this is a known limitation with ClientCert authentication (or Windows Authentication). Bill can confirm

Correct. Please see https://github.com/aspnet/Mvc/issues/8314, and https://github.com/aspnet/SignalR/issues/2259

Closing as duplicate of known issue.


Docker Toolbox Updates fixes #14561

Tested Mac/iterated with Jeff on fixes
Waiting on formal uninstall;manual now
4 hour work
Fixe #14562 converting Windows to Mac
Found errors in installer need fixes/another iteration
Updated as far as possible with limited installation
3 Hours work
Entering comments from PR review
New screen captures and migration material
Entering Sven's comment
Testing with powershell, Seb's comments
Fix link in upgrade
Minor tweaks to http and typos
Adding deprecation note

Signed-off-by: Mary Anthony<EMAIL_ADDRESS>(cherry picked from commit 6ca22add1845ca87ba9a3ec0c319a70f981545b2)
Conflicts:
docs/installation/mac.md
docs/installation/windows.md

LGTM

@moxiegirl apart from the images, this is only whitespace changes, is that correct? https://github.com/docker/docker/pull/15514/files?w=1
Not sure if all whitespace changes are related (sorry, checking on my phone)

@thaJeztah I thought you'd be asleep.  This pr was left out of the cherry pick cycle.  It is mostly images yes...the original PR was a while back.  If you spot any issues eagle eye...:-) please feel free to file an issue.

@moxiegirl never asleep, always watching LOL. Will do! just noticed it was whitespace only in this one :-)


dataset

Hi !
Why is there no 'dataset/vevo_meta/split/' directory in the dataset? However, generate.py requires this directory. Looking forward to your reply.
thanks.

I added 'dataset/vevo_meta/split/' directory in this repo.


Change font back to Lato?

Related to #9801
Lato 2 supports 4551 characters — 1.7x more than Roboto! The current version of Roboto used by Gitea supports only 2688 characters.
And Roboto looks awful :(

Actually we've removed Roboto in 1.13 so it's only system-native fonts now and I don't see us going back to webfonts. You can of course add a custom CSS file/template to your installation that changes the font to your liking.

@silverwind ok I left comment there https://github.com/go-gitea/gitea/issues/11818#issuecomment-657661674

If the main goal is to support "many more language glyphs", then "system-native" fonts may be a better choice, so okay


[stochastics] update for new stochastic iptimizers in gpy

Current coverage is 38.00%

Merging #323 into devel will decrease coverage by -0.05% as of e4a4344

@@            devel    #323   diff @@
=====================================
  Files         166     167     +1
  Stmts       15253   15313    +60
  Branches     2218    2227     +9
  Methods         0       0
=====================================
+ Hit          5804    5819    +15
- Partial       223     225     +2
- Missed       9226    9269    +43

Review entire Coverage Diff as of e4a4344

Powered by Codecov. Updated on successful CI builds.


Run testsuite on the non-default .mat formats

At the moment, we are only running the test suite of the default .mat format used by matio. It could make sense to extend it to also to test other file formats, for example using Catch2 Generator feature https://github.com/catchorg/Catch2/blob/v2.13.4/docs/generators.md .

Indeed, this allowed me to find a first bug https://github.com/dic-iit/matio-cpp/issues/33

Indeed, this allowed me to find a first bug https://github.com/dic-iit/matio-cpp/issues/33

I added some tests in #30. Unfortunately, it seems that it crashes on Windows when using the 7.3 version of the .mat file. This happens only when matio is obtained via vcpkg, which uses the version 1.5.17, while it is not failing with conda that instead uses the master version. Indeed, it seems that there were some leakages that have been fixed around a week ago: https://github.com/tbeu/matio/commit/905acda6b885b3971b75048b03aa91b2a893c98e. Despite this, the tests are working on Ubuntu and MacOs. I need to check if these tests work on Windows with the latest release (1.5.19).

while it is not failing with conda that instead uses the master version.

I think conda is using libmatio 1.5.19, see https://anaconda.org/conda-forge/libmatio .

while it is not failing with conda that instead uses the master version.

I think conda is using libmatio 1.5.19, see https://anaconda.org/conda-forge/libmatio .

Ah great, thanks. Then I will disable that test on Windows with a version lower than that one.

while it is not failing with conda that instead uses the master version.

I think conda is using libmatio 1.5.19, see https://anaconda.org/conda-forge/libmatio .

Ah great, thanks. Then I will disable that test on Windows with a version lower than that one.

Yes, I think it make sense. In the meanwhile I open a PR to update the matio version in vcpkg: https://github.com/microsoft/vcpkg/pull/15971 .


Fixed browse_from_source.md Link in docs

The link gives 404 error previously on git hub.

Can any one review this ?

If i had write access i would merge it.
@piranna would you be so kind to merge it?

I'm too busy lately due to work and don't seems to decrease in the future, sorry.

@piranna
What are the future plans with this project ?
I am happy to help :100:


Incorrect warning: The property "logging" is not allowed on objects of type "QueueServicePropertiesProperties"

Bicep version
0.7.4
Describe the bug
The following Bicep code for deploying a queue service with properties for logging results in the following warning:
The property "logging" is not allowed on objects of type "QueueServicePropertiesProperties". No other properties are allowed.
To Reproduce
resource queueService 'Microsoft.Storage/storageAccounts/queueServices@2021-09-01' = {
  parent: storageAccount
  name: 'default'
  properties: {
    cors: {
      corsRules: []
    }

    logging: {
      delete: false
      read: false
      retentionPolicy: {
        enabled: false
      }
      version: '1.0'
      write: false
    }
  }
}

Additional context
The parent storage account resource is defined as follows:
resource storageAccount 'Microsoft.Storage/storageAccounts@2021-09-01' = {
  name: stName
  location: location
  sku: {
    name: skuName
  }
  kind: 'StorageV2'
  properties: {
    minimumTlsVersion: 'TLS1_2'
    allowBlobPublicAccess: true
    networkAcls: {
      bypass: 'AzureServices'
      virtualNetworkRules: []
      ipRules: []
      defaultAction: 'Allow'
    }
    supportsHttpsTrafficOnly: true
    encryption: {
      services: {
        file: {
          keyType: 'Account'
          enabled: true
        }
        blob: {
          keyType: 'Account'
          enabled: true
        }
      }
      keySource: 'Microsoft.Storage'
    }
    accessTier: 'Hot'
  }
}

As a workaround, I inserted #disable-next-line BCP037# above the logging object to ignore the warning:
#disable-next-line BCP037
    logging: {

I added the logging object because running what-if without it resulted in the following change:
  ~ Microsoft.Storage/storageAccounts/testfoto/queueServices/default [2021-09-01]
    - properties:

        logging.delete:                  false
        logging.read:                    false
        logging.retentionPolicy.enabled: false
        logging.version:                 "1.0"
        logging.write:                   false

+1. I encountered the same bug today and mitigated it in the same way also adding a comment that leads here.

I encountered the same bug today but when i add the logging properties like you @TsakyDev and @elvenstone did my deployment fails with the error below:
{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/733431ef-9ca9-4cfa-861d-8c09fcf0fcfa/resourceGroups/sm-test-storage/providers/Microsoft.Resources/deployments/main","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidXmlDocument","message":"XML specified is not syntactically valid.\nRequestId:04eccce8-f003-0016-74ed-be9774000000\nTime:2023-07-25T11:48:31.2342772Z"}]}}
But when i comment the logging property, it deploys successfully.


ArgumentError: NilClass is not a valid CodeObject whilst installing RMagick Gem

$ yardoc -v
yard <IP_ADDRESS>

$ gem install --user-install rmagick -v 2.13.2
Fetching: rmagick-2.13.2.gem (100%)
WARNING:  You don't have /home/jbergler/.gem/ruby/1.9.3/bin in your PATH,
	  gem executables will not run.
Building native extensions.  This could take a while...
Successfully installed rmagick-2.13.2
1 gem installed
Installing ri documentation for rmagick-2.13.2...
Building YARD (yri) index for rmagick-2.13.2...
[error]: Unhandled exception in YARD::Handlers::C::MixinHandler:
[error]:   in `ext/RMagick/rmmain.c`:611:

	611: rb_include_module(Class_Pixel, observable);

[error]: ArgumentError: NilClass is not a valid CodeObject
[error]: Stack trace:
	/usr/lib/ruby/gems/1.9.3/gems/yard-<IP_ADDRESS>/lib/yard/code_objects/base.rb:23:in `push'
	/usr/lib/ruby/gems/1.9.3/gems/yard-<IP_ADDRESS>/lib/yard/handlers/c/mixin_handler.rb:10:in `block (2 levels) in <class:MixinHandler>'
	/usr/lib/ruby/gems/1.9.3/gems/yard-<IP_ADDRESS>/lib/yard/handlers/c/mixin_handler.rb:7:in `scan'
	/usr/lib/ruby/gems/1.9.3/gems/yard-<IP_ADDRESS>/lib/yard/handlers/c/mixin_handler.rb:7:in `block in <class:MixinHandler>'
	/usr/lib/ruby/gems/1.9.3/gems/yard-<IP_ADDRESS>/lib/yard/handlers/processor.rb:114:in `block (2 levels) in process'
	/usr/lib/ruby/gems/1.9.3/gems/yard-<IP_ADDRESS>/lib/yard/handlers/processor.rb:112:in `each'

Installing RDoc documentation for rmagick-2.13.2...

Sorry for taking so long. This is now resolved, but the error is still a warning, since the observable variable syntax used is not detectable by YARD (it does not yet support const lookups to resolve variables). A workaround would be to use something like the variable name rb_cObservable to hint to YARD what the actual class name is.


Make relative() case-insensitive for Windows paths + URIs

+ fix some other minor inconsistencies with slash directions such as relative always assuming input and output slash directions match (on Windows, we'd expect relative() on two file URIs to return a relative path, not URI). posixAndURIPaths was renamed to avoid confusion with Windows file URIs (which differ from other posix paths and URIs in that things like relative() will use backslashes in the result).
Removes a workaround in the ignore helper (See https://github.com/sourcegraph/cody/issues/2929), although it might be that there are still other places that are incorrectly case-sensitive on Windows (that aren't using these path helpers).
Test plan

Covered by tests that run on CI (some of which were updated/expanded with this change)

woops ill fix it

@abeatrix @olafurpg this had conflicts with the agent recordings when I merged main. I don't believe I have access to the accounts to regenerate them - is it possible one of you can regenerate them for me?

The tests should pass reliably if you rebase on https://github.com/sourcegraph/cody/pull/3194


Variable group override precedence

Hey,
Say I have multiple environments and a variable group for each environment. But a lot of the variables are same for most of them. So I create a common group and now each environment has the groups common and their own.
If I were override a value that's defined in the common group in one of the other groups, will it work? What gets the precedence?
Thanks!

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

ID: 4827aa99-ae62-bd63-6f2f-a87a4065ed27
Version Independent ID: c9e461ee-7f42-3503-9460-18fa3a807bbb
Content: Variable groups for VSTS and TFS
Content Source: docs/pipelines/library/variable-groups.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

Thank you for your feedback. As noted in previous feedback, the order of precedence for variables where names collide is "Release scoped variable group" < "Release scoped process variable" < "Environment scoped variable group" < "Environment scoped process variable" < "Variable updated by one of the previous tasks in the phase"

Variable override precedence information for builds and releases should be added to the documentation, it helps for strategizing our release train ecosystem.

So what happens when we have 2 "Release scoped variable groups" with a variable with the same name? Which takes precedence? You haven't answered the question.

Upvote for answer


Unable to use gui, items can be taken

Unable to use gui
have not messed with anything besides the config file
error has occurred sense installation
https://pastebin.com/SJyxekw3

This is due to you using v<IP_ADDRESS> of CE which is NOT for 1.13+. Use the dev build if you wish to use it on 1.13+.


FIX: Disabled cursor on disabled category

Pull Request
Related Issues:
[List any related issues or reference them using the syntax #issue_number.]
Fixes #(issue number)
#141
Description:
Add a not-allowed cursor type instead of auto when transaction type "income" is selected
Checklist:

[x] I have tested my changes.
[x] My code follows the project's coding standards.
[ ] I have updated the documentation (if applicable).

Screenshots:
https://github.com/ani1609/Spendwise/assets/65119631/6a1f6bd9-0630-483c-a081-cc8f3b132dc7

@Jaimin25 LGTM!


Boot order remains on Try Install after first reboot

Hi,
thanks for this, it's very usefull.
I'm facing and issue were after cloud init autoinstall, the vm reboots but i can see that the disk is not being unmounted and when it starts it launches installation once again.
Have you got any ideas about this?
I'm trying to work with qemuargs at the moment to set boot order.

@Emanuele94 In most cases when you see the installation again, the user-data was not successfully executed. Can you run qemu in graphics mode to see the logs from cloud-init?

Hi, thanks for the response. unfortunately i cannot use headless false. Though, i'm trying to set the efibootmgr, fist by checking efibootmgr -v once i get the vm working.
The cloud-init validate works fine, i get no errors.

Thanks again man!
i've solved by checking manually efibootmgr -v and than changing as you suggested the order in cloud-init user-data efibootmgr -o


Fix the sample tests

The samples tests are currently failing on master:
https://circleci.com/gh/googleapis/nodejs-dialogflow/4426
We need to fix these before we can ship :)

https://github.com/googleapis/nodejs-dialogflow/pull/162


time to first byte script stops on failure

The Issue
If the time to first byte script runs into a download failure, the script stops and doesn't show any stats. It should continue and show failures / continuing showing stats for completed ones.
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Internal Use
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

This is fixed on master


fix: do not update during render

I've noticed that, probably due to concurrent rendering in react 18, setState within useCookies is being called from within a render of another component:

Component A calls useCookies()
Component B calls useCookies([keyX])
React complains, that component B sets the state of component A during render (as cookies.getAll() triggers listeners)

Our fix was to always pass the keys to useCookies, but since that might not always be an option, I think this should be the correct solution to the issue.

@SantoJambit Thank you for opening a PR on this issue! This change seems very reasonable. I can see how it will avoid side-effects like this. We can include this in the next release. Would you mind fixing the formatting? You can just run npx prettier . --write and commit the result, it should be good.


Refactor arquitetura

:+1:

mmm yeahhhh, I don't know what that means... we need to do a meeting to schedule a meeting about that, mmmkay?


Register form – select multiple languages

Hi team, here is the simplest way to do the multiple selection.
It doesn't look so bad, however I was desperately trying to do it in a better manner, by using vue-multiselect
(https://vue-multiselect.js.org). Precisely, I was trying to implement Tagging.
However, I didn't make it work for some reason.  If not, maybe my solution will work too, anyway we have a lot of tasks to do.

Hi Ekaterina, how is your solution supposed to work? It seems to allow only one item selected for languages in the registration form. I will be looking at vue-multiselect, to figure it out.

Hi @danielhalasz it perfectly works if I keep pressed the Shift button while choosing the options, on MacBook. should be different on Windows/Linux.

oh, you haven't mentioned using the shift key :) but even with that, it does not work on a Mac..tried in Chrome and Safari

if you check in the branch, the code is different..
https://github.com/BeHelp/BeHelp/blob/registerform/frontend/src/components/Register.vue

oh, you haven't mentioned using the shift key :)

@danielhalasz try Cmd if you are on Mac, sorry for mistake :)

vue-multiselect was last updated 3 years ago and is not compatible with Vue3, that's why you couldn't make it work :( will try to look for another solution

@katsmamina I have found that vue-select beta channel works with Vue3..I am experimenting with it now..it seems like a nice and easy solution for our wishes 😄

check PR #155 to see it in action


Collision Detection

Rectangle vs Rectangle
Ray vs Rectangle
Dynamic Rectangle vs Rectangle
Circle vs Circle
...

I'll add more later if I think I need them.
What is most important to me is that a player can collide with a tile map. I have a proof of concept of this somewhere, it works pretty nicely but I think the approach was wrong. Anyway, I'm probably going to need to do 1, 2 and 3 in order to get it working.
I think exposing the collision functions is probably useful, but what I really want is just for the user to be able to do something as simple as collide(hero, tilemap) and just have Bramble figure out how to do it. I'm not sure exactly how this will look but it needs doing.

I have come to think that perhaps it is not a good idea to try and handle collision response at the "engine" level and instead let each game decide how it wants to handle the collision data when it gets it.
I've got a build of AABB working nicely in another project, but I will consider merging it into Bramble soon.
It does 1, 2, and 3.
It doesn't do dynamic rectangles vs other dynamic rectangles.
It doesn't do arbitrary polygons or circles.
The rectangles can't be rotated (it's AABB, baby!)
If we want rotation and arbitrary polygons when we'll need to implement SAT too. There's no need for that just yet.

Added a line vs cubic bezier curve function. It probably needs some tidying up to bring it in line with the rest of the api but it's there.


What type is Axis min/default/max?

From https://github.com/googlefonts/fontmake-rs/pull/2#discussion_r1021844201, is f32 the right type?
https://learn.microsoft.com/en-us/typography/opentype/spec/fvar#variationaxisrecord uses fixed. https://fonttools.readthedocs.io/en/latest/designspaceLib/xml.html#axis-element informs us it's a number.

f32 seems to be the correct type given:

Most (all?) fonts seems to specify these in integer units of order 1e3
We probably don’t want to leak OT specific types into the IR if it can be avoided

closing as f32 is good


Non Compatibilty with .Net Framework 4.5

Thanks a lot for your effort in creating a proper library for C#. Google API Documentation does not have any examples on consuming the their REST API in C#.
I'm trying to use your library in one of my Winforms project that targets .net Framework 4.5. Installing from nuget does not seem to work since there is some compatibility issues with .Net 5. I have tried manually adding the DLLs but still there are some reference issues. Is there an official way to make this work with .Net Framework 4.5 ?

The lowest target of the package is .NET Standard 2.0, however .NET Framework 4.5 is only compatible to .NET Standard at level 1.1, see https://docs.microsoft.com/en-us/dotnet/standard/net-standard for more detail.
This Google Photos package takes dependencies on other .NET Standard 2.0 packages so there really isn't much hope in getting this package to work in your current setup.
I believe your best hope is to update your WinForms app to target .NET Framework 4.6.1 or higher...


chore(main): release 0.45.4

:robot: I have created a release beep boop
0.45.4 (2024-03-09)
Bug Fixes

lib not found (f3666a4)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/samuele-cozzi/obsidian-marp-slides/releases/tag/0.45.4 :sunflower:


Produce a report that summarizes Pass/Fail for each QC check for each sample

We'd like to be able to determine at a glance if any samples failed QC checkpoints in the pipeline.
Produce a summary file that reports Pass/Fail status for each sample, for each QC checkpoint. The summary file can then be loaded into some sort of grid view that will be easy to identify QC failures for a full multi-sample run.

PASS/FAIL flags added for pre-assembly QC module, stored in dictionary 'qc_verdicts' in commit https://github.com/Public-Health-Bioinformatics/cpo-pipeline/commit/48cf43bf875b0c77eb9718a1474945d7558da645


Failed to compile Assemblies couldn't be loaded

I'm tryig to reuse Fable-Repl. However I got  "Failed to compile
Assemblies couldn't be loaded. Some firewalls prevent download of binary files, please check."
both locally and on Azure.
Spent hours to figure out how this enable on firewall.
How did you manage to solve it on the prod server?
Or it just worked without additional setup for you?

Yes, it didn't require any additional setup. I just added the message because some users were reporting the calls to download the assemblies were failing and we concluded it was because of the firewall. But the error message is somewhat generic an the reason could be different in your case: https://github.com/fable-compiler/Fable/blob/972505785486fe003ab70764544c2cf498e32fcd/src/fable-standalone/src/Worker/Worker.fs#L91-L99
Also, please note the repl contains several "hacks" to make it work. Because of this, we don't provide specific support to run it in other environments (although some people have managed to do it). We did write a brief guide on how Fable could be run as a service in web app but it's not battle-tested. You can find it here: https://github.com/fable-compiler/Fable/issues/1651#issuecomment-463286299

Well indeed it seems be not related to firewall...
I quickly went throught steps from the comment and I have interesting finding.
I just deployed all my static files and depedencies/lib to Azure Storage, enabled Webpage option and it works! Real serverless :)

I wanted to include my code in the REPL which points to my domain code (open wrometr.domain.addresses) but it obviously fails to find it.
I included reference to my domain code (github) in paket.depenedencies (first day when I use paket)
however when I do paket install or paket update to download it I have problems with Thoth-org and enums. It is slightly different when I do install or update but I assume the problem is the same - something has change in the Thoth
I have no idea how to fix as I do not understand first why we have both Thoth.Json as nuget and github. I also did the update for both paket and npm so no futher ideas.
Second question : is this really all I have to do to use my domain code in REPL? Include the github url in paket.dependencies ? Need to update paket.references as well ? (how to do it when I use github reference, just point the files from paket-files?


when running a test group using JUnit 5 csvsource tests, need get a good output format like intellij idea did

When running a test group using JUnit 5 csvsource tests, need to get a good output format like intellij idea did, click one test case in the case list then only show the related content in the output window, don't show all contents together.

/extJava


Google Word Sequence CPP Solution added

Hi @sauravjaiswalsj, Please merge Google Interview problem - Word Sequence  C++ solution.
issue is #299
Thanks

@rajvijen : Thanks for Contributing


Updated latest tokens

Description
Updated to the latest tokens
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

New Tokens Added (114):

accent-content-color-default
character-count-to-field-quiet-extra-large
character-count-to-field-quiet-large
character-count-to-field-quiet-medium
character-count-to-field-quiet-small
combo-box-minimum-width-multiplier
combo-box-quiet-minimum-width-multiplier
combo-box-visual-to-field-button-extra-large
combo-box-visual-to-field-button-large
combo-box-visual-to-field-button-medium
combo-box-visual-to-field-button-quiet
combo-box-visual-to-field-button-small
component-to-menu-extra-large
component-to-menu-large
component-to-menu-medium
component-to-menu-small
disclosure-indicator-top-to-disclosure-icon-extra-large
disclosure-indicator-top-to-disclosure-icon-large
disclosure-indicator-top-to-disclosure-icon-medium
disclosure-indicator-top-to-disclosure-icon-small
field-edge-to-alert-icon-extra-large
field-edge-to-alert-icon-large
field-edge-to-alert-icon-medium
field-edge-to-alert-icon-quiet
field-edge-to-alert-icon-small
field-edge-to-border-quiet
field-edge-to-disclosure-icon-100
field-edge-to-disclosure-icon-200
field-edge-to-disclosure-icon-300
field-edge-to-disclosure-icon-75
field-edge-to-text-quiet
field-edge-to-validation-icon-extra-large
field-edge-to-validation-icon-large
field-edge-to-validation-icon-medium
field-edge-to-validation-icon-quiet
field-edge-to-validation-icon-small
field-label-to-component
field-label-to-component-quiet-extra-large
field-label-to-component-quiet-large
field-label-to-component-quiet-medium
field-label-to-component-quiet-small
field-text-to-alert-icon-extra-large
field-text-to-alert-icon-large
field-text-to-alert-icon-medium
field-text-to-alert-icon-small
field-text-to-validation-icon-extra-large
field-text-to-validation-icon-large
field-text-to-validation-icon-medium
field-text-to-validation-icon-small
field-top-to-alert-icon-extra-large
field-top-to-alert-icon-large
field-top-to-alert-icon-medium
field-top-to-alert-icon-small
field-top-to-progress-circle-extra-large
field-top-to-progress-circle-large
field-top-to-progress-circle-medium
field-top-to-progress-circle-small
field-top-to-validation-icon-extra-large
field-top-to-validation-icon-large
field-top-to-validation-icon-medium
field-top-to-validation-icon-small
focus-indicator-gap
focus-indicator-thickness
help-text-to-component
menu-item-top-to-disclosure-icon-extra-large
menu-item-top-to-disclosure-icon-large
menu-item-top-to-disclosure-icon-medium
menu-item-top-to-disclosure-icon-small
negative-border-color-default
negative-border-color-down
negative-border-color-hover
negative-border-color-key-focus
negative-content-color-default
picker-minimum-width-multiplier
picker-visual-to-disclosure-icon-extra-large
picker-visual-to-disclosure-icon-large
picker-visual-to-disclosure-icon-medium
picker-visual-to-disclosure-icon-small
progress-bar-maximum-width
progress-bar-minimum-width
side-label-character-count-to-field
side-label-character-count-top-margin-extra-large
side-label-character-count-top-margin-large
side-label-character-count-top-margin-medium
side-label-character-count-top-margin-small
slider-bottom-to-handle-extra-large
slider-bottom-to-handle-large
slider-bottom-to-handle-medium
slider-bottom-to-handle-small
slider-control-height-extra-large
slider-control-height-large
slider-control-height-medium
slider-control-height-small
slider-handle-border-width-down-extra-large
slider-handle-border-width-down-large
slider-handle-border-width-down-medium
slider-handle-border-width-down-small
slider-handle-gap
slider-handle-size-extra-large
slider-handle-size-large
slider-handle-size-medium
slider-handle-size-small
slider-track-thickness
static-black-focus-indicator-color
static-white-focus-indicator-color
swatch-border-color
swatch-border-opacity
swatch-disabled-icon-border-color
swatch-disabled-icon-border-opacity
text-area-minimum-height
text-area-minimum-width
text-field-minimum-width-multiplier
transparent-black-100
transparent-white-100

Tokens removed (13):

accent-content-color
focus-ring-color
focus-ring-gap
focus-ring-thickness
menu-item-top-to-chevron-extra-large
menu-item-top-to-chevron-large
menu-item-top-to-chevron-medium
menu-item-top-to-chevron-small
negative-content-color
progress-bar-maximum-width
progress-bar-minimum-width
static-black-focus-ring-color
static-white-focus-ring-color

Token values updated (14):

blue-background-color-default
celery-background-color-default
chartreuse-background-color-default
cyan-background-color-default
fuchsia-background-color-default
gray-background-color-default
green-background-color-default
indigo-background-color-default
magenta-background-color-default
orange-background-color-default
purple-background-color-default
red-background-color-default
seafoam-background-color-default
yellow-background-color-default

Potentially rename tokens (10):

accent-content-color -> accent-content-color-default
focus-ring-gap -> focus-indicator-gap
focus-ring-thickness -> focus-indicator-gap
menu-item-top-to-chevron-extra-large -> disclosure-indicator-top-to-disclosure-icon-extra-large
menu-item-top-to-chevron-large -> disclosure-indicator-top-to-disclosure-icon-large
menu-item-top-to-chevron-medium -> disclosure-indicator-top-to-disclosure-icon-medium
menu-item-top-to-chevron-small -> disclosure-indicator-top-to-disclosure-icon-small
negative-content-color -> negative-border-color-default
static-black-focus-ring-color -> swatch-disabled-icon-border-color
static-white-focus-ring-color -> static-white-focus-indicator-color

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 12.0.0-beta.53 :tada:
The release is available on:

GitHub release
npm package (@beta dist-tag)

Your semantic-release bot :package::rocket:


Allow nodeset YAML files to contain ERB

This allows users to embed ERB content into their nodeset YAML files.
This is particularly important when doing Docker testing on a shared
environment since the nodes cannot have overlapping names.
After thinking about a lot of different potential solutions, this one
appeared to be the most flexible and allow users to do what they needed
to in a language that is understood to Puppet users.
If no ERB content is present, there will be no change noticed by
current users.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4190/

@kevpl The 'for instance' is pretty easy!
Go run a Beaker test with docker in GitLab...then go use another PR to run the same module in parallel on the same environment. 💥 Instant death.
Or have a Beaker run with docker fail 💥 instant death with manual cleanup needed. (I'd like my CI system to be able to continue doing CI even when things are a bit of a mess).
Another 'for instance': I want to use my AWS credentials the way I usually do (via environment variables) and I don't want to go hack the AWS backend to Beaker. Hack the nodeset to read those variables in the appropriate place and...instant win.
I'm not asking you to make it more complicated, I'm asking it to support being more complicated if the user needs it. Otherwise, we end up having to write crazy nodeset generator code and wrap beaker in other scripts just to twiddle some variables. The CI system gets more complicated and it makes more work for everyone.
I'm also not recommending that everyone use these capabilities in nodesets, I just want the ability to do so when it makes sense (like when running docker containers on a shared/CI system).

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4212/

@trevor-vaughan @kevpl I can see a lot of handy use cases for ERB nodesets:

keeping secrets out of the CONFIG sections
nodesets that are portable between different environments
ENV-based overrides

@kevpl Are the changes OK now?

As an additional note, I think we might be hitting this on Travis CI when using Beaker to drive Docker. It's evidencing as random test failures but the only way I've gotten it to repeat outside of Travis is to have a run fail in the middle and not clean up my container names properly. My guess is that they're not getting reaped right away and we're hitting a duplicate name error out on Travis.
If I could detect that in my nodeset that I'm using on Travis runs, I could smack a unique ID in there and work around the issue.

retest this please

Build finished.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4279/


Creating User Error 500

When creating a new user Error 500 Internal Server Error closes the connection. Will update email server to mailtrap.io by creating the .env file with connections and login credentials.

Successfully linked mailtrap.io server to ensure that user creation work.

Links to code changes can be found in branch 1-creating-user-error-500


[WIP] puppet: Use r10k to manage modules.

This should make updating/adding modules easier.
Testing Plan:
GIFs or Screenshots:

I just read #7423. I suppose another solution is to install puppet >=4.8 on 14.04 in order to use the latest version of puppet-apt.

@rht thanks for thinking about improving our puppet setup!
Generally, the direction we want to go in is not using any third-party modules, since they tend to be badly implemented and version-dependent, and we're hardly using the ones we have.  The only thing we're using them for is a few lines of apt configuration, which we could probably transition to a bit of custom code that just calls scripts/setup/setup-apt-repo to do the apt repo setup if necessary.


Selecting the last date in DateRangePicker.showDatePicker throws assert error in MonthPicker

Hi,
This is my code
var picked = await DateRagePicker.showDatePicker(
context: context,
initialFirstDate: DateTime.fromMillisecondsSinceEpoch(
_flightSearch.itineraries[0].departureDate),
initialLastDate: (DateTime.fromMillisecondsSinceEpoch(
_flightSearch.itineraries[1].departureDate)),
firstDate: DateTime.now().add(Duration(days: -1)) ,
lastDate: tenYears,
);
when the picker is opened and the user selects the last year and the last date, MonthPickers " assert(!selectedFirstDate.isBefore(firstDate) &&
(selectedLastDate == null || !selectedLastDate.isAfter(lastDate)))" is fired.

I have the same problem.

I observed this problem whenever I pick a different year (especially the last year) then tried to select a date. It seems the selectedLastDate becomes greater than the widget.lastDate
The hack I came up with was to do a conditional if check and reassign the selectLastDate if it's greater than the widget last date.


Terminal: Set Fixed Dimensions crashes font size

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.68.1 and
OS Version: Windows 10 and 11 both latest versions

Steps to Reproduce:

Start and application that logs in the terminal (PowerShell)
Run Termina: Set Fixed Dimension and enter 6000 (it happens with values > 2000)

The resulting terminal looks like this:

Tracked upstream in https://github.com/xtermjs/xterm.js/issues/4186

Tracked upstream, we also have a cap of 4096 pixels now to prevent the canvas from stretching like this


modify copyright at implement.go

Ⅰ. This pr is to modify copyright at pkg\controllers\v1alpha1\alluxio\implement.go

/assign @cheyang

you should add -s when you use command "git commit".  please pr again

交了一个新的PR，ID为#3857，加了-s
At 2024-04-16 22:30:00, "LiYuhang9527" @.***> wrote:
you should add -s when you use command "git commit". please pr again
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

new pr is commented and will be approved soon.  you can cancel this pr

new pr is commented and will be approved soon.  you can cancel this pr


Add support for API version 16

See https://github.com/appgate/sdp-api-specification/tree/version-16

Closed by https://github.com/appgate/sdp-operator/pull/121