Fixing the fast generation

I think I found the problem with the fast generation. Problem probably was in a bug in this line in the _generator_dilation_layer() method:
conv_gate = output_gate + variables['gate_bias']
That it should be:
output_gate = output_gate + variables['gate_bias']
So, everyone that has used the bias parameter as True, has been generating noise for a long time. I test with the image generation (#125) and now all was fine with the fine fast generation (no different outputs between fast and standard generation).

Ops! Please, do not merge the binary file I uploaded in my fork. Just the update in the model.py file  (53ad718).

I posted a cleaned version as #127.

@Zeta36: Should I go ahead and merge #127 or do you want to remove the .wav file from this PR?

@ibab I don't mind, you can go ahead with #127. Actually, I don't really know how to remove the .wav file from this pull request :P.

Okay :)
Thanks a lot for fixing this!
I'm not sure why this problem didn't cause the unit tests to fail.

There is a test for training with a sine wave and overfitting and a test
for generating white noise with an untrained net and doing size and range
checks. We should add a test that generates a sine wave with an overfitted
net to close the loop :)
El dv., 7 oct. 2016 a les 14:43, Igor Babuschkin<EMAIL_ADDRESS>va escriure:

Okay :)
Thanks a lot for fixing this!
I'm not sure why this problem didn't cause the unit tests to fail.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ibab/tensorflow-wavenet/pull/126#issuecomment-252329923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCF5kucT7QlbAltRhVuOLCLvr3S5kcEks5qxpKagaJpZM4KQsy1
.

Thanks @Zeta36 for finding that and the fix! I confirm that it works.

You are welcome @jyegerlehner :)


Updated the pydantic dependency to provide more flexibility for users

Related to #333

Did you run the integration tests with later versions of Pydantic?

@ErnestoLoma I have tested on pydantic-2.7.1 (latest) locally, and the GitHub CI also passes. I hope we don't face any issues with pydantic>=2.0.0,<3.0.0 in the future, as long as Pydantic follows semantic versioning 🤞
It's also worth noting that in pyatlan, we still don't use any Pydantic v2 features (we are still using the v1 compatibility layer pydantic.v1 in our models), so I think we're good to go 😄


Correct already merged issue 4634 "Handle no AWS metrics collected"

The solution merged for issue 4634 [1] had a bug.
This Issue will be used to track fixing that bug.
[1] https://github.com/ManageIQ/manageiq/pull/4634

The bug was:
sort fails when a nil is in the array...the compact needs to come before the sort
[4] pry(main)> ["a", "a", nil].sort
ArgumentError: comparison of String with nil failed


MySQL configuration is using the wrong 'host' value

The host variable that is being passed to mysql::db for both the exported, as well as non-exported resource is not correct.
You're passing the database location in and not the information of the client machine that should be connecting. This causes the resource to be created (or tried to be created) on the MySQL collection side to create incorrect user records.
I would recommend that it should be set to $::ipaddress or $::fqdn or some other value that defaults to one of those.

Resolve in #9


Feature/problem0003

Codecov Report

Merging #6 (75e2806) into main (7c22449) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         9    +2
  Lines           66        93   +27
=========================================
+ Hits            66        93   +27

Impacted Files
Coverage Δ

src/helpers/divisors.py
100.00% <100.00%> (ø)

src/helpers/divisors_test.py
100.00% <100.00%> (ø)

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


RFC: Better events/tasks for deployment automation (dev/build++), may include event-dispatcher being a core dependency

Right now we have dev/build as a critical part of the a production deployment.
That's great, but it's incomplete. In particular, it is inappropriate to call this multiple times on a multi-server environment.
It would be helpful if there were a broader range of points to hook into the deployment pipeline, such as:

Prepare the the content of the BASE_PATH for deployment (e.g. vendor-expose, GraphQL4 where code goes into BASE_PATH)
Prepare an environment's shared resources to prior to activation of the code that this is being run on (e.g. the current dev/build)
Warm this environment prior to activation of the code that this is being run on (e.g. flush, template rendering, GraphQL4 where code generation goes into temp path)

This would mean

automated deployment systems could run these events without needing to know which modules were installed
modules would have more tools to work with

An obvious choice for these hooks would be build tasks. But @unclecheese's work with event-dispatch might also be good base for this.
So the questions are:

What hooks do we want to add to deployments?
BuildTask or event dispatch?

Do we want event-dispatcher in core?
If we used event-dispatcher for this, it will make it a core dependency. Are we ready for that?

Strictly speaking it could be a suggestion, and maybe only a dependency of graphql 4. If we used core build tasks to trigger these events, they could trigger the events only if event-dispatcher were included, and without event-dispatcher it could limit itself to executing only the basics (e.g. dev/build). But that's a bit messy and I'd only do that if there was an important reason to avoid making it a requirement.

The biggest risk about pulling in event-dispatcher is not the code itself, but commitments to the API. IMO we'd want to pull it in as a 0.x dependency, which means that there are fewer stability commitments about its API.

This seems okay to me, as no-one is obligated to use this new API.
In practical terms, however, it may increase the chance that we need to make core support multiple 0.x release lines with differing APIs. In particular, if lots of sites make heavy use of the API and couldn't easily jump to 0.2 o 0.3. To be honest I think that cognitive overload is probably less than trying to invent APIs that are perfect before we try them in production. :P
We can avoid needing to support multiple event-dispatcher APIs in the future by including it but marking it as experimental.
...which brings us back to maybe making it a suggested rather than required dependency.

For the "what hooks do we want" it would be good to hear from people who are more focused on server-setup and deployment.

Agree this is a good idea, and it paves the way for more deterministic cache creation over time. I think ?flush=1 and ?flush=all have basically broken dev's mental models about what cache is invalidated when over the years. I could not tell you if you still need a dev/build/?flush=1 right now without looking up some intricate use cases, and I'm not 100% sure if ?flush=all still does something different than ?flush=1. It's just gotten so confusing over the years that (like everyone else) I'm doing "superstitious flushes", rather than based on sound understanding of caching. That's quite different to e.g. Laravel's caching, which is basically "no caching in dev, generate caches through tasks during deployment". So I think if we're introducing something like this, it needs to be accompanied with a "caching overview" and a "deployment guide" in our docs.
I'd say BuildTask, but extensible via event-dispatch rather than Extension based. No strong feelings about other points.

I love the idea of adding more reactive programming paradigms to the framework, but we're essentially saying the event-dispatcher module becomes a core dependency if we go that route. Have we thought all of that through? Might need a separate RFC.

I'd say BuildTask, but extensible via event-dispatch rather than Extension based.

Do you mean a build task that basically just goes Dispatcher::dispatch($someEvent)? I could roll with that

I love the idea of adding more reactive programming paradigms to the framework, but we're essentially saying the event-dispatcher module becomes a core dependency if we go that route. Have we thought all of that through?

I'll change the heading of this instead ;)

_ prepares to scratch "write a core module" off bucket list_

I think the main choice is:

Do we make it a required module, used extensively, and risk needing to support the current API in 4.x, alongside any future API changes we make.

Do we make it a required module, but clearly mark it as experimental and drop the current API if it undergoes changes in the future

Do we make it a suggested module, with its use guarded by class_exists()

I'm not familiar with the event dispatcher module, would someone mind giving a quick summary of how it would solve the problems in this RFC?

This module in question was https://github.com/silverstripe/silverstripe-event-dispatcher which was originally developed while working on versioned-snapshots.
It's based on Symfony's event system and lets you attach event listeners to a central dispatch service. Notably, listeners are attached to the central dispatch rather than individual objects. This makes it well suited to helping loosely coupled subsystems interact, but less well-suited to connecting the internals of cohesive code within a subsystem. (This is why we opted not to use it for the add/remove callback feature)
For this case you could dispatch events for the various steps in the build cycle. So rather than creating a build task. The event dispatcher provides a way of ensuring that any number of calls can be added to a single extension point.
Triggering an event requires a PHP call, so a simple wrapper would be 1 or more build tasks that do nothing other than trigger the event in question. This could also be a dedicated CLI script, but presenting as a build task probably makes it more findable for Silverstripe devs.
Without event dispatch, you'd probably need a way to, for example, group together a bunch of build tasks and execute them all at once, letting developers add tasks to the pre-existing groups as desired. That's something that event dispatch gives us for free, but if we brought it in solely for this use-case, it'd be a bit weird. So the question is really "would event dispatch be a useful pattern to have in the system" which to me seems like a good idea. I think this was why Aaron initially said "should this be a separate RFC" but I wanted to avoid ticket fragmentation.
As an example of its use, in the case of versioned snapshots, https://github.com/silverstripe/silverstripe-cms-events/ provides a bunch of events around interaction with your content manual that is slightly less granular than individual ORM operations and closer to "individual human button-clicks", while also covering cases such as GraphQL.
One thing that I'm not sure event-dispatch gives us is the ability to tweak the order of the event handlers. This is a bit of a minefield and it's probable that the are better ways of dealing with order-dependency. For example, we could get in the habit of having critical build steps trigger their own before/after events, and developers could attach listeners to those events instead of the parent step. But it needs thought.

@silverstripe/core-team We're moving along the path of core inclusion of silverstripe/cms-events with this new GraphQL v4 PR: https://github.com/silverstripe/silverstripe-graphql/pull/352. GraphQL v4 isn't stable yet, and not required by the core recipe. Once we do that, we'll also take on maintenance of silverstripe/cms-events (as well as a new Symfony dependency). Even with GraphQL v4 stable, I don't believe we need to call silverstripe/cms-events stable, but it should have beta releases. Notably according to our definition of a beta release, while they're targeted at bugfixes we can still change APIs.
Three core committers think that an event dispatcher in core is a good idea in general. Where we struggled before is actually rolling out such a change consistently.
Just for completeness, here's a few unresolved discussion points. Some of those might influence this RFC (given we don't want to split the deployment events from event listener), some of them might become tickets on the module.

Event namespacing conventions (if any)
Wildcard event listeners (if we do namespacing)
Overlap between events and queues (see https://laravel.com/docs/8.x/events#queued-event-listeners)
Conventions for strongly typing events
Dispatcher singleton vs. DI (always going to be global, but making the dependency clearer)
Making https://github.com/silverstripe/silverstripe-cms-events obsolete (inlining it into core)

Quick point of clarification here -- we're not making cms-events a dependency. We're making silverstripe/event-dispathcer a dependency.
The dispatcher provides the backend, and cms-events provides the subscribers to specific events.


Create raspberry-pi-zero-w.md

1.) Created a guide for running a full node on a Raspberry Pi Zero W. This guide will work for Raspberry Pi Zero's without wireless capability, however an OTG -> USB / Ethernet hub must be used if one intends on using USB Flash storage and an ethernet cable.
2.) The only way I found it possible to run Vertcoin on my Raspberry Pi Zero W, was to compile the source on the Pi Zero, otherwise the vertcoind binary would produce segmentation fault errors.
3.) I seriously recommend sideloading the blockchain, it's a Raspberry Pi Zero with a single core CPU and 512MB of RAM.

Sick!
On Wed, Jun 20, 2018, 7:16 PM Sam Sepiol<EMAIL_ADDRESS>wrote:

1.) Created a guide for running a full node on a Raspberry Pi Zero W. This
guide will work for Raspberry Pi Zero's without wireless capability,
however an OTG -> USB / Ethernet hub must be used if one intends on using
USB Flash storage and an ethernet cable.
2.) The only way I found it possible to run Vertcoin on my Raspberry Pi
Zero W, was to compile the source on the Pi Zero, otherwise the vertcoind
binary would produce segmentation fault errors.
3.) I seriously recommend sideloading the blockchain, it's a Raspberry Pi
Zero with a single core CPU and 512MB of RAM.
You can view, comment on, or merge this pull request online at:
https://github.com/vertcoin-project/VertDocs/pull/72
Commit Summary

Create raspberry-pi-zero-w.md

File Changes

A docs/FullNodes/raspberry-pi-zero-w.md
https://github.com/vertcoin-project/VertDocs/pull/72/files#diff-0
(656)

Patch Links:

https://github.com/vertcoin-project/VertDocs/pull/72.patch
https://github.com/vertcoin-project/VertDocs/pull/72.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vertcoin-project/VertDocs/pull/72, or mute the thread
https://github.com/notifications/unsubscribe-auth/AhpvjA_Z63t4fnEtzV1xAq_fgwlk2lEmks5t-uXAgaJpZM4Uw1KT
.


fix hasSalary null reference exceptions, part 2

Context
Turns out there was some code duplication so the issue from this fix resurfaced:
https://github.com/DFE-Digital/search-and-compare-ui/pull/84
Changes proposed in this pull request
Include hasSalary in the view model rather than evaluating the expression twice
Guidance to review
n/a

 Error in search suggested results view


Update sbt-scoverage to 1.6.1

Updates org.scoverage:sbt-scoverage from 1.6.0 to 1.6.1.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

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

labels: semver-patch

Codecov Report

Merging #78 into master will decrease coverage by 6.81%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #78      +/-   ##
=========================================
- Coverage   47.72%   40.9%   -6.82%
=========================================
  Files           1       1
  Lines          44      44
  Branches        1       1
=========================================
- Hits           21      18       -3
- Misses         23      26       +3

Impacted Files
Coverage Δ

.../main/scala/io/circe/bson/BsonCodecInstances.scala
40.9% <0%> (-6.82%)
:arrow_down:

Continue to review full report at Codecov.

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


In-app notification about new version of Dr. Mongo

Has anyone an idea how to let Dr. Mongo users know about a new version available? Directly in-app.
My idea for solution:

app should regularly check for current version on a predefined url (for example: www.drmongo.com/version) and compare it to a constant set in code
if versions don't match, show an icon by the home button + show popup on connections page

Graphics and funcitonality prepared, but need to get version from somewhere + need to discuss versioning.

All done, using GitHub raw file access :)


About experiment result

Hi @felipecruz, what is you rmse  in your experiment using movielens dataset?

Hello @lhxandcxy . What dataset are you referring? ml-100k?
I achieved the same results (MAE) as this work: http://people.ischool.berkeley.edu/~nakov/selected_papers_list/ICML2013_CF_Botzmann_poster.pdf

Hello@ @felipecruz .Thanks! I will try to run your code later :)

Hello @felipecruz. I have rewritten your code without theano and run successfully! Thanks a lot!
I also achieved the same MAE as the work you mentioned.
However , I wonder why I didn't achieved the rmse as the work in "Restricted Boltzmann machines for collaborative filtering",
I achieved almost 1.05 and it achieved 0.95 or less when k=1 in the paper.
I read the paper before, it uses softmax unit as RBM visible unit. It makes no difference to expand softmax unit in your code, but I am quiet confused about sampling visible units. As a softmax unit, it can be sampled by multinomial distribution. In your code, you sample the visible units using binomial distribution. Look forward to your reply :)  .

I also rewrite it in Matlab and also got 1.05 RMSE error. Still not figure out why.

Hello @lhxandcxy . Your point is valid. The binomial was kind of inherited from the regular RBM model where each unit is handled individually. Here's an attempt to change that portion of the code to sample from multinomial.
https://github.com/felipecruz/CFRBM/compare/feature/sample_visible_from_multinomial?expand=1
Can you check? thanks in advance both of you

Hello @felipecruz . It seems that sampling visible units from multinomial makes little d

Hello @lhxandcxy .Thanks on your feedback. If I come up with an new idea I'll let you know. If you have another idea let me know also. Thanks


net: lwm2m: Update security object to 1.1

Update LwM2M security object to version 1.1
Added Kconfig option to switch between object versions 1.0 and 1.1
Signed-off-by: Jarno Lamsa<EMAIL_ADDRESS>

@VeijoPesonen @jheiskan81 @SeppoTakalo  please review

Thank you @VeijoPesonen for your review comments. Those have been now addressed, please re-review.

Thank you for your review comments @rlubos I think I have addressed those, could you please re-review.


[FEATURE REQUEST] Add 3.11 support

Blocked by napari/napari#5514

Looks like it works https://github.com/napari/napari/issues/5514#issuecomment-1651888656


[stdlib] Include POSIXError as part of Glibc

POSIXErrorCode is compiled as part of the platform module on Darwin, but not as part of Glibc on Linux and other platforms. This makes the platforms consistently define POSIXErrorCode which should have been compiling for Linux since https://github.com/apple/swift/commit/8157194e83ea49a3fbadefaf04395b1b15d72474#diff-c86969eead9d9f63ad0faa3e75802e66R268.

Resolves SR-10485.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 787bc36f6d0b68c95052ce70ab90fa7145c4fabc

@compnerd Builds fine on Linux, not sure what the issue is with macOS.
18:45:51 ERROR: Step ‘Publish xUnit test result report’ failed: [JUnit] - No test report file(s) were found with the pattern 'branch-master/buildbot_incremental/swift-macosx-x86_64/swift-test-results/**/*.xml' relative to '/Users/buildnode/jenkins/workspace/swift-PR-osx' for the testing framework 'JUnit'.
18:45:51 Did you enter a pattern relative to (and within) the workspace directory?
18:45:51 Did you generate the result report(s) for 'JUnit'?"
18:45:51 [BFA] Scanning build for known causes...
18:45:51 [BFA] No failure causes found
18:45:51 [BFA] Done. 0s
18:45:51 Adding one-line test results to commit status...
18:45:51 Setting status of 787bc36f6d0b68c95052ce70ab90fa7145c4fabc to FAILURE with url https://ci.swift.org/job/swift-PR-osx/12537/ and message: 'Build finished. No test results found.'
18:45:51 Using context: Swift Test OS X Platform
18:45:51 **Build failed**

@swift-ci please test macOS platform


Fix NotFoundAction handling

Previously POSTing to an unknown path would result in a 200 with an
empty response body, instead of the expected 404. Multiple problems:

The NotFoundAction was only bound for GET requests
The NotFoundAction only supported requests with Accept: text/plain

The NotFoundAction is now bound for both GET and POSTs, and supports
requests for any type of content (but always returns text/plain). Also
added a backstop in the WebActionsServlet to return a 404 if no suitable
action could be found; this handles cases where applications do not
install the NotFoundAction, or when a request arrives with an
unsupported HTTP method.

This was previously approved, but I think got lost in the reformatting

And sorry about the reformatting slaughter.


Trade-off pnr time and performance

When experimenting with SymbiFlow a long time ago (almost 2 years ago) I was able to adjust vpr parameters such as astar_fac, max_criticality, acc_fac, initial_pres_fac, etc. to trade-off pnr time and performance. After experimenting with this again recently, it seems changing these parameters no longer provides a significant speedup over the default values.
I am wondering if anyone knows a way to decrease pnr time if I am willing to make significant sacrifices to performance. Are there known changes within VPR that have reduced the impact of these input parameters?

There was an effort to make this trade-off (see https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1735 ).  I'm not surprised you were not able to extract more runtime.

@litghost I have looked into that work, but my understanding was that it wasn't willing to reduce QoR.  Is that correct?

@litghost I have looked into that work, but my understanding was that it wasn't willing to reduce QoR. Is that correct?

That is true.  You can checkout the raw data used in #1735 in https://colab.sandbox.google.com/drive/1X91RGZnvlC7dBjJJUbS7JfqCbPCzJ3Xb?usp=sharing


various cleanups for 1.3.0

This does mostly cosmetic work for 1.3.0.
It includes renaming of some macro-related code.
Also addresses case where addSampler is given a sampler name that includes the namespace.

@kenkellner I've merged in cleanups_1.3.0, which has the macro-related changes we've been discussing, into devel.
So I think you can go ahead and update nimbleMacros  to be consistent with devel.


Fix: Block Related Images on Google Images

Summary
This PR fixes issue #521 where related images on the Google Images page were not being blocked on Desktop.
Some minor alignment improvements for action/control buttons are also included.

Technical Explanation
The udm=2 handler on Desktop was missing a pagerHandler attached to a serpEntry rule.

I just noticed, but this PR is also a fix for #440

Thank you for your contribution.


Can't display minus sign (-) correctly when file is txt

I push a txt file which contains the minus sign (e.g -1) will  be display as " â€“ " in the web page, but when i view   the original file, it is correct.
Type            number of bypes                             Range of value
char                    1                                           â€“128 to +127 or 0 to +255
should be
char                    1                                           -128 to +127 or 0 to +255
Environment:
gogs: 0.8.10
OS: ubuntu 15.04
git: 2.1.4

Can you reproduce on https://try.gogs.io ?

@jenningsloy318  You might have some unicode character for "minus". Please look at it in hexffump or hd. Gogs should still understand such symbol.

I can't confirm after trying few unicode '-' characters.
Gogs prints unicode characters from particular source files as-is, and page has charset=UTF-8.
So the user needs to provide what character this was in hex, what browser/OS did he use.

I used the VIM to edit the file.
when i ued hex edit to display the -, it give me
â --->20

I used the VIM to edit the file., and VIM shows me that the file is UTF-8.
HEX shows the character (-) is E2
not tested in try.gogs.io

Please reproduce on demo site, otherwise we can't help and no idea of what is going on.

Tested in try.gogs.io, but it displays normal.
Is there any other config relevant with this?

No config, maybe you need to upgrade?

wii try to edit the file and re-push again to see if this issue is fixed.

I found that gogs can't display the "±"      " ’ " used in  isn’t .

Sorry, I dont know what you are talking until you can show us on the demo site.

@jenningsloy318 : The way to deal with such problem:

What does hexdump say the characters hex representation is?
What does the 'file' utility say the file encoding is?
Does the source of the gogs html page have "" in it?
What browser do you use? Did you try another browser? (chrome, firefox, opera)

Because I can't reproduce the problem.

I can't  get this situation react, will close this issue.


pull request for e2e test at 12/21/2016 21:26:18

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[WFRP4e System] «the wrong type of Corruption»

When running a Corruption test, the error "the wrong type of Corruption" occurs
@Corruption[minor], @Corruption[moderate], @Corruption[major]From: mr.denginfoundry: 12.331wfrp4e: 8.2.3wfrp4e-altdorf: 6.0.1wfrp4e-archives1: 6.0.1wfrp4e-core: 6.0.1wfrp4e-dotr: 6.0.1wfrp4e-eis: 6.0.2wfrp4e-middenheim: 6.0.2wfrp4e-pbtt: 6.0.0wfrp4e-rnhd: 6.0.2wfrp4e-starter-set: 6.0.1wfrp4e-ua1: 6.0.1wfrp4e-up-in-arms: 6.0.2wfrp4e-wom: 6.0.2Active Modules: JB2A_DnD5e, ambientdoors, autoanimations, babele, chat-images, chat-portrait, colorsettings, combatbooster, dice-so-nice, drag-ruler, foundryvtt-simple-calendar, fxmaster, illandril-token-hud-scale, image-hover, lib-wrapper, monks-tokenbar, party-overview, permission_viewer, popout, ru-ru, ru-wfrp4e, scaleGrid, sequencer, simple-dice-roller, socketlib, splatter, token-action-hud, token-hud-art-button, token-variants, tokenmagic, tokenmagic-automatic-wounds, vance-sidebar-resizer, warhammer-lib, wfrp4e-gm-toolkit, forge-vtt

Non reproducible, or I don't understand what this means

sounds like issue with translation to me

Probably. Please consult the developer of the translation being used. Closing unless I need to address something.


Compatibility with Scratch 2.0 → 3.0 userstyle?

See mxmou/customize-scratch#24
I want my userstyle's dark mode feature to be compatible with this. The problem is that your userstyle sets .markItUpDropMenu's background to transparent, while mine sets its background color to #e0e0e0 and doesn't remove the image. They also set different sizes of the buttons. It would be best to make some changes to both this and my userstyle.
The best solution in my opinion is to use CSS variables to inform my userstyle that this one is enabled (would that work?) and then the black icons could be replaced with white ones in dark mode instead of having a light gray background.

Closing this as I agree with the solution suggested here.

@easrng I'm now working on this and realized that if my userstyle sets a variable that isn't enough because not only the icons should get inverted, but the light background added by my userstyle should be removed. The relevant part of my code looks like this:
.markItUpHeader > ul > li
.markItUpHeader > ul > .markItUpDropMenu
    background-color: #e0e0e0
/* ... */
.markItUpHeader > ul > li:hover
    background-color: white

If your userstyle set a CSS variable:
:root {
    --material-buttons: 1;
}

It could be changed to something like this:
.markItUpHeader > ul > li
.markItUpHeader > ul > .markItUpDropMenu
    background-color: rgba(224, 224, 224, calc(1 - var(--material-buttons)))
/* ... */
.markItUpHeader > ul > li:hover
    background-color: rgba(255, 255, 255, calc(1 - var(--material-buttons)))

This way the invert() can be in my userstyle instead.

Both userstyles are now available in Scratch Addons and compatible with each other (ScratchAddons/ScratchAddons#3940).


Updated for changed BETYdb instance

Update for Action - no review

Codecov Report

Merging #64 (05c8aab) into develop (05d1572) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #64   +/-   ##
========================================
  Coverage    62.09%   62.09%
========================================
  Files            5        5
  Lines          372      372
========================================
  Hits           231      231
  Misses         141      141

Continue to review full report at Codecov.

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


Add Microconfig

Open source tool created to do configuration management.

Taken together, it is not currently planned to incorporate the product you recommend, thank you for your submission


Backport "Warn if extension receiver already has member" to LTS

Backports #17543 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-20227.
Reference


Can update to use scraperapi.com api  ???

Hey guys, I have been testing plain several proxies, not even using the instagram scraper, .. they are able to detect each of the proxies tested. the only working service I have tested that will give me the instagram correct output is scraperapi.com ,
so I guess the instagram scraper can be update to using scraperapi.com api to retrieve the data, this will definitely be the best course of action.
particularly for my use im caching the data into a .json and and checking the last updated before using any scraping again :)

Hey, how did you manage to implement scraperapi?
I’ve been trying but I kee getting 400s.
Can you please show some code examples?

Hey, how did you manage to implement scraperapi?
I’ve been trying but I kee getting 400s.
Can you please show some code examples?

Same too

Hey guys, I have been testing plain several proxies, not even using the instagram scraper, .. they are able to detect each of the proxies tested. the only working service I have tested that will give me the instagram correct output is scraperapi.com ,
so I guess the instagram scraper can be update to using scraperapi.com api to retrieve the data, this will definitely be the best course of action.
particularly for my use im caching the data into a .json and and checking the last updated before using any scraping again :)

Can you provide an example of your code, please?


Failures on [repo] improve the analysis of the tools/ directory

There are new test failures on [repo] improve the analysis of the tools/ directory.
The test
standalone/io/addlatexhash_test CompileTimeError (expected Pass)

is failing on configurations
dartdevk-checked-mac-release-chrome
dartk-strong-linux-debug-x64
dartk-strong-linux-release-x64
dartk-strong-mac-release-arm64

Log in strong mode is stderr:
tools/addlatexhash.dart:25:1: Error: A library can't opt out of null safety by default, when using sound null safety.
// @dart = 2.9
^^^^^^^^^^^^^^

Thanks, I'll take a look.

This CL might address it: https://dart-review.googlesource.com/c/sdk/+/233530.
It looks like tools/addlatexhash.dart is being imported by tests/standalone/io/addlatexhash_test.dart (though I'm not sure why).
https://github.com/dart-lang/sdk/blob/main/tests/standalone/io/addlatexhash_test.dart#L10

@whesse - I'm having trouble determining if this did in fact address the failure. Do you mind checking?

It looks like it has, from the result feed:
https://dart-ci.firebaseapp.com/#showLatestFailures=false&test=standalone/io/addlatexhash_test
I think it only shows up as fixed on three configurations, because the others run on daily builders and haven't run yet.


Remove Apple Copyrighted ICC profile from test orientation images 2-8

An ICC profile which is Copyright 2007 Apple Inc. has been added to landscape_{2..8}.jpg, presumably by the tool used by the exif-orientation-examples project to process the images. It seems probably that these profiles are incompatible with Free software licensing (see, for example, the discussion at [0]) and they are unnecessary for the purpose of demonstrating exif orientation. I have removed them with the command:
for i in {2..8}; do convert landscape_$i.jpg +profile "icc" landscape_$i.jpg; done
It is also necessary to make a slight adjustment to a tolerance in tests/test_wand.py.
I have also reported this upstream https://github.com/recurser/exif-orientation-examples/pull/6
This Closes Issue #46.
Thanks.
Christopher Hoskin
[0] https://lists.debian.org/debian-devel/2014/05/msg00312.html

Thanks for resolving this, and apologies for being a little bit hasty in closing #46


BIGTOP-3778: Fix Hive3.1.3 WebHCat service compatible issue with Hadoop3.3.x

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
[ ] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

Thanks for working on it, @kevinw66
What about adding JIRA number prefix to the patch name like patch11-HIVE-24083-webhcat-xxxx.diff ?
It could be convenient for us to track the Hive issues and reduce our maintenance burden in Bigtop.  If it was merged to Hive trunk, we could easily remove it from Bigtop.
Thanks.

@guyuqi Done

Let me test it by Hive building and Hive deployment in Mapck.

+1.
Tested build and smoke tests on Rockylinux-8:
Successfully started process 'Gradle Test Executor 2'

Gradle Test Executor 2 started executing tests.
Gradle Test Executor 2 finished executing tests.

> Task :bigtop-tests:smoke-tests:hive:test
Finished generating test XML results (0.023 secs) into: /bigtop-home/bigtop-tests/smoke-tests/hive/build/test-results/test
Generating HTML test report...
Finished generating test html results (0.028 secs) into: /bigtop-home/bigtop-tests/smoke-tests/hive/build/reports/tests/test
Now testing...
:bigtop-tests:smoke-tests:hive:test (Thread[Execution worker for ':',5,main]) completed. Took 24.281 secs.

BUILD SUCCESSFUL in 1m 34s

Verified Hive Mapck deployment on Arm64/x86_64:

Merged, thanks. @kevinw66


Program for Lowercase to Uppercase

Name - Vishal Arunagiri
Community - GDSC-RAIT , RAIT-ACM

Already done by other user try again  with dif branch name / language


shapes of inputs

hello! currently, the inputs to the layers assume that it is an image, but it would be great if one can use it for a sequence of vectors (which is what you do I suppose internally).

It should work for arbitrary tensor shapes. Originally it supported up to 3-dimensional tensors, which were intended to be used for transformers. It should work for 2D cases now.
# sequence modeling case: [batch_size x num_tokens x feat_size]
vq_layer = VectorQuant(feature_size=32, num_codes=512, dim=-1).cuda()
z_e = torch.randn(16, 8, 32).cuda()
vq_layer.codebook.weight.data[:128] = z_e.view(-1, 32).data.clone()
z_q, vq_dict = vq_layer(z_e)
assert torch.allclose(z_q, z_e)

# 2d matrix case: [batch_size x feat_size]
vq_layer = VectorQuant(feature_size=32, num_codes=512, dim=-1).cuda()
z_e = torch.randn(128, 32).cuda()
vq_layer.codebook.weight.data[:128] = z_e.data.clone()
z_q, vq_dict = vq_layer(z_e)
assert torch.allclose(z_q, z_e)

Does this solve this for your case?

ah ok... i actually never tested... my bad!

feel free to open up the issue back up if you run into any issues.


test(bn-btn): test loading and href logic

Context

Banano is a component library for use in platanus projects

Changes
This PR adds tests for the BnBtn component, focusing mainly in logic and not in style changes, like other components' tests

 Btn no tiene test


Adding "undecoded_path" to providers. This should be the first step f…

…ixing Issues with special characters in names
Pulled the request uri out of the tornado header, then split it based on the provider name and '?'
There may be a few edge cases where this splitting could be a problem, but since its the non-decoded path, it should be okay(shouldn't hit any problems with splitting on '?')
refs: https://openscience.atlassian.net/browse/SVCS-256
Purpose
We need the un-decoded file name to distinguish between files with special characters.
ie: "me/ow.txt and me%2Fow.txt" The decoding tornado does makes these files hard to distinguish.
Summary of changes
Added an "undecoded_path" variable to the base_provider. This gets set in the "prepare" function to be the undecoded_path received from the request. The path is pulled from 'self.request.uri'
QA
QA will come on individual tickets for providers

Coverage increased (+0.008%) to 76.688% when pulling 7ea50793e50e358580a67d670aaaee881d395b9b on AddisonSchiller:feature/url_decode into b787a92c180697cb8fb2f5b6c402cf7b931b339d on CenterForOpenScience:develop.

Coverage increased (+0.02%) to 79.342% when pulling a19fc66b3452e0f6397e63fe7a3976c7c8f79ee7 on AddisonSchiller:feature/url_decode into 879aedd4a424f5079929cf435c1cebe80e0cc2f7 on CenterForOpenScience:develop.

Coverage increased (+0.02%) to 79.342% when pulling a19fc66b3452e0f6397e63fe7a3976c7c8f79ee7 on AddisonSchiller:feature/url_decode into 879aedd4a424f5079929cf435c1cebe80e0cc2f7 on CenterForOpenScience:develop.

Added requested Changes

Coverage increased (+0.02%) to 79.342% when pulling a8717a57a02d9741cabb1a2ed9d452174c49c763 on AddisonSchiller:feature/url_decode into 879aedd4a424f5079929cf435c1cebe80e0cc2f7 on CenterForOpenScience:develop.

Might want to wrap up this conflict.


Formatter should insert a new line between method invocations with do ... end

def foo
  yield
end

foo do
  puts "1"
end
foo do
  puts "2"
end

I would think it should be formatted to:
def foo
  yield
end

foo do
  puts "1"
end

foo do
  puts "2"
end

This would match the behavior when two methods/types are defined without a newline.

I just don't think this rule is wanted all the time.

I just don't think this rule is wanted all the time.

Could be worth implementing a PoC to see what the diff would look like, it someone's interested in doing that.
It's not a high priority, though.

Could be worth implementing a PoC to see what the diff would look like, it someone's interested in doing that.
It's not a high priority, though.

Elixir's formatter puts every multi-line construct in its own "paragraph", and in my experience it has never improved the output in any way (on top of the other things Elixir also puts a newline and indents for).

Elixir's formatter puts every multi-line construct in its own "paragraph", and in my experience it has never improved the output in any way (on top of the other things Elixir also puts a newline and indents for).


Team Wiki

demo wiki functionality in this repo to team

discussed this with Julia today, will try to discuss with Team at meeting today (Feb 28/2023)

Check in with Julia to make sure that everything she needs to move forward with a wiki has been completed


First implementation of manifest autoupdate

Hi
Some time ago I added checkver informations to a lot of manifests, now we know that a lot of manifests are outdated. It will take a lot of work to update all those manifests manually.
I started implementing an easy way to update manifests. The idea is that the checkver script not only finds the newest version string but also the download urls and hashes for the files.
Most time the download url can be build by only knowing the version string, alternatively it can be extracted from the website. The hashes can be obtained from the download page (php etc.) or from a separate file (nodejs etc.) the last resort would be downloading the file and hash it locally.
I implemented a the base for it, the nodejs manifest contains the new autoupdate block. Running bin/checkver.ps1 nodejs -u updates the manifest file with the newest version. Of course the current nodejs manifest is up to date.
Writing the JSON file from powershell results in a not that pretty file as you can see in the attached commit, this is one of a few things that can be improved
I would like to have some feedback about the idea

What do you think about it?
Would a complete implementation be appreciated?
I am new to powershell scripting, any comments/tips to my coding style?
checkhash could be implemented to spot broken manifests

Todo (some todos are documented in the sourcecode)

Implement more ways of getting the URL and Hash (Extract from page, Github Release, etc,)
Better JSON output (any ideas how to do that)
Testing
Writing documentation

This is great! Nice work. Should keep programs much more up to date and save lots of tedious work at the same time. It'd be great if you can keep going with this.
How hard would it be to split out the checkver and autoupdate parts into another autoupdate directory, i.e. autoupdate\node.json? I think it's worthwhile keeping app manifests simple so it's easy to see what install steps will be taken, and to make it less intimidating to get started writing manifests. And a separate directory will allow us to see at a glance which apps have autoinstall and which don't. Would that work?
Your Powershell coding style is nice. No complaints there!
JSON output – I think scoop create suffers from similar problems. The automated tests show an error about the UTF8-BOM, so might need to do this sort of thing. I know it's lame, but maybe you could do a regexp replace to clean up the indentation and any other formatting problems.
Thanks for your work, and I'm looking forward to seeing what you come up with next!

Thanks, I will continue implementing it
I am not sure if splitting the manifest into multiple files will be a good idea. I would like to encourage people to also add the optional checkver and autoupdate blocks if possible. But I understand your point.
It would be easy to do it.
The ConvertTo-Json will be improved soon PowerShell#2736 I will add a function to reformat the json output.
Is there a better place to discuss this?

Great! If you think it works better to keep autoupdate in the manifest then that's fine by me. I think package maintainers will jump on this functionality either way if it's available.
You can email me directly at<EMAIL_ADDRESS>if you like, otherwise here on GitHub is probably the best place for discussion.

Better JSON Output will land with PowerShell 6 https://github.com/PowerShell/PowerShell/releases/tag/v6.0.0-alpha.17


option to provide defaults for env variables that are not set

I was going to go with try/except around TEST_MODE, but adding a new optional argument to _get_env_var we can use this for other use cases too.
Issue: https://github.com/PyBites-Open-Source/karmabot/issues/84

Superseded by https://github.com/PyBites-Open-Source/karmabot/pull/97 < that PR I'd love to go in which includes the changes from this PR.


Post close fixes

Hey @VaibhavSimusolar I don't think we need this anymore, right? The diff is empty. I'm closing the PR.


Added fill_value for unstack

[x] Closes #3518
[x] Tests added
[x] Passes black . && mypy . && flake8
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

Added an option fill_value for unstack.
I am trying to add sparse option too, but it may take longer.
Probably better to do in a separate PR?

Hello @fujiisoup! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file xarray/tests/test_dataset.py:

Line 2808:9: F821 undefined name 'assert_equals'
Line 2812:9: F821 undefined name 'assert_equals'

Thanks, @max-sixty, for the review :)

Great to see you back! Hope all's well


Modal : Pass remote response data to 'loaded' event

Modal : Pass remote response data to 'loaded' event  …

Pass response data from remote loading to the 'loaded' event so we can handle them.

data : data from the response
textStatus : Status of the response (cf. JQuery documentation : "success", "notmodified", "nocontent", "error", "timeout", "abort", or "parsererror")
response : The whole response object

This would be very useful for many of us who load content throught the data-api and would like to handle stuff from time to time.

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: a0d898026148b21b5a8912435ee3708073769260
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/134992328
(Please note that this is a fully automated comment.)

Bootstrap v3 in general is no longer open to new features.
The loading feature of modals is deprecated and has been removed in Bootstrap v4.

Therefore, going to decline this PR.
We appreciate the thought though!

sobbing *

Ok, too bad, I'll find a workaround. Thanks anyway !


Add setTitle logic

Closes #1852

Coverage remained the same at 78.819% when pulling 4596a559981dafff8ab470068ebb07765c917acc on eatonphil:add-titles-to-docs into 568bf00788b46a133d38df4fbff2946610a886b2 on linode:develop.

Coverage remained the same at 78.819% when pulling b2e49f77f27beadafebcae548afd7f4baea515c8 on eatonphil:add-titles-to-docs into 568bf00788b46a133d38df4fbff2946610a886b2 on linode:develop.

Coverage remained the same at 78.819% when pulling b2e49f77f27beadafebcae548afd7f4baea515c8 on eatonphil:add-titles-to-docs into 568bf00788b46a133d38df4fbff2946610a886b2 on linode:develop.

thank you!


Fix: removes default parameter name for terraform provider

Description of your changes

Fixes #5427
I have:

[x] Read and followed KubeVela's contribution process.
[x] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

After offline talk with @afzalbin64 . #5427 should be fixed by remove default provider name ("default") in config templates. This PR can be closed.
See: https://github.com/kubevela/catalog/pull/638

Please fix the test.

cc @chivalryq @wonderflow


Exploratory Testing: Shadow state

@mikary moving this to your plate. When chat about what it encompasses whenever you are ready.

The interaction between FromSql and shadow state hasn't been tested yet, this is an area that could use some coverage.

The only thing we need to do for RC is verify that query works with the new API pattern we decided on. After that, this can move to the 7.0.0 milestone if there is anything we think needs doing.

We are happy that we have covered this


Z390 Gaming Pro Carbon AC support?

just seeing if this program is still being updated at all and if there's any support for the z390 chipset. MSI Mystic Light is very limiting. Especially when selecting multiple parts. When i used Aura i was even able to change the individual LEDs on my RAM.

Hi there I have a z390-A pro and can confirm it works, im sure theyre pretty similair

Thanks @Wtcheesecakes for the feedback. However, different motherboards, however similar, may have different mechanisms. The Z390 Gaming Pro Carbon AC doesn't seem to be supported by MSIRGB.


support multiple tunnels in wstuncli

Is this necessary as you can run multiple lightweight instances of the client?


Make it easier to choose a custom range of bus departure times

User feedback:

Please allow access to previous departures for more than 3 minutes!! There is a very narrow window to report a late/no show bus and no sense of whether a particular bus is e.g. an early 9:15 arrival or an extremely late 8:55 arrival.

My response:

Viewing late/no-shows goes back 5 minutes, but if you tap on "Report a Problem" you'll see buses that go back 30 minutes.

I agree that the latter problem is definitely an issue. I'm not sure how to best address it, though, without creating a significant amount of cognitive overhead for people whose buses are running on time, though, unfortunately. I've been thinking about supplementing "Load More" with a double-sided slider that would let you choose a wider range of default times.

[ ] Design
[ ] Implementation

Interestingly, I'm getting the same request from users on OBA Android for the first time:
https://github.com/OneBusAway/onebusaway-android/issues/728
I'm guessing there is a new systematic data issue for a route in Puget Sound.


Add resources

NBA API
RAPID API-NBA
How to make NBA Shot Charts
Excel - Create an NBA Shot Chart Using Python & Copilot
How to Create NBA Shot Charts in Python
Plotting with Python play-by-play data of NBA Games (2015–2021)

Inspire from architecture of RAPID API-NBA


PGN cleanup may break comments

It looks like these global replacements are intended to gracefully deal with invalid PGNs enclosed in [pgn]...[/pgn], using non-ASCII dashes in O-O and O-O-O, and en passant captures like exd6 e.p.. But they would also incorrectly modify comments.
https://github.com/ornicar/scalachess/blob/6e6062fd3f9ddba870051ceaf9e47b87733a7d2d/src/main/scala/format/pgn/Parser.scala#L24-L28

I was wondering about this part as well. With the current implementation we don't really need this step.
Removing this step also helps us show the error location correctly. Now we can only show the location of the error in the pre-processed string, not for the whole original string.
I can work on this issue.


How to get indentation too?

I am newbie to this plugin. So, without nvim-autopairs,it works like this.
int functionname() {
    |

with , nvim-autopairs , i get this,
int functionname() {
|}

I wanted this.
int functionname() {
    |
}

Please help me. I want closing brace to be on next line

check readme about mapping .
if it still not working  download your language pack from plugin or enable treesitter indent
https://github.com/windwp/nvim-autopairs/issues/24


Tuya Third-patry authorization management

Hi jasonacox,
I noticed that Home Assistant has a 'Third-party authorization management' feature with a user code that is provided in the Tuya-based app. Do you think this could be possible for your project to bypass the 6-month renewal?

Is that for cloud access? I suspect it is and wouldn't help with those wanting local access. But may be worth exploring.
What is the HA plugin called?

Yes is for cloud access at HA, If users add a new device after 6 months of the last dump of the json they need to extend the subscription. Here is the location https://github.com/home-assistant/core/tree/dev/homeassistant/components/tuya

I hope they answer, but I am afraid not.


Display user's current location if available

Modules that interact here are:

maps.Controller
mapstate.Service
index.js

Also these concepts are important:

My location button
Tracking my location (on/off)
Starting up at my location if no previous location is known (too rare to be useful I think)

Implementation plan:

if geolocation api is available, create button (what if user denies permission?)
if geolocation api is available and user gives permission, show a blue dot on the map
if the tracking button is pressed, it stays down
while the tracking button is down the center of the map follows the blue dot
if the map is panned or zoomed, the button pops up and tracking is stopped.


Protect against wrong ordering on events - events before the workflow start event occurs

Situation
This high level code:
activeJobs := set.NewSet[string]()  // section 1: lines
workflow.Go(ctx, func(ctx workflow.Context) {  // section 2: lines
   ...
   workflow.CreateSubWorkflowInstance[result.Conclusion](ctx, workflow.SubWorkflowOptions{
				InstanceID: jobInstanceID,....Get(ctx)  // section 2: lines, label: B
}
...
for activeJobs.Len() > 0 { // section 1: lines
   ...
   if err := workflow.SignalWorkflow(ctx, jobInstanceID, signals.Canceled,  // section 1: lines, label: A
   ...
}

Creates two go-routines (backed by co-routines) in go-workflows:

Handling section 1
Handling section 2

We proceed with the go-routine util it's blocking and then give the other go-routines a chance to move forward.
So, we can end up with the follow execution order: section 1 -> section 2
Meaning, for jobInstanceID, these are the events:
EventType_SignalReceived (from label: A) -> EventType_WorkflowExecutionStarted (from: label: B)
What happens
When that happens, we should handle the signal received first which calls e.workflow.Continue() which calls w.s.Execute()
But wait! workflow scheduler (that's the s) was never set! It gets set at NewWorkflow which is called from handleWorkflowExecutionStarted.
So we get
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xd95e64]

goroutine 178 [running]:
go.opentelemetry.io/otel/sdk/trace.(*recordingSpan).End.func1()
        /go/pkg/mod/go.opentelemetry.io/otel/sdk@v1.7.0/trace/span.go:359 +0x34
go.opentelemetry.io/otel/sdk/trace.(*recordingSpan).End(0xc000540000, {0x0, 0x0, 0x0})
        /go/pkg/mod/go.opentelemetry.io/otel/sdk@v1.7.0/trace/span.go:398 +0xafb
panic({0x1236920, 0x1b27c30})
        /usr/local/go/src/runtime/panic.go:890 +0x267
github.com/cschleiden/go-workflows/internal/workflow.(*workflow).Continue(0x0)
        /go/pkg/mod/github.com/cschleiden/go-workflows@v0.6.1-0.20220914182430-72955318893d/internal/workflow/workflow.go:88 +0x24

What should we do
We can either handle it and fail OR fix it.
Suggestion is to fix it, similar to what azure durable task did (Thanks @cschleiden for pointing this), this is fixing/band-aid after the situation occurs.
From @cschleiden:
Maybe we could at least do that on the way in (preventing the situation, but fixing it than failing): https://github.com/cschleiden/go-workflows/blob/main/internal/history/grouping.go, if the events come in as part of same execution, this might need more thoughts

I have what I believe is a fix for this issue at ☝
Let me know what you think when you have some time (no rush, though!). I'm happy to discuss/make corrections as needed! 😄


[FLINK-6044] Replace calls to InputStream#read(...) with the indended…

This PR fixes FLINK-6044. On top of that, I searched through the code for other calls to InputStream#read(...) that ignore their return value and replaced them with the intended InputStream#readFully(...) calls.

CC @uce @tillrohrmann

Thanks for your contribution @StefanRRichter. Changes look good to me. +1 for merging.

Thanks for the review @tillrohrmann. Merging this.


feat: filedef add new messages in Activity File

"I find that these messages are commonly present in FIT files produced by Garmin devices. Having these fields will benefit us in manipulating known messages, especially when handling Split Summary messages, as these messages must be unique within each split_type.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (3e5a59e) to head (04a8d0e).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #419   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         3612      3629   +17
=========================================
+ Hits          3612      3629   +17

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Help] Can not open https://weex.apache.org/zh/ webside

I can open https://weex.apache.org/
but can not open  https://weex.apache.org/zh/guide/introduction.html
It's showed ERR_TOO_MANY_REDIRECTS at 2019.06.20 22:00
Now it's showed ERR_CONNECTION_TIMED_OUT
Tried someone else's computer but not work.

Fixed now.
Thanks


cpp: Undefined references on mangled function names

Implemented functions are mangled, so the linker is not able to find them:

Mangled function name:

Yeah, that's how C++ works, not an splat issue
If you don't want the name to be mangled then you would need to use extern "C"

Yeah, that's how C++ works, not an splat issue
If you don't want the name to be mangled then you would need to use extern "C"

That's what I'm doing currently. But eventually, we will have to use C++ classes.

Ignoring the splat aspect of this for a sec, how is it supposed to look? Clearly you wouldn't be putting mangled names into source code, so something is missing

Then use them :man_shrugging:
This is likely to produce a domino effect in which most of your files will become C++ instead of C.
To get the C++ functions to see the undecomped asm functions you would probably need to mangle the asm functions yourself

So the issue is that our generated function name for the s files would need to be mangled? I think that's not an unreasonable thing for us to do (include the mangled name with a comment for the actual func name). The problem is having a symbol mangler that matches your exact compiler, which could be tricky. It's also a lot of stuff for splat to worry about (all possible compilers' symbol mangling algorithm)

symbol mangling depends on the signature of the function, so we would need to know ahead of time what types the function take and what it returns, which we can't figure out with just the assembly.
The only solution I can think of is the user doing it manually with a symbol_addrs file, which sounds tedious

The only solution I can think of is the user doing it manually with a symbol_addrs file, which sounds tedious

Perhaps a mangled_names file?

Ah yeah, that's a good point. I guess on some platforms, the mangled names are visible because you have an elf or something. But yeah... Definitely seems like a much later thing for us to work on if at all

How would a mangled_names file would work and look like?

Nevermind, lol. Yeah, doing it on the symbol_addrs file sounds fine.

In case you don't know what a symbol_addrs.txt file is, it is a file where you can list the symbols from your ROM, give them a name different than the autogenerated ones, add additional properties, etc. All this information will be used when generating the disassembly.
As an example of manually mangling the function from your error:
_GLOBAL_$F$func_8001D584__Fv = 0x8001D584;

And the disassembler will use that name to disassemble the function

Is there anything for us to do here, or can we close this as 'wont/cant fix' ?

Closing as wont/cant fix.


Switch index to parquet format

@fedorov Once https://github.com/ImagingDataCommons/idc-index-data/pull/17 is merged, and new pypi release is created,
I'll lock the data version in idc-index's pyproject.toml. This PR should then pass the tests.

We have a problem: https://github.com/ImagingDataCommons/idc-index-data/issues/18

For the background, we are switching to Parquet because it improves query performance, compresses better and organizes data column-wise as opposed to row-based organization in CSV. One article discussing this: https://blog.enterprisedna.co/pandas-read-parquet-file-into-dataframe/.


make external gitinfo match internal

GitInfo drifted between internal and external.  This brings the API into alignment with the actual API used.
/assign @bparees
I'll put together the fake bump and handling downstream.

/lgtm
thanks

/hold
for following process of carrying bumps.

downstream looks good
/hold cancel


[Docker Images] Images should be built and published by CI system

Today docker images that are used for build and testing are manually built and uploaded, this should be done automatically with a github action or a jenkins workflow.
Here is an example github action that we could use, https://github.com/marketplace/actions/build-and-push-docker-images.

I can do this as LINUX now support buildx for both x64 and arm64, the thing is we need to run on Ubuntu as it is the only known version for now to support binfmt-support qemu-user-static.

@peterzhuamazon putting this into the product backlog and we can circle back to it, we might want to create a separate repo or a proposal

We already start the automation in #801 so close this.

Lets close this when it is fully automated, documented and merged into main, it looks like the core changes are still in a fork


No inventory number

fixes #201

django.po needs fixing, can be merged afterwards

The conflicts were resolved, but there seems to be a problem with the docker tests.

Closed because there were to many problems, I'll just start a new branch from develop and copy the changes.


[Documentation] Add initial backend setup guide

Description
Prepare documentation for the initial backend setup.
Check out the  backend-setup branch, go through the entire codebase, and prepare well-descriptive documentation that will be used for the wiki page of the project.
It will be a unique experience as you get a chance for 1-1 interaction with the mentors. We would love to share our experiences and exchange knowledge with you.
This issue will call for several revisions and discussions. Please feel free to contact us via slack.
This issue can be assigned to multiple people

Can i work on this issue??

Can i work on this issue??

Sure, go ahead. Go through the code once and then we can discuss more on it

Sure, go ahead. Go through the code once and then we can discuss more on it

@jackfrost13 Yeah sure !!

@jackfrost13 Yeah sure !!

@jackfrost13 @Kajol-Kumari Please provide me with some backend documentation so that i get an idea how the documentation should be

@jackfrost13 @Kajol-Kumari Please provide me with some backend documentation so that i get an idea how the documentation should be

Surely, DM me on slack!

Surely, DM me on slack!

Have assigned you one of the requested issues, please complete that first

Sure @jackfrost13

@manishaag7 Please let us know on which module you are working?

I will tell you by tonight, sorry for the delay

Can I work on url shortener module, can you also provide some guide or example how to write backend documentation?
Thank you!

Why there is a need for this issue?
The backend setup guide is already available at Readme.

@Ashuto7h Yes the initial guide has been prepared but it doesn't contain all the documentation required.
This issue serves as an umbrella under which multiple issues(module specific is created)

I would like to work on this issue under GSSOC`22. If no one is working on it. @jackfrost13


consistent log config across commands

Pull Request Test Coverage Report for Build 890543598

33 of 37 (89.19%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 81.939%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/cli/update_runner.go
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/cli/update_runner.go
1
56.52%

Totals

Change from base Build 889882565:
-0.001%

Covered Lines:
989

Relevant Lines:
1207

💛  - Coveralls

Pull Request Test Coverage Report for Build 890543598
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

33 of 37 (89.19%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 81.939%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/cli/update_runner.go
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/cli/update_runner.go
1
56.52%

Totals

Change from base Build 889882565:
-0.001%

Covered Lines:
989

Relevant Lines:
1207

💛  - Coveralls

Pull Request Test Coverage Report for Build 890543598
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

33 of 37 (89.19%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 81.939%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/cli/update_runner.go
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/cli/update_runner.go
1
56.52%

Totals

Change from base Build 889882565:
-0.001%

Covered Lines:
989

Relevant Lines:
1207

💛  - Coveralls


Generating bindings for Cricket - missing headers

Hello,
I'm working on generating bindings in Go for Cricket, but I can't do anything without access to some headers that are listed in .gitignore - namely cpu_rpc_prot.h.
Out of curiosity why are these excluded? Also can I work around this by using cpu_rpc_prot.x? Not really sure what the .x file extension is or what the file itself is doing.
Thanks!

Just do make cpu_rpc_prot.h. This should generate the header from the .x file. You need rpcgen for that. Have you had a look at https://github.com/gavrie/oncrpc? I am sure there are other projects.

Ah got it, I'll take a look at oncrpc too. Thanks!
Out of curiosity, not sure if I'm doing anything wrong here:
nravichandra@ubuntu:/Users/nravichandra/go/src/github.com/nravic/cricket-go/cricket/cpu$ rpcgen -C cpu_rpc_prot.x
        ptr_result rpc_register_function(ptr, ptr, string, string, int) = 50;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cpu_rpc_prot.x, line 216: only one argument is allowed


Unable to pull Charts from Private Registry

What happened?
I'm trying to create a Helm Release using helm-provider, but I'm getting "Certificate Signed by Unknown authority even after adding "insecureSkipTLSVerify: true". Can some one help me how to fix the cert issue or how can I skip the TLS verification?
How can we reproduce it?
apiVersion: helm.crossplane.io/v1beta1
kind: Release
metadata:
  name: helm-testing
spec:
  forProvider:
    insecureSkipTLSVerify: true
    chart:
      pullSecretRef:
        name: helm-secret
        namespace: default
      name: <Chart Name>
      repository: oci://<Private Registry>
      version: 0.1.1
    namespace: default
    values:
      cluster_name: crossplane
  providerConfigRef:
    name: default

What environment did it happen in?
Crossplane version:  1.13.2
Include at least the version or commit of Crossplane you were running. Consider
also including your:

Cloud provider : AWS
Kubernetes version (use kubectl version): 1.25
Kubernetes distribution (e.g. Tectonic, GKE, OpenShift) EKS
OS (e.g. from /etc/os-release) amzn linux

In terms of the insecureSkipTLSVerify option, looks like support for that was added to helm v3.12.0, and we're currently on v3.10.2 in this repo. So perhaps upgrading our dependency would make insecureSkipTLSVerify start working 🤔
Are you interested in testing that out in your environment? 🙏
There may be further work to make end to end TLS work, but it's hard to tell what may be wrong there without setting up a specific repro environment that we have full control over - otherwise there's too many unknown variables in the environment for which this issue was opened in.

Thanks for looking into this @jbw976
So it looks like insecureSkipTLSVerify works with http based helm registry, but never worked when using oci:// registry
@sujith1594 which registry you are using, is it based on an open source and could you provide how is it setup?

Hi @csantanapr, We are using Redhat Quay which is built on top of Openshift Cluster. Quay is an OCI Registry

Hi @sujith1594,
which fiels are set in your secret?
I would like to pull from a private ECR registry but I can't find how the secret must be composed.
Thank you.
BR

I've got the same problem with Zot OCI registry:
forProvider:
  chart:
    name: scheduler
    pullSecretRef:
      name: ""
      namespace: ""
    repository: oci://zot.default.svc.cluster.local:5000/charts
    version: 0.1.0
  insecureSkipTLSVerify: true

The provider-helm Release returns this error:
Warning  CannotCreateExternalResource  1s (x6 over 10s)  managed/release.helm.crossplane.io  failed to install release: failed to pull chart: failed to do request: Head "https://zot.default.svc.cluster.local:5000/v2/charts/scheduler/manifests/0.1.0": tls: failed to verify certificate: x509: certificate signed by unknown authority
My certificate has the proper FQDN and SAN but was signed by a self-signed root CA. I'm going to try with the cluster CA.

Looks like helm added a --plain-http different than insecure skip tls verify for this kind of scenarios: https://github.com/helm/helm/pull/12128
We would need a corresponding spec in the API type and pass it to our helm clients here.
Contributions are welcome 🙏


Fixes:#886- Jashwanth/localrun_error

Issues Identification
Closes: #886
Description
there was path issue with loading of image and pages, i fixed it , for all.
Now i am sure that this will work in all the systems.
Summary
The issue with loading images and pages was due to incorrect file paths. After identifying and fixing the path discrepancies, all components are now correctly referenced. The solution ensures that the project will work seamlessly across different systems without path-related errors.
Types of Changes
Please check the boxes that apply

[x] Bugfix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes do not break the current system and pass all existing test cases
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Screenshots
before : localhost stage

after:
https://github.com/user-attachments/assets/f4675329-976b-4888-8b70-21c564a129a6
Additional Information
dont forget to add gssoc and hacktoberfest tag

check the deployment none of the pages work

but Your code wont work in mine system sir,


Better handling of void elements & child first links.

Ref: https://github.com/ben-eb/remark-word-wrap/issues/1
Ref: https://github.com/ben-eb/remark-word-wrap/issues/2
@wooorm Does this fix your issues? Can it be improved?

Fixed by https://github.com/ben-eb/remark-word-wrap/commit/0c53e60290a7bfbdfb04bca19f75ab66dbe85814


Power toys v0.41 Updates

@mattwojo please help us get this checked in by 6/28 EOD if possible.

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

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

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

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

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

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


Problem with :create command and custom types

Describe the bug
When using custom write type and read type to modify the data before inserting / after fetching data from the database, the create command passes original unmodified data to read type, sometimes causing exceptions.
To Reproduce
require 'bundler/inline'

gemfile do
  source 'https://rubygems.org'
  gem "json"
  gem "rom-sql"
  gem "sqlite3"
end

require 'rom'
require 'rom-repository'

rom = ROM.container(:sql, 'sqlite::memory') do |conf|
  conf.default.create_table(:test) do
    primary_key :id
    column :value, String, null: false
  end

  class TestRelation < ROM::Relation[:sql]
    WriteType = Dry.Types.Constructor(String) { |value| JSON.dump({content: value}) }
    ReadType = Dry.Types.Constructor(String) { |value| JSON.parse(value)["content"] }

    schema(:test, infer: true) do
      attribute :value, WriteType, read: ReadType
    end
  end

  conf.register_relation(TestRelation)
end

class TestRepo < ROM::Repository[:test]
  commands :create
end

record = TestRepo.new(rom).create(value: "test value")

This causes:
/home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/json/common.rb:216:in `parse': unexpected token at 'test value' (JSON::ParserError)
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/json/common.rb:216:in `parse'
	from rom_custom_type_problem.rb:21:in `block in <class:TestRelation>'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/constructor/function.rb:17:in `call'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/constructor.rb:81:in `call_unsafe'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/schema/key.rb:46:in `call_unsafe'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/schema.rb:330:in `block in resolve_unsafe'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/schema.rb:324:in `each'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/schema.rb:324:in `resolve_unsafe'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/schema.rb:60:in `call_unsafe'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/constructor.rb:81:in `call_unsafe'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/dry-types-1.7.1/lib/dry/types/type.rb:47:in `call'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-sql-3.6.1/lib/rom/sql/commands/create.rb:41:in `block in finalize'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-sql-3.6.1/lib/rom/sql/commands/create.rb:41:in `map'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-sql-3.6.1/lib/rom/sql/commands/create.rb:41:in `finalize'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-core-5.3.0/lib/rom/command.rb:479:in `block in apply_hooks'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-core-5.3.0/lib/rom/command.rb:474:in `each'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-core-5.3.0/lib/rom/command.rb:474:in `reduce'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-core-5.3.0/lib/rom/command.rb:474:in `apply_hooks'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-core-5.3.0/lib/rom/command.rb:289:in `call'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-sql-3.6.1/lib/rom/sql/commands/error_wrapper.rb:18:in `call'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-core-5.3.0/lib/rom/commands/composite.rb:19:in `call'
	from /home/katafrakt/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rom-repository-5.3.0/lib/rom/repository/class_interface.rb:130:in `block in define_command_method'
	from rom_custom_type_problem.rb:35:in `<main>'

The data is actually written correctly to the database, but it fails on trying to return the value. Stacktrace points to finalize hook of rom-sql:
        def finalize(tuples, *)
          tuples.map { |t| relation.output_schema[t] }
        end

This indeed tries to feed original data, unmodified by write type, to a read type.
Expected behavior
Creating a record using custom write and read type returns correct result.
My environment

Affects my production application: NO
Ruby version: 3.2.2
OS: Linux

Oh, I just realized that it works when I specify WriteType as write
# not: attribute :value, WriteType, read: ReadType
attribute :value, write: WriteType, read: ReadType

Not sure why I missed this before. It makes sense.

Actually, that was premature optimism. With write: is does not encode the value before putting it in the db, so naturally in this case it does not crash, but it also does not do what's desired - there's just a plain string "test value" in the database.

I did some more digging and found out that this problem is only present for SQlite and MySQL. Or, to be more precise, is not a problem in PostgreSQL. This lead me to discovery that it's because PostgreSQL has it's own implementation of insert for create command. The default insert implementation is broken and tries to apply read type twice - first when relation.where(...).to_a is called at the end of insert and after that in finalize hook. For PostgreSQL the insert does not use relation, so the type is onl applied during finalize.
I think that's enough for me to prepare a PR with a fix.


'.\filename' (dot-path local execution) requirement not required for files '.file'

Edit: Adding hints from the conversation
Steps to reproduce
First, insure you do not have the test subject file in your path:
.test.html # should produce a 'not recognized' error

If the above did not produce an error, change the command so that the file name still starts with a . but produces the said error, and change the below example accordingly.
If the above produced an error, then try the following:
@'
<!DOCTYPE html>

    <title>foo</title>

Hello

'@ > .test.html # generate a sample file

.test.html # invoke sample file

Expected behavior
I would expect an error saying '.test.html' is not recognized as … but does exist in the current location.
Actual behavior
The default browser will open the file.
It appears that the '.' that begins the file name is enough to satisfy the 'dot path' rule for executing files in the current working directory.   I did not expect this.
Environment data
PowerShell Core 6.2.0 on Windows 10 1809.  Also confirmed in Windows PowerShell 5.1, same OS.

You're not executing .test.html, you're applying the Windows shell's default verb to it - something that has always worked this way.
In other words: you're opening document .test.html  rather than invoking an executable.

But it doesn't work for 'test.html'  Instead I get an error saying not a command, but exists in the current location.
Opening a document is the same as invoking an executable in Windows, for all intents and purposes.

To be clear, if I have two files, '.test.html' and 'test.html',
.test.html # succeeds opening default browser
test.html # reports 'not recognized, but exists in the current location'
.\test.html # succeeds opening default browser

Good point - I'd  used *.txt in my tests, which PowerShell happily opens even without the .\ prefix.
I don't know what explains the difference (haven't looked at other extensions), but it's certainly an inconsistency, and from a security and predictability standpoint it makes sense to always require an explicit path reference to open/execute a file in the current location (tab completion assists with that by automatically prepending .\ / ./ for a file that exists in the current dir.)
Complementarily, it makes sense to only support locating executables via $env:Path (as defined via $env:PATHEXT), not also documents (i.e., files with names whose extensions aren't marked as executable).

I am not seeing the behavior of .txt' files acting any differently.  Without the .` prefix I get the same message, 'not recognized... but exists in the current location', unless the file name starts with a dot.

@msftrncs:
You are correct: My mistake was that  I had a t.txt located somewhere in $env:PATH, which is what actually was opened, not my current-directory-local copy.
So to summarize:

What your OP reports is indeed a bug: a filename starting with . bypasses the need to open/execute a file located in the current directory with a path (whether relative or absolute).

Separately, it is problematic that PowerShell allows opening even non-executable files by filename only, as long as they're located in $env:PATH.

I want to clarify that I tested deleting the .test.html file, and tried to run it, to validate that I did not have such a file on my PATH somewhere.  I wanted to make sure I wasn't making that mistake,

Understood, @msftrncs; re my 2nd point above: please see #9469.

Also, confirming that the same issue occurs with the use of dot-source . or the call & operators or the invoke-expression cmdlet and a string value, in a variable or quoted literal.
$a = '.test.html'
$b = 'test.html'
.$a # opens (not expected)
.$b # errors (as expected)
&$a # opens (not expected)
&$b # errors (as expected)
invoke-expression '.test.html' # opens (not expected)
invoke-expression 'test.html' # errors (as expected)

The fact that all invocation methods work the same would be expected.

As this is existing 5.1 behavior, this is considered an enhancement.  cc @iSazonov

@TravisEz13, does it change it any if my example of an HTML file was replaced with a script file .test.ps1.   The same behavior happens, (and protective feature bypassed) if the example was a script file.  Fixing this would seem to be a defense-in-depth condition.

@TravisEz13 It is not clear for me why it is "enhancement" if we see unexpected (and possibly dangerous) behavior. From my understanding "enhancement" is "add new useful functionality".

@iSazonov I think just meant that the request to fix this would be considered an enhancement of the existing behaviour, rather than a bug. Tricky wording.

I'm sorry.  I miss read the repro.  This is by design.  ./ or .\ is not required to execute a file.  Not all scenarios work, but we have explicit tests to verify that this scenario actually works.

I thought about this more. This is not a good design.  I remember arguing for changing it myself when fixing a recent Defense in Depth issue.


Argo Component improvements

Currently Argo component has too many dependencies which must be removed:

[x] OpenID connect configuration should be removed from the component
[x] Integration with the Postgres database should be removed
[x] VirtualService is an abstraction of Istio and also should be removed from the component

If Argo needs to integrate with the services mentioned above, it must be done using stack-level hooks.
Also, the following adjustments must be made:

[x] dns.domain property must be removed from the component manifest
[x] Ingress is deployed if ingress.hosts for Argo value is set on the stack
[x] For compatibility we should still keep --context=$HUB_DOMAIN_NAME on kubectl commands (it's set by hubctl extensions outside the component)
[x] Bumb version of Argo and Argo Helm Chart to the latest version
[x] Allow setting custom workflow executor: leave emissary as default

@akranga please review


When Unrelated Group PR Exists, All Dependencies Skipped for Group

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pnpm (applies to all)
Package manager version
pnpm=8.9.2
Language version
node=20
Manifest location and content before the Dependabot update
N/A
dependabot.yml content
version: 2
updates:
  - directory: /web
    commit-message:
      prefix: Web
    package-ecosystem: npm
    open-pull-requests-limit: 3
    schedule:
      interval: weekly
      day: monday
      time: '05:00'
      timezone: America/Toronto
    versioning-strategy: increase-if-necessary
    allow:
      - dependency-type: all
    groups:
      major:
        update-types: [major]
      minor:
        update-types: [minor, patch]

Updated dependency
N/A
What you expected to see, versus what you actually saw
Expected Behaviour
When running dependabot via
Each dependency to be checked for updates, and a new PR to be opened for any groups that don't already have a PR.
Actual Behaviour
After detecting an existing pull request:
Detected existing pull request for 'minor'.

And starting to work on the first group:
Starting update group for 'major'

Every dependency gets skipped with the same message:
Skipping <dependency> as it has already been handled by a previous group

And the run skips checking for any updates.
What's particularly interesting is that at this point the first group is being processed, there is no "previous group" yet.
It seems that, when an existing PR is detected, every dependency gets marked as "already processed" somehow.
This causes a "clean" run (where no PRs exist), to behave differently from a "subsequent" run (once one or more PRs have been opened); it is very confusing when dependabot runs successfully but new dependency versions are not detected.
Native package manager behavior
N/A
Images of the diff or a link to the PR, issue, or logs
full run logs
Smallest manifest that reproduces the issue
version: 2
updates:
  - directory: /web
    package-ecosystem: npm
    groups:
      major:
        update-types: [major]
      minor:
        update-types: [minor, patch]

All that's needed is to have an open group PR, and a secondary group for which we would expect a new PR to be opened.

We have the same issue - when I close all open PRs and rerun it usually work.


[Bug fix] bugs in LM_MA_ES

Hi, thanks for such a nice library.
I found a bug in LMMAES and will send a pullrequest.
Background
Recently I'm interested in LM-MA-ES and use both implementation in numpy and one in jax, this library has.
Here this is my first test code and unfortunately only evosax's LM_MA_ES sampled nan-valued solution vectors and its step-size grew to infinity after several generations;
from evosax.problems import BBOBFitness
from evosax.strategies import LM_MA_ES
import jax.numpy as jnp
import jax

#Initialization
seed = 0
rng = jax.random.PRNGKey(seed)
dim = 2000 # high dimension, but same bug occured in lower dimension too.
sphere = BBOBFitness("Sphere", num_dims=dim, seed_id=2)
default_lamnda_and_m = int(4+jnp.floor(3*jnp.log(dim)))
mean = 3
sigma = 2
max_evals = 3*10**5*default_lamnda_and_m
criterion = 10**-10
strategy = LM_MA_ES(popsize=default_lamnda_and_m,
                    num_dims=dim, memory_size=default_lamnda_and_m                    )
es_params = strategy.default_params.replace(init_min=mean, init_max=mean, sigma_init=sigma)
state = strategy.initialize(rng, es_params)

best = float('inf')
t = 0
while best > criterion:
    rng, rng_gen, rng_eval = jax.random.split(rng, 3)
    x, state = strategy.ask(rng_gen, state, es_params)
    if jnp.isnan(x).any():
        print("nan exist in x.")

    fitness = sphere.rollout(rng_eval, x)
    state = strategy.tell(x, fitness, state, es_params)
    best = min(best, fitness.min())
    if (t + 1) % 50 == 0:
        print(f"# Gen: {t+1}|Fitness: {best:.12f}")
    if jnp.isnan(fitness).any():
        print('nan exists in fitness.')
        break
    if jnp.isnan(state.mean).any():
        print('nan exists in mean.')
    if jnp.isinf(state.sigma):
        print('sigma is inf.')
    t += 1

print(f"Gens:{t},evals:{t*default_lamnda_and_m},lamb:{default_lamnda_and_m}")

So I started bug fixing and finally I did. I will send my pull requests.

Thank for the PR and work! I left some review comments. Could you have a look and tell me what you think?


updates bias_from_probabilities to set number_of_shots to zero

OK, abandoning this as our instructions say explicitly to set this to -1 if shots is not applicable to your task.


drivers: Rename renesas ra drivers

With current name nomenclature for Renesas RA driver, it's not possible to target them correctly in the MAINTAINER file.
Rename all drivers to be able to delimit Renesas areas correctly.
Blocking #67487

The Kconfig renames should be added to the migration guide/release notes.

I added notes to both release note and migration guide, please @henrikbrixandersen tell me if I did it well !
Thanks

Addressed @kartben request

Added "CONFIG" prefix to previous and new Kconfig options names in release note and migration guide


Sort "Recently Discovered VMs" by discovery date

The ems_created_on column is for the VM creation timestamp, and is not
included in all providers (and even worse nil is sorted to the top of
the list). The created_on column is for the discovery timestamp and
should be populated in every row.
fixes #21461

I think if we do created_on, then we should change the column title to say "Discovered On", because "Created On" is ambiguous.

i.e. change the header - Created on Time to - Discovered on

I think if we do created_on, then we should change the column title to say "Discovered On", because "Created On" is ambiguous.


Add support for virtual packages

I cannot test it though, because __glibc is not used in published packages yet. __osx is, but I don't have a Mac. The other one is __cuda and I don't have an Nvidia card!
@wolfv can you test it on a Mac?
More generally, I'm wondering if we should not set up an environment test, that would let us mock things like that.

cool! yes will try.
I have some data in the tests subdir but yes, we need to make this easier to use and add (lots of) tests :)

whoops the directory i was referring to has never been uploaded :)

I have added the test stuff I have locally here: https://github.com/wolfv/mamba/tree/add_test
I think for the moment we could use this and extend it to capture the virtual packages.

I'm going to see if I can add a test as part of this PR.

I have added the test stuff I have locally here: https://github.com/wolfv/mamba/tree/add_test

You mean you are going to add in upstream?

I have added the test stuff I have locally here: https://github.com/wolfv/mamba/tree/add_test

You mean you are going to add it upstream?

yeah, or something similar / better :)

Should I wait for that to test this PR?

ok I just quickly added the changes from my repo here. But feel free to change how testing is done, it was really ad-hoc what I did.

I could already see that my PR doesn't work. If you modify __glibc=2.30 with whatever version you have on your system, this doesn't work:
mamba create -n xxx --override-channels --strict-channel-priority --dry-run -c ./test/channel_b -c ./test/channel_a b

But it works fine with conda.

Maybe we need to mock the solver that the virtual packages can be provided?

It might not be your fault -- it could be that the constrains field actually doesn't yet work as intended.

ok no I just checked, I believe the syntax in the depends field is slightly wrong: it's got to be something like:
__glib ==2.4.0

let me try your PR locally :)

Same issue.

I think it works for me!
3 packages in file:///home/wolfv/Programs/mamba/test/channel_a/linux-64
0 packages in file:///home/wolfv/Programs/mamba/test/channel_a/noarch
1 packages in file:///home/wolfv/Programs/mamba/test/channel_b/linux-64
0 packages in file:///home/wolfv/Programs/mamba/test/channel_b/noarch
Encountered problems while solving.
Problem: nothing provides __glibc 2.30* needed by b-0.1.0-abc
:tada: !!
The problem was probably that the bz2 version of the repodata wasn't updated! Here is my modified script:
#!/bin/sh
rm -rf test/channel_a/**/repodata.json.bz2
rm -rf test/channel_b/**/repodata.json.bz2

tar -czvf test/channel_a/linux-64/repodata.json.bz2 test/channel_a/linux-64/repodata.json
tar -czvf test/channel_a/noarch/repodata.json.bz2 test/channel_b/noarch/repodata.json
tar -czvf test/channel_b/linux-64/repodata.json.bz2 test/channel_b/linux-64/repodata.json
tar -czvf test/channel_b/noarch/repodata.json.bz2 test/channel_b/noarch/repodata.json

conda create -n xxx --override-channels --strict-channel-priority --dry-run -c ./channel_b -c ./channel_a a
mamba create -n xxx --override-channels --strict-channel-priority --dry-run -c ./channel_b -c ./channel_a a
conda create -n xxx --override-channels --strict-channel-priority --dry-run -c ./channel_b -c ./channel_a b
mamba create -n xxx --override-channels --strict-channel-priority --dry-run -c ./channel_b -c ./channel_a b
conda create -n xxx --override-channels --strict-channel-priority --dry-run -c ./channel_a -c ./channel_b b
mamba create -n xxx --override-channels --strict-channel-priority --dry-run -c ./channel_a -c ./channel_b b

hm wait, it should actually work with __glibc >= 2.30 as that is what I have in my system :)

;-)

hmm. i tried moving the dependency to the constrains field but it also hasn't helped. I am going to check that the constrains stuff work tomorrow... I think this is definitely supposed to work.

one other possibility would also to make a "fake" virtual package channel and add the 2-3 virtual packages as "installable" packages there... that should definitely work.

With this last commit this works:
mamba create -n xxx --override-channels --strict-channel-priority --dry-run -c ./test/channel_b -c ./test/channel_a -c ./test/channel_fake b

But it is still going to install __glibc, although it is in the installed packages.

one other possibility would also to make a "fake" virtual package channel and add the 2-3 virtual packages as "installable" packages there... that should definitely work.

But the version of the virtual packages in this fake channel must match the local versions, or all the possible versions must be available in the fake channel... not great.

It works now, no need for a fake channel:
mamba create -n xxx --override-channels --strict-channel-priority --dry-run -c ./test/channel_b -c ./test/channel_a b

Nice improvements!


Increase or Decrease volume with volume bar

Added a bar and styling to handle the volume of the song for this #10
@samratghosh291 please check

@VivekChatterjee please attach an ss here.

Here is the view.
@samratghosh291  please add hacktoberfest-accepted label


Avoid JIT'd Perl in dracut to avoid SELinux errors

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Dracut uses -P when calling grep in one location. This requires executing JIT'd code out of memory which is blocked by SELinux. While not a fatal error it generates a large number of SELinux and audit reports. (see https://github.com/dracutdevs/dracut/issues/2323). Use a more basic call to grep and use awk to extract the result instead.
Change Log

Remove dracut call to grep PCRE and replace with an extra call to awk instead.

Does this affect the toolchain?

NO
Associated issues

https://github.com/dracutdevs/dracut/issues/2323

Test Methodology

Local build and testing via VM

Hello - dracut upstream here. Thank you for your contribution upstream and sorry for the slightly off-topic note. Noticed that Mariner is on dracut v55, which is now about 2 years old (latest is v59). Most Linux distros - including Photon OS is on v59. Is there anything we can help to update dracut for Mariner ? What would be the best process to go about it ?
Hey @LaszloGombos , happy to chat! For Mariner we try to limit big package updates to our major releases (we went to v55 ~ around Mariner-2.0).

Dracut is definitely on our todo list for the next release though, (alongside grabbing a newer systemd) since we are looking at supporting some new boot flows and features. I've made issue #5494 as a place to chat and track this. I'd be happy for any advice you have. We are certainly open to public contributions as well, if that is something you are interested in (although we don't have a branch for the next major release yet).