Remove auto labeling "ambient-type"= "workload"

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@howardjohn Not familiar with the ambient integration test
https://github.com/istio/istio/blob/4c1097808cd1972f541400ce240191ebb8ad2481/tests/integration/ambient/main_test.go#L201
Maybe need to remove some test as well

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_experimental-ambient
ab7e763b03d74de1207162de2c11442a76fe50d1
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_experimental-ambient
ab7e763b03d74de1207162de2c11442a76fe50d1
link
true
/test integ-ambient

integ-security-multicluster_istio_exp
ab7e763b03d74de1207162de2c11442a76fe50d1
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I was working on similar as part of https://github.com/istio/istio/issues/43254. will send a PR

https://github.com/istio/istio/pull/43313

Close in favor of that


Fix orphan instances

Right now the FromJSON and ToJSON instances are orphaned. They should be moved to the same file.

Added in the would-be v<IP_ADDRESS>


Editing to add community link & clarify meetings

Hi, @phillipgibson - how does this edit look? Changes welcome.
Signed-off-by: Bridget Kromhout<EMAIL_ADDRESS>

Looks great!

I'm wondering if we should add a community link on the main openservicemesh.io page that links out to all the community info like helm.sh has? People will only see the community call link if they choose to read the blog post.

I'm wondering if we should add a community link on the main openservicemesh.io page that links out to all the community info like helm.sh has?

@phillipgibson sounds good - perhaps we should open an issue for Ronan to add that to the site design?


TypeScript: Component typing

There should be an example of typing components - @typescript/eslint shows a warning with default configuration. Is there something inside Solid type definitions - if there is, excuse my ignorance...

More detail is always appreciated in issues. What warning are you seeing? What default configuration are you talking about? How did you create it? How do you reproduce the warning?
Component and JSX related typing is all here: https://github.com/ryansolid/dom-expressions/blob/master/packages/babel-plugin-jsx-dom-expressions/types/index.d.ts

Missing return type on function.
const Counter = () => {
  const [state, setState] = createState({ count: 0 }),
    timer = setInterval(() => setState({ count: state.count + 1 }), 1000);
  onCleanup(() => clearInterval(timer));

  return (
    <>

{state.count}

    </>
  );
};

Something that would by declared as FC or FunctionalComponent in React. Is there a substitute?

The return type must be assignable to JSX.Element, so you could just do const Counter = (): JSX.Element => {

This would work in the simplest cases, yes. How would I type a component that I want to reuse?
const StyledDiv: JSX.Element = () =>
Styled Div!
;

return (
    <>


Panic in go guru

Please answer these questions before submitting your issue. Thanks!

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Ran go guru via go-guru-describre in emacs.
What did you expect to see?
not a panic
What did you see instead?
a panic
https://gist.github.com/mlsteele/caa4e523c4dc0aa77588854bc4f9f74a#file-panic-log
(sorry about the numerous edits of this post, accidentally ctrl+enter'd early)

CC @alandonovan

This is a segfault in mallocgc, not a bug in guru itself.
Which revision of Go are you using exactly? go version says 1.7.3 but your filenames say 1.6.3, and the line numbers suggest a third revision.
Is it deterministic?

Wow that's unsettling. I installed Go via homebrew months ago, upgraded via homebrew some weeks, and recently upgraded to OSX Sierra.
From my shell it's consistently 1.7.3.
$ go version
go version go1.7.3 darwin/amd64
$ ls /usr/local/Cellar/go
1.6.3  1.7  1.7.3

I agree those filenames say 1.6.3. Not sure what to tell you. The panic seems to occur mostly on invalid identifiers. There may be a concurrent go install happening using the source files I'm guru-ing on also.

In case it helps I'm using this version of go-guru for emacs /Users/miles/.emacs.d/elpa/go-guru-20160715.854. emacs package src

I wouldn't be surprised if my guru executable was built with 1.6.3. Not sure how to tell. I suspect rebuilding it would make this issue go away, not sure if that's what you want.

Rebuilding guru with 1.7.3 would likely make this problem disappear.  However, it is a valid bug report against the Go 1.6.3. runtime's mallocgc function.

Alright well let me know if you'd like anything else for me, otherwise I'll rebuild my guru tomorrow.

However, it is a valid bug report against the Go 1.6.3. runtime's mallocgc function.

While true, 1.6.3 is no longer supported. I did dig into this a bit in case it was something that still affected 1.7 or master. Unfortunately, it's clearly memory corruption since something overwrote the global runtime.mheap_.lock field with a bad value. This means it's both very hard to debug (the traceback certainly isn't enough to debug it) and very hard to tell if we've fixed since 1.6.3 (and it's likely we have).
Given all of this, I think you should go ahead and rebuild guru and I'm going to close this issue. Obviously, if it continues to happen, we can reopen it. :)


StaleElementReferenceException from is_text_not_present

I just encountered this stack trace (version 0.7.5):
  File "/.../lib/python3.6/site-packages/splinter/driver/webdriver/__init__.py", line 319, in is_text_not_present
    self.driver.find_element_by_tag_name('body').text.index(text)
  File "/.../lib/python3.6/site-packages/selenium/webdriver/remote/webelement.py", line 73, in text
    return self._execute(Command.GET_ELEMENT_TEXT)['value']
  File "/.../lib/python3.6/site-packages/selenium/webdriver/remote/webelement.py", line 491, in _execute
    return self._parent.execute(command, params)
  File "/.../lib/python3.6/site-packages/selenium/webdriver/remote/webdriver.py", line 238, in execute
    self.error_handler.check_response(response)
  File "/.../lib/python3.6/site-packages/selenium/webdriver/remote/errorhandler.py", line 193, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: element is not attached to the page document
  (Session info: chrome=57.0.2987.133)
  (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cfd9),platform=Mac OS X 10.11.6 x86_64)

It seems that the body went away after the call to find_element_by_tag_name('body') but before text could be accessed from the result. The possibility of this makes sense to me based on the application that I'm testing.
I think the solution is to handle StaleElementReferenceException the same way as NoSuchElementException.

I agree. The StaleElementReferenceException should be handled

In the meantime, is a workaround available?


Need help

Hey guys,
its pretty complicated if you ask me. Is there no video tutorial i can follow to get this setup?

I agree it is complex, but if you read through it a few times you'll get the hang of it. You may miss steps like adding the Sharepoint URLs, making the correct connections, creating the power apps and flows with the service account etc.

@OxygenGS we don't have a video tutorial I'm afraid, I will pop this on the roadmap, if you run into issues with the documentation then feel free to raise another issue and we can get the documentation updated. Thanks


Add support for RxSwift 4.4 & Swift 4.2

I've just created branch supports RxSwift 4.4 and Swift 4.2
pod 'RxBiBinding', :git => 'https://github.com/dialogs/RxBiBinding.git', :tag => '0.2.3-rxswift4'

@d2vydov
Hi, this is not a good idea to downgrade. Because it will be difficult to support normal branch and legacy. This is my opinion


Design and implement FAQ Page.

References :

Flowbite-react
Figma Cummunity
React icons
Tailwind CSS

#19


metadata permission

这个 PR 实现什么功能/修复什么问题:
修复设置metadata权限问题
是否需要 backport 到之前的 release 分支:

release/2.11.0
release/2.10.0
release/2.9.0
release/2.8.0

/area region
/cc @swordqiu @yousong

Codecov Report

Merging #1626 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1626      +/-   ##
=========================================
+ Coverage    7.67%   7.68%   +<.01%
=========================================
  Files         411     411
  Lines       63033   63028       -5
=========================================
+ Hits         4839    4842       +3
+ Misses      57785   57778       -7
+ Partials      409     408       -1

Flag
Coverage Δ

#aFlag
7.68% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/metadata.go
11.86% <ø> (+0.09%)
:arrow_up:

pkg/cloudcommon/db/standalone.go
0.93% <0%> (+0.01%)
:arrow_up:

pkg/util/rbacutils/rbac.go
74.76% <0%> (+0.93%)
:arrow_up:

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 0f0a090...69aab12. Read the comment docs.

/lgtm
/approve


CultureSelector should call JS interop asynchronously

Description
Although the first demo is "client-side only" (WASM), I believe the CultureSelector.razor versions in the article (definitely at least the BWA version) should use JS interop asynchronously. This means JavaScript should not be called from the set_Culture property setter, but from an asynchronous event handler, such as @bind-Culture:after or bind-Culture:set.
For consistency, all CultureSelector components should be refactored to remove any logic from set_Culture and instead utilize a separate event handler.
If you agree, I will prepare a PR for this.
cc @guardrex
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/globalization-localization.md
Document ID
d6f07538-228e-9f96-680f-6c324caf11d6
Article author
@guardrex

Sure thing! 👍
Given that the new binding became available at 7.0, you'll need to retain the current approach for <7.0. Fortunately, these code examples are in the article's text. Also, I think your suggested changes will require little or no text updates. I think you'll just need to manage the versioning as you're dropping in new code.
Side Note: There's an on-going internal discussion about the BWA approach here. You see that it basically extends the use of local storage from the standalone WASM (client-side only) approach. However, Hisham prefers dropping local storage on the client in a BWA in favor of hacking the loc cookie. I felt that the hacked-cookie approach is kind'a nasty 🤮 ... the JS that parses the cookie manually. However, Dan will have someone, Javier probably, look at the approaches and see which one will be the best. I don't think it has any bearing on what you plan to do here for this issue. I just mention it in passing as you work on the approaches.


Remove paramiko due to licensing conflicts

LGTM

Codecov Report

Merging #8 into master will decrease coverage by 1.49%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master       #8     +/-   ##
=========================================
- Coverage   82.07%   80.57%   -1.5%
=========================================
  Files          24       25      +1
  Lines         753      767     +14
=========================================
  Hits          618      618
- Misses        135      149     +14

Impacted Files
Coverage Δ

chaosmonkey/cm/cm.py
0% <0%> (ø)
:arrow_up:

chaosmonkey/dal/cme_sqlalchemy_store.py
87.23% <0%> (ø)
:arrow_up:

chaosmonkey/cm/profiling.py
0% <0%> (ø)

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 d826612...c5e0fac. Read the comment docs.


No war file created for eureka 2 server

The wiki says that I should have a eureka server war after the build.
The directory eureka/eureka2-server/build/libs only contains this though:
eureka2-server-2.0.0-SNAPSHOT.jar  eureka2-server-2.0.0-SNAPSHOT-javadoc.jar  eureka2-server-2.0.0-SNAPSHOT-sources.jar
I build using
./gradlew build
Is this a bug or is the documentation just not up to date?

Hi @cschneider eureka2 is not a jersey base application, so there is no war file generated. Having said this, the current stable eureka is the build on the master branch, which is the 1.x system. The 2.x system is currently not complete. Thanks.

I know 2.x is not yet released. We are currently evaluating registries and eureka 2 sounds quite good from the API perspective.
Does it make sense to already look into eureka2? Our product is going to go into production end of this year. Do you think eureka2 will be out until then?
If yes how do I start the server? I do not have the requirement for it to be a war.


Symbol has a "description" argument, not "name"

http://www.ecma-international.org/ecma-262/6.0/#sec-symbol-description

Thanks.


Title: Transpose of 3X3 Matrix Calculator

Is your feature request related to a problem? Please describe.
I want to add Transpose of 3X3 Matrix Calculator as a project to be made during the 30 days of the JavaScript challenge.
Describe the solution you'd like.
This Calculator calculates the transpose of a given 3X3 matrix in very few seconds. This is built with- HTML,CSS and JavaScript. It is responsive and supports all devices.
I am GSSOC 2022 Contributor. Please assign me this issue.
Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.

@ShruthiKartik Good Luck 👍🏻


Fix height reference handling in ModelExperimental

This PR fixes two bugs with height reference in ModelExperimental:

the update height callback was setting model._heightChanged instead of model._heightDirty
ModelVisualizer.getBoundingSphere was not waiting for _clampedModelMatrix to be defined for ModelExperimentals with height references

This doesn't change the incorrect camera behavior in #10555, but it at least makes it consistent with Model. Sandcastle for testing, with the expected behavior:

Click FlyToModel and it will be incorrect. Click it a second time, and it will be differently incorrect. Click it a third time and it is correct. There is clearly a race condition going on involved with clamping to ground.

Sometimes (even for Model) the camera ends up slightly above the model instead of where it accurately is, but it ultimately ends up above ground with part of the model in view.

Thanks for the pull request @j9liu!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Changes look good, I can confirm that the behavior is consistent with Model. Thanks @j9liu!


Remove S3 model hack and use customization instead for Size

https://github.com/awslabs/smithy-rs/pull/679 added a hack to sync-models.py to correct S3's Size to be a long instead of an int since it wasn't possible to do it with Smithy's ModelTransformer at the time.
This issue tracks removing this hack and enabling S3CorrectSizeIntegerType customization once https://github.com/awslabs/smithy/pull/900 lands.
Touch points:

https://github.com/awslabs/smithy-rs/blob/8676d8dcf79ac187a77dbd9b2b355b00ee0171fd/aws/sdk/sync-models.py#L49-L50
https://github.com/awslabs/smithy-rs/blob/8676d8dcf79ac187a77dbd9b2b355b00ee0171fd/aws/sdk-codegen/src/main/kotlin/software/amazon/smithy/rustsdk/customize/s3/S3Decorator.kt#L62-L65
https://github.com/awslabs/smithy-rs/blob/8676d8dcf79ac187a77dbd9b2b355b00ee0171fd/aws/sdk-codegen/src/test/kotlin/software/amazon/smithy/rustsdk/customize/s3/S3DecoratorTest.kt#L18-L20

fixed a while ago


Need a simpler example

the example demo is wayyyy too complicated. 90% of people don't need that level of command line complexity. provide several examples each of varying simplicity.

I totally concur. Well, such mind-twisting example is just defeating the whole point of using this library in the first place. It is  rather easier to deal with low-level parsing of command line myself.

I am very confused with new version. I need to see a simple argument parsing demo

@g2david  @sampomike
https://github.com/commandlineparser/commandline/pull/274
this might help. i have not verified it because i stopped using this library due to tons of issues when using it within mono

I like this approach. See if you feel that this is easier to understand:
        // Commandline options
        internal class CmdOptions
        {
            [Option('f', "file", Required = true, HelpText = "Database file to open")]
            public string DBFile { get; set; }

            [Option("driveletter", Default = @"X:\", HelpText = "Driveletter to use")]
            public string DriveLetter { get; set; }
        }

        //Entrypoint
        static void Main(string[] args)
        {
            var cmdOptions = Parser.Default.ParseArguments<CmdOptions>(args);
            cmdOptions.WithParsed(
                options => {
                    Main(options);
                });

        }

        //Overloaded main, called with CmdOptions from main(string[])
        static void Main(CmdOptions options)
        {
            Console.WriteLine($"Database file used {options.DBFile}");
            string dbFile = options.DBFile;

            Console.WriteLine($"Mounting to drive {options.DriveLetter}");
            string driveLetter = options.DriveLetter;
         }

If I wanted to write Scala (or any other functional language), I would do so.

@Rainmaker52
Pardon the month+ necro, but I actually just finished struggling through the documentation by rubber-ducking it with someone in a .NET chatroom, and I definitely like the format of your approach. I'd love to help/be kept in the loop about updating the documentation.

@Rainmaker52 I second this. The only thing is that if main returns an int this setup dosen't work. I used this for mine.
CmdOptions opts;
Parser.Default.ParseArguments<Options>(args).WithParsed(options => { opts = options; });

@Rainmaker52 's example is exactly what the doctor ordered.

It would be ideal to also include the actual command line that is being sent to the application.
I've been scratching my head trying to figure out why the most basic of items won't work, and I can't find a 'super duper happy path' example that actually shows me the proper input string so that I can use it in a unit test.


Fixed a slew of bugs related to templates and variables...

Talked to Ryan and it seems like this work is not going to be continued but I'll submit the PR anyway.

Ping could you please "Waiting for CLA signature by @nvalentine-puppetlabs"

Puppet Labs employee and have previously signed. It won't allow me to sign again.

can you squash your commits please and we can merge it.

Thanks for the work you have put in to this pull request. However due to inactivity and needed the commits squashed. This pull request is being closed. If you want to re-submit this pr with the necessary changes, we will look at the new pull request.


Update Redis Docker File

The dir for the conf seems to be missing from the base image, so the copy fails
Also if the server does not start with the conf as parameter it will not pick it up. Which leaves Redis wide open to attack by default:
Example try to telnet to your ip on the redis port for this container:
telnet <IP_ADDRESS> 6379
echo "Hey no AUTH required!"

For people who see this later, also do this yourself, as people or bots can telnet in and install ssh keys and the like from redis in very few lines of normal commands.
Explainer post:
http://antirez.com/news/96
Copy in the latest conf
http://download.redis.io/redis-stable/redis.conf
Edit the "requirepass" and "bind" lines, the pass needs to be complex, as redis can try so many passwords a second its ridiculous. The bind I found worked on a Digital Ocean server was to <IP_ADDRESS> rather than <IP_ADDRESS> or the main IP.
bind <IP_ADDRESS>
requirepass something-very-long-and-complex-pass123@

Should this security measure not be enabled by default?


Suggested addition Tours

Thanks for a fantastic list of resources!
I just released an ambitious project LiveTourLab, built on React VR. It makes VR tours easy to create, and there is nothing quite like it today.
I think Tours will grow to a fairly big category, given the initial popularity of proprietary systems like Matterport even though they are both proprietary and lack most of the functionality we just launched.
With that in mind, I suppose a fitting place would be a subcategory Tours under Software, like the below. Also I will be adding a more diverse set of contributors to the project, let me know if any of you are interested.
Software
...
Tours

LiveTourLab - Framework for creating VR Tours.

Thank you!
Please, make a pull request ;-)

Thank you! Done the PR.
And congrats again for a great repo. I have come back to it many times and found it very useful! Cheers


CouchDB failing to replicate behind a proxy server

Expected Behavior
When replicating from a remote CouchDB database to a CouchDB database on the local PC via a proxy, replication should be successful.
Current Behavior
CouchDB is seeing localhost / <IP_ADDRESS> as an HTTP-based target and assuming it needs to use the proxy, this causes replication to fail with CouchDB reporting an 'invalid_json' error due to the request via the proxy returning an error HTML page.
Possible Solution
A possible quick solution would be to add a check for localhost URLs and not use the proxy for those. Alternatively, it may be useful to add a sourceProxy and targetProxy, leaving the current proxy setting to behave as is. So the logic for getting the source poxy in the code would be to look at sourceProxy first, then the current proxy setting. Similarly for the target. The benefit of this alternate approach would be that you can proxy localhost if you need to (e.g. for local development using Fiddler).
Steps to Reproduce (for bugs)
This can be easily reproduced by using a replication document similar to the one provided below in the /_replicator/ database.
{
  "_id": "rep_init",
  "_rev": "20-81f3b1999b7f8e9ac51a45e3acbc4432",
  "source"<EMAIL_ADDRESS>  "target": "http://<IP_ADDRESS>:5984/<target_db_name>",
  "create_target": false,
  "continuous": false,
  "filter": "replication_filter/no_ddocs",
  "owner": null,
  "proxy": "http://<proxy_ip_address>:<proxy_port>",
  "_replication_state": "error",
  "_replication_state_time": "2017-12-07T15:59:12+08:00",
  "_replication_state_reason": "{invalid_json,{error,{1,invalid_json}}}",
  "_replication_id": "d449aac07eeb8da0e322d4646e0b0f9a"
}

Context
For further context please refer to the following
Your Environment

Version used: 2.0.0 (also reproducible in CouchDb 2.1.1)
Operating System and version (Desktop): Windows 10

Hi,
I noticed it's been four months since this issue was raised and I was wondering if there has been any progress? Any information is most appreciated.
Thanks.

@jkroon-immt We’re a volunteer driven project and so far nobody has volunteered to pick this up. PRs are always welcome.


Embed nice GraphViz graph drawings for scipy.sparse.csgraph?

For the scipy.sparse.csgraph page, it could be nice to use pretty drawings of the graphs instead of ASCII drawings.
First solution: sphinx.ext.graphviz
The sphinx.ext.graphviz extension was written for this very purpose.
(Here is an example of a Sphinx page that uses this extension.)
If we can be sure that adding the extension to conf.py will not break anything, I will write these two graphs on scipy/sparse/csgraph/__init__.py in the dot format and propose a PR.
Second solution: simply embed the SVG files
So graphviz does not become a requirement for building the docs.
I can generate the two SVG files and include them on the rST file.

https://github.com/scipy/scipy/pull/5345


Exporting the full model

I am trying to export the full model for further usage. Present code just saves the checkpoints weights and not full model. so it is difficult to use the model. model.save() method could export the model but while loading it, i am facing unknonw layers and functions issue.

Model.saved_model.save() solved the problem


Get rid of EpochInfo in TPraosParams

EpochInfo can be constructed from the hard fork history, and we can take a snapshot, but there isn't a single EpochInfo that remains static.
Related to #2030.

Depends on #2086

This is no longer required, we now have support for PartialConsensusConfig in #2034.


[$250] [HOLD for payment 2024-12-16] Incorrect default feed name in feed selector

Coming from here, when you first add a card feed, the default feed name is %Bank% cards. You can then edit this name to be whatever you want. The default feed name should appear consistently everywhere (the feed itself, feed settings, feed selector, etc.) It currently does not appear correctly on the feed selector.

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021866248038611712453
Upwork Job ID:<PHONE_NUMBER>611712453
Last Price Increase: 2024-12-09

Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.

Small PR has been opened for the review: https://github.com/Expensify/App/pull/53536

TY!

Oh wait, just checking - @allgandalf will you be paid for this job specifically, or are you bundling this job into a larger payment?

We will bundle the payments

Ok cool, i shall close the Upworks job then - thanks Vit

LMK if anyone needs a payment summary. Upworks job is closed now.

@allgandalf Can you add the checklist and then we can close

No payment needed

Thanks @allgandalf!


Any thoughts on plans for supporting procs for asset prefix?

We attempted to fork and add this functionality. We got the specs passing, but in our Sprockets precompile, Sass was not liking our fix.
Take a look at our fork, but it's not worth merging in just yet.
https://github.com/outright/sprockets-helpers

I hadn't thought of it, but sounds useful. After looking at your fork, I'm not really sure what the problem is though. Can you tell me more about your precompile setup? Are you using sinatra-asset-pipeline?

No. We're wedging Sprockets 2 into a Rails 2 app. Which means we're recreating the Rails 3.1 asset pipeline as closely as possible.
We'd hacked Sasset (https://github.com/CapnKernul/sasset) to support the 'Pipeline. But it's not enough in development - while sprockets-sass worked great in dev, but we needed this fix for production. Sass puked all over itself on render, likely because calls are happening out of order. But we gave up trying to understand all of Sprockets' guts.
Our fix right now is to use our fork of Sasset in production (really, just the precompile step), but to gem 'sprockets-sass' in dev. We're not explicitly using sprockets-helpers.

Yeah I think so. I'm not really sure how to help. Would it be possible to build a minimal version of your setup that I can use to test?

Just to chime in, this would help me out a ton as well.

I went and ahead and implemented this. Thanks for the help & input. Please try v0.3.0.


Automate release process in Jenkins

Overview

Automate release process in Jenkins, ensure that GPG signing works so the release doesn't fail.

This can be closed now

This can be closed now


Failed to download the framework of Carthage on Swift 4.2.

*** Checking out ReactorKit at "1.2.0"
*** No cache found for ReactorKit, building with all downstream dependencies
*** xcodebuild output can be found in /var/folders/l3/ggj8jv5s69n9fp29726kl9j40000gn/T/carthage-xcodebuild.KMgSlQ.log
*** Downloading ReactorKit.framework binary at "1.2.0"
*** Skipped installing ReactorKit.framework binary due to the error:
	"Incompatible Swift version - framework was built with 4.1 (swiftlang-902.0.48 clang-9<IP_ADDRESS>) and the local version is 4.2 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)."
*** Skipped building ReactorKit due to the error:
Dependency "ReactorKit" has no shared framework schemes

If you believe this to be an error, please file an issue with the maintainers at https://github.com/ReactorKit/ReactorKit/issues/new

The framework at Release is not build on Swift 4.2.
Please rebuild and upload ReactorKit framework.

Carthage/Build/iOS/ReactorKit.framework/Headers/ReactorKit-Swift.h:
// Generated by Apple Swift version 4.1 (swiftlang-902.0.48 clang-9<IP_ADDRESS>)
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wgcc-compat"

...

Thanks.

Also, I forgot to mention, for your CI, the error code from carthage update will likely fail your build, but I think that redirecting its output to dev/null would work: carthage update 2>/dev/null


Add documentation for the new --subscription argument.

MERGE ON 6/19

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/manage-azure-subscriptions-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

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.


Fix rabbitmq config decryption

Description of changes
rabbitmq-server: Use openssl_1_1 to fix config decryption
Fixes #192499, nixosTests.rabbitmq
Reverts the effect of the openssl upgrade introduced in 0565276a075531b6dad21171de459473dd5e6a27 https://github.com/NixOS/nixpkgs/pull/150093
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Does RabbitMQ not (yet) support OpenSSL 3.0? Would be nice if we can switch there eventually.

The RabbitMQ docs aren't explicit about the openssl dependency, but their Docker stuff is, and it's all OpenSSL 1.1. I agree.


i18n: TEA Wormhole start configuration message for Japanese

Overview
This is a small Japanese translation update for The Epic of Alexander trigger settings.
This change is necessary to inform users that the actual mechanic handling (e.g., positioning, movement) and initial setup differ from the popular method used in Japan.

Other languages specify that this is a cactbot-specific strat, and the previous ja translation included this I believe. Is there a reasonable way to keep this information in the new translation?

@valarnin

Other languages specify that this is a cactbot-specific strat, and the previous ja translation included this I believe. Is there a reasonable way to keep this information in the new translation?

Thank you for your feedback. The previous Japanese translation for this line was:
ja: '絶アレキサンダー討滅戦：cactbot「次元断絶のマーチ」ギミック', // FIXME

Unlike other languages, the Japanese translation did not include a reference URL to the specific cactbot strategy, which made it unclear what to do.
This change aims to address the //FIXME comment and align the Japanese translation with other languages by clarifying that this is a cactbot-specific strategy.
I believe this change is necessary for accuracy and consistency.
If you have any further suggestions or concerns, please let me know.


Electrical fan speed mode create

Hi i want to control the speed of a electrical fan, but I don't sees any mode related to it so ask here may I have one custom mode and its settings?
By the way, I want to speed mode has three settings, fast , medium, slow respectively
Thank you very much

Mode "fan speed" already exists.
value: "fan speed", "speed"
Setting "medium" exists.
I'll add in fast and slow.

Thank You.
Does it means I can use it now?

I'll update the thread when the new grammars are rolled out.

Hi Mr. Fleker
After I applied those values you mentioned above,
the Google Home just replayed me with "That mode is not available for my fan"
Do you know what's going on?

We've added the FanSpeed trait for smart fans.


Perhaps ellipsize test case names with tooltip

First off, thanks for this nice extension.
The PHP plugin shows the entire FQCN of the test case class, which makes items in the tree very long. This in turn makes it hard to reach the button to navigate to the source - which I didn't even know existed and I wanted to report an issue about it, until I discovered #69.
An example to demonstrate how long the test names are:

Would it be possible to ellipsize long test names (and e.g. show the full name in a tooltip on hover), or ellipsize the first part of the name (as the last part is usually the most important)? The idea is that there would be no horizontal scrollbar and the action buttons would always be visible on hover to the right. This would be similar to what the Tree Style Tabs extension does in Firefox:

Thanks!

Long test names are already being ellipsized, there is no horizontal scrollbar, the action buttons are visible and the full test name appears on hover:

All of this is actually standard VS Code behavior for contributed tree views.
The only thing that is missing here is the ability to ellipsize the first part of the name. This could only be done statically (i.e. the first part would always be cut off, even if you increase the width of the side bar) because VS Code doesn't offer any APIs for influencing how it ellipsizes the texts in a tree view. If this is desired, it should be done by the test adapter, it can specify the full name for the tooltip here.

Thanks for the response. I've created an issue in the adapter repository here: https://github.com/recca0120/vscode-phpunit/issues/47.


az deployment mg create command does not support Complete deployment mode

Describe the bug
From the following doc, az deployment mg create should support [--mode {Complete, Incremental}].
https://learn.microsoft.com/en-us/cli/azure/deployment/mg?view=azure-cli-latest#az-deployment-mg-create
But I tested it from my side, the error message mentioned the deployment mode "complete" is not supported for the management group scope.

Related command
az deployment mg create --location WestUS --management-group-id xxx --name xxx --template-file "xxx"
Errors
{"code": "InvalidDeployment", "message" : "Specified deployment mode 'Complete' is not supported for deployment at the current scope. Please see https://aka.ms/deployment-modes for usage details."}
Issue script & Debug output
az deployment mg create --location WestUS --management-group-id xxx --name xxx --template-file "xxx"
Expected behavior
The deployment should be handled with Complete mode.
Environment Summary
azure-cli 2.50.0
Additional context
No response

Thank you for opening this issue, we will look into it.

Since this error message was returned by the REST service, it needs the ARM service team to see if the REST supports Complete  mode. Please note that the relevant documentation doc link states that it is supported.

Thanks for your reply.
May I know is it possible to transfer/merge this GitHub issue to the GitHub page managed by ARM team?

Since this error message was returned by the REST service, it needs the ARM service team to see if the REST supports Complete  mode. Please note that the relevant documentation doc link states that it is supported.

Complete mode is not a valid mode for non-RG scoped deployments. Is "Complete" a current valid enum for this property?

@alex-frankel
Hi Alex, may I know will you help to raise any work item to update the REST API doc with the correct swagger spec?

https://msazure.visualstudio.com/One/_workitems/edit/24640447
Does this work item need to be finished in order to resolve this CLI issue? I don't believe these CLI commands are auto-generated. If that is the case, someone will need to create the PR on the CLI side, is that right?

@zhoxing-ms since the root cause of this is a swagger inaccuracy, please could you move this to https://github.com/Azure/azure-rest-api-specs?

since the root cause of this is a swagger inaccuracy, please could you move this to https://github.com/Azure/azure-rest-api-specs?

@anthony-c-martin Sorry, our team is not responsible for this repo, so we do not have permission to transfer it. Could you please directly create a new issue on that repo and copy the content over?


API not up to date

please add a way to update BattleBitAPIRunner :)

See PR https://github.com/BattleBit-Community-Servers/BattleBitAPIRunner/pull/8, if it is merged, you can use the official docker image from https://github.com/BattleBit-Community-Servers/BattleBitAPIRunner.
Otherwise, you need to use my fork ghcr.io/jackblk/battlebit-api-runner:latest. If you're already using my docker compose file, do docker compose pull then start the compose again.
Judging by the status of the BattleBitAPIRunner, looks like there won't be further update so I just synced the fork, it should be up to date now.


Set working directory when calling pico8 -run

Hello and thanks for this package!
My projects are in sub-sub-directories of the pico-8 carts location, or in other directories entirely.
I usually run !pico8 -run % which works as pico-8 interprets the relative path correctly (I have autochangedir note), it does not try to load the filename from its carts directory.  With :Pico8Run I get loading errors.
I think the current working directory should be set for the pico-8 process, or the absolute file path should be passed.

Thank you for your report!
I could not reproduce the problem on my Windows environment, but it seems better to pass the absolute file path.
Please update the plugin and check if your problem has been resolved.

Thanks for the quick reply!
I updated and still have a loading error with the absolute path.  I will try to find more info!

I ran with strace and found that this path is tried:
openat(AT_FDCWD, "/home/user/working/dir/'/home/user/working/dir/cart.p8'", O_RDONLY) = -1 ENOENT

So pico8 is already aware of the working directory, but passing a full path leads to bad concatenation.
I am reverting the change you did to see the original issue.

The original issue was a bad path too: "/home/user'/home/user/working/dir/cart.p8'"
Feels that pico-8 wants an unexpanded, unquoted relative path!

This change works for me with the autochdir option active, but not without!
diff --git a/autoload/pico8.vim b/autoload/pico8.vim
index a4ff0ae..c869a58 100644
--- a/autoload/pico8.vim
+++ b/autoload/pico8.vim
@@ -14,7 +14,7 @@ endfunction

 function! pico8#run(mods, options) abort
-  let cmdline = '"' . pico8#get_config('pico8_path', 'pico8') . '" -run ' . expand('%:p:S')
+  let cmdline = '"' . pico8#get_config('pico8_path', 'pico8') . ' "-run ' . expand('%')
   if has('win32')
     " PICO-8 on Windows does not output logs if run directly.
     let cmdline = $ComSpec . ' /C "' . cmdline . '"'
``


Expose setter for titleBarHeight

Expose setter for titleBarHeight so we can have thick title bars like Chrome

You can place a MoveWindow widget inside any widget you want to use for moving the window.
For the title bar can use a SizedBox widget with a child MoveWindow widget inside like this:
        SizedBox(
          height: 40, // set your title bar height here
          child: MoveWindow(
            child: Container(
              color: Colors.yellow[700], // set your title bar color here
              child: .. // put anything inside this Container
            ), // Container
          ), // MoveWindow
        ), // SizedBox


[UI Improvement] Months separated on "cells" & custom design

Not an issue per se. Rather a mere improvement on this library to support the below design.

On the above image, we can clearly see that each month is separated in its own "cell" with rounded corners and a drop shadow. I achieved the above by using a UICollectionView and UICollectionViewCell. Each cell includes an instance of a JTAppleCalendar with a custom configuration in order to only show one month.
It would be great if JTAppleCalendar could provide such ability instead of having to create a custom one like I did.

Alright. I'll get to work on a prototype to accomplish this.
will get back to you in some time

@patchthecode For the sake of simplicity I created a stripped down version of my implementation. You Can find the repository here — https://github.com/dimmdesign/CustomCalendar

@dimmdesign awesome. checking it out now.

made good progress on this. Expect a massive update in version 7.0.0
Code is ready. Just doing final tests.

Issue resolved on version 7.0
Releasing Beta version this weekend.


chore(main): release faro-shop 0.7.1

:robot: I have created a release beep boop
0.7.1 (2024-06-23)
Bug Fixes

do not declare faro_namespace doubly (#418) (22636f6)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

faro-shop-0.7.1
:sunflower:


chore: update sleep.ts example

Motivation
The jsdoc @example snippet is probably leftover from v2 since it's using yield instead of yield*. Same goes for the scope and streams and subscriptions (for subscription.next()) docs.

My pleasure! Awesome library - really appreciate all your thoughts (posts) around structured concurrency.
ps. Had to push again as I hadn't been signing my commits

The fixes for the guides are live. The type docs are versioned with the release of the code, and so will appear with the next release. Again, thanks!


Scale MySQL depending on the scale of the cluster

mysql-k8s-operator needs to be scaled depending on the number of
connections services need.
MySQL takes two config options:

profile-limit-memory: how much memory to configure MySQL with
experimental-max-connections: how many max connections to configure

If experimental-max-connections is set, the needed memory will be taken
from the profile-limit-memory. What remains will be used to configure
the respecting buffers.

Force push is a rebase on main

Force push is rebase on main + changed how service scaling affects the computation

Back to draft, I need to add values for watcher


can't read localization what's new

def read_app_info():     api = Api(AUTH_KEY_ID, AUTH_FILE_PATH, AUTH_ISSUER_ID, submit_stats=True)     apps = api.list_apps()     for app in apps:         print(app.name, app.sku)     pre = api.list_beta_build_localizations()     x = {v.locale: v.whatsNew for v in pre}     print(x)
why the code can read apps, but the beta build localizations are empty?

they are all "None", as the first picture shows, I indeed inputted what's new for 'en-US', why is none by my code?
If I get the concept wrong, please point it out. Any help is appreciated.

@zrx89757 Thanks for pointing this out.
What your code is requesting is localization for beta builds.
What you screenshot shows is localization for a live version of your app. This info is available in the AppStoreVersionLocalization object described here:
https://developer.apple.com/documentation/appstoreconnectapi/appstoreversionlocalization/attributes
This was added in App Store Connect API v1.2 which is not supported by this library yet. It is at top priority in my TODO list but I can't tell when I'll have time to add it.
We can leave this issue open until then.

Thanks for your reply. Because of my mistake, I uploaded a screenshot in Chinese. Please see the new screenshot below. Currently, what I want to do is a tool that can be used to upload What's new for multiple languages. Because my App is adapted to 12 languages, every time a new version is released, manually uploading What's new is a painful task. The problem is, I’ve been puzzled for a long time and haven’t figured out which API to use to achieve the function.


Trading page no UI

I made setup of peatio and everything works fine except trading page UI
Can someone please help?
This is how it looks

I've done bin/init_config and assets precompile
Peatio and trading ui are the both 1.8

I don't know your setup but you probable need to browse network calls and see what's wrong.

You can also use Telegram channel for quick community support https://t.me/peatio


Viewer app problem

Greetings,
Thank you for the new update.
I exported the viewer app as a zip package, but it does not function properly when opened locally. After uncompressing the zip file, upon opening the HTML file on Chrome, it gets stuck at the loading screen and does not progress further (see the screenshot attached below). I tested it on an iPhone 15 Pro and experienced the same problem. Could you please assist in troubleshooting this issue?
Thank you for your support.

Hi @hjodeiri ,
In order to run the zip version of the viewer, you must access the files through a server. You can't load the html file directly.
I do this using a python script on my Macbook:
#!/usr/bin/env python3
from http.server import HTTPServer, SimpleHTTPRequestHandler, test
import sys

class CORSRequestHandler (SimpleHTTPRequestHandler):
    def end_headers (self):
        self.send_header('Access-Control-Allow-Origin', '*')
        SimpleHTTPRequestHandler.end_headers(self)

if __name__ == '__main__':
    test(CORSRequestHandler, HTTPServer, port=int(sys.argv[1]) if len(sys.argv) > 1 else 8000)

I run this script from the folder containing the viewer files. Then I can access it from the browser using URL http://localhost:8000/index.html or similar.
The server script must have execution privileges on linux and mac, not sure how this works on windows.
Thanks!

Closing, but feel free to reopen if there's anything else we can help with!

Thanks for your response. I was able to view the model in the web browser. However, the AR button does not appear on iOS.

Yeah, WebXR is an Android-only thing for the moment. Hopefully Apple will implement it on iOS some day in the future!


Update to Laravel 10

Is your feature request related to a problem? Please describe.
Laravel 10 will be released on Feb 7, 2023 and will have security fixes till Feb 4, 2025.
https://laravel.com/docs/9.x/releases#support-policy

We might want to try https://laravelshift.com instead of doing the upgrade ourselves.

Upgrade guide
Consider using a service like Laravel shift


Add Water Snake Gun Game

I want to contribute in this repository, so kindly assign me this task, under hacktoberfest 2023

Sure


Added class to interface with Twitter's API (v1.1)

I thought it seemed logical to give some way to use the API straight off without having to dig around the docs too much.
I realise some API routes could deprecate, but these should be easy to update/fix.
This doesn't have to be comprehensive, but it's great for a quickstart. Still loads to be done as well.

i think this is a neat idea but not something i want to directly add to the main library. perhaps have this as your own wrapper that depends on tmhOAuth through composer instead.


Plyr qualities do not update on source change

Hi, it is my pleasure working with Plyr, that is totally cool!
I have worked with it nowadays and it seems there is a problem when video source tags get updated with different size attributes Plyr does not change qualities in settings.
I mean it does not work with React when I set new source tags, destroy Plyr, and recreate it still has old settings.
So is there any option to reset Plyr settings, qualities, captions...?

@amir2mi why did you close this issue? Were you able to find a solution?

I'm facing the same problem. I initialized plyr with empty video tag. Then I want to update the sources of video. But it doesn't work.


Fix to #6451 - Query :: Include doesn't work with SelectMany

Problem was that in several places we transformed query model but we were not updating the (include) annotations accordingly. This resulted in annotations going out-of-sync with the actual query model which then resulted in us not being able to find the right query source to run include on.
Fix is to update query annotations where necessary (nav rewrite, select many rewrite, join elimination).
There was additional problem with string based include - we were always assuming that the include operator was called directly on a DbSet, so string based include didn't work for cases like:
customers.SelectMany(c => c.Orders).Include("...");
orders.Select(o => o.Customer).Include("...");
Fix is to add additional metadata to the IncludeResultOperator that describes the path from the initial query source (i.e. DbSet) to the actual include method. Also refactored expression based include in similar fashion - split old NavigationPropertyPath into two expressions: PathFromQuerySource (the same as with string based include) and lambda describing properties that are being included.

@anpete @smitpatel

Does include work with select many or not? Title is so misleading... :trollface:

Bug was complaining that include didn't work . Fix to this bug is to make it work:)

@anpete new version up, refactored lambda based include and added some extra tests

:shipit:

Merged in 93ecfeca38c45cfc3081756e0a65920db19b42a0


How to setup one Server with Many cleints between ASP Core web and .net Console service

Hi, how do I set this up with one ASP Core site (which acts the main hub) and several services and console apps that run as cleints.
I need to ne able exchange commanfs and heart neat

Hi,
This library is an in-process event aggregator. It seems to me you need a different approach for what you are trying to achieve e.g. SignalR or GRPC.


Fix ScheduledTask Description Whitespace issue - Fixes #258

Pull Request (PR) description
This PR fixes an issue where the ScheduledTask resource will not go into state if the desired description starts or ends with whitespace chars.
This Pull Request (PR) fixes the following issues

Fixes #258

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

@johlju - would you mind reviewing for me when you have time?

This change is

Codecov Report

Merging #279 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff          @@
##            dev   #279    +/-   ##
====================================
+ Coverage    88%    88%   +<1%
====================================
  Files        14     14
  Lines      1483   1485     +2
====================================
+ Hits       1308   1310     +2
  Misses      175    175


Use common code and enable CodeCovIo

This change is

Hi @TravisEz13, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor. If you're full-time or an intern, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@5a366d0). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev      #23   +/-   ##
======================================
  Coverage       ?   86.89%
======================================
  Files          ?        3
  Lines          ?      145
  Branches       ?        0
======================================
  Hits           ?      126
  Misses         ?       19
  Partials       ?        0

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 5a366d0...f96044e. Read the comment docs.

@jcwalker FYI, we are trying to use common code to run tests.  It will add code coverage reports to the PRs and keep track of how we are doing for code coverage over time.  Here is an example from xWindowsUpdate.  The files section at the bottom can be especially useful for making sure you have covered everything you intended to cover.

@kwirkykat  Can you review?

Reviewed 1 of 2 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


Iris flower classification

https://github.com/IEEE-WIE-VIT/WIE-WoC/tree/main/ML AI

Please assign this to me

hey you can close it, i guess it merged with my previous pull request so already updated

Have you completed this PR?

yes its already merged with the main repo, got merged along with the previous issue


TINKERPOP3-670 tail step (v1)

https://issues.apache.org/jira/browse/TINKERPOP3-670
This is implemented as specified in JIRA, with a couple more tests for good measure.
As specified, the behavior for tail(local, 1) is special if the input is a List, in that it emits the element and not a one-element List.  That makes it different from limit(local, 1), but more like select("x") (for a single step label.
In the spirit of "containers only when necessary", should limit(local, 1) be changed to emit the element rather then a one-element List?  I filed https://issues.apache.org/jira/browse/TINKERPOP3-673 to think about that.
I had some OOM problems running the full integration test suite, but all of the new tests are disabled for COMPUTER for various reasons.

@okram This is one of the things you said I could work on.  Any feedback before I rebase against master?

Can you demonstrate TailGlobalStep working with bulks? For instance, do a repeat() to get some bulk going and then make sure your tail() returns expected results. As it stands, I don't think you take that into account.
Did you add your GraphTraversal methods to __ (anonymous traversal)?

I had a quick look - shouldn't TailGlobalStep be a CollectingBarrier?

As I mention in the ticket, I don't think CollectingBarrierStep is optimal because it collects all of the items.  But I will see how it handles bulk, and try to address that in my next PR.

Yea, I don't think CollectiveBarrierStep is right... For bulk, please see how RangeGlobalStep handles bulks.

I'm looking in more detail at how RangeGlobalStep works.  It seems there are a few places where this exact step is a special case (via instanceof checks, e.g. in TraverserMapReduce as well as in several strategies).
The way that Bypassing is used also has to be considered.
I also see that ComputerVerificationStrategy looks for specific types of steps, and TailGlobalStep might belong there.
It feels like some refactoring is warranted.  RangeGlobalStep and CollectingBarrierStep each represent some class of steps to which TailGlobalStep may or may not belong.  Perhaps Bypassing is one such aspect, but are there others?
Maybe TailGlobalStep is really a new animal, but it feels like it ought to be composed from pieces that mean "it is like a barrier, but not exactly CollectingBarrierStep" and "it is like a range, but not exactly RangeGlobalStep".
I'm still coming up to speed on the design, and I'm not yet totally lost, but any pointers would be appreciated.  I can appreciate the tension between a fully a generalized "step aspects" API and one that assumes that the number of fundamental steps is small and so will scale with special case logic.

RangeGlobalStep and TailGlobalStep could inherit from some abstract class. However, I think getting TailGlobalStep built is best first or else the PR will be too big and too hard to review. After that studying the two implementation should yield the generalization. Moreover, both steps are very similar to DedupStep as well. They are like "lazy barriers."
TraverserMapReduce is responsible for dealing with the end of a traversal. It does any final computations like ranging, sorting, etc. And yes, TailGlobalStep would fit there as well. However, I can connect it up to TraverserMapReduce -- its not that hard.
And yes -- ComputerVerificationStrategy will need to complain if TailGlobalStep is used mid-traversal. It can only be used as the end step and thus, its processing relegated to TraverserMapReduce.

Replaced with PR #61


[BanyanDB] Remove ID tag from the measure’s schema.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
OAP’s logical id is used to fetch arbitrary data from the storage layer. In BanyanDB’s scenario, we found a chance to remove this intermediate transformation.
In a typical scenario, OAP combines entity_id + timebucket to logical id. When the data is written, BanyanDB will create an inverted index to map the id to an internal item id which is series_id + timestamp. series_id is encoded from entity_id, and timestamp is encoded from timebucket. So we can remove the logical id to use the original combination to fetch data.
Based on the above, we could remove the ID tag from the measure’s schema in the metric creation phase, then transform by id queries to by entity_id +timebucket.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@lujiajing1126 Before you work on this, we should schedule an offline discussion around the details.


config(prow/config): fix external plugin forwards for tidb-operator

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
What's Changed:
How it Works:

/approve

/approve

/hold

/unhold


Win2008 Browser Functional Test flakiness

https://gist.github.com/BrennanConroy/c6cb60c673d2d99813b9ad6fcc4ebdd7
Tests failing 100% of the time it looks like

Merged https://github.com/aspnet/SignalR/pull/1959 to provide a longer timeout and more logging. Reopen if the failures reoccur. cc @ryanbrandenburg


Update multiple domains documentation

How is what this adds any different than steps 1 and 2 further up the page (https://deploy-preview-533--warden-docs.netlify.app/configuration/multipledomains#multiple-domains)?


Cursors do not align when moving them with the arrow keys while in insert mode

[X] Did you check Readme and existing issues?

Describe the bug
The cursors do not align when moving them with the arrow keys while in insert mode.
To Reproduce
Steps to reproduce the behavior:

Enter normal mode of multicursors with <leader>m.
Move the cursor down or up with j or k.
Enter insert mode with i.
Move the cursor with the arrow keys.

Expected behavior
It is expected that the cursors align when moving them with the arrow keys, just as they do when entering insert mode with a.
Screenshots

Nvim version:
NVIM v0.10.1
Build type: RelWithDebInfo
LuaJIT 2.1.1713484068
NVIM v0.11.0-dev-657+gbb4b6b427
Build type: RelWithDebInfo
LuaJIT 2.1.1724232689
NVIM v0.11.0-dev-660+gcf44121f7
Build type: RelWithDebInfo
LuaJIT 2.1.1724512491
Multicursor version:
commit 562809a
Additional context
Add any other context about the problem here.
It works with append a:

Tested on minimum configuration:
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
  local lazyrepo = "https://github.com/folke/lazy.nvim.git"
  local out = vim.fn.system({ "git", "clone", "--filter=blob:none", "--branch=stable", lazyrepo, lazypath })
  if vim.v.shell_error ~= 0 then
    vim.api.nvim_echo({
      { "Failed to clone lazy.nvim:\n", "ErrorMsg" },
      { out, "WarningMsg" },
      { "\nPress any key to exit..." },
    }, true, {})
    vim.fn.getchar()
    os.exit(1)
  end
end
require("lazy").setup({
  spec = {
    {
      "smoka7/multicursors.nvim",
      event = "VeryLazy",
      dependencies = {
        "nvimtools/hydra.nvim",
      },
      opts = {},
      cmd = { "MCstart", "MCvisual", "MCclear", "MCpattern", "MCvisualPattern", "MCunderCursor" },
      keys = {
        {
          mode = { "v", "n" },
          "<Leader>m",
          "<cmd>MCstart<cr>",
          desc = "Create a selection for selected text or word under the cursor",
        },
      },
    },
  },
  defaults = {
    lazy = false,
  },
})

I just verified that it works correctly in version 2.0.0. It would be good to consider this regression in the main branch (commit 562809a) for future versions.

I can't reproduce this. Are you sure that the behavior changed since v2.0.0?
Cause there is no change in logic between v2.0.0 and the main.

You're right, I did more testing with version 2.0.0, and the problem persists.

The issue occurs with insert and append when I create the multicursors from anywhere other than the beginning of the word in the case of insert or the end of the word in the case of append.

It should move that way cause j and k only create a selection for just a char not the word.
If you want to create cursor for the word use the n.


[ll] layer range for clear_attachments

Replaces the Rect in clear_attachments with ClearRect to allow for clearing layers in an attachment. Only implemented for vulkan & dx12 for now.
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends: vulkan, dx12

bors delegate+

bors r=kvark


Importing cris-configuration.xls always sets 'new-line' property to 'false' for nested objects...

... due to little typo. I've already created a pr: https://github.com/4Science/DSpace/pull/66

PR above merged, issue solved. Thanks again to report and fix it


Add PowerTab History $PowerTabStatus.History

Adding a history for Powertab would help with generating unit tests and finding bugs. Have an exported variable like $PowerTabStatus with a property of History ($PowerTabStatus.History). I would think a few properties would be useful: Line, LastWord, CurrentDirectory, TabList (list of choices returned to PowerShell), and Time (when it was run).
Originally reported on CodePlex by StephenMills.

There is a logging function that I have been using to develop PowerTab. If you set $PowerTabLog to $true, it will create a log in your user home directory. I have thought about formalizing it more.

Comment from StephenMills:
Interesting. I've turned mine on for now. Unfortunately, it looks like you would have to parse it if you wanted to use it to build a unit test. I was thinking of using either a PSObject with properties or a Dataset with a DataTable. If it included the results it got, then you could see what it got or what it should get for a unit test.

I am defering this now that there is a Trace log and Debug log that can be enabled in PowerTab. Additionally, you can configure the selection handler to "Default" to have all choices returned by PowerTab in the case of unittesting.


Begin fixing landing customization

There is a surprising amount of content that depends on $.Site.Data.landing. This is bad and should be removed or made to use something default-but-changeable This changeset does exactly that. I've also reworked the way that iamge compare is checked for, which makes it possible to use it in the body content as well later as a shortcode.
This also begins the process of making all scripts fingerprintable for SRI.
TODO:

[x] Reduce uneccesary calls to $.Page.Scratch.Get and related.
[ ] add a way to set the default configuration for image comparisons (simple now)
[x] Move the script at the end into app.js (w/a check that we have indeed added the script)
[x] Pet the dog & drink eggnog.

Changes

Move around template logic for the Image Comparison script inclusion. Adding to the end is the right way to do it.
Rename landing.yaml to landing_default.yaml -> This should actually be in data/lotusdocs to namespace it away but I didn't want to make any sudden movements.
Fixed up references to $.Site.Data.landing to one.
Made templates relative to their config data. This allows for multiple instances of each that do not interfere with one another.

fixes #143 and future-proofs it a bit.

When is this PR get reviewed potentially merged?
i had to update couple of things by manually to make the landing page works.
Kudos to the creator. 👏 I love this theme.

Nice to see this! It was driving me crazy and then decided to check the issues and prs. Looking forward to it getting merged.

I'm pretty confident that this is ready for at least an initial review.
Things that should be considered for a future change:

Default image comparison options
Unify the CSS into one single set of scss instead of weird duplication.

knock knock: Any chance of getting this merged?

Would be great to see this merged. @colinwilson any chance you can have a look at this?


Replace error-chain with failure

error-chain is going to be deprecated.
Using failure means it is easier to integrate with frameworks such as actix as well as requiring less boilerplate in end user binaries.

Hi @chris-ricketts, thanks for the PR.  Agree that error-chain needs to go away; it was the flavor of the day at the time but, in hindsight, wasn't an appropriate choice for this crate.
Right now I'm debating whether it makes sense to have the failure dependency or whether it might be better to just expose a custom error enumeration.  Now that (as of 1.30.0) std::Error has source we could still daylight the underlying nix (or whatever) error as needed.
For brevity in tests/examples I think failure as a dev-dependency (if it simplifies anything) is reasonable.
Thoughts?

Hey @posborne, do you know of any crates that show the use of source with std::Error that would serve as a good example?

This thread has some good information and this post contains links to how @burntsushi is doing things in several places.  There is certainly some extra boilerplate in doing things this way but I think it is worthwhile to be explicit about errors in a crate like this one.
https://users.rust-lang.org/t/error-chain-is-no-longer-maintained/27561/8
Admittedly I still need to do some reading and I don't think some of these solutions solve the backtrace problem.  With a proper breakdown of errors, however, I think this is probably not too big of a problem in practice (for this crate).

Another example I saw while looking at a new crate from Alex: https://github.com/alexcrichton/wast/blob/master/src/lib.rs#L165-L214

Hi @posborne - thanks for the feedback, research and links to the examples.
I think an approach like Alex's would be the best plan.
It gets rid of a dependency and gives the end user the choice.
failure::Fail has a blanket implementation for anything that implements std::error::Error + Display and is also 'Send + Sync + 'static so I think we should try to fulfill those requirements.
I will close this PR and open an issue that references it.
I'm happy to try and complete the task.

Thanks @chris-ricketts, absolutely take a shot, otherwise I can certainly take on the task as well.  Just let me know.


Cannot create consumer with file deliverGroup

I got this problem when createing consumer by nack unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Consumer.spec): unknown field "deliverGroup" in io.nats.jetstream.v1beta2.Consumer.spec

This is my configuration
apiVersion: jetstream.nats.io/v1beta2
kind: Consumer
metadata:
  name: my-push-consumer
spec:
  streamName: mystream
  durableName: my-push-consumer
  deliverSubject: my-push-consumer.orders
  deliverPolicy: last
  ackPolicy: none
  replayPolicy: instant
  deliverGroup: test

The problem is I use old crd k8s, sorry for this inconvenient


Sample Azure Function App with C# Library

Description
As a SDK consumer, I want to look at an example Azure Function  app so I can see how the API would get called in a real-world scenario and learn how to structure my own usage of the API.
Acceptance Criteria

[ ] Azure Function app that can be loaded and debugged on any machine with dotnet core.
[ ] No dependencies on Azure or other external services apart from the C# CA-SDK library
[ ] Demonstrated minimum viable usage of the API
[ ] Tests demonstrate usage of json data sources as mocks for the real data sources
[ ] Code demonstrated how to configure credentials for WattTime / ElectricityMap and how to configure the aggregator to point to whichever data source.

Dependencies

#160

Task List

[ ] Split az func to be for IEmissions and IForecast
[ ] Integrate into pipeline to build automatically
[ ] Integrate into pipeline to run
[ ] Perform emissions requests against az func running.
[ ] Document any extra vscode packages needed to be able to run func.
[ ] Review docs to ensure clear about what is local, and what requires azure deployment as an example.

Sprint-Ready Checklist

[ ] Acceptance criteria defined
[ ] Acceptance criteria is verifiable / testable
[ ] External / 3rd Party dependencies identified
[ ] Engineering team understands acceptance criteria
[ ] Is the user story small enough to be implemented in a short amount of time, but large enough to provide value?

There is a sample Console App in the Branch for #171 .  I was able to use the code in the Console sample to get an Azure Function up and running.  Please review and evaluate if we need more in the console app.

Love the sample that was checked in as part of that commit and I think that's a great place to start. It has the conceptual level of complexity that I think we need here. That said, I think we can revisit this once we have the full library built out to have a full living artifact that is a good representation of the library at that time.

PR merged


soft links do not always apply the changes in the python scripts

this issue doesn't appear on all computer and may be related with permissions (/usr/local/ installation). It can also be caused by the creation of the link, that we do during the package creation and not during the installation.
This issue can be problematic for patches.

fixed in commit 8f70f0271f09b8a6eaa56b2ca6a61c0a7074c879


refactor(catalogClient): return fetched entities sorted by ref

Signed-off-by: Phil Kuang<EMAIL_ADDRESS>Implementing suggestion by @freben to sort entities fetched from the catalog to preserve alphabetical order behavior from the old catalog processing engine.
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

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

We should probably create a ticket out the back of this to implement sorting at the backend level either at the API or GraphQL when the time comes :)

Also @kuangp sorry, you'll need to rebase this too 👍

Merging with the caveat that we need to address this properly before pagination.


[Broker] Add spotbugs to pulsar-broker

Signed-off-by: Zixuan Liu<EMAIL_ADDRESS>

The license format of findbugsExclude.xml is wrong, take https://github.com/apache/pulsar/blob/master/pulsar-client-api/src/main/resources/findbugsExclude.xml for example.
Also, you need to fix the spotbugs if existed.

The license format of findbugsExclude.xml is wrong, take https://github.com/apache/pulsar/blob/master/pulsar-client-api/src/main/resources/findbugsExclude.xml for example.
Also, you need to fix the spotbugs if existed.

/pulsarbot run-failure-checks

@nodece Can you rebase the pull request?

@sijie done.

/pulsarbot run-failure-checks

Too long for no activity, so close.


In network contrained environement we shoud have a diferent url for github like an artifactory proxy

When we use in contrained environement it try to download already build binnary its great but i cannot use a different url to download this file and i cannot acces to github.com so i have to proxy it can we do a environement variable to permit to change this url  ?
Did they is a different workarround for this ?
Thanks !
from-github-release.js
https://github.com/lovell/sharp/blob/fc32e0bd3f9111b80cf078df7b0cfc355695674e/npm/from-github-release.js#L42

Please ensure you are using the latest version as everything is published to the npm registry and nothing is downloaded from GitHub.
(The file you link to contains pre-publish logic and does not run on your machine.)


Project type is being reconfigured to PHP if config is run before composer install

Is there an existing issue for this?

[X] I have searched the existing issues

Expected Behavior
When checking out a new project with type: drupal10 (or lower), and something like this is run before composer install:
❯ ddev config --web-environment-add="COMPOSER_CACHE_DIR=/var/www/html/.ddev/.drainpipe-composer-cache"
You are reconfiguring the project at /home/justafish/repos/site.com
The existing configuration will be updated and replaced.
A project of type 'php' was found in /home/justafish/repos/site.com/web, but the project is configured with type 'drupal10'
Configuring a 'php' project with docroot 'web' at /home/justafish/repos/site.com/web
Configuration complete. You may now run 'ddev start'.

This is causing jobs using Drainpipe's DDEV action to fail. Example workflow here: https://github.com/Lullabot/drainpipe/issues/512
Actual Behavior
This is happening because when detecting the project type it's looking for a file that isn't necessarily present yet: https://github.com/ddev/ddev/blob/63f9c6744d3080cbf4cf729946c228e4928a6faf/pkg/ddevapp/drupal.go#L321

Already fixed in (will be available in DDEV v1.23.0):

#5887

BTW, your GitHub action uses an old repo link. It works, but it's better to update it to the latest one.


Missing field 'target_contract'

Component
Cast
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (8ef9433b6 2024-10-12T07:23:31.975840000Z)
What command(s) is the bug in?
cast run --tweak UniswapV2 0x01cb3ebe9f9222771f1d025edd195c9d06a0a9cd27378bad920bd478cb31224c --rpc-url https://rpc.ankr.com/eth
Operating System
None
Describe the bug
I follow the tutorial, but without any log adding, just run the cast run --tweak, then i got the following error:
failed to load tweak project from path:,
Context:
- missing field `target_contract` at line 1 column 2982

I just merged a PR fixing this bug. Could you try the latest commit? @Refrain-123


OSMC still uses MirrorBits

I'm not sure why it says we used to use MirrorBits, we still use it to this day!

This is fixed :)


about the Brats Dataset

The original Brats Dataset are 3D slices, how you transform them to 2D slices like sample dataset

As described in Section 3 of the paper, we slice the 3D MR scans in axial slices. Since tumors rarely occur on the upper or lower part of the brain, we exclude the lowest 80 slices and the uppermost 26 slices.

@JuliaWolleb where is this - the exclusion of 80 and 26 slices happening in the code? kindly tell me


Correct typing error arclix docs

Issues:

There is an extra double quotes in scopeStyle command.
Screenshot of the issue

[ Triaged ] Good to fix this issue.


Added check for required npm and node versions

This solves #149

Hmm, seems like we need to install gulp before this, any ideas?

That was a bug from my side, let see if now all is okay.

Looks good to me! How about making the check even before running tsd --reinstall?
If node/npm is not the version we need there's no point installing the ambient type definitions as well.

Actually if I move that gulp check to be first on that npm postinstall task. Version check will crash with following error (also note that this happen with clean install, so there is no node_modules and those tsd files):
[12:45:17] Requiring external module ts-node/register
----------------------------------
⨯ Unable to compile TypeScript

gulpfile.ts (1,23): Cannot find module 'gulp'. (2307)
----------------------------------

npm ERR! Linux 3.13.0-66-generic
npm ERR! argv "/home/wunder/.nvm/versions/node/v4.0.0/bin/node" "/home/wunder/.nvm/versions/node/v4.0.0/bin/npm" "install"
npm ERR! node v4.0.0
npm ERR! npm  v3.3.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: `gulp preinstall && tsd reinstall --clean && tsd link && tsd rebundle && gulp postinstall`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'gulp preinstall && tsd reinstall --clean && tsd link && tsd rebundle && gulp postinstall'.
npm ERR! This is most likely a problem with the angular2-seed package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp preinstall && tsd reinstall --clean && tsd link && tsd rebundle && gulp postinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls angular2-seed
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/wunder/projects/angular2-seed/npm-debug.log

Oh, yeah sure...It makes sense it can't find the typing definitions for gulp. Merging.


Add Korean Translation

Is your feature request related to a problem? Please describe.
Thank you for creating a wonderful repository for training generative AI!
I would like to start a translation project to make this repository accessible and useful for Korean users as well.
Describe the solution you'd like
The following modules are planned for translation.
Please let me know if you would like to translate any of them, and I will add your name to the list as a tag.

[ ] Course Introduction - How to Take This Course @FacerAin
[ ] Introduction to Generative AI and LLMs @FacerAin
[ ] Exploring and comparing different LLMs @Eeap
[ ] Using Generative AI Responsibly @mreraser
[ ] Understanding Prompt Engineering Fundamentals @FacerAin
[ ] Creating Advanced Prompts @FacerAin
[ ] Building Text Generation Applications
[ ] Building Chat Applications
[ ] Building Search Apps Vector Databases
[ ] Building Image Generation Applications
[ ] Building Low Code AI Applications
[ ] Integrating External Applications with Function Calling
[ ] Designing UX for AI Applications @mreraser
[ ] Continue Your Learning

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello @FacerAin! Can I participate in your project as well? I'll do my best!
If I can choose a module, I would like to select 'Using Generative AI Responsibly' and 'Designing UX for AI Applications'.
Thank you!

Hello, @FacerAin
If there is no one who translate "Exploring and comparing different LLMs", I want to select it !
Thank you :)

Hi everyone, thanks for wanted to contributing a Korean Translation. Will get a reviewer once a PR is submitted. Good luck and let us know how we can support!

Thanks for your help! @mreraser
I’m sorry for the late reply.
Could you submit a PR to the translation/ko branch of this repository?
After review, we will proceed with a request to the original repository via one PR.

Hello @FacerAin, if nobody translated [ch 5 : Understanding Prompt Engineering Fundamentals] can I additionally participate on?

Hello @FacerAin, if nobody translated [ch 5 : Understanding Prompt Engineering Fundamentals] can I additionally participate on?

@mreraser
Oops, I’ve already done the work but forgot to update the list 😭😭 I’ve updated the post with the chapter I’m working on. Could you please refer to it and let me know again?
Thank you so much for your contribution. ☺

Building Text Generation Applications

OK, then can I translate [Building Text Generation Applications]?

Hello @FacerAin, if nobody translated [ch 5 : Understanding Prompt Engineering Fundamentals] can I additionally participate on?

@mreraser
Oops, I’ve already done the work but forgot to update the list 😭😭 I’ve updated the post with the chapter I’m working on. Could you please refer to it and let me know again?
Thank you so much for your contribution. ☺

OK, then can I translate [Building Text Generation Applications]?

@mreraser
Of course! I’ll add it to the list above! Thank you ☺


Add e2e tests

I think we should really have some e2e tests for this project to ensure that, when new features are added, we don't break existing functionality.
My preference would be to write mostly e2e tests for the checklist with Cypress. Cypress a fast and reliable testing framework and I have been using it for some of my projects. It really is reliable and writing tests is fun as well.
So I suggest that we create some tests for at least,

[ ] 1. project page

[ ] adding projects
[ ] editing
[ ] renaming
[ ] and deleting

[ ] 2. checklist page

[ ] check / uncheck items
[ ] add / remove favorites
[ ] edit mode (check / uncheck categories, test if a popup is shown when the category has favorites, test if the content area is not actionable and no items can be toggled)
[ ] change project
[ ] search for items and categories
[ ] filter items
[ ] check / uncheck all
[ ] about dialog

If anyone wants to take this over, I am more than happy to provide assistance and help you out with getting Cypress up and running.

i'll give it a try (great way to learn Cypress).

Yay, this is good news! Thanks @geromegrignon for giving this a try. Let me know if I can help you with anything. You can look at my [library]https://github.com/d3lm/ngx-drag-to-select/tree/master/cypress() for some inspiration. Make sure to add a TypeScript preprocessor using the @cypress/webpack-preprocessor package. I would definitely want the tests to be written in TypeScript. Also, remove all the Protractor stuff from the project. Important for the setup is a tsconfig.json inside the cypress folder.
Again, let me know if you need help with this.
Oh and, keep your commits as small and focused as possible. This makes it easier to review your PR and all the changes. For example, the first commit should be set up cypress, etc.

@geromegrignon How about I take care of the setup and you and some other people can work on the tests itself? Because there was also someone else on Twitter that was interested and I thought that we could make this a collaborative effort. Maybe you could work on the projects page and @IxquitilisSaid could work on the checklist or vice versa. But I suggest that we coordinate this here, not that multiple people work on the same tests.
How does that sound? Do you have a preference as to what you'd like to test? If you want you can also do the setup, but I'd really like to help.

I almost completed the setup part with typescript so i'll make a pull request if you don't mind (it'll be a great help to know if it's allright).
I would be happy to share this part : i have no preference.

I'll start to work on 'project page' tomorrow.
Would you prefer a pull request once it's fully done or as soon as i implemented the first test to be able to discuss about changes gradually?

Hi @geromegrignon!
I would try to keep PR's as small as possible. The sooner you submit something, the sooner we can provide feedback. :)

Btw, I'm gonna make sure the tests are run on Travis during every build as well. I'll create a PR for that asap.

Thanks @KwintenP.
@geromegrignon As Kwinten already said, please feel free to send in WIP PRs. Those are totally fine. The sooner you commit something, the sooner we can give feedback and review your code.

For each PR, i'll wait the review to add data-cy attributes to target DOM elements as a best practice.


Phase Advancement Bug

During the Ga BEST 2017 gameday event, the system picked the wrong teams to be advanced from the Seeding phase to the Wildcard phase.
No crash or fatal errors, just picked the wrong team numbers.

No longer relevant as Olympus has become FLL only


acr_values should be a space separated string

As defined in  https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest, the acr_values parameter should be handled as a space-separeted string.
Actually is defined as
ACRValues    []string            `json:"acr_values" schema:"acr_values"`

instead of
ACRValues   SpaceDelimitedArray  `json:"acr_values" schema:"acr_values"`

This causes a panic when a request object of this kind is used:
{
  ...
  "acr_values": "foo-bar"
}

@dellekappa thanks for the report we will have a look at it

@dellekappa you are right. This can be considered a bug.
If you want, you can open a PR with a fix against the next branch, just to make sure it doesn't break for people that depend on the current but broken implementation. If you are not able, we will pick it up but it might take a bit longer ;).


Add tests for different code paths in tools/cell_census_builder/tissue_mapper.py

Motivation
The goal is to at least have coverage for all of the positive test paths.
Definition of Done
Add unit tests that cover the logic flows in TissueMapper.get_high_level_tissue

I noticed that this code is extracted from the data portal, which has its own test. We have a few options:

Leave it as is

Copy the test as well

Package it into a new library

Package it into cellxgene-schema and publish a new version

is obviously the best solution but will involve a bit of coordination since we'll have to create a new repo and pypi library. I also know there is some work scheduled for an
"ontology service", which would naturally include this method, but I don't know the ETA.

is a decent solution but adds a dependency that we might not need (although technically the census depends on the cellxgene schema to work, so might not be so bad...)
Thoughts?

I'm proposing that we reject this ticket and replace it with an "use the Ontology Service when available to replace tissue_mapper.py". I don't think we should copy the test over from the data portal as that will increase data duplication. I would add a comment at the top of the file with the new ticket number and with a note to not modify the file (unless the same change is also applied to the data portal).
@Bento007 any thoughts on the above approach?


Docs: use the minimum CMake version supported by vcpkg

Describe the pull request
What does your PR fix?
vcpkg examples use CMake minimum versions that aren't compatible with the one specified in https://github.com/microsoft/vcpkg/blob/master/scripts/vcpkgTools.xml.
This PR instead uses the smallest CMake version number present in vcpkgTools.xml, which is version 3.12.4 at the current time.
Which triplets are supported/not supported? Have you updated the CI baseline?
I don't believe that's relevant.
Does your PR follow the maintainer guide?
Yes, I think that's the case.

Personal opinion since I dont give anything about linux distros. It should be 3.17 or even better 3.18 since this will be the minimum vcpkg internally uses.

Thanks for the PR!
The version of CMake used in our examples is explicitly decoupled from the version in vcpkgTools.xml -- users are not required to use the version of CMake that vcpkg builds packages with.
This also makes a bunch of unrelated changes: every markdown bullet is changed from * to - and the manifest file example has been formatted away from our required canonical format.
Given this, I'm going to close this PR for now. If you'd like to open new documentation improvement PRs in the future, we're happy to review them.

You're right, my editor auto formatted on save and I didn't notice. Could you clarify if you would accept a PR that would only do the change of CMake version, or if that's something you would be against? At minimum that would make it more consistent and suggest to use a more recent version of CMake, but I don't know if that's valuable from your point of view.


Bug: Running Depscan returns Killed

Expected Behavior
When using depscan I expect it to scan the folders to make an SBOM and check for CVE's
Actual Behavior
It returns the following:
The depscan banner and the text Killed below it.
I did not imput anything between running the command and Killed being returned.
Steps to Reproduce
Use an Ubuntu 20.04.6 machine.
Install CDXGen en Depscan using the manual in this repo.
Additional Information
Is it possible that Ubuntu 20.04.6 is not supported by Depscan anymore? I have been able to run in on both Windows 11 and Ubuntu 22.04.
Both CDXGen and Depscan installed without errors.
I also tried running depscan with the --debug flag but that also just returns the banner and then killed.

It must be running out of memory. Could you allocate a minimum of 8GB RAM and 15GB hdd space?

It must be running out of memory. Could you allocate a minimum of 8GB RAM and 15GB hdd space?

I can confirm that the machine has more that 15GB of free space on the HDD.
Does depscan by itself need 8GB of RAM or is that for the whole machine?

How much free memory is available? Best to watch the process using top command and find when it crashes?

How much free memory is available? Best to watch the process using top command and find when it crashes?

We have increased the RAM of the machine for 8GB to 16GB and the problem is no longer there.
When I ran the top command before I saw that the machine was running out of RAM so that was indeed the issue.
Thank your for the help with troubleshooting

Thank you @Geertkok1. We are looking into the memory issue for depscan v6. It will use vdb6 powered by sqlite, so doesn't require the entire index to be loaded in memory.


Improve PPO baselines when there are no partial resets

They perform pretty poorly when there aren't partial resets, unclear exactly why this occurs. Could be a small bug in the PPO implementation. Initial experimentation suggests the reward scale has a lot of impact on performance than usual, and value loss explodes when tasks begin to succeed.

A possible reason could be due to using logstd without clipping std? you can try with
    self.actor_std = nn.Parameter(torch.ones(1, np.prod(env.single_action_space.shape)) * 0.1)

and do
action_std = torch.clamp(self.actor_std, min=1e-5, max=0.1).expand_as(action_mean)

You can try testing it with
seed=1
python ppo_rgb.py --env_id="PushT-v1" --seed=${seed} \
    --num_envs=256 --update_epochs=8 --num_minibatches=8 --reward_scale=1 \
    --total_timesteps=50_000_000 --num-steps=100 --num_eval_steps=100 --gamma=0.99 \
    --no_partial_reset --reconfiguration_freq=1 --num_eval_envs=16 \
    --exp-name="ppo-PushT-v1-rgb-${seed}-walltime_efficient"

and the partial reset version
python ppo.py --env_id="PushT-v1" \
  --num_envs=1024 --update_epochs=8 --num_minibatches=32 \
  --total_timesteps=25_000_000 --num-steps=100 --num_eval_steps=100 --gamma=0.99

I think the no partial reset version runs much slower than expected. I have to set reward_scale=0.1 to avoid value loss explosion. I can also give your trick a try later.

unfortunately did not work. Black line is with reward scaling of 0.1, other line is with clamping and no reward scaling. normally I do not do any reward scaling with the ppo example code in here: https://github.com/haosulab/ManiSkill/blob/main/examples/baselines/ppo/examples.sh


Expose Optimized Transformers Inference for ETL

Feature request
I'd like to use this library for really high throughout ETLs along as an inference server. How I imagine this working is exposing some sort of object which can operate on in-memory datasets.
I am sort of running under the assumption this would be even more performant than native bettertransformer inference in memory.
Motivation
Inspired by vLLMs offering which is great for running LLMs in a big data or ETL setting.
from vllm import LLM
llm = LLM("facebook/opt-13b", tensor_parallel_size=4)
output = llm.generate("San Franciso is a")

Your contribution
If this is a reasonable first task I would be happy to take a look.

@sam-h-bean Not to easy, i tried that in a similar project (https://github.com/michaelfeil/infinity) - thats written in pure python, and a bit slower (2.5x less throughput).
Some starting points:
Here the codebase is purely in Rust, using tokio for the async stuff, so you might want to launch a server with open port + you need a channel for the grcp things.

Create a RustAPI that requires launching the server without a server.
Figure out what to do with the grcp channel.
Create python bindings for the rust api.


Add NuGet.org API token as a Repository Secret

Per https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository
please add the CodeMonarchs NuGet.org API token as a Repository Secret named NUGET_ORG_API_TOKEN
I can't do it because this is restricted to the repo owner.

@cpdohert Added.


No commits in common is shown when comparing identical branches

Gitea version (or commit ref): 1.14.0+dev-622-g41c077656
Git version: 2.30.0
Operating system: Docker
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL) https://try.gitea.io/test_org21/test_repo/compare/master...master
[ ] No

Description

No commits in common. 'master' and 'master' have entirely different histories.

I think this is a typo

I think this is a typo


Create unified structure for all support packages

use only lower case letters in resources

Apologies for the many comments. I should've submitted a review instead.

Apologies for the many comments. I should've submitted a review instead.

Thanks for the quick review, it was perfect this way too :)
If you do not have any other comments (aside from licensing, which decision I would postpone), I will merge this PR

If you do not have any other comments (aside from licensing, which decision I would postpone), I will merge this PR

I've not gone over everything, but for now I believe the majority has been addressed.
I'll post issues if I believe there is something else to suggest.


Fix TestCaddyStartStop

Move this test to caddymain to fix import problems
Minor fixes to bypass locks and race conditions
1. What does this change do, exactly?
Fixes TODO test.
2. Please link to the relevant issues.

3. Which documentation changes (if any) need to be made because of this PR?
There shouldn't be documentation changes
4. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I am willing to help maintain this change if there are issues with it later

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Its my first contribution to this project. There is minor change with fixed TODO test. Let me know if this is required change or shouldn't be done in a future.

Hi @SmilingNavern - welcome to the project, and thanks for submitting a PR!
Can you help me understand, what exactly does this fix? It looks the same to me, except it moved to a different package...

Hi, @mholt
Okay, i will break it down as i understand it:
This test checks if caddy can start. When we use caddyfile and want to start caddy we need to have some plugins(for server_type support). When test was ran at caddy there was no plugins because they should be imported(http plugin for example). And we can't import http into caddy because of cyclic import problem.
So i moved it to caddymain as it seems most logical way to fix this problem.
Also i changed a two lines: we get testInst to correctly close instances(or we get some kind of deadlock) and added sleep to prevent bind problem.
If you need any further explanation let me know.

Hmm, well this test was disabled because it has kind of a race condition, especially on Windows. It has nothing to do with the plugins. I think I intend to remove integration tests such as this one and put a suite of tests in a separate repository to do them more thoroughly and correctly.

Oh, ok. So it wasn't needed after all:) But i've got problems described above after enabling this test.
So should i close this pull request?

Yeah, sorry. I think a full integration + systems test suite will best be implemented in a new repo.