Disable Wii extension addon by default

The Wii extension addon inadvertently enables the addon and maps pins by default, causing validation issues in the web config and confusion for the user. This PR disables the extension by default and unsets the default pin mappings.

FYI GP2040-CE_0.7.1_MavercadeKeebfighter.uf2 does not boot into any controller without this change. git bisect narrowed the boot issue down to d662fcbdfea1bd4ff229224e0497ec90bb786bae and merging this lets it boot again; must be some pin funny business.


Godot 4: Scene assignment to property through editor not saved

Godot version:

Godot 4 dev 64bit (built from 1/31)
OS/device including version:

Ubuntu 20.04
Issue description:

While going through the "Your first game" tutorial I ran into an issue with this step:
https://docs.godotengine.org/en/latest/getting_started/step_by_step/your_first_game.html#main-script
where I changed the following to what I believe is the correct new syntax:
export(PackedScene) var mob_scene --> @export var mob_scene: PackedScene
I then assigned a scene to the property through the editor. But, when I save the project the assignment is lost. The editor just goes back to displaying [empty] for the property.
I was able to work around the issue by assigning the resource in the script.
@export var mob_scene: PackedScene = preload("res://Mob.tscn")
Steps to reproduce:
export a packed scene variable and assign a scene through the editor
Minimal reproduction project:

dodge.zip

Hi, I face the same problem.
As a workaround use @tool annotation.

Does this occur only in master or also in 3.2.3?

This works as expected in 3.2.3 with the older export syntax. For the master, is @export var mob_scene: PackedScene perhaps incorrect?

I also experienced this issue.
I also built a copy in 3.2.3 and it worked as expected with older export syntax.
Thank you, jpew, for finding a work-around!
This is truly the most irritating of bugs.

I noticed an issue with the following code in gdscript.cpp _update_exports, the following lines:
	if (placeholders.size()) { //hm :(

		// update placeholders if any
		Map<StringName, Variant> values;
		List<PropertyInfo> propnames;
		_update_exports_values(values, propnames);

		for (Set<PlaceHolderScriptInstance *>::Element *E = placeholders.front(); E; E = E->next()) {
			E->get()->update(propnames, values);
		}
	}

It seems at line: E->get()->update(propnames, values);
The new value of E->get() is replaced by the default value of the script
To be confirmed though, I will continue looking at it

Thanks for taking a look. I guess it may be some time before the devs have a chance to address this relatively minor bug.

Seems to be same issue as:
#41509
#41690
and maybe #45120

In PlaceHolderScriptInstance::update, by changing this line:
if (!values.has(n) || values[n].get_type() != E->get().type)
to:
if (!values.has(n) && values[n].get_type() != E->get().type)
The value is changed properly, but something weird happens with the following script:
@export var mob_scene: PackedScene # = preload("res://Mob.tscn")
@export var num: int
@export var numDefault: int = 42
@export var pathToNode: NodePath

When I let numDefault to 42, after saving, the value is set to 0. But if numDefault value is different than 42, the new value is saved properly...
The 3 others fields seems so work as expected

The root cause is really because of values[n].get_type() != E->get().type, where E->get().type is Nil as pointed in #45120.
Adding the fix given by https://github.com/godotengine/godot/pull/45120#issuecomment-784715031, changing GDScriptAnalyzer::resolve_class_interface, fixes the issue.

The issue is fixed in one of the latest Godot 4.0 f7ae5442a607ff1fdd7f63b87ad93d067867aeec
Probably same reason as in issue #41690, and also with the non-exported properties being visible (issue to be create soon).
Therefore, I think this issue can be closed too.

Thanks for testing!


added Gemini_API: market campaign generator

🎯 Title and Issue Number
added gemini_api : market campaign generator

Closes #283

🗒 Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X]  I have gone through rules of when PR will get merged.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have followed proper file structure.
[X] I have gone through CONTRIBUTING GUIDELINES.md.

Thank you for contributing!❤
Don't forget to show some love by ⭐ the repository!

Hey @abckhush, Thank you for creating PR! We will review it super soon. 😇❣
As we continue to evolve and innovate, we encourage you to share your ideas, feedback, and code to help us push the boundaries of what's possible in the world of APIs🚀.
We hope you have followed CONTRIBUTING GUIDELINES.
Thank you for being an essential part of our community. Together, we'll keep building amazing things!
Don’t forget to ⭐ our repository!
Happy Coding!✨
Will See you soon❣

Hi @dishamodi0910 Could you pls merge this PR?

@abckhush We're thrilled to inform you that your pull request has been successfully merged into the APIverse🚀🎁
Your hard work, dedication, and expertise have made a significant impact on our project, and we couldn't be more grateful for your contributions.😇
Your code will now be a part of our growing ecosystem, helping developers worldwide to create exceptional APIs.❣🔥
Happy Coding! ✨
Will See you soon❣


test/runner: Bump test timeout to 35 minutes

Test runs on the new infrastructure appear to take a bit longer.

LGTM


Use map_err in PSBT EcdsaSigHash deserializer

Details: https://github.com/rust-bitcoin/rust-bitcoin/pull/776#discussion_r785781258

hi, May I work on it ?

Of course!


[Improvment Suggestion] I would like to compile and package as a Linux app

Hello @ifedapoolarewaju !
Yes, I have read the README which tells me to run npm install and npm start, but I would like to compile and package the developing/testing/unstable repository as a Linux app on a Linux OS, but the problem is when I run gulp build && build --dir or gulp build && build -mwl --x64, it downloads the Electron designed for macOS and gives errors. I also tried to run npm run dist linux zip, but it still downloads Electron for macOS and gives the same errors. I have removed the macOS and Windows distributions from package.json, but it still gives the problem due to the path /usr/local/Cellar/go/1.12.1/libexec/src/runtime/asm_amd64 which is designed for macOS. Here is full error:
  • electron-builder version=20.43.0
  • loaded configuration file=package.json ("build" field)
  • writing effective config file=dist/builder-effective-config.yaml
  • no native production dependencies
  • packaging       platform=linux arch=x64 electron=2.0.12 appOutDir=dist/linux-unpacked
  • downloading               parts=8 size=49 MB url=https://github.com/electron/electron/releases/download/v2.0.12/electron-v2.0.12-linux-x64.zip
  • retrying (1)
  • retrying (2)
  • retrying (3)
  ⨯ part download request failed with status code 403
github.com/develar/app-builder/pkg/download.(*Part).doRequest
        /Volumes/data/Documents/app-builder/pkg/download/Part.go:128
github.com/develar/app-builder/pkg/download.(*Part).download
        /Volumes/data/Documents/app-builder/pkg/download/Part.go:66
github.com/develar/app-builder/pkg/download.(*Downloader).DownloadResolved.func1.1
        /Volumes/data/Documents/app-builder/pkg/download/downloader.go:110
github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2
        /Volumes/data/Documents/app-builder/pkg/util/async.go:67
runtime.goexit
        /usr/local/Cellar/go/1.12.1/libexec/src/runtime/asm_amd64.s:1337

Error: /home/gusbemacbe/node_modules/app-builder-bin/linux/x64/app-builder exited with code 1
    at ChildProcess.childProcess.once.code (/home/gusbemacbe/node_modules/builder-util/src/util.ts:244:14)
    at Object.onceWrapper (events.js:286:20)
    at ChildProcess.emit (events.js:198:13)
    at maybeClose (internal/child_process.js:982:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
From previous event:
    at _unpack (/home/gusbemacbe/node_modules/app-builder-lib/out/electron/ElectronFramework.js:298:18)
    at unpack (/home/gusbemacbe/node_modules/app-builder-lib/out/electron/ElectronFramework.js:257:18)
    at ElectronFramework.prepareApplicationStageDirectory (/home/gusbemacbe/node_modules/app-builder-lib/src/electron/ElectronFramework.ts:125:12)
    at /home/gusbemacbe/node_modules/app-builder-lib/src/platformPackager.ts:180:21
    at Generator.next (<anonymous>)
From previous event:
    at LinuxPackager.doPack (/home/gusbemacbe/node_modules/app-builder-lib/src/platformPackager.ts:167:165)
    at /home/gusbemacbe/node_modules/app-builder-lib/src/platformPackager.ts:113:16
    at Generator.next (<anonymous>)
From previous event:
    at LinuxPackager.pack (/home/gusbemacbe/node_modules/app-builder-lib/src/platformPackager.ts:111:95)
    at /home/gusbemacbe/node_modules/app-builder-lib/src/packager.ts:430:24
    at Generator.next (<anonymous>)
    at xfs.stat (/home/gusbemacbe/node_modules/fs-extra-p/node_modules/fs-extra/lib/mkdirs/mkdirs.js:56:16)
    at /home/gusbemacbe/node_modules/graceful-fs/polyfills.js:285:20
    at FSReqWrap.oncomplete (fs.js:154:5)
From previous event:
    at Packager.doBuild (/home/gusbemacbe/node_modules/app-builder-lib/src/packager.ts:396:24)
    at /home/gusbemacbe/node_modules/app-builder-lib/src/packager.ts:366:57
    at Generator.next (<anonymous>)
    at /home/gusbemacbe/node_modules/graceful-fs/graceful-fs.js:111:16
    at /home/gusbemacbe/node_modules/graceful-fs/graceful-fs.js:45:10
    at FSReqWrap.args [as oncomplete] (fs.js:140:20)
From previous event:
    at Packager._build (/home/gusbemacbe/node_modules/app-builder-lib/src/packager.ts:335:133)
    at /home/gusbemacbe/node_modules/app-builder-lib/src/packager.ts:331:23
    at Generator.next (<anonymous>)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)
From previous event:
    at Packager.build (/home/gusbemacbe/node_modules/app-builder-lib/src/packager.ts:288:14)
    at build (/home/gusbemacbe/node_modules/app-builder-lib/src/index.ts:59:28)
    at build (/home/gusbemacbe/node_modules/electron-builder/src/builder.ts:228:10)
    at then (/home/gusbemacbe/node_modules/electron-builder/src/cli/cli.ts:49:19)

It is why you should improve the README for programmers who want to compile, build and package.

Hello @gusbemacbe, I get a similar error when trying to compile buttercup on an Arch Linux machine: https://pastebin.com/kcUgW5WB Did you solve this issue? If so, how?

Hi @erikwesselius
Yes, I did. But the macOS path has been solved, and you need to install some modules required.
To solve the macOS path, you use nvm, install the node version 8.9.1, required by the most of repos, including Thermal and @sylveon's VSCode's transparency enabling and switch to the version.
npm install
npm install app-builder-lib electron-builder gulp jquery popper.js
npm run dist linux zip

Do not worry about few errors. These errors are related to Windows because you are not a Windows user.


Progress tracker for Composer Create-Project

Add tracking for folders created under ./flarum/vendors/ to see how many are created to allow a rough progress bar on the front end. (Extend the $ajax=status?)
I am fairly sure this will be straight forward, and that my main problem will be honing my JS and front-end skills.

Outscetched how to do this. Count folders, and have a bootstrap tracker with values min 0 max(how many folders in vendor) and get the current number trough $ajax=status&substatus=x
I am fairly certain this will work. Alternative would be to run a full check on how many files, but lets keep it fairly simple.

Depending on tests, I could perhaps do something like this:
$phfiles = new FilesystemIterator(DIR, FilesystemIterator::SKIP_DOTS);
echo iterator_count($phfiles);
So, if I truly know the count of files (After testing) I can get a more suitable answer. It would validate better then just counting the folders.
Depends on how long it takes to run it though.
Ref: Very old SO thread: http://stackoverflow.com/questions/12801370/count-how-many-files-in-directory-php

Alternatively, I have now a Composer.log file which should be 88 lines long when complete. This approach is perhaps the easiest, and less taxing on the system..
Some SO searching gave this:
'''
$lines = 0;
$file = fopen( $file, 'r');
while( !feof( $file) {
fgets( $file);
$lines++;
}
fclose( $file);
'''


Allow different total number of phase encode steps in KData

This simplifies the logic to determine n_k2 and n_k1 in KData. A lot of the complexity was due to the error message for the NotImplementedError.
Before, there were some edgecases that were not fully covered.  Now we also have a fallback for different numbers of phase encodes for different "other" labels, with shape (total_aquisitions, 1, 1, k0) with a warning instead of an exception.
(I would also be fine with removing the warning. I added it as I think it could  for us equally likely be a data/user error than the expected resullt.)
I also renamed KTrajectoryRawShape.reshape as this looked to close to Tensor.reshape: I was wondering why we would reshape with "sort_idx" as one of the sizes. Now it is sort_and_reshape
Note: This is currently vs the ruff PR, but will be rebased onto main and will be merged seperatly, either before or after #193

This will require some testing on actual data which I have not done yet.

Before, there were some edgecases that were not fully covered. Now we also have a fallback for different numbers of phase encodes for different "other" labels, with shape (total_aquisitions, 1, 1, k0) with a warning instead of an exception.

I am not sure I understand what the reason for this is. Yes, we can do this, but we don't have any code which allows for the reconstruction of such data.

How about having another KDataRaw class which has a from_file method which does everything up to this point: https://github.com/PTB-MR/mrpro/blob/caa89eba74c65c64d498ffb996f94054393cb8ad/src/mrpro/data/_kdata/_KData.py#L132
Then we have a method in KData called from_raw which does the rest (and of course keep from_file which would do both steps in one call). from_raw would then throw an error if KDataRaw is not valid, i.e. cannot be reshaped into our matrix. Then we would have an option to fix certain parts of the data but make it clear that KDataRaw cannot yet be used for image reconstruction.

Moving the reshaping in a different function could simplify the from_file method a bit and allow us to call it again at a later point after changing some indices.
I would prefer NOT to add a new class for the different shapes. A warning is IMHO enough.
Most functions should really work the same irregardless of the shape. If you want to do an nmr spectrum you should be able to do it. The gain of the new class does not outweigh the added complexity wrt to mixins and protocols..

If you want to do an nmr spectrum you should be able to do it.

We can do this already because the different spectra are not encoded as different phase encoding points. Hence everything will work as expected.

Most functions should really work the same irregardless of the shape.

True, but it is not about the shape but the fact that we split kdata into dimensions which require Fourier transform (k0, k1, k2) and are combined in a single image and dimensions which lead to different images (coils, other). If we now put phase encoding dimensions into other, our code will "work" but the result will be wrong.

The gain of the new class does not outweigh the added complexity wrt to mixins and protocols.

KDataRaw would not require any Mixins or Protocols because it would really only be a data class with a single method.

Then it doesnt really help. If we cannot at least reshape, rearrange, and select subsets KDataRaw use useless.
If we do this, it should be the other way around and everything should by default be implemented for KDataRaw except if need to know the phase encoding steps.
I still vote to return the Data and print a warning. We can give the warning a
We can explicitly mention that reconstruction will most likely fail and use a bit stronger language in the warning
If you really want to have it fail in your code, you can use (or similar, depending on the actual message we use for the warning) to treat it as an exception
import warnings
warnings.filterwarnings("error","Data Shape Issue" )

I still don't think it is a good idea to return KData which will break the rest of the code but luckily we are three admins so we can have a majority vote. Maybe extend the warning message for n_acqs_per_other > 1 by mentioning that the rest of the reconstruction will most likely yield unexpected results.


refactor(runbook)!: change variable job_schedules type

BREAKING CHANGE: change type of variable job_schedules from map(object) to list(object).

Reasoning for change will be documented in baseline, see equinor/terraform-baseline#88.


Various fixes

There may be some changes which aren't implemented perfectly, but at least the bug fixes should be pretty good.

Firefox users weren't able to create folders, because the application accepted only the Content-Type json/application, but Firefox sends this as json/application; charset=utf-8 or so. This resulted in an 400 Bad Request error.
The admin was unable to delete a user with it's files because it was unable to retrieve the files from another user because of the restrictions in the file model used.
Files couldn't be downloaded with a password, because the method verifyPassword didn't exist.
Logged in users were unable to download files from other users.
The view/admin/index.tpl file had an error. Admins weren't able to open the admin overview page.

Thanks for your contribution! Can you please change this PR so it can be merged into dev (instead of master)? Also, your commits do not cover all the problems you mentioned, do they? If not, please add issues :)

Yes the mentioned problems should be all fixed.
The adaption of model/File.class.php maybe isn't perfect. You may want ot take a look at that to implement a different solution.


Move Velocity and Hammerjs from the dev deps to the deps

Because on the first look the empty deps mean that the library doesnt have a deps

https://github.com/shakee93/vue-toasted/pull/30

It was already there on the earlier releases. i have removed it as it will be installed with the package which the plugin doesn't need as the plugins start point is the min file.


Invalid data stored in etcd

In a non-k8s setup (refer - https://kloudone.atlassian.net/browse/AK-8529), the kvm-service fails to start (the restoration fails) because of invalid data stored in etcd with the error as shown below.

Attached the dump of key-value pairs in etcd - kvms-etcd-data.txt
The initial analysis of this data shows that,

There are entries with empty labels, nil values and identity mentioned as 0.
There are entries where instead of array of strings, data is stored as string.

We have to fully analysis the etcd dump and add proper validation and checks so that these junk data can be reduced to zero.

@nyrahul @seswarrajan

@nyrahul @seswarrajan Also, what we should do if the restoration fails? Can we start the kvm-service in a clean state with a error/warning saying that restoration failed. Or the kvm-service should exit as it happens now?


Cargo does not build on stable (beta) channel

When I try to build Cargo with rust-1.0.0-beta, I see a bunch of failures, but most of it seems to be fixed upstream. Here's a summary:
Can't derive Copy as trait core::clone::Clone is not implemented on:

liblibc: Fixed upstream

types::os::common::posix01::{glob_t,timeval,timespec,timezone}
types::os::common::bsd43::rusage
types::os::common::bsd44::{sockaddr,sockaddr_storage,sockaddr_in,in_addr,sockaddr_in6,in6_addr,ip_mreq,ip6_mreq,addrinfo,sockaddr_un,ifaddrs}
types::os::arch::posix01::{stat,utimbuf,pthread_attr_t}
types::os::arch::extra::mach_timepase_info

term-0.2.4: Fixed in 0.2.6

terminfo::parm::{States,FormatState,Flags,FormatOp
Attr

semver-0.1.17: Fixed in 0.1.18

version_req::{ReqParseError,LexState}

regex-0.1.24: Fixed in 0.1.25

vm::{MatchKind,StepState}

glob-0.2.7: Fixed in 0.2.9

MatchResult

Use of feature flags

threadpool-0.1.2: Fixed in 0.1.3

#!feature(unsafe_destructor)

pkg-config-0.3.2: Fixed in 0.3.3

#!feature(convert)

gcc-0.3.3: Fixed in 0.3.4

#![feature(convert)]

Other

tar-0.2.7: Fixed in 0.2.9

Wrong arity when calling Error::new

rustc-serialize-0.3.10: Fixed in 0.3.11

Uses undeclared trait std::error::FromError

...and that rabbit hole went a bit deeper than expected. Iteratively updating a bunch of dependencies landed me at a point where I can almost compile Cargo, but for tar's reliance on #![feature(fs, fs_time, fs_ext)].
Upstream tar bug: https://github.com/alexcrichton/tar-rs/issues/17

Cargo also needs git2, which doesn’t build on beta due to #![feature(catch_panic)] (alexcrichton/git2-rs#54).

Thanks for this! This is a known issue, and we've actually got quite a small set of features to remove before Cargo builds on stable rust (as you've discovered!).
At this time this unfortunately isn't actionable as all these features are crucial to the operation of Cargo and can't be removed. I plan to write an RFC for all the fs-related features quite soon, and git2's feature of catch_panic will likely also be stabilized during this next cycle (it was a late addition in the last one).


Support "compressed" ciphertext encryption

We might want to eventually support "compressed" encryption, where instead using the whole random "a" polynomial, you just provide the seed for "a" and what PRNG to use. This gives a nearly free 2x reduction in communication overhead (for the client->server direction)  and is therefore used pretty much universally when fresh ctxts are stored/sent across the network.
I'm guessing it'd need its own lwe.compressed_encrypt (or similar),  and probably also an explicit "decompression" op to turn it into a "real" ciphertext. In terms of type, this could either output an (R)LWE ciphertext with one of the Attributes (which are currently being reworked) indicating the compressed nature, or it could output a special compressed ciphertext type.
Lowering the encrypt op would probably produce a tuple<!polynomial.polynomial<...>, i32> (or whatever integer type is required for the seed), and the lowering the decompress op would be basically the "previously skipped" parts of the encrypt lowering.

You'd also need a PRNG state machine Op description ?


DRP: Start date being unintentionally set to the last value of current week when focusing it a second time

react-dates version
<EMAIL_ADDRESS>Describe the bug
If you've chosen a start- and end-date. The start date will automatically change to the last day of the previously selected week when you focus on the start date field a second time
Reproduction steps:

Choose a start date which is not at the end of a row (not the last day of a week in other words).
Choose an end date.
Focus the start date field by clicking it.
Blur the field by pressing outside the calendar component

The value is now set to the last day of the week that was previously selected.
Please see the gif
Source code (including props configuration)
This bug is found in any setup of the component that I've tried, also in the publically available storybook here:
https://airbnb.io/react-dates/?path=/story/daterangepicker-drp--default
(Use the same prop setup as the storybook basic example)
Screenshots/Gifs
In the gif, 27th of september is initially selected. It is the changed to the 28th of september without any user input when you focus the input element a second time
https://gyazo.com/07e8fa227d0ff9d12c436c6365f73dd2
Desktop:

OS: macOS
Browser: Chrome
Version: 77.0.3865.90

Is the issue reproducible in Storybook?
Yes.
https://airbnb.io/react-dates/?path=/story/daterangepicker-drp--default

Duplicate of #1807 #1804 #1800 #1799 #1795

Alright, didnt see those.
Thank you! : )


Array changes when object taken from array gets changed

Not sure if this is a bug or if I just don't understand the behavior:
You start with an array with objects in them.
You assign a variable for one of these objects.
When you change that object, the original array is changed as well.
Steps to reproduce
Example1:
# Set up an array with two objects in it
$SourceArray = @(
    [PSCustomObject]@{
        Name = "Value1"
        property1 = "blieb"
        property2 = "blaab"
        property3 = "bloeb"
    }
    [PSCustomObject]@{
        Name = "Value2"
        property1 = "blieb"
        property2 = "blaab"
        property3 = "bloeb"
    }
)

# Create a variable based on an object in the array
$IssueObject = $SourceArray[0]
# Add a member to the object
$IssueObject | Add-Member -MemberType NoteProperty -Name "ExtraProperty" -Value "blaib" -Force
# So we have the object with an extra property
$IssueObject

# Now if we call the same object from the source array,
# I wouldn't expect an extra member, as I created a new variable for the changed object
$sourcearray[0]
# Turns out the object in the variable has changed as well??

# Looking further: Let's create the variable again but add | select-object *
$IssueObject = $sourcearray[1]  | Select-Object *
# Do the same thing as before
$IssueObject | Add-Member -MemberType NoteProperty -Name "ExtraProperty" -Value "blaib" -Force
$IssueObject

# Call the object form the array again
$SourceArray[1]
# And results are as expected: without the extra member.

Example2 (run as admin to reproduce):

# Collect all the services in an array
$Services = Get-Service

# Collect the status of the time service
$Services | Where-Object {$_.Name -eq "W32Time"}

# Save the Time service in a new variable
$Time = $Services | Where-Object {$_.Name -eq "W32Time"}

# Start the time service (or stop if it was already started)
$Time | Start-Service

# The time service is now running. But I did not touch the Services variable.
# So I would expect the status in the Services Variable to still be Stopped.
# But it now comes back as running...
$Services | Where-Object {$_.Name -eq "W32Time"}

Expected behavior
I would expect the array to change when I define a new variable to work with. I would also not expect a difference when Select-Object is used.
Actual behavior

Environment data
Tested on multiple devices (all Windows), on PowerShell 7.1.0, 7.2.0 as well as Windows PowerShell

Name                           Value
----                           -----
PSVersion                      7.1.0
PSEdition                      Core
GitCommitId                    7.1.0
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.2
PSEdition                      Core
GitCommitId                    7.2.0-preview.2
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

In short: The behavior is by design.
Also, unless you're reasonably sure that you've found a problem with PowerShell itself, please don't post here and use one of the following resources instead, at least until you're sure you've found an actual problem:

The Slack and Discord community chat forums (they seamless talk to each other).

Q&A site StackOverflow.com and the PowerShell.org forum for searching or posting questions about PowerShell.

Re example 1:

After assignment $IssueObject = $SourceArray[0], both $IssueObject and $SourceArray[0] by design point to the very same [pscustomobject] instance.

Creating a new variable is not the same as creating a copy of the RHS value - that only applies to .NET value types, whereas [pscustomobject] is an instance of a reference type.

See this Stack Overflow answer for more information.

To create a (shallow) copy of a [pscustomobject] instance, call its .psobject.Copy() method.

Select-Object, when used with -Property (positionally implied) always creates a new ([pscustomobject]) instance (except if -ExpandProperty is passed), but note that Select-Object * with an [pscustomobject] input isn't always the same as calling .psobject.Copy() on that input, because only properties are copied; also, the new object reports its type name as Selected.System.Management.Automation.PSCustomObject.

Note that both methods of copying properties create shallow copies, which means the property values are copied as-is, so that again you get data copies for value-type instances and reference copies for reference-type instances.
There is no general mechanism for deep copying (cloning), though individual types may implement one.
Re example 2:
What Get-Service outputs are so-called live objects (of type System.ServiceProcess.ServiceController) .
That is, their properties reflect the current state of the resource being pointed to instead of taking a snapshot of the state.
It is up to each type to implement one behavior or the other, and this aspect is independent of the question of when a copy of the actual data vs. a reference to the same object is created.
An easy way to get a snapshot of a service-info object is to use Select-Object * to create a [pscustomobject] whose properties then contain static copies of those properties in the original that are calculated properties (properties whose value is determined dynamically, on very access) - but note that for non-calculated properties whose values happen to be instance of reference types you'll again get copies of the references.

@mklement0 This is a perfect place to ask this kind of question. If you don't like, ignore it. Please, it's not on you to tell anyone to post somewhere else.

@alexandair:

It isn't the perfect place to ask such questions, for the reasons stated - and as also reflected in the types of issue templates offered when you create an issue (bug reports, feature request, ...).

Someone who has questions such as this one is far better served by asking them in the communities that I linked - the likelihood of getting a satisfying answer is much greater there (even though in this particular case I (hopefully) happen to have provided one here).

Or did I miss a decision to turn this into a general-purpose PowerShell support forum?
I don't think so, but even if I did, I think that would be a mistake, as it would generate far too much noise for a repository focused on fixing bugs and developing new features.
As a community, we should have clarity on what does and doesn't belong here - unfortunately, the bug-report template doesn't do a good job of communicating that - despite having a very obvious name: bug report.
The very opening statement of this issue, "Not sure if this is a bug or if I just don't understand the behavior" is an indication that conceptual clarity should be sought first before reporting something as a bug, and sites like Stack Overflow are the perfect place for that.
You seem to think of this as dismissing the OP, I think of it as helpful guidance.
Unless I hear convincing arguments to the contrary or see an official decision that general support questions are now acceptable, I will continue to provide this type of guidance.
Unless you want to engage in an actual discussion of the issue, I suggest you take your own advice: "if you don't like, ignore it".

It isn't the perfect place to ask such questions, for the reasons stated - and as also reflected in the types of issue templates offered when you create an issue (bug reports, feature request, ...).

That's more for "how do I do X". OP thought they found might have found a bug, that's good enough here. Won't be many folks reporting bugs if we require them to know for certain it's actually a bug before posting.

You seem to think of this as dismissing the OP, I think of it as helpful guidance.

I'm sure you didn't intend it to, but your original reply does read a bit like you're annoyed.  Even if you are, leaving that in usually just incites defensive replies. Also if you're going to answer anyway there's not a whole lot of point in mentioning it.

Also if you're going to answer anyway there's not a whole lot of point in mentioning it.

The point is to extend a courtesy this time - given that the issue has already been posted - as well as to provide guidance for the future.

I'm sure you didn't intend it to, but your original reply does read a bit like you're annoyed.

Indeed I didn't intend to, and I can't take responsibility for that interpretation: It needed saying (see below) and it provided helpful information (unless you disagree that the places I linked to are good places for asking such questions).

OP thought they found might have found a bug

That's a formal criterion that is too easily satisfied.
While there are ultimately no hard and fast rules, the specific nature of this issue suggests an unfamiliarity with fundamental .NET concepts, and I hope we can agree that:

This isn't the place to teach them.
Issues of this type could end up ignored here, for that reason ...
... unlike on platforms such as Stack Overflow - hence the recommendation to ask there.

Indeed I didn't intend to, and I can't take responsibility for that interpretation: It needed saying (see below) and it provided helpful information (unless you disagree that the places I linked to are good places for asking such questions).

We're all responsible for how we're interpreted.  Unless you're specifically looking for conflict, putting some effort into less aggressive wording would be advisable.

That's a formal criterion that is too easily satisfied.

And that's great!

While there are ultimately no hard and fast rules, the specific nature of this issue suggests an unfamiliarity with fundamental .NET concepts, and I hope we can agree that:

That's right, like the vast majority of the PowerShell community. Bug reporting shouldn't be gate kept, it's already hard enough to get folks to report things.

We're all responsible for how we're interpreted.

Only to a degree. If someone wants to take offense, they will.

putting some effort into less aggressive wording would be advisable.

Commendable, and certainly something I strive for in general.
Re-reading my comment, I could have done better in this case.
I can only hope that my having taken the time to answer the question with care (as a one-time courtesy) served to indicate that I was well-intentioned.

And that's great!
shouldn't be gate kept,

It isn't great, and mistaking proper guidance  for gate-keeping is unfortunate.
What I think would be helpful, to everyone involved, is to communicate the following clearly, as part of the bug-report template (an earlier version had more of that, but it was taken out):

If you're seeing behavior that deviates from the intended behavior, as documented, report it here.

If you're not sure what the intended behavior is or you have questions about PowerShell in general, please seek help from the community via the following forums:

The Slack and Discord community chat forums (they seamless talk to each other).

Q&A site StackOverflow.com and the PowerShell.org forum for searching or posting questions about PowerShell.

Ok, few responses:

The explanation and provided link is very clear, thank you for that.
The recommendation did feel a bit reprimanding and I'm glad that was cleared up.
I posted here as I thought this could be a bug, or at least unwanted behavior. I personally find this very counter-intuitive. The two examples here came from two different people who were as confused as I was. So even if it isn't a bug, I thought it was useful to be mentioned here as behavior that raises questions.

As my wondering has been cleared up I will close this issue, thank you all for your responses

Thanks for the feedback, @Ba4bes - point re feeling reprimanded taken; glad to hear the information was helpful.
As for providing better guidance via the bug-report template: I've created a PR at https://github.com/PowerShell/PowerShell/pull/14479.

I agree with @SeeminglyScience that OP posted what they thought was unexpected behavior, so open an issue (if one doesn't already exist) is the right thing.  I appreciate @mklement0 responding with correct information and pointers.  In general, we are considering enabling GitHub Discussions for general type of discussions not specific to the code of this project, but we won't get to that til next year.
On the internet where all you see is text and no body language, sometimes one may presume the worst, but many times I find that was not the intent (which is clear in this case by @mklement0's response later in the thread).  Overall, it looks like everything worked out and I appreciate the discussion.


feat: there are several months on the calendar

BREAKING CHANGE: calendar data type

@vf1 thanks! the reason i hadn't yet added this is because i don't like the idea of returning something not Date. trying to stick with how date-fns works, returning native types whenever possible.
i was previously thinking of instead of returning calendar: Date[][] we can instead return calendars, which is just an array of Date[][]. to get the first day of the month, you can just use date-fns. that way we don't need CalendarMonth.
you'd just render calendars.map and it works whether you only have 1 or 30. so the change required after upgrading is just changing calendar to plural and using map. however you're rendering it wouldn't need to be changed.
any thoughts?

@its-danny actually the first edition was with calendar: Date[][][], but IMHO it is not very readable when maping to components.  A version calendar: Date[][][] | Date[][] is confusing too. I would prefer to use months instead of calendars: months.map(month => month.weeks.map(week =>... The month typically contains days, but with clarification weeks it looks good.

@vf1 that makes sense. can you update it to just be months instead of calendar, then? also yarn build-docs to update the ts docs.
firstDay seems unnecessary still since you can just use isFirstDayOfMonth from date-fns. would like to let that library handle as much as possible. any reason we'd want to not do that? it'd still be Date[][][] but called months it'd maybe be more clear?
also i can just do it myself, i don't have many people open PRs on my stuff so not sure if it's more polite to ask you to do it or me to do it lol. feel free to ask me to if you don't feel like it, tho.

firstDay seems unnecessary still since you can just use isFirstDayOfMonth from date-fns.

Do you mean search for first day in calendar/months?

would like to let that library handle as much as possible. any reason we'd want to not do that? it'd still be Date[][][] but called months it'd maybe be more clear?

The Date[][][] is not self descriptive for me. This could of course be the solution, but I prefer data structure that can be read w/o docs. This is a purely personal opinion. I am not sure that it will be correct decision in this case.

also i can just do it myself, i don't have many people open PRs on my stuff so not sure if it's more polite to ask you to do it or me to do it lol. feel free to ask me to if you don't feel like it, tho.

@its-danny think I need even more specific version for mine project. So I will try to change your lib without regard to compatibility, and then try to find general purpose features to come back with new PR.


org.testcontainers.containers.ContainerFetchException: Retry limit reached while trying to pull image: selenium/standalone-chrome-debug:3.3.1

Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image name from org.testcontainers.images.RemoteDockerImage@5254d860
	at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:739)
	at org.testcontainers.containers.GenericContainer.setDockerImageName(GenericContainer.java:727)
	at org.testcontainers.containers.BrowserWebDriverContainer.configure(BrowserWebDriverContainer.java:86)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:166)
	... 30 more
Caused by: org.testcontainers.containers.ContainerFetchException: Retry limit reached while trying to pull image: selenium/standalone-chrome-debug:3.3.1
	at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:79)
	at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:21)
	at org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:20)
	at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:27)
	at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:737)
	... 33 more

The latest version available at DockerHub (today) is 3.3.0, not 3.3.1. Why it wants to pull 3.3.1?

Ok, I found that the version is determined from version of webdriver:
testCompile group: 'org.seleniumhq.selenium', name: 'selenium-remote-driver', version: '3.3.1'

Recent webdriver in maven repo is 3.3.1, but on docker hub is 3.3.0.
Shouldn't webdriver be added as a transitive dependency to TestContainers? It would solve the problem, and be easier for the programmer.

Re the transitive dependency, I didn't want to lock testcontainers users into a single version of selenium. I worried that if we did that, we'd quickly become a bottleneck and source of frustration for users.
With the automatic fetch of the matching version container we are at the mercy of the selenium team to keep their container images released in sync with the Java libs. But for the most part they're fairly good, and are better placed to keep things in line than we are.
In this situation, you have the choice of using the 3.3.0 Selenium Java library with the 3.3.0 Docker image (which I'd strongly recommend), or the 3.3.1 library with the 3.3.0 container. You can force this with: new BrowserWebDriverContainer("selenium/standalone-chrome-debug:3.3.1") ...
I'd recommend using the same versions though - part of the reason for testcontainers' selenium support existing is painful experiences of mismatched library/browser extension versions!
Does this answer the question?

I'll close this as I hope this answers the question - please re-open if not.


how/where do i deploy this repo to test the marketplace?

Hi, how/where do i deploy this repo to test the marketplace? Thanks
(i'm used to ethereum/polygon)

@latonet this contract is already live on both Mainnet and Testnet:
https://github.com/onflow/nft-storefront#contract-addresses
Feel free to use the Testnet version to test it out.
Happy to connect and chat about building on Flow in general.

@albeethekid I'll be very happy to have a quick chat about how to use it to have some customizations like limited editions or other metadata that we specifically need for our Marketplace

Sure! Shoot me an email and will work out a time to chat asap<EMAIL_ADDRESS>


test: Handle failed InstallPlans during e2e installations

Update the e2e package to deal with InstallPlan failures that we have no
control over. Currently, OLM will mark an InstallPlan as failed when it
encounters any errors, regardless of the context around that error.
In the context of metering, we're seeing more and more e2e flakes
centered around installations not being able to be installed due to
failed InstallPlan resources. These failed installations are typically
due to CRD conflicts being returned from the apiserver and OLM not
handling that error correctly and the result is metering can't be
installed.
We can workaround this by detecting any failed InstallPlan resources
that we know are due to conflicting resource versions and attempt to
re-install metering in the applicable test handlers.

/retest

/retest

I need to move a couple of things outside of this PR:

Need to land the expired Report custom resources fix that has incorrect re-queue logic.
Need to move any of the cmd,pkg/deploy changes outside of this PR.
Stop running the NFS test every CI cycle.

This appears to be working locally with all of the commits cherry-picked together.
/hold

/hold cancel

This may require backports to 4.6/4.7 as we're still seeing this pop up frequently in those release branches e2e runs.


Why the merge tool is so ugly. Why?

Why the merge tool is so ugly? Looks like somebody got  brainfart implementing this :D
Ok sorry, but could you do this in better way?
Like it is done "Sublime merge", "JetBrains"

It's almost done by clicking on "Compare Changes" but it's read only. So lets do it this way - make left side (local copy) editable so the user just could copy some stuf from incoming changes
Originally posted by @FDiskas in https://github.com/microsoft/vscode/pull/47884#issuecomment-726805988

/duplicate of #37350


Codebase optimization and refactoring

cleaned up code
removed lot of extra stuff
used better practices
remove lots of try/except blocks
better use of regex
use of argparse (for argument handling)
added checks to prevent errors

More could be organized to help readability and commented to help understand.

Thanks. Pushing to bearlike:refactor for now.


Make user responsible for producing their own Chrome Custom Tab intent instead of giving us a colour

Kept the current arrangement for now.

This would be a public API change. However, it would enable:
a) App developers can handle custom embedded web browser stuff on their own terms, including customizing its colours and other settings;
b) we can remove the transitive dependency on Chrome custom tabs.

I think for now this is not really worth it. Leaving it out for now.


Replace Moshi with generated marshaller for operation json serialization

Part of #572
Next step is to remove Moshi from SqlNormalizedCache

@sav007 should this be made configurable. I worry that most won't care about the optimization but will care about the additional methods the request parsing generates.

@digitalbuddha well I see your point but not sure if that won't be a messy to have it both. I fell like we already have too much configs, and it was our initial idea use generation instead of Moshi.
Plus I feel like we really won't benefit of saving couple methods here. Maybe we can later optimize it a little bit when such concern raised.

@digitalbuddha I completely agree.
@sav007 In this PR, I did not see you remove the dependency from the build.gradle. Did you remove it in another PR?

Are you going to remove moshi completely from this repository? It looks like it is still used: https://github.com/apollographql/apollo-android/search?utf8=✓&q=moshi&type=.


NibReusable -> Reusable & NibLoadable

Hi.
There is no need in strict NibReusable protocol conforming in register functions. You can use protocol composition type.

Thanks for this PR!
Yup, that convenience NibReusable protocol was added for convenience both for the consumer (easier to make your tableView cells conform to a single protocol) and clarity when reading the source.
But that was before Swift 3, when the syntax was still protocol<Reusable, NibLoadable> which was a bit verbose to use. Now that the syntax has changed in Swift 3 that convenience protocol isn't really needed anymore indeed 😉

I think that you should leave NibReusable as syntax sugar.

I think that you should leave NibReusable as syntax sugar.

🤔 But then what's the point of this PR, if you don't mind me asking?

If you will make a subclass of Reusable cell and make it NibLoadable you will get error on register of subclass. Because it doesn't conforms to NibReusable, but if you try to conform it to NibReusable you will get error that your subclass conforms to Reusable protocol twice.
Or you just make a cell that is Reusable, NibLoadable and you will get an error too.
That is the point of PR.
Lets create cell with theme.
class MyCellWithTheme: UITableViewCell, Reusable {
  var theme: Theme {
    didSet {
      setupTheme()
    }
  }
  func setupTheme() {
     // set bg color, fonts for default labels
  }
}

And this will not work in 3.0.0, but succeeds in my PR.
// Subclass
class MyCustomCellWithTheme: MyCellWithTheme, NibLoadable {
  @IBOutlet private var doStuffbutton: UIButton!
  override func setupTheme() {
    super.setTheme(theme)
     // set bg color, fonts for default labels
  }
}

// Two protocols conforming
class MyAnotherCell: UITableViewCell, Reusable, NibLoadable {
}

And it will not brake existing API, so there is no need to deprecate NibLoadable protocol, and now it can be used as syntax sugar (no strict conforming).
// And this will work too
class MyAnotherCell: UITableViewCell, NibReusable {
}

Ok, I think I understand, but what surprises me then is that doing this change:
-  final func register<T: UICollectionViewCell>(cellType: T.Type) where T: NibReusable {
 +  final func register<T: UICollectionViewCell>(cellType: T.Type) where T: Reusable & NibLoadable {

Would change anything in your scenario… I mean, isn't it the same to conform to NibReusable (which is convenience for Reusable & NibLoadable) or to conform to Reusable & NibLoadable?
Or maybe if it is different — because NibReusable is a separate protocol conforming to both protocols and not strictly a & protocol composition — it would be simpler if that PR just changed protocol NibReusable: Reusable, NibLoadable to typealias NibReusable = Reusable & NibLoadable?

Yep, it is different — because NibReusable is a separate protocol.
😱 typealias for protocol composition it's brilliant idea.
Reusable & NibLoadable equals to NibReusable in both cases
a)typealias NibReusable = Reusable & NibLoadable. Reverse equatable.
b) protocol NibReusable: Reusable, NibLoadable. Reusable, NibLoadable object can't conform to NibReusable.
But I think conformance to 2 protocols Reusable & NibLoadable in func definitions is better than conformance to one typealias NibReusable it clearly shows a list of base protocols to which you should conform.
Cause at first look at this function (as a new programmer who uses this framework at the first time) you will see, that you need to implement 2 protocols in your class.
final func register<T: UICollectionViewCell>(cellType: T.Type) where T: Reusable & NibLoadable

And in the case below you will see one protocol, but in fact there are two of them, so you should check both of them anyway, but it implicit.
final func register<T: UICollectionViewCell>(cellType: T.Type) where T: NibReusable

I'm agree that those protocols conform-and-go, but I prefer to check all frameworks used by me (especially small ones) for what is under the hood.

Cool, let's go for this then! 👍

Using typealias NibReusable instead of protocol NibReusable, but still keeping it (both for retro-compatibility and convenience for users of the lib)
Switching to explicit use of Reusable & NibLoadable in the function implementations is ok for me if you think it's more clear

🤔 That's the 4th time I relaunch the Travis-CI build because each time it errors (it doesn't launch the job and fail, no, it just errors without even launching the build).
I have no idea if that's linked to the shortage that Travis-CI is currently experiencing with OSX jobs or not, so if we should change something to make it build again or not, I'm a bit confused…
(same problem with #38)

Ok, still don't know why the Travis job keeps erroring, and I have no idea how to investigate further… so merging anyway after testing it locally.


[BUG] Unable to upgrade from Harvester v1.1.2 to v1.2.0 because of wrong API group version in version.yaml

Describe the bug
Harvester's upgrade to v1.2.0 does not appear in the UI in non-airgapped mode.
When trying to apply the airgapped procedure manually, I downloaded the version.yaml from here, and I was not able to deploy because of the version in the YAML.
In the version.yaml file, the kind Version is associated with the group/version: harvesterhci.io/v2beta1 which does not exist in Harvester v1.1.2. Replacing in the YAML, v2beta1 by v1beta1 and applying the file makes the upgrade option appear in the UI.
To Reproduce
Have a Harvester v1.1.2 in an environment with access to internet, and see that the upgrade to v1.2.0 never appears.
Expected behavior
Since the version.yaml exists, the upgrade option should appear.
Support bundle
None needed.
Workaround

Download the file version.yaml file from here.
Modify it to change v2beta1 to v1beta1
Run kubectl apply -f version.yaml with the modified file on a management node
See the upgrade option appear in the UI, and proceed.

Alternatively, use this corrected content for the version.yaml file:
apiVersion: harvesterhci.io/v1beta1
kind: Version
metadata:
  name: v1.2.0
  namespace: harvester-system
spec:
  isoChecksum: '267d65117f6d9601383150b4e513065e673cccba86db9a8c6e7d3cb36a04f6202162f1b95c3c545a7389c4f20f82f5fff6c6e498ff74fcb61e8513992b83e1fb'
  isoURL: https://releases.rancher.com/harvester/v1.2.0/harvester-v1.2.0-amd64.iso
  releaseDate: '20230908'

@belgaied2 The reason is that v1.2.0 was not published to the upgrader due to  https://github.com/harvester/harvester/issues/4519, v1.2.1 is coming soon next week and we'll update it.


Live Migartion Fail

I'm not able to do a live migration between two 100% identical Google Cloud machines (in the same zone) both running Ubuntu 16.04 and the same (latest) LXD + CRIU.
lxc move zJY-movetest06241 lxd-uscentral-2:zJY-movetest06241 error: Error transferring container data: restore failed: (10.727191)    683: Error (pipes.c:226): Can't restore pipe size: Operation not permitted (10.728790)    417: Error (pipes.c:226): Can't restore pipe size: Operation not permitted (10.729151)    680: Error (cr-restore.c:1350): 683 exited, status=1 (10.731129)    680: Error (pipes.c:226): Can't restore pipe size: Operation not permitted (10.885172) Error (cr-restore.c:1352): 20679 killed by signal 9 (10.914615) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.DwwGDn.cr.1.ghost] ghost: No such file or directory (10.914625) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.hbp7Hn.cr.2.ghost] ghost: No such file or directory (10.950649) Error (cr-restore.c:2182): Restoring FAILED.
On next try I got this:
lxc move lxd-uscentral-2:zJY-movetest06241 zJY-movetest06241 error: Error transferring container data: restore failed: (00.637016)    371: Error (files.c:594): 371: Can't setup 15 file owner pid: No such process (00.638986)      1: Error (cr-restore.c:1350): 371 exited, status=1 (00.690242) Error (cr-restore.c:1352): 765 killed by signal 9 (00.725849) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.CA5pel.cr.1.ghost] ghost: No such file or directory (00.725855) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.wA0ZNk.cr.2.ghost] ghost: No such file or directory (00.756351) Error (cr-restore.c:2182): Restoring FAILED.
Please advise.
Update: when creating a new Ubuntu 16.04 based, empty/plain container live migration works.

On Fri, Jun 24, 2016 at 06:22:45AM -0700, David Reiner wrote:

I'm not able to do a live migration between two 100% identical Google Cloud machines (in the same zone) both running Ubuntu 16.04 and the same (latest) LXD + CRIU.
lxc move zJY-movetest06241 lxd-uscentral-2:zJY-movetest06241 error: Error transferring container data: restore failed: (10.727191)    683: Error (pipes.c:226): Can't restore pipe size: Operation not permitted (10.728790)    417: Error (pipes.c:226): Can't restore pipe size: Operation not permitted (10.729151)    680: Error (cr-restore.c:1350): 683 exited, status=1 (10.731129)    680: Error (pipes.c:226): Can't restore pipe size: Operation not permitted (10.885172) Error (cr-restore.c:1352): 20679 killed by signal 9 (10.914615) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.DwwGDn.cr.1.ghost] ghost: No such file or directory (10.914625) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.hbp7Hn.cr.2.ghost] ghost: No such file or directory (10.950649) Error (cr-restore.c:2182): Restoring FAILED.

This looks like a CRIU bug; the F_SETPIPE_SZ fcntl requires real root,
and this doesn't go through the usernsd proxy that criu sets up. Can
you file a bug here: https://bugs.launchpad.net/ubuntu/+source/criu

On next try I got this:
lxc move lxd-uscentral-2:zJY-movetest06241 zJY-movetest06241 error: Error transferring container data: restore failed: (00.637016)    371: Error (files.c:594): 371: Can't setup 15 file owner pid: No such process (00.638986)      1: Error (cr-restore.c:1350): 371 exited, status=1 (00.690242) Error (cr-restore.c:1352): 765 killed by signal 9 (00.725849) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.CA5pel.cr.1.ghost] ghost: No such file or directory (00.725855) Error (files-reg.c:516):  - XFail [/tmp/.ZendSem.wA0ZNk.cr.2.ghost] ghost: No such file or directory (00.756351) Error (cr-restore.c:2182): Restoring FAILED.

This looks like another CRIU bug where we need a pid helper for dead
pids who still own files. Can you file another bug with this log at
the URL above?
Thanks!

Please advise.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/lxc/lxd/issues/2153

As @tych0 mentioned, we're tracking CRIU bugs at https://launchpad.net/ubuntu/+source/criu rather than here. Unless the issue is with how LXD itself interacts with CRIU.
Please file a bug on Launchpad and we'll pick it up from there, thanks!


true standalone html download/CLI

The zip-based download approach is not that great from a user perspective, and makes server integration more complicated than it needs to be.
This PR (will) contain an updated HTML exporter that embeds its CSS and JS directly in the notebook.
Additionally, we'll want to be ready for nbconvert 4.2 which will likely obviate the need for the custom command line script... though it may be worth maintaining, in a simpler form, if it is more convenient for users/integrators.

Added tests for exported HTML: still having some issues with font-awesome, considering just going with unicode chars for the navigation... but i can imagine wanting icons in my presentations, so it's probably worth inlining them.

Hooray! Always unicode problems on anaconda cloud.... I wonder if this is a thing worth fixing with LOCALE?
I fixed up the unicode errors, and updated the doc, as we'll no longer offer the zip format...

Once the linux and osx builds run, going to merge this, close https://github.com/Anaconda-Server/anaconda-nb-extensions/issues/39 and refocus efforts on https://github.com/Anaconda-Server/anaconda-nb-extensions/issues/135 (already in progress while waiting for builds)

All :green_heart: for osx and linux-64.
I pronounce this done.... but we'll see what happens on master as I rejiggered the ci config.


LEAN-4073: LW-FY25-Q2-rollover: Scrolling is not working correctly af…

Update the handleScrollToBibliographyItem function to support scrolling to the selected comment. Simplify the scrolling logic, renaming the function and variables for more clarity.

@mnatsheh
Based on our discussion, I have removed the changes made to the article editor. The scrolling is now handled by overriding the handleScrollToBibliographyItem function, updating the ID selector for more accuracy, and simplifying the scrolling logic.

@nghazzawi-atypon you got rid of the bibliography item logic, which we still need.

This is not only for comments, it's also supposed to work when clicking on a bibliography item suggestion in the history tab. If you insert a bibliography item and click on the suggestion, I suspect it will not work.

This is not only for comments, it's also supposed to work when clicking on a bibliography item suggestion in the history tab. If you insert a bibliography item and click on the suggestion, I suspect it will not work.

@mnatsheh  thank you for pointing out the side effect. I've addressed it in the update. Please let me know if there are any additional changes required


🌉 Eimis bridge template

The goal of this issue is to provide a better support to organizations willing to join the experimentation.
Template
From https://github.com/matrix-org/matrix-appservice-bridge we could make a github template specific to our needs.

Some test here : https://github.com/ad2ien/test-matrix-bridge

start dev env for a bridge with a synapse docker-compose setup
create a ghost user
send a message with this ghost user
create a user and invite existing user(s)


Fix sign for stage-to-time conversion in OpticalLaserDelay

This is a bit embarassing, and I'm still puzzled how it actually came to be. I double-checked it multiple times now with different datasets and it's consistent. Note that the problem is only relevant (in the sense of giving wrong values) when combining trigger and stage delay, by themselves it just seems like an odd definition.
@JamesWrigley Do you know whether this was used at MID already (only other really supported instrument)? This will change the values actually, though the impact is only the sign if not combining with other delay sources.

Then I'm relieved, thanks!


Docker Zulip Release v1.3.10

Current dev branch: dev-v1.3.10
Wait for Zulip to merge the modified scripts and the dockervoyager.pp manifest, see https://github.com/zulip/zulip/pull/450.

I'm going to move the changes from my pull request in the repo so I can finally release it.

Hi, I'm interested to run a docker image of zulip, and i see recently the PR you manage here : https://github.com/zulip/zulip/pull/450
What is the best option actually, wait and see for a merge on zulip repository ? or install directly your docker release / image ?
Thanks a lot for your work !
Rey.

@reyman I currently don't have an up to date status of the PR https://github.com/zulip/zulip/pull/450 and when it may get merged.
But a good way would be to use the image here, cause the version in the PR has less features (The PR doesn't contain the automatic backup and some other fancy stuff).

Ok :)
And i suppose migration between the two images can be made later, so thanks :)

@reyman Migrating between them will not be possible!
My galexrt/zulip image uses different structures than the Docker image in the PR.
I would recommend you using this image here, because it has more features, like automatic backups.

Pushed the changes required for Zulip 1.3.10 to the branch dev-1.3.10.

Closing as #61 is the last issue to be resolved before the new release can be released.


Add Actions

We should add the various actions. Requires #2  to be done.

I can work on this, unless @rodkings is already on it.


CON-1120: Edit Conclave Mail Doc

I have made the changes to simplify and reorder the contents of the Conclave Mail doc. A couple of other docs which refer to the conclave mail doc were changed too. Please review.

I just noticed that this has been raised against release/1.3! This needs to be raised against master! Please re-raise.

Never mind, disregard this comment!


Deployment targets

This lowers the deployment target for iOS and OS X to 8.0 and 10.10 respectively.

Merged as dac1f27


Properly defining floats

Scratching my own itch (#13), in a hacky way...
Also add swagger "description" fields to attributes, albeit also hacky.  Proper support should be included in Cerberus more likely.  Right now I'm adding a "description" attribute on the validation rules in settings.py in Eve.

Hey thanks for this. I went the "less hacky way" instead, see https://github.com/nicolaiarocci/eve-swagger/commit/6d7e976226602863fd993779ef1dd1e10387da55. Would you resubmit the 'description' field support as a stand-alone PR? I'm willing to merge that one.


Full automated test code coverage

To enable continuous deployment and leave pre-release, we should have full code coverage of the bindings in the automated test project. It also needs clarified in the contribution guidelines that any changes are expected to have accompanying code coverage.

It's likely we may need to look into including a custom app that we can test against. The current tests are dependent on Dynamics 365 modules being installed and the Dynamics 365 apps probably don't provide all the possible permutations that we need to provide full coverage.

@DavidRcapgemini @markcunninghamuk I've gone through the bindings and I suggest we create a cap_PowerAppsSpecFlowBindings_Mock solution with the following -

[ ] Multiple business process flows for an entity

[ ] Multiple stages for a business process flow
[ ] Text. option set, multi-select option set, boolean, numeric, currency, datetime and lookup fields on a business process flow
[ ] A business process flow error (possibly a mandatory boolean field in a stage will allow for this)

[ ] Multiple dashboards
[ ] Two entities

[ ] A one-to-many relationship
[ ] a many-to-many relationship
[ ] Text, option set, boolean, numeric, currency, datetime and lookup fields on a form
[ ] All of the above field types (where applicable) on a form header
[ ] Multiple forms on an entity
[ ] Three tabs on a form, two visible, one hidden
[ ] Mandatory and optional fields
[ ] A form notification
[ ] An option set field on a form with multiple options
[ ] A read-only field
[ ] A visible field and hidden field on a form
[ ] A sub-grid on a form with view selector enabled and text, option set, boolean, numeric, currency, datetime and lookup fields on a view
[ ] An entity configured for categorized search
[ ] A lookup dialog (the kind shown when using Xrm.Utility.lookupObjects)
[ ] A lookup on a form with view selector enabled and multiple views
[ ] A lookup on a form for multiple entities (e.g. customer or regarding field)
[ ] An entity enabled for quick create with a quick create form
[ ] Text, option set, boolean, numeric, currency, datetime and lookup fields on a quick create form
[ ] A timeline on a form for an entity enabled for activities

That should cover everything we need broadly, I'm sure we'll find more things that we need when writing the tests.

Thanks Max.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Max Ewing<EMAIL_ADDRESS>Sent: Wednesday, December 9, 2020 7:53:43 AM
To: Capgemini/powerapps-specflow-bindings<EMAIL_ADDRESS>Cc: markcunninghamuk<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Capgemini/powerapps-specflow-bindings] Full automated test code coverage (#18)
@DavidRcapgeminihttps://github.com/DavidRcapgemini @markcunninghamukhttps://github.com/markcunninghamuk I've gone through the bindings and I suggest we create a cap_PowerAppsSpecFlowBindings_Mock solution with the following -

Multiple business process flows for an entity
*    Multiple stages for a business process flow
*    Text. option set, multi-select option set, boolean, numeric, currency, datetime and lookup fields on a business process flow
*    A business process flow error (possibly a mandatory boolean field in a stage will allow for this)
Multiple dashboards
Two entities
*    A one-to-many relationship
*    a many-to-many relationship
*    Text, option set, boolean, numeric, currency, datetime and lookup fields on a form
*    All of the above field types (where applicable) on a form header
*    Multiple forms on an entity
*    Three tabs on a form, two visible, one hidden
*    Mandatory and optional fields
*    A form notification
*    An option set field on a form with multiple options
*    A read-only field
*    A visible field and hidden field on a form
*    A sub-grid on a form with view selector enabled and text, option set, boolean, numeric, currency, datetime and lookup fields on a view
*    An entity configured for categorized search
*    A lookup dialog (the kind shown when using Xrm.Utility.lookupObjectshttps://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-utility/lookupobjects)
*    A lookup on a form with view selector enabled and multiple views
*    A lookup on a form for multiple entities (e.g. customer or regarding field)
*    An entity enabled for quick create with a quick create form
*    Text, option set, boolean, numeric, currency, datetime and lookup fields on a quick create form
*    A timeline on a form for an entity enabled for activities

That should cover everything we need broadly, I'm sure we'll find more things that we need when writing the tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Capgemini/powerapps-specflow-bindings/issues/18#issuecomment-741600023, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFKLYCEV3LVBHRWYYERP7H3ST4UIPANCNFSM4R667CDQ.

Branch here https://github.com/Capgemini/powerapps-specflow-bindings/tree/test/full-test-coverage

@DavidRcapgemini @markcunninghamuk I've updated the UI test build to build and copy the mock solution. I've also added a SpecFlow BeforeTestRun hook to import the solution and an AfterTestRun hook to remove it.
Should be easy to start picking up tests now!


[stable/traefik] Fix compress option identation when proxy protocol i…

What this PR does / why we need it:
When using the proxyProtocol, the compress option is generated as a child of proxyProtocol which is not the correct configuration, if should be under entryPoints.httpor entryPoints.https.

/lgtm


Version .84 breaks Honeywell Climate Component

Home Assistant release with the issue: 0.84.3

Last working Home Assistant release (if known): 0.83.3
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io on ResinOS on RPi3

Component/platform: Honeywell Thermostat climate component
https://www.home-assistant.io/components/climate.honeywell/

Description of problem:
I updated hassio to 0.84.3, and all of my honeywell thermostats disappeared from homeassistant. I restarted several times to see if they would come back and they did not. I downgraded back to 0.83.3 and they all came back immediately.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
climate:
  - platform: honeywell
    username: !secret honeywell_username
    password: !secret honeywell_password
    scan_interval: 600
    region: us

**Traceback (if applicable):**N/A

Additional information:

Any errors in the logs?

@uchagani I had downgraded to 0.83.3 to get my thermostats back. To double check the logs, I upgraded to the latest 0.84.5 to recreate the issue. Thermostats were still there after the update. I'll keep monitoring it and update if the issue returns.

I'm on 0.90.2 and can confirm that this is not working for me. I have not attempted to downgrade.
Triple-checked my credentials, they are valid.
 Try waiting a bit.

my scan interval is 600 and this error never returns though, so I suspect it has nothing to do with actual rate limiting issues. Could there be an API change causing this?


ReqMgr2 CouchDB update function restriction

ReqMgr2 update function can only be called directly from ReqMgr2 service, not e.g. via curl with exception of ReqMgr2 developers. Figure out correct restrictions.

@ticoann do you understand this issue?

We can change reqmgr  couchdb 2 ways, going through reqmgr2 api and direct access to couchdb. There are more control over what it can be done with reqmgr2 api. (which permission is given to which function, etc). We should have the same control on direct couch access. But this might be hard to do that.
One thing we can do is restrict direct couch update access to local  and only allow reqmgr2 api access.


Add basic lua hot-loading support with libfswatch

When a file is required, begin watching it. If the file is changed, re-load it.
libfswatch is a cross-platform library to enable this.
In future, it may be desirable to track the actual modules required by each module and reload dependents after a module is changed.

Scratch that, libfswatch is GPL, need to find an MIT alternative or roll our own.

I take that back. The MIT license is compatible with GPL and thus linking from MIT to GPL actually satisfies the GPL terms.


Update dependencies in setup.py.

Add missing dependencies: Shapely and openmdao.
Move pytest to tests_require.

Technically openmdao is an optional dependency, I can merge once that is changed.

Updated accordingly.


The Installation of the Knative Istio controller aborts on a private cluster.

Describe the bug
The Installation of the Knative Istio controller aborts  on a private cluster.
Error from server (InternalError): error when creating "https://github.com/knative/net-istio/releases/download/v0.21.0/net-istio.yaml": Internal error occurred: failed calling webhook "config.webhook.serving.knative.dev": Post https://webhook.knative-serving.svc:443/config-validation?timeout=10s: dial tcp <IP_ADDRESS>:8443: i/o timeout
The networking-istio Pod fails with:
Failed to start configuration manager
Expected behavior
Installation process works
To Reproduce
Steps to reproduce the behavior.
1.) create cluster:
gcloud container clusters create private-cluster-1 \
    --create-subnetwork name=my-subnet-1 \
    --enable-master-authorized-networks \
    --enable-ip-alias \
    --enable-private-nodes \
    --master-authorized-networks="$(curl -s https://icanhazip.com/)/32" \
    --master-ipv4-cidr <IP_ADDRESS>/28 \
    --machine-type=n2-standard-2 --max-nodes=3 --min-nodes=1

2.)
install istio conforming https://istio.io/latest/docs/setup/install/istioctl/  Verion 1.9.1
istioctl install

kubectl apply --filename https://github.com/knative/serving/releases/download/v0.21.0/serving-crds.yaml
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.21.0/serving-core.yaml

kubectl apply --filename https://github.com/knative/net-istio/releases/download/v0.21.0/net-istio.yaml

Error from server (InternalError): error when creating "https://github.com/knative/net-istio/releases/download/v0.21.0/net-istio.yaml": Internal error occurred: failed calling webhook "config.webhook.serving.knative.dev": Post https://webhook.knative-serving.svc:443/config-validation?timeout=10s: dial tcp <IP_ADDRESS>:8443: i/o timeout
Knative-GCP release version
v0.21.0
Additional context
If the cluster is not private the installation works

I think it is platform specific and I need to create a firewall rule..
elastic/cloud-on-k8s#1437
I works if I open all ports...I will try to find out which ports must be opened in details..

I will try to find out which ports must be opened in details..

The Kubernetes API server must be able to reach the Knative Webhooks.
They are listening on 8883.
A better approach is too have them listen on a port already allowed by the default firewall rules: 443 (requires to run as root) or 10250. This requires patching Knative release YAML.

@JRBANCEL
Thanks for your help.
I opened port 8883 (and 8443 because of nginx ingress) instead of *
Now it works. BUT:
-The deployment process (hellpworld-go) is much slower than with all ports open (until the revision gets active).
-running the knavite-istio controller installation template https://github.com/knative/net-istio/releases/download/v0.21.0/net-istio.yaml. is  10 times slower than with alle ports open.
There must be traffic which is blocked an slows the processes down due to timeouts. How could I investigate it??
In which file I can patch the listen port from 8883 to 443. I did not find it in my installation files.
# install istio

cd /Users/sklose/Downloads/istio-1.9.1
export PATH=$PWD/bin:$PATH
istioctl install --set profile=default -y

# install knative serving

kubectl apply --filename https://github.com/knative/serving/releases/download/v0.21.0/serving-crds.yaml
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.21.0/serving-core.yaml

kubectl apply --filename https://github.com/knative/net-istio/releases/download/v0.21.0/net-istio.yaml

# install knative  eventing

kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/eventing-crds.yaml
kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/eventing-core.yaml

kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/in-memory-channel.yaml
kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.21.0/mt-channel-broker.yaml

# install knative  knative-gcp

export KGCP_VERSION=v0.21.0
kubectl create namespace cloud-run-events
kubectl apply --filename https://github.com/google/knative-gcp/releases/download/${KGCP_VERSION}/cloud-run-events-pre-install-jobs.yaml

kubectl apply --selector events.cloud.google.com/crd-install=true \
--filename https://github.com/google/knative-gcp/releases/download/${KGCP_VERSION}/cloud-run-events.yaml

kubectl apply --filename https://github.com/google/knative-gcp/releases/download/${KGCP_VERSION}/cloud-run-events.yaml

I opened the port: Source --master-ipv4-cidr (<IP_ADDRESS>/28) Target: ServiceAccount
If I add the port to the generated firewall rule k8s-fw-* with source <IP_ADDRESS>/0 and target tag gke-private-cluster-1-e9fe715e-node   the problem seems to be solved (creation is 10 faster).

.


C++ IR: Fix performance of large value-initialized arrays

https://github.com/faragon/libsrt/blob/2830d1fc43e875969db6f7bcd34517951fbd7f6c/test/counter.h#L97 causes the creation of a huge array as a class member in libstdc++. That blew up in https://github.com/Semmle/ql/blob/ba4812c4ed/cpp/ql/src/semmle/code/cpp/exprs/Literal.qll#L245. There were two problems:

The inline predicates isInitialized and isValueInitialized on ArrayAggregateLiteral caused their callers to materialize every int that was a valid index into the array. This was slow on huge value-initialized arrays.
The isInitialized predicate was used in the TInstructionTag IPA type, creating a numbered tuple for each integer in it. This seemed to be entirely unnecessary since the TranslatedElements using those tags were already indexed appropriately.

I've amended the first commit with a one-line fix to cpp/ql/test/library-tests/literals/aggregate_literals/arrays_value_init.ql.

Fixed.

@dave-bartolomeo PR updated.


ActivityReminder: Obey system quiet mode & extend allowed dismiss delay

Obey system quiet mode
Extend allowed dismiss delay

Thanks,
It's pretty cool for the quiet mode. And I just saw you did another pull request with cool features too ;).
However for the "Dismiss delay" with the current implementation it can pose some problems if it's higher than the "Max inactivity".
I plan to rework this part to prevent such bug, be able to add a longer delay "Pause" (for meetings and such) and reduce the battery usage which is quite high right now.

Thanks for your feedback @Stiralbios. I added a notice to the README. I hope this is fine for now.

Thanks!


auth error

summary:  331 GiByte in 15h 42min 35.7sec - average of 6136 KiB/s
An error occurred uploading the document: googleapi: Error 401: Invalid Credentials, authError

kept getting this error when uploading large file
any suggestion?

+1: uploaded a folder with several files and subfolders. Let it ran successfully for a while then stopped at "An error occurred: googleapi: Error 401: Invalid Credentials, authError".
Could it be due to Oauth token expiration?
https://developers.google.com/identity/protocols/OAuth2

Access tokens have limited lifetimes. If your application needs access to a Google API beyond the lifetime of a single access token, it can obtain a refresh token. A refresh token allows your application to obtain new access tokens.

Should "refresh token" periodically when uploading folders?
Env:
64 bits
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.2 LTS
Release:        14.04
Codename:       trusty

+1 Similar situation: was uploading a huge directory (overnight) and in the morning I saw that an error occurred: Error 401: Invalid Credentials, authError.
Seems to be the expiration of the token.

Has anyone found a way around this expiration?  I'm running into the same issue trying to upload a very large directory.

Can you see if this situation has improved in gdrive 2? I have been able to do 10 hours+ uploads without a problem at least.

I was unaware there was an update!  I will check it out when I get a chance and report the results back.

Installed gdrive 2 and am currently uploading a very large directory.  9+ TB  Speed is great at 7-9 MB/s.
I initially tried the sync upload and it was bouncing back an error "Failed to prepare local files: readdirent: remote I/O error" on Cent (nfs mount to drive).
The error I got for sync upload on the windows install was:
Failed to prepare local files: GetFileAttributesEx Z:\xxxxxxxxxxxxxxx\xxxxxxxxxxxxxx\xxxxxxxxxxxxxxxx\xxxxxxxxxxxxx\xxxxxxxxxxxx\xxxxxxxxxxxxxxxxxxxxx\xxxxxxxxxxxxxxxxxxxxx.PRV\b50e39c2-b8f9-44a5-bb02-6391d58bc576+610ee9e9ee03d754fc88b590 48000.cfa: The system cannot find the path specified.

Same problem here.  Token expires after about 1 day, and no refresh.
I thought there is a long life token, or auto-refresh.    If it is not possible to have a token that lasts forever or at least a few months, this is quite useless.   Thank you.
Failed to find root dir: googleapi: Error 401: Invalid Credentials, authError
root@pa005:~/.gdrive# more token_v2.json {   "access_token": "xxxx",   "token_type": "Bearer",   "refresh_token": "yyy",   "expiry": "2016-12-19T13:21:01.99092458-08:00" }


Not working on Windows

I am having to work on a Windows XP machine today, and node-ecstatic does not appear to work on WIndows.

Fixed with your pull request!


[WIP] [#62] add refactored method for Japanese MinHashLSH-based near-deduplication

https://github.com/EleutherAI/dps/issues/62

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


add config and create_model of uniformer

Codecov Report

Merging #1418 (0e2697b) into main (fc7a1eb) will decrease coverage by 0.22%.
The diff coverage is 64.78%.

@@            Coverage Diff             @@
##             main    #1418      +/-   ##
==========================================
- Coverage   68.61%   68.38%   -0.23%
==========================================
  Files         294      300       +6
  Lines       16123    16490     +367
  Branches     2601     2675      +74
==========================================
+ Hits        11062    11277     +215
- Misses       4317     4471     +154
+ Partials      744      742       -2

Impacted Files
Coverage Δ

towhee/models/uniformer/uniformer.py
61.85% <6.06%> (-7.26%)
:arrow_down:

towhee/models/movinet/movinet.py
61.70% <36.00%> (-9.73%)
:arrow_down:

towhee/models/uniformer/config.py
96.42% <96.42%> (ø)

towhee/models/clip/clip_utils.py
32.52% <0.00%> (-42.28%)
:arrow_down:

towhee/models/omnivore/omnivore.py
65.30% <0.00%> (-13.08%)
:arrow_down:

towhee/engine/execution/pandas_execution.py
80.00% <0.00%> (-6.67%)
:arrow_down:

towhee/models/clip/clip.py
87.20% <0.00%> (-1.54%)
:arrow_down:

towhee/utils/git_utils.py
51.89% <0.00%> (-0.88%)
:arrow_down:

towhee/hub/repo_manager.py
23.96% <0.00%> (-0.82%)
:arrow_down:

towhee/models/drl/drl.py
18.07% <0.00%> (-0.62%)
:arrow_down:

... and 18 more

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 fc7a1eb...0e2697b. Read the comment docs.


"Choose action command invoke locations" should provide the corresponding context values

The "Choose action command invoke locations" section says where you can show the command, but it doesn't say how the locations map to the context values.

Choose action command invoke locations
The first thing you need to decide is where your action command can be triggered (or more specifically, invoked) from. By specifying the context in your app manifest, your command can be invoked from one or more of the following locations:

The buttons at the bottom of the compose message area.
By @mentioning your app in the command box. Note: You cannot respond with a bot message inserted directly into the conversation if your messaging extension is invoked from the command box.
Directly from an existing message via the ... overflow menu on a message. Note: The initial invoke to your bot will include a JSON object containing the message from which it was invoked, which you can process before presenting them with a task module.

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

ID: efcdf768-1513-2249-b344-bf38ef64c70d
Version Independent ID: 415b5d57-2d41-9540-55a7-2a33a4315e37
Content: Define messaging extension action commands - Teams
Content Source: msteams-platform/messaging-extensions/how-to/action-commands/define-action-command.md
Product: msteams
GitHub Login: @clearab
Microsoft Alias: anclear

Could you please add documentation for context information in respective point ?

compose message area
Command context = compose
command box
Commands context = commandBox
Existing message via the ... overflow menu
Commands context = message


Add Next Permutation into Numerical Folder (Math)

Implement next permutation, which rearranges numbers into the lexicographically next greater permutation of numbers.
If such an arrangement is not possible, it must rearrange it as the lowest possible order (i.e., sorted in ascending order).
Link : HERE

I would like to contribute to the above problem in java as I am a participant of GSSOC'21. Kindly assign this to me.


[HUDI-4103] Fix CTAS test failures in TestCreateTable  for Spark3.2

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@XuQianJin-Stars The CI have passed,can you please take a review?


chore: bdd-gh-1574165139 to 0.0.1

chore: Promote bdd-gh-1574165139 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Missing assembly type Microsoft.Data.SqlClient.Server.Format in Microsoft.Data.SqlClient, Version=<IP_ADDRESS>

I'm attempting to create a new DacService object instance with the latest stable package installed (i.e. "v160.6161.0"), and I'm running on the .Net 6.0.
...Sadly I am met with these missing assembly type exceptions (TypeInitializationException) when attempting the create the construct the DacServices() object.
Code snippet
public string InitialiseDatabase(string dacpacRelativePath){

  var connectionString = "Data Source=(LocalDb)\\MSSQLLocalDB;Integrated Security=True";
  var instance = new DacServices(connectionString);

}

StackTrace:
System.TypeInitializationException
  HResult=0x80131534
  Message=The type initializer for 'Microsoft.SqlServer.Dac.DacServices' threw an exception.
  Source=Microsoft.SqlServer.Dac
  StackTrace:
   at Microsoft.SqlServer.Dac.DacServices..ctor(String connectionString)
   at B1Link.Audit.Tests.BasicTest.InitialiseDatabase(String dacpacRelativePath) in C:\..\..\B1NG-Service-Audit\B1Link.Audit.Tests\BasicTest.cs:line 44
   at B1Link.Audit.Tests.BasicTest..ctor() in C:\Users\Sebee\Development\B1 LINK MVP\B1NG-Service-Audit\B1Link.Audit.Tests\BasicTest.cs:line 24
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)

  This exception was originally thrown at this call stack:
    [External Code]

Inner Exception 1:
TypeInitializationException: The type initializer for 'SqlSchemaModelStaticState' threw an exception.

Inner Exception 2:
TypeLoadException: Could not load type 'Microsoft.Data.SqlClient.Server.Format' from assembly 'Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5'.```

Duplicate of #126

Item is duplicate to #126 - expected later this year.


Support ruby 2.2 and drop ruby 1.9.3

Since official support for 1.9.3 has ended a few days ago I think we should drop it too.
Ruby 2.2 needs eventmachine 1.0.7, and this required some changes to twitter-stream for which I created two pull requests, our Gemfile uses a branch of my fork until these PR have been merged.

Nice!! Does your fork of twitter_stream need any additional changes from mine?

Don't think so, I only found that you bumped the http_parser.rb version, which is included in my branch.

Looks good to me!

Great :)


RemotingContext injection in test

Adds support to inject RemotingContext in tests

This change is

Coverage decreased (-0.05%) to 60.4% when pulling 777ac3875a516391014be9bec0406781dfb111a4 on RemotingContext-Test-Injection into aa7a4c990209204b3b7e402074cb38806bf26d10 on master.


v1.2.1 Crash on start up Win7x64

Console window just pops up and immediately disappears. Running mcedit.exe from command window results in the following error:
Traceback (most recent call last):
File "", line 35, in
AttributeError: 'module' object has no attribute '_MEIPASS'

If anyone who had this issue previously could test this build for me it would be appreciated, we are trying to upgrade our build software but don't want to break this again. https://www.dropbox.com/s/diblg860juepoil/mcedit 1.5.x.x test.exe?dl=0


improve setup for unix

closes #25
fixes #24
@abhinavtyagi88
added a setup.sh file to simply project setup for unix based systems with a single command.
Also added .gitignore so as to avoid pushing node_modules and unnecessary files to github.
setup.sh
#!/bin/bash
cd frontend
npm install
npm start &
cd ../Backend
npm install
npm run start

.gitignore
# Node modules for both frontend and Backend
frontend/node_modules
Backend/node_modules

# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*

# Dependency directories
node_modules/
jspm_packages/

# Build directory for frontend (React)
frontend/build/
frontend/dist/

# Temporary build files
frontend/.next/
frontend/.nuxt/

# React cache
frontend/.cache/
frontend/.eslintcache/

# Production files
frontend/.env.production
Backend/.env.production

# Local environment files
frontend/.env.local
Backend/.env.local

# Optional npm cache directory
frontend/.npm/
Backend/.npm/

# IDE specific files
.vscode/
.idea/
*.sublime-workspace

# OS generated files
.DS_Store
Thumbs.db

This also updates the documentation file as:
Setup
On a UNIX system, run the following commands:
   chmod +x setup.sh
   ./setup.sh

will it work same as it is working on windows after merging

sure

all files are present as per my commit
also the .gitignore must be present in the root directory and node_modules files were removed as they can be installed locally using npm install.
I don't think this might cause issue on merging.

**merged succesfully **

I have merged and now I am facing this error

what was that module for?

wasn't the folder name Backend instead of 'backend' also try npm install in ./Backend

Solved but I have deleted previous node_modules and package-lock.json file and reinstall them


Changed private methods to protected to allow easier rewrites.

This is a simple change to make it easier to rewrite your classes.

I will include the changes related to the methods visibility in the next release


Extends docs stimulus contributors

Based off #10127
Extends off the PR by Thibaud on Stimulus contributors guide
Added more content with mine and @lb- reviews.

i would definitely like to see this to extend up to point where we get some idea for writing ### tests for these controllers as well,  because they could be really tricky sometimes. and as far as i am aware there's no docs present for those at all.

additionally, in Docs when describing about python tests. there's  a special section explaining how to run individual python tests
https://docs.wagtail.org/en/stable/contributing/developing.html#running-only-some-of-the-tests
we should also add that same symmetrical sections for npm run test:unit describing how to run tests individually for stimulus controllers and rest. describing command npm run test:unit DemoController.test.js.
about here: https://docs.wagtail.org/en/stable/contributing/developing.html#unit-tests-for-javascript
Cc : @lb- @Lovelyfin00.

Changes have been merged back into https://github.com/wagtail/wagtail/pull/10127


AB#5045

Proposed changes

Related issues

Checklist

[x] I consider the submitted work as finished
[x] I tested the code for its functionality
[ ] I wrote test cases for the relevant uses case
[ ] I added/update the relevant documentation (either on github or on notion)
[ ] Where necessary I refactored code to improve the overall quality

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@DallasP9124 and @r-joyce, please take a quick look and merge PR. This one has no issues as it's basically removing a line of code.


ErrorException: Undefined array key "adapter" in AbstractCommand.php:470

https://github.com/cakephp/phinx/blame/2e9d7d2fd6aa81187bc1c09892d0a9a6e321765b/src/Phinx/Console/Command/AbstractCommand.php#L470
When the Pninx environment is defined via the "connection" like in the https://book.cakephp.org/phinx/0/en/configuration.html, the "adapter" is not a part of the $envOptions, so it fails on error:
ErrorException: Undefined array key "`adapter`" in /opt/srv/super-secret-project/vendor/robmorgan/phinx/src/Phinx/Console/Command/AbstractCommand.php:470

Thanks for reporting the issue. I've released 0.16.4 that has a fix for this bug.


Create lists of supported hardware and software.

Should I prefer vaapi over vdpau?

supported hardware

I think, almost every Intel GPU came out later than 2010 is capable of hardware video decoding acceleration. Since 2011 they had H.264 capability. Unfortunately, I can't list them all.

and software

What works, works. Initially, I developed code to support NPAPI Flash, and during development also used MPlayer and mpv, so they should work. Although code changes, so what worked before can stop working now. It's easier to just try than guess.
If it doesn't work, it's a bug, and worth mentioning in the issue tracker. Project doesn't receive as much time as I wanted, but I'm planning to implement all API features eventually.

Should I prefer vaapi over vdpau?

Most often, you don't have a choice. If you have an Intel GPU, you have native VA-API support. If you have a NVIDIA GPU, you have native VDPAU support. In case you do have a choice, for example, for opensource Radeon drivers, you can select anything you want. There is no much difference between APIs, as they solve the same task.
If you have software which speaks only VDPAU, and hardware, which speaks VA-API, you can use libvdpau-va-gl as a traslation layer. If program of your choice supports multiple APIs, choose native one.

Does it work with wayland?

VDPAU at the moment have no Wayland support. VA-API have Wayland support. libvdpau-va-gl implements VDPAU, and therefore is not Wayland-capable.