text:
Find-Module -AllVersions returns no results when run against internal/private repositories

In version 1.1.7 of PowerShellGet, running "find-module <module_name> -AllVersions" returns no results when run against private /internal repositories. It does return all versions when run against the powershell gallery.
Version 1.0.0.1 of PowerShellGet that ships with Powershell 5.1 doesn't have this problem. It returns all versions of a module regardless of which repository it is run against.
Expected Behavior
Running find-module <module_name> -AllVersions should return all non-prerelease versions of a module from a repository
Current Behavior
find-module <module_name> -AllVersions returns nothing, not even the current version. However, runing find-module <module_name> without the "-AllVersions" does return the current version, regardless of the type of repository.
Possible Solution

Steps to Reproduce (for bugs)

Create a file share on local or remote computer.
Register the repository
Create a module and publish it to the repository.
Increment build number an publish to the repository
Run find-module -Repository <my_repository> will show the current version
Run find-module -Repository <my_repository> -AllVersions returns no results.

Context
We rely on being able to find and install previous versions of modules on occasion if we need to test a previous version of code. With this bug, people who have the latest build of PowerShellGet can't use some of our source code tools.
Your Environment

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.16299.98
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.98
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

> Get-Module
ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     1.0.0.0    CimCmdlets                          {Export-BinaryMiLog, Get-CimAssociatedInstance, Get-CimClass, Get-CimInstance...}
Manifest   3.0.0.0    Microsoft.PowerShell.Host           {Start-Transcript, Stop-Transcript}
Manifest   3.1.0.0    Microsoft.PowerShell.Management     {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Content...}
Manifest   3.1.0.0    Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable, Compare-Object...}
Script     1.1.7.0    PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package, Get-PackageProvider...}
Script     1.6.0      PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Find-RoleCapability...}
Script     1.2        PSReadline                          {Get-PSReadlineKeyHandler, Get-PSReadlineOption, Remove-PSReadlineKeyHandler, Set-PSReadlineKe...

> Get-Module -ListAvailable PowerShellGet,PackageManagement
ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.1.7.0    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSo
Binary     1.0.0.1    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSo
Script     1.6.0      PowerShellGet                       {Install-Module, Find-Module, Save-Module, Update-Module...}
Script     1.0.0.1    PowerShellGet                       {Install-Module, Find-Module, Save-Module, Update-Module...}

> Get-PackageProvider
Name                     Version          DynamicOptions
----                     -------          --------------
Chocolatey               2.8.5.130        SkipDependencies, ContinueOnFailure, ExcludeVersion, ForceX86, PackageSaveMode, FilterOnTag, Contains, AllowPr...
msi                      3.0.0.0          AdditionalArguments
msu                      3.0.0.0
NuGet                    2.8.5.210        Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag, Contains, AllowPrereleaseVersions,...
PowerShellGet            1.6.0.0          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, InstallUpdate, NoPathUpdate, AllowPr...
Programs                 3.0.0.0          IncludeWindowsInstaller, IncludeSystemComponent

> Get-PackageProvider -ListAvailable
Name                     Version          DynamicOptions
----                     -------          --------------
Chocolatey               2.8.5.130        SkipDependencies, ContinueOnFailure, ExcludeVersion, ForceX86, PackageSaveMode, FilterOnTag, Contains, AllowPr...
msi                      3.0.0.0          AdditionalArguments
msu                      3.0.0.0
nuget                    2.8.5.208
NuGet                    2.8.5.210        Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag, Contains, AllowPrereleaseVersions,...
PowerShellGet            1.6.0.0          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, InstallUpdate, NoPathUpdate, AllowPr...
PowerShellGet            1.0.0.1
Programs                 3.0.0.0          IncludeWindowsInstaller, IncludeSystemComponent

After investigation, I found that this is a regression in 1.1.7.0 version of PackageManagement. PowerShellGet provider returns the results but PackageManagement core in 1.1.7.0 version doesn't return these results.

This issue was moved to OneGet/oneget#343

authors: bmanikm dheise

repo: PowerShell/PowerShellGet


text:
Connect issues when using non stanadard ports

First I install SQL with xSqlServerSetup
Then I Configure Networking with xSQLServerNetwork to set a non standard port 9999 (not really using this port)
Then I disable browser service.
Then I disabled Shared Memory Protocol in SQL Configuration
It runs fine the first time but when I run the Config again it errors on Test-Resource with Can't connect to instance. This is because it is attempting an connection on localhost/InstanceName with no port information.
I recommend during the SQL connect function it checks to see if port is specified and uses that port. Maybe check for browser service and shared memory.

Hi,
I have the same exact problem. It was working well in the release 4 but since release 5, it seems to be broken.

I did a test with release 6 and didn't get the error. Seems it has been fixed.

@wickedave Happy to hear that 6.0 solved your issue.
@edycus Could you test released version 6.0? See if the problem is gone like for @wickedave.
6.0 was release yesterday.

I have tested and it did work for the first pass but after the disabling of the service I get this
VERBOSE: [SSVDBOLYTEST01]: LCM:  [ Start  Resource ]  [[xSQLServerSetup]installSqlServerTestSql1]
VERBOSE: [SSVDBOLYTEST01]: LCM:  [ Start  Test     ]  [[xSQLServerSetup]installSqlServerTestSql1]
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] Importing the module MSFT_xSQLServerSetup in force mode.
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-33: Using path: C:\Admin\DBA\DSCPowershellSQL\Software\SQL2014ENT\setup.exe
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] Perform operation 'Query CimInstances' with following parameters, ''queryExpression' = SELECT * FROM Win32_Service WHERE Nam
e = 'MSSQL$TESTSQL1','queryDialect' = WQL,'namespaceName' = root\cimv2'.
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] Operation 'Query CimInstances' complete.
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] Perform operation 'Query CimInstances' with following parameters, ''queryExpression' = SELECT * FROM Win32_Service WHERE Nam
e = 'SQLAgent$TESTSQL1','queryDialect' = WQL,'namespaceName' = root\cimv2'.
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] Operation 'Query CimInstances' complete.
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-33: Detecting replication feature (HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.TESTSQL1\Configura
tionState)
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-33: Replication feature not detected
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-33: Client Connectivity Tools feature not detected
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-33: Client Connectivity Tools Backwards Compatibility feature not detected
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-33: Connected to SQL SSVDBOLYTEST01\TESTSQL1
The following exception occurred while trying to enumerate the collection: "Failed to connect to server SSVDBOLYTEST01\TESTSQL1.".
+ CategoryInfo          : NotSpecified: (:) [], CimException
+ FullyQualifiedErrorId : ExceptionInGetEnumerator
+ PSComputerName        : SSVdbOlyTest01
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-48: Clustered instance not detected
VERBOSE: [SSVDBOLYTEST01]:                            [[xSQLServerSetup]installSqlServerTestSql1] 2017-03-10_12-15-48: Features found: 'SQLENGINE,SSMS'
VERBOSE: [SSVDBOLYTEST01]: LCM:  [ End    Test     ]  [[xSQLServerSetup]installSqlServerTestSql1]  in 15.5610 seconds.
The PowerShell DSC resource '[xSQLServerSetup]installSqlServerTestSql1' with SourceInfo 'C:\Admin\DBA\DSCPowershellSQL\3 - SSVdbOlyTest01.ps1::364::13::xSqlServerSetup' threw one or more non-terminating errors while
running the Test-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.
+ CategoryInfo          : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : NonTerminatingErrorFromProvider
+ PSComputerName        : SSVdbOlyTest01

I close this issue and track this in the issue https://github.com/dsccommunity/SqlServerDsc/issues/329 instead. There should be a way to support this.

source: gharchive/issue

authors: edycus johlju wickedave

repo: PowerShell/xSQLServer

license: mit

license_type: permissive

license_source: bigquery


text:
additional parameters for xSPWebAppGeneralSettings in hardened environments

added the following parameters to xSPWebAppGeneralSettings
SecurityValidationExpires
SecurityValidationTimeOutMinutes
AllowOnlineWebPartCatalog
SelfServiceSiteCreationEnabled

This change is

Review status: 0 of 5 files reviewed at latest revision, 1 unresolved discussion.

README.md, line 112 [r2] (raw file):
Please ping me on the steps to get the cla-required tag removed

Comments from Reviewable

Review status: 0 of 5 files reviewed at latest revision, 1 unresolved discussion.

README.md, line 112 [r2] (raw file):
Done.

Comments from Reviewable

closing and reopening to update cla tag

Reviewed 1 of 5 files at r2.
Review status: 1 of 5 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 5 of 5 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Tests/xSharePoint/xSharePoint.xSPWebAppGeneralSettings.Tests.ps1, line 13 [r2] (raw file):
Why do we need to force the import of the module here?

Comments from Reviewable

the -force is left over from testing. Changes to the code would not reload in the same powershell session. I'll remove and re-commit.

Review status: 4 of 5 files reviewed at latest revision, 1 unresolved discussion.

Tests/xSharePoint/xSharePoint.xSPWebAppGeneralSettings.Tests.ps1, line 13 [r2] (raw file):
Done.

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

source: gharchive/pull-request

repo: PowerShell/xSharePoint

license: MIT

license_source: github-api


text:
It doesn't detect the letters properly. Please fix.

Example: It detecs this: Thisw trip exntails nonsftop white water qrapids, narrnow passageowayS<T Anhbdi ssteep drropsx, g. You can tell that that's not the right text.

Could you maybe decode the JS and maybe I can find a fix with a pull?

It is correct detection. Thisw is This, trip is trip, nonsftop is nonstop, and so on.
The extra characters are added for error generation. Set accuracy to 100 and you will get all words correct.

It still doesn't work. It fixed the detection problem, but it doesn't type the words.

repo: PrabhakarRai/nitro-type-hack-bot


text:
4.g.iii Number of User Stories Deleted

A user should be able to see the number of deleted user stories.
Priority: LOW
Estimation: 1

Merged into user story #48

repo: PragTob/TracketyTrack


text:
File browser broken

Hello. I've tried and installed this wonderful platform. But  I can't upload a file in the admin section because when I clicked on the button 'photo', nothing occurs. I've tried to add a new product. The situation is similar when I try to add a new banner and so on.

@sly04 please, explore this package https://unisharp.github.io/laravel-filemanager/installation

hi can you send the screen capture pls

Did anyone get a fix to this issue, Im facing the same issue
On Thu, 5 May 2022, 23:20 R Λ Z, @.***> wrote:

hi can you send the screen capture pls
—
Reply to this email directly, view it on GitHub
https://github.com/Prajwal100/Advance-Ecommerce-in-laravel-7/issues/57#issuecomment-1119009198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJUZ7KHG6PMVQH6UME5LAQDVIQUO7ANCNFSM5QV5NSOQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
.com>

@dzeusif please pull the lastest code.


text:
phlow spinner

The phlow spinner resulted in wrong formatting on windows, and was removed from the release. However the feedback was quite good and we need to figure out if we want to keep it

there have been no complaints about the removal of the spinner, so we will keep it removed until further notice

repo: Praqma/git-phlow


text:
Emerald apple does not get consumed when used on zombie villager

Minecraft version & Mod Version:
Horizons III modpack , 1.12
Single player or Server: SP
Emerald apple is supposed to be a single use item and get consumed
https://twitter.com/lothrazar/status/936489057974067200

Emerald apple is so expensive that I think it shouldn't be consumed。

Maybe i did do that on purpose, i forget.
Or maybe it could have multi uses, or be cheaper?
It kind of does two different things, maybe that could be split into 2 items? Ill think on that. Any suggestions?

Player can use emerald apple to let two villagers breed a little villager。Is it OK？

Some people want zombie villager become a new special villager（need custom in code）or just villagers in other mods such as AA or IE。

When a zombie villager is cured, it can be come any type, modded or not from what I have seen.
I will make it much cheaper so that having it get consumed is not so bad. Ill do some testing and get some feedback before release

authors: PrinceOfAmber forestbat

repo: PrinceOfAmber/Cyclic


text:
As a content manager, I want to be able to update the homepage content without requiring dev work or writing html

This updates the index page to run through a new filter to format the content from Mezzanine. The home page is broken down into 2 components - main and credits. The main section is minimally formatted, just wrapped in a section. The credits are more stylized and require the user to make smaller changes to render correctly. The credited role must be bold and the name must be italics. These were chosen based on the common styles available from the TinyMCE options.
An example of the page in the CMS would looks like this:
[main]
“Derrida’s Margins” aims to create a website and online research tool for annotations from the Library of Jacques Derrida, housed at Princeton University Library...
[/main]
[credits]
Project Director
Katie Chenoweth
...
[/credits]

All of the homepage content is now editable using the rich text editor. Two shortcuts have been added to the editor:

"Credits", which inserts a set of role/name with the correct styling
"Credit section", which inserts the wrapper for the credits, in case it was accidentally deleted.

The default text for the homepage and credits have been changed to the provided versions in this document.

authors: kevinglover thatbudakguy

repo: Princeton-CDH/derrida-django


text:
As a user, I want to see a chronological list of circulation activity for a single library item so that I can see which library members interacted with it.

testing notes
designs
initial view - desktop / tablet / mobile
scrolled down - desktop / tablet
you should be able to visit any book's page via the books search to test this. make sure to check:

member's names should be links to their member page
dates should be right
sorting the table should work

the designs for mobile include sorting controls that stick to the top; this isn't implemented for any of the tables (like borrowing or membership activity on members) but is a wishlist feature.
dev notes
this page parallels the member borrowing activities page, but for a book instead of a person. most of the design/behavior should be identical.

Will need to include issue number/date or volume if known.

Desktop: I tested with Pilgrimage (tons of circulation, as well as different volumes) and The Autobiography of Alice B. Toklas:

YES, I am able to click on the name of the members who borrowed the book and it takes me to the individual member detail page
YES, all the dates look correct
YES, I am able to sort by: start date, end date, status, and vol/issue (tried the latter with Pilgrimage's many volumes)

Mobile: I tested with Dubliners (lots of circulation) and The Adventures of Peregrine Pickle (multivol)

YES, I am able to click on the name of the members who borrowed the book and it takes me to the individual member detail page
YES, dates are all correct, and if the book has multi volumes then I see them on the right side of the screen:

I don't see any sorting options but I understand this is a wishlist item for mobile

Tablet: Tried with Ulysses

YES, I am able to click on the name of the members who borrowed the book and it takes me to the individual member detail page
YES, all the dates look correct
YES, I am able to sort by: start date, end date, status, and vol/issue

This looks fantastic. It's amazing seeing the data in a whole new way.

authors: clmahoney jkotin rlskoeser

repo: Princeton-CDH/mep-django


text:
Feature Request : Add more dimensionless units : ppm, ppb, ‱, etc...

For now % (percent) and ‰ (permille) dimensionless units are supported.
It would be nice to also have :

‱  : per 10,000
pcm : per 100,000
ppm : per million
ppb : per billion
(see https://en.wikipedia.org/wiki/Parts-per_notation)

The custom units does not work well with dimensionless units. See the following code :
'1 Ampere multiplied by 1ppm equals 1μA => works fine
1A*0.0001%|μA

'Same calculus, does not work properly
.ppm = 0.0001%
1A*1ppm
1A*1ppm|μA

Hi!
I added these in version 7.1.0:
https://github.com/Proektsoftbg/Calcpad/releases/tag/v7.1.0.
Dimensionless units: %, ‰, ‱, pcm, ppm, ppb, ppt, ppq;

Thank you for the quick feedback!
Everything seems to work fine, except for the permyriad symbol, for which I get the following error :
Error in "1‱" on line [12]: Invalid symbol: "‱".
I used the symbol directly from the documentation page :

I think this update added a bug with |%.  Surely changed the behaviur from the 7.19 since broked some my old code

In my opinion 0.14|% should give 14% aka 0.14

@sononicola, yes you are absolutely right. Thank you! I will fix that too.

Hi! Everything is now fixed in version 7.1.1:
https://github.com/Proektsoftbg/Calcpad/releases/tag/v7.1.1

authors: Proektsoftbg fblgdc sononicola

repo: Proektsoftbg/Calcpad


text:
Update to 1.20.6

As titled. Confirmed it starts without errors and the Dynatech category is present. Not sure what the paperlib shading business is about but it seems to work, just lmk if you need anything changed

Why was paperlib added as a dependency?

authors: LordIdra ProfElements

repo: ProfElements/DynaTech


text:
Letter customization

#428 #529

@paramsiddharth I need to review it locally.

@DietBepis1 Hi Glenn, just wanted to share the screen recording for the error that is coming up with current code.
https://user-images.githubusercontent.com/843538/232210484-b5d812a3-9acd-466d-84aa-e5060c1d24db.mp4
Also, did some analysis with help from @yoyoyojoe on ways to resolve the error. Essentially, we made two main changes:

Removed persistCustomization() function from LetterLoad.vue file and committed userCustomMessage within the watch option.
Removed this.$refs.letterLoad.persistCustomization() from TakeAction.vue file.

Please see the screen recording below to see the flow after these changes. Notice userCustomMessage getting added in this.$store.state
https://user-images.githubusercontent.com/843538/232214448-09934154-407b-4b46-a8ee-16e323355d7b.mp4
I can add a commit for you to see the code changes if this is something you would like me to proceed with. Please let me know if you would recommend another approach. Looking forward to your feedback. Thank you.

@DietBepis1 Hi Glenn, just wanted to share the screen recording for the error that is coming up with current code.
Also, did some analysis with help from @yoyoyojoe on ways to resolve the error. Essentially, we made two main changes:
* Removed persistCustomization() function from LetterLoad.vue file and committed userCustomMessage within the watch option.

* Removed this.$refs.letterLoad.persistCustomization() from TakeAction.vue file.

Please see the screen recording below to see the flow after these changes. Notice userCustomMessage getting added in this.$store.state
I can add a commit for you to see the code changes if this is something you would like me to proceed with. Please let me know if you would recommend another approach. Looking forward to your feedback. Thank you.

@SAUMILDHANKAR and @yoyoyojoe, just wanted to say that this was excellent collaboration and a great demonstration. 👍🏽

@paramsiddharth and @SAUMILDHANKAR, how did this PR get branched off of the original one from Sammy? The reason I am asking is that I noticed a missing prop repName error in the videos posted in the last few comments. That prop is removed in our main branch. The PR itself looks good and ready to merge, but I am worried that we may introduce bugs into the main codebase since I can see this unused prop.

@paramsiddharth and @SAUMILDHANKAR, how did this PR get branched off of the original one from Sammy? The reason I am asking is that I noticed a missing prop repName error in the videos posted in the last few comments. That prop is removed in our main branch. The PR itself looks good and ready to merge, but I am worried that we may introduce bugs into the main codebase since I can see this unused prop.

@DietBepis1 Saumil branched it off Sam's PR's branch into a branch in this repository – The prop must have been introduced while resolving the conflicts. It is something we'll have to pair up on, I believe. Perhaps outside the pair hours, some dedicated time.

@paramsiddharth and @SAUMILDHANKAR, how did this PR get branched off of the original one from Sammy? The reason I am asking is that I noticed a missing prop repName error in the videos posted in the last few comments. That prop is removed in our main branch. The PR itself looks good and ready to merge, but I am worried that we may introduce bugs into the main codebase since I can see this unused prop.

@DietBepis1 Saumil branched it off Sam's PR's branch into a branch in this repository – The prop must have been introduced while resolving the conflicts. It is something we'll have to pair up on, I believe. Perhaps outside the pair hours, some dedicated time.

+1 to what Param just mentioned. Also, wanted to share that the workflow looked fine when I removed repName in my local environment and the error went away as well.

authors: DietBepis1 SAUMILDHANKAR paramsiddharth

repo: ProgramEquity/amplify


text:
RichTextBlock go wrong after navigating back

What it should be:

but I get:

after scrolling down then back to the top, everything works fine.

What's your ItemTemplate?

@higankanshi like this
                    <DataTemplate>                         <StackPanel x:Name="stackPanel" Height="{Binding Length}" Background="{Binding Brush}" HorizontalAlignment="Stretch">                             <TextBlock FontSize="50" Text="{Binding Num}" HorizontalAlignment="Center" VerticalAlignment="Center"/>                             <RichTextBlock HorizontalAlignment="Stretch" VerticalAlignment="Stretch">                                 <Paragraph>                                bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10bug10                                 </Paragraph>                             </RichTextBlock>                         </StackPanel>                     </DataTemplate>

See the last commit, maybe this commit fix it.

Well, actually no, it still there

authors: Tlaster higankanshi

license: WTFPL


text:
Issue creating a listing.

There were barely any examples of creating a listing in the docs for this; so i've been scraping code off of some issues here. I cant figure out what to do next to create a listing. It looks like infura api is getting requests but no listing is created on testnet opensea.
All Im trying to do is create a listing for a testnet NFT. Any help appreciated :)
const { Seaport } = require('@opensea/seaport-js');
const { ethers } = require('ethers');

// Provider must be provided to the signer when supplying a custom signer
const provider = new ethers.providers.JsonRpcProvider(
  "https://goerli.infura.io/v3/<API_KEY>"
);
const privateKey = "";
const signer = new ethers.Wallet("privateKey", provider);

const seaport = new Seaport(signer);

const main = async () => {
    const offerer = "0x096483d4AdDD6ccB428D81400483D503DaE2e505";
    const { executeAllActions } = await seaport.createOrder(
        {
            offerer: offerer,
            zone: "0x0000000000000000000000000000000000000000",
            zoneHash: "0x0000000000000000000000000000000000000000000000000000000000000000",
            startTime: Math.floor(new Date().getTime() / 1000).toString(),
            endTime: Math.floor(new Date().getTime() / 1000 + 60 * 60).toString(),
            offer: [
                {
                    itemType: 2,
                    token: "0xd08d514c3a6f4625a3546a9dff43c8e27a5cd00a",
                    identifier: "18",
                },
            ],
            consideration: [
                {
                    amount: ethers.utils.parseEther("0.0002").toString(),
                    recipient: offerer,
                },
            ],
            orderType: 1,
        },
        offerer
    );

    const order = await executeAllActions();
    console.log(order);
}
main();

Current output:
{
  parameters: {
    offerer: '0x096483d4AdDD6ccB428D81400483D503DaE2e505',
    zone: '0x0000000000000000000000000000000000000000',
    zoneHash: '0x0000000000000000000000000000000000000000000000000000000000000000',
    startTime: '1686777408',
    endTime: '1686781008',
    orderType: 0,
    offer: [ [Object] ],
    consideration: [ [Object] ],
    totalOriginalConsiderationItems: 1,
    salt: '0x000000000000000000000000000000000000000000000000aaea3fd9cdfbc111',
    conduitKey: '0x0000000000000000000000000000000000000000000000000000000000000000',
    counter: '0'
  },
  signature: '0x37a68eca15edf5c5978501417f29f6d09651b3439d8ddc77b9ea1d30cbf5de6e14541f29947aad6c31d5d9c030515f76c00d6ca7f85cae1597a4bed679e'
}

you have to call validate() if you want it to list it on chain, otherwise use opensea-js and create a self serve API key to submit it to opensea without an on chain tx

to have it show up on opensea you also need to have a consideration item to the opensea fee recipient wallet with 2.5%. using opensea-js to submit will give you feedback if the order isn't properly formatted

you have to call validate() if you want it to list it on chain,
validate like so? ```
const validated = seaport.validate([order]);
const transaction = await validated.transact();
console.log('validated: ', await transaction.wait());

I've tried this before but i get this result ```
validated:  {
  to: '0x00000000000000ADc04C56Bf30aC9d3c0aAF14dC',
  from: '0x096483d4AdDD6ccB428D81400483D503DaE2e505',
  contractAddress: null,
  transactionIndex: 124,
  gasUsed: BigNumber { _hex: '0x0101d6', _isBigNumber: true },
  logsBloom: '0x00000000400008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000100000000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000',
  blockHash: '0x1df56ecd9a27c6481c0869ca42630aff1a4b7dfc53be535f24453fa1341e',
  transactionHash: '0xc8cfdf17d4f13a39915b205d0fe8230668c85c12a3181fddc8ee92fe6c625',
  logs: [
    {
      transactionIndex: 124,
      blockNumber: 9179549,
      transactionHash: '0xc8cfdf17d4f13a39915b205df0b0fe8230668c85c12a3181fde92fe6c625',
      address: '0x00000000000000ADc04C56Bf30aC9d3c0aAF14dC',
      topics: [Array],
      data: '0xff7daa4ff4a7398384e15824bc924a048a0b3168910e4156e428e848e6a2816800000000000000000000000000000000000000000000000000000000000000400000000000000000000000000964b428d81400483d503dae2e505000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000220000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000648a399d00000000000000000000000000000000000000000000000000000000648a47ad00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009e27946a922795c70000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000002000000000000000000000000d08d514c3a6f4625a3546a9dff43c8e27a5cd00a00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000b5e620f480000000000000000000000000000000000000000000000000000000b5e620f48000000000000000000000000000096483d4addd6ccb428d81400483d503dae2e505',
      logIndex: 220,
      blockHash: '0x1df56ecd9a27c6481c0869ca42630aff1252ea4b7dfc53be535f24453fa1341e'
    }
  ],
  blockNumber: 9179549,
  confirmations: 1,
  cumulativeGasUsed: BigNumber { _hex: '0xc947b8', _isBigNumber: true },
  effectiveGasPrice: BigNumber { _hex: '0x5e60db4b', _isBigNumber: true },
  status: 1,
  type: 2,
  byzantium: true
}

thanks, yeah looks good but i found the error on our backend:

You provided an invalid conduit key: 0x0000000000000000000000000000000000000000000000000000000000000000, please use OpenSea's conduit key: 0x0000007b02230091a7ed01230072f7006a004d60a8d4e71d599b8104250f0000 for order placement
so you'll want to approve the conduit for that contract from your account too before you send the validate()

I'm not sure I understand what you mean by that. Sorry kinda new to this, could you elaborate on that a bit?

no prob

on your token contract from your offerer address call setApprovalForAll with operator= 0x1e0049783f008a0085193e00003d00cd54003c71
set the conduitKey in your order to 0x0000007b02230091a7ed01230072f7006a004d60a8d4e71d599b8104250f0000

im not sure if i did it right but it still didnt show up on opensea hmmm
    const conduitAddress = "0x1e0049783f008a0085193e00003d00cd54003c71";
    const conduitKey = "0x0000007b02230091a7ed01230072f7006a004d60a8d4e71d599b8104250f0000";

    const tokenContractAddress = "0xd08d514c3a6f4625a3546a9dff43c8e27a5cd00a";
    const tokenContract = new ethers.Contract(tokenContractAddress, contractABI, signer);
    await tokenContract.setApprovalForAll(conduitAddress, true);

    const { executeAllActions } = await seaport.createOrder(
        {
            offerer: offerer,
            zone: "0x0000000000000000000000000000000000000000",
            zoneHash: "0x0000000000000000000000000000000000000000000000000000000000000000",
            startTime: Math.floor(new Date().getTime() / 1000).toString(),
            endTime: Math.floor(new Date().getTime() / 1000 + 60 * 60).toString(),
            offer: [
                {
                    itemType: 2,
                    token: "0xd08d514c3a6f4625a3546a9dff43c8e27a5cd00a",
                    identifier: "18",
                },
            ],
            consideration: [
                {
                    amount: ethers.utils.parseEther("0.0002").toString(),
                    recipient: offerer,
                },
            ],
            orderType: 1,
            conduitKey: conduitKey
        },
        offerer
    );

update:
I added operator approval through etherscan and it still doesnt get listed on opensea. Any idea what's going wrong?

@FiveNine the error is:
Failed to submit an order: An incorrect OpenSea fee has been provided. Expecting 250 basis points, but received 0. . Transaction hash 0x414938abd987583392ecaa68ec2c6bf2594ed3431b6647b5d710bc8a6d6fad86 , order hash 0xe86ddabea324068e5c593291aa40673073f4e468be4da2cde5637118d6998687

you'll need to add 2.5% of the total order value as a consideration item to 0x0000a26b00c1F0DF003000390027140000fAa719

ah thank you so much, it worked!
I'm just gonna leave my code here and close the issue in case anyone else stumbles upon this
const { Seaport } = require('@opensea/seaport-js');
const { ethers } = require('ethers');

const provider = new ethers.providers.JsonRpcProvider(
  "https://goerli.infura.io/v3/<API_KEY>"
);

const signer = new ethers.Wallet("<Private_KEY>", provider);

const seaport = new Seaport(signer);

const main = async () => {
    const offerer = "0x096483d4AdDD6ccB428D81400483D503DaE2e505"; // address of the NFT owner

    const conduitKey = "0x0000007b02230091a7ed01230072f7006a004d60a8d4e71d599b8104250f0000";

    const { executeAllActions } = await seaport.createOrder(
        {
            offerer: offerer,
            zone: "0x0000000000000000000000000000000000000000",
            zoneHash: "0x0000000000000000000000000000000000000000000000000000000000000000",
            startTime: Math.floor(new Date().getTime() / 1000).toString(),
            endTime: Math.floor(new Date().getTime() / 1000 + 60 * 60).toString(),
            offer: [
                {
                    itemType: 2,
                    token: "0xd08d514c3a6f4625a3546a9dff43c8e27a5cd00a",
                    identifier: "18",
                },
            ],
            consideration: [
                {
                    amount: ethers.utils.parseEther("0.0002").toString(),
                    recipient: offerer,
                },
                {
                    amount: (ethers.utils.parseEther("0.0002") * 0.025).toString(),
                    token: "0x0000000000000000000000000000000000000000",
                    recipient: "0x0000a26b00c1F0DF003000390027140000fAa719" // opensea fee
                }
            ],
            orderType: 1,
            conduitKey: conduitKey
        },
        offerer
    );

    const order = await executeAllActions();
    console.log(order);

    const validated = seaport.validate([order]);
    const transaction = await validated.transact();
    console.log('validated: ', await transaction.wait());

}
main();

great to hear, thanks!

authors: FiveNine ryanio

repo: ProjectOpenSea/seaport-js


text:
added test case for deleting promotions

nosetests confirmed service is working properly

reviewed.

repo: PromotionsSquad/promotions


text:
No option to remove near expiry profiles

Describe the Bug
Unable to remove near expiry profiles due to the option not being available
Expected Behavior
Request to remove should appear on a profile no matter how long it's registered
Screenshots

Device and Browser Information
Brave, Chrome, Edge, Firefox

This is the expected behavior. It's not allowed to request a removal while profiles are in the renewal period.

repo: Proof-Of-Humanity/proof-of-humanity-web


text:
Support for show/hide neutral losses spectrum annotation

Replaced the context menu items for ion type and charge selection with specialized menu-hosted controls.

This PR is ready for the code review.

This is how it looks with enough losses defined:

I was thinking how to address that extra border problem when a button on the control has focus. Do you think this style will work? It doesn't have borders at all.

repo: ProteoWizard/pwiz


text:
MPU6050 calibration

Ok I uploaded the sketch to the arduino. How do I get it to run? The wiki says press any key but that does nothing as far as I can see and I don't get anything to answer yes to.

1st! You need to open the Serial Monitor on Tools.
2nd! Sets the right Baud Rate for communications. (If this does not match the value set up in your sketch in Setup, characters will be unreadable). Example: Serial.begin(9600); Some sketches or other applications may use a different Baud Rate.

That's in theory.
I do all that but can't configure my accelerometer yet.
I figured out that my problem with Gravity Color was a bad calibration of my MPU6050.
How we can configure the offsets manually?

But what do I send when I open serial monitor. It seems to do nothing regardless of what I send.

If you configure the right Baud the serial monitor will send you a message like "press any key to continue" and then you press "any key" and the sketch will set up the offsets.
When it's done the Serial Monitor will ask you if you want to save the offsets to the EPROM.
In other way, if you don't see any legibly message on your serial monitor, try with other Baud.

The communication baud in the sketch says 115200. I set it to that and it still does nothing. Not liking the look of this!!

If you need to recalibrate your MPU, use this one, same as I use to test my DIYino boards:
https://github.com/Protonerd/DIYino/blob/master/DIYino_Testsketch_Pro.ino
Let us know how it performs for you.

Ok I'll have a go with that once its downloaded.

Ok I ran that and it said connecting to DFplayer and then connected to DFPlayer and that was it nothing else.

Thank you! I will try that one too.

Well I have still had no life from the calibration program. I also uploaded the fxsaberos sketch to see if that did anything and it doesn't. Whether its because the mpu6950 calibration hasnt run though I don't know.
The nano I am using is a cheap copy though with a ch340 serial chip, would that make a difference or is that what others are using?

It shouldn't matter.  The calibration program is pretty simple from the
user side and should just work, I've used it with nano and pro mini from
various vendors as well as the DIYino boards.
Jason "Kuma" Brinkerhoff
*Mad Science Workshoppe, *proprietor
http://jbkuma.com/workshoppe
On Thu, Dec 28, 2017 at 11:07 AM, FatherCool notifications@github.com
wrote:

Well I have still had no life from the calibration program. I also
uploaded the fxsaberos sketch to see if that did anything and it doesn't.
Whether its because the mpu6950 calibration hasnt run though I don't know.
The nano I am using is a cheap copy though with a ch340 serial chip, would
that make a difference or is that what others are using?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Protonerd/FX-SaberOS/issues/34#issuecomment-354311930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATdCMJdgEZ78Y7ACcP-977yYXJUaON_Cks5tE7ykgaJpZM4RNyJt
.

It doesn't run.
I have uploaded the simple led blibk test sketch to check the board and that runs no problem.
I have just put a multimeter across the 3v3 pin and ground and only got 1.84v which is the wire going to the mpu6050. Do you think that that is an issue?
Would you advise that I rebuild with new parts?

It will definitely need the proper power supplied to it.
Does the script prompt you at all?  Something should be showing up in your
serial monitor.
Jason "Kuma" Brinkerhoff
*Mad Science Workshoppe, *proprietor
http://jbkuma.com/workshoppe
On Thu, Dec 28, 2017 at 12:00 PM, FatherCool notifications@github.com
wrote:

It doesn't run.
I have uploaded the simple led blibk test sketch to check the board and
that runs no problem.
I have just put a multimeter across the 3v3 pin and ground and only got
1.84v which is the wire going to the mpu6050. Do you think that that is an
issue?
Would you advise that I rebuild with new parts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Protonerd/FX-SaberOS/issues/34#issuecomment-354320283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATdCMHIRhVPl6MfHMx2-0HOLFCGEwxZcks5tE8kdgaJpZM4RNyJt
.

If the MPU6050 isn't working your serial monitor should look like this:
`Send any character to start sketch.
MPU6050 Calibration Sketch
Your MPU6050 should be placed in horizontal position, with package letters facing up.
Don't touch it until you see a finish message.
MPU6050 connection failed`

No I don't receive anything through the serial monitor at all. When I ran protonerds other sketch I got a dfplayer connected prompt but still nothing from the mpu6050 part of it at all.

I just uploaded the calibration sketch to nano with nothing attached to it, straight from the package and got those results.  Are you sure you are uploading the calibration sketch to the board properly?

I believe so. It compiles fine and shows the red RX light and then a little TX light before saying upload done.

Will it work on a mega as I have one of those spare to use as a test bed?

Ok update. I have stripped everything from the board to run it naked so to speak. The sketch with nothing attached now runs and talks to the serial monitor correctly. I can only assume that something was causing an issue connected to the board. The bad news is that I have managed to rip off the copper track on the 3v3 pin completely during de-soldering to the board is a dead stick now for purpose in any case.
New board required!!

It seems like something was bad with the board already since the 3v3 line was low, perhaps it was shorted or the regulator was fried. Fortunately Nanos are plentiful and cheap these days!

Yes indeed. I am just frustrated that I now need to wait to get another!!

authors: FatherCool MattLeshman Protonerd jbkuma

repo: Protonerd/FX-SaberOS


text:
Classical LP Solver

Solver that can be selected in the LP problem mask.
We could use GAMS here, but using any open-source LP solver would work too.
Google OR-Tools could be used here, it also has a Java wrapper and can be added via Maven:
https://developers.google.com/optimization/install/java/pkg_windows?hl=de
Solving LP Example:
https://developers.google.com/optimization/lp/lp_example?hl=de
Start by creating a new repo and implementing prototypes for the solvers there. We need a wrapper so that we can call them from Java. The input format has to be an LP file.

@eifi0 did some work for this issue in a practical course.
Find input here: https://github.com/ProvideQ/ilp-solving

Extended to #84

repo: ProvideQ/toolbox-server


text:
Suggestion

Can you make a way to grand XX user with "XX" node and they would have full perms for it (Like creating servers with the ram/disk space they got.)

Has been suggested in the past, not planned in the near future, see the old issue for details.
Also, when you have a feature request, please be a little more specific, especially in the title. Maybe something like [Suggestion] Permissions per node or something and a little more text in the description itself. It's not like i didn't get what you would like to have in the panel. But as you want something done, just put a little more love into the request. And if its just setting a proper title so we can see what the issue is about at a glance.
Duplicate of #199

authors: RedixCoreBG schrej

repo: Pterodactyl/Panel


text:
Investigate Nestjs

Take a look at NestJS and make a decision about using it or not in the Complaint Manager 2.0 MVP.

What is NestJS?
Nest (NestJS) is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with and fully supports TypeScript (yet still enables developers to code in pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).
Under the hood, Nest makes use of robust HTTP Server frameworks like Express (the default) and optionally can be configured to use Fastify as well!
Nest provides a level of abstraction above these common Node.js frameworks (Express/Fastify), but also exposes their APIs directly to the developer. This gives developers the freedom to use the myriad of third-party modules which are available for the underlying platform.
Reference
Other than the documentation, I also took a look at these samples of implementations.
Should we use it for MVP?

[ ] Yes
[x] No

Given that NestJS adds a abstraction layer on top of Express (which we were planning to use to begin with), I decided to suggest for the team to not use NestJS for the MVP because it adds complexity to the project. Also since NestJS is an opinionated package, it would require the project to be structured following their point of view.

What is NestJS?
Nest (NestJS) is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with and fully supports TypeScript (yet still enables developers to code in pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).
Under the hood, Nest makes use of robust HTTP Server frameworks like Express (the default) and optionally can be configured to use Fastify as well!
Nest provides a level of abstraction above these common Node.js frameworks (Express/Fastify), but also exposes their APIs directly to the developer. This gives developers the freedom to use the myriad of third-party modules which are available for the underlying platform.
Reference
Other than the documentation, I also took a look at these samples of implementations.
Should we use it for MVP?

[ ]  Yes
[x]  No

Given that NestJS adds a abstraction layer on top of Express (which we were planning to use to begin with), I decided to suggest for the team to not use NestJS for the MVP because it adds complexity to the project. Also since NestJS is an opinionated package, it would require the project to be structured following their point of view.

authors: faraakhatTW heliofreitastw

repo: PublicDataWorks/complaint-manager


text:
upgrade

please upgrade appcompat-v7 to 27.1.1,  I have mix vertion of this lib  with 26
thanks before.

bye.

Hi @sooodi. In the last release I've updated SDK version to 27.

authors: PuffoCyano sooodi

repo: PuffoCyano/Range-Time-Picker-Dialog


text:
Travis, CodeCov and GitHub release badges images are broken

Looks like links to these images are broken, possibly just a changed URL somewhere

thanks @pacharanero
@BogdanScherban could you take a look at this please?
thanks, T

@tony-shannon
We need in login and password for https://github.com/PulseTile/ and https://github.com/LeedsCC/ to set these buttons. Because Travis use login and password the same for Github.
We checked possibility to solve this issue for my repository:

thanks @BogdanScherban
The issue isnt with login access, its with the change in URL as @pacharanero suggested
ie the readme file here points to;
///https://travis-ci.org/PulseTile/PulseTile-React
and so needs adjusting accordingly

authors: BogdanScherban pacharanero tony-shannon

repo: PulseTile/PulseTile-React-Core


text:
🛑 Overseerr is down

In 9a1725b, Overseerr (https://request.pxlbuzzard.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Overseerr is back up in 0905d9b.

repo: PxlBuzzard/upptime


text:
Show filenames with errors in --check mode

Now:
Running autoflake...
Unused imports/variables detected.%

How will be great:
Running autoflake...
src/foo/bar/file.py - Unused imports/variables detected.

Seems this was fixed in #57

This should've been fixed already but #148 fixed this again. @fsouza  can we close this?

authors: MarcoGorelli arxell ericstengard

repo: PyCQA/autoflake


text:
Fix F541

I updated flake8 and noticed that autoflake doesn't fix F541: f-string without any placeholders. I'd be happy to write up a PR for this, but I'm not familiar with the code--anybody have pointers?

https://github.com/dannysepler/rm_unneeded_f_str handles this as a CLI tool or pre-commit hook

authors: dannysepler jmcarp


text:
Deployment and safety code interacting causes issues.

Having the deployment be an asynchronous call causes the safety code to measure the voltage during burn. Because of the high burn currents, this voltage is lower than is "safe" and the safety code takes over.

The 15s deployment burn time is also way too long, we can definitely cut it down to 5 seconds with a 20% duty cycle.


text:
Implement PyClass for PathBuf and Path

There exists an infallible conversion from String to PathBuf (and hence Path), so if I'm not missing something, there is no real reason not to implement PyClass for PathBuf/Path.
That would allow Rust functions exposed to Python to take paths as parameters with the actual appropriate Rust type, instead of having to use String as a workaround.

I'm trying to make a PR for this

I'm trying to make a PR for this

I think rather than PyClass, you should implement IntoPy<PyObject>, ToPyObject, and FromPyObject for PathBuf (and maybe Path, if you can make it work).

I think rather than PyClass, you should implement IntoPy<PyObject>, ToPyObject, and FromPyObject for PathBuf (and maybe Path, if you can make it work).

I think it will be better to implement those three traits on OsStr and OsString, because that's what the this work is really about: converting between Python's magic strings and Rust's opaque OS strings.
Path and PathBuf can just redirect to the implementations on OsStr and OsString.

I think it will be better to implement those three traits on OsStr and OsString, because that's what the this work is really about: converting between Python's magic strings and Rust's opaque OS strings.
Path and PathBuf can just redirect to the implementations on OsStr and OsString.

That sounds sensible to me! If you're looking at string types, it could be worth assessing if CStr and CString should also be supported. I think Python allows null bytes in the middle of its strings so definitely from-Python would be fallible for those.

That sounds sensible to me! If you're looking at string types, it could be worth assessing if CStr and CString should also be supported. I think Python allows null bytes in the middle of its strings so definitely from-Python would be fallible for those.

Should the conversion functions from/to OsStr/Cstr go onto the PyString struct? It would get four new methods:

from_osstr
to_osstr
from_cstr
to_cstr

The alternative would be to create new modules types/cstr.rs and types/osstr.rs, and implement the conversions there

Should the conversion functions from/to OsStr/Cstr go onto the PyString struct? It would get four new methods:

from_osstr
to_osstr
from_cstr
to_cstr

The alternative would be to create new modules types/cstr.rs and types/osstr.rs, and implement the conversions there

I would suggest avoiding new methods on PyString if we can - as much as possible the methods on the python-native types are just wrappers around the underlying Python C API.
Is there a reason the traits above don't provide enough functionality for what you need? The traits are all we need for #[pyfunction] / #[pymethods] etc.

I would suggest avoiding new methods on PyString if we can - as much as possible the methods on the python-native types are just wrappers around the underlying Python C API.
Is there a reason the traits above don't provide enough functionality for what you need? The traits are all we need for #[pyfunction] / #[pymethods] etc.

I was just asking what you preferred, I'm fine with both.
In any case, I wrote the trait implementations for OsStr/OsString: https://github.com/kangalioo/pyo3/blob/bbc578fda767134ff678c1ebc62eae5e0e756cb2/src/types/osstr.rs. I'd greatly appreciate if you could check it out to make sure I didn't do anything totally stupid. Commenst with // HELP mark places where I was unsure if I was doing the right thing.

I was just asking what you preferred, I'm fine with both.
In any case, I wrote the trait implementations for OsStr/OsString: https://github.com/kangalioo/pyo3/blob/bbc578fda767134ff678c1ebc62eae5e0e756cb2/src/types/osstr.rs. I'd greatly appreciate if you could check it out to make sure I didn't do anything totally stupid. Commenst with // HELP mark places where I was unsure if I was doing the right thing.

👍 totally makes sense - nice work and thanks for the PR; I'll do my best to make time to review it as soon as I can.

👍 totally makes sense - nice work and thanks for the PR; I'll do my best to make time to review it as soon as I can.

Closed by #1379 . Thanks again for the PR.

authors: davidhewitt kangalioo


text:
Python2 support

I’d like to drop python2 support

I don't have a huge problem with this, but I will say that as a library developer who is intending to support Python 2.7 for some time longer, it will make it harder to write a Rust backend for my libraries that support both 2 and 3.
It might be a good idea to get a stable API to enable polyglot Rust for those still supporting Python 2.7 for some time - e.g. if you want to write a Rust backend for your Python 2/3 library, pinning the 2.7 version against an old PyO3 build will still work with minimal code changes, even if you can only use a subset of all pyo3 features.

I happen to work in an industry (vfx for film/tv) in which python is ubiquitous (its embedded in a ton of commercial apps), but which has not updated to python3.x yet (vendors are targeting 2020). This would rule out Pyo3 for us (which is a shame). I suppose that it is good to know now.

@jlgerber Well, luckily, support for Python 2 in the general ecosystem is waning every day. It's already past the point where you should be able to go to your management and say, "Tick tock, the writing is on the wall". The more things like PyO3 drop support for Python 2, the easier it will be to make the case that you need to be moving to Python 3 now.

@pganssle - As i said, our timetable is driven by commercial vendor integration of python3, which is slated for 2020 based on the vfx open platform. Until applications like Maya, Houdini, and Nuke all support python3, its moot.

Well, point is that this sort of thing isn't going to get any easier. It's ridiculous that none of those applications read the writing on the wall years ago and added Python 3 support. Even "we're targeting 2020" is basically saying, "We are going to wait until the last possible minute". Making it clear that the official EOL is not the only thing to worry about will help people prioritize this.
That said, if you're in an environment where you can't even use Python 3, it's shocking to me that you would be allowed to use Rust. You probably don't want to get your Rust infrastructure tied up with all your legacy Python code anyway.

python2 is 16% of usage on https://www.jetbrains.com/research/python-developers-survey-2018/.
How about removing it now? I can do a pull request if people are ok.

@ijl I think after 0.6 would be a good time to remove python 2 support. But note that it's not as trivial as deleting a bunch of files. You need unify num-common.rs and num3.rs, remove the Py_3 cfg flag, change the build script, etc.

Sorely disappointed to see this. Python 2.x is not going away any time soon, regardless of how loud people may shout and scream that it is and will magically stop existing on some particular day, despite the reality of the free licenses covering the millions of lines of self-supported code in the 2.x ecosystem. This is a weird and deeply embarassing meme in the contemporary Python community that does not match whatsoever the behaviour of any other software in the history of computing.
There will be Python 2.x machines around in 10 years, and there will always be customers with applications so large and under-budgeted they could never have possibly moved.  I hope the maintainability gains from dropping 2.x were profound and worth breaking compatibility for, as it severely limits the dependability of Rust for use in a commercial context: not just technically, but culturally. C++ is good enough, and that ecosystem always understood compatibility as an integral part of craftsmanship.

@dw I'm not particularly happy about it since it will make it much harder for me to add a Rust backend to my libraries that still support Python 2, but it's a bit unfair to imagine that this is part of some conspiracy to wish away Python 2. I think most of the maintainers of this library just don't see Python 2 as a sufficiently important platform to support at the moment that it justifies the maintenance burden.
If you look at the library before this was merged, it was not actually written in a way that makes maintaining Python 2 support particularly easy, and it would be a decently large effort to actually unify the Python 2 and Python 3 codebases, which is a lot of burden, particularly when the kind of people who can use Rust (I think specifically nightly Rust, or if we're ready for stable then a very recent version) are not generally the kind of people who cannot use Python 3.
If you think it's worth the effort, forking this project to maintain Python 2 support is definitely an option. PyO3 is itself a fork of rust-cpython. If there's commercial interest in this, then you may even be able to get someone to pay to do it!

The size of the removal diff is definitely quite surprising. From previous experience porting from 2.x to 3.x, the C API barely changed, and only a tiny handful of (C) macros were generally necessary to paper over the differences. So perhaps the previous approach taken in this project was more verbose than necessary and was a genuine source of maintainability problems.
Would there be interest in returning 2.x support if it could be done in a smaller amount of code? Really outside of module initialization and Unicode the 2.x/3.x APIs are highly compatible..

I can recommend reading https://python3statement.org/ which explains the reasons for removing python 2 support much better than I could

Would there be interest in returning 2.x support if it could be done in a smaller amount of code? Really outside of module initialization and Unicode the 2.x/3.x APIs are highly compatible..

No. Also for pyo3 there's a much bigger difference than for other library since the goal is to support basically all of the c api, we can't use c macros in rust and need to do our own linking logic. However as @pganssle said you're free to fork pyo3.

the goal is to support basically all of the c api

This is easily possible without breaking backwards compatibility. I hope you realize the C API has continued to vary quite rapidly within the 3.x series. Perhaps the goal is to only fully support the daily CPython master branch?
rust-cpython serves the desired purpose without forcing any artificial tradeoffs, so forking won't be necessary.

Is there any statistic about how many people use Python2?
I'm basically a Rust programmer and really not familiar with the nature of the Python community.
So if one say 'There will be Python 2.x machines around in 10 years...', I can't judge it's true or not from my knowledge.

python2.7 EOL is January 1st 2020

So if one say 'There will be Python 2.x machines around in 10 years...', I can't judge it's true or not from my knowledge.

It's certainly true, in the same way that 'There will be Windows XP machines around in 10 years' is true: outdated, unmaintained legacy versions keep being used (and will be exploitable) for various reasons. But in the interest of putting volunteer effort into what matters most, it is not worth supporting IMO.
Especially since I assume the cross section of legacy Python and Rust is pretty small, Rust 1.0 having been released 7 years after Python 3.0.

According to PyPI BigQuery, 53% of all downloads yesterday that included an identifiable runtime version were downloaded by some version of pip or setuptools running on Python 2.x. That is 54.9 million packages downloaded by software that allegedly will cease to exist in 185 days time. In practical terms the EOL date is meaningless, as it bears no relationship with the longevity of Python 2.x in the real world.
The "real" EOL date is much further away -- and at least not before the last long term support releases expire for Linux distributions presently shipping it. For example, Ubuntu 18.04 which includes support for Python 2 does not reach EOL until April 2028.

supporting old code if huge burden for maintainers, what is the problem with the fork?

software that allegedly will cease to exist in 185 days time.

I'm not sure why you keep pushing that strawman: nobody says that Python 2 and its packages will be purged from existence upon EOL. Of course they won't. Likewise we're not talking about purging older versions of PyO3 that did support Python 2 from existence. But it is very reasonable, and common, for packages to stop supporting Python 2 at some point.

Ubuntu 18.04 which includes support for Python 2 does not reach EOL until April 2028.

The relevant date, i.e. end of publicly available support, is 2023.

@ fafhrd91 thanks for your feedback. I'll consider a "PyO23" if rust-cpython is eventually no longer sufficient.

so you dont even use pyo3?

@fafhrd91 I found this ticket in the process of figuring out whether I wanted to use PyO3 :)  It is obviously more popular and the design looks nicer, but broken compatibility is a showstopper. Thanks for your work

authors: birkenfeld dw fafhrd91 ijl jlgerber kngwyu konstin pganssle


text:
add back RL

What does this PR do?
Adding back RL
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

later this will be merged without squash eventually in the command line to keep the contributions...

Hello @Borda! Thanks for updating this PR.

In the file pl_bolts/models/rl/common/cli.py:

Line 30:121: E501 line too long (121 > 120 characters)

In the file tests/datamodules/test_experience_sources.py:

Line 313:30: W504 line break after binary operator
Line 314:52: W504 line break after binary operator


text:
trainer.test after fp16 training with apex

Summary
In the current huggingface examples/seq2seq/finetune.py,
trainer.test fails in fp16 mode with torch 1.5.1.

Nowhere in the huggingface code is model.half called.
Models maybe saved to disk in either fp16 or fp32 format, but since we are resuming from a pl checkpoint, I think pl is controlling the saving and loading here.
Bonus: this test will hang if you pass gpus=2 by switching this line.

To reproduce
You must be on a machine with cuda installed
git clone git@github.com:huggingface/transformers.git
cd transformers
pip install -e .
pip install -e .[examples]  # installs pytorch-lightning==0.8.5
git checkout broken-fp16-test
RUN_SLOW=1 USE_CUDA=1 pytest examples/seq2seq/test_bash_script.py

Small Traceback
 RuntimeError: Found param model.model.shared.weight with type torch.cuda.HalfTensor, expected torch.cuda.FloatTensor.
When using amp.initialize, you do not need to call .half() on your model
before passing it, no matter what optimization level you choose.

Full Traceback
(failure from this line)
============================= test session starts ==============================
platform linux -- Python 3.7.4, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
rootdir: /home/shleifer/transformers_fork, inifile: pytest.ini
plugins: forked-1.1.3, xdist-1.31.0, requests-mock-1.8.0
collected 1 item

examples/seq2seq/test_bash_script.py Selected optimization level O2:  FP16 training with FP32 batchnorm and FP32 master weights.

Defaults for this optimization level are:
enabled                : True
opt_level              : O2
cast_model_type        : torch.float16
patch_torch_functions  : False
keep_batchnorm_fp32    : True
master_weights         : True
loss_scale             : dynamic
Processing user overrides (additional kwargs that are not None)...
After processing overrides, optimization options are:
enabled                : True
opt_level              : O2
cast_model_type        : torch.float16
patch_torch_functions  : False
keep_batchnorm_fp32    : True
master_weights         : True
loss_scale             : dynamic

Validation sanity check: 100%|██████████| 2/2 [00:00<00:00,  2.76it/s]

Training: 0it [00:00, ?it/s]
Training:   0%|          | 0/125 [00:00<?, ?it/s]
Epoch 1:   0%|          | 0/125 [00:00<?, ?it/s] Gradient overflow.  Skipping step, loss scaler 0 reducing loss scale to 32768.0

Epoch 1:   1%|          | 1/125 [00:00<00:10, 11.29it/s, loss=12.438, v_num=219]
...
Epoch 2:  74%|███████▍  | 93/125 [00:14<00:04,  6.55it/s, loss=12.427, v_num=219]
# DONE TRAINING
Selected optimization level O2:  FP16 training with FP32 batchnorm and FP32 master weights.

Defaults for this optimization level are:
enabled                : True
opt_level              : O2
cast_model_type        : torch.float16
patch_torch_functions  : False
keep_batchnorm_fp32    : True
master_weights         : True
loss_scale             : dynamic
Processing user overrides (additional kwargs that are not None)...
After processing overrides, optimization options are:
enabled                : True
opt_level              : O2
cast_model_type        : torch.float16
patch_torch_functions  : False
keep_batchnorm_fp32    : True
master_weights         : True
loss_scale             : dynamic
F

=================================== FAILURES ===================================
______________________ test_train_mbart_cc25_enro_script _______________________

    @slow
    @pytest.mark.skipif(not CUDA_AVAILABLE, reason="too slow to run on CPU")
    def test_train_mbart_cc25_enro_script():
        data_dir = "examples/seq2seq/test_data/wmt_en_ro"
        env_vars_to_replace = {
            "$MAX_LEN": 200,
            "$BS": 4,
            "$GAS": 1,
            "$ENRO_DIR": data_dir,
            "facebook/mbart-large-cc25": MBART_TINY,
        }

        # Clean up bash script
        bash_script = Path("examples/seq2seq/train_mbart_cc25_enro.sh").open().read().split("finetune.py")[1].strip()
        bash_script = bash_script.replace("\\\n", "").strip().replace("$@", "")
        for k, v in env_vars_to_replace.items():
            bash_script = bash_script.replace(k, str(v))
        output_dir = tempfile.mkdtemp(prefix="output")

        if CUDA_AVAILABLE:
            gpus = 1  # torch.cuda.device_count()
        else:
            bash_script = bash_script.replace("--fp16", "")
            gpus = 0

        testargs = (
            ["finetune.py"]
            + bash_script.split()
            + [f"--output_dir={output_dir}", f"--gpus={gpus}", "--learning_rate=3e-1"]
        )
        with patch.object(sys, "argv", testargs):
            parser = argparse.ArgumentParser()
            parser = pl.Trainer.add_argparse_args(parser)
            parser = SummarizationModule.add_model_specific_args(parser, os.getcwd())
            args = parser.parse_args()
            # assert args.gpus == gpus THIS BREAKS
            # args.gpus = gpus
>           model = main(args)

examples/seq2seq/test_bash_script.py:71:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
examples/seq2seq/finetune.py:392: in main
    trainer.test()
../miniconda3/envs/nb/lib/python3.7/site-packages/pytorch_lightning/trainer/trainer.py:1281: in test
    results = self.__test_using_best_weights(ckpt_path, test_dataloaders)
../miniconda3/envs/nb/lib/python3.7/site-packages/pytorch_lightning/trainer/trainer.py:1321: in __test_using_best_weights
    results = self.fit(model)
../miniconda3/envs/nb/lib/python3.7/site-packages/pytorch_lightning/trainer/trainer.py:1003: in fit
    results = self.single_gpu_train(model)
../miniconda3/envs/nb/lib/python3.7/site-packages/pytorch_lightning/trainer/distrib_parts.py:182: in single_gpu_train
    model, optimizers = model.configure_apex(amp, model, self.optimizers, self.amp_level)
../miniconda3/envs/nb/lib/python3.7/site-packages/pytorch_lightning/core/lightning.py:1006: in configure_apex
    model, optimizers = amp.initialize(model, optimizers, opt_level=amp_level)
../miniconda3/envs/nb/lib/python3.7/site-packages/apex/amp/frontend.py:358: in initialize
    return _initialize(models, optimizers, _amp_state.opt_properties, num_losses, cast_model_outputs)
../miniconda3/envs/nb/lib/python3.7/site-packages/apex/amp/_initialize.py:171: in _initialize
    check_params_fp32(models)
../miniconda3/envs/nb/lib/python3.7/site-packages/apex/amp/_initialize.py:87: in check_params_fp32
    name, param.type()))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

msg = 'Found param model.model.shared.weight with type torch.cuda.HalfTensor, expected torch.cuda.FloatTensor.\nWhen using a...alize, you do not need to call .half() on your model\nbefore passing it, no matter what optimization level you choose.'

    def warn_or_err(msg):
        if _amp_state.hard_override:
            print("Warning:  " + msg)
        else:
>           raise RuntimeError(msg)
E           RuntimeError: Found param model.model.shared.weight with type torch.cuda.HalfTensor, expected torch.cuda.FloatTensor.
E           When using amp.initialize, you do not need to call .half() on your model
E           before passing it, no matter what optimization level you choose.

../miniconda3/envs/nb/lib/python3.7/site-packages/apex/amp/_amp_state.py:32: RuntimeError
=========================== short test summary info ============================
FAILED examples/seq2seq/test_bash_script.py::test_train_mbart_cc25_enro_script
============================== 1 failed in 38.75s ==============================

There's also another related issue I've been getting that may be related. I notice Lightning switched from O1 to O2 AMP level between versions 0.7 to 0.8.5. This can break models trained on older versions.

@nateraw to verify if this is still an issue,

@calclavia @sshleifer mind share PT version you were using and eventually test it the issue is still presented on master?

It is broken in a new way -- it errors and then hangs. The error is my code but it shouldn't hang. Both 0.8.5 and 0.9.0.
The code above takes about 3 minutes to run.
My setup is broken on master with some wandb error that I do not have time to debug at the moment.
But if you run these instructions or my command in #3597 you will be able to see all the errors.

@sshleifer this is with Apex, right? Same issue with native amp?

Different issue. Also fails in fp32.

It's failing earlier than it used to fail so IDK if this is fixed.

ok, looking at this tomorrow ahead of 1.0 this week.

@sshleifer Here's a notebook that shows trainer.test on native 16 bit precision. I use the self.write_prediction feature as well to write the test predictions to file.
Here's what I do in the notebook:

Train on 1 GPU, 16 bit precision
Test best model, write predictions to predictions.pt file.
Reload checkpoint from steps 1 and 2 and re-run test loop, this time saving to predictions_new.pt
Compare predictions.pt and predictions_new.pt to make sure they're the same.

@nateraw anything left todo here?

This can be closed. I've shared this example with Sam, which I have shown works with Transformers on both native fp16 and apex for multi-gpu predictions with pl.Trainer.test.

authors: Borda calclavia edenlightning nateraw sshleifer williamFalcon

repo: PyTorchLightning/pytorch-lightning


text:
Attach version_ to checkpoint path only if version is int

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
N/A Did you make sure to update the docs?
[x] Did you write any new necessary tests?
[x] If you made a notable change (that affects users), did you update the CHANGELOG?

What does this PR do?
Fixes #1659.
We should only attach the prefix version_ to the default checkpoint path when the logger's version is an integer.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @yukw777! Thanks for opening this PR.

In the file tests/callbacks/test_callbacks.py:

Line 263:111: E501 line too long (116 > 110 characters)

Do see the Hitchhiker's guide to code style


text:
enable testing DDP examples

What does this PR do?
enable DDP test for example
Resolves #4694
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

seems that the DDP is hanging...

@Borda by how much will this increase drone test runtime?

I think, we should only run this nightly with a cron job or so. Because when we run this more often, we will significantly slow down the development process, as we already experience some bottlenecks with iron and then it would pile up even more.

I think, we should only run this nightly with a cron job or so. Because when we run this more often, we will significantly slow down the development process, as we already experience some bottlenecks with iron and then it would pile up even more.

well then you can say the same for each test we run, we can run a test just nightly :]
if you want some simplification we shall skip all code testing for pure doc changes...

I think, we should only run this nightly with a cron job or so. Because when we run this more often, we will significantly slow down the development process, as we already experience some bottlenecks with iron and then it would pile up even more.

well then you can say the same for each test we run, we can run a test just nightly :]
if we want some simplification we shall skip all code testing for pure doc changes...

I don't think so. There's a difference in running unit tests and examples (which are basically some kind of integration/functionality testing).

I very much agree with Justus on this one

I don't think so. There's a difference in running unit tests and examples (which are basically some kind of integration/functionality testing).

so you say we shall drop the test and simply call the script in a command-line as another entry after python -m pytest

@justusschock @awaelchli this is what you had in mind b26adda?

it looks like this would still run on every commit?

it looks like this would still run on every commit/PR?

yes, or what is your suggestion, just at midnight, but then we do not know what PR breaks it... (well, stop it which would break it...)

@justusschock @awaelchli so whall we keep this DDP testing or just drop it to run it only on master?

running only on master would be wiser I think, given that some of these examples run for several seconds. Or you could also group them with the other "special tests" that we have.

authors: Borda awaelchli justusschock


text:
Add files via upload

latest changes (images)

Closing as we already merged @TaeBlack's changes.

authors: TaeBlack krook

repo: Pyrrha-Platform/Pyrrha-Website


text:
Add support to specify table class with attr_list

The bootstrap 3 framework has support for tables, but requires various classes be set on the
 element: e.g.
.
If I try to do this with the attr_list and tables extensions, a new empty row is created and the class is applied to the first  element in that row.
For example...
| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 2 is      | centered      |   $12 |
| zebra stripes | are neat      |    $1 |
{: .table table-bordered .table-striped}

...outputs...

      Tables
      Are
      Cool

      col 2 is
      centered
      $12

      zebra stripes
      are neat
      $1

Since
 is a block level element, I would expect the attributes to be applied to there; I certainly don't expect an extra empty row.

just add a default css tag.  Pretty simple.  class=markdown-table
problem solved.

just add a default css tag. Pretty simple. class=markdown-table
problem solved.

Can you please elaborate on how and where can I add a default class to generated HTML elements? I couldn't find any such property or attribute in the pelicanconf.py, nor in the theme.

For anyone that's looking for a quick and dirty solution to this, I have implemented an extension for myself which mirrors the Kramdown syntax (because I am having to render markdown that's been written previously for Jekyll).
Syntax is:
for lists
{:.tabular-list}
- list item
- list item

for tables
{:.my-table}
| header | header |
| --- | --- |
| etc

Caveat: I wrote this in about an hour, as my first ever attempt at a markdown extension. It works for what I needed it for, but I have not tested it properly by any means.  YMMV
import markdown
import re
from markdown.extensions import attr_list

def makeExtension(**kwargs):
    return ImpliedAttrListExtension(**kwargs)

class ImpliedAttrListExtension(markdown.Extension):
    """Extension for attatching `attr_list` entries to implied elements.  Specifically: lists and tables"""

    def extendMarkdown(self, md: markdown.Markdown, *args, **kwargs):
        md.preprocessors.register(ImpliedAttrListPreprocessor(md), "implied_attr_list", 100)
        md.treeprocessors.register(ImpliedAttrListTreeprocessor(md), 'implied_attr_list', 100)
        md.registerExtension(self)

class ImpliedAttrListPreprocessor(markdown.preprocessors.Preprocessor):

    def run(self, lines):
        """
        Insert a blank line in between the declaration of the attr_list and the thing that it applies to
        This will allow it to render the list normally.  The attr_list will get rendered into the text of a paragraph
        tag which the Treeprocessor below will handle
        """

        new_lines = []
        for line in lines:
            new_lines.append(line)
            if re.fullmatch(ImpliedAttrListTreeprocessor.BASE_RE, line):
                new_lines.append("")
        return new_lines

class ImpliedAttrListTreeprocessor(attr_list.AttrListTreeprocessor):

    def run(self, doc):
        """
        Iterate through the doc, locating
 tags that contain ONLY the syntax for attr_lists.

        Once one is found, the value is applied to the next element in the iteration of the doc, and the

 tag is removed

        :param doc:
        :return:
        """
        holdover = None
        removes = []
        for elem in doc.iter():
            if holdover is not None:
                self.assign_attrs(elem, holdover)
                holdover = None

            if elem.tag in ["p"] and elem.text is not None:
                m = re.fullmatch(self.BASE_RE, elem.text)
                if m:
                    holdover = m.group(1)
                    removes.append(elem)

        if len(removes) > 0:
            parent_map = {c: p for p in doc.iter() for c in p}
            for r in removes:
                parent = parent_map[r]
                parent.remove(r)

authors: Goddard jonblack prahladyeri richard-jones

repo: Python-Markdown/markdown


text:
Fixed links to source code on GitHub from the documentation

With the current version, if you open e.g. this page, the ‹› links on the right side of the page will point to URLs like https://github.com/Python-Markdown/markdown/tree/3.6//home/runner/work/markdown/markdown/md/markdown/blockprocessors.py which are wrong (note the /home/runner/work/ part).
This commit fixes them by replacing filepath with relative_filepath. It seems to work locally for me, but needs to be tested on our main documentation website.

Thanks for this. I noticed the issue and hadn't yet had the opportunity to track it down.

I just did a manual deploy to update the documentation with the current master and this has resolved the issue. 👍


text:
Making the footer attractive and linking its items

I will assign you this issue when DCP will start from 10th July.

Okay @QAZIMAAZARSHAD sir

I would like to work on footer. please assign this to me @QAZIMAAZARSHAD

I would like to work on footer. please assign this to me @QAZIMAAZARSHAD

Look for some other issues. This will be assigned to @aakankshabhende.

Please assign this issue to me under DCP.

I would like to work on this issue under DCP.

I would like to work on this issue under DCP.

Already assigned look for some other issues.

Can you please send social links of Apni Dukaan @QAZIMAAZARSHAD sir as I want to link them in footer.

@aakankshabhende this is just a demo website.
Social links do not exist, just link them to social pages.

Hi can i contribute to this if no one was assigned?

Please assign this issue to someone else @QAZIMAAZARSHAD sir

What happened @aakankshabhende you had already made the PR?

repo: QAZIMAAZARSHAD/Apni-Dukaan


text:
Changed Footer Copyright year

Issue Number
fixes #248
Describe the changes you've made
Hey @QAZIMAAZARSHAD
I have changed the footer copyright year using Js,
Please check and update.
Thanks
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Additional context (OPTIONAL)
Add any other context or screenshots about the feature request here.
Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.
How someone can test your code?
Checklist

[x] I have added my name in the contributors list at the end of README.md file.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] The title of my pull request is a short description of the requested changes.
[x] Open Source Program names(OPTIONAL: If you participated in any open-source program then please mention the program name here)

Review your changes.
Can't accept this PR.
Update, fetch upstream then make a new PR.
Only necessary changes should highlight.

repo: QAZIMAAZARSHAD/Movie-Streaming-Website


text:
make release throws an error

make release throws an error:
src/Composer.tsx(13,28): error TS2307: Cannot find module '@jupyter_vre/core' or its corresponding type declarations.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! jlpm run build stderr:
error Command failed with exit code 1.
lerna ERR! jlpm run build exited 1 in '@jupyter_vre/faicells-composer'
lerna WARN complete Waiting for 2 child processes to exit. CTRL-C to exit immediately.
make: *** [Makefile:25: build-frontend] Error 1

To build locally you may use: https://github.com/QCDIS/NaaVRE/wiki/Development

repo: QCDIS/NaaVRE


text:
Add formatting to the CI

As discussed in this MR: https://github.com/QEDjl-project/QEDbase.jl/pull/13 we should include a linter stage to the CI.

done in #11


text:
pt转onnx 的问题

大佬您好，我想问一个关于转模型的问题，由于官方的yolov7 转onnx的参数选择太多，并且没有给无后处理的onnxdemo，我想问您 转onnx的时的指令是什么 。我在转模型后  不能把onnx转为ncnn

I've used a ready-made model by Xiang Shin Wuu. You might take a look here

thanks, I got it done

You're welcome

authors: Qengineering sssssshf


text:
How to do anchor links within a single page

Hello, really enjoy docsify. Is there any way to be to have anchor links within a single page?
My use case is that I generate markdown API documentation automatically from JSDoc, and would like to be able to just add that as a single page within docsify project / site. The generated markdown automatically generates a "table of contents" that's a listing of all functions and classes of all the API within the project at the top of the file, and the table of contents links to the actual documentation for those that are elsewhere later in the file.
So for example it may end up being something like:
MyClass
...

### MyClass

I can't seem to get this to work even if I try modifying the anchor links or setting data-id properties.
Is this possible to accomplish using docsify somehow (even with some hacking or manual manipulation of the generated markdown).
If not perhaps point me in the right direction and I can try and do a PR.
Thanks

You need generate markdown syntax. Such as
[MyClass](#MyClass)

It will not be compiled if it is HTML.

Hmm maybe I didn't explain the issue correctly. It seems that docsify actually parses the file and sets the links to non-existent / invalid path. Lets say you have markdown file api.md and in it we have something like this:
See documentation for [MyClass](#myclass)

And this should jump to elsewhere later in api.md. Docsify seems to create a link http://localhost:3000/#/?id=myclass when the correct link is http://localhost:3000/#/api?id=myclass. I am trying to see if there is a workaround so it actually jump within the actual page, rather than trying to look for a path / route within docsify app. Hope this helps.

It really is a bug. Do you have time to fix it?

From some debugging it seems that this fixes it, but I am not sure about the complete effect my changes...?
function toURL (path, params) {
  var inline = path[0] === '#';
  var route = parse(replaceSlug(path));

  route.query = merge({}, route.query, params);
  path = route.path + stringifyQuery(route.query);
  path = path.replace(/\.md(\?)|\.md$/, '$1');

  if (inline) path = currentPath + path;

  return cleanPath('#/' + path)
}

Basically we detect that the path / href starts with '#' indicating usage of inline anchor / href link like
[MyClass](#myclass)

It will generate a link http://localhost:3000/#/api?id=myclass
And then later in file if we have

### MyClass

It will correctly link and jump to that anchor. Not sure if this is the correct approach.

Yes, I think it is right.

It'd be neat to be able to apply this mapping to regular  tags too, because there are some cases where it is not possible to put the a[]() syntax.
For example, I want to make some tables, but GitHub-flavored markdown does not support cells with multi-line content, so I need to use
 and due to the nesting, I can not place markdown inside the  elements. But I can only place  elements.

authors: QingWei-Li bojand trusktr

repo: QingWei-Li/docsify


text:
Add minimal working code expample in experiment API docs

Summary
This change adds minimal working code examples to the API pages for each experiment,especially in characterizaion experiments. The minimal working code example is a code snippet which users can copy and paste to run the experiment.
Details and comments

This change solves the issue#1238 (See also the issue#1221).
In the API pages, the documentation for each experiment has been updated with its code example. Users are required to specify a backend in the code example. As a default, the backend is a simulator such as GenericBackendV2(num_qubits=27).
In some experiments,
CorrelatedReadoutError
ResonatorSpectroscopy
CrossResonanceHamiltonian and
EchoedCrossResonanceHamiltonian,
the backend is an IBM Quantum real device due to the backend.defaults() dependence of the code example.
In these cases, the code example explicitly imports the module qiskit-ibm-provider in order to retrieve the job on IBM Quantum real devices.
Therefore, requirements-dev.txt has been updated to add the dependency on qiskit-ibm-provider for running tests and building documentation.

PR checklist (template)

[x] I have read the contributing guide CONTRIBUTING.md.
[ ] I have added the tests to cover my changes.
[x] I have updated the documentation accordingly.
[x] I have added a release note file using reno if this change needs to be documented in the release notes.

PR checklist (additional in CONTRIBUTING.md)

[x] The code follows the code style of the project and successfully passes the tests.
[x] The API documentation has been updated accordingly.
[x] You have updated the relevant documentation or written new docs. In case the PR needs
to be merged without delay (e.g. for a high priority fix), open an issue for updating
or adding the documentation later.
[] You've added tests that cover the changes you've made, if relevant.
[] If your change has an end user facing impact (new feature, deprecation, removal,
etc.), you've added or updated a reno release note for that change and tagged the PR
for the changelog.
[x] If your code requires a change to dependencies, you've updated the corresponding
requirements file: requirements.txt for core dependencies,
requirements-extras.txt for dependencies for optional features, and requirements-dev.txt
for dependencies required for running tests and building documentation.

 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.

@coruscating, thank you for your review and suggestion, . The branch issue-#1238 has been updated.

authors: CLAassistant Naohnakazawa

repo: Qiskit-Extensions/qiskit-experiments


text:
Add static list of curated syllabi to the Classroom view

We need to add the curated syllabi to the user account Classroom view:

use content from @pandasa123
use SyllabusCard components

Good afternoon Team. I was wondering if this is the design you expect to see from this issue. I am a bit uncertain of what to do after filling up the information provided by Sanket, as there was no visual attachments to the issue. I asked Eddy to invite me to the Curated Syllabus project on Figma since I didn't have previous access to it.
If this is the final design, does anyone know where I could find a sample of the final cards? Anywhere they might have been used previously, or a similar version of them.
Thank you :)

Hey @mariacloehb, sorry about that. Here's how it looks on the Qiskit.org (and the expected order)
The items in here are placeholders:

Merged, thank you @mariacloehb

authors: mariacloehb pandasa123 techtolentino

repo: Qiskit/platypus


text:
[WIP] Add warning if backend is paused

Summary
Fixes #99
Details and comments

Pull Request Test Coverage Report for Build 2254276896

-2 of 3 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.3%) to 29.783%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/ibm_backend.py
1
3
33.33%

Totals

Change from base Build 2235600754:
-3.3%

Covered Lines:
1647

Relevant Lines:
5530

💛  - Coveralls

Pull Request Test Coverage Report for Build 2254276896

1 of 3 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.3%) to 29.783%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/ibm_backend.py
1
3
33.33%

Totals

Change from base Build 2235600754:
-3.3%

Covered Lines:
1647

Relevant Lines:
5530

💛  - Coveralls

repo: Qiskit/qiskit-ibm-provider


text:
Gibbs states preparation framework; QITE-based implementation.

Summary
Closes: #7480
A framework for preparing Gibbs quantum states is introduced. It will be used by the Quantum Boltzmann Machine feature in Qiskit ML (to be implemented) and possibly other algorithms in various contexts.
This contribution is based on the following paper (see section 3.1): https://link.springer.com/content/pdf/10.1007/s42484-020-00033-7.pdf.
This contribution depends on the following PR: #7349.
Details and comments

An interface for Gibbs state preparation is introduced and implemented for the case of Gibbs state preparation using Quantum Imaginary Time Evolution.
The Gibbs state builder class  constructs a default ansatz and initial parameters accepted by the algorithm.
In case a custom ansatz and initial parameters are provided by the user, tools for validating their quality are provided.
The result of the algorithm is an instance of a GibbsState class provided in this contribution. It contains a final quantum state (a Gibbs state) and relevant metadata.
A method for calculating gradients of Gibbs states is also implemented there.

TODO:

[ ] Add unit tests that actually use the VarQite algorithm from #7349 once it is completed.
[ ] Add more unit test cases for computing gradients of Gibbs states.
[ ] Fix all pylint issues.
[ ] Add packages docs.

UML diagram of this feature:
TODO - add updated version

Pull Request Test Coverage Report for Build 1663756843

53 of 114 (46.49%)  changed or added relevant lines in 5 files are covered.
6 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.07%) to 83.049%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/algorithms/gibbs_state_preparation/gibbs_state.py
35
37
94.59%

qiskit/algorithms/gibbs_state_preparation/ansatz_mes_validator.py
18
21
85.71%

qiskit/algorithms/gibbs_state_preparation/gibbs_state_builder.py
0
9
0.0%

qiskit/algorithms/gibbs_state_preparation/default_ansatz_builder.py
0
17
0.0%

qiskit/algorithms/gibbs_state_preparation/qite_gibbs_state_builder.py
0
30
0.0%

Files with Coverage Reduction
New Missed Lines
%

qiskit/circuit/controlflow/if_else.py
1
96.24%

qiskit/extensions/quantum_initializer/uc.py
2
88.65%

qiskit/pulse/library/waveform.py
3
89.36%

Totals

Change from base Build 1655633790:
-0.07%

Covered Lines:
51996

Relevant Lines:
62609

💛  - Coveralls

Comment so that @dlasecki can add me to the reviewer list?

authors: Zoufalc coveralls dlasecki

repo: Qiskit/qiskit-terra


text:
update-ecr-doc

Summary
Fix definition of ECRGate .. it doesn't implement RZX(pi/2) as pointed out in #9234
Fixes #9234

Pull Request Test Coverage Report for Build 3603413405

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.585%

Totals

Change from base Build 3602972482:
0.0%

Covered Lines:
63085

Relevant Lines:
74582

💛  - Coveralls

authors: ajavadia coveralls


text:
Question regarding QFT

Description

Hi, I am now using QISKit to realize quantum fourier transform. I run the code provided by you in this link.
The input state is set to 000 by default. Is there any methods to change the input, for example to 001?
Could you please answer my question? Thank you so much!
Your Environment

QISKit version: 0.6.0
Python version: 3.6

Hi @yangjy0826
To change the initial qubit from 0 to 1 you can apply the X gate.
In the 4th cell of the notebook the statement q = QuantumRegister(3) creates a quantum register with 3 qubits all in state 0.
To change one qubit from 0 to 1 you can apply X to that particular qubit (using the qubit index) right after you create the circuit. The 4th cell becomes:
q = QuantumRegister(3)
c = ClassicalRegister(3)
qft3 = QuantumCircuit(q, c)

qft3.x(q[0]) # changes the first qubit (with index 0 ) q[0] to 1

input_state(qft3, q, 3)
qft(qft3, q, 3)
for i in range(3):
    qft3.measure(q[i], c[i])
print(qft3.qasm())

Oh I understand! That's smart. Thank you so much! But I still have a question: when you design this package, why dont't you consider to design a function to set the initial value?

because that is really user code to make the state to have the Fourier transform applied to.  I think this should be left to the user but the user can use the initializer method to make the state they want.

OK, thanks!

authors: jaygambetta muneerqu yangjy0826

repo: Qiskit/qiskit-tutorial


text:
[wip] Remove Qiskit 0.45 docs from release notes

See https://github.com/Qiskit/qiskit/pull/11840 for the context.

Turns out this wasn't actually necessary for stable/0.46 because it didn't set the branch option to use stable/0.45.

repo: Qiskit/qiskit


text:
fix indentation in XXPlusYYGate docstring

Summary
The matrix is supposed to be part of the note.
Details and comments

Pull Request Test Coverage Report for Build 8994166620
Details

0 of 0   changed or added relevant lines in 0 files are covered.
15 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.003%) to 89.633%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
3
92.37%

crates/qasm2/src/parse.rs
12
96.69%

Totals

Change from base Build 8993960642:
-0.003%

Covered Lines:
62261

Relevant Lines:
69462

💛  - Coveralls

authors: coveralls kevinsung