Can't remove embedded class property

OrientDB Version, operating system, or hardware.

v2.2.13

Operating System

[x] Linux
[x] MacOSX
[ ] Windows
[ ] Other Unix
[ ] Other, name?

Expected behavior and actual behavior
After I dropped a property of an embedded class I want to be able to remove no longer existing property from the embedding class. After updating the record with a 'remove' statement, both console and studio report success, but 'select' shows that the property is still there in the embedding class.
Steps to reproduce the problem
I was able to reproduce this bug with two simple classes. Here is how the logic flows:

Create A class
Create B class
Create 'name' property for the A class
Embed A class into B
Insert a record into the B class by setting the embedded A class's name
Create a temporary 'name2' property in the A class
Copy data from name1 to name2 in the B class (needed for temp reasons)
Get rid of the no longer needed name2: drop 'name2' from A class
Now attempt to remove no longer needed 'name2' in the B class (in embedded class)
Observe that console reported that record was updated, but select shows it's still there

orientdb {db=Customers}> create class A extends V
Class created successfully. Total classes in database now: 77.

orientdb {db=Customers}> create class B extends V
Class created successfully. Total classes in database now: 78.

orientdb {db=Customers}> create property A.name STRING
Property created successfully with id=1.

orientdb {db=Customers}> create property B.aName EMBEDDED A
Property created successfully with id=1.

orientdb {db=Customers}> insert into B set aName = {"name":"Mike"}
Inserted record 'B#281:0{aName:A{name:Mike}} v1' in 0.001000 sec(s).

orientdb {db=Customers}> create property A.name2 STRING
Property created successfully with id=2.

orientdb {db=Customers}> info class A
CLASS 'A'
Records..............: 0
Super classes........: [V]
Default cluster......: a (id=277)
Supported clusters...: a(277), a_1(278), a_2(279), a_3(280)
Cluster selection....: round-robin
Oversize.............: 0.0

PROPERTIES
+----+-----+------+-----------------+---------+--------+--------+----+----+-------+-------+
|#   |NAME |TYPE  |LINKED-TYPE/CLASS|MANDATORY|READONLY|NOT-NULL|MIN |MAX |COLLATE|DEFAULT|
+----+-----+------+-----------------+---------+--------+--------+----+----+-------+-------+
|0   |name |STRING|                 |false    |false   |false   |    |    |default|       |
|1   |name2|STRING|                 |false    |false   |false   |    |    |default|       |
+----+-----+------+-----------------+---------+--------+--------+----+----+-------+-------+

orientdb {db=Customers}> info class B
CLASS 'B'
Records..............: 1
Super classes........: [V]
Default cluster......: b (id=281)
Supported clusters...: b(281), b_1(282), b_2(283), b_3(284)
Cluster selection....: round-robin
Oversize.............: 0.0

PROPERTIES
+----+-----+--------+-----------------+---------+--------+--------+----+----+-------+-------+
|#   |NAME |TYPE    |LINKED-TYPE/CLASS|MANDATORY|READONLY|NOT-NULL|MIN |MAX |COLLATE|DEFAULT|
+----+-----+--------+-----------------+---------+--------+--------+----+----+-------+-------+
|0   |aName|EMBEDDED|A                |false    |false   |false   |    |    |default|       |
+----+-----+--------+-----------------+---------+--------+--------+----+----+-------+-------+

orientdb {db=Customers}> update B set aName.name2 = aName.name
Updated record(s) '1' in 0.001000 sec(s).

orientdb {db=Customers}> select from B
+----+------+------+-----------------------+
|#   |@RID  |@CLASS|aName                  |
+----+------+------+-----------------------+
|0   |#281:0|B     |A{name:Mike,name2:Mike}|
+----+------+------+-----------------------+

orientdb {db=Customers}> drop property A.name2
Removed class property in 0.004000 sec(s).

orientdb {db=Customers}> info class A
CLASS 'A'
Records..............: 0
Super classes........: [V]
Default cluster......: a (id=277)
Supported clusters...: a(277), a_1(278), a_2(279), a_3(280)
Cluster selection....: round-robin
Oversize.............: 0.0

PROPERTIES
+----+----+------+-----------------+---------+--------+--------+----+----+-------+-------+
|#   |NAME|TYPE  |LINKED-TYPE/CLASS|MANDATORY|READONLY|NOT-NULL|MIN |MAX |COLLATE|DEFAULT|
+----+----+------+-----------------+---------+--------+--------+----+----+-------+-------+
|0   |name|STRING|                 |false    |false   |false   |    |    |default|       |
+----+----+------+-----------------+---------+--------+--------+----+----+-------+-------+

orientdb {db=Customers}> update B remove aName.name2
Updated record(s) '1' in 0.001000 sec(s).

orientdb {db=Customers}> select from B
+----+------+------+-----------------------+
|#   |@RID  |@CLASS|aName                  |
+----+------+------+-----------------------+
|0   |#281:0|B     |A{name:Mike,name2:Mike}|
+----+------+------+-----------------------+

I think this is the case with the embedded classes only. I tested with a straight forward single class properties and remove works fine, but with embedded it failed in my actual class and in the reproduced scenario above.
Thanks,

Hi @borov333
I'm checking it now
Thanks
Luigi


Dneto inline from mr534 by greg lunarg

Tiny fixup for https://github.com/KhronosGroup/SPIRV-Tools/pull/534
I'm not looking for a code review. :-)

Will wait for bots

I verified that this fixes the MSVC build failure.  It also passes its tests on Linux and Windows.
Will still wait for bots.


Provide information about using an OAuth 2.0 server to obtain B2C access tokens in API Management Dev Console

How to require B2C JWT tokens for requests to succeed is documented here, but now how to configure the API Management instance so that a B2C-enabled JWT token can be acquired when testing APIs through the API Management developer console is not.
This other document: https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-protect-backend-with-aad does explain how to configure such an OAuth 2.0 server and leverage that in the developer console while testing APIs.
This seems like quite a vital piece of the puzzle for someone implementing B2C in their application to protect APIs - making those APIs testable via dev console.

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

ID: 6515b078-b617-baf5-0e10-0001a6af887f
Version Independent ID: d40e7400-4c07-fe33-aca3-4dc8690c11d1
Content: Secure an Azure API Management API by using Azure Active Directory B2C
Content Source: articles/active-directory-b2c/secure-api-management.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@boylec
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Hi @boylec
Thank you for your feedback and patience. We've noted the discrepancy, and we'll work to address that. We've opened a work item to track this issue internally, so we'll close this issue. If you've any queries, please let us know. #please-close.


systemctl not found

On macOS Catalina: I tried installing it, but now it's just spamming "Starting Docker..." in the terminal, followed by "command not found: systemctl". What do I do?

Up! I have the same issue on macOS


update issue

Hello first. Upon running the function below on Android, if the contact has a picture assigned it gets deleted ( seems to be deleted). Same happens when trying to update a contact name. When the function below runs, the address is updated successfully but the pic is not visible on the device native contacts app. I have tested on both an emulator and a real device. The same code works OK for IOS without issues.
fn1() async{
Contact testContact = await FlutterContacts.getContact('some ID');
Address testAddress = Address('test', customLabel: 'test' , label: AddressLabel.custom);
testContact.addresses.insert(0, testAddress);
await testContact.update();
}
This is on version ^0.2.2 as I haven’t yet migrated to null safety.

Hi, I'll look into this shortly. But in the meantime, you should be able to move to 0.3.3 (or more recent) even if you're not using null-safety in the rest of your project.

Hey @Billy-80 I could reproduce the issue. https://github.com/QuisApp/flutter_contacts/commit/a391dbfe80063ef5e01eb1a2e1875bf3bef043cc should fix it, and I'll include in the next version.

Just cut a new version 0.3.3+1 with the fix. Thanks for reporting!
Feel free to reopen if needed.


Changelog for 1.4.18 release

FYI @ericpre @isuruf: we've tagged a new release. Please let us know if there are open PRs in constructor that need to get merged, and we can work on releasing that as well.

Thanks @chenghlee. There's a couple of PRs in contructor that needs attention,
https://github.com/conda/constructor/pull/458
https://github.com/conda/constructor/pull/449

Thanks @chenghlee. There's a couple of PRs in contructor that needs attention,
conda/constructor#458
conda/constructor#449

Thanks @chenghlee, yes, a constructor release would be good to remove the corresponding patches in conda-standalone. conda/constructor#458/conda/constructor#459 (similar fix) is an easy bug fix.


Clean up overrides.ts

Use inline imports to make the file less verbose and easier to change in the future.
Sort alphabetically instead of arbitrarily.
Name styles consistently like MuiPickers<component_name>, except for MuiPickersBasePicker.

There are a number of questions that haven't been answered:

Side question: Is it intended that things like defaultReduceAnimations are exported from the top-level index.ts?
If the prefix is really just Mui and not MuiPickers, that might cause clashes on things like the ModalDialog.
Maybe we need some reusable function that will build a standardized name. Something like ... buildStyleName ...

Though it's quite possible that you think it's fine to leave as is. Otherwise please let me know if you want me to change something in this PR.

Side question: Is it intended that things like defaultReduceAnimations are exported from the top-level index.ts?

@Philipp91 I think that it was exposed by chance. In the core repository, we edge against this risk with a folder and index file for each component we export. Adopt this same structure, before migration in the mono-repository could help.

If the prefix is really just Mui and not MuiPickers, that might cause clashes on things like the ModalDialog.

The picker components are part of the official set of Material-UI components. I think that the prefix should be Mui.

Maybe we need some reusable function that will build a standardized name. Something like ... buildStyleName ...

What's wrong with a duplication of the name of the component?

Okay, then this PR should be fine as is.

@oliviertassinari we cannot ship this PR.
We are not providing any other styling solution different from global overrides. So we must make all of our components style-able by global overrides.
I am so sorry for being too late @Philipp91. You are doing awesome contribution, thank you!

Even if we will provide classes prop. We need to make all the components like Calendar accept global overrides, just because it is useful as feature

So we must make all of our components style-able by global overrides.

@dmtrKovalenko The concern is interesting. The way we have solved that problem with the other components was by either 1. exposing the lower-level building blocks, allowing people to compose them or 2. to keep all the logic under a single public style sheet and hide a bit into private style sheets with the option to provide custom implementations.
However, this component is different. It's the first time I encounter a component with this set of challenges.
Any objection to make all the component that exposes their styles public?
I have noticed a couple of styles that are private, is it expected?

I don’t really know about all the components. But it looks useful from the custom design system perspective. If we can design anything in 1 place it is easier to reuse custom theme.

Private styles are unexpected.

How can we move forward? Maybe we should be less ambitious with the changes here. @Philipp91 Was was the original issue you were going after?

My ultimate goal was exporting the toolbar components (#1707). It doesn't really matter (for my use case) whether their styles are exported too or not.

Ok cool, in this case, maybe we should close and leave this pull request to the core team?

Sure, I'll let you take it over.


Add Ground Control Points support

There should be an option to use GCP while reconstructing. This should be used when aligning the reconstruction and during bundle adjustment.

Please @paulinus can you tell me when is gcp used inside the reconstruction ?
Is it absolutely necessary for images to have exif data ?

Ground control points supports can be found here : https://www.opensfm.org/docs/using.html#ground-control-points.
@btchouston regarding your questions :

GCP are used through the SfM reconstruction process during bundle adjustment.
No necessarily, but it will definitely helps and makes the difference between a bad or average reconstruction and a very good one.


Close void elements in Razor components

Fixes #12481
Engineering resolved unclosed void elements on https://github.com/aspnet/Mvc/pull/2956.
Docs have moved in that direction (for example, Unclosed void elements in topics (aspnet/AspNetCore.Docs #11881).
Is this a point-in-time problem for Blazor, or will they always require closure?
btw - There are two spots where <base> tags are still unclosed. I think those don't suffer from this issue; but if I'm incorrect, I can add those two on another commit here before we merge this. :ear:

I chatted with @NTaylorMullen @ajaybhargavb about this and we think this is a product issue. If the HTML spec allows for no end tag then we should too. Filled https://github.com/aspnet/AspNetCore/issues/10498.
But for the time being we can update the docs.

I'll open a follow-up docs issue tracking on that engineering issue and put it in the HOLD column on the project.


cargo audit reported vulnerabilities in 2.12.0

http-types 2.12.0 is the latest version. The default features pull in dependencies with reported vulnerabilities.
Steps to reproduce. The cargo check will create the Cargo.lock that cargo audit uses.
git checkout tags/v2.12.0
cargo check
cargo audit

PS C:\Users\cataggar\io\http-types> cargo audit
    Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 421 security advisories (from C:\Users\cataggar\.cargo\advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (135 crate dependencies)
Crate:         aes-soft
Version:       0.6.4
Warning:       unmaintained
Title:         `aes-soft` has been merged into the `aes` crate
Date:          2021-04-29
ID:            RUSTSEC-2021-0060
URL:           https://rustsec.org/advisories/RUSTSEC-2021-0060
Dependency tree:
aes-soft 0.6.4
└── aes 0.6.0
    └── aes-gcm 0.8.0
        └── cookie 0.14.4
            └── http-types 2.12.0

Crate:         aesni
Version:       0.10.0
Warning:       unmaintained
Title:         `aesni` has been merged into the `aes` crate
Date:          2021-04-29
ID:            RUSTSEC-2021-0059
URL:           https://rustsec.org/advisories/RUSTSEC-2021-0059
Dependency tree:
aesni 0.10.0
└── aes 0.6.0
    └── aes-gcm 0.8.0
        └── cookie 0.14.4
            └── http-types 2.12.0

Crate:         cpuid-bool
Version:       0.2.0
Warning:       unmaintained
Title:         `cpuid-bool` has been renamed to `cpufeatures`
Date:          2021-05-06
ID:            RUSTSEC-2021-0064
URL:           https://rustsec.org/advisories/RUSTSEC-2021-0064
Dependency tree:
cpuid-bool 0.2.0
└── polyval 0.4.5
    └── ghash 0.3.1
        └── aes-gcm 0.8.0
            └── cookie 0.14.4
                └── http-types 2.12.0

Crate:         stdweb
Version:       0.4.20
Warning:       unmaintained
Title:         stdweb is unmaintained
Date:          2020-05-04
ID:            RUSTSEC-2020-0056
URL:           https://rustsec.org/advisories/RUSTSEC-2020-0056
Dependency tree:
stdweb 0.4.20
└── time 0.2.27
    └── cookie 0.14.4
        └── http-types 2.12.0

warning: 4 allowed warnings found

The main branch updates to cookie v0.14.4 -> v0.16.0 and does not have the vulnerabilities. It would be good to publish a new version.

An alternative is to disable the optional feature.
http-types = { version = "2.12", default-features = false }

@jbr @yoshuawuyts @Fishrock123 Could one of you make a new release so this can be closed?

I am once again asking for a new release 😄


[1.21 & 1.22] Using commands /cc or /crazycrates causes extreme TPS loss

Spark link
https://spark.lucko.me/g6udnG4vq5
Server Version
1.20.4
Server Platform
Paper
Describe the bug
Using /cc or /crazycrates causes extreme lag/drop inTPS
Crate Type
None
Steps to reproduce

Use version 1.21 or 1.22 of the plugin
Type /cc or /crazycrates
Observe issue

Additional context
This issue does NOT occur on version 1.20 of the plugin

Agreements

[X] I have searched for and ensured there isn't already an open issue regarding this.
[ ] I ticked all the boxes without actually reading them
[X] My version of Minecraft is supported by CrazyCrew.

You need to run a spark profile for at least 5-10 minutes and send the link.

Here is the link for the Spark Profile
https://spark.lucko.me/g6udnG4vq5
I ran it for about 10 mins.
For about 5 mins, I used the command /cc
I waited and did nothing for about 3 mins.
Then for the last 2 mins, I used the command /cc
I hope this helps. Please let me know if you have any other questions or concerns.

You only have 1 gb of ram. That doesn't actually help you much either ( with more hardware, the key checks wouldn't effect you as much. )... As for why it's showing up so much is because of the way keys are checked.
This has changed on Jenkin builds not published to Spigot no longer compare itemstacks, lores and names causing the high usage but simply checking PersistentDataContainers which is much more lightweight.
https://jenkins.crazycrew.us/view/crazycrew/job/CrazyCrates/ -> These are considered stable until they aren't builds and you should tread with caution.
https://github.com/Crazy-Crew/CrazyCrates/blob/main/CHANGELOG.md

also percentages are rather misleading, A little tidbit with spark is to change it to see how many milliseconds is being used.

An in depth breakdown slowly shows which part is the heaviest and also shows that 100ms while not perfect is also not that bad, It's 0.1 of a second.
It used to be higher but I reduced unnecessary getItemMeta checks if it didn't have item meta in the versions you use.
Spark is a tool and is a tool that is useful when you know how to use it well. https://spark.lucko.me/docs

Thank you!
The 2.0-218 build from Jenkins works perfectly fine and the issue no longer occurs.
This is great because, in 1.21 and 1.22, the command was freezing the server for 10 seconds each time it was ran.
Thanks again for your help!


Add dynamic inspect and query commands

These new commands use the protoreflect third-party library.
The inspect subcommand lets you explore available services and their
associated message types on a remote chain.
The query subcommand lets you send arbitrary messages to specific gRPC
services on a remote chain. It accepts JSON-formatted messages at the
command line; then converts them to protobuf internally, sends them to
the server, receives a protobuf response and formats it as JSON on
stdout.

Panic when lens dyn i cosmoshub
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x28 pc=0x103087578]

goroutine 1 [running]:
github.com/jhump/protoreflect/desc.(*ServiceDescriptor).GetFullyQualifiedName(...)
	/Users/johnzampolin/go/pkg/mod/github.com/jhump/protoreflect@v1.12.0/desc/descriptor.go:1353
github.com/strangelove-ventures/lens/cmd.dynamicInspect(0x14000eb8a00, 0x14000141f80, {0x14000ed31e0, 0x1b}, {0x0, 0x0}, {0x0, 0x0})
	/Users/johnzampolin/go/src/github.com/strangelove-ventures/lens/cmd/dynamic.go:252 +0x1738
github.com/strangelove-ventures/lens/cmd.dynInspectCmd.func1(0x14000eb8a00, {0x14000eb4290, 0x1, 0x1})
	/Users/johnzampolin/go/src/github.com/strangelove-ventures/lens/cmd/dynamic.go:216 +0x1d0
github.com/spf13/cobra.(*Command).execute(0x14000eb8a00, {0x14000eb4270, 0x1, 0x1})
	/Users/johnzampolin/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:856 +0x668
github.com/spf13/cobra.(*Command).ExecuteC(0x14000e29680)
	/Users/johnzampolin/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:974 +0x410
github.com/spf13/cobra.(*Command).Execute(...)
	/Users/johnzampolin/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:902
github.com/strangelove-ventures/lens/cmd.Execute()
	/Users/johnzampolin/go/src/github.com/strangelove-ventures/lens/cmd/root.go:130 +0x78
main.main()
	/Users/johnzampolin/go/src/github.com/strangelove-ventures/lens/main.go:23 +0x20

Thanks @jackzampolin, I just pushed commit b0f52bf0e3adbfa5ab8d31fd3b3102822e834711 which should fix the cosmoshub error. Can you share the gRPC address you're using for osmosis?

I am fairly convinced this is a bug in one of the libraries we're using.
You get the same error  if you request a single proposal: lens dyn q osmosis.strange.love:9090 cosmos.gov.v1beta1.Query Proposals '{"pagination": {"limit":1}}'.
The binary content of that response, base64-encoded, is
CtADCAESwAIKIC9jb3Ntb3MuZ292LnYxYmV0YTEuVGV4dFByb3Bvc2FsEpsCCiNXZSB3YW50IHRvIGNsYWltIHJld2FyZHMgY29tcGxldGVseRLzAVJld2FyZC1jbGFpbWluZyB0ZXh0IHByb3Bvc2FsCgpQbGVhc2UgZGVwb3NpdCBhbmQgdm90ZSBmb3IgdGhpcyBwcm9wb3NhbCBpZiB5b3Ugd2FudCB0byBjb21wbGV0ZSAxMDAlIG9mIHlvdXIgZHJvcCBjaGFsbGVuZ2UgQVNBUC4KClRoYW5rcyBPc21vc2lzIHRlYW0gZm9yIEtZQy1mcmVlIGFuZCBuby1idWxsc2hpdCBkcm9wLgpMZXRzIGJ1aWxkIHRoZSBzdHJvbmcgY29tbXVuaXR5IGFuZCBiZXR0ZXIgd2ViIHRvZ2V0aGVyIRgDIjoKDTQ0ODE5NjA0MzQ2NjYSDTEzNzE3MTc1ODE5MjQaDDYxNjAzNTcwOTk0MiIMMTEwMDYwNjYwNDI3KgwIuIe5hgYQtoCb6AEyDAi48YKHBhC2gJvoAToTCgV1b3NtbxIKMjUxMDAwMDAwMEIMCMrguYYGEJT7/aADSgwIysnJhgYQlPv9oAMSCgoIAAAAAAAAAAI=.
You can paste that into online protobuf decoders, e.g. https://protobuf-decoder.netlify.app/, and it decodes correctly.
You can modify the lens code to text-marshal it instead of JSON-marshalling, and it works successfully:
proposals:<proposal_id:1 content:<type_url:"/cosmos.gov.v1beta1.TextProposal" value:"\n#We want to claim rewards completely\022\363\001Reward-claiming text proposal\n\nPlease deposit and vote for this proposal if you want to complete 100% of your drop challenge ASAP.\n\nThanks Osmosis team for KYC-free and no-bullshit drop.\nLets build the strong community and better web together!" > status:PROPOSAL_STATUS_PASSED final_tally_result:<yes:"4481960434666" abstain:"1371717581924" no:"616035709942" no_with_veto:"110060660427"> submit_time:<seconds:1624130488 nanos:486981686 > deposit_end_time:<seconds:1625340088 nanos:486981686 > total_deposit:<denom:"uosmo" amount:"2510000000"> voting_start_time:<seconds:1624141898 nanos:874478996 > voting_end_time:<seconds:1624401098 nanos:874478996 >> pagination:<next_key:"\000\000\000\000\000\000\000\002">

It is only when we attempt to JSON-marshal it, that we hit this panic. I'll continue reducing the test case tomorrow, and may end up filing an issue upstream.

This may be an issue with chain side implementation too.

I filed https://github.com/jhump/protoreflect/issues/507 and made a standalone reproducer at https://github.com/mark-rushakoff/protoreflect-json-marshal-any-repro. I have a couple more leads I can try on working around this in the meantime.

We should prob merge this in anticipation of other work here. been sharing this with a number of folks


Can't install on Magento 2.4.2

I get a few problems:
company@rb-VirtualBox:/var/www/company/m2$ memcomposer require zepgram/module-disable-search-engine
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
Info from https://repo.packagist.org: #StandWithUkraine
Using version ^0.2.0 for zepgram/module-disable-search-engine
./composer.json has been updated
Loading composer repositories with package information
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Can only install one of: magento/module-catalog-search[102.0.4, 102.0.2].
    - Can only install one of: magento/module-catalog-search[102.0.4, 102.0.2].
    - Can only install one of: magento/module-catalog-search[102.0.4, 102.0.2].
    - zepgram/module-disable-search-engine 0.2.0 requires magento/module-catalog-search ^102.0.4 -> satisfiable by magento/module-catalog-search[102.0.4].
    - Installation request for zepgram/module-disable-search-engine ^0.2.0 -> satisfiable by zepgram/module-disable-search-engine[0.2.0].
    - Installation request for magento/module-catalog-search (locked at 102.0.2) -> satisfiable by magento/module-catalog-search[102.0.2].

Installation failed, reverting ./composer.json to its original content.

I also tried it with composer v2
company@rb-VirtualBox:/var/www/company/fresh_m242$ composer2 require zepgram/module-disable-search-engine
Using version ^0.2.0 for zepgram/module-disable-search-engine
./composer.json has been updated
Running composer update zepgram/module-disable-search-engine
Loading composer repositories with package information
In Laminas\DependencyPlugin\DependencyRewriterV2::onPrePoolCreate
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires zepgram/module-disable-search-engine ^0.2.0 -> satisfiable by zepgram/module-disable-search-engine[0.2.0].
    - zepgram/module-disable-search-engine 0.2.0 requires magento/framework ^103.0.4 -> found magento/framework[103.0.4] but the package is fixed to 103.0.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require zepgram/module-disable-search-engine:*" to figure out if any version is installable, or "composer require zepgram/module-disable-search-engine:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I tried it with composer require zepgram/module-disable-search-engine:* and it worked. It was not working because the latest version is not compatible with Magento 2.4.2, It worked with 0.0.3.

The latest version is for Magento 2.4.4 as mentioned in readme.MD

Yes I understand now that there is no backwards compatibility


Roll engine 21ae92651a38..9f1310a74e54 (3 commits)

git@github.com:flutter/engine.git/compare/21ae92651a38...9f1310a74e54
git log 21ae92651a38..9f1310a74e54 --no-merges --oneline
2019-08-19<EMAIL_ADDRESS>Roll src/third_party/skia f8221786d088..8566dda51b42 (4 commits) (flutter/engine#11220)
2019-08-19<EMAIL_ADDRESS>Update metal layer drawable size on relayout. (flutter/engine#11224)
2019-08-19<EMAIL_ADDRESS>Make firebase testlab always pass (flutter/engine#11226)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (stuartmorgan@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5408869713444864

Commit queue failed; closing this roll.


Roll Engine from 30f3d75822d6 to d24339f20462 (1 revision)

https://github.com/flutter/engine/compare/30f3d75822d6...d24339f20462
2022-04-09<EMAIL_ADDRESS>Unify unhandled error reporting, add PlatformDispatcher.onError (flutter/engine#32078)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Feature request: open and manage Chrome extensions

I have several Chrome extensions and the only way to open or manage is to select "Open Extensions" in Chrome Palette and then select the specific extension I want. Instead it would be great if I could directly type the name of the extension into Chrome Palette to open or manage it. Thanks in advance for considering this suggestion! 😊

It looks like it should be possible https://developer.chrome.com/docs/extensions/reference/api/management
I'll look into it

V2.1.0 is being reviewed by google and has this feature

That's amazing — thank you for being the most responsive Chrome extension developer I've ever met! 😊
I'm also curious to know if you have any other future improvement plans / roadmap for this extension?

No roadmap, I just add things when I miss them :)

One thing I do miss is a command to resize the window to the left 50% of the screen and then put the current tab in a new window on the right 50% of the screen

One thing I do miss is a command to resize the window to the left 50% of the screen and then put the current tab in a new window on the right 50% of the screen

What operating system do you use? On Macos this could easily be accomplished using something like Alfred / BetterTouchTool / etc.

Yes I use better touch tool for that, but the extension could do it in one step

Alfred definitely supports multi-step actions like this with a single command. I think BetterTouchTool can also do this.

FYI: extensions list is live!
Also split screen in review (should be out tomorrow)

Hi @dbuezas - There seems to be some regression and the extensions list is no longer working for me (but split screen is working).

Are you on v<IP_ADDRESS>?
It does work for me.
Please try this:

Right click on the extension pop-up
Inspect
See if there are any errors in the console
Enter search extensions section
Check for errors again
Paste any error here

You have to get Into "search extensions" first

Or type e> firdt

Oops - this was just user error, my bad!
On Mon, Oct 21, 2024 at 10:59 AM David Buezas @.***>
wrote:

Or type e> first
—
Reply to this email directly, view it on GitHub
https://github.com/dbuezas/chrome-palette/issues/4#issuecomment-2427373075,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7SMVLJRYG5XP5B4UGQFLLZ4U6GTAVCNFSM6AAAAABPHMWCW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXGM3TGMBXGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

I could put everything at the root, but with history, tabs and bookmarks it gets crazy big. Also I opted to keep the root list fixed so you always know you'll get the same action with the same input


[Community Process] Create milestones for Patch Releases

If we need to backport fixes into a patch release, we could create a milestone for that release and add cherrypick PRs to those milestones. This will give the releasers an easily verifiable "green light" to begin their release.
[I think?] A nice side effect is that all our releases would have a nice page to view all the cherrypicked PRs, even the ones that didn't get a changelog entry. Ex: https://github.com/operator-framework/operator-sdk/milestone/28?closed=1

I wonder if its possible to have the bot do this?

We agreed to this on the community meeting today. I'll add this process to our documentation.


added Bouachain Mainet

Fixed, Please conduct a new review.

Fixed ✅✅

Added Https and closed the code base
Fixed ✅✅

Fixed ✅😄


Advance music cog updated.

playlists added
Queue/history embed formatted
Custom checks/error

And format using black please

Thank you!


when users has more than 10,Users pager throw exception

There is a syntax error near 'OFFSET'. The use of option FIRST in the FETCH statement is invalid
var results = await users
.Skip(pager.GetStartIndex())
.Take(pager.PageSize)
.List();

Which database are you using?

SQLSERVER 2008 R2

Maybe the dialect that is generated is only compatible with a more recent version. I need to think about a way to specify the dialect in the connection string then.

Looks like the OFFSET keyword was introduced in SQL Server 2012

@sebastienros you can close this after your merge my PR https://github.com/sebastienros/yessql/pull/64 and update the YesSQL libs


Returning null from class validators causes 500.

Actual behavior (the bug)
If you make a JavalinValidator that returns a null value instead of throwing an exception, the validator assume that the Class was not registered and throws a 500
Expected behavior
I would expect a null value to be treated as invalid input so a 400 would be throw instead saying the parameter could not be converted
To Reproduce
This is obviously contrived, but its the simplest code that shows the problem
JavalinValidation.register(MyClass.class, str -> null);
The in handler
ctx.validatedQueryParam("param").asClass(MyClass.class).getOrThrow();
The above will throw a ConversionException sating that the class was not registered when in fact it was.  I would expect this instead to throw A BadRequestResponse and say its not a valid MyClass object.
Additional context
This is because the validation is currently done in single line
JavalinValidation.converters[clazz]?.invoke(value) ?: throw ConversionException(clazz.simpleName)
So if the class wasn't registered or if the invoke returns null then throw a conversion exception.  Instead I feel like they should be checked separately albeit that makes the code less elegant. This can obviously be worked around by a more complex validator that checks for null and throws an exception, but I feel like the current behavior is confusing because I did register a validation method.

I can take this on if you think its worth changing

Thanks, please make a PR!


Filter ipset entries based on node

From @awh on September 20, 2016 13:18
For the sake of simplicity, the current implementation builds the same rules and ipsets on all nodes. This limits scalability - instead, a pod's IP should only be added to a node's matching ipsets if that pod is scheduled on that node (it may be possible to implement this by putting a filter on the k8s notification API subscription).
Copied from original issue: weaveworks/weave-npc#6

a pod's IP should only be added to a node's matching ipsets if that pod is scheduled on that node

This optimisation is only applicable to destination ipsets, i.e. those appearing in the dst portions of the iptable rules weave-npc maintains.

I believe that statement follows from the fact that we only have ingress rules at present. When we add egress rules it would be the src address.
I think it would be better to filter out non-applying rules at a higher level, where we know which way round they are and hence which end is interesting.

I believe that statement follows from the fact that we only have ingress rules at present.

Yes, but it wasn't obvious to me, hence I figured it would be good to clarify that, especially since even with only ingress rules we also have ipsets that represent sources (i.e. where connections are allowed to come from).

I tried this, and it blocked the outgoing end of the connection.

I missed a large subtlety: the same IPset can be used for both src and dst checks depending on where a selector appears in the rules, and if it is used as a src it needs to include all pods anywhere in the network.


Add IntraDayActivity

Hello,
I added calls to intradaysActivity methods on the source code as specified here : http://oauth.withings.com/api/doc#api-Measure-get_intraday_measure
It is fully functionnal but you have to ask withings an authorization to make these requests. It works fine on my side.

@Spepsi got it, I will try to review sometime this week.

@Spepsi please add unit tests for your new method, similar to what exists already in tests.
It looks like our Travis builds are failing, but not because of your change. Feel free to take a look and fix it, otherwise I'll take a look this weekend.

Allright I will add unit tests probably beginning of next week.
Le 28/07/2016 à 16:14, Jacob Sachs a écrit :
@Spepsihttps://github.com/Spepsi please add unit tests for your new method, similar to what exists already in tests.
It looks like our Travis builds are failing, but not because of your change. Feel free to take a look and fix it, otherwise I'll take a look this weekend.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/amida-tech/withings-lib/pull/13#issuecomment-235926232, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJAzy-Pum_cEu4OxKaUT8GxjW4Dlyekuks5qaMdogaJpZM4JU-Jg.


[Bug]: Admin claims are cleared on server restart

Bug Description
The mod clears all admin claims on server restart.
How to Reproduce?

make a couple of admin claims
restart server
join back in and try to find existing admin claims

Expected Behavior
The admin claims should continue existing after a server restart.
Version
1.0.2
Mod Loader Version
1.20.1 - 47.1.0
Mod Loader
No response
Logs or additional context
No response
Code of Conduct

[X] I have searched the issue tracker and confirmed that the issue has not been reported
[X] I have checked the FAQ (if one is present) and my issue is not listed
[X] I have verified that I am using the latest version of the mod
[X] I have verified that I have installed all the required dependencies for the mod
[X] I have verified that I do not have Optifine installed. We will close issues if we detect Optifine is in your pack. We cannot fix Optifine issues. Please do not report issues with Optifine present.

I'm unable to reproduce this. I'm testing on forge 47.1.3 by making a fresh server instance with just Cadmus, creating a few admin claims, restarting the server, and finding that they're all still there.
Can you try on a new server instance with just Cadmus? It may be old/corrupted files or another mod causing it.

Sorry for cluttering the issues tab. I tried it with a new instance, and now it is working. Thank you for your help.

👍


Adding Perl client to list of User Libs

Adding a link to Net::Kubernetes perl module to list of user contributed client libraries.
Related issue: https://github.com/GoogleCloudPlatform/kubernetes/issues/10114

Thanks for the PR (and thanks for writing the client)


Create plugin manifest atomically after library is built

As well as path issues, pretty sure the configure file is not correctly updating the version anymore

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

Project coverage is 55.17%. Comparing base (b88b965) to head (137d27a).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #18   +/-   ##
========================================
  Coverage    55.17%   55.17%
========================================
  Files           79       79
  Lines         4176     4176
  Branches       461      461
========================================
  Hits          2304     2304
  Misses        1872     1872

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


fix: add JS for icon property in buttons

Description
Add JS functionality for icon in buttons, button group, menu button
Fixes #11142
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Tested Manually
Checklist:

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

/perf-test ref=rhito/feat-create-run-meta-before-test-starts-compare-lt-st-for-prev-runs

/perf-test ref=rhito/feat-create-run-meta-before-test-starts-compare-lt-st-for-prev-runs

Hey when will this PR be accepted

Hey @Tooluloope Can you approve the changes

@somangshu Can you review this too?

@sanjus-robotic-studio while I am looking into the above query, can you merge with latest release branch

/ok-to-test sha=a4daf2a

@sanjus-robotic-studio thanks for the changes, the tests are running right now; Ill merge this by tomorrow. 🙏

Sure, Thanks


The file given is not an instance of Blob or File with v2.0.0 on Next.js

As of v2.0.0, your Next.js example appears to only work when you start Next.js in development mode, not production. Could this be related to core-js being dropped?
The docs say this polyfill is for IE only, but this issue affects Next.js on the latest version of Chrome, Firefox, and Safari.
yarn dev

yarn start

Here's a temporary fix for anyone looking for it:
yarn add<EMAIL_ADDRESS>--exact

@maxproske I couldn't reproduce this issue. Can you provide more details? Such as the image file, OS platform, and browser version.
You may also try to run again yarn build followed by yarn start. It works for me on Windows 10 Chrome 100.0.4896.88 with both PNG and JPG file.

@maxproske I am having the same issue.
Please find the following detail
OS: MacOS 12.3.1
Chrome: 102.0.5005.115
The image

@tom555my Here is the result of your image using the production mode of the example Nextjs app (https://github.com/Donaldcwl/browser-image-compression/tree/master/example/Nextjs App)

I tested on both Win and MacOS Chrome.
Could you provide more information about the issues you faced?

I faced with the exact same issue. This might be related to the swcMinify option, which is available in newer Next.js versions (details). With swcMinify, the production build breaks and browser-image-compression refuses to output compressed images. If I set swcMinify to false, this error disappears.
I also confirmed that the example is not broken with/without newer Next.js versions, as swcMinify seems to be not enabled by default.

@3c1u
I just tested<EMAIL_ADDRESS>on<EMAIL_ADDRESS><EMAIL_ADDRESS>with swcMinify enable (true). I can't reproduce the issue. Could you share your source code that has the issue?
The nextjs source code I tested can be found here: https://github.com/Donaldcwl/browser-image-compression/tree/master/example/Nextjs App


WeMod Beta version 7.0.1-beta01

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

image is of different manifest, but it is failing the same way,

image is of different manifest, but it is failing the same way,

see above, sorry

see above, sorry

cc @KevinLaMS: It's installing fine over here:

cc @KevinLaMS: It's installing fine over here:


Reporting not working under 3.8.1

Describe the bug
Map details or reports work at all in 3.8.1.
What version are you running?
3.8.1
Did this happen on prior versions to the one you are running?
Yes <IP_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

Go to reports select a service body
Click on any of the buttons to export and nothing happens

Expected behavior
reports should load on selection and be exportable.
Screenshots

Additional context
Add any other context about the problem here.

are you using HTTPS?

Hi Danny,
Sorry for the late response.  It seems that its all working again now.
Very confusing.  I haven't done anything different.  Maybe it was cache....


building_jedi.rst: add python3 executable override

Update the "Building JEDI" docs to reference the use of the DPython3_EXECUTABLE flag for ecbuild. This flag is used to specify the python3 binary in order to ensure that python3 linked build targets are linked with the spack-stack supplied python3 interpreter.

@eap Thanks for updating the doc. You need to issue your PR in jcsda-internal/jedi-docs. jcsda/jedi-docs gets updated automatically after every update in the develop branch of jcsda-internal/jedi-docs.

Moving this to https://github.com/JCSDA-internal/jedi-docs/pull/562.
I'll close this and delete the branch.


Ensembl Perl API is not installed

The Ensembl Perl APIs are apparently not installed.
This affects all the Ensembl-depending tools :

supported-organisms-ensembl
perl-scripts/download-ensembl-features
perl-scripts/download-ensembl-genome
perl-scripts/download-ensembl-go-annotations-biomart
perl-scripts/download-ensembl-variations
perl-scripts/ensembl-org-info
perl-scripts/get-all-ensembl-seqs
perl-scripts/get-ensembl-genome-no-objects.pl
perl-scripts/get-ensembl-genome-only-objects.pl
perl-scripts/get-ensembl-genome.pl
perl-scripts/get-ensembl-one_chrom.pl
perl-scripts/retrieve-ensembl-seq
perl-scripts/retrieve-ensembl-seq-norsat.pl
perl-scripts/supported-organisms-ensembl
perl-scripts/supported-organisms-ensemblgenomes

Calling any of these scripts returns error like this :
[root@clust-rsat:/opt/rsat-tools/rsat]$ retrieve-ensembl-seq -help
Can't locate Bio/EnsEMBL/Registry.pm in @INC (you may need to install the Bio::EnsEMBL::Registry module) (@INC contains: /opt/rsat-tools/rsat/ext_lib/biomart-perl/lib/ /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensemblgenomes-api/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl-variation/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl-tools/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl-functgenomics/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl-external/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl-compara/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl/modules /opt/rsat-tools/rsat/ext_lib/bioperl-release-/bioperl-live /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base /opt/rsat-tools/rsat/perl-scripts/lib/  /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl/modules /opt/rsat-tools/rsat/ext_lib/ensemblgenomes-52-105/ensembl-compara/modules) at /opt/rsat-tools/rsat/perl-scripts/retrieve-ensembl-seq line 28.

I currently use a makefile to install Ensembl Perl API.
 make -f makefiles/install_software2.mk install_ensembl_api

@FanchTheSystem , the installation via this makefile is a bit heavy, and not very clean.
Would it be possible to convert this to an Ansible recipe, so that these Ensembl Perl API would be installed automatically ?
Thanks

Ah, en fait il y avait déjà des librairies Ensembl installées, mais comme entretemps j'avais mis à jour les version s d'ENSEMBL_RELEASE et ENSEMBLGENOMES_RELEASE elles n'étaient pas dans le bon dossier.

Cependant il manquait une autre librairie : bioperl
make -f makefiles/install_software2.mk install_ensembl_bioperl

la version de ensemblgenoms api n'est pas correct (la 52 n'existe pas) https://github.com/rsa-tools/rsat-code/pull/11


python312Packages.frozendict: 2.4.0 -> 2.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.frozendict is: Module for immutable dictionary
meta.homepage for python312Packages.frozendict is: https://github.com/Marco-Sulla/python-frozendict
meta.changelog for python312Packages.frozendict is: https://github.com/Marco-Sulla/python-frozendict/releases/tag/v2.4.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.1 in filename of file in /nix/store/qzj8lrknxivq1m0l4p0xw1rj5cca65x5-python3.12-frozendict-2.4.1

Rebuild report (if merged into master) (click to expand)

14 total rebuild path(s)

14 package rebuild(s)

First fifty rebuilds by attrpath
markdown-anki-decks
octoprint
opshin
python311Packages.bsuite
python311Packages.frozendict
python311Packages.genanki
python311Packages.pluthon
python311Packages.pycardano
python311Packages.uplc
python311Packages.yfinance
python312Packages.bsuite
python312Packages.frozendict
python312Packages.genanki
python312Packages.yfinance

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qzj8lrknxivq1m0l4p0xw1rj5cca65x5-python3.12-frozendict-2.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.frozendict https://github.com/r-ryantm/nixpkgs/archive/6d89459fb0840c7f0782afb42deaf45b41d348a2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6d89459fb0840c7f0782afb42deaf45b41d348a2#python312Packages.frozendict

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qzj8lrknxivq1m0l4p0xw1rj5cca65x5-python3.12-frozendict-2.4.1
ls -la /nix/store/qzj8lrknxivq1m0l4p0xw1rj5cca65x5-python3.12-frozendict-2.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages failed to build:

python312Packages.bsuite
python312Packages.bsuite.dist

26 packages built:

markdown-anki-decks
markdown-anki-decks.dist
octoprint
octoprint.dist
opshin
opshin.dist
python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.frozendict
python311Packages.frozendict.dist
python311Packages.genanki
python311Packages.genanki.dist
python311Packages.pluthon
python311Packages.pluthon.dist
python311Packages.pycardano
python311Packages.pycardano.dist
python311Packages.uplc
python311Packages.uplc.dist
python311Packages.yfinance
python311Packages.yfinance.dist
python312Packages.frozendict
python312Packages.frozendict.dist
python312Packages.genanki
python312Packages.genanki.dist
python312Packages.yfinance
python312Packages.yfinance.dist

Maintainer pings
cc @pbsds for testing.

Result of nixpkgs-review pr 300708 run on aarch64-darwin 1

4 packages marked as broken and skipped:

python311Packages.bsuite
python311Packages.bsuite.dist
python312Packages.bsuite
python312Packages.bsuite.dist

24 packages built:

markdown-anki-decks
markdown-anki-decks.dist
octoprint
octoprint.dist
opshin
opshin.dist
python311Packages.frozendict
python311Packages.frozendict.dist
python311Packages.genanki
python311Packages.genanki.dist
python311Packages.pluthon
python311Packages.pluthon.dist
python311Packages.pycardano
python311Packages.pycardano.dist
python311Packages.uplc
python311Packages.uplc.dist
python311Packages.yfinance
python311Packages.yfinance.dist
python312Packages.frozendict
python312Packages.frozendict.dist
python312Packages.genanki
python312Packages.genanki.dist
python312Packages.yfinance
python312Packages.yfinance.dist


Add a wasmtime-specific wasmtime_wat2wasm C API

This commit implements a wasmtime-specific C API for converting the text
format to the binary format. An upstream spec issue exists for adding
this to the C API, but in the meantime we can experiment with our own
version of this API and use it in the C# extension, for example!
Closes #1000

Question: Would it be possible to support line number and column info for parse failure - ie. separate from error message? Or maybe just prepare API for now - and then add info later if it becomes possible to support. Just to avoid having to change API later.

I believe the wat crate already provides line and column, along with contextual information of where the parse error was.

Looking at https://webassembly.github.io/spec/core/text/lexical.html - it seems that null-terminator is allowed in comments. Current API is would not allow this.

Oh sorry, I misread that.  As separate pieces of information, not how we're doing it currently, no.
@alexcrichton is there an error type we can extract the line and column from?

Yes the wat/wast crates have enough information to return line numbers of errors. The C API in general doesn't do super well with errors and adding rich information like filename/line number (as opposed to just a string) would likely require us to invent new idioms/machinery/etc. I don't think there's any reason why we can't do that, but I would imagine that if we were to focus on errors in the C API we should take a look at them as a whole instead of only situation-solving one API.

Maybe add some note in API documentation about if UTF-8 BOM is allowed or not. Not sure if Rust runtime will strip it. If it is supposed to work then it would be good to have a wat test file with a BOM.

Oh I forgot to mention earlier, but your comment about the nul byte was previously correct when it was using char* but now that it's using wasm_byte_vec_t* that should be handled because it's a pointer/length.
For BOM handling Rust doesn't do anything special there, it would be up to the lexer, if anything, to skip it. Currently the wat parser doesn't skip it and will fail on any file that contains the BOM marker. Looking at the lexical structure of the text format I don't think the BOM is allowed, so it sounds like this may be a spec question/update/tweak to bring up with the official repo.

Thanks @alexcrichton. But one note - BOM, if handled, should only be done at the decoding/encoding layer and not passed on to the internal Unicode representation. So not direct impact here for lexer.

Ok I'm gonna go ahead and land this and we can continue to iterate on specifics in-tree.


can i add with bootstrap 4?

Maybe you can create a branch to design for bootstrap4?

@Linnzh , make a new branch?

@amin007 , I just make a suggestion. You can add a Bootstrap4 branch and add the corresponding class name to each tag in the branch code, or add a template to the generated HTML, etc. Of course, you can also fork the repository and customize it yourself (I tried Add the class name to the tag, but unfortunately this PR was not passed).
Of course, this is based on the fact that the class name is known and fixed. If you want to add freely, I think it will be very troublesome and lose the simplicity of this library.

@Linnzh , i have try add style in this library.
but if i add style, this library lose the simplicity

@amin007 , Yes. So what I did later, after generating the HTML snippet, use a  tag to wrap it, and then customize the style on this  tag. This will be simpler and can be changed at will.


(Calendar) When opening the dialog, date does not match the day of the week

When opening the dialog, the date does not match the day of the week. However, if we move to another month and back, everything  is becoming right (attaching screenshots when opening the dialog and after we selected another month and returned back)

I Just had the same problem with v1.3.0 of the calendar module.
I think that its a bug for that version.
For me it worked the following:

Keeping the sheets-compose-dialogs:core at 1.3.0
Downgrading the sheets-compose-dialogs:calendar module from 1.3.0 -> 1.2.1

Hope it helps!

Keeping the sheets-compose-dialogs:core at 1.3.0
Downgrading the sheets-compose-dialogs:calendar module from 1.3.0 -> 1.2.1

Hope it helps!

Yes, it is! Thanks a lot :)


Converts AddressFamily to struct with associated consts

Split off from #2199
Script I used to generate the variants: https://gist.github.com/Jan561/067d64641c93017a9bf6b346ac078ec1
Checklist:

[x] I have read CONTRIBUTING.md
[x] I have written necessary tests and rustdoc comments
[ ] A change log has been added if this PR modifies nix's API

I'll provide a changelog when rebasing on top of #2211


Remove extra brackets

Codecov Report

Merging #40 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #40   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         132    132
  Branches       28     28
=====================================
  Hits          132    132

I recognize that these parentheses are strictly unnecessary, but I find the code more intuitively readable with them.

Ok
On Mon, Sep 10, 2018, 18:03 Rob Speer<EMAIL_ADDRESS>wrote:

I recognize that these parentheses are strictly unnecessary, but I find
the code more intuitively readable with them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LuminosoInsight/ordered-set/pull/40#issuecomment-419946110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADSjI-9Gpo6G_YIvjWSa4_tmdWjIlSUBks5uZn9fgaJpZM4WgN7t
.


Flaky test in "pageObjectModel.test.js"

pageObjectModel.test.js has a flaky test. Fails sporadically with error:
  ● Example › should access an element defined directly in page

    expect(received).resolves.toBeTruthy()

    Received: false

      21 |         await HomePage.FeedBackLink.click();
      22 |         console.log("Clicked on feedback link");
    > 23 |         await expect(FeedbackPage.TitleText.exists()).resolves.toBeTruthy();
         |                                                                ^
      24 |     });
      25 | });
      26 | }

      at Object.toBeTruthy (node_modules/expect/build/index.js:198:20)
      at Object.<anonymous> (example/tests/pageObjectModel.test.js:23:64)

Unable to reproduce currently, both with headless=false and headless=true. Additional waiters does not seem to be needed, because one is already included into exists() method. shortTimeout could be increased in the configuration.


Model.sav Not found

I am trying to run the program, but am getting this error:
model = pickle.load(open(filename, 'rb'))
FileNotFoundError: [Errno 2] No such file or directory: 'model/model.sav'
I have checked the model folder and model.sav seems to be there, so I am unaware of what might be causing this error

I just needed to add the full relative path in the folder


Allow using different service accounts on GCE

It should be as easy as changing this line:
cloud.WithTokenSource(google.ComputeTokenSource(""))

to not use an "".

I'm a little confused by the various access methods but it looks to me like access scopes are now deprecated[1] and instead Pachyderm should encourage users to create a GCE service account and accept a configuration[2] of the credentials.json for that service account that is uses on any pods that need write access to Google Cloud Storage.
1: https://cloud.google.com/compute/docs/access/service-accounts#accesscopesiam
2: https://godoc.org/cloud.google.com/go#example-package--ServiceAccountFile

Also, the official Google recommendation (see Securing containers with Kubernetes Engine 1.8) is to reduce the default permissions given to individual nodes:

The principle of least privilege helps to reduce the "blast radius" of a potential compromise, by granting each component only the minimum permissions required to perform its function. Should one component become compromised, least privilege makes it much more difficult to chain attacks together and escalate permissions.
Each Kubernetes Engine node has a Service Account associated with it. You’ll see the Service Account user listed in the IAM section of the Cloud Console as “Compute Engine default service account.” This account has broad access by default, making it useful to wide variety of applications, but has more permissions than you need to run your Kubernetes Engine cluster.
We recommend you create and use a minimally privileged service account to run your Kubernetes Engine Cluster instead of the Compute Engine default service account.

(Emphasis mine.)

As far as I can see, at least with the current (0.17) version of the Google SDK, you should instantiate client.NewClient without options. The current call is:
	client, err := storage.NewClient(
		ctx,
		cloud.WithTokenSource(google.ComputeTokenSource("")),
		cloud.WithScopes(storage.ScopeFullControl),
	)

But reading the code, it looks like the absence of a token source will cause the client to call google.FindDefaultCredentials, which goes through the standard Google SDK ways of finding credentials:
//   1. A JSON file whose path is specified by the
//      GOOGLE_APPLICATION_CREDENTIALS environment variable.
//   2. A JSON file in a location known to the gcloud command-line tool.
//      On Windows, this is %APPDATA%/gcloud/application_default_credentials.json.
//      On other systems, $HOME/.config/gcloud/application_default_credentials.json.
//   3. On Google App Engine it uses the appengine.AccessToken function.
//   4. On Google Compute Engine and Google App Engine Managed VMs, it fetches
//      credentials from the metadata server.
//      (In this final case any provided scopes are ignored.)

As for WithScopes, the default scope is actually ScopeFullControl, so it can be dropped.
In other words, Pachyderm can just use google.DefaultClient(ctx) instead of what it does now. On GCE, this would use the metadata API to get the node's credentials (today's behaviour), but also allow Pachyderm to be deployed with other credentials (either OAuth 2.0 token or a service account, as described here).


feat(zk): implement create proof part1

This PR contains implementations of Synthesizer and Argument.
The Synthesizer covers the code generating advice columns in the CreateProof().
See AdviceSingle, Assigning AdviceSingles.
The Argument provides all the data required to generate a proof. In detail, it has fixed/advice/instance columns in evaluation form and coefficient form. Argument makes it easier to analyze data and to understand the data flow during the proof generation process.
See InstanceSingle, Assigning InstanceSingle.
And this PR includes minor fix bugs.

@dongchangYoo Can you fix 20985f0 as a refac commit?

@dongchangYoo Can you fix typo in message of 2250507? conststant -> constant

@dongchangYoo Can you fix 20985f0 as a refac commit?

This commit will be removed.


Error coming on formatting scss file with scss-formatter

sass-convert' is not recognized as an internal or external command,
operable program or batch file.

I am not sure if this error is from this extension. There is no such command as sass-convert. Can you re-verify it once?

Closing this issue for now. Feel free to reopen with more info if you still think this problem is with this extension. Thank you


 Error: No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! ["0.0.1","0.1.0","0.2.0","0.3.0","0.3.1","0.4.0","0.4.2","0.5.0","0.6.0","0.7.0","0.8.0","0.9.0","0.10.0","0.11.0","0.12.0","1.0.0","1.0.1","1.0.3"]
npm ERR!     at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:682:10)
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:597:10
npm ERR!     at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR!     at Object.oncomplete (fs.js:93:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR! System Linux 3.19.3-200.fc21.x86_64
npm ERR! command "node" "/usr/local/bin/npm" "install" "tern"
npm ERR! cwd /home/bryan
npm ERR! node -v v0.9.12-pre
npm ERR! npm -v 1.2.14
npm http 304 https://registry.npmjs.org/glob
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/bryan/npm-debug.log
npm ERR! not ok code 0

Could it be that your npm is old(ish)? I believe support for ^ notation in dependency versions was added not so very long ago. Try upgrading npm, it might solve this.

You're right, sorry. I was assuming npm was being updated by the package manager but it turns out that it was separately installed and not updating. Fixed now.
Thanks


Refactor Clipboard Operations to Utilize new copyToClipboard Utility

Is your feature request related to a problem? Please describe.

Enhance consistency in UI/UX.
Improve the behavior of the clipboard icon to reflect proper state changes.
Ensure Success/Error Notifications are handled efficiently and provide clear feedback.

Describe the solution you'd like

Required in places like AssetWarrantyCard , ShiftDetails etc

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

I would like to work on this update if applicable @rithviknishad @Jacobjeevan @nihal467

not a requirement based on the current develop


Logo looks very small in navbar

logo looks very small in navbar it doesnt look nice

plz add level,hacktoberfest and gssoc 2024 extnd

@keerthana2-005 assigned, before going it to, provide an demonstration!

Hello is please assign me this issue


Fix Demo Project

This PR relate to #10
Sica.framework should be an embeded framework to run SicaDemo.app with iOS Devices.

 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.

Thanks!!


Improve article 2306.11825

Exact location of issue
The whole paper.
Problem details
The cached paper is not updated when the original arxiv had a major update in its contents

As a rule, ar5iv only supports a single version of an article, and it is usually the first version released by arXiv in the official bulk download channels.
From time to time I run a bulk update for the collection - the last one was in February 2024. So this paper may update again to its latest version before a full rerun, but there is no telling when exactly that will be.
That said, I think you can find the v2 HTML at the official arXiv URL already, right?
https://arxiv.org/html/2306.11825v2


:robot: triggering CI on branch 'release-next' after synching from upstream/main

Codecov Report

Merging #623 (dba4353) into release-next (dba4353) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head dba4353 differs from pull request most recent head d03702c. Consider uploading reports for the commit d03702c to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@              Coverage Diff              @@
##           release-next     #623   +/-   ##
=============================================
  Coverage         49.40%   49.40%
=============================================
  Files                96       96
  Lines             13113    13113
=============================================
  Hits               6479     6479
  Misses             5991     5991
  Partials            643      643

OCF Webhook is merging this PR


Update helm v3 version in klipper-helm image

There is a vulnerability in helm versions before 3.6.1. I'm not sure if we're strictly affected since helm-controller does not support authenticating to chart repos, but we should update the helm v3 version in klipper-helm and pull this through into our next round of releases.

https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf
k3s-io/klipper-helm#30

Validated on master by checking pkg/helm/controller.go.


Thoughts on property defaults.

Consider a component caled Box with the following property:
export default {
props: {
    type: {
        type: String,
        default: "text"
    }
}
}

The intension of the component designer here is that anything we don't have a meaningful input for "type", it should be "text".
In Vue it seems that defaults are assigned only if the property is omitted. Consider the following example of using the box component.
<template>
Box type:
   <box :type="box_type" />

Box text type:
  <box />
</template>

In the first case if "box_type" is defined, this works well and good. If "box_type" is undefined for whatever reason, this causes the Box component's type property to be unset and a warning to be issued in the console.
The second usage of  works as expected and the property defaults to "text".
Should undefined property values cause defaults to be assigned? I think it would make for a nicer development practice.

I've run into this as well.  I feel like the default should be used if a prop is not defined.

what if you want to explicitly set the value to undefined?

@posva That is indeed a good point, however I'm failing to see how an API designer would make sure of this. Would you give me an example of how that would work.

RANT I feel like the undefined type shouldn't have existed in the first place. It's one of those JS language constructs that is probably too late to get rid of now. Every time I've come head to head with undefined types in Javascript it's always under bad circumstances :-)

You may have a component that is showing up yet is waiting for some async resource to be available.
Although null could be used too but this may be tricky for some users

+1 for bringing this up to the table.

The semantics of default is for providing a value when the prop is absent (i.e. the consumer of the component did not even provide a value). This is different from providing a value, but with a value of undefined. As @posva mentioned, this could lead to unexpected results for some users, and is also a breaking change, which in general we should try to avoid if there's no strong benefits in doing so.
I think the use case can be covered by the suggested coerce option though: https://github.com/vuejs/vue/pull/1955

Hi !
I think this is debatable.
In JavaScript, the sole purpose of undefined is precisely this case: explicitely saying that no value has been affected.
This is the sole definition of undefined value in the ECMA specifications: http://www.ecma-international.org/ecma-262/6.0/#sec-undefined-value
It should be interpreted as a value but as the absence of value.
This is also why JSON.stringify will dump null keys but notundefined ones.
So, in my opinion, when undefined is set as property anywhere, it should be interpreted as "no value is assigned" and in the case of Vue properties, it should trigger default.

This is debatable exactly because some users feel the other way. And the point is that this will be a breaking change, so I prefer to leave it in current state unless everyone agrees it should be changed.

Agreed. Perhaps in the next MAJOR (semantic version), this could be reconsidered by opening it to the community (as you already suggest).
This is not that hard to workaround, and the coerce option makes it even better. Thanks.

is it possible to access default value from coerce callback?
So i could do it manually where needed.
Or event better way would be: is it possible to conditionally pass prop to child component?
<child :msg="parentMsg"></child>

So, if parentMsg is undefined it is not passed at all?

Where are we at with this decision?
In my opinion it is embedded in the nature of javascript for a schema to use the default value of the property if the property is passed as undefined.
Actually it isn't embedded but that's how mongoose schema definition does it and it's logical in my opinion.
How else do you make a
with a default item value resort to the default when you want to add a new item to items, and do so by pushing an undefined value into the items list. So that the component takes care of the default value, because you shouldn't have to put any component logic into the parent, am I right.
What workaround is there for my use case to ensure that :item is only passed if it is not undefined? So I can get the default value working?
thank you kindly vue team

Im still favouring undefined value as no value (use default value), if value is null or false, than use passed one.
Otherwise i have to write:
<template>
   <box v-if="box_type" :type="box_type" />
   <box v-else />
</template>

But i could write:
<template>
   <box :type="box_type || undefined" />
</template>

You could build your Box component to use a computed property based on the prop, and if the passed prop matches your criteria, make it a default:
export default {
    name: "box",
    props: ["box_type"],
    computed: {
        internalBoxType() {
            return this.box_type || "default"
        }
    }
}

Then you only use internalBoxType within your Box component.

A computed property doesn't break the v-binding nature of properties?

@sirlancelot yeah, but that sort of makes props default value obsolete.
This is the way i usually approach similar things. i don't use default prop values at all (there could be cases where that would work, but for sake of consistency across project...)

@lopugit https://vuejs.org/v2/guide/computed.html#Computed-Setter is the way to use computed properties for two way binding (as v-model)


executablePath seems to have no effect

i have sqlfluff installed in a virtualenv. I tried setting sql.linter.executablePath to the virtualenv location (I am pretty certain is correct) but the extension says "The executable was not found". after installing sqlfluff globally, then the extension works (whether I set executablePath or not). this leads me to think that the executablePath configuration field is not correctly taken into consideration

Please try v0.0.6 and let me know if the problem is still occurring.


test: Fix skipping of ipvlan test suite

Previously, AfterEach statements were executed regardless whether the ipvlan suites were skipped (due to running on ubuntu-next) which made the whole suite to fail.
Fix: #7443
Fixes: 314a6d3fd6 ("test: Extend runtime connectivity tests to include ipvlan")

This change is

test-me-please

test-me-please

test-me-please

Coverage decreased (-0.002%) to 42.336% when pulling fd7094b86d9042b7b7d6fefdf1e758c9216e7f04 on pr/brb/fix-ipvlan-ci-skip into f332375063be1ea16ab2d81a55af9b0d62f5bec1 on master.

Build failure:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/10865/
Appears that the issue which this PR is fixing is not hit anymore, but will run again to be sure.

test-me-please

VM download took a long time and timed out:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/10870/execution/node/57/log/
Will re-run tests.

test-me-please


how to get url file, i want show image thumnail file uploaded???

@luanphan1996 Please use an option 'additionalFetchField'.
$options = ['additionalFetchField' => 'thumbnailLink']
$adapter = new \Hypweb\Flysystem\GoogleDrive\GoogleDriveAdapter($service, '['root' or folder ID]', $options);

@nao-pon thanks !

Hot to access the additionalFetchField result?


Reproducing paper results from feature vectors (STS-B dataset)

I would like to reproduce the results of the paper on the STS-B dataset, but instead of fine-tuning BERT, I would like to use the feature vectors (I am aware the accuracy will be slightly worse with this approach).

In the paper, this approach is used to obtain results on the  CoNLL-2003 NER task. This is done by adding :

a randomly initialized two-layer 768-dimensional BiLSTM before the classification layer

What approach should I take for the STS-B dataset ? I have tried the 2-layers BiLSTM, but the results are not good.

My bad, the 2-layers BiLSTM works perfectly.
The issue was :
I was extracting the feature vectors for both sentence and then concatenate it later, before the BiLSTM.
Extracting just one feature vectors for the sentence Sentence1 ||| Sentence2 solved it.


[22.05] diffoscope build is broken (test failure)

Steps To Reproduce

nix-build -A diffoscope fails. (This only happens on release-22.05, it builds fine on master.)

  In this case, just swallow the warning.
                    # See also https://docs.python.org/3/library/sys.html# sys.__stderr__
                    if file is not None:
                        file.write(
                            formatWarning(message, category, filename, lineno, line)
                        )
                except IOError:
                    pass

            warnings.showwarning = _showwarning
        self.strict = strict
        self._flattened_pages = None
        self.resolved_objects = {}
        self.xref_index = 0
        self._page_id2num = None  # map page IndirectRef number to Page Number
        if hasattr(stream, "mode") and "b" not in stream.mode:
            warnings.warn(
                "PdfReader stream/file object is not in binary mode.  You can switch to the metadata attribute already. [pdf.py:94]
PendingDeprecationWarning: PdfFileReader was renamed to PdfReader. PdfFileReader will be removed [pdf.py:93]
=============================== warnings summary ===============================
tests/comparators/test_pdf.py::test_no_differences
tests/comparators/test_pdf.py::test_differences_found_with_weird_encoding
tests/comparators/test_pdf.py::test_text_diff
tests/comparators/test_pdf.py::test_compare_non_existing
tests/comparators/test_pdf.py::test_metadata
tests/comparators/test_pdf.py::test_annotations
  /build/diffoscope-213/diffoscope/comparators/pdf.py:93: PendingDeprecationWarning: PdfFileReader was renamed to PdfReader. PdfFileReader will be removed
    pdf = PyPDF2.PdfFileReader(file.path)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED tests/comparators/test_pdf.py::test_compare_non_existing - AttributeEr...
= 1 failed, 664 passed, 25 skipped, 9 deselected, 6 warnings in 285.28s (0:04:45) =
error: build of '/nix/store/k7w4glmv1pcfvsrxdnx1s69s926i5q9c-diffoscope-213.drv' on<EMAIL_ADDRESS>failed: builder for '/nix/store/k7w4glmv1pcfvsrxdnx1s69s926i5q9c-diffoscope-213.drv' failed with exit code 1;
       last 10 log lines:
       > tests/comparators/test_pdf.py::test_compare_non_existing
       > tests/comparators/test_pdf.py::test_metadata
       > tests/comparators/test_pdf.py::test_annotations
       >   /build/diffoscope-213/diffoscope/comparators/pdf.py:93: PendingDeprecationWarning: PdfFileReader was renamed to PdfReader. PdfFileReader will be removed
       >     pdf = PyPDF2.PdfFileReader(file.path)
       >
       > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
       > =========================== short test summary info ============================
       > FAILED tests/comparators/test_pdf.py::test_compare_non_existing - AttributeEr...
       > = 1 failed, 664 passed, 25 skipped, 9 deselected, 6 warnings in 285.28s (0:04:45) =
       For full logs, run 'nix log /nix/store/k7w4glmv1pcfvsrxdnx1s69s926i5q9c-diffoscope-213.drv'.
error: builder for '/nix/store/k7w4glmv1pcfvsrxdnx1s69s926i5q9c-diffoscope-213.drv' failed with exit code 1;
       last 10 log lines:
       > tests/comparators/test_pdf.py::test_compare_non_existing
       > tests/comparators/test_pdf.py::test_metadata
       > tests/comparators/test_pdf.py::test_annotations
       >   /build/diffoscope-213/diffoscope/comparators/pdf.py:93: PendingDeprecationWarning: PdfFileReader was renamed to PdfReader. PdfFileReader will be removed
       >     pdf = PyPDF2.PdfFileReader(file.path)
       >
       > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
       > =========================== short test summary info ============================
       > FAILED tests/comparators/test_pdf.py::test_compare_non_existing - AttributeEr...
       > = 1 failed, 664 passed, 25 skipped, 9 deselected, 6 warnings in 285.28s (0:04:45) =
       For full logs, run 'nix log /nix/store/k7w4glmv1pcfvsrxdnx1s69s926i5q9c-diffoscope-213.drv'.

Additional context
It was broken by https://github.com/nixos/nixpkgs/commit/80554b6ab7999095d9fae73fa952694c8e972cff. (CC @dotlambda).
Notify maintainers
@dezgeg @Ma27 @danielfullmer

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Made a PR here: https://github.com/NixOS/nixpkgs/pull/180257. Currently building.

Fixed by https://github.com/NixOS/nixpkgs/pull/180257.


Update hipchat to 4.30.1-756

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you, and welcome.

Awesome cask-repair script, Vítor! It made contributing really easy.
My only suggestion would be to update https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md with more direct information about installing and configuring hub (which I know isn't a prerequisite, but made dealing with github auth even smoother). Maybe I'll submit a pull request for that page when I have a spare moment.
Thanks!


Unexpected type error during the Future<List> variable assigning.

Dart SDK Version: 2.1.0-dev.4.0
OS: Windows 10 (64 bit)
Probably this is a duplicate of #34482, however I prefer to create a separate bug here: it's casting to Future<FutureOr> there and to raw Future here. Please let me know if I should treat such similar cases as duplicates of each others
Here is a sample code:
import "dart:async";
main() {
  Future<List<int>> f1 = new Future(() => [0, 1]);
  Future ff = new Future(() => [0, 1]);
  Future<List<int>> f2 = ff;
}

Analyzer does not produce compile errors here.
Dart passes on the line 3 and throws type exception on the line 5:

Unhandled exception:
type 'Future' is not a subtype of type 'Future<List>'
#0      main (file:///D:/DART/sdk/tests/co19/src/LanguageFeatures/Instantiate-to-bound/Future/test.dart:5:21)
#1      _startIsolate. (dart:isolate/runtime/libisolate_patch.dart:289:19)
#2      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

Seems like in both cases above Future object gets assigned to [Future<List>] variable, so it's expected that the result should be the same (it should not be errors here).

This error seems correct. After type inference, your program is:
import "dart:async";
main() {
  Future<List<int>> f1 = new Future<List<int>>(() =><int> [0, 1]);
  Future<dynamic> ff = new Future<dynamic>(() => <int>[0, 1]);
  Future<List<int>> f2 = ff;
}

and the assignment of a Future<dynamic> (value of ff) to a variable with type Future<List<int>> (f2) is a correct run-time error.
When we have a situation like dynamic x = [1, 2]; where the context type doesn't constrain the type parameter of the expression, we use upwards inference to find the list type, so we infer dynamic x = <int>[1, 2]; here.

You are correct, I believe bugs should be closed.


Incorrect link for workplace-join client

Hyperlink for workplace-join client on this page takes us to "Surface Laptop 3" page, NOT the expected download page for workplace-join client.  Same result happens when I search web for "workplace-join client" and select link for download.

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

ID: 2010f5ac-1080-addd-1fb3-5b05db26c1f6
Version Independent ID: 1aa18d6a-5846-7989-b844-fc8ad027921b
Content: Azure AD Connect: Seamless Single Sign-On
Content Source: articles/active-directory/hybrid/how-to-connect-sso.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@tplas Thanks for your feedback! We will investigate and update as appropriate.

@tplas I am redirecting to correct download website when I click on "workplace-join client" link.

Download link : https://www.microsoft.com/download/details.aspx?id=53554

@tplas We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add Version newtype wrapper

Ash currently represents Vulkan API versions as u32, and has a bunch of bare functions and constants to deal with them. I think it would be more idiomatic if these were represented as a newtype wrapper Version. Then the constants can be associated constants, and the functions can be methods. I realise that Vulkan itself represents these as uint32_t, so recognising which values are versions may be more difficult.

Curious how much this would conflict with #431 though.

Feel free to crib openxr::Version


Do not run integration tests in cron stage

Description
Integration tests are meant to run only as part of the test phase in travis. This PR updates the stage definition so that only the security vulnerability job is run by the cron job in travis.
I noticed this in https://travis-ci.com/github/apache/druid/builds/214984064

This PR has:

[x] been self-reviewed.
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.

merging since this change will only affect the cron travis job so no reason to run through here (and should maybe help free up a bit of travis capacity for other PRs)

merging since this change will only affect the cron travis job so no reason to run through here (and should maybe help free up a bit of travis capacity for other PRs)


Fix PostgreSQL ossp-uuid extension issues

@jamesc discovered the latest nightly builds of CS12 are causing the Analytics tests to fail with:
STDERR: ERROR:  could not open extension control file "/opt/opscode/embedded/share/postgresql/extension/uuid-ossp.control": No such file or directory
---- End output of psql --dbname actions --single-transaction --set ON_ERROR_STOP=1 --command 'CREATE EXTENSION IF NOT EXISTS "uuid-ossp"' ----
Ran psql --dbname actions --single-transaction --set ON_ERROR_STOP=1 --command 'CREATE EXTENSION IF NOT EXISTS "uuid-ossp"' returned 1
[2014-12-14T09:53:04+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

After some digging it was discovered CS12's PostgreSQL installation was to blame. The latest nightly builds were building two copies of PostgreSQL (9.2.8 and 9.2.9) as some software definitions depended on postgresql92 and others depended on postgresql. There was a time in the past when we shipped two copies of PostgreSQL for upgrade purposes but this is no longer the case with CS12+. This PR finally updates opscode-omnibus to properly depend on the upstream postgresql software definitions from omnibus-software.
PLEASE NOTE - Commit a48c538 will be finalized once opscode/omnibus-software#347 is merged.
/cc @opscode/release-engineers @opscode/server-team @jamesc @metadave

Can this be closed?

I believe this was ultimately fixed by ad01b7eafa2da7863d7a1278cf599acbeda88c80
Closing this.


Allow to pass arbitrary props to th underlying div

E.g, the LayoutSplitter component adds props to its div child, and it is styled. We can't customize its appearance, which can be annoying :/
Something usual is to split props between those used by the component and other props which we may want to apply to the underlying div, like this :
  render() {
    const {
      orientation,
      getPreviousLayout,
      //... other specific props,
      className = '',
      style,
      ...props
    } = this.props;

    let classes = ['LayoutSplitter', this.props.orientation].concat(className.split(' ');
    let finalStyle = {
      width: this.props.orientation === 'horizontal' ? LayoutSplitter.defaultSize : this.props.containerWidth,
      height: this.props.orientation === 'vertical' ? LayoutSplitter.defaultSize : this.props.containerHeight,
      ...style
    }

    return <div className={classes.join(' ')} style={finalStyle} onMouseDown={this.handleMouseDown} { ...props }/>
  }

Thanks @jide, would you be willing to put a PR up?  We'd gladly take any contributions.