Jenkinsfile testing for scenario runner

Description
This is test version of Jenkins based pipeline for scenario runner, which will help in continuous integration.
As per the initial attempt it is expected from this file that it should return the python version.
Result of this test will help in determining the further step of either rework on pipeline code or work on sh file that will contain the commands to be executed automatically.

Fixes #
Results of this attempt will lead to fixes
Where has this been tested?
Needs to be tested on Jenkins server
Possible Drawbacks
Since it will be tested in Jenkins server, if anything goes wrong check the Jenkins server 1st.

This change is

Hm... Maybe we should discuss the testing procedure, before going into writing Jenkins scripts? How will a scenario be executed? What is success and what is failure? What docker image do we need to use, how do we handle different branches, etc.?

Hm... Maybe we should discuss the testing procedure, before going into writing Jenkins scripts? How will a scenario be executed? What is success and what is failure? What docker image do we need to use, how do we handle different branches, etc.?

Sure, Lets discuss !


Instalation ERROR

Windows 10 64 bit, node 12.15.0, npm 6.13.7
I'm following https://lwc.dev/guide/install#tools and encounter errors at the beginning,
`salesforce> npx create-lwc-app mvv-app
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@typescript-eslint/parser'
npm ERR! notarget
npm ERR!  C:\Users\marce\AppData\Roaming\npm-cache_logs\2020-02-10T20_26_01_533Z-debug.log
Install for [ 'create-lwc-app@latest' ] failed with code 1`
As mention here: https://github.com/salesforce/lwc/issues/1718#issuecomment-584344950, issue also find on mac

Does this still happen? There seemed to be a problem with their npm package which seems to be resolved now.
https://github.com/typescript-eslint/typescript-eslint/issues/1588

No is not happening anymore, thanks

.


Vimeo speed controls do not work

Speed switching does not work on Vimeo videos with tariff Plus

It's may related to this issue https://github.com/sampotts/plyr/issues/2123


Improve contrast for project/tag selection

Please remember the Contributing Guidelines :heart:
:star2: What does this PR do?

Continuation of work from @devnetkc
Replace green/gray with rebrand pink/purple in the project/tag popdown

:bug: Recommendations for testing
All changes should be tested across Chrome and Firefox.

Dark Mode

Light Mode

:memo: Links to relevant issues or information
Related #1813

Please remember the Contributing Guidelines :heart:

Thank you for the great tips. I will try and do a better job next time.

@devnetkc That comment is just part of the PR template your PR was great, thanks for your contribution


Update README.md with serial comma

Update README.md to include a serial comma to better resolve ambiguity between the three terms HTML, SVG, and CSS. Wikipedia states that an omission of a comma before the last term can suggest a stronger connection between the last two items in a series.

+1 Minor but correct.

+1 for the Oxford comma.

@mbostock Do pull requests actually get merged here? Or is submitting one mostly a waste of time?

@awelch83 I’ve merged hundreds of d3-related pull requests.

I made the corresponding to d3js.org as well.


docs: Added new dodevops puppet lint checks

I'm not sure if you'd like to have https://github.com/dodevops/puppet-lint-module_reference-check in the list, because it's mostly very specific to our implementation. (see also #44)

Releasing it would be blocked on https://github.com/puppetlabs/puppet-lint/issues/32. I'm not sure if @puppetlabs is looking into this.


ARROW-13448: [R] Bindings for strftime

This is to resolve ARROW-13448.

Thanks for the review @thisisnic!

Another thing to note here is that behavior of the %S flag is different in arrow:

Output precision of %S (seconds) flag depends on the input timestamp precision. Timestamps with second precision are represented as integers while milliseconds, microsecond and nanoseconds are represented as fixed floating point numbers with 3, 6 and 9 decimal places respectively. To obtain integer seconds, cast to timestamp with second resolution. The character for the decimal point is localized according to the locale. See detailed formatting documentation for descriptions of other flags.

This is already tested in c++ and we test it in Python like so. I'm not sure there's a point in testing it in R but it could look like this:
  arr <- Array$create(c(lubridate::ymd_hms("2018-10-07 19:04:05"), NA), type = timestamp("s"))
  expect_dplyr_equal(
    input %>%
      mutate(x = strftime(x, format = "%S")) %>%
      collect(),
    arr
  )

Except this wouldn't work for type reasons:
Error (test-dplyr-string-functions.R:756:3): strftime
Error: no applicable method for 'mutate' applied to an object of class "c('Array', 'ArrowDatum', 'ArrowObject', 'R6')"

behavior of the %S flag is different in arrow

So, the R "%S" returns an integer, so you're right in highlighting the difference between Arrow and R.  We have other time-related functions which return slightly different values, which we allow for, e.g.
https://github.com/apache/arrow/blob/5260fd5970d34c62e0ae7680f606b29eab56d96b/r/tests/testthat/test-dplyr-lubridate.R#L155-L164
The function expect_dplyr_equal(), as you've pointed out, won't work on Array objects.  However, you could write a test like the one shown above, which just adds a tolerance (given that the user is being returned a more precise answer than they would have, the tolerance is justified).

@thisisnic @jonkeane sorry this took a while. Could you please make another pass?

@thisisnic good catch on format_ISO8601. If you don't have a strong preference I'll go ahead and add id.
Yet another thing to note: the c++ strfkernel only works for timestamps at the moment. When dates and times are added (ARROW-13916) we should add tests in R as well. I'll make a note on Jira.

Ok, added format_ISO8601 and moved %c check into c++. I suppose another review is in order @thisisnic :)

Thanks @thisisnic @jonkeane @edponce !


[TC-APPLAUNCHER-] Manual Yaml Script has to be updated as per Verification Step document

Description:
Manual Yaml Script has to be updated as per Verification Step document for below mentioned test cases

[ ] TC-APPLAUNCHER-3.7.1 -  command has to be updated as per Verification Step document for all steps.
[ ] TC-APPLAUNCHER-3.8.1 -  command has to be updated as per Verification Step document for all steps.
[ ] TC-APPLAUNCHER-3.9.1 -  command has to be updated as per Verification Step document for all steps.

Yaml-References:
https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_APPLAUNCHER_3_8_1.yaml
https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_APPLAUNCHER_3_7_1.yaml
https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_APPLAUNCHER_3_9_1.yaml
Verification Step Document References:
https://docs.google.com/spreadsheets/d/13zltSz50GRs_kidvobceEuIT8kAAHSK64ANyWcc3xQI/edit?usp=sharing

This issue has been addressed in this branch https://github.com/project-chip/connectedhomeip/commit/17fc008fe270596886cb4d6f6a7d70013e48a972


Uploading images on iOS

I'm trying to upload a PNG image to the Media Pool on iOS but am getting stuck with what I believe to be the correct value to set for the uncompressedSize parameter to uploadStill. See my code below:
The resizeImage function just resizes the image to fit within a 1920x1080 box. The same problem occurs if I try to send the original UIImage.
Looking at your TitleGenerator example, you're setting the size of the uncompressedData to be 1920x1080x4. When I do this, or use the actual byte count from the PNG data, the ATEM gets stuck and unresponsive to future uploads.
Any thoughts on what might be happening?
func uploadStill(at index: Int?, image: UIImage) {
	guard let slot = index,
		let resizedImage = self.resizeImage(image: image, targetSize: CGSize(width: 1920, height: 1080)),
		let pngData = resizedImage.pngData()
	else { return }

	let imageSize: CGSize = resizedImage.size
	let width = imageSize.width
	let height = imageSize.height

	let numBytes = UInt32(pngData.count)

	let yuvData = Media.encodeRunLength(rgbData: pngData)
	let numYuvDataBytes = yuvData.count

	let size: UInt32 = UInt32(width * height * 4 * resizedImage.scale)

	// controller should be defined outside of this method. Neither of these two methods work.

	controller.uploadStill(slot: UInt16(slot), data: yuvData, uncompressedSize: numBytes)

//	controller.uploadStill(slot: UInt16(slot), data: yuvData, uncompressedSize: size)
}

Hey Adam, I have no ATEM at my disposal anymore but maybe I can think along and help you.
Uncompressed size should be the number of bytes of a full resolution (depends on the resolution of your ATEM) uncompressed YUV image. (That is: Alpha1 Blue Lum1 Alpha2 Red Lum2, with 10bits for each color channel). This is the only format that the ATEM accepted at the time I wrote the code. Hence the size should always be targetResolution * 4.
I see that you are using pngData as a source to feed encodeRunLength(rgbData:). I don’t know what pngData exactly is but I suspect that it is the compressed PNG data, which is the wrong format. That function requires raw 8bit RGBA data. That is a long string of 32 bit values representing pixels, the pixels are described encoded as 4 consecutive 8bit color values: red, green, blue, alpha.

Thanks. This will point me in the right direction.
Follow up question. What is your plan for the code base now that you don’t have an Atem anymore? Aside from implementing more of the commands, were there sections that remained unfinished and in need of improvement?

I'm a software engineering student and I have close contacts with a broadcasting company. From time to time I get some equipment from them to take home and develop some software.
This is all done in my spare time. And it just happened so that for the moment I have no equipment at home. But I still intend to expand this library and to continue improve it.
The broadcasting company is using a lot of automation software that I wrote in javascript and runs in a nodeJS engine. This project is the start of a transition that I would like to make: from javascript to Swift.

were there sections that remained unfinished and in need of improvement?

These are some things that remain undone but that I would like to finish:

Merge your pull request ;)
Update the documentation
Add Codable support for the ATEM messages to make it more easy to add new messages and commands.
Use native buffers from SwiftNIO instead of [UInt8] arrays
Do some testing:

Add endurance tests using real hardware
Automated testing: test my simulator against the provided libraries from black magic design.

What are you using this library for? Do you already have something in production?

Been working on a paid iOS app to control Atem devices. Getting close (I hope) to release, but there’s a lot of features to support in these devices so the scope keeps increasing. I only have an Atem Mini Pro at the moment. The simulator has been useful to at least see how other features might be represented in my app.

I got this to work thanks to your points. The key part was making sure that the image is resized to fit and drawn into a 1920x1080 rectangle (or whatever the switcher is outputting). This image is then converted to RGBA data object which is then sent to the Media.encodeRunLength function.
Using this code to do the resizing:
func resizeImage(image: UIImage, targetSize: CGSize) -> UIImage? {
	let targetRect = CGRect(x: 0, y:0, width: targetSize.width, height: targetSize.height)
	let drawRect = AVMakeRect(aspectRatio: image.size, insideRect: targetRect)
	let format = UIGraphicsImageRendererFormat()

	format.opaque = false
	format.scale = 1.0
	format.preferredRange = .standard

	let renderer = UIGraphicsImageRenderer(size: targetSize, format: format)

	return renderer.image { (context) in
		image.draw(in: drawRect)
	}
}

and this UIImage extension to extract the pixel information:
extension UIImage {
	func pixelData() -> [UInt8]? {
		let size = self.size
		let dataSize = size.width * size.height * 4
		var pixelData = [UInt8](repeating: 0, count: Int(dataSize))
		let colorSpace = CGColorSpaceCreateDeviceRGB()
		let context = CGContext(data: &pixelData,
							width: Int(size.width),
							height: Int(size.height),
							bitsPerComponent: 8,
							bytesPerRow: 4 * Int(size.width),
							space: colorSpace,
							bitmapInfo: CGImageAlphaInfo.noneSkipLast.rawValue)
		guard let cgImage = self.cgImage else { return nil }
		context?.draw(cgImage, in: CGRect(x: 0, y: 0, width: size.width, height: size.height))

		return pixelData
	}
}


Confidence level

Hi,
Nice package!
I think it would be nice to add an example to docs or have a new feature for estimating the 95% confidence level by which the spectrum differ from white or red noise.
I found this post on Stack Overflow and would like to know the best way to do that using your package.

Thanks for using our package @iuryt :)
In Appendix E of this paper, we provide how to estimate the 95% confidence level based on the chi2 distribution: https://agupubs.onlinelibrary.wiley.com/doi/abs/10.1029/2021MS002692
Jupyter notebooks where I compute the confidence interval are available via Github doi:10.5281/zenodo.5563893 .

You can also estimate the confidence intervals via bootstrapping

Possibly useful: xbootstrap


use folders instead of /.cloned dependency

that's what actually gets created when cloning
will always be older than the content

Let's not merge this until the dlang.org autotester is fixed.
https://github.com/D-Programming-Language/dmd/pull/4923

OK, let's try it.

Tried a clean build, seems to work!
(aside from demanding that LATEST is specified on the command line, we should get rid of that some day)


<#497404618679123978> error

📢 Bug reported by Profxy<PHONE_NUMBER>30229761)
What is the title of your bugreport?
<#497404618679123978> error
How can you reproduce the bug?
if a role get assigned / removed the name of the role is not visible in the log. <#497404618679123978>
Which result would normally have to be?
it should be Role assigned! :paperclip: Member: Profxy#5396<PHONE_NUMBER>30229761) :inbox_tray: Role: Giveaways 08.09.2019
but it is
Role removed! :paperclip: Member: Profxy#5396<PHONE_NUMBER>30229761) heute um 22:10 Uhr now.
Comments:
❗✅ Dadi: could be reproduced

https://github.com/LenoxBot/LenoxBot/commit/7d4818e6341daa6fbd3af6e83988fa5593b7151f


cnocr_train.py训练，accuracy一直是0

使用crnn-mxnet的Synthetic Chinese Dataset样本，执行
python ./cnocr-master/scripts/cnocr_train.py --loss ctc --dataset cn_ocr --data_root ./data/images --train_file ./data/train.txt --test_file ./data/test.txt
cnocr_train/cnocr-master# proc 0 started
proc 1 started
proc 2 started
proc 3 started
proc 0 started
proc 1 started
[16:56:12] src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
2019-05-29 16:56:46,983 Epoch[0] Batch [0-50]   Speed: 199.47 samples/sec       accuracy=0.000000
2019-05-29 16:57:30,919 Epoch[0] Batch [50-100] Speed: 145.66 samples/sec       accuracy=0.000000
2019-05-29 16:58:17,541 Epoch[0] Batch [100-150]        Speed: 137.27 samples/sec       accuracy=0.000000
2019-05-29 16:59:03,438 Epoch[0] Batch [150-200]        Speed: 139.44 samples/sec       accuracy=0.000000
2019-05-29 16:59:51,143 Epoch[0] Batch [200-250]        Speed: 134.16 samples/sec       accuracy=0.000000
2019-05-29 17:00:39,957 Epoch[0] Batch [250-300]        Speed: 131.11 samples/sec       accuracy=0.000000
2019-05-29 17:01:13,673 Epoch[0] Batch [300-350]        Speed: 189.82 samples/sec       accuracy=0.000000
2019-05-29 17:01:56,561 Epoch[0] Batch [350-400]        Speed: 149.23 samples/sec       accuracy=0.000000
2019-05-29 17:02:39,406 Epoch[0] Batch [400-450]        Speed: 149.37 samples/sec       accuracy=0.000000
2019-05-29 17:03:24,134 Epoch[0] Batch [450-500]        Speed: 143.09 samples/sec       accuracy=0.000000
2019-05-29 17:04:08,365 Epoch[0] Batch [500-550]        Speed: 144.69 samples/sec       accuracy=0.000000
2019-05-29 17:04:52,112 Epoch[0] Batch [550-600]        Speed: 146.30 samples/sec       accuracy=0.000000
2019-05-29 17:05:40,416 Epoch[0] Batch [600-650]        Speed: 132.49 samples/sec       accuracy=0.000000
2019-05-29 17:06:27,831 Epoch[0] Batch [650-700]        Speed: 134.98 samples/sec       accuracy=0.000000
2019-05-29 17:07:03,921 Epoch[0] Batch [700-750]        Speed: 177.34 samples/sec       accuracy=0.000000
2019-05-29 17:07:47,872 Epoch[0] Batch [750-800]        Speed: 145.62 samples/sec       accuracy=0.000000
2019-05-29 17:08:34,820 Epoch[0] Batch [800-850]        Speed: 136.32 samples/sec       accuracy=0.000000
2019-05-29 17:09:24,825 Epoch[0] Batch [850-900]        Speed: 127.99 samples/sec       accuracy=0.000000
2019-05-29 17:10:00,173 Epoch[0] Batch [900-950]        Speed: 181.06 samples/sec       accuracy=0.000000
2019-05-29 17:10:43,914 Epoch[0] Batch [950-1000]       Speed: 146.32 samples/sec       accuracy=0.000000
2019-05-29 17:11:29,664 Epoch[0] Batch [1000-1050]      Speed: 139.89 samples/sec       accuracy=0.000000
2019-05-29 17:12:18,869 Epoch[0] Batch [1050-1100]      Speed: 130.07 samples/sec       accuracy=0.000000
2019-05-29 17:12:54,773 Epoch[0] Batch [1100-1150]      Speed: 178.25 samples/sec       accuracy=0.000000
2019-05-29 17:13:45,715 Epoch[0] Batch [1150-1200]      Speed: 125.63 samples/sec       accuracy=0.000000
2019-05-29 17:14:16,195 Epoch[0] Batch [1200-1250]      Speed: 209.97 samples/sec       accuracy=0.000000
2019-05-29 17:14:58,715 Epoch[0] Batch [1250-1300]      Speed: 150.52 samples/sec       accuracy=0.000000
2019-05-29 17:15:41,078 Epoch[0] Batch [1300-1350]      Speed: 151.08 samples/sec       accuracy=0.000000
2019-05-29 17:16:25,221 Epoch[0] Batch [1350-1400]      Speed: 144.98 samples/sec       accuracy=0.000000
2019-05-29 17:17:09,735 Epoch[0] Batch [1400-1450]      Speed: 143.78 samples/sec       accuracy=0.000000
2019-05-29 17:17:57,844 Epoch[0] Batch [1450-1500]      Speed: 133.03 samples/sec       accuracy=0.000000
2019-05-29 17:18:35,149 Epoch[0] Batch [1500-1550]      Speed: 171.56 samples/sec       accuracy=0.000000
2019-05-29 17:19:22,321 Epoch[0] Batch [1550-1600]      Speed: 135.67 samples/sec       accuracy=0.000000
2019-05-29 17:19:57,424 Epoch[0] Batch [1600-1650]      Speed: 182.32 samples/sec       accuracy=0.000000
2019-05-29 17:20:38,650 Epoch[0] Batch [1650-1700]      Speed: 155.24 samples/sec       accuracy=0.000000
2019-05-29 17:21:23,728 Epoch[0] Batch [1700-1750]      Speed: 141.98 samples/sec       accuracy=0.000000
2019-05-29 17:22:11,530 Epoch[0] Batch [1750-1800]      Speed: 133.89 samples/sec       accuracy=0.000000
2019-05-29 17:22:52,154 Epoch[0] Batch [1800-1850]      Speed: 157.54 samples/sec       accuracy=0.000000
2019-05-29 17:23:38,767 Epoch[0] Batch [1850-1900]      Speed: 137.30 samples/sec       accuracy=0.000000
2019-05-29 17:24:13,728 Epoch[0] Batch [1900-1950]      Speed: 183.07 samples/sec       accuracy=0.000000
2019-05-29 17:24:59,449 Epoch[0] Batch [1950-2000]      Speed: 139.98 samples/sec       accuracy=0.000000
2019-05-29 17:25:45,785 Epoch[0] Batch [2000-2050]      Speed: 138.12 samples/sec       accuracy=0.000000
2019-05-29 17:26:28,279 Epoch[0] Batch [2050-2100]      Speed: 150.61 samples/sec       accuracy=0.000000

遇到同样的情况

@naygnol @kevinchen1223 是之前的版本有bug，v1.0.0已修复，欢迎试用


Distributed cache topic UE pass

.

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

ID: 0d01025d-86b2-bb2d-86c1-ef0695bc98e3
Version Independent ID: 5b9a6572-3671-0d54-b2ef-83d04f8b3e96
Content: Work with a distributed cache in ASP.NET Core
Content Source: aspnetcore/performance/caching/distributed.md
Product: aspnet-core
GitHub Login: @ardalis
Microsoft Alias: riande

@Tratcher Can u give me a tip here ...
The current topic+sample goes with a ConfigureDevelopmentServices, ConfigureStagingServices, and ConfigureProductionServices. I get it, but showing devs too many ways of doing things ... not being opinionated enough ... is making this (and other topics) too complicated imo for devs coming to Core for the first time. If the environment is set on a property in ConfigureAppConfiguration or injected into Startup for a local var, we could use ConfigureServices with a conditional for these environmental caching configurations.
Should I retain the barely explained/rarely seen Configure{Environment}Services approach, or go with an environment local var or property and conditional? If the latter, can we look down the road to the Generic Host for guidance on what to show? Shouldn't we show the following approach ... the Nutjob Pattern:tm: :smile: [and given that CreateDefaultBuilder isn't a thing (yet) for the Generic Host ... you said something like it might be built later; let's make my example here for Web Host] ...
public static IHostingEnvironment Environment { get; set; }

public static IWebHostBuilder BuildWebHostBuilder(string[] args) =>
    WebHost.CreateDefaultBuilder(args)
        .ConfigureAppConfiguration((hostingContext, config) =>
        {
            Environment = hostingContext.HostingEnvironment;
        })
        .ConfigureServices(services =>
        {
            if (Environment.IsDevelopment())
            {
                // Development
                services.AddDistributedMemoryCache();
            }
            else
            {
                // Staging/Production/Whatever
                services.AddDistributedSqlServerCache(options =>
                {
                    options.ConnectionString =
                        @"Data Source=(localdb)\v11.0;Initial Catalog=DistCache;" +
                        @"Integrated Security=True;";
                    options.SchemaName = "dbo";
                    options.TableName = "TestCache";
                });
            }
        }
        ...

Whatever we do with examples for environmental service registrations, I think we should do it one way (the most common way/the recommended way/the simplest way) across the docs.

Call the overload of ConfigureServices that gives you the HostingContext.

public static IWebHostBuilder BuildWebHostBuilder(string[] args) =>
    WebHost.CreateDefaultBuilder(args)
        .ConfigureServices((hostContext, services) =>
        {
            if (hostContext.HostingEnvironment.IsDevelopment())
            {
                // Development
                services.AddDistributedMemoryCache();
            }
            else
            {
                // Staging/Production/Whatever
                services.AddDistributedSqlServerCache(options =>
                {
                    options.ConnectionString =
                        @"Data Source=(localdb)\v11.0;Initial Catalog=DistCache;" +
                        @"Integrated Security=True;";
                    options.SchemaName = "dbo";
                    options.TableName = "TestCache";
                });
            }
        }
        ...

Lovely. :shipit:

@Tratcher One more ❓ ...
The current orders (AFAIK) from management (DE?, DR?) is that we are to use a Startup class for all samples (except for the Generic Host sample). I even created a few repo samples in ancient times (a year or two ago :smile:) using the extension methods approach before I was ordered to go with a Startup class everywhere.
You remarked briefly on one of the issues (I think a Generic Host discussion) that moving to the extension methods everywhere might be a good alternative ... or under consideration as a recommendation ... or something along those lines.
Has there been a ruling yet to go away from Startup classes and start using the extension methods everywhere in samples? ... or is that under discussion?
I ask because if management has said 'make it happen,' then I'd like to go ahead here with the extension methods (:heart:) for this Distributed Cache sample and other samples that I'll be working on in the coming weeks.

Hold off, we're revisiting this in 3.0 as part of moving WebHost onto GenericHost.

Ok, thanks.


github publish: some markup conversion failures

I just used a fairly complex GH issue (that I had written on GH) to test POSSE-ing to a test repo:
https://www.svenknebel.de/posts/2018/11/8/ to https://github.com/sknebel/random-test-repo/issues/1
The HTML in my post is a cleaned up version of Githubs HTML (with mentions of users and other issues removed to cut down the noise)
The following things in the created issue were unexpected:

the nested lists didn't convert correctly
< > were added around bare links
in the "output format" section, a space was added before the italicized "not")
the JSON code example was cut, but I had forgotten to escape a < - the browser still displayed the code following, probably because <------ clearly wasn't valid HTML tag, but it is understandable bridgy (or maybe even mf2py?) failed there (I have since edited the post to use a <)

EDIT: feel free to move this issue to granary or ask me to split it up or ... - happy to help you as much as I can.

hey, thanks for the report! yeah, converting HTML to markdown will often be imperfect, and mostly at the mercy of html2text, but i can take a look!

Just tested: lxml and mf2py handle the <----------- correctly (and escape the < in the html output of the e-content), which makes it surprising it doesn't make it through.

It seems the nested list is something where the original markdown implementation and those based on it accept html2text's output (the markdown documentation doesn't appear to describe nested lists at all), but CommonMark, on which GitHub's markdown support is based, specified it explicitly in a way that requires a deeper indentation. Its specification has a section on this history: https://spec.commonmark.org/0.28/#motivation

Looks like the space before __not__ is this html2text bug: https://github.com/Alir3z4/html2text/issues/324

...and the two spaces indent for lists is hard coded here: https://github.com/Alir3z4/html2text/blob/296e6f24d16a36bf88b8042d56ebd69ec37aef9c/html2text/init.py#L602

I've filed https://github.com/Alir3z4/html2text/issues/344 for the list bug.

fixed! the first three at least, if not the <------ one. thanks for your patience!


Update to permissions requested by APP

This is the screenshot that needs to be updated:

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@anwara-ms


Cherry-pick 1736 and 1740 to develop

fix(host-devices): extend allowed major list

Extends major list with the Local/Experimental 240-254 range and 255 reserved.

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

fix: invalid error code on locked resource

Return aborted rather than already exists...

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge


Add support for python 3.12

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

Comparison is base (68e3bb2) 100.00% compared to head (687017a) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #220   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           69        69
  Lines         1689      1689
  Branches       177       177
=========================================
  Hits          1689      1689

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


cookieplone does not accept a project name that exists of only one word

cookieplone only accepts project names with multiple words. Otherwise there is a traceback.  For example a project name plone6test is not valid.
 -> Setup Backend
Traceback (most recent call last):
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/cookieplone/generator.py", line 56, in generate
    result = cookiecutter(
             ^^^^^^^^^^^^^
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/cookiecutter/main.py", line 161, in cookiecutter
    prompt_for_config(context_for_prompting, no_input)
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/cookiecutter/prompt.py", line 283, in prompt_for_config
    cookiecutter_dict[key] = render_variable(env, raw, cookiecutter_dict)
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/cookiecutter/prompt.py", line 224, in render_variable
    return template.render(cookiecutter=cookiecutter_dict)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/Users/fred/.local/pipx/venvs/cookieplone/lib/python3.12/site-packages/cookieplone/filters/__init__.py", line 14, in package_name
    return v.split(".")[1]
           ~~~~~~~~~~~~^^^
IndexError: list index out of range

same with Cookieplone 0.8.0
A tripled namespace test.plone.something results in
+ /home/astro/Plone6/Test/test-plone-something/backend/.venv/bin/uv pip install -r requirements-mxdev.txt
error: Build backend failed to determine requirements with `build_editable()` (exit status: 1)

[stderr]
error in test.plone.kwk setup command: Distribution contains no modules or packages for namespace package 'test.plone'
make[2]: *** [Makefile:69: build-dev] Error 2
make[2]: Leaving directory '/home/astro/Plone6/Test/test-plone-something/backend'
make[1]: *** [Makefile:63: backend-install] Error 2
make[1]: Leaving directory '/home/astro/Plone6/Test/test-plone-something'
make: *** [Makefile:89: install] Error 2

@acsr The fix for this was just merged today in https://github.com/plone/cookieplone-templates/pull/86 -- please try again

THX here as well. works!


bunzip2 compressed file ends unexpectedly error

Attempting to run apt-cyg update results in the following error:
--2019-11-22 14:06:37--  http://mirror.datacenter.by/pub/mirrors/cygwin//x86_64/setup.bz2
Resolving mirror.datacenter.by (mirror.datacenter.by)... <IP_ADDRESS>, 2a02:2208:1:3::12
Connecting to mirror.datacenter.by (mirror.datacenter.by)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 304 Not Modified
File ‘setup.bz2’ not modified on server. Omitting download.
bunzip2: Compressed file ends unexpectedly;
perhaps it is corrupted?  Possible reason follows.
bunzip2: No such file or directory
Input file = setup.bz2, output file = setup
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bunzip2: Deleting output file setup, if it exists.
mv: cannot stat 'setup': No such file or directory
Updated setup.ini

hi, I had same problem like you, just remove your cygwin cache dir ( in installer 'local package directory' ) and rerun update :)


Rename secure channel create commands

Currently we have:
ockam secure-channel create connector

and
ockam secure-channel create listener

We want to change it to:
ockam secure-channel create

and
ockam secure-channel create-listener

where ...create connector is changed to ...create and create listener is changed to create-listener
https://github.com/build-trust/ockam/blob/develop/implementations/rust/ockam/ockam_command/src/secure_channel/create.rs

@mrinalwadhwa I'd like to take a shot at this one, if that's ok?

@tmuro17 👋 that would be awesome, please do.

added in https://github.com/build-trust/ockam/pull/3062


const constructor support for fixed size strings

I'm currently facing a challenge with using the tstr and by extension the strN types in const contexts in a situation where I need to store default prefixes for further processing; Looking at the code in tiny_internal.rs it should be possible to refactor this to turn make into a const fn.
It should be relatively simple with a loop similar to the one commented out already. Would a PR changing either make or create, or adding a const variant of those functions be accepted to allow for const contexts?

I've just published version 0.5.5, which has const constructors for several of the fixed string types, including tstr.  I added new constructors and the left the original ones in place because I can't call the copy_from_slice function, which is recommended by the Rust performance lints, inside a const function. Thus the original ones should still be better when called from a non-const context. In addition, I've also made the .len() and new() functions const, so the following is now possible:
const C:str16 = str16::const_make("abcd");
let A = [0u8;C.len()];

When I have more time I may make some of the other functions const.

Absolutely amazing! Made a fork yesterday to prepare for potential PRs, but it seems like that won't be necessary then.
Other functions being turned const is amazing too, thanks a lot!


Render multiple sequences

Hi! I would like to know if there’s the possibility to render multiple sequences automatically, instead of going one by one as it would save a lot of time. I’ve tried to create a python script but it’s impossible to run the plug in with it. Thanks!

Hi! There's any news about this? I'm also trying to render multiple sequencers at once so i can automatize the process.

Hi, sorry I missed the question.
Currently, there is no built-in support for this, but it would probably be a relatively simple change.
E.g. just allowing the submission of an array of sequences for rendering instead of only a single one.
I hope I'll find time for it this week.

Unfortunately, this proved to be a challenge, I was not able to reverse-engineer UE's array property view.
I hope I'll get back to this at some point.


[AD-681] Add all_prices method to variant decorator

What problem is the code solving?

We add this new method to return variant prices information in a way that is useful for then indexing these variants in Algolia.

How does this change address the problem?

Returning variant price information for each country.

Why is this the best solution?
Share the knowledge

Closing this PR because these changes were added in mejuri-web.


[API] v3 Payments

API v3
sendInvoice
[source]

[x] Add tests.
[x] Generate documentation.
[x] Run tests.

answerShippingQuery
[source]

[x] Generate documentation.

answerPreCheckoutQuery
[source]

[x] Generate documentation.

Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
— https://core.telegram.org/bots/api-changelog#may-18-2017
Renamed the fields new_chat_participant and left_chat_participant of the Message object to new_chat_member and left_chat_member.
— https://core.telegram.org/bots/api-changelog#april-9-2016

This might be a non-issue really. But how should we ensure we do not do something unexpected by the user. Should we provide "polyfills" on top, to hide the API updates (until we decide to bump major!), that allow the library to work as expected; emit the expected events?

@GochoMugo This seems ok.

@yagop You'll need to add the Payments provider token, i.e. TEST_PROVIDER_TOKEN for this to fix our tests.


Integrate new pydicom DS formatting

As noted in #57, highdicom currently produces datasets with invalid decimal strings in many situations. The functionality to correctly format DSs is now integrated into pydicom, see https://github.com/pydicom/pydicom/pull/1334.
This PR integrates this behaviour into highdicom wherever it sets a value for a DS attribute.
Important this depends upon behaviour on pydicom master branch that will be in the next release of pydicom, which will be 2.2.0. I have updated setup.py to reflect this. This PR should not be merged until such a time that pydicom 2.2.0 is released and available on pypi. Tests will also fail until that time, but they do pass on my local machine when I have pydicom installed from master branch.

This replaces #57

Merged into dev branch to integrate into #93


out-of memory build jupyter lab

Error: Can't resolve '@mui/material/Box'
[webpack-cli] ModuleNotFoundError: Module not found: Error: Can't resolve '@mui/material/Box' in '/home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@jupyter_vre/components/lib'
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/Compilation.js:1768:28
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:742:13
    at eval (eval at create (/home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:276:22
    at eval (eval at create (/home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:405:22
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:119:11
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:650:24
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:813:8
    at /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:933:5
resolve '@mui/material/Box' in '/home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@jupyter_vre/components/lib'
  Parsed request is a module
  using description file<EMAIL_ADDRESS>(relative path: ./lib)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@jupyter_vre/components/lib/node_modules doesn't exist or is not a directory
      looking for modules in /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@jupyter_vre/components/node_modules
        /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@jupyter_vre/components/node_modules/@mui/material doesn't exist
      /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@jupyter_vre/node_modules doesn't exist or is not a directory
      /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/node_modules doesn't exist or is not a directory
      looking for modules in /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules
        /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/staging/node_modules/@mui/material doesn't exist
      /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/lab/node_modules doesn't exist or is not a directory
      /home/justmingo/anaconda3/envs/rclone-data-mounter/share/jupyter/node_modules doesn't exist or is not a directory
      /home/justmingo/anaconda3/envs/rclone-data-mounter/share/node_modules doesn't exist or is not a directory
      /home/justmingo/anaconda3/envs/rclone-data-mounter/node_modules doesn't exist or is not a directory
      /home/justmingo/anaconda3/envs/node_modules doesn't exist or is not a directory
      /home/justmingo/anaconda3/node_modules doesn't exist or is not a directory
      looking for modules in /home/justmingo/node_modules
        /home/justmingo/node_modules/@mui/material doesn't exist
      /home/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[LabBuildApp] JupyterLab failed to build
[LabBuildApp] Traceback (most recent call last):

Maybe retry to scap the environment

Scrapped the environments with for i in conda env list|awk '{print $1}'|egrep -v 'base|#'|tr '\n' ' ';do echo $i;conda env remove --name $i;done
Cleaned with make purge
Checked every dependency in main package.json was also in /packages/data-mounter/package.json


[Event Request] codeunit 90 "Purch.-Post"

Please add OnPostInvoiceOnBeforePostLedgerEntry event in function PostInvoice
 local procedure PostInvoice(var PurchHeader: Record "Purchase Header")
    var
        TotalAmount: Decimal;
        IsHandled: Boolean;
    begin
        IsHandled := false;
#if not CLEAN19
        OnBeforePostGLAndVendor(PurchHeader, TempInvoicePostBuffer, PreviewMode, SuppressCommit, GenJnlPostLine, IsHandled);
#endif
        OnBeforePostInvoice(PurchHeader, PreviewMode, SuppressCommit, GenJnlPostLine, IsHandled);
        if IsHandled then
            exit;

        with PurchHeader do begin
            // Post purchase and VAT to G/L entries from buffer
#if not CLEAN19
            if UseLegacyInvoicePosting() then
                PostInvoicePostingBuffer(PurchHeader, TotalAmount)
            else begin
#endif
            GetInvoicePostingParameters();
            InvoicePostingInterface.SetParameters(InvoicePostingParameters);
            InvoicePostingInterface.SetTotalLines(TotalPurchLine, TotalPurchLineLCY);
            InvoicePostingInterface.PostLines(PurchHeader, GenJnlPostLine, Window, TotalAmount);
#if not CLEAN19
            end;
#endif

            // Check External Document number
            if PurchSetup."Ext. Doc. No. Mandatory" or (GenJnlLineExtDocNo <> '') then
                CheckExternalDocumentNumber(VendLedgEntry, PurchHeader);
//NEW EVENT
            IsHandled := false;
            OnPostInvoiceOnBeforePostLedgerEntry(PurchHeader, GenJnlPostLine, Window, HideProgressWindow, TotalPurchLine, TotalPurchLineLCY, InvoicePostingInterface, InvoicePostingParameters, IsHandled);
            If IsHandled then
                exit;
//NEW EVENT
            // Post vendor entries
            if GuiAllowed and not HideProgressWindow then
                Window.Update(4, 1);
...

    [IntegrationEvent(false, false)]
    local procedure OnPostInvoiceOnBeforePostLedgerEntry(var PurchaseHeader: Record "Purchase Header"; var GenJnlPostLine: Codeunit "Gen. Jnl.-Post Line"; var Window: Dialog; HideProgressWindow: Boolean; var TotalPurchLine: Record "Purchase Line"; var TotalPurchLineLCY: Record "Purchase Line"; var InvoicePostingInterface: Interface "Invoice Posting"; var InvoicePostingParameters: Record "Invoice Posting Parameters"; var IsHandled: boolean);
    begin
    end;

Sorry, we cannot make this kind of change, as this is breaking change for others. We should not use handled event with exit in the middle of procedure. If you extension exit, next events in same procedure will not be invoked.
Please provide more details about your project and why do you need handled event here.

We need it in order to post Vendor entries and Balance entries inside a loop.
If OnBeforePostInvoice changed to this would be ok ?
OnBeforePostInvoice(PurchHeader, PreviewMode, SuppressCommit, GenJnlPostLine,TotalPurchLine, TotalPurchLineLCY,InvoicePostingInterface, IsHandled);

I am closing this and open an new issue https://github.com/microsoft/ALAppExtensions/issues/16115
with request to change existing event OnBeforePostInvoice


[FLINK-33330] Update zookeeper to 3.7.2, 3.8.3 to address CVE-2023-44981

There is CVE-2023-44981 which is addressed by this PR

thanks for taking a look


I want to be able to adjust to the height and width automatically, but I can't find any way.

I want to be able to adjust to the height and width automatically, but I can't find any way.

I hope I can fix the height, but I can't find any way


"The code-style analysis feature is experimental and may change" message seems out of date.

The page says The code-style analysis feature is experimental and may change between the .NET 5 and .NET 6 releases. Now that .NET 6 is released, is it safe to remove this? Perhaps it should be updated?

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

ID: f8906b2c-b984-0427-d064-829e7ea2fc55
Version Independent ID: 128f9903-971d-6a66-a2cb-9b12acbc55e7
Content: Code analysis in .NET
Content Source: docs/fundamentals/code-analysis/overview.md
Product: dotnet-fundamentals
GitHub Login: @gewarren
Microsoft Alias: gewarren

cc @mavasani

@jmarolf @mikadumont

Would be nice if this notice could be updated to give readers confidence and clarity in using code style analysis.


multiple debuggers can be registered with the same type

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

VS Code Version: 1.57.1
OS Version: Windows

Description:
In Extension API doc, above the function  registerDebugAdapterDescriptorFactory(), It says that "Registering more than one DebugAdapterDescriptorFactory for a debug type results in an error." But that error doesn't pop up when two debugger with same type are registered.
Steps to Reproduce:

install any debugger extension (like cpptools)
package and install my own debugger extension with same type "cppdbg" (if my own extension is launched directly, that error will pop up correctly, the only way to reproduce is to install from .vsix)
two extensions are both activated successfully without error
when launch a debug with type "cppdbg", the actual debugger used is my own extension

Expectation:
No matter what circumstance, that error should pop up. Right now we have two extensions with same debug type, and we rely on this mechanism to force our custumers to migrate from the old one to the new one. Without this error, our custumers would install both extensions and only the old one would be used.

There seems to be code that is handling this here https://github.com/microsoft/vscode/blob/main/src/vs/workbench/api/common/extHostDebugService.ts#L335
For now leaving this up to @weinand since he added that code.
Feel free to assign back to me if you would like me to investigate more.

Moving out to backlog since we do not plan to tackle this in Endgame.


inputFieldAccessoryView with ContainerView (with UIViewController)  problem

Hi,
You can download example project here: https://goo.gl/iLtxY5
Issue reproduce steps;
1- Run project
2- Add one or more tag
3- Select one tag and delete it.
Error; 'UIViewControllerHierarchyInconsistency', reason: 'child view controller should have parent view controller:<UICompatibilityInputViewController: 0x7fc56dd4eca0> but actual parent is...
I read a lot of documents but i can't find solution.

@hamzauzumcu Thanks. I will take a look.

@ricardopereira Did you solve the issue?

@hamzauzumcu Not yet sorry. Is this blocking you?

Yes, i cant continue to develop the app

@hamzauzumcu That error happens when you the keyboard is showing?

Closed because of inactivity. If the problem persists, feel free to reopen the issue. Thanks.


Project not compatible with recent Grunt?

I tried to install Grunt (thought npm), and I cant get grunt working for the project. The most obvious thing is that the grunt-file should now be called Gruntfile.js instead of grunt.js; fine enough. But when I try to rename it, it seems Grunt won't recognize any of the tasks:
$ grunt
Warning: Task "concat lint min" not found. Use --force to continue.

Aborted due to warnings.

Fixed upstream


Getting Error: Cannot find module 'cypress-mochawesome-reporter/plugin' when i run cypress in docker

I have created a docker file that contains the below line of code.

FROM cypress/base:14.19.0
RUN mkdir /legrande-cypress
WORKDIR /legrande-cypress
COPY ./package.json .
COPY ./cypress.json .
COPY ./cypress  ./cypress
RUN npm install
ENTRYPOINT ["npx","cypress","run"]

When I run cypress test using docker run -i -v "%cd%":/legrande-cypress -t cypress-image:latest --spec cypress/integration/examples/*.js it will throwes an error below.

Error: Cannot find module 'cypress-mochawesome-reporter/plugin'

Require stack:

- /legrande-cypress/cypress/plugins/index.js

- /root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js

- /root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/lib/plugins/child/index.js

    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)

    at Function.Module._load (internal/modules/cjs/loader.js:746:27)

    at Module.require (internal/modules/cjs/loader.js:974:19)

    at require (internal/modules/cjs/helpers.js:101:18)

    at module.exports (/legrande-cypress/cypress/plugins/index.js:22:3)

    at /root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js:94:12

    at tryCatcher (/root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/util.js:16:23)

    at Function.Promise.attempt.Promise.try (/root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/method.js:39:29)

    at load (/root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js:91:7)

    at EventEmitter.<anonymous> (/root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js:209:5)

    at EventEmitter.emit (events.js:400:28)

    at process.<anonymous> (/root/.cache/Cypress/9.5.1/Cypress/resources/app/packages/server/lib/plugins/util.js:19:22)

    at process.emit (events.js:400:28)

    at emit (internal/child_process.js:912:12)

    at processTicksAndRejections (internal/process/task_queues.js:83:21)```

Hello, I am not an expert but can you please cross-check if you have added the below dependencies in your package.json.
"mocha": "^8.2.1",
"cypress-commands": "^1.1.0",
"mochawesome": "^6.2.1",
"mochawesome-merge": "^4.2.0",
"mochawesome-report-generator": "5.1.0"

Yes, I have added it to my package.json file. You can check below.

Sorry for the late reply. Are things running fine outside docker ? Are you able to generate a report when you execute Cypress commands directly?

Hi, @vaibsaraswat Thank you for giving a wonderful time. I am not using docker. I am running on my local machine. and also able to generate reports.

I am seeing the same error while running in AWS Code pipeline. Its working fine in my local machine.

I am seeing the same error while running in AWS Code pipeline. Its working fine in my local machine.

Do you find a solution for this ?

The original error was reported on a version of Node.js (cypress/base:14.19.0) which is no longer supported.
The error looks like a configuration problem and not a problem with the Docker image

I am closing this now. If there is a similar issue with a current version of a Cypress Docker image and you think it is a bug in the Docker image, please open a new issue.
Usage issues can be discussed in the Cypress technical community on Discord
 (click on button)


Removed 'run' command as it no longer necessary after creation of 'en…

…v' command

Need to update conf/.gitignore

Update conf/.gitignore in f57437d02c

+1


Skip script chance logic providers if their spawn chance is zero

HDMod was having big issues with level loading times, turns out it was due to script procedural chances still being run when they were set to zero, with this change, average level loading changes got ~5x times better on it. It should be around the same on most small scripts.
Also, should I make the same change to community chances? I guess it would make sense

Any opinions or updates on if this is gonna get merged?
Should I not use a different vector to store the enabled chances? Maybe just checking the chance in handle_chance and not running the provider.is_valid if the chance is zero would be performant enough?

Any opinions or updates on if this is gonna get merged?

Oh right, in my headcanon I had twisted your earlier statement about community chances as something you still want to add to this, and maybe we should if that's also a big performance issue.

Should I not use a different vector to store the enabled chances? Maybe just checking the chance in handle_chance and not running the provider.is_valid if the chance is zero would be performant enough?

Well if this was a big performance issue, whatever sounds like the most performant choice, it's not that much memory wasted. I'm not very familiar with this part of the api and can't really think what kind of a hit it would have compared to this.

I haven't tested how the community chances affect the performance, probably less than script chances since it's with compiled code. But still, running checks to verify a spot is valid for spawning a thing when it's definitely not going to spawn anywhere, seems like a waste...

Also, a very weird case where this optimization could cause a bug, is if someone decides to change a chance from 0 to higher, inside an is_valid or do_spawn function by using the PostRoomGenerationContext:new() to access the chance. Though seems very specific and you could already expect not everything to work by using PostRoomGenerationContext outside of the callback made for it.
To me this maybe bug seems seems justifiable due to my statement right above, idk what you think.

Also, a very weird case where this optimization could cause a bug, is if someone decides to change a chance from 0 to higher, inside an is_valid or do_spawn function by using the PostRoomGenerationContext:new() to access the chance. Though seems very specific and you could already expect not everything to work by using PostRoomGenerationContext outside of the callback made for it. To me this maybe bug seems seems justifiable due to my statement right above, idk what you think.

there is sol::no_constructor if you don't want people to be able to construct object

there are some valid use cases of constructing it tho, like cells_interlinked.lua has to use it since it stops the POST_ROOM_GENERATION callback from even happening

Yeah I specifically added the constructor for it since we put too many good functions behind it, but it's still not a very convenient way to use those functions outside the callback. There were a lot less callbacks when it was made.

I tried not using a vector to store enabled chances, and just check if the chance was not zero before the valid checks... Turns out it was actually more performant than the one using the vector, so I deleted the other commit and made a new one, this should be the final one
Also, adding the optimization to community chances made a change of time spent on procedurals spawn, from previously ~0.01s to ~0.0015s (tested on dwellings), I guess more than x5 faster, but very small change


Update fast_gradient.py with comments

Description
Please include a summary of the change, motivation and which issue is fixed. Any dependencies changes should also be included.
Fixes # (issue)
Type of change
Please check all relevant options.

[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.

[ ] Test A
[ ] Test B

Test Configuration:

OS
Python version
ART version or commit number
TensorFlow / Keras / PyTorch / MXNet version

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Hi @lea4n Thank you for using ART and your contribution. Please apologise the delayed response. I think we need to change the merge target from branch master to branch dev. I tried to do it but it seem that your local branch has been forked from branch master. Could you please move your commit 4c4a758faf71b31ad4cc8b3ec7cf42925c5885f7 to your updated branch dev and update this pull request?

I have included the requested changes in #180


Node 16 Update Required By June 14th

Github is turning off Node 12 support and Actions need to be updated to Node 16 by June 14th. If not updated, this action will stop working.
This is the current issue returned to us when this runs:

assign_reviewers
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: uesteibar/reviewer-lottery@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Sorry it was not raised sooner, this one slipped through our cracks with others that we were dealing with.

Done and published as v3, thanks for the heads up!

@uesteibar You're amazing. Thanks so much, updating this week!


Langfuse: add invocation_context to identify traces

WIP, used to demonstrate a possible solution to https://github.com/deepset-ai/haystack-core-integrations/issues/916

Any estimate on when this could be merged?

Do you find this PR useful @ggdupont ? Can you tell us a bit about your use case please?

I want (at least) to track session id accross calls to the llm just like the original issue. Later I also plan to add conversation metrics for performance monitoring. All should be ligh weigths and simple type metadata so the "invocation_context" seems quite perfect for this.

Ok thank you @ggdupont I agree and it seems like a low impact high return PR. Let's see what the peer review says

@silvanocerza please have a look as well and luk your thoughts.

ping @silvanocerza - have a look now 🙏

FYI already integrated and happy of the result.


Zone dependent Name resolution

I have a hybrid cloud scenario with zone east and zone west where each zone is running on a own paas that does outbound discovery by DNS Name resolution using a router component.  Discovery is done with zone affinity in each cloud west or east or if no server found by discovery in other regions zone using peered eureka in each region.
In case if discovery on same zone the extra hop vua the router that resolves discovered global unique  FQDN (Wan) is to expensive. Instead I want to use for  a connection to targets in same Zone the lan ipadress instead of the global Wan FQDN.
The only idea I have is to implement a selection in ribbon basd on own with target zone match, that uses either VIP or up address.

Maybe related to https://docs.google.com/document/d/1Kix6QzXn8Q2Rbgdl97S4E6xsHUTSfKUQJKrBv7JzAVc/edit?usp=drivesdk

Is the problem here that you want to register with the FQDN to support the cross region communication but only want that used in that scenario.  Otherwise when making a request to an app in the same region you want to use the VIP instead?

So you essentially want Ribbon to be smart and choose the correct one?

Yes, the calle check if the callee is on same zone (could be done by comparing the zone field i think). What is needed is a address the DiscoveryClient register the mciroservice for a local route (same zone) and one that can be used for same region (outside same PCF) , what will be mostly a global dns name or wan address

There is partly a solution (https://content.pivotal.io/isolation-segments/6-ways-pivotal-cloud-foundry-1-10-improves-your-security-posture , https://content.pivotal.io/blog/building-spring-microservices-with-cloud-foundrys-new-container-networking-stack ) which allows to register a micoservice running on PCF/PWS with its local ip address (instead of public route) which allows combined with container to container networking since PCF 1.10 to have a direct communication setup between direct registered application/microservices in same PCF instance(local access route using overlay IP). However if i want that the same microservice should be accessed also from outside, e.g. all same zone app instances are no healthy and ribbon wants to choose an instance which runs on the "other" pcf instance in the "other" cloud, there is no "overlay network" spaned in between and i need to use the "public route" which shall be known i my zone by peered Eureka's (see http://docs.pivotal.io/spring-cloud-services/1-2/service-registry/enabling-peer-replication.html ).
So in fact a microservice has to offer also an external  route which allows access by load balance or just lookup from another PCF / Eureka region that is no party of the local overlay network.

Thats all assuming you are using PCF, which may not always be the case.

@csterwa  Would you help us to find a good solution, where/how to implement that shared for both words (pcf or any other xaas). Tx a lot.

@cforce @spencergibb @ryanjbaxter @habuma sounds like we have a potential solution. The SCS team has prioritized this now and will provide an update when we have more information.

Great news for multi/hybrid cloud scenarios 😀. good luck for the Sprint, looking forward to it

@cforce Your first option is a bit unsettling. At this point, the clients only deal with Eureka and any services that they discover from Eureka. This option would require that they also be aware of and communicate with the cloud platform to know if the target is reachable. This would be highly dependent on the capabilities of the platform in question and would make the application aware of the platform. I'm not sure I'm excited about this option.
The retry approach is intriguing, though. I think that you're suggesting that it should try one way (IP, let's say) and then, if that doesn't work, try the other way (host). On the surface it sounds reasonable, but thinking through where this would need to happen makes me think it is a bit complex. And I worry about performance, as making a bad first call and then falling back will take longer than just making the right call the first time. Even so, it's an option worth exploring.

Actually spring cloud netflix is not aware of the XaaS, what is advantage and disadvantage at the same time. I don't see a big disadvantage to introduce a XaaS native API (to ask for C2C or P2P connectivity) as dep in Spring Cloud Ribbon that is implemented at runtime by autoconfiguration for the supported XaaS (PCF or Kubernetes).


Print url when server has been started

This is useful when running the server on the dart VM for debugging

Good catch, my update should do the trick :)


release: Bump versions to 0.32.3

Let's release the function attributes JSON ABI change into the wild!

Shouldn't we be bumping to 0.33.0 instead to avoid the same issues that we faced a few days ago with messagesTypes? Changes to the JSON ABI types breaks the compiler.


UI Glitch when updating the data

When updating the data, the annotations will sometimes appear on the top left corner while the animation is taking place. When the animation is done, the annotation will move to its correct position.

This behavior can be reproduced right from the samples of the online docs : https://www.chartjs.org/chartjs-plugin-annotation/samples/types/line.html#line

Click on remove data until there is no more data
Click on add data

This happens because the "minValue" returns Infinity when there is no data. Inifinity us quite far up, but the label is enforced to stay inside chartArea. The last animation step going from infinity to the actual value is still infinite large, that's why it jumps to its final position at last frame. The solution is to prevent infinity.

@kurkle Maybe this is a way to fix it in this particular example, but I don't thick it actually fixes the real issue. In my actual use case, the problem happens on datetimes with the zoom plugin (so not related to Infinity)

I understand that the annotation must stay inside the chart, so maybe there isn't any way to really fix this.

@philfontaine ok, I think I found the problem.


getting-started comments

Git clone command has permition issues, better to change it with http one
About the clone command, should it be aframe or aframe2? (aframe2 requests login in)
To initialize submodules I think you need to be in the repo, so maybe add an instruction for the user to cd in the repo.
The update of submodules has an permition issue

(igwn) [vasileios.skliris@ldas-pcdev12 ~]$ cd aframe/
(igwn) [vasileios.skliris@ldas-pcdev12 aframe]$ git submodule update --init
Cloning into '/home/vasileios.skliris/aframe/hermes'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:ML4GW/hermes.git' into submodule path '/home/vasileios.skliris/aframe/hermes' failed
Failed to clone 'hermes'. Retry scheduled
Cloning into '/home/vasileios.skliris/aframe/ml4gw'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:ML4GW/ml4gw.git' into submodule path '/home/vasileios.skliris/aframe/ml4gw' failed
Failed to clone 'ml4gw'. Retry scheduled
Cloning into '/home/vasileios.skliris/aframe/mldatafind'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:ML4GW/mldatafind.git' into submodule path '/home/vasileios.skliris/aframe/mldatafind' failed
Failed to clone 'mldatafind'. Retry scheduled
Cloning into '/home/vasileios.skliris/aframe/hermes'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:ML4GW/hermes.git' into submodule path '/home/vasileios.skliris/aframe/hermes' failed
Failed to clone 'hermes' a second time, aborting

Ah okay - my instructions assume you have added an ssh key to github. Let me point to the git versions of those instructions.

Oh of course this is not ligo gitlab


Remove json tags from pkg/api/types.go

Previous discussion in #1004 and #3900.
We should never serialize the internal representation. Removing the json tags would make this clearer.
/cc @thockin

The tags are a nuisance and a source of confusion, which is evident in the first couple sentences of #5459. Someone should just do the experiment of removing the tags to see if anything breaks.

not really a priority for 1.0 though...
--brendan
On Fri, Mar 13, 2015 at 4:30 PM, Brian Grant<EMAIL_ADDRESS>wrote:

The tags are a nuisance and a source of confusion, which is evident in the
first couple sentences of #5459
https://github.com/GoogleCloudPlatform/kubernetes/pull/5459. Someone
should just do the experiment of removing the tags to see if anything
breaks.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/3933#issuecomment-79527249
.

So @brendandburns, @bgrant0607 what is actual priority of this issue? I can do it.

Low.  Its one of the last things I'd do before v1.0, and I think we could
clearly ship 1.0 without it.  Improving the swagger api doc generation (and
docs in general) is way higher priority, for example.
Brendan
On Mar 18, 2015 11:25 AM, "Piotr Szczesniak"<EMAIL_ADDRESS>wrote:

So @brendandburns https://github.com/brendandburns, @bgrant0607
https://github.com/bgrant0607 what is actual priority of this issue? I
can do it.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/3933#issuecomment-83110433
.

@brendandburns This comes up in many API code reviews.
I just did:
sed -i 's/ *`json:[^`]*`//' types.go

Building and testing now.

Failures, most likely due to things using the internal rep. where they should not:
--- FAIL: ExampleEmptyConfig (0.00s)
--- FAIL: ExampleOfOptionsConfig (0.00s)
FAIL    github.com/GoogleCloudPlatform/kubernetes/pkg/client/clientcmd/api      0.007s
--- FAIL: TestPrinters (0.00s)
FAIL    github.com/GoogleCloudPlatform/kubernetes/pkg/kubectl   0.077s
--- FAIL: TestExtractFromHTTP (0.01s)
FAIL    github.com/GoogleCloudPlatform/kubernetes/pkg/kubelet/config    2.062s

Kubelet test failure is probably due to a stray use of api.ContainerManifest here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/bdc1981eb5260f7baa456529b0e3cad9198c4ed3/pkg/kubelet/config/http_test.go#L155

Since I determined what doesn't work, removed from 1.0 milestone and demoted priority.

#5632 fixes the Kubelet test.

#8294 took a stab at this and failed.
Sadly, the codebase is not ready for this.  Specifically:

clientcmd depends on api.TypeMeta (not documented) and the JSON tags therein.
kubectl does a JSON marshal/unmarshal which breaks without the core JSON tags.

There may be more but I gave up.

I'm now thinking we should eliminate api/types.go. Discussion here: https://github.com/GoogleCloudPlatform/kubernetes/issues/8190#issuecomment-114139999

Late to the party-- anything that serializes the internal structs is BROKEN and needs to be fixed. :( :(

I completely agree.
My preference is to nuke api/types.go.

We should prioritize this. It is masking issues like https://github.com/kubernetes/kubernetes/issues/23173

I just tried to remove these again.  It fails in jsonpath formatting, now.


Authoring with user control - diagnostics catching Xaml generated file

Describe the bug
Authoring diagnostics catches that one of Xaml's generated files doesn't have the default overload attribute on their classes.  It used to be that as long as the attribute was set on the interface (which it is), it was implied the same attribute on class.
To Reproduce

Add empty User Control WinUI template to authoring component project
Build results in error: Severity    Code    Description    Project    File    Line    Source    Suppression State    Tool
Error    WME1085    In class XamlMetaDataProvider: The 1-parameter overloads of GetXamlType must have exactly one method specified as the default overload by decorating it with Windows.Foundation.Metadata.DefaultOverloadAttribute.    UserControlLibrary    C:\Users\angzhang\source\repos\WinUII3Desktopnternal\UserControlLibrary\obj\Debug\net5.0-windows10.0.18362.0\XamlTypeInfo.g.cs    46    Build        Csc

Version Info

1.1.1-prerelease.210111.5

I'm still seeing this error with a blank User Control - should it be fixed in 1.1.2-prerelease?
Severity	Code	Description	Project	File	Line	Source	Suppression State	Tool
Error	CsWinRT1016	In class XamlMetaDataProvider: The 1-parameter overloads of GetXamlType must have exactly one method specified as the default overload by decorating it with Windows.Foundation.Metadata.DefaultOverloadAttribute	WinUIAuthoringSample	C:\repos\WinUIAuthoringSample\WinUIAuthoringSample\obj\x64\Debug\net5.0-windows10.0.18362.0\XamlTypeInfo.g.cs	46	Build		Csc

@angelazhangmsft it requires you a WinUI projection update with the CsWinRT 1.1.1. build.


Do not remove trailing comma in value argument list in annotation

Description
The code previously contained special handling for case below:
    @Annotation([
        "something",
    ])

This special case however was also triggered in case of:
    @Annotation(
       foo = [
        "something"
       ],
       bar = "some-bar"
   )

In this case the normal handling of value argument lists should be used once for the outer value argument list (containing elements foo and bar) and once for the inner value argument list of parameter foo (containing element "something"). So in example above, a trailing comma has to be added to both the outer and the inner value argument list.
Closes #1297
Checklist

[X] tests are added
[X] CHANGELOG.md is updated

@paul-dingemans Thanks for taking care of that. 💪


fix link to interpolation tagging in SC docs

Coverage remained the same at 99.669% when pulling 145833e41a7a8918bf42c68d5a06d80a75f3aa03 on WickyNilliams:patch-1 into 715f3b7d36353036eb740eae1c674163705c0299 on styled-components:master.

Haha, thanks! That definitely wasn't the way to spell tagging ;)

Thank you so much for helping us improve styled-components! Based on our Community Guidelines every person that has a PR of any kind merged is offered an invitation to the styled-components organization—that is you right now!
Should you accept, you'll get write access to the main repository. (and a fancy styled-components logo on your GitHub profile!) You'll be able to label and close issues, merge pull requests, create new branches, etc. We want you to help us out with those things, so don't be scared to do them! Make sure to read our contribution and community guidelines, which explains all of this in more detail. Of course, if you have any questions just let me know!

Hey @mxstbr, that's an interesting approach! Do you ever have any problems with giving people write access so soon? I have a few open source projects that i'm struggling to maintain, and maybe this is a good approach for me!

We've been doing it for a few years on Danger and Moya and never had problems 👍

Cool. Thanks for letting me know!

Do you ever have any problems with giving people write access so soon?

Nope :blush:

I just joined. I promise I won't cause problems 😄


Documentation missing entries: EBGSSystemsV4

These entries from the systems response are missing from the documentation:

system_address
conflicts
secondary_economy

This is fixed in v5 API


feature: Upgrade loader to be compatible with django 1.10

This pull request closes the issues: #261 #256

could someone please release this fixed version?

@hmleal , @syrusakbary ,
Has this PR been tested on Django 1.9 ? (I don't have django 1.9 installed and didn't test it)
Based on the assumption that previous code was working with django 1.9, I understand how the try/except works for both django 1.9 and 1.10, but I don't understand how the __init__ with then new engine param would work in django 1.9 as it would be called with only 2 parameters right ?
And for django 1.10, it seems that the Loader class, renamed here as BaseLoader seems to take engine as __init__ parameter. But __init__ is never called. I suppose it would be important.
I haven't played with django for literally 10 years, and all my analysis is just based on few code lines I just read, and not tested, so I may say a lot of silly things.

travis is continuosly testing this repo and only reported problems for Django 1.6 and 1.7 have a look above

So has this version of PyJade been released yet or?

Hey there!
Thank you for fixing this issue, good job man.
IMHO when you fix such major issue please release new version and put in on PyPy. People then don't have to figure out how to install last commit from master git repo via pip.

As of now this issue is not fixed with the current version of pyjade
I am trying Django 1.10.6 with pyjade 4.0.0 and the error still exists.

@ptrdvds
Looked into my virtualenv site-packages folder into the pyjade.ext and it seemed that though I have the pyjade=4.0.0, the relevant line that fixed this issue in the above PR is missing.
Until it would be fixed (@syrusakbary perhaps something is wrong with the pypi shipping?), you can bypass this issue by installing directly from the master branch on github:
pip install git+https://github.com/syrusakbary/pyjade.git


App not compatible with my device in Google play store

Hi,
I really want to use this app for debugging, but google play will not let me install because it says the app is not compatible with my phone.  I am not too concerned because I am planning to buy a new Android phone for this purpose anyway, but before I buy I must be sure that this app will work on it.
Can you please reply with the minimum requirements of this app running on Android devices ??
Thank You,
Phil

Hi am using Itel 1506 running Android 5.1
Tried installing App through google play and it says "Your device isn't compatible with this version."
I tried installing it on 20/05/2016
Thanks you for your assistance in solving this.

I am having a similar issue to @Macwilcy with a Acer Liquid Z380 running Android 5.1.1.

Hi @Macwilcy & @RetroCraft,
Please take a look at https://github.com/phonegap/phonegap-app-developer/issues/408.
Unfortunately your device does not meet some minimum standards that we require for our app. You can still manually download the apk and install it yourself and it may work just fine for your needs. But some of the features might not work as intended.


Implement cmp+branch instruction fusion

Closes https://github.com/paritytech/wasmi/issues/712
This improves performance of the count_until.wat benchmark by roughly 40%.
TODO

[ ] Write more and proper tests for all or most cases.
[ ] Try to find other ways to introduce cmp+branch instruction fusion.
[x] Fuse cmp+branch instruction for branch_nez encoding.
[ ] Fuse cmp+branch instruction for branch_eqz encoding.
[ ] Find ways to allow for fusion with uninitialized branch offsets with might exceed 16-bit encoding.

 Please review.

Comparison is base (d1bc10c) 81.41% compared to head (36a8510) 80.83%.

Files
Patch %
Lines

...mi/src/engine/regmach/translator/visit_register.rs
0.00%
56 Missing :warning:

.../wasmi/src/engine/regmach/translator/result_mut.rs
0.00%
52 Missing :warning:

...smi/src/engine/regmach/translator/instr_encoder.rs
42.85%
44 Missing :warning:

crates/wasmi/src/engine/regmach/executor/instrs.rs
17.30%
43 Missing :warning:

...wasmi/src/engine/regmach/executor/instrs/branch.rs
68.57%
11 Missing :warning:

...rates/wasmi/src/engine/regmach/translator/visit.rs
25.00%
6 Missing :warning:

crates/wasmi/src/engine/regmach/bytecode/utils.rs
90.90%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #789      +/-   ##
==========================================
- Coverage   81.41%   80.83%   -0.59%
==========================================
  Files         271      273       +2
  Lines       24236    24556     +320
==========================================
+ Hits        19732    19849     +117
- Misses       4504     4707     +203

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


Change versioning policy on Read the Docs

Right now we have both latest and stable, which is good, and also 1 version per tag, which is not so good.
The problem with stable is that it is a moving target (in the same way as latest) and therefore for releases, announcements, and things like that I prefer to use a version that refers to a given tag that will be preserved.
However, since we follow (more or less) Semantic Versioning, patch releases don't introduce significant changes, and the latest one within a given minor version. In other words: 0.16.2 should always be preferred over 0.16.0, but 0.17.0 introduces new functionality and breaking stuff.
Therefore, it would be better to use branch-based versions instead of tag-based versions, so that we can always point folks to
https://docs.poliastro.space/en/0.17.x/

instead of having to change from https://docs.poliastro.space/en/v0.17.0 to https://docs.poliastro.space/en/v0.17.1 when there is a patch release.
We will apply this change starting with the 0.17.x branch.

This has been effectively done.


Upgrade XNAT version to <IP_ADDRESS>

More of a suggestion than an issue.

Currently having incompatibility issues with some AIS supported plugins. Includes the openid auth provider plugin.
A release candidate image has been added to help with ongoing development.

Work in coordination with Alastair has completed a viable 1.8.2 xnat image


MIPRO v2

I'm submitting a ...
[x] feature request

Summary
I would love to see MIPRO v2 implemented in here.

if anyone wants to work on this reach out on discord i'm happy to help


Could I share my CUDA context with a PyZEDCamera?

Though the ZED SDK provides a way to share my CUDA context with a ZED camera,
it seems that the current version of its python wrapper lacks it:

InitParameters::sdk_cuda_ctx
Camera::getCUDAContext

Is there any way to share my context with a PyZEDCamera?
I'm grad if ZED cameras could be used in CUDA applications developed on python.

Hi,
Yes, it's a missing feature, you currently can't (without modifying the plugin).
It is planned though. It will probably require PyCUDA.

Hi,
thank you for clarification. For now, I will try to modify the plugin to run it with PyCUDA.

Hi,
I've noticed that I can use CUDA context switching (push & pop) to run my CUDA programs with PyZED rather than trying to share the contexts, which is sufficient for my purpose.
Yet it'd be convenient if context sharing will be implemented on PyZED in future :)

@oha08 I'm new to this and trying to figure out how to do the same (I need to run a DNN and query the ZED In the same process). Any code you can share? How exactly does one switch cuda contexts? Thanks!

I made a tiny cython module to do this and it works! Thanks for the tip guys!
https://github.com/frk2/cuda-fun

@frk2 Hi, Your module looks pretty nice and simple enough for working! In my case, I'm using PyCUDA to create and push/pop my context. Because PyCUDA doesn't provide any interface to get the current context, I've selected to keep the context made by ZED stacked and push my context on top of it:

open ZED Camera where a context is created
create my context, which is automatically stacked on top of the previous context
pop my context when calling ZED functions
push my context when calling my CUDA kernels (if it is popped before)
and so on

Your module enables more flexible control than this :)  Thanks a lot!

I was thinking of doing the same - but the bummer is that you can't pass a created context to either ZED or Pytorch (they both create one) and hence pycuda was useless since it doesn't let me get the current context.
Thanks for the tip though definitely guided me in the right direction!

@frk2 By default the ZED SDK creates a new context, but with the C++ SDK you can pass your own context to the ZED with InitParameters::sdk_cuda_ctx.
As mentioned in the original post, this feature is missing from the python wrapper though.

Any update whether context sharing is possible with ZED camera and the python API? I'm trying to work with the ZED camera an CuPy an have probably encountered an issue related to this.

Just to update on my solution for this issue. The ZED runs its own context internally and therefore processing images using CuPy should be handled in a different thread. My best solution relied on the ZED-TensorFlow example which worked pretty good.

你好。我用的是zed相机，cuda是11.7，  运行get_python_api.py文件时，提示PermissionError: [Errno 13] Permission denied: 'C:\Program Files (x86)\ZED SDK\pyzed-3.8-cp39-cp39-win_amd64.whl'，但是安装whl文件之后，继续重复出现这个错误，是什么原因导致的呢

Hello. I use a zed camera, and the cuda is 11.7. When I run the get_python_api.py file, I am prompted with permission error: [errno13] Permission denied:' C: \ \ Program files (x86) \ \ ZED SDK \ \ PYZED-3.8-CP39-CP39-Win-amd64.whl', but after installing the whl file, what causes this error to appear repeatedly?


Plugin/extension system

Clear and concise description of the problem
An easy way to add a stack into any project
Suggested solution
Reuse @stacksjs/cli
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Reusing Vite's plugin ecosystem/setup


Https.jawaker.com

#457 #468
@

[ ]

[ ]

[GNI-Principles-AR.pdf]

_3# _

jawaker

https://github.com/ikatyang/emoji-cheat-sheet/issues/470#issue-676486389


DOC 1868 intodb option

Addresses DOC-1868:

Expanded description for into_db RESTORE option by adding code block that the database needs to exist before running the restore

Fixed versions 21.1-22.2

Cleaned options table to group into_db and new_db_name together; changed new_db_name description for consistency

Fixed versions 22.1, 22.2

Staging:

Restore tables into a different database
Options table

Oops, should have looked more clearly to avoid for the backtick typo, thanks Kathryn!


on_run is not invoked if Visual Studio is unable to start debugger for unknown toolchains

Xmake Version
2.9.4
Operating System Version and Architecture
Windows 10
Describe Bug
When working with a custom toolchain, pressing Start in Visual Studio 2022 throws an error for a missing debugger.
There doesn't seem to be a way to run custom debuggers at the moment, so I hoped I could invoke the platform debugger with on_run as a workaround, but it is not called if the application fails to start.
Expected Behavior
If Visual Studio does not have a debugger, on_run should still be invoked.
Or preferably, allow a custom debugger to be added to the toolchain. Related #5554
Project Configuration
cannot provide
Additional Information and Error Logs
Visual Studio:
Unable to start debugging. Check your debugger settings by opening project properties and navigating to 'Configuration Properties-->Debugging'

vs/vsxmake generator does not support the custom debugger.


Creating the basic directory structure for the bot

I created the directory structure for the bot:
.
├── bot
│   ├── cogs
│   │   └── __init__.py
│   ├── __init__.py
│   └── __main__.py
├── LICENSE
├── Pipfile
├── Pipfile.lock
└── README.md

it looks like this for now. feel free to comment and discuss with me :smiley:

My idea is:

Once we are done with the basic structure, we can then create another branch develop where we can test features by creating branches based off of develop for the bot before merging such features to develop. Further testing may promote such features from develop to main and then we select which features to implement for the bot in the  release branch.

Cool! The PR looks good to me!

My Idea is too complex...
Based on @gustavwilliam 's suggestion, my idea is rather complex since the bot is still at its infancy. So here is the updated workflow according to @gustavwilliam :
Steps

Evaluate what features we want
Create bot core and fix dependency management and similar
Implement features

Comments on workflow:

I agree on the workflow.
I suggest we create two branches - core and develop:

core branch is the bot's core so if anything is messed up, it stays there.
develop is where we test the new features. We create this features by branching off from the develop branch. The branches should be named after the feature (e.g. feature/ci) and then PR to develop for further testing. These will prevent mishaps if something goes wrong from the feature branch.

Alrighty! Let's go!!!

Feel free to comment here and discuss.

@ReneganRonin maybe this would work even better as a discussion issue?

@gustavwilliam alrighty

If we need a database I suggest using Postgres within Docker.

@Xithrius feel free to open discussion in https://github.com/gurkult/gurkbot/issues/7#issue-770758569

yeah i dont know why we need this, we should just add things as we need them, plus you forgot a utils folder

yeah i dont know why we need this, we should just add things as we need them, plus you forgot a utils folder

@mudkipdev these are some great contributions. The fact that @ReneganRonin took the time to work on the fundamental folder structure for the project is really valuable. That's something we need to have in a structured and well-built application. The issue with this PR wasn't the contents, but rather the fact that it would fit better as an issue.
Also, try to keep a positive tone. That message seemed more like your were trying to point out every flaw in the PR. We prosper as a community only when we are encouraging and inclusive.

Also, try to keep a positive tone. That message seemed more like your were trying to point out every flaw in the PR. We prosper as a community only when we are encouraging and inclusive.

Sorry if it sounded that way, I was just trying to give a suggestion. I also agree that this should fit better as an issue or a discussion rather than a pull request.


10 connexions-invalides (template)

Type: Feature Request
OUESLATI BELHASSEN
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.19045
Modes:

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


[Bug]: WebSocket Crashes with ValueError on latest_event_id

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
Description:
I'm encountering a critical issue while integrating OpenHands with LiteLLM Proxy to access Amazon Bedrock. The WebSocket crashes repeatedly due to a ValueError when OpenHands attempts to process the query parameter latest_event_id. This seems to occur because the value of latest_event_id is 'undefined', which cannot be converted to an integer.

Steps to Reproduce:

Configure LiteLLM Proxy with the following config.yaml:
model_list:
  - model_name: bedrock/us.anthropic.claude-3-5-sonnet-20241022-v2:0
    litellm_params:
      model: "us.anthropic.claude-3-5-sonnet-20241022-v2:0"
      aws_region_name: us-east-1
    model_info:
      id: "arn:aws:bedrock:us-east-1:6xxxxxxxxx8:inference-profile/us.anthropic.claude-3-5-sonnet-20241022-v2:0"

general_settings:
  master_key: sk-xxxxxxxxx

Start the LiteLLM Proxy:
export AWS_ACCESS_KEY_ID=your-access-key-id
export AWS_SECRET_ACCESS_KEY=your-secret-access-key
export AWS_REGION=us-east-1
litellm --debug --config ./config.yaml

Verify that the LiteLLM Proxy works by making the following API call:
curl --location 'http://<IP_ADDRESS>:4000/chat/completions' \
  --header 'Content-Type: application/json' \
  -H 'Authorization: Bearer sk-xxxxxxxx' \
  --data '{
    "model": "us.anthropic.claude-3-5-sonnet-20241022-v2:0",
    "model_id": "arn:aws:bedrock:us-east-1:6xxxxxxxxxx8:inference-profile/us.anthropic.claude-3-5-sonnet-20241022-v2:0",
    "messages": [{"role": "user", "content": "what llm are you"}]
  }'

Expected Result: The request completes successfully, and the response is returned by LiteLLM Proxy.

Start OpenHands using the following Docker command:
docker --debug run -it --rm --pull=always \
  -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.14-nikolaik \
  -e LOG_ALL_EVENTS=true \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -p 3000:3000 \
  --add-host host.docker.internal:host-gateway \
  --name openhands-app \
  docker.all-hands.dev/all-hands-ai/openhands:0.14

Configure OpenHands with the following in the UI:

Custom model: litellm_proxy/us.anthropic.claude-3-5-sonnet-20241022-v2:0
Base URL: http://<IP_ADDRESS>:4000
API Key: sk-xxxxxxxx

Start a conversation in OpenHands.

Observed Behavior:
OpenHands enters an infinite loop, throwing the following error repeatedly:
ValueError: invalid literal for int() with base 10: 'undefined'
  File "/app/openhands/server/listen.py", line 347, in websocket_endpoint
    latest_event_id = int(websocket.query_params.get('latest_event_id'))
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Environment Details:

OpenHands Version: 0.14
LiteLLM Proxy Version: 1.52.10
Operating System: MacOs
Hosting Environment: Docker
AWS Region: us-east-1

OpenHands Installation
Docker command in README
OpenHands Version
0.14
Operating System
MacOS
Logs, Errors, Screenshots, and Additional Context
No response

Going to gently ping @enyst as he's quite good with these things...

This looks strange... On one hand, the error is not about Bedrock/LLM, it's from the websocket, for some reason the UI has an event without id here. Maybe @tofarr has a better idea there?
I cannot replicate it, even if I use bedrock and litellm proxy. @liatweissman could you please try to add in the model name 'bedrock' though, or make sure litellm works?
Also, could you do a hard refresh of the browser, and try again? Normally even if there's a problem with the llm it should start.

Hi @enyst
Thank you for the suggestions. I tried the following based on your feedback:

Updated the model name in OpenHands to include bedrock, as in:litellm_proxy/bedrock/anthropic.claude-3-5-sonnet-20241022-v2:0

Confirmed that the LiteLLM Proxy works flawlessly with the curl command I shared earlier.
Performed a hard refresh in the browser and also tested in incognito mode.
Upgraded LiteLLM to the latest version (1.52.12).

Unfortunately, I am still encountering the same ValueError related to latest_event_id. The WebSocket session starts but fails due to the undefined value for latest_event_id.
Could you suggest any additional steps or debugging options I could try? Also, is there any more information you need from my side to help replicate this issue?
Let me know how I can assist further in diagnosing or resolving this.

Thank you. Can you please try to run openhands:main instead of openhands:0.14?

I already tried running openhands:main instead of openhands:0.14, but unfortunately, I am still encountering the same error with the latest_event_id being 'undefined'.

Oh, that can explain it. Except if you delete everything and incognito mode... @liatweissman Considering the above, could you please try to clean out the browser's local storage? Then maybe also, make a new project, or at least change the settings and save, to force a new session.


Namespace details views show pods that belong to other namespaces

Apparently the filtering for listing pods that belong to a namespace, in their namespace details view is broken and there are pods from different namespaces being shown in others' details views.

This is still happening, according to @lijianzhi01 , when you go to StatefulSets:

Choose a StatefulSet resource
Verify that the pods listed for it belong to different namespaces than the StatefulSet


Compile error in the World.cc of sdformat12-12.6.0

Hi I tried to build sdformat12-12.6.0 with ignition-math6-6.8 as specified in the cmake file. but, it occurred compile error as following.
I think SufaceType is enum and your code convert it to reference of string in this line. so, error occurred.
Can you please look into this issue?
Environment

OS Version: Ubuntu-20.04
Source or binary build? 12.6.0
 1ee5f0717a09c3951a9aeea9929b5ab50d1706c6

Description

Expected behavior:  Should build successfully
Actual behavior:

| /home/bchoi/nvidia-yocto-bsp/bchoi-build/tmp/work/armv8a-oe4t-linux/sdformat12/12.6.0-r0/git/src/World.cc: In member function 'sdf::v12::ElementPtr sdf::v12::World::ToElement(const sdf::v12::OutputConfig&) const':
| /home/bchoi/nvidia-yocto-bsp/bchoi-build/tmp/work/armv8a-oe4t-linux/sdformat12/12.6.0-r0/git/src/World.cc:893:55: error: cannot convert 'ignition::math::v6::SphericalCoordinates::SurfaceType' to 'const string&' {aka 'const std::__cxx11::basic_string<char>&'}
|   893 |           this->dataPtr->sphericalCoordinates->Surface()));
|       |           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~

Steps to reproduce

Output

The conversion was added in https://github.com/gazebosim/gz-math/pull/235 and was released in ign-math6 6.9.0. So you'll need that version to compile.
The version in the SDFormat CMakeLists should have been 6.9, but it's not something we can fix now. Sdformat has since been updated  and now requires ign-math6 6.13.0 or newer.


[COMPRESS-534] use StandardCharsets.

In most cases using StandardCharsets is faster.
You can get more information at decode(String charsetName, byte[] ba, int off, int len) and decode(Charset cs, byte[] ba, int off, int len) in class java.lang.StringCoding

Coverage increased (+0.08%) to 87.31% when pulling 243bfff8cace2a29e32b0622ae205b6b66c07616 on XenoAmess:use_StandardCharsets into 04abbdf3b7e78e9fd4ba5c46e22f0472a7974ad6 on apache:master.

Many thanks @XenoAmess