GitHub Sync not working

Hi, I’m trying to set up the GitHub Sync, following the instructions precisely, and every time I reach the point where I click Setup, I get an error message telling me
Unable to proceed because Github Downloader - InOutError Could not initialize OpenSSL library
Machine being used runs on Windows 8.1 Professional. I tried googling the error message (whole and in parts), but couldn‘t find any solution. Also, for some reason my version doesn’t show the ChangeSyncRepo button mentioned in the explanation, only Setup.
Any pointers to what I can try much appreciated.
Thank you!

Hmm, I have only tested github sync with Windows 10/11, ssl libraries can be very picky.  You 'might' be able to solve this by putting an appropriate open SSL dll file in the same directory as tomboy-ng, that will override the system installed one without affecting any other application.
I will look into this and see what I can find, will get back as soon I can ...
The Change Sync Repo button only shows up after you have a working sync, sounds like you have not got that far yet !
Davo

eamwml, yes, I can confirm that the ssl DLLs at https://indy.fulgan.com/SSL/ work fine. Others may too but I know most Windows using Pascal people use the ones from Indy.
Seems I have previously installed them on both my Windows test boxes system wide so they just worked there. So, very sorry about the problems I have cause you (and anyone else who does not already have SSL installed on a Windows machine).
I suggest the easiest and safest way to use these DLLs is to download the latest zip from the above link, extract just the two DLL files (libeay32.dll and ssleay.dll) and then put them in the same directory as the tomboy-ng binary. In my case that is c:\Program Files\tomboy-ng\
Restart tomboy-ng and all will work as expected.
I do not suggest you put the DLLs in a general purpose area in case they clash with some other app, probably not but just not worth the risk IMHO. But its quite likely you know far more about Windows that I do ! If you have your own favorite openSSL DLLs, that you would prefer to use, just put them in with the tomboy-ng binary, will probably work fine.
Please let me know how you go.
David
Ref: https://wiki.openssl.org/index.php/Binaries

Hi David,
Thanks a lot, everything works perfectly now! I'm usually on Ubuntu, but I don't always get a choice at work ...


[switch.wemo] Fix mW to kW conversion.

Description:
Conversion was wrong.
8954105 mW should convert to 8.954105 kW, not 8954.105 kW.

This was certainly wrong - but don't think this completely fixes it.
Hadn't finished digging - but I think wemo reports this in milliwatt minutes. So I think we probably also need to multiply by 60.

@pavoni I'm not sure I understand. That'll turn this calculation into 537 kW which is also very wrong.

Sorry my description was wrong
    @property
    def today_energy_kwh(self):
        """Today total energy usage in kWh."""
        if self.insight_params:
            return convert(self.insight_params['todaymw'], float, 0.0) / (1000.0 * 1000.0 * 60)

@pavoni that looks much better, 0.14kW.


feat: add support for fail state

What type of PR is this?

/kind enhancement

What does this PR do / why we need it:
This PR aims to add support for fail state
Which issue(s) this PR fixes:
Fixes #33
How to test changes / Special notes to the reviewer:

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

Project coverage is 6.94%. Comparing base (e30ffc9) to head (c9edde6).

Files
Patch %
Lines

internal/controller/statemachine_controller.go
0.00%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##            main     #34      +/-   ##
========================================
- Coverage   7.00%   6.94%   -0.07%
========================================
  Files          6       6
  Lines        314     317       +3
========================================
  Hits          22      22
- Misses       291     294       +3
  Partials       1       1

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


method_missing': undefined method this' for #<Gem::Specification:0xbdf8f8 eventmachine-<IP_ADDRESS>> (NoMethodError)

This is a bug in rubygems/rvm/bundler:
https://github.com/rubygems/rubygems/issues/1420
Please upgrade rubygems, rvm and bundler.


Restore flank auth login

Fix #502

Codecov Report

Merging #505 into master will decrease coverage by 0.1%.
The diff coverage is 41.07%.

@@             Coverage Diff             @@
##             master    #505      +/-   ##
===========================================
- Coverage      78.3%   78.2%   -0.11%
- Complexity      662     666       +4
===========================================
  Files            73      73
  Lines          1885    1913      +28
  Branches        281     293      +12
===========================================
+ Hits           1476    1496      +20
- Misses          234     235       +1
- Partials        175     182       +7


sketch of basic pipenv show impl

Basic WIP sketch of addition of pipenv show PKG_NAME functionality, analogous the the command in pip.
I'm aware of some things that ought to be added to this to make it acceptable for merging. I made these changes as part of a quick experiment in determining whether I could easily do it before I opened an issue asking whether such a feature was welcome. Since I got this far, I figured I'd show my work.

As per the discussion on #1462, we think it's better to improve the documentation around using pipenv run pip ... to access pip subcommands beyond those directly supported by pipenv.


Cannot read property 'attempt' of undefined

When providing a value in the "Name of stage (override)" field on the release task I get the following errors upon execution
2020-09-30T17:08:04.8571718Z Show associated items for primary artifact only is set to false
2020-09-30T17:08:04.8572513Z Getting deployment count for stage
2020-09-30T17:08:04.8613589Z ##[error]TypeError: Cannot read property 'attempt' of undefined
2020-09-30T17:08:04.8628406Z ##[error]TypeError: Cannot read property 'attempt' of undefined
2020-09-30T17:08:04.8736885Z ##[error]TypeError: Cannot read property 'attempt' of undefined
These errors are only seen when a value is provided for the "Name of stage" field.  I have confirmed that the name I am providing in the field represents a uniquely named stage in the release pipeline as well.
My intention was to run this from an early stage in the pipeline comparing to "Prod" so I can generate  release notes that would map to "What would the release look like if this were deployed to prod?"... without having to actually deploy to prod/ie as the final step in the pre-prod stage.
Env info
Name: Generate Release Notes (Crossplatform)
I am running version 3.15.3 (I see the same error if I switch to a 2.* version as well)

It would appear that in your case there has been no pre deployment approval for the named stage so it cannot get an attempt count. I will get a new version (it will be 3.17.x) that will add an extra check that pre deployment deployment is not null.
Let me know if that fixes you issues.

Thank you for the fast turnaround here.  However, while this did fix the original error, the scenario still fails (different error now)
2020-10-01T17:04:44.8146611Z Show associated items for primary artifact only is set to false
2020-10-01T17:04:44.8148018Z Getting deployment count for stage
2020-10-01T17:04:44.8178088Z ##[error]Failed to locate stage with name prod so cannot get attempt
Perhaps casing is the cause?
The stage name I am attempting to use here is "Prod" while the error message mentions "prod"
A shortened version of my pipeline
StageName: Dev
-Has this task; specifies "Prod" (no quotes) in the 'Name of stage' field
StageName: Prod

Has a predeployment approval (not executed)

Dev --> Prod

Sure, here is a link to the log.
tasklog_6.log

The reason you are seeing different log results to me is that you have a stopOnRedeploy=true set. This is a rarely used feature, enabling it triggers a check to see how many previous releases have been made and if greater an 0 aborts the release notes generation.
You had found a bug that an exception was being thrown that meant it thought there was a past release when there was none.
I have altered the logic so that if it finds no release to stage then it return a zero count as expect (as opposed to the exception). This will be released as 3.18.x later today when all the automated tests have run.
An immediate fix would be to set stopOnRedeploy=false to bypass the problematic logic

Looks good.  I ran it again after your 3.18.x update (stopOnRedeploy=true) and targeting another stage for comparison (vs current stage) all looks good.  Thank you for the quick turnaround here!


Unable to find the selected font "Cascadia Mono" in Windows 10

Windows Terminal version
1.13.10336.0
Windows build number
10.0.19044.0
Other Software
I have both Windows Terminal (1.11.3471.0) and Windows Terminal Preview (1.13.10336.0) installed. The Store says Windows Terminal Preview updated today, but both apps are unable to find the "Cascadia Mono" font, which I'm told should be bundled with the app.
Steps to reproduce
Open Windows Terminal Preview
Expected Behavior
A "Warning" popup does not appear.
Actual Behavior
A "Warning" popup in the Terminal window appears with the following text
Unable to find the selected font "Cascadia Mono".

"Consolas" has been selected instead.

Please either install the missing font or choose another one.

Again?! :(
This was a really annoying issue some 5+ months ago. Not great that it's popped up again.

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #11648 for more discussion.
/dup #11648

FYI: When I implemented a fix I used APIs which only work on Windows 11.
Today I made some changes to make it work on Windows 10. I'll open a PR soon.

I'm repurposing this issue to submit a change for Windows 10 support.

This is not fixed in Preview 1.13.10983.0

My Windows Terminal Preview was updated today, so it is clear that update is still broken. What is a workaround?

Huh. @lhecker & @DHowett for visibility. Any ideas if we left in any logging do diagnose why the preemptive fallback wouldn't be working?

Well, my repro is already gone, unless you have debug logs in some file in somewhere (temp folder?)
This is Windows 10.0.19044.1586, latest publicly available version (21H2). You have tested some prerelease insider build.

Just updated Windows Terminal Preview on other Windows 10 machine (same version), and bug didn't repro.

@srdjanjovcic I think I've figured out what went wrong. See #12904.


SwiftyJSON - rawData() behaves different with nested json

Problem
The JSON.rawData() function passes JSON instances to the  JSONSerialization.isValidJSONObject() function, and it returns false. I think this is incorrect behavior.
The original SwiftyJSON/SwiftyJSON behaves correct.
Proof of concept
func asJson() -> JSON {
	let user: JSON = [
		"name": "John Doe"
	]
	return [
		"alarmLevel": 123,
		"user": user
	]
}

func main() {
	let json = asJson()
	let s = json.rawString() ?? "ERROR"
	print(s)
}

Output 1 - using SwiftyJSON/SwiftyJSON
{
  "alarmLevel" : 123,
  "user" : {
    "name" : "John Doe"
  }
}

Output 2 - using IBM-Swift/SwiftyJSON
ERROR

Environment

Xcode 8.2.1
macOS 10.12.1
I have not investigated this on Linux.
IBM-Swift/SwiftyJSON, 5ca3f000588b49a3184271c21d36ade1205d81b2, 2016 Dec 19
SwiftyJSON/SwiftyJSON, d6e1c7e45455ea7db41cca254c428e07400b0d28, 2017 Feb 24

Unit test pull request
I have submitted a PullRequest to the original SwiftyJSON project containing a unittest that recreates this problem.
Ugly work around
One solution could be to make sure that JSONSerialization.isValidJSONObject() never sees any JSON instance.
Something like this:
public func rawData(options opt: JSONSerialization.WritingOptions = JSONSerialization.WritingOptions(rawValue: 0)) throws -> Data {
	/// Replace occurrences of JSON dictionaries with [String: Any]
	func process(_ rawObject: Any) -> Any {
		if let rawDictionary = rawObject as? [String: Any] {
			var dict = [String: Any]()
			for (key, value) in rawDictionary {
				dict[key] = process(value)
			}
			return dict
		}
		if let json = rawObject as? JSON {
			if let rawDictionary: [String: Any] = json.dictionaryObject {
				var dict = [String: Any]()
				for (key, value) in rawDictionary {
					dict[key] = process(value)
				}
				return dict
			}
		}
		return rawObject
	}
	let obj: Any = process(self.object)
	guard JSONSerialization.isValidJSONObject(obj) else {
		throw SwiftyJSONError.errorInvalidJSON("JSON is invalid")
	}
	return try JSONSerialization.data(withJSONObject: obj, options: opt)
}

It doesn't deal with arrays.

As of Kitura 2 we no longer use SwiftyJSON so I'm closing this issue.  Thank you for reporting it.


README.rst: Library => library

Thanks! :)
Merged in: https://github.com/jonathanslenders/python-prompt-toolkit/commit/8e78bfa2948a094298416edfda9fb3e07d3705b9


Run 1 Plan

I brought the Run 1 plan up to date here, but it needs some gaps filling in.

[ ] @jbkalmbach can you please edit the lens sprinkling paragraph for accuracy? We should say roughly how many lenses are being put in.
[ ] @rbiswas4 can you please add a paragraph with what your plan is for including SNe in the Run 1 images?
[x] @TomGlanzman based on your experience with generating images, can you please add a statement of how many images we can expect to be able to generate, in, say, one week?
[ ] @jchiang87 @danielsf Since we are running short on time, we might want to thin out the visit dates somehow: it would be annoying to generate 100 images and find that they were all taken in the same night. What's the easiest way to make a small image set that spans a whole 4-5 month season? Choose only the WFD visits? Or randomly downsample the list of visits?
[ ] @wmwv @SimonKrughoff can you please check through the plan and edit to fit? We need a link to the physics over-ride file, the name of the OpSim database we're using, maybe some more on what tests we must do before we show up at SLAC in March.
[x] @tony-johnson So far we don't say anything about workflow development, but we should. Can you please add a few sentences on how we are using the workflow engine, for posterity?

Thanks!

If you are using CatSim's ObservationMetaData generator to turn OpSim runs into CatSim pointings, it would be pretty easy to just query for all of the pointings that are on your desired patch of sky and then loop through them and only generate images from disparate nights.  I am imagining something that keeps track of the MJD of all previously generated images and refuses to generate an image for a specific pointing if its MJD is closer than some threshold to a previous image.
Are the images originating from Simon's generatePhoSimInput.py script in the Twinkles repo?  If so, I can put a pull request on that implementing what I have just described.

@danielsf Feel free to submit the PR, but what you propose sounds simple enough that we would just implement it ourselves as we'd need to generate the instance catalogs fairly soon, i.e., by some time early next week.

Based on rather limited experience (timing tests and pipeline workflow development), generating 1000 phoSim runs/images/visits over the course of a work week is a conservative estimate.  If there are no serious break-downs or resource bottlenecks, that number could be significantly larger, say x5 to x10, although the upper end of that range is speculative.  For the purposes of planning, please use 1000, but let's be prepared for 5000 in case we are lucky.

Here are plots of the cumulative number of visits for each band in kraken_1042 for our DDF (fieldID=1427).   Without downselecting:

and limiting to one visit per night per band:

We get about 40-50 visits per band per season (the vertical lines are at 150d intervals), so if we can generate ~1000 images, this corresponds to about 3 seasons.

I have added a paragraph on workflow and dataflow.

That's a lot of DDF visits: 25000 in 10 years! And so, about 2500 visits
per year, or (on average) about 400 visits per filter per year.
So, if we have the capacity to make a few thousand images between now and
the collaboration meeting, it looks as though we have a few good options:

Full DDF, from survey start to the end of season 1 (MJD 60000) - c. 2500
visits

3 seasons of WDF (c. 300 visits) plus 1 season of DDF ugriz (c. 2000
visits)

10 seasons of nightly downsampled DDF (c. 2500 visits)

Some other permutation?

@wmwv @rbiswas4 What would be best for the early SN tests you'd want to do,
before or at the collaboration meeting? Do you need the DDF time sampling?
Or multiple seasons? I like option 2, because it shows us what the WDF
(main survey) cadence looks like. I'm not sure how important the y band is
to you though (you could always drop a different one - or go with less than
a season - etc)
On Fri, Feb 5, 2016 at 3:51 PM, James Chiang<EMAIL_ADDRESS>wrote:

Here are plots of the cumulative number of visits for each band in
kraken_1042 for our DDF (fieldID=1427). Without downselecting:
[image: all_visits_kraken_1042_fieldid_1427]
https://cloud.githubusercontent.com/assets/1994473/12862358/b775f7a8-cc1f-11e5-9dc3-099da0dc3a60.png
and limiting to one visit per night per band:
[image: one_visit_per_night_kraken_1042_fieldid_1427]
https://cloud.githubusercontent.com/assets/1994473/12862365/d1fc1e22-cc1f-11e5-80d3-f15e11fd3fde.png
We get about 40-50 visits per band per season (the vertical lines are at
150d intervals), so if we can generate ~1000 images, this corresponds to
about 3 seasons.
—
Reply to this email directly or view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/110#issuecomment-180627450
.

BTW: another nice feature of option 2 is that it would get us into the
habit of switching between the WFD and DDF proposals in our analysis.
On Mon, Feb 8, 2016 at 8:54 AM, Phil Marshall<EMAIL_ADDRESS>wrote:

That's a lot of DDF visits: 25000 in 10 years! And so, about 2500 visits
per year, or (on average) about 400 visits per filter per year.
So, if we have the capacity to make a few thousand images between now and
the collaboration meeting, it looks as though we have a few good options:

Full DDF, from survey start to the end of season 1 (MJD 60000) - c.
2500 visits

3 seasons of WDF (c. 300 visits) plus 1 season of DDF ugriz (c. 2000
visits)

10 seasons of nightly downsampled DDF (c. 2500 visits)

Some other permutation?

@wmwv @rbiswas4 What would be best for the early SN tests you'd want to
do, before or at the collaboration meeting? Do you need the DDF time
sampling? Or multiple seasons? I like option 2, because it shows us what
the WDF (main survey) cadence looks like. I'm not sure how important the y
band is to you though (you could always drop a different one - or go with
less than a season - etc)
On Fri, Feb 5, 2016 at 3:51 PM, James Chiang<EMAIL_ADDRESS>wrote:

Here are plots of the cumulative number of visits for each band in
kraken_1042 for our DDF (fieldID=1427). Without downselecting:
[image: all_visits_kraken_1042_fieldid_1427]
https://cloud.githubusercontent.com/assets/1994473/12862358/b775f7a8-cc1f-11e5-9dc3-099da0dc3a60.png
and limiting to one visit per night per band:
[image: one_visit_per_night_kraken_1042_fieldid_1427]
https://cloud.githubusercontent.com/assets/1994473/12862365/d1fc1e22-cc1f-11e5-80d3-f15e11fd3fde.png
We get about 40-50 visits per band per season (the vertical lines are at
150d intervals), so if we can generate ~1000 images, this corresponds to
about 3 seasons.
—
Reply to this email directly or view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/110#issuecomment-180627450
.

@rbiswas4 @jchiang87 @TomGlanzman Let's look at the Run 1 plan together on Thursday. I think we can finalize the plan and close out this issue without anyone else's help at this point!

OK, I think the Run 1 plan is more or less complete. Please take a look and see what you think, edit as you see fit - I added notes from today's hangout on the tests we think we want to do on the light curves (kept as simple as possible to get started).

Declaring victory, only 27 days after Run 1 was released!


keep leading slash in catalog file path

Avoids removing leading / in a path provided to a catalog before reading the file.
fixes #225
Signed-off-by: Tim Robinson<EMAIL_ADDRESS>

created as draft before some quick local tests are completed

local test with invocation:
./iascable build -i /Users/timro/Public/ISV/software-automation/watson-boms/roks-new-nlp/bom.yaml -c https://modules.cloudnativetoolkit.dev/index.yaml -c file:/Users/timro/Public/ISV/software-automation/watson-embedded-catalog/catalog.yaml

passed, updating from draft.


Be able to define bursty traffic

Perhaps there is a way to do it with existing functionality but I would like a way to generate bursty traffic.
By that I would mean : define it in terms of standard deviations or multiples of baseline load for a certain interval.
So for now, if I have a N single workers I will have on average M = N * (min_wait + max_wait) /2  requests per second made.
What I would like is - every K seconds  increase the load to say M * L requests per second for J seconds, where J,K,L > 1
Thoughts?

Two locusts? One for baseline and another for the burst? Your "burst" locust could sleep for K seconds and repeat. That's what I would do.

What @4tapsmobile  is suggesting might work for you.
It should also be fairly easy to achieve by overriding the wait method in your TaskSet, which is the method that each running Locust user calls between each task execution. (https://github.com/locustio/locust/blob/ab6f330eb0abe324b6b7ce6a7406e5093b91c021/locust/core.py#L327)
Here's a start:
from time import time
from locust import TaskSet

class BurstingTaskSet(TaskSet):
    K = 10
    J = 3
    burst_wait_time = 0.1

    bursting = False
    interval_start = time()

    def set_bursting(self):
        if not self.bursting and time() - self.interval_start > self.K:
            self.bursting = True
            self.interval_start = time()
        elif self.bursting and time() - self.interval_start > self.J:
            self.bursting = False
            self.interval_start = time()

    def wait(self):
        self.set_bursting()
        if self.bursting:
            self._sleep(self.burst_wait_time)
        else:
            super(BurstingTaskSet, self).wait()

If you want to synchronise the bursting between a lot of running locust users (which take time to spawn, and might run distributed on different servers), you probably want to add some synchronisation logic that uses the system clock.


smp: try out a realllllllly high context count to see what memory usage is like

Added this in 8d0f1e7f93e0ca3b6bf3723eb5d6a9c6ece57497.


Documentation-webpage is broken

Hello
The documentation-webpage seems to be broken.
Regards

I'll write to readme.io it seems to be a bug on their website

They fixed it


Better unused warning

In a pest file, there will be always have a grammar_rule is not used. But that is the final rule, so the extension it will always show the unused warning.

Duplicate of #14


Refactor verification function with Opts struct

Description

Per RFC 3161 2.2, we need to support the following for verification:

[ ] Verify that the TSR's hashed message matches the digest of the artifact to be timestamped
[ ] Verify the TSR's ESSCertID, the certificate identifier, matches a provided TSA certificate (kind of done here, but see below for note on updating to support out-of-band provided leaf)
[ ] If embedded in the TSR, verify the TSR's leaf certificate matches a provided TSA certificate
[ ] Verify the TSA certificate using a CA certificate chain
[ ] Verify the TSA certificate and the intermediates (called "EKU chaining") all have the extended key usage set to only extended key usage - See https://github.com/sigstore/timestamp-authority/blob/main/pkg/x509/x509.go#L35 - Note that the pkcs7 library verify does not check this
[ ] Verify the signature of the TSR using the public key in the leaf certificate (like here)
[ ] Verify the OID of the TSR matches an expected OID
[ ] Verify the status of the TSR does not contain an error
[ ] Verify the nonce - Mostly important for when the response is first returned

Note that the leaf certificate may be provided out of band, as it is not a requirement that the certificate is embedded in the TSR. verifySignature from the pkcs7 library seems to expect that the certificate is present always. We'll need upstream changes I think to update verification to support TSRs without certificates.
It looks like there are more errors in the pkcs7 verification logic - for example, https://github.com/digitorus/pkcs7/blob/21b8b40e6bb42e43036336c7828a1bee77c2b1d6/verify.go#L157 assumes that all certificates stored in the pkcs7 certs struct are intermediates (so I don't think verification even works if you have a chain with an intermediate? Haven't confirmed though, please do). Upstream fixes are probably needed. I'd avoid reimplementing signature verification (complex!, so let's try to fix in upstream, and we can work off my fork for now.
EDIT:  Verification works in our code because we read in all certificates into a single cert pool, and those are called the "trust store" roots - Since the leaf is in this cert pool, and the leaf is in the p7.Certificates, then verification passes because it'll find a "chain" from leaf to leaf. This is ok to use as long as we also verify the certificate chain ourselves, but I think it's worth still figuring out how to redesign this in upstream. Something like VerifyWithChain here taking a root pool, intermediate pool, optional leaf certificate, and optional EKU.
The Opts pattern we've followed from Cosign has worked well, so I'd recommend we do the same here.
type VerificationOpts struct {
  oid asn1.ObjectIdentifier
  TsaCertificate *x509.Certificate
  Intermediates *x509.CertPool
  Roots *x509.CertPool
  Nonce string
}

Blocked by https://github.com/sigstore/timestamp-authority/issues/119
@malancas did you want to take a look at this?

Also worth confirming that all verification we're doing includes what openssl does

@haydentherapper sure, I'll take a look.

@malancas Just checking in on issues, any updates for this one?

@haydentherapper I'm making progress on this issue and am planning to post some PRs for this on Wednesday.


[CMAKE]SDL2 Curl Zlib build failure

Host Environment

OS: Windows 10 Pro Version 1909 Build 18363.900
Compiler: Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Framework

To Reproduce
Steps to reproduce the behavior:
.\vcpkg install sdl2 curl
Failure logs
PS C:\vcpkg> .\vcpkg install sdl2 curl
Computing installation plan...
The following packages will be built and installed:
curl[core,non-http,ssl,sspi,winssl]:x86-windows
sdl2[core]:x86-windows

zlib[core]:x86-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/3: zlib:x86-windows
Building package zlib[core]:x86-windows...
-- Downloading http://www.zlib.net/zlib-1.2.11.tar.gz...
CMake Error at C:/vcpkg/scripts/cmake/vcpkg_download_distfile.cmake:185 (file):
file RENAME failed to rename
/c/vcpkg/C:/vcpkg/downloads/temp/zlib1211.tar.gz

to
/c/vcpkg/C:/vcpkg/downloads/zlib1211.tar.gz

because: No such file or directory
Call Stack (most recent call first):
C:/vcpkg/ports/zlib/portfile.cmake:5 (vcpkg_download_distfile)
C:/vcpkg/scripts/ports.cmake:73 (include)
Additional context
Old installation of vcpkg broke after installing opencv, removed old installation.
Cloned and created new installation of vcpkg, followed steps from readme.
I've noticed the double directory

/c/vcpkg/C:/vcpkg/downloads/zlib1211.tar.gz

not sure if that's the issue.

./vcpkg install zlib:x86-windows
Computing installation plan...
The following packages will be built and installed:
zlib[core]:x86-windows
Starting package 1/1: zlib:x86-windows
Building package zlib[core]:x86-windows...
CMake Error at C:/vcpkg/scripts/cmake/vcpkg_download_distfile.cmake:82 (file):
file must be called with at least two arguments.
Call Stack (most recent call first):
C:/vcpkg/ports/zlib/portfile.cmake:5 (vcpkg_download_distfile)
C:/vcpkg/scripts/ports.cmake:73 (include)
Could not copy into file: C:\vcpkg\packages\zlib_x86-windows\share\zlib\vcpkg_abi_info.txt

Can you re-clone vcpkg in a non-system partition and try again?
Thanks.

PS D:\git\vcpkg> .\bootstrap-vcpkg.bat
Building vcpkg.exe ...
pch.cpp
archives.cpp
checks.cpp
chrono.cpp
cofffilereader.cpp
downloads.cpp
enums.cpp
files.cpp
hash.cpp
json.cpp
machinetype.cpp
parse.cpp
strings.cpp
stringview.cpp
system.cpp
system.print.cpp
system.process.cpp
unicode.cpp
binarycaching.cpp
binaryparagraph.cpp
build.cpp
buildenvironment.cpp
cmakevars.cpp
commands.autocomplete.cpp
commands.buildexternal.cpp
commands.cache.cpp
commands.ci.cpp
commands.ciclean.cpp
commands.contact.cpp
commands.cpp
commands.create.cpp
commands.dependinfo.cpp
commands.edit.cpp
commands.env.cpp
commands.exportifw.cpp
commands.import.cpp
commands.integrate.cpp
commands.list.cpp
commands.owns.cpp
commands.porthistory.cpp
commands.portsdiff.cpp
commands.search.cpp
commands.setinstalled.cpp
commands.upgrade.cpp
commands.version.cpp
commands.xvsinstances.cpp
dependencies.cpp
export.cpp
export.chocolatey.cpp
export.prefab.cpp
globalstate.cpp
help.cpp
input.cpp
install.cpp
logicexpression.cpp
metrics.cpp
packagespec.cpp
paragraphparseresult.cpp
paragraphs.cpp
portfileprovider.cpp
postbuildlint.buildtype.cpp
postbuildlint.cpp
remove.cpp
sourceparagraph.cpp
statusparagraph.cpp
statusparagraphs.cpp
tools.cpp
triplet.cpp
update.cpp
userconfig.cpp
vcpkgcmdarguments.cpp
vcpkglib.cpp
vcpkgpaths.cpp
versiont.cpp
visualstudio.cpp
vcpkglib.vcxproj -> D:\git\vcpkg\toolsrc\msbuild.x86.release\vcpkglib.lib
vcpkg.cpp
Generating code
Previous IPDB not found, fall back to full compilation.
All 18348 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
Finished generating code
vcpkg.vcxproj -> D:\git\vcpkg\toolsrc\msbuild.x86.release\vcpkg.exe
vcpkgmetricsuploader.cpp
Generating code
Previous IPDB not found, fall back to full compilation.
All 7760 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
Finished generating code
vcpkgmetricsuploader.vcxproj -> D:\git\vcpkg\toolsrc\msbuild.x86.release\vcpkgmetricsuploader.exe
Building vcpkg.exe... done.
Telemetry
vcpkg collects usage data in order to help us improve your experience.
The data collected by Microsoft is anonymous.
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics,
passing --disable-metrics to vcpkg on the command line,
or by setting the VCPKG_DISABLE_METRICS environment variable.
Read more about vcpkg telemetry at docs/about/privacy.md
PS D:\git\vcpkg> .\vcpkg integrate install
Applied user-wide integration for this vcpkg root.
All MSBuild C++ projects can now #include any installed libraries.
Linking will be handled automatically.
Installing new libraries will make them instantly available.
CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=D:/git/vcpkg/scripts/buildsystems/vcpkg.cmake"
PS D:\git\vcpkg> .\vcpkg install sdl2 curl
Computing installation plan...
The following packages will be built and installed:
curl[core,non-http,ssl,sspi,winssl]:x86-windows
sdl2[core]:x86-windows

zlib[core]:x86-windows
Additional packages (*) will be modified to complete this operation.
A suitable version of powershell-core was not found (required v6.2.1). Downloading portable powershell-core v6.2.1...
Downloading powershell-core...
https://github.com/PowerShell/PowerShell/releases/download/v6.2.1/PowerShell-6.2.1-win-x86.zip -> D:\git\vcpkg\downloads\PowerShell-6.2.1-win-x86.zip
Extracting powershell-core...
A suitable version of 7zip was not found (required v18.1.0). Downloading portable 7zip v18.1.0...
Downloading 7zip...
https://www.nuget.org/api/v2/package/7-Zip.CommandLine/18.1.0 -> D:\git\vcpkg\downloads\7-zip.commandline.18.1.0.nupkg
Extracting 7zip...
A suitable version of nuget was not found (required v5.5.1). Downloading portable nuget v5.5.1...
Downloading nuget...
https://dist.nuget.org/win-x86-commandline/v5.5.1/nuget.exe -> D:\git\vcpkg\downloads\nuget.exe
Starting package 1/3: zlib:x86-windows
Building package zlib[core]:x86-windows...
A suitable version of git was not found (required v2.26.2). Downloading portable git v2.26.2...
Downloading git...
https://github.com/git-for-windows/git/releases/download/v2.26.2.windows.1/PortableGit-2.26.2-32-bit.7z.exe -> D:\git\vcpkg\downloads\PortableGit-2.26.2-32-bit.7z.exe
Extracting git...
-- Downloading http://www.zlib.net/zlib-1.2.11.tar.gz...
CMake Error at D:/git/vcpkg/scripts/cmake/vcpkg_download_distfile.cmake:185 (file):
file RENAME failed to rename
/d/git/vcpkg/D:/git/vcpkg/downloads/temp/zlib1211.tar.gz

to
/d/git/vcpkg/D:/git/vcpkg/downloads/zlib1211.tar.gz

because: No such file or directory
Call Stack (most recent call first):
D:/git/vcpkg/ports/zlib/portfile.cmake:5 (vcpkg_download_distfile)
D:/git/vcpkg/scripts/ports.cmake:73 (include)
Error: Building package zlib:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: zlib:x86-windows
Vcpkg version: 2020.02.04-nohash
Additionally, attach any relevant sections from the log files above.
PS D:\git\vcpkg>

Can you re-clone vcpkg in a non-system partition and try again?
Thanks

Thank you for taking a look at the problem @JackBoosY
I've cloned it into my D: drive this time, same issues.

Seems it could be an issue with Cmake, possibly from a newer version.

Removed Cmake installation -> removed vcpkg -> cloned vcpkg -> did setup -> Redownloaded cmake from vcpkg -> installed SDL2 Curl = Success.
Seems it is an issue with Cmake, read some issues on gitlab which pointed to incorrect virtual directories and ninja.

@SufAfrican Yes, we need to wait for cmake to update.


NIFI-6748: Fixed bug in Parameter Contexts' affected components where…

… if a Controller Service referenced a Parameter, any component that references that service should also be considered an affected component but wasn't. Also fixed a bug in how we handled stopping a Processor that was in the STARTING phase.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...

Looks good, merging


ISPN-12074 Test progress messages are split over multiple lines

https://issues.redhat.com/browse/ISPN-12074
Workaround for https://issues.apache.org/jira/browse/SUREFIRE-1814

Thanks @danberindei


Recent vim changes seem to make loclist jumps go to wrong line

Sorry that this bug isn't great, I'm having a hard time tracking down what could have broken this. What I know so far is if I upgrade from vim 7.4.1583 to 7.4.1821, the loclist error references end up pointing to the wrong line (so hitting enter on them goes to the wrong line). This is with
let g:syntastic_check_on_open=0
let g:syntastic_auto_loc_list=1
let g:syntastic_python_checkers=['pylint']
let g:syntastic_enable_highlighting = 1

And specifically with the pylint checker, although I suspect that doesn't matter. Here's what changed between, there are a few quickfix/loclist-related changes, but I'm not familiar enough with the mechanism there to be more helpful :\

As I bisect, I realized that I was missing what was actually happening- when i hit enter on the line, i get the error message E926: Current location list was changed and the cursor just doesn't move (i.e. it's not that the locline points to the wrong line).
I'm currently bisecting, so hopefully i'll have an exact patch reference soon.

Okay, bisection complete. 7.4.1640 Is the first one that breaks.

.... Okay, apparently I was running an ancient version of syntastic. Running syntastic master, this is no longer a problem.

Okay, bisection complete. 7.4.1640 Is the first one that breaks.

Yeah, I could have saved you the time of doing the bisection and point you to #1127.

Running syntastic master, this is no longer a problem.

It's still a problem, it just doesn't happen as often.  Vim's API doesn't permit avoiding all problematic cases.
Vim patch 1640 is, well, not that great.  I suggested a much simpler approach that would have avoided the problem in the first place, but it looks like nobody has bothered to take the time to understand what I'm saying.  I'll probably have to drop check_on_open when running the forthcoming Vim 8. shrug


Add prettier message when syncing inexistent pair

Fixes #345

Thanks! Test fail though, you need to create a config first.

Yes, I noticed I broke a test but didn't get around to fixing it last night. I'll see if I can narrow down how I broke them later today. (feedback is welcome if it's more obvious to you though).

 It works now.

Interesting, credentials for the Davical server are not available on forks.
I will need to look into skipping those tests if the credentials are missing.

Thanks!


chmod change from 644 to 777

Task name: ContainerBuildV0, DockerInstallerV0, HelmInstallerV0, KubernetesV0, KubernetesV1
Description: Changing the chmod of the tasks from 644 to 777
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N) https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2014934
Checklist:

[ ] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

/azp run

Hey, any feedback on when the fix will be merged? Should we expect to have this released in the next sprint?


Replacing role usage with playbook

Depends-On: https://github.com/openstack-k8s-operators/edpm-ansible/pull/256

Depends-On: https://github.com/openstack-k8s-operators/dataplane-operator/pull/324

recheck


Xcode 12 'IPHONEOS_DEPLOYMENT_TARGET' warning

Please consider submitting the following information (if relevant):
The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99.

CocoaPods
Version of the library.
21.0.0
Xcode version.
12.0
OS version.
iOS 14

Hi @gilrodar, thanks for reporting the issue. Is it possible to isolate the issue in a small demo app and attach here so I can have a look?

I only added Cosmos with SwiftPackage and built the application with cmd + b. After that it shows this warning. But only with Xcode 12

That's good to know, I'll check that once Xcode 12 gets out of Beta.

I think Xcode 12 is no longer a beta.
You can download the version from the App Store.

I think Xcode 12 is no longer a beta.
You can download the version from the App Store.

Oh, I did not know that, thanks. I'll have a look.

Fixed in version 23.0. Let me know if it works for you.

Thanks, with Swift Package not update to version 23.0. :(

Oh, is there an error?

There is no error, only the version 23 is not downloaded. I give in update and the version 21 is kept.
I already deleted and re-downloaded and it still brings version 21.0.0

Computers suck! It worked for me though:
https://drive.google.com/file/d/112yn6rgGQRvIzbg-3vE_ucAV6m8a4Qk_/view?usp=sharing

It's working for me.

Ready it works, I had to delete the swift package and download it again and it brought me the 23.00 version


KIE forms jBPM integration:

Support for BeanValidation for dynamic models
Fixing minor issues

KIE forms jBPM integration:

Fixing binding strategy for jBPM

Merge with: https://github.com/droolsjbpm/kie-wb-common/pull/572
This PR reverts droolsjbpm/jbpm-console-ng#567
@cristianonicolai this is the easiest way I found to do it ;)

jenkins reterst this

jenkins retest this

jenkins retest this

@cristianonicolai https://github.com/droolsjbpm/kie-wb-common/pull/572 has been merged

@pefernan I am assuming the jbpm-console-ng build is broken, because the upstream kie-wb-common PR was merged and this one wasn't. Is that correct?

Merging as the same changes were approved by https://github.com/droolsjbpm/jbpm-console-ng/pull/560, which was than reverted, because the kie-wb-common PR wasn't merged at the same time.


Using the keyboard Alt shortcuts for menus and the arrow keys seems inconsistent

Issue Type: Bug
I wanted to open the Settings in VSC. I used (Alt+F, P) and "Preferences" was selected and the flyout menu for it opened. I then hit the right arrow key to move the selection and instead of moving the selection, the Edit menu was activated.   If I instead hit the down arrow twice, the selection moves to the flyout menu and starts moving down it
I'm not sure if this is a problem with the selection by keyboard, or that the selected item isn't actually what is selected.  Its not that big of a problem but it may end up being frustrating  after a while.
VS Code version: Code 1.39.0 (9df03c6d6ce97c6645c5846f6dfa2a6a7d276515, 2019-10-09T06:58:04.439Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.55GB (3.73GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.9.1

xml
Dot
2.5.0

vscode-solution-explorer
fer
0.3.5

beautify
Hoo
1.5.0

vscode-docker
ms-
0.8.1

mssql
ms-
1.6.0

python
ms-
2019.10.41019

remote-wsl
ms-
0.39.9

azure-account
ms-
0.8.6

azurecli
ms-
0.4.6

csharp
ms-
1.21.4

powershell
ms-
2019.9.0

vs-keybindings
ms-
0.2.0

team
ms-
1.149.2

(1 theme extensions excluded)

@sbatten - I'd expect an explanation for the closure, but the activity after it doesnt look like closing it was intended. Can you provide some info on this topic?

@StingyJack it's closed because I fixed the issue in commit https://github.com/microsoft/vscode/commit/2c535a36e9d6427261b537da0859dafb6f686357

As someone who probably reads a lot of things for a living, can you tell me which of these two descriptions is clearer?

Visual Studio 2019 on Windows 2019
windows-2019

If you didn't consider "clearer for what purpose", the purpose is to build an application with VS 2019.
It's also probably important to take into context that the other choices in the second items list all mention a version of visual studio.
If you said the first one was clearer, congratulations!
Hopefully it's not too late. If you can, please withdraw the commit at least until the issue I already have open with the target team is addressed.


[Bug]: v30-alpha.5 TestPathPatterns pattern-match regression

Version
30.0.0-alpha.5
Steps to reproduce
This can be demonstrated with jest's own examples/getting-started on a Window vscode powershell terminal:

clone https://github.com/jestjs/jest
copy the examples/getting-started to a new folder outside of Jest, so we can change the jest version freely.
goto this standalone getting-started folder
edit package.json to change the jest and babel-jest versions to 30.0.0-alpha.5
yarn install
run a specific test like this in a powershell terminal:

> yarn jest --testLocationInResults --testNamePattern "adds 1 \+ 2 to equal 3$" --no-coverage --colors --watchAll=false --testPathPatterns "c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js"

Expected behavior
Expect this to work just like with jest 29.x.
Edit package.json to update jest and babel-jest to 29.7.0; run yarn install then run the command again (replacing --TestPathPatterns with --TestPathPattern):
PS C:\Users\dev\github\open-source\getting-started> yarn jest --testLocationInResults --testNamePattern "adds 1 \+ 2 to equal 3$" --no-coverage --colors --watchAll=false --testPathPattern "c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js"
js";dbee3b2e-0ab6-4105-a99f-3a96e3b4cf5eyarn run v1.22.19                                             i
$ C:\Users\dev\github\open-source\getting-started\node_modules\.bin\jest --testLocationInResults --testNamePattern "adds 1 \+ 2 to equal 3$" --no-coverage --colors --watchAll=false --testPathPattern c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js
 PASS  ./sum.test.js
  √ adds 1 + 2 to equal 3 (2 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.669 s, estimated 1 s
Ran all test suites matching /c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js/i with tests matching "adds 1 \+ 2 to equal 3$".
Done in 1.23s.

Actual behavior
the pattern match failed so no test is run:
PS C:\Users\dev\github\open-source\getting-started> yarn jest --testLocationInResults --testNamePattern "adds 1 \+ 2 to equal 3$" --no-coverage --colors --watchAll=false --testPathPatterns "c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js"
yarn run v1.22.19
$ C:\Users\dev\github\open-source\getting-started\node_modules\.bin\jest --testLocationInResults --testNamePattern "adds 1 \+ 2 to equal 3$" --no-coverage --colors --watchAll=false --testPathPatterns c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In C:\Users\dev\github\open-source\getting-started
  4 files checked.
  testMatch: **/__tests__/**/*.?([mc])[jt]s?(x), **/?(*.)+(spec|test).?([mc])[jt]s?(x) - 1 match
  testPathIgnorePatterns: \\node_modules\\ - 4 matches
  testRegex:  - 0 matches
Pattern: c:\\Users\\dev\\github\\open-source\\getting-started\\sum\.test\.js - 0 matches
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Additional context

This issue only occurs on Windows. It works as expected on macOS, as far as I can tell.
Also noticed jest seems to perform a case-insensitive match for TestPathPattern in v29.x. Can't tell if v30 is doing the same.

Environment
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^30.0.0-alpha.5 => 30.0.0-alpha.5

@SimenB any insight on this issue?

@SimenB, sorry to ping you again. This issue has blocked the release of our jest@30 support PR (jest-community/vscode-jest#1153). Has the path-regex-matching algorithm changed intentionally? The same path pattern is recognized in v29 but not in v30. If this is a breaking change in v30 and not a bug, please let us know the right path forward so we can fix the PR and start to support jest@30 users.

I've been investigating this issue further and it looks like the problem might be related to TestPathPatterns.regexString(), specifically in how it prefixes rootDirRegex.
It seems that the current implementation only considers POSIX-style path patterns and might be missing Windows absolute path patterns, like c:\\dir\\test-file\.test\.ts, which were supported in earlier Jest versions.
This looks like a bug to me, cc @SimenB and @brandonchinn178 for insights and actions.

It looks like the issue is line 29, right? It assumes an absolute path starts with a slash, but that's not true in Windows.
Does look like a bug. Not sure what the correct fix is, I don't work with Windows paths too much. Should it also check for \w:\\?


Batch remove the images

Through the UI:

I can only delete the image one by one
everytime when I delete it, the page will do not refresh automatically
no way to batch remove multiple images only if you delete the project

We'll see the refresh issue.
Currently we don't plan to support deleting multiple images on UI.

just need some checkboxes.

@moooofly thanks for the response

@bibotai have a try with harbor-go-client

Batch remove from UI is supported, additionally as pointed out in previous comment, you can use the client developed by community user to to batch deletion.


Bug in the version published in ArtifactHub

Hi guys, there seems to have been a bug in the latest version change in ArtifactHub.

What's the bug? We bumped the major version on purpose, since the chart is considered stable now

Shouldn't the package jump to version 1.0.0?

Why? We don't use semver


Automated cherry pick of #1474: fix: service catalog nil pointer

Cherry pick of #1474 on release/2.11.0.
#1474: fix: service catalog nil pointer

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11.0@a109e17). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.11.0   #1475   +/-   ##
================================================
  Coverage                  ?   7.69%
================================================
  Files                     ?     411
  Lines                     ?   62816
  Branches                  ?       0
================================================
  Hits                      ?    4835
  Misses                    ?   57573
  Partials                  ?     408

Flag
Coverage Δ

#aFlag
7.69% <0%> (?)

Impacted Files
Coverage Δ

pkg/keystone/models/identity_provider.go
2.27% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm
/approve


Multiple Second Delay when using in a git repository

Is there an existing issue for this?

[X] Yes, I have searched the existing issues
[X] Yes, I have checked troubleshooting page

The problem
When using zsh running spaceship-prompt in a git repository, running any command comes with a multi-second delay.
Relevant Zsh configuration
SPACESHIP_USER_SHOW="always";
SPACESHIP_USER_COLOR="green";
SPACESHIP_DIR_PREFIX="| ";
SPACESHIP_DIR_COLOR="yellow";
SPACESHIP_EXEC_TIME_SHOW="true";
SPACESHIP_EXEC_TIME_COLOR="green";

What is version of Spaceship are you using?
3.16.1
What is version of Zsh are you using?
zsh 5.8 (x86_64-pc-linux-gnu)
What operation system are you running?
Linux
Do you use any Zsh framework or plugin manager?
No response
Which terminal emulator do you use?
Kitty
Additional information
This has only started happening recently.

Check sections which need network connecting and disable them, such as Kubernetes and Docker and so on

Check sections which need network connecting and disable them, such as Kubernetes and Docker and so on

Doing this seemed to have no effect. I'm guessing it has something to do with the git section since it only happens inside git repos.

@Slips-PC I also have a similar issue inside git repos, the only difference is that i have fish instead of zsh.

@Slips-PC  Is your git repo large? Can I get a repo to reproduce?

@Slips-PC Is your git repo large? Can I get a repo to reproduce?

@Runrioter No, not particularly.
Try this one: https://git.envs.net/Slips/clementeyene
It's just 3 files.
(Sorry for the non-github link, I don't really use github all that much beyond issue posting.)

Here is a video of what my issue looks like:
https://www.slipfox.xyz/files/1105-example.mp4

@Slips-PC  which version of git do you use?

2.34.1-1, latest in the Arch repos.

Any update on why this may be happening?

Should be resolved in 4.x. Reopen if needed.


Incompatibility with timezone and utc props

Describe the bug
When i set timezone and utc props, the date value was bad caclculated
UTC date was calculated from the browser timezone instead of the timezone passed as props
To Reproduce

go to (https://stackblitz.com/edit/nuxt-starter-u8yvpj?file=app.vue)[https://stackblitz.com/edit/nuxt-starter-u8yvpj?file=app.vue]
change the date and show the value displayed upside the input

Expected behavior
When timezone and utc props was used, compute the value from the timezone props instead of browser timezone
Desktop & mobile (please complete the following information):

Browser: Chrome and Arc
Library version: 5.4.0

They are basically the same prop, utc was only supported before the timezone prop was added. In your case, the check for utc is before the one for the timezone.


Item Properties(name, keywords, roomdesc) not hydrating properly.

To replicate:
Load an item from item definition in datasource. Modify the name, keywords, or roomdesc. Save the player. Quit the game. Login again. It will reset to the original name, keywords, and roomdesc.
This seems to be an issue with hydrating, not serializing.  Look at hydrate method in Inventory.js, aprox lines 86 - 110.
hydrate(state, belongsTo) {
    // Item is imported here to prevent circular dependency with Item having an Inventory
    const Item = require('./Item');

    for (const [uuid, def] of this) {
      if (def instanceof Item) {
        def.belongsTo = belongsTo;
        continue;
      }

      if (!def.entityReference) {
        continue;
      }

      const area = state.AreaManager.getAreaByReference(def.entityReference);
      let newItem = state.ItemFactory.create(area, def.entityReference);
\\=======================================================
\\ The line above this is where the item is created exactly from entityReference.
\\ Currently the 'serialized' state of the item is saved in def.
\\=======================================================
      newItem.uuid = uuid;
      newItem.belongsTo = belongsTo;
      newItem.initializeInventory(def.inventory);
      newItem.hydrate(state, def);
\\=======================================================
\\ Here the serialized def is passed into hydrate on the newly created item.
\\=======================================================
      this.set(uuid, newItem);
      state.ItemManager.add(newItem);
    }
  }
}

  hydrate(state, serialized = {}) {
\\=======================================================
\\ serialized data is saved in serialized
\\=======================================================
    if (this.__hydrated) {
      Logger.warn('Attempted to hydrate already hydrated item.');
      return false;
    }

    // perform deep copy if behaviors is set to prevent sharing of the object between
    // item instances
    if (serialized.behaviors) {
      const behaviors = JSON.parse(JSON.stringify(serialized.behaviors));
      this.behaviors = new Map(Object.entries(behaviors));
    }
\\=======================================================
\\ serialized gets used here to set the behaviors
\\=======================================================
    this.setupBehaviors(state.ItemBehaviorManager);

    this.metadata = JSON.parse(JSON.stringify(serialized.metadata || this.metadata));
\\=======================================================
\\ and here for the metadata
\\=======================================================
    this.closed = 'closed' in serialized ? serialized.closed : this.closed;
    this.locked = 'locked' in serialized ? serialized.locked : this.locked;

    if (typeof this.area === 'string') {
      this.area = state.AreaManager.getArea(this.area);
    }

    // if the item was saved with a custom inventory hydrate it
    if (this.inventory) {
      this.inventory.hydrate(state, this);
    } else {
    // otherwise load its default inv
      this.defaultItems.forEach(defaultItemId => {
        Logger.verbose(`\tDIST: Adding item [${defaultItemId}] to item [${this.name}]`);
        const newItem = state.ItemFactory.create(this.area, defaultItemId);
        newItem.hydrate(state);
        state.ItemManager.add(newItem);
        this.addItem(newItem);
      });
    }

    this.__hydrated = true;
  }

Nowhere does it set the other properties though. I believe it should be
name, keywords, roomdesc, desc

Your code is out of date, they were added in 361ddd6bbe8c42fbd0a2189ac0dbf017f1254fe1

oh my god!  you're so very right. Thanks Shawn.


About modal API needs review following changes

Noted that the additionalInfo is still an array, but we are only rendering the first element.
While it might be useful to cope with and without array the array version should be deprecated if no longer apprpriate

@glapadre as you recently changed this is it one you can pick up? I'll be. happy to review.

@davidmenendez thanks for jumping on this, I just saw this message!


more testing

more testing would be nice

Ideas:

different relative paths for output files and data dirs
invalid paths
invalid combinations of arguments


Error when running "make uhdm/yosys/test-ast"

I follow the step of Verilator setup and Yosys setup. Then I run "make uhdm/yosys/test-ast" in uhdm-integration for both Yosys and Verilator. However, both of them don't work.
The Error for Yosys is shown below:
rm -rf /home/houpeijun/peijunh/yosys/uhdm-integration/build
mkdir -p /home/houpeijun/peijunh/yosys/uhdm-integration/build
(cd /home/houpeijun/peijunh/yosys/uhdm-integration/build &&
/home/houpeijun/peijunh/yosys/uhdm-integration/../image/bin/surelog -parse -sverilog -d coveruhdm   /home/houpeijun/peijunh/yosys/uhdm-integration/tests/onenet/top.sv)
[INF:CM0023] Creating log file ./slpp_all/surelog.log.
[FTL:CM0008] Verilog File "/usr/local/lib/surelog/sv/builtin.sv" does not exist.
[  FATAL] : 1
[ SYNTAX] : 0
[  ERROR] : 0
[WARNING] : 0
[   NOTE] : 0
make: *** [surelog/parse] Error 1

And the Error for Verilator is shown below:
make uhdm/verilator/test-ast
rm -rf /home/houpeijun/peijunh/verilator/uhdm-integration/build
mkdir -p /home/houpeijun/peijunh/verilator/uhdm-integration/build
(cd /home/houpeijun/peijunh/verilator/uhdm-integration/build &&
/home/houpeijun/peijunh/verilator/uhdm-integration/../image/bin/surelog -parse -sverilog -d coveruhdm   /home/houpeijun/peijunh/verilator/uhdm-integration/tests/onenet/top.sv)
[INF:CM0023] Creating log file ./slpp_all/surelog.log.
[FTL:CM0008] Verilog File "/usr/local/lib/surelog/sv/builtin.sv" does not exist.
[  FATAL] : 1
[ SYNTAX] : 0
[  ERROR] : 0
[WARNING] : 0
[   NOTE] : 0
make: *** [surelog/parse] Error 1

Your Surelog install directory is not following the expected location (/usr/local/bin/surelog) after intall.
Please add -nobuiltin to the Surelog command line in the meantime.
Check your install path.

Merci @alaindargelas. This is resolved.


Upgrade minor versions of sbt, scala and libraryDependencies

This pull request upgrades minor versions of sbt, scala and libraryDependencies.
I've checked dependencies' latest versions by using sbt-updates.

Bump sbt 0.13.7 to 0.13.8
Bump Scala minor versions (also Travis settings)
Bump scalatest, scalacheck, caliper stuff and so on
Bump sbt-pgp 0.8 to 1.0.0 (I'm already heavily using in my projects)

Seems like a transient build error. I'm re-running, will merge if it passes.
Thanks!

It seems like the build keeps stalling and getting killed by Travis.
Have you completed a clean build? Any sense of how long you expect it to take? It's possible one of these upgrades extended the duration in 2.10 until the build doesn't finish on time.

I just tried sbt ++2.10.5 clean test again and that successfully finished in 493 seconds on my machine. Would you rerun the Travis job?

So at this point I've run the build 4-5 times and it's failed every time.
It seems like we're just exceeding Travis' maximum time allowed without output.

I'll try to look into possible ways to speed up the build under 2.10. I'm nervous about giving up on 2.10 in Travis, since it has caught real compatibility bugs. I guess we'll see.

Thanks. After doing rm -rf */target, this problem represented on my machine too. I'll investigate more on that.

Hey there,
Sorry to possibly conflict with you on #419 -- this was something I was working on before this PR came in. If that gets merged I can try to help update this PR to get it merged as well.

just rebased against the master branch although I've not fixed the Scala 2.10 build issue yet..

In the short term, you might want to try reverting to 2.10.2 and see if the rest of it works.
We chose not to upgrade to 2.10.3 or 2.10.4 because the compile times were way too slow, and there weren't any obvious problems we noticed with 2.10.2. So I'd be fine with leaving it back here as well.

Thanks. I just reverted Scala 2.10 minor version and Travis build looks fine. https://github.com/seratch/spire/commit/7df155e1c1a254f7f5d4c3984347005db8fdb35a

Merging. Thanks!


Virtualmin Server Dropdown

Just installed your theme and it seems very impressive. One immediate thing I noticed however was that the older version of the Virtualmin theme italicised disabled severs in the Server drop down menu (top left) while yours does not. This was a very useful feature to identify quickly the status of servers.
Also - a small point; the character limit on the server name in the drop down can be increased (now that your theme uses a smaller font size in the drop down).. but perhaps this is a webmin thing.
Many thanks

Hi,
Yes, you can control the length in Virtualmin Configuration.
I mark disabled servers in red. What version of the theme are you using?

You mean when they are not selected.. I see. Ok

Yes exactly Ilia - when they are not selected.
Thanks also for domain character length tip - I never saw that before.
Many thanks

You are welcome. :)

It will be working in 17.40.
Meanwhile, if you want it already just add this to theme->extensions->js the following:
t__wi_p.$("aside select").on("select2:open", function (a) {
			$.each($("select > option"), function () {
				if ($(this).attr("style") && $(this).attr("style").indexOf("italic") > -1) {
					var $this = $(this);
					setTimeout(function () {
						t__wi_p.$("body").find('li[id$="' + $this.attr("value") + '"]').attr("style", "color: #e73c38 !important; font-style:italic !important; ")
					}, 1);
				}
			})
		});

Tell me if it's what you expected.
Don't forget to remove it when upgrading to 17.40.

FYI - I tried this and it made no difference for me but I'm happy to wait for next version.
010

Well. Save the file and hard reload the theme (Ctrl+R or Shift+Ctrl+R)


Publish v1.2.0 to npm

Hi,
can you please publish the recent version to npmjs?
https://www.npmjs.com/package/angular-resizable

+1

Done. Sorry about that guys...


support jpa

support jpa

JPA won't be supported since Spring Fu only targets reactive stack, but reactive and coroutines API for SQL databases will be available via #14 .


Installing on Ubuntu

Please i need steps to install this tool on my ubuntu.
Thank you

sudo apt install libboost-all-dev cmake build-essential
cmake -DCMAKE_BUILD_TYPE=Release . && make
mv axmldec ~/.local/bin/

sudo apt install libboost-all-dev cmake build-essential

FWIW, I'm on Ubuntu 22.04 and instead of libboost-all-dev, which installs a lot of packages, for me, it was sufficient to install the following subset:
sudo apt install libboost-dev libboost-system-dev libboost-iostreams-dev libboost-program-options-dev libboost-locale-dev

Disclaimer: It could be that there are other libboost-*-dev packages that I had installed from previous software installs on this machine.


Fix nondeterminism with environment markers #5239

Thank you for contributing to Pipenv!
No problem
The issue
What is the thing you want to fix? Is it associated with an issue on GitHub? Please mention it.
Fixing #2927 5239
The fix
We were using set to keep track of constraints, this changed their order leading to nondeterministic behaviour.
The checklist

[X] Associated issue
[X] A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

I'm not able to say much about the change, because the tests break. Should the test also be modified?

hmmm, let me check the tests. I thought they might flaky, but this seems more than flake.

I'm not able to say much about the change, because the tests break. Should the test also be modified?

@oz123 I think it is Fixed now. most of the tests are passing, but I am not sure if what I have done is in line with what the algorithm expects.

Looks like there are some other places in the code that are still calling .add() to add a constraint. The test failures have more details.

fixed :D. I did actually run the tests, but then pushed when they started taking too long to finish :D.

The changes proposed look alright for me. However, I am wondering if ordered-set is a more appropriate solution.
It keeps the set, but adds order like a list.
An ordered set recipe can be floating around, and we can simply add it to our utils.

What about a sorted set vs an ordered set so that we get a consistent ordering regardless of the order things are added in?

The changes proposed look alright for me. However, I am wondering if ordered-set is a more appropriate solution.
It keeps the set, but adds order like a list.
An ordered set recipe can be floating around, and we can simply add it to our utils.

It is a good idea, specially that then it would maintain the functionality of the code the same. The main draw back of the list is that it can have duplicates and I don't have a clue what that would entail.
The con is that we'd have to add an extra library for the ordered set.
@matteius I don't think sorted set would work.

One more option is to use a set and a list together in these 2 places and just check the set before inserting in the list.

@bakhtiary Well technically there is a SortedSet implementation that would work, but it would probably be simpler to use "use collections.OrderedDict from the Python standard library with just keys (and values as None) for the same purpose."  https://stackoverflow.com/questions/1653970/does-python-have-an-ordered-set

But as @oz123 said we can also make our own ordered-set. We can make it using a list and a set or using the dict which is ordered since python 3.6.
Or we can vendor either the OrderedSet or the ordered-set package.
These are all easy, just tell me which one and I'll get it done in a second :smiley_cat: I personally like the orderedset based on the dict Idea.

@bakhtiary I was thinking we could use collections.OrderedDict and then just sorted(d.keys()) without having to add any new code.

@bakhtiary I was thinking we could use collections.OrderedDict and then just sorted(d.keys()) without having to add any new code.

Oh I see. you are right. I believe the orderedDict will give us the keys in the order they were inserted.
I think it would work. should I do it?

@bakhtiary Yeah OrderedDict feels like the cleanest solution to me in terms of least amount of memory and least additional code added.   We can probably sort the keys to be safe before we pass them as constraints, seeing as how the ordering upstream might change and I would be surprised if the ordering mattered for the actual correct application of the constraints.  We can debate this point about the sorting -- but what I really don't understand and I think to be true, is if we add a new package the markers for an existing package could completely convert to a different type of marker because technically the set and ordering could and would change when adding new dependencies.  Determinism is good though; consistency will probably be the next thing we will want to figure out in a separate effort.

I'm glad I triggered such a good discussion.
The package ordered-set has very unpleasant code to read imo. Compared to the original recipe
Therehttps://github.com/ActiveState/code/blob/3b27230f418b714bc9a0f897cb8ea189c3515e99/recipes/Python/576696_OrderedSet_with_Weakrefs/README.md.
However, the idea of using a dictionary with keys only as a set replacement is my favorite.
It might not be straight forward for people who read the code in the future so it's worth adding a comment.
Also, we don't need ordereddict. All dictionaries in python 3.6+ are ordered.
@bakhtiary sorry for sending you for another round of work on this. Thank you for your patience and work on this issue. 🤗

I somehow accidentally closed this. I have opened another PR here: https://github.com/pypa/pipenv/pull/5286. feel free to revive this PR and delete the other one if there is a way.

@matteius This PR some how was accidentally closed. It was not merged. I opened a new one here: https://github.com/pypa/pipenv/pull/5286


[Feature Request]  Setting to define the composer.json location

Hello,
Could you add a new setting to set the location of the composer.json file explicitly?
Thanks

I think vscode doesn't allow extension configuration at the workspace level, unless you manually create the .vscode/settings.json file.
Anyway, I don't understand in which case you would need to manually define the location of the composer.json file, since the extension itself finds the closest composer.json starting from the folder in which you want to create the class, and iterating back one level above until it finds composer.json.

Folder composer: \include\libs\composer\composer.json
Folder application with structure: \application
in composer.json
"psr-4": {
"Application\": "../../../application"
}
I have problem on New Class in application folder: The composer.json file could not be found

@YanKolosovsky I just published an update with this feature.
Now, in the extension settings, there is a new option Composer File path where you can specify the relative path to the composer.json file.
This setting can be setted at workspace level (useful in your case) and at User/global level (is not really useful).
In your case, the path would be include/libs/composer/composer.json.
Note that the slashes are "unix style" but not like in Windows, for compatibility.


can't update or install apps

I can't update or install apps. Has anyone else had this and can anyone help? This is frustrating

Me too someone please help I try to install a tweak or something and it stays on loading screen forever.

I am trying to install App Store apps. I'm fine with tweaks

My App Store doesn't update either

Unrelated to jailbreak, BUT seeing how im here, FIRST hold power and home for 10 sec let your shit reboot. THEN go into itunes, and log out.

That's odd. My App Store works just fine.
Did you download the IPA from @kpwn's website? If not, that might be the problem: You added a backdoor to your own phone. And it doesn't have a single lock.

Can you send a link
Sent from my iPhone

On Feb 2, 2017, at 10:10 PM, Albert Tang<EMAIL_ADDRESS>wrote:
That's odd. My App Store works just fine.
Did you download the IPA from @kpwn's website? If not, that might be the problem: You added a backdoor to your own phone. And it doesn't have a single lock.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Cannot get command to work

Hi there, first of all thanks for this action.
I've looked through the open issue but could not find any solution to this.
I attempt to dynamically spawn multiple jobs based on a multi-dimensional array containing the test files which is produced by a nodejs script in a prepare job using the matrix strategy.
// the array, for sake of simplicity
TEST_CHUNKS = [  [ foo.js, bar.js ], [ baz.js, qux.js ] ]

The job configuration
- name: run cypress
  uses: cypress-io/github-action@v2
  if: always()
  with:
    ci-build-id: ${{ needs.prepare.outputs.uuid }}
    install: false
    start: npm run dev
    wait-on: 'http://localhost:3000'
    command: echo $TEST_CHUNKS | jq '.[${{ matrix.chunk-idx }}] | join(",")' | xargs npm run cypress:run -- --spec

Note: matrix.chunk-idx comes from a prepare job that provides the indexes of the TEST_CHUNKS array
The log reveals, that the TEST_CHUNKS exists in the env
Run cypress-io/github-action@v2
  with:
    ci-build-id: sha-baac7166eaeda54633e1473293450254ed0c0b0f-time-1639841791
    install: false
    start: npm run dev
    wait-on: http://localhost:3000
    command: echo $TEST_CHUNKS | jq '.[2] | join(",")' | xargs npm run cypress:run -- --spec
    record: false
    config-file: cypress.json
  env:
    TEST_CHUNKS: [[ foo.js, bar.js ], [ baz.js, qux.js ]]

And finally when it comes to run the command there is just the following output, not running any of the specs
Using custom test command: echo $TEST_CHUNKS | jq '.[2] | join(",")' | xargs npm run cypress:run -- --spec
current working directory "/home/runner/work/demo"
/usr/bin/echo $TEST_CHUNKS | jq '.[2] | join(",")' | xargs npm run cypress:run -- --spec
$TEST_CHUNKS | jq '.[2] | join(",")' | xargs npm run cypress:run -- --spec

Can anyone please shed some light why the command is not working in contrast to a local machine ?
Thanks in advance and
best regards
~david

Update:
Using {{env.TEST_CHUNKS}} will output the complete array, so it looks like the piping to jq and following does not work.

@davidlinse
This is quite an old issue and the usage of the action is also quite specialised. Can we close this issue now?

Closing, since this is a stale, inactive issue.


[BEAM-8815] Skip manifest when no artifacts are staged

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Portable_Python PreCommit

Unrelated failure in Run Portable_Python PreCommit
07:56:50 > Task :sdks:python:test-suites:portable:py2:installGcpTest FAILED
...
07:56:50       File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Portable_Python_Phrase/src/build/gradleenv/1866363813/local/lib/python2.7/site-packages/setuptools/wheel.py", line 110, in _install_as_egg
07:56:50         self._convert_metadata(zf, destination_eggdir, dist_info, egg_info)
07:56:50       File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Portable_Python_Phrase/src/build/gradleenv/1866363813/local/lib/python2.7/site-packages/setuptools/wheel.py", line 131, in _convert_metadata
07:56:50         os.mkdir(destination_eggdir)
07:56:50     OSError: [Errno 17] File exists: '/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Portable_Python_Phrase/src/sdks/python/.eggs/pytest_runner-5.2-py2.7.egg'
07:56:50     ----------------------------------------
07:56:50 ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Run Portable_Python PreCommit

(tracking those Python flakes here: https://issues.apache.org/jira/browse/BEAM-8793)

Merging, unrelated CI issue is tracked in  https://issues.apache.org/jira/browse/BEAM-8793


Update docs: local git changes have to be commited

I have been approach several times with question: "why the s2i isn't building the latest changes in my repository?" and the answer usually was that "you need to commit all your changes", so I figured out it would be wise to have this info in our docs, i case anyone would read them :P

thanks. [merge]


Use gocache in CI when building KubeOne

What this PR does / why we need it:
This PR proposes using the gocache mechanism in the CI to speed up the build jobs. The build times right now are on average 2-3 minutes, but depending on the load, the build times can go up to 5-10 minutes. Building all the dependencies each time also requires more resources.
The gocache mechanism should solve this and reduce build times and resource consumption. Right now, we're only using it for building the binary, but if it works, we'll use it for other tasks as well.
The gocache scripts are based on work @xrstf did in #1075 and for KKP and other projects.
This PR also brings some utility functions from KKP which we'll use for other scripts in the future.
Does this PR introduce a user-facing change?:
NONE

/lgtm cancel
please add the download-gocache file to the .gitignore

/lgtm

/test pull-kubeone-e2e-aws-conformance-1.20


Fix map_geometries() loss of feature IDs

I noticed that a Feature passed to geojson.utils.map_tuples() loses it's ID. Here is a simple replication.
The cause seems to be that IDs are not included in the dict returned by geojson.utils.map_geometry().
This PR:

adds the ID to the dict aca22cb
adds a test to check ID is present after mapping f3e876a

I don't know what codecov/patch is or why it is failing.

Hi @bryik, thank you for your contribution. However, I'm leaning against making this change, because I don't know that id should be returned by those functions.
If you read the docstrings (the main comments directly under each function declaration) in https://github.com/jazzband/python-geojson/blob/master/geojson/utils.py then you will see that the various utility functions in this repo are only intended to return partial data, not a full representation of the input object.
So, my understanding is that the utility functions are not intended to be a "put your object in one end and get it out the other transformed" functions, but "give me your object and I'll give you some transformed data you can add to it" functions.
Would using them this way meet your needs? In other words, change the second half of your example to:
geojson_feature = geojson.Feature(
    id=example["id"],
    geometry=geojson.Point(example["geometry"]["coordinates"]),
    properties=example["properties"])

# The ID is present.
print("id before map:", geojson_feature["id"])

# Map over the feature's tuples (without doing anything).
geojson_feature['mapped_geometry'] = geojson.utils.map_tuples(lambda t: t, geojson_feature)

# The ID and mapped data are now both available on the original object!
try:
    print("id:", mapped_feature["id"])
except KeyError:
    print("ID is missing!")

Hello @rayrrr. I'm not quite sure I understand your proposal.
geojson_feature['mapped_geometry'] = geojson.utils.map_tuples(lambda t: t, geojson_feature)

results in a geojson_feature that looks like:
{
  "geometry": {
    "coordinates": [-77.1291115237051, 38.7993076720178, 0],
    "type": "Point"
  },
  "id": "0",
  "mapped_geometry": {
    "geometry": {
      "coordinates": [-77.1291115237051, 38.7993076720178, 0],
      "type": "Point"
    },
    "properties": {
      "line": "blue",
      "marker-col": "#0000ff",
      "marker-sym": "rail-metro",
      "name": "Van Dorn Street"
    },
    "type": "Feature"
  },
  "properties": {
    "line": "blue",
    "marker-col": "#0000ff",
    "marker-sym": "rail-metro",
    "name": "Van Dorn Street"
  },
  "type": "Feature"
}

See this repl.
Are you saying that this is intended?

Looking at the docs again, I see map_tuple() says it "maps a function over all coordinates and returns a geometry of the same type" which implies Features should not be passed to it or if they are, that users should be prepared to receive only a geometry back.
However, the docstring of map_tuples() says it takes "A geometry or feature to extract the coordinates from" and Features have an explicit case in the code that does not raise an exception. Also when given a Feature, map_tuples() returns a Feature and not a geometry.

@bryik your additional notes helpful, and you are correct. Merging your PR in its current form. I was basing my earlier comments off of misleading docstrings, sorry. The docs/docstrings for utils.py functions need improvement...we have a related open issue: #110. While I would like these changes to be a bit more idiomatic, I will handle that in a quick follow-up PR and will give you a heads up on that. Thanks again.

@rayrrr Happy to help :-)
Thanks for the review and for maintaining this project!

@bryik #130 is the follow-up PR, have a look.


Support for RxJS 6

I'm submitting ... [x] Feature request
Current behavior
Using RxJS 5.5.x imports like import { Observable } from 'rxjs/Observable'; are used.
Expected behavior
RxJS 6 brings simplified imports like import { Observable } from 'rxjs'; ... so it is necessary to import all classes from directly rxjs.
What is the motivation / use case for changing the behavior?
The problem is the size of a bundled application when the application is using RxJS 6 and a package is using 5.5.x because it is necessary to use rxjs-compat package and load both of them.
Other conditions
If all places in code where angular-modal-gallery is using RxJS imports are manually rewritten to new RxJS import style, everything works so it seems that this change would be very easy to done and the only question is how to manage and publish this package for RxJS 5.5.x and RxJS 6.x in parallel.
Environment (the most important section to fill very carefully)
Angular 6.0.0-rc.3
RxJS 6.0.0-tactical-rc.1

I'm not using rxjs in the sourcecode of the lib right now. I'll add it in the next releases, but for now there aren't imports of rxjs.
Did you find a specific problem?
rxjs 6 is backward compatibile with angular 5?

@Ks89 ... if you look at angular-modal-gallery.umd.js you can see that there is require('rxjs/Observable') for example.
There is rxjs-compat package for backward complete compatibility ... but in reality for the most of app just updating imports is 99% of the work to switch to RxJS 6.

@Ks89 ... ah, sorry. You are right. It was really version 4.0.1.

Ok perfect, no problem.


Out memory error 4.25 with DX12 RHI

Withe the latest version form source control I get an out of video memory error when trying to save. I have 11gb of video memory and the project is 1gb so there is no conceivable way it could run out. (don't know why it would even be using VRAM)

To add some info to this issue.

Issue is easily reproducible by me and my team when checking out any asset config/texture/level etc with RHI set to DirectX12.
It only occurs for me and my team when using dx12, past dx11 projects work fine.
After opening a working existing dx11 project, switching RHI to DX12, and restarting the editor, the issue occurs upon first checkout.
The issue occurs with release  2.16-beta and still occurs after https://github.com/SRombauts/UE4GitPlugin/commit/214af6df6adbd133f616b6191b090012cafb7f3c
@SRombauts I cannot find a workaround for this, and as my team rely on an LFS locking workflow we are a bit stuck until it is resolved.

@Carbon-NateBowman after getting this with another plugin I determined it was a UE 4.25 bug. You can attempt to verify this is you want. But I do no know if it can be fixed plugin side or has to be fixed engine side.

Thanks for reporting this and updating me.
The question is, is this happening without Source Control enabled ?

Thanks for reporting this and updating me.
The question is, is this happening without Source Control enabled ?

It does not appear to happen without source control enabled.
For me, DX12, no source control, at least 5hrs a day since 4.25 release, not happened once.

I've had it happen with the megascans plug-in (another plugin which would be doing similar UE side operations) only starting with 4.25, with dx12 which is far to specific to be unrelated.

I've had it happen with the megascans plug-in (another plugin which would be doing similar UE side operations) only starting with 4.25, with dx12 which is far to specific to be unrelated.

Oh, that's a good point, when 4.25 came out, I also had something similar (straight ctd, no error) when importing large megascans assets with their first 4.25 plugin versions. It was resolved after a few revisions. As a test, I just imported a few 8k surfaces and high poly models (with all lods) without issue.

UE 4.24.3 with 2.15-beta RHI set to DX12, spikes on checkout but not fatal for small numbers of assets. However, checking out multiple items causes the same kind of spike and eventually a crash, just much slower.
Checking out 25 items.

Which makes me think it's not a bug with update to 4.25 but a bug or change with ue that requires a plug-in side work around or change.

I'm having the same issue :(

Sorry guys, I am having more things to deal with on my day job, and at the same time more things to do with the family at home.
Thanks a lot @crevetor for fixing this for us all

Better results in 4.25 but unfortunately not fixed completely.
see https://github.com/SRombauts/UE4GitPlugin/pull/142#issuecomment-658848702

Still present with UE5.0 & pre-UE5.1 built from sources
see https://github.com/SRombauts/UE4PlasticPlugin/issues/97
I have started reproducing the issue in Unreal without any Source Control operation, with a simple infinite loop in the Provider, meaning it's purely a render thread issue (and I can see how other progress bars in the Editor code seem to handle this)

A similar bug https://issues.unrealengine.com/issue/UE-93603 Directx 12 RHI can run out of video memory on long process (anims import)
has been fixed by adding End & BeginFrame on the RHI thread https://github.com/EpicGames/UnrealEngine/commit/4cbce19c2848723ccc01a4fba3133d663d64d4ae

And the official issue would be https://issues.unrealengine.com/issue/UE-100291 "Out of video memory" crash when attempting to save many assets with source control enabled.
A very recent one even mention the workaround I implemented in the plastic plugin! https://issues.unrealengine.com/issue/UE-160299 GPU memory leak during large source control operations:

The crash has been seen in Git and SVN, and can be avoided by removing FScopedSourceControlProgress::Tick. This will prevent Slate from being ticked during the operation, but will prevent the throbber widget from animating.

PR to Epic Games :)
https://github.com/EpicGames/UnrealEngine/pull/9492 [UE-100291][UE-160299] Fix source control progress bar crashing out of video memory in case of long-running operation #9492

The proper fix has been submitted to ue5-main https://github.com/EpicGames/UnrealEngine/commit/67dacf2baaafe0d9b6fb5eeb5b179fb5b871a4bf
It will be part of UE5.1 release :)


Add YandexGPT Chat model

Introducing an ability to work with the YandexGPT chat model.

Hey @tyumentsev4, changed the name to ChatYandexGPT to match our convention but looks good otherwise! Will merge if that change is ok with you?

@jacoblee93 thank you everything is fine

Great, thanks!


[Outlook] (Mac) Update saveAsync note based on feedback

See feedback on PR https://github.com/OfficeDev/office-js-docs-pr/pull/1045.

Docs Build status updates of commit 340d0b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.3/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.4/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.5/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.item.md
:white_check_mark:Succeeded

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


Use plain text files to record node ids and add flag to replay them

Unfortunately due to the limitations of bat file sizes on Windows we
need to use another solution; in the end seems better anyway because
now you can take files generated in one platform and use that in
another platform.

What happens if xdist is used when replay a recorded file?
pytest --replay=.pytest-replay-gw1.txt -n 2

It will run only the tests contained in the file, in parallel. (which kind defeats the purpose, but it works)


Docker update #937

Newer version of docker outputs its result to stderr, not stdout.
Also, docker's command has been changed a lot (for example, docker images is now docker image ls).

Sorry, I forgot to open this as draft.


Fix silent errors when using syncdata

There is an issue while importing broken fixtures (i.e. when there is an invalid UUID).
The fixture fails silently and interrupts the whole process, resulting in a success message Installed x objects from y fixtures.
This happens because another exception is thrown when attempting to rollback a failed transaction, which was the case.

Coverage decreased (-0.01%) to 70.076% when pulling 995f18d31f0dca89bd530c3b386b7014e7e7bb4a on cuchi:fix-supressed-exceptions into 1351a68b8c0d7ba21275b71743b9d02f1be2b422 on django-extensions:master.

Coverage decreased (-0.01%) to 70.076% when pulling 995f18d31f0dca89bd530c3b386b7014e7e7bb4a on cuchi:fix-supressed-exceptions into 1351a68b8c0d7ba21275b71743b9d02f1be2b422 on django-extensions:master.

The build error should fix itself after rebasing to master.
Would it be possible to have a test case for this ?
And/or maybe have a bit more detailed explanation why using get_rollback is the correct fix.

Closed in favor of #1532

Thanks for your help and work on this @cuchi !