Dependency of type 'PSGalleryNuget' without specifying version throw error

During testing with PSDepend today I ran into an issue when trying to install a module from a MyGet feed using the 'PSGalleryNuget' dependency type. The module was not installed, and "Unable to find package 'psdepend'. Existing packages must be restored before performing an install or update." was output to the console.
The problem only showed when not specifying a version in the build.requirements.psd1.
Steps to reproduce (on my system atleast):

Bootstrap PSDepend to a D:\Some\Custom\Path using the Install-PSDepend.ps1 found in your BuildHelpers repo
Import the PSDepend module from D:\Some\Custom\Path\psdepend\PSDepend.psd1
Invoke PSDepend (see build.requirements.psd1 below)

Invoke-PSDepend -Path "$PSScriptRoot\build\build.requirements.psd1" -Target D:\Some\Custom\Path -Force -Install

Result:
Module is not installed/downloaded, and this output is shown (as standard output):
Unable to find package 'psdepend'. Existing packages must be restored before performing an install or update.
By debugging I found the parameters nuget.exe is called with, and calling nuget.exe directly with those parameters produced the same result:
D:\Some\Custom\Path\psdepend\nuget.exe install TestMod99 -Source "https://some.myget.feed/.../api/v2/" -ExcludeVersion -NonInteractive -OutputDirectory "D:\Some\Custom\Path"
However by trial and error I found that when removing the '-ExcludeVersion' parameter it succeeds:
D:\Some\Custom\Path\psdepend\nuget.exe install TestMod99 -Source "https://some.myget.feed/.../api/v2/" -NonInteractive -OutputDirectory "D:\Some\Custom\Path"
I don't know much about NuGet and it's parameters, so can't really say if it would generally be safe to remove that parameter when no version is specified (or even entirely).
build.requirements.psd1:
@{
    'TestMod99' = @{
        DependencyType = 'PSGalleryNuget'
        Source         = 'https://some.myget.feed/.../api/v2/'
    }
}

NuGet Version:
NuGet Version: <IP_ADDRESS>79

Windows Version:
ProductName           Version Build UBR
-----------           ------- ----- ---
Windows 10 Enterprise 1709    16299 214

PowerShell Version:
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           <IP_ADDRESS>

Host:
Name             : Visual Studio Code Host
Version          : 1.5.1
InstanceId       : 30c5f87d-9b2a-4cc6-8d86-0cf9703f8320
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : da-DK
CurrentUICulture : en-US
PrivateData      :
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

Ahh that's a pain.  IIRC did this to avoid odd folder names:
ExcludeVersion | Installs the package to a folder named with only the package name and not the version number.
Wonder if anything changed in nuget that broke this?  Will poke around

Hi again!
Would you mind running with -verbose and including sanitized output?  Curious to see what path it's following.  Wonder if there are API differences with MyGet

My guess is MyGet doesn't understand -version latest.  Seems to line up with the error, and would explain why it happens when not specifying a version (latest is used in that case).

What really puzzled me was that even when running nuget.exe manually, trying to get TestMod99 downloaded, it would still complain about psdepend in the message. I even tried moving nuget.exe to a different folder. Guess this is a NuGet thing.
I will run with -verbose and post output later today :)

build_psdepend.ps1:
$tempPath             = Join-Path -Path $PSScriptRoot -ChildPath 'temp'
$tempModulePath       = Join-Path -Path $tempPath -ChildPath 'modules'
$installPSDependPath  = Join-Path -Path (Join-Path -Path (Join-Path -Path $PSScriptRoot -ChildPath 'build') -ChildPath 'helpers') -ChildPath 'Install-PSDepend.ps1'

### Getting dependencies

# Get PSDepened
& "$installPSDependPath" "$tempModulePath" -Verbose

Remove-Module -Name 'PSDepend' -Force -ErrorAction SilentlyContinue
Import-Module ('{0}\temp\modules\psdepend\PSDepend.psd1' -f $PSScriptRoot) -Force -Verbose

Invoke-PSDepend -Path "$PSScriptRoot\build\build.requirements.psd1" -Target $tempModulePath -Force -Install -Verbose

build.requirements.psd1 (sanitized):
@{
    'TestMod99' = @{
        DependencyType = 'PSGalleryNuget'
        Source     = 'https://some.myget.feed/.../api/v2/'
    }
}

Verbose output (sanitized):
D:\Some\Custom\Path> D:\Some\Custom\Path\build_psdepend.ps1

VERBOSE: GET https://dist.nuget.org/win-x86-commandline/latest/nuget.exe with 0-byte payload
VERBOSE: received 5066856-byte response of content type application/x-msdownload
Feeds used:
  https://www.powershellgallery.com/api/v2/

Installing package 'PSDepend' to 'D:\Some\Custom\Path\temp\modules'.
  GET https://www.powershellgallery.com/api/v2/FindPackagesById()?id='PSDepend'&semVerLevel=2.0.0
  OK https://www.powershellgallery.com/api/v2/FindPackagesById()?id='PSDepend'&semVerLevel=2.0.0 150ms
  GET https://www.powershellgallery.com/api/v2/FindPackagesById?id='PSDepend'&$skiptoken='PSDepend','0.1.60'
  OK https://www.powershellgallery.com/api/v2/FindPackagesById?id='PSDepend'&$skiptoken='PSDepend','0.1.60' 118ms

Attempting to gather dependency information for package 'PSDepend.0.1.63' with respect to project 'D:\Some\Custom\Path\temp\modules', targeting 'Any,Version=v0.0'
Gathering dependency information took 42,4 ms
Attempting to resolve dependencies for package 'PSDepend.0.1.63' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'PSDepend.0.1.63'
Resolved actions to install package 'PSDepend.0.1.63'
Retrieving package 'PSDepend 0.1.63' from 'https://www.powershellgallery.com/api/v2/'.
Adding package 'psdepend.0.1.63' to folder 'D:\Some\Custom\Path\temp\modules'
Added package 'psdepend.0.1.63' to folder 'D:\Some\Custom\Path\temp\modules'
Successfully installed 'PSDepend 0.1.63' to D:\Some\Custom\Path\temp\modules
Executing nuget actions took 260,1 ms
VERBOSE: Loading module from path 'D:\Some\Custom\Path\temp\modules\psdepend\PSDepend.psd1'.
VERBOSE: Loading 'FormatsToProcess' from path 'D:\Some\Custom\Path\temp\modules\psdepend\PSDepend.Format.ps1xml'.
VERBOSE: Loading module from path 'D:\Some\Custom\Path\temp\modules\psdepend\PSDepend.psm1'.
VERBOSE: Importing function 'Get-Dependency'.
VERBOSE: Importing function 'Get-PSDependScript'.
VERBOSE: Importing function 'Get-PSDependType'.
VERBOSE: Importing function 'Import-Dependency'.
VERBOSE: Importing function 'Install-Dependency'.
VERBOSE: Importing function 'Invoke-DependencyScript'.
VERBOSE: Importing function 'Invoke-PSDepend'.
VERBOSE: Importing function 'Test-Dependency'.
VERBOSE: Running Invoke-PSDepend with ParameterSetName 'installimport-file', PSDependAction Install, and params:
Key     Value
---     -----
Path    {D:\Some\Custom\Path\build\build.requirements.psd1}
Target  D:\Some\Custom\Path\temp\modules
Force   True
Install True
Verbose True

VERBOSE: Working with [1] dependency files from [D:\Some\Custom\Path\build\build.requirements.psd1]:
D:\Some\Custom\Path\build\build.requirements.psd1

VERBOSE: Overriding Dependency target [] with target parameter value [D:\Some\Custom\Path\temp\modules]
VERBOSE: Running Invoke-DependencyScript with ParameterSetName 'Map' and params:
Key              Value
---              -----
PSDependAction   {Install}
PSDependTypePath D:\Some\Custom\Path\temp\modules\psdepend\PSDependMap.psd1
Dependency       @{DependencyFile=D:\Some\Custom\Path\build\build.requirements.psd1; DependencyName=TestMod99; DependencyType=PSGalleryNuget; Name=; Version=; Parameters=; Source=h...

VERBOSE: Dependencies:

DependencyFile  : D:\Some\Custom\Path\build\build.requirements.psd1
DependencyName  : TestMod99
DependencyType  : PSGalleryNuget
Name            :
Version         :
Parameters      :
Source          : https://some.myget.feed/.../api/v2/
Target          : D:\Some\Custom\Path\temp\modules
AddToPath       :
Tags            :
DependsOn       :
PreScripts      :
PostScripts     :
PSDependOptions :
Raw             : {Source, DependencyType}

VERBOSE: Searching for D:\Some\Custom\Path\temp\modules\psdepend\PSDependScripts\PSGalleryNuget.ps1
VERBOSE: Searching for PSGalleryNuget.ps1
VERBOSE: Get-Parameters for D:\Some\Custom\Path\temp\modules\psdepend\PSDependScripts\PSGalleryNuget.ps1\PSGalleryNuget.ps1
VERBOSE: Found parameters [Dependency Force Import PSDependAction]
VERBOSE: Invoking 'D:\Some\Custom\Path\temp\modules\psdepend\PSDependScripts\PSGalleryNuget.ps1' with parameters
Name                           Value
----                           -----
Dependency                     @{DependencyFile=D:\Some\Custom\Path\build\build.requirements.psd1; DependencyName=TestMod99; DependencyType=PSGalleryNuget; Name=; Version=; Paramet...
PSDependAction                 {Install}

VERBOSE: Getting dependency [TestMod99] from Nuget source [https://some.myget.feed/.../api/v2/]
VERBOSE: Saving [TestMod99] with path [D:\Some\Custom\Path\temp\modules]
VERBOSE: Running nuget.exe with arguments install; TestMod99; -Source; https://some.myget.feed/.../api/v2/; -ExcludeVersion; -NonInteractive; -OutputDirectory; D:\Some\Custom\Path\temp\modules
Unable to find package 'psdepend'. Existing packages must be restored before performing an install or update.
VERBOSE: Feeds used:
  https://some.myget.feed/.../api/v2/

Installing package 'TestMod99' to 'D:\Some\Custom\Path\temp\modules'.
  GET https://some.myget.feed/.../api/v2/FindPackagesById()?id='TestMod99'&semVerLevel=2.0.0
  OK https://some.myget.feed/.../api/v2/FindPackagesById()?id='TestMod99'&semVerLevel=2.0.0 227ms

Attempting to gather dependency information for package 'TestMod<IP_ADDRESS>' with respect to project 'D:\Some\Custom\Path\temp\modules', targeting 'Any,Version=v0.0'
Gathering dependency information took 749,39 ms
Attempting to resolve dependencies for package 'TestMod<IP_ADDRESS>' with DependencyBehavior 'Lowest'

D:\Some\Custom\Path>


[Docs] git install document update, sourcing nvm

please refer to the issue https://github.com/nvm-sh/nvm/issues/2204

@huahuayu this is still waiting for you to update the PR to resolve the issue i mentioned; are you still interested in completing the PR?


How can I join to slack?

Hello,
I have few questions so I wanted to join your slack, but I can't register because I do not have @jetbrains.com  email.
Can you invite me by my e-mail oraz need I ask here?

Use this link: https://surveys.jetbrains.com/s3/kotlin-slack-sign-up
You don't need @jetbrains email address to join.


CC76665: Tab and style issue

Hello, @corob-msft,
This proposed file change comes from https://github.com/MicrosoftDocs/cpp-docs.zh-cn/pull/25 .
Could you review this contribution and help to merge if agreed?
Many thanks in advance.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions

#sign-off


Added DataContract serialization support via System.Runtime.Serialization library.

I needed to store entities of Microsoft Dynamics 365 which are only serialized correctly by DataContract serializers. So, I've added DataContract serialization support via System.Runtime.Serialization library.
I tried but then gave up trying to support .NetStandard1.6 and below versions because of this issue. So I'm just supporting .NetFramework4.5 & .NetStandard2.0 right now.
One more thing: DataContractJsonSerializer class may serialize DateTime values in a different way. I've added comment to let the user know the usage on CacheManager.Tests project.

hey @rebulanyum thanks for the PR! I'll take a look soon™ ;)

@MichaCo don't have free time for merging, right? 😄

@rebulanyum thanks again for the great PR. I will go ahead and do some code style changes and integrate it with some other things.
The only thing I saw is that you added a copy right in the project file with your name and a link to your license file in your project. Was this intentional? I'll have to change that to use the PR.
Thanks,
M


PoC: Investigate state transition proofs

Problem
The rln-contract is stateless, i.e we do not store the whole tree onchain, but we only store the commitments, and emit them as events for users to sync from scratch.
For users who just want to verify proofs, they have to sync the whole tree to know the current root
Proposed solution
We make use of a "merkle state transition proof" where we accept a merkle proof of the state before making an insertion, and the merkle proof of the state after the insertion. This will allow having the root of the new state onchain, while maintaining lower gas costs than having the whole tree onchain.
The proposed state transition circuit is as follows -
pragma circom 2.1.0;

include "./utils.circom";
include "../node_modules/circomlib/circuits/poseidon.circom";
include "../node_modules/circomlib/circuits/comparators.circom";

template RLNStateTransition(DEPTH, LIMIT_BIT_SIZE) {
    // Private signals
    signal input identitySecret;
    signal input userMessageLimit;
    signal input newPathElements[DEPTH];
    signal input newIdentityPathIndex[DEPTH];

    // Public signals
    signal input previousRoot;
    signal input previousRateCommitment;
    signal input pathElements[DEPTH];
    signal input identityPathIndex[DEPTH];

    // Outputs
    signal output newRoot;
    signal output rateCommitment;

    signal identityCommitment <== Poseidon(1)([identitySecret]);
    rateCommitment <== Poseidon(2)([identityCommitment, userMessageLimit]);

    newRoot <== MerkleTreeInclusionProof(DEPTH)(rateCommitment, identityPathIndex, pathElements);
    // old root calculation
    signal oldRoot <== MerkleTreeInclusionProof(DEPTH)(previousRateCommitment, identityPathIndex, pathElements);

    // ensures the old root != new root
    signal isEq <== IsEqual()([oldRoot, newRoot]);
    isEq === 0;
}

component main { public [previousRoot, pathElements, identityPathIndex] } = RLNStateTransition(20, 16);

As per internal discussion, this feature will not be pursued since only one state transition proof may be accepted per block, and it would require an indexer to accept and aggregate registrations to the membership set.


Arrays testing

InThis PR:

Testing out the methods

Closing this PR, because we do not merge solutions into this repository

Sorry, was a mistake on my part
On Wed, Aug 7, 2024 at 2:04 PM Rachel Moser @.***>
wrote:

Closing this PR, because we do not merge solutions into this repository
—
Reply to this email directly, view it on GitHub
https://github.com/TheOdinProject/ruby-exercises/pull/103#issuecomment-2273207078,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5YBEDB42J3MDOA4TKC2J3ZQH5MHAVCNFSM6AAAAABMD4J2P6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZTGIYDOMBXHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


test: fix flaky sample test

It seems like operation disappear if Instance is old I am not able to find any document for same.
Instead of deleting instance based on operation's start time it checks the created label and deletes the instance that created before 4 hr.

@AVaksman PTAL.

Yes, I have come across the same issue before. It seems that if an instance is old enough, the operations' logs "disappear".
Hence return undefined in the test logic.
Your proposal seems fine. Instead of relying on the operation, we add another label with the timestamp of instance creation and validate the age of the instance based on that label.
Another point towards this implementation is that similar logic is used in system-test clean up.
Approving


Remove ReadOnly flag

Review app deployed to https://teaching-vacancies-review-pr-2845.london.cloudapps.digital


Do not use std::io::IoSlice in libxcb's FFI

On Windows, xcb defines its own iovec struct in xcb_windefs.h, which does not match the WSABUF struct used in IoSlice.

How did you find this? Did this actually break something, or did you just come across this "accidentally"?

How did you find this? Did this actually break something, or did you just come across this "accidentally"?

Just accidentally, I didn't have the chance to test x11rb on Windows yet.


Clarification as to 'Dropbox API app with full access'

I'm hoping that git-remote-dropbox will work just fine with an API token generated for a Dropbox App that gets full access to a single folder for that app, but based on the current documentation, that's not clear:

Generate an OAuth 2 token by going to the app console, creating a Dropbox API app with full access to all files and file types, and generating an access token for yourself.

There's also the possibility that granting full access to the App folder will work but is not the ideal setup; if so, adding that explanation to the documentation would be helpful. (I'd also like to know this, so if that's the case, a reply here would be appreciated!)
Thanks!

Hmm, I don't know if it works. If you want to experiment with that and let me know if it works, that would be awesome!

Yes, it works pretty much well!


prop: BUG

Example don't work:
ERROR: POST https://api.digitalocean.com/v2/domains/NYC3/records: 404 The resource you were accessing could not be found.
It must be https://api.digitalocean.com/v2/domains/records
If ZONE :="/"
ERROR: POST https://api.digitalocean.com/v2/domains///records: 404 The resource you were accessing could not be found

Possibly this problem? https://github.com/libdns/digitalocean/pull/3

No, I don't think. It's only related to libdns, in  digitalocean case ZONE not used. For my opinion it's very easy to fix.
Hmm.. I decide use LEGO lib. In fact  in begin "CADDY" use LEGOlib for DNS-01.
https://twitter.com/mholt6/status/1073103805112147968

How should we fix it?
(You can read more about why we switched from lego in https://github.com/caddyserver/certmagic/issues/71.)

Fix, maybe somewhere:
if digitalocean {
not use zone
else {
.....
}
Sorry,  I don't have time exam (certmagic) project.
From other side LEGO support about 50 DNS providers. Why not use it? Or at least give option use it.

From other side LEGO support about 50 DNS providers. Why not use it? Or at least give option use it.

Lego is not a general-purpose DNS library like libdns is. All its providers can do is set and delete ACME TXT records. But if you're using Caddy, you can still use lego, it's just a bit clunky to configure: https://github.com/caddy-dns/lego-deprecated

I see good! Unfortunately it my case digitalocean provider don't work for me. I have about 2000 domains to convert for https:
In fact looks like it simple tupo:
POST https://api.digitalocean.com/v2/domains/NYC3/records
POST https://api.digitalocean.com/v2/domains/records


Update docs

Explain that the results will only be available once a new commit is pushed. We can have a workflow_dispatch trigger users can trigger manually the first time to see the results flow
Explain where to find the reason why a run failed
Move users to GITHUB_TOKEN
Explain whether pull request trigger is supported or not
Call out that running scorecard on forks is not officially supported
Orgs may need to enable GitHub Advanced Security https://github.com/ossf/scorecard-action/issues/134#issuecomment-1064197494

cc @naveensrinivasan added Call out that running scorecard on forks is not officially supported, per our discussion in https://github.com/ossf/scorecard-action/issues/135

cc @naveensrinivasan added Call out that running scorecard on forks is not officially supported, per our discussion in #135

Thank you!

@naveensrinivasan thanks for all the e2e tests, it's great. Is there a way to document where to look for, for example for workflow_dispatch, schedule, push and pull_request triggers. Where to find them :-)?
Thanks!


Easier licensing terms

This is the same license that Sentry uses.

You need to update the license attribute in the composer.json too.

Good point :)


Extend NDB Operator capabilities to support Postgres HA

What this PR does / why we need it:
This PR incorporates the capability to provision Postgres HA databases in NDB via the operator.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
How Has This Been Tested?"
Special notes for your reviewer:
Release note:

@irion4686 can you rebase your branch on main please


Add a feature based object store provider

Which issue does this PR close?

Closes #257, #6.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

Hi @andygrove, @tustvold, @matthewmturner, could you help review this PR?

cc @avantgardnerio who has been working on supporting custom object stores in DataFusion/Ballista

The approach here LGTM but I have not worked with the object store yet

Let's merge it first. Will update the ObjectStoreProvider interface after upgrading datafusion to the latest version.

It's unclear from skimming this: what is the intended usage? Should a statement like:
create external table customer stored as CSV DELIMITER '|' location 's3://minioadmin:minioadmin@<IP_ADDRESS>:9000/tpch';

Work now?


Use FlatBuffer configuration change messages

DM-1901
Use new schema for configuration change messages.
Added unit tests for parsing the messages and updated the system tests.

I will go ahead with merging this change. Anyone needing to support the old JSON configuration messages can use the 0.1.0 release


FBX2glTF out of date with upstream

It appears that the official https://github.com/godotengine/FBX2glTF has received some fixes that haven't been pulled into https://github.com/barcoderdev/FBX2glTF yet
According to https://github.com/V-Sekai/unidot_importer/issues/19 they have reviewed and are supportive of your modifications
Could you please submit your changes upstream as a PR or update barcoderdev/FBX2glTF from upstream?

Also, the artifacts at https://github.com/barcoderdev/FBX2glTF/actions/runs/5040011556 have expired, and I accidentally deleted the copy I had... 😭

Also, the artifacts at https://github.com/barcoderdev/FBX2glTF/actions/runs/5040011556 have expired, and I accidentally deleted the copy I had... 😭

I forced a rebuild and updated the link in the readme.  I hope to have time to work on this project more sometime soon, and get the stdin/stdout/pivot changes pushed to the main repo.

@barcoderdev Thank you! 🙏


Invoke py.test correctly with coverage run

If I run make coverage (Python 3.5), I get:
$> make coverage
coverage run --source my_project py.test
No file to run: 'py.test'
Makefile:64: recipe for target 'coverage' failed
make: *** [coverage] Error 1

Correct invocation is to use the -m switch.
http://stackoverflow.com/a/16524426/405682

Thanks @benjaoming !


xctool is unable to load frameworks introduced with Xcode 6

When project references framework that can be created for iOS with Xcode 6 then it fails with following error.
sim[60162:303] DYLD_INSERT_LIBRARIES contains possible bad values.  Caller beware: /Users/user/Projects/xctool/build/0b27b43/6A280e/Products/Release/lib/otest-query-lib-ios.dylib
dlopen(/Users/user/Library/Developer/Xcode/DerivedData/MyApp-ctfopcccyokbvrarehhgryskhaip/Build/Products/Debug-iphonesimulator/MyAppTests.xctest/MyAppTests, 1): Library not loaded: @rpath/Quick.framework/Quick
Referenced from: /Users/user/Library/Developer/Xcode/DerivedData/MyApp-ctfopcccyokbvrarehhgryskhaip/Build/Products/Debug-iphonesimulator/MyAppTests.xctest/MyAppTests
Reason: image not found

Is there any more thoughts on this, anything I can provide?
Failed to query the list of test cases in the test bundle: 2015-01-06 20:38:56.709 sim[38743:241853]     /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/sim:   No simulator devices appear to be running.  Setting data directories to /var/empty.
2015-01-06 20:38:56.710 sim[38743:241853] DYLD_INSERT_LIBRARIES contains possible bad values.  Caller beware: /usr/local/Cellar/xctool/0.2.1/libexec/lib/otest-query-lib-ios.dylib

Xcode - Version 6.1.1 (6A2008a)
OSX   - Version 10.10.1 (14B25)
xctool - Version 0.2.3 (HEAD)
Like others I have no "custom" frameworks, I do have 3rd party ones, I tried including them as @alexeyxo suggested. No joy.

I had a similar error:
Failed to query the list of test cases in the test bundle: 2015-02-11 15:34:22.630 sim[53512:2310403] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/sim: No simulator devices appear to be running.  Setting data directories to /var/empty.
2015-02-11 15:34:22.632 sim[53512:2310403] DYLD_INSERT_LIBRARIES contains possible bad values.  Caller beware: /usr/local/Cellar/xctool/0.2.2/libexec/lib/otest-query-lib-ios.dylib
dlopen(/Users/Radek/Documents/Developer/GitHub/DateKit/Build/Products/Debug-iphonesimulator/DateKitTests.xctest/DateKitTests, 1): Library not loaded: @rpath/DateKit.framework/DateKit
  Referenced from: /Users/Radek/Documents/Developer/GitHub/DateKit/Build/Products/Debug-iphonesimulator/DateKitTests.xctest/DateKitTests
  Reason: image not found

My project was a Swift framework.
I've managed to resolve it by adding "New Copy Files Phase" to Build Phases, than I've chosen Destination: Frameworks and using '+' I've selected and added my framework.
I hope this will help you.

@alexeyxo THANK YOU!  Your solution worked for me perfectly.

Same issue - no workspace frameworks.

Could anyone provide a project that I could use to repro?

Thanks to @alexeyxo. His solution has just worked for me.

Could anyone provide a project that I could use to repro?

@ExtremeMan if that is still actual you can clone my project from this commit. If I remove "Copy Framework" phase the problem reappears.

@stanislaw I checked your project but it fails or succeeds for both xctool and xcodebuild. I tried several commits.

@ExtremeMan okay looks like that is a different issue then. Anyway @alexeyxo's solution works for me. Thanks for turnaround.

Had the same problem.
Failed to query the list of test cases in the test bundle: 2015-03-31 14:51:56.905 sim[55679:303] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/sim: No simulator devices appear to be running.  Setting data directories to /var/empty.
2015-03-31 14:51:56.907 sim[55679:303] DYLD_INSERT_LIBRARIES contains possible bad values.      Caller beware: /usr/local/Cellar/xctool/0.2.2/libexec/lib/otest-query-lib-ios.dylib
2015-03-31 14:51:56.907 sim[55679:303] Error spawning child process: Bad CPU type in executable

Clearing derived data solved the problem.

I bumped into this problem as well on a Swift Cocoa Touch Framework project. I solved it by adding my own project's .framework file to the copy files build phase.

For what it's worth, I suspect there is a code change needed for this bug. I did indeed hit this issue and resolve it by adding the framework to the test bundle as described above. However, this should not be necessary. xcodebuild itself runs the tests just fine without this additional step. That tells me that ideally xctool should not require it either, and should "just work" in this case.

Just wanted to confirm that adding a "Copy Files" phase fixed my issue with running Quick/Nimble tests using xctool. Had to copy both the Quick and Nimble frameworks, even though they are also under the "Link Binary With Libraries" section.

I have found a fix! I will merge into master soon. The fix is now here: https://github.com/facebook/xctool/tree/nekto/common_env

@ExtremeMan unfortunately your fix is not solving issue for me. Neither is "Copy files" solution, actually, which is really strange.

@crazyjooe then most likely you are hitting another issue. What error do you see? Is your project open sourced?
Anyways you can run otool -l <path to the test bundle>, checkout all @prath values, then open test bundle and verify that you have everything in those paths.

Fix is on master. Please open new issue if you see errors saying that Library not loaded: @rpath/... in the test bundle.

FYI, the build on Homebrew is probably out of date.

The homebrew release is blocked on https://github.com/Homebrew/homebrew/pull/40289 (problems with Xcode 5).

What is the status of homebrew Formula?

What is the status of homebrew Formula?

What is the status of homebrew Formula?

What is the status of homebrew Formula?

I've cloned the HEAD just now (--version shows 0.2.5).
And this issue is still happening.

We have this problem in our build. After debugging it, the problem for us is that we load some third party libraries which write to stdout. Since otest-query returns the list of tests via JSON written to stdout, it's obviously a problem if something else is also writing to stdout. Since we don't control the other libraries, my short term fix to get our builds running again is to remove the extra stuff. This is only a short term fix.
I wonder if it's possible to use a separate file to communicate the list of tests cases, rather than stdout? I don't think it's safe to assume nothing else in the binary will ever write to stdout. I'm happy to make the change if you you agree

@jeffpearce I think it makes sense. Not sure how easy it would be to implement but nothing impossible.

I had the same problem as @XBeg9
Upgrading xctool to 0.2.4 solved my problem ! Thanks !

In my case the reason was the tests that were written in Kiwi and I had some objects initialized directly in the describe() section.
Apparently the describe() sections are queried when XCtool tries to gather info about the tests to run, so those heavyweight objects ended up accessing infrastructure not available at this step.
For some reason this doesn't happen when calling xcodebuild directly.
Takeaway: when using with Kiwi don't initialize variables in describe() instead declare them as __block <class> varName; and initialize in beforeAll().

@rciobanu-omnifone, oh, hm. Right, xctool first query test cases names and then runs them. Xcodebuild just run them w/o pre-querying.


Lowest iOS version supported?

Before my app goes to TestFlight, I am checking it with older iOS versions with simulators.
8.1 - crash in the react-native-permissions module
9.0 - same
10.3 - runs ok
I am now downloading all iOS version above 9.0 simulators, which takes ages...
Does anyone know what the lowest iOS version is that I should set in my Xcode project?
TIA!

it should work with ios >= 8.0. Can you share more details about the crash?

use 8.2

closing for inactivity


storybook template

[x] I have searched the issues of this repository and believe that this is not a duplicate.

When working with material-ui you usually end up adjusting the typography, overwriting some global styles and so on to create your own "themed variant" of material-ui. Within material-ui some of these styles/overwrites affect another as e.g. Typography is part of more or less any other material-ui component. So adjusting typography might adjust tabs without you noticing. In our current workflow we have one relatively gigantic storybook showcasing all the components we have (including a re-export of basically all material-ui components).
I think it might be a good idea to create a "template" as part of material-ui to get new component libraries started more quickly & to share themed variants with no-code designers. The current "color selection theming" in the material-ui docs is relatively limited.
Summary 💡
It would be great if there was a "ready to go & up-to-date" storybook example within the examples folder to showcase all the components.
Examples 🌈
Sadly our storybook is closed source atm, but we might think about abstracting & open sourcing the material-ui part of it.
Motivation 🔦
Did this once manually, don't want to do it twice and I assume other companies have similar workflows.

Just when writing this:

The current "color selection theming" in the material-ui docs is relatively limited.

I started wondering if we couldn't just deploy a custom themed variant of the docs instead of doing things in storybook. Doing things in storybook would be nicer in terms of our testing setup, but the docs are much more in-detail as the ones we have in storybook :thinking:
Is this sth people are doing?

OT: while writing that i was wondering if that actually is a feature request or would be better suited for discussions. I'd love if you enabled discussions, as e.g. in the styled-components tickets that's a pretty endless "discussion", but seems to not provide any value to the actual ticket.

@sakulstra This issue makes me think of #11242. I'm all in for exploring this path 👍.
What do you think about using your previous storybook to seed the exploration? Maybe we could create a new https://github.com/mui-org/storybook repository with it. If it gets traction, we integrate the project back into https://github.com/mui-org/material-ui?

Also, there is this alternative direction: #20275.

@oliviertassinari thanks for pointing me to these tickets - have to think about this a bit as all these things have a lot of drawbacks :sweat_smile:
As i see it there are basically 3 suggestions solving different problems
Maintaining a storybook example (this ticket)
Usecases: Kickstart themed & general ui development, Showcase components
Pro

is likely to help a lot of people (at least from person experience within the last 4 years, storybook as a widely accepted tool and there are barely react teams not using it)
is usually well integrated into developer/testing workflows (if it's with chromatic or jest addon)

Con (#11242)

just maintaining it outside(also inside) of material-ui brings a gigantic maintenance overhead as you have to write stories & demos¹

Shipping a docs generator
Usecase: Kickstart themed development, Showcase components
Pro

probably doable without to much effort :thinking:. Have to check the code, but one could probably "just alter the build pipeline to inject a theme". In a very basic implementation people could build their own docs from checking out material-ui.

Con

is likely to not integrate well with developers workflows dependent on the implementation
forces you out of storybook at least for the material-ui part

Live customization in demos (#20275)
Usecase: Allow people to play around with theming
Pro

that's just very cool :rainbow: :rocket:
(might have to nice side-effect of teaching people how theming works #learningByDoing - I just joined a frontend team, where the theme usage can just be described as abusing. All material-ui functionality is literally destroyed.)

Con

disclaimer: it's not a real con: this is simply another usecase i think

¹I think "co-maintaining" this might be unreasonable. The docs are incredible good imo and even with our current custom storybook implementation I checkout the docs from time to time :)
That said I'm wondering if one could generate the storybook stories & docs from material-ui/docs source to reduce maintenance burden & automatically get all the new features & fixes into the storybook.

I was looking at the sales metrics (over 50 days) and came to a very strange observation. We have two ads that link to the exact same URL:
A.

B.

Ad A. leads to 18% more clicks than ad B., however, if we look at the conversions to orders later down the road. We have $0 for ad A. This makes me believe that there is a non-neglieable demand for themes on top of Material-UI (free or paid) that is poorly addressed.
Then we had #21113 by @anisg. What if we were moving with the following "master" plan 😍?

#21111. We expose a storybook right from this repository. We automatically generate stories from the existing demos. We create a new category per parent folder and item per name of the demo. For instance, docs/src/pages/components/buttons/ButtonSizes.js turns into

This should be relatively easy to do. We can do the same as we do for the visual regression tests.
https://github.com/mui-org/material-ui/blob/8357c68cdc37c2b9c2a84891adb4df705f8ef155/test/regressions/index.js#L172
So, we create a new folder in the repository, let's say a /storybook folder that developers can clone. When they go into it, they must run a command to copy the demos from the version of Material-UI they have installed. It copies the demos from this repository, or update them if they upgrade to a new version. The repository has a section that explains how to customize the theme and how to add new stories. It can be used as a seed for a new design system. We make it MIT as it's an important foundation for what comes next.

#18908. We provide multiple built-in themes. Something a developer can import as easy as follow.

import AntdTheme from '@material-ui/core/antd-theme';
import { ThemeProvider, createMuiTheme } from '@material-ui/core/styles';

<ThemeProvider theme={createMuiTheme(AntdTheme)}>
  <YourApp />
</ThemeProvider>

I would say that 1 or 2 should be enough to make a point that it's possible and well supported

#20275. We make it possible to copy and paste a theme and to see it live on the documentation.
#21113. We list a couple of popular themes from the community, that they can preview right in the documentation, maybe using an external fetch.
#17991. We create a theme builder/design system builder. Something developers can use to quickly create a new theme. It starts free, with a long term potential to turns into something like https://modulz.app/.
We enable third-party authors to sell gorgeous themes. It would contain the documentation, using the storybook of 1. as well as Figma and Sketch assets.

cc @mui-org/core

That sounds actually great!
I might try to prototype sth on the weekend - in essence what we need for 1 would be some script which simply copies demos into a folder and enriches them with some csf as I get it?

@sakulstra Yes. What does "csf" mean?

sorry for the unnecessary abbreviation especially as I just learned what it means a few days ago as well :sweat_smile:
component-story-format(csf)

Short update on this:
I wrote a little codemod which essentially transforms the tsx files inside docs/src/components to named export & adds a new default export for component-story-format syntax. https://github.com/sakulstra/material-ui/blob/cdd40f3bf8aac0bed41a3fa2c9cd6561fb4f9a25/storybook-starter/scripts/csf-transform.js ... it worked for most components out of the box.

It that the correct direction. Wdyt?
Issues I faced so far:

https://github.com/reactjs/react-docgen/issues/387 - for new we don't have prop type docs for ts. Might be solved at some point :man_shrugging:
Some demos use 3th party libraries (e.g. material-table) which we would have to either install or drop the demos
It's a lot of stories and i'm not sure if all of them are actually useful
i tried to make this work with typescript, but there might be users using storybook with js as well :thinking:
the codemod currently breaks export default withStyles() statements as that's not easily transformable to a named export. For the sake of "quickly testing this" I just removed the corresponding stories.

@sakulstra Oh wow, I wasn't expecting an update that soon 😍. A couple of feedback.

For the third-party libraries, the documentation has a module to resolve the required dependencies and the version to run all the demos in CodeSandbox. We could share this util. There are definitely a lot of missing dependencie.
The more the merrier 🤷♂, but we could ignore the same one that we ignore for the visual regression tests. After all, isn't the objective the same? https://github.com/mui-org/material-ui/blob/5f2a237ff689ef067b048459e82dd05379069658/test/regressions/index.js#L20. I would also fix the broken story issues: https://github.com/sakulstra/material-ui/pull/2/files#diff-a09da5a06815b8e6589db87b874bb247R21.
What about we go full TypeScript? Developers would still be able to add new JavaScript stories anyway?
We could potentially migrate them to hook. But I'm not sure it's worth spending time on.

Are you sure we should bundle prettier? https://github.com/sakulstra/material-ui/blob/cdd40f3bf8aac0bed41a3fa2c9cd6561fb4f9a25/storybook-starter/package.json#L31 I would expect developer already have a custom prettier config in their repository.
v8 as the other packages? https://github.com/sakulstra/material-ui/blob/cdd40f3bf8aac0bed41a3fa2c9cd6561fb4f9a25/storybook-starter/package.json#L11
Please no pre-commit rules https://github.com/sakulstra/material-ui/blob/cdd40f3bf8aac0bed41a3fa2c9cd6561fb4f9a25/storybook-starter/package.json#L28.
I believe the /stories/components/ folder should be empty: https://github.com/sakulstra/material-ui/tree/cdd40f3bf8aac0bed41a3fa2c9cd6561fb4f9a25/storybook-starter/stories/components.  (add it to the .gitignore?)
Vuetify has a similar package we can use to benchmark: https://github.com/nidkil/vuetify-with-storybook.
Would it make sense to add the @storybook/addon-viewport plugin and have it configured using the theme.breakpoints values?
I don't understand what we need the tsdx dependency.

Oh wow, I wasn't expecting an update that soon heart_eyes

We might want to sue this soonish internally so it didn't make sense to wait :sweat_smile:
2)3) will check that out
4) i'm personally fine with that
5) It's just Hidden and SwipeableTextMobileStepper - might refactor it or adjust the jscodeshift to be a bit more clever about replacing exports

I think you looked at an outdated commit :speak_no_evil: https://github.com/sakulstra/material-ui/pull/2/files
6) comes with tsdx, which i already dropped¹
7) i don't care to much, but 8 is EOL afaik (https://github.com/nodejs/Release) - would discourage usage if possible
8) see 6)
9) :thinking:, you mean it should come empty by default and people have to run the script on their own? Having this "synced" with the current codebase would have the advantage of dropping that step. For me it's not clear yet how the distribution path will look like :thinking:
10) thanks for the ref, will check that out :+1:
11) It might, have to think about how to actually do the theming part as well - probably just a global decorator expecting src/theme.ts to exist or sth like that
12) see 6)
¹I initially started of with tsdx as that's what I currently use, dropped it though as not everyone might want to use it. Comed in handy though if you want to develop your "ui-kit"/themed material-ui as a package.

@sakulstra Did you make progress with the storybook template? :)

Sadly, not at all - won't get to it before the end of next week :/
feel free to pick it up though

@oliviertassinari sorry i wont get back to this in the nearest future due to limited and more pressing things :(

I've been having a conversation on Twitter with @MaterialUI about a sidecar, parallel feature to this. Just for quick context to wrap that conversation here:

I can imagine a docs page that points developers to a naive approach that provides one step composition to the official version, with users guided toward the fully themed localized approach in that issue when it's complete. Stronger initial hook, before moving to a purchase.

I'd personally prefer the full implementation that includes theme as discussed here. The Storybook team might be excited to have that basic option. Both options depend on this issue, which looks like it could use a hand. Would ya'll be interested in outside contribution to get this moving forward? Any specific issues I could help target if this is a little too tightly constrained? My time is a little constrained, but I'm interested.

@lancegliser thanks so much for getting this conversation on my radar. for my part, i can do my best to prioritize storybook issues that improve the dev experience for MUI, as I've already done in the case of #12734. i believe @tooppaaa is also interested in contributing.

@lancegliser I don't follow the logic around the commercialization aspects of this issue "Stronger initial hook, before moving to a purchase". My comment in https://github.com/mui-org/material-ui/issues/21111#issuecomment-631037264 might have led you down this road. However, I think that better integration with Storybook can be interesting independently.
At this point, I think that what's important is to maximize adoption, focus on points before 5. and 6.
In 5. I was referring to leveraging the best ideas from existing attempts, e.g. anima, Modulz. It seems that anima gets the integration with designers right. They have created a plugin for Figma/Sketch/AdobeXD. Modulz seems to get the importance of allowing designers and developers to interact on the same content, as well as the generation of the documentation right. If we were to go down this road, we would raise, starting by building a plugin for Figma, create a SaaS to store your components, have a GitHub integration to sync them with your code, have a way to generate high-quality documentation for it. However, we likely have identified a better opportunity ahead so I can't say if we will pursue this one (at least not first, e.g. give it two years for the unstyled components #6218 to gain traction).
In 6. and in hindsight, data suggests the opportunity cost is too high relative to other problems. It's likely not worth carrying, we have a store this could be enough. Our latest plan on this is to build a second and only theme: #22485. Then, have premium templates for it.

Would ya'll be interested in outside contribution to get this moving forward?

Yes!

@lancegliser It seems that there are a couple of different topics related to a tighten integration with Storybook, I'm not sure which one should be focused on:

Material-UI using Storybook. We are using it in https://github.com/mui-org/material-ui-x. It's great for us when the test case can't be in the documentation nor in the end-to-end tests or the visual regression tests. We maintained a list of stress test cases there. We should probably extend its usage for end-to-end tests and custom visual regression tests. Our main pains are around the DX: slowness to load, lack of server-side rendering, too isolated environment. I'm personally more productive working inside the Next.js documentation than inside the Storybook.
A Storybook template generator. A tool to pull out the demos from Material-UI and quickly create one for your components. When I talk with users of the library, what most seem to want is the capability to generate custom documentation like the one we have on http://material-ui.com/. However, I think that it's not in opposition to having the capability to quick start a lot of demos. @kutnickclose how did you solve this problem in the end?
A Storybook inside Material-UI. It's a reference to https://storybook.js.org/docs/react/workflows/storybook-composition. I have to admit, I don't understand the use cases. It would be great to provide more information.
Storybook using Material-UI. I recall they were experimentation with it for Storybook v4 two years ago https://github.com/storybookjs/SBNext. With Material-UI v5 coming with emotion instead of JSS and unstyled components, or even planning a non-Material Design base theme, maybe some of the blockers were solved 🤷♂.

for point 2, I:

copied https://github.com/sakulstra/material-ui/pull/2/files
Separately, I did a Create React App w/ typescript and added Storybook 6
manually copied over the generated results from point 1 above.  (note: I also had to change https://github.com/sakulstra/material-ui/pull/2/files#diff-091fd7e09f049e1b700bd85156091bf83c38d3edec473feeea4a200f9753f857R23 slightly to get it to work for storybook 6 which came out after this PR.  I think I changed it from Material-ui|${component}|${test} to Material-ui/${component})
I needed to install a lot of dependencies and @types before it would compile
Added a preview.js file kinda like this to see light/dark theme

import React from 'react';
import { ThemeProvider } from "@material-ui/styles";
import { CssBaseline, createMuiTheme } from "@material-ui/core";

const darkTheme = createMuiTheme({
  palette: {
    type: 'dark',
  },
});

const lightTheme = createMuiTheme();

export const globalTypes = {
  theme: {
    name: 'Theme',
    description: 'Global theme for components',
    defaultValue: 'light',
    toolbar: {
      icon: 'circlehollow',
      items: ['light', 'dark'],
    },
  },
};

const withThemeProvider = (Story,context) => {
  const theme = context.globals.theme === 'light' ? lightTheme : darkTheme

  return (
    <ThemeProvider theme={theme}>
      <CssBaseline />
      <Story {...context} />
    </ThemeProvider>
  )
}

export const decorators = [withThemeProvider];

for deployment, there's a storybook deployer addon that can deploy to github pages which is nice for public storybooks but wasn't an option for the private storybook I worked on.

My biggest complaint is that storybook doesn't auto-detect the controls of a component.  Their docs specifically state that the controls won't be auto detected if "You're trying to generate controls for a component defined in an external library" https://www.npmjs.com/package/@storybook/addon-controls.

It might be overkill, but it seems like you could repurpose much of https://github.com/mui-org/material-ui/tree/next/framer/scripts to create the annotated wrapper shown in https://www.npmjs.com/package/@storybook/addon-controls#my-controls-arent-being-auto-generated-what-should-i-do. It does something similar for Framer controls.

My biggest complaint is that storybook doesn't auto-detect the controls of a component. Their docs specifically state that the controls won't be auto detected if "You're trying to generate controls for a component defined in an external library" npmjs.com/package/@storybook/addon-controls.

We might be able to fix this as part of improving MUI support in Storybook. @mbrookes your workaround sounds great as a short-term fix.

Any further movement on this?  Been struggling to implemnent storybook, seems blocked by #24282

I am building a Design System with MUI, I think this is important
Are you guys using storybooks privately or only on grid-x?

Are you guys using storybooks privately or only on grid-x?

@danielvianna Answered in point 1. of https://github.com/mui-org/material-ui/issues/21111#issuecomment-734496442

@oliviertassinari we started privately but it took so much time to pull basic components into stories that we gave up (the same thing as you have in docs). We are not using grid-x yet* (maybe will soon)
The challenge is that on top of material UI we also building custom components, so just the effort to make them work is already too much work for a startup with 2 frontend guys only, as we need to focus on making the system work and focus on product-market fit. I'm working on a system that is not the typical CRM, but it involves video streaming, control of robotic cameras, AI machine vision, and many things that material wouldn't have. The initial idea was just really to get a collection of the basic stuff and see when we make changes how the impact would be and compare visually the design. We not only have different components - I'm talking about new smaller "atoms" but also combination "molecules" "pages"

Our first internal solution is this patch: https://gist.github.com/eudinnou/e7f5a73f7441bf138d2c583c243abc1a following these steps:

clone the repo and checkout the tag version that you need
apply the patch
run yarn
run yarn docs:build-bundle

Usage:
import { MuiDocs } from 'mui-docs';
import theme from 'your custom theme';

const Wrapper = ({ children }) => (
  <MuiDocs.Providers theme={theme}>{children}</MuiDocs.Providers>
);

export const Accordion = () => (
  <Wrapper>
    <MuiDocs.Accordion />
  </Wrapper>
);

...

Additionally, we also copied some static images from docs/public/static and prism-okaidia.css.

@eudinnou That's really reasonable for create default MUI components Storybook. 😀
I used to have a project that was converted from MUI's Components Docs to Storybook, but it is not currently maintained as I am mainly working on the backend now.
storybook: https://main--632a01c394385880b3383063.chromatic.com/?path=/docs/components-alert--default
repo: https://github.com/laststance/mui-storybook
Recently I saw a blog post on the official Storybook blog about how to handle MUI Components in Storybook in a way that is partially similar to my approach.
https://storybook.js.org/blog/material-ui-in-storybook/
I have a complaint about generating from the TS type information in docgen only results in a useless Object button for parameters other than primitive types, and does not create a control panel where you can intuitively learn all the various parameters a component can accept.
I think MUI Official Team could make better Storybook for all MUI default compoments. 😎

Hey @ryota-murakami! I'm a Developer Experience Engineer for Storybook 😁 I wrote the article that you mentioned.
You're right that our controls for object props aren't ideal. Do you have a way that you envisioned being able to control object types?

Hey friends! I recently put together an example repository for Material UI and Storybook for our recent article, Material UI in Storybook. I'd be happy to expand on it a bit and put up a PR for the examples directory.

@ShaunLloyd Thank you for reacting to my comment!
Frankly, I don't think it is possible to generate control UI other than scaler values with the current docgen-typescript.
Therefore , it will be necessary to manually write Controls Addon settings.
this will need a lot of community contribution and time...
I'm working as a backend engineer now so I don't use MUI and Storybook heavily.
I hope Storybook/MUI official and community will produces better integration Storybook x MUI, and I'm glad to see it when I bring back frontend in the future! 😄


Fix typo

As reported by https://github.com/Roblox/Core-Scripts/issues/883.

Closed as this has already been made a PR.


GVRExternalScene problems loading new scene

GVRExtenalScene is not removing the previous scene despite setting the replace parameter to true, and it is crashing if I don't attach it to the root.
Below is the code being used when I receive an X3D command in the <Anchor> tag to go to a new X3D page.
GVRExternalScene gvrExternalScene = new GVRExternalScene(gvrContext, url, true);
root.attachComponent( gvrExternalScene );
If I attach gvrExternalScene to the root, I get the new scene, but the previous scene is still there.  If I don't attach gvrExternalScene, it crashes calling AssetRequest (because the first parameter is null).

I will work on it with you this afternoon.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Mitch Williams<EMAIL_ADDRESS>Date: 5/9/17 8:46 AM (GMT-08:00)
To: Samsung/GearVRf<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [Samsung/GearVRf] GVRExternalScene problems loading new scene (#1190)
GVRExtenalScene is not removing the previous scene despite setting the replace parameter to true, and it is crashing if I don't attach it to the root.
Below is the code being used when I receive an X3D command in the  tag to go to a new X3D page.
GVRExternalScene gvrExternalScene = new GVRExternalScene(gvrContext, url, true);
root.attachComponent( gvrExternalScene );
If I attach gvrExternalScene to the root, I get the new scene, but the previous scene is still there. If I don't attach gvrExternalScene, it crashes calling AssetRequest (because the first parameter is null).

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Samsung/GearVRf/issues/1190, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQw1S1Y7-S8UKggLscrHrYdOM1Wk7O-Rks5r4IpFgaJpZM4NVgkN.

This now works and can be closed.
There is a new issue with lights that has been documented, but the scene is loading as expected.
The resolution is that GVRExternalScene needs to be attached to a new GVRSceneObject, not root.


Monster Tamer Ep 58 - Title Scene - Nine Slice Menu

ticket to track work tied to title scene changes to support nine slice implementation. for this, we should have a separate video that talks about what nine slice is and how to use that in phaser 3. this would result in a class that can be re-used in this video series

https://raw.githubusercontent.com/devshareacademy/code-examples-from-my-video-content/GH-20-phaser-nineslice-demo/phaser-3/3.60/custom-nine-slice/src/main.js

make sure we add a link to the video

3:00 - card to video on nine slice
0:17 - Review nine slice scaling technique
2:05 - Code for nine slice scaling
3:21 - Create nine slice class and review code
8:11 - Define nine slice class config


README update

Codecov Report

Merging #856 (878b919) into main (eef6f01) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #856   +/-   ##
=======================================
  Coverage   85.10%   85.10%
=======================================
  Files          71       71
  Lines        6010     6010
=======================================
  Hits         5115     5115
  Misses        895      895

Continue to review full report at Codecov.

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


Implement Search deck

Closes #1069

@dkildar Could you review and test search deck feature?!

I don't really sure that this PR broke headers but FYI: `@undefined` instead of `@ecency` and `@` instead of `@username`


Error after git pull: No such highlight group name: CoqtailSent

Hi !
I updated my vim / plugins this morning and I got the following error message after my first evaluation command (leader c j, :CoqStart is fine):
Error detected while processing :
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 162, in step
    self.send_until_fail()
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 276, in send_until_fail
    self.reset_color()
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 612, in reset_color
    _make_matcher((sline, scol + 1), (eline + 1, ecol)),
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 734, in matchadd
    vim.command("let b:{} = matchadd('{}', '{}')".format(var, group, zone))
vim.error: Vim(let):E28: No such highlight group name: CoqtailSent

Here are my revisions/versions:

coqtail: 97d1633f01a48341d8668aa7d46f9d0295d631f8
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jun  3 2019 04:49:45)
macOS version
Included patches: 1-1450
Compiled by Homebrew
The Coq Proof Assistant, version 8.8.0 (February 2019)
compiled on Feb 1 2019 10:31:25 with OCaml 4.07.0

Do you have g:coqtail_nosyntax = 1?

No, I don't seem to have that variable set (:let g:coqtail_<tab> only returns coqtail_project_name and coqtail_sourced, and I don't have anything in my .vimrc).

Could you see if 0bf1da0 fixes the problem?

I don't have the time to test it in deep atm but a rapid test says it is fixed ! Thank you. I'll try to test in more later next week.

Great, I'll leave this issue open for now in case you run into any more problems with this.

No issue this morning, it seems to be correctly fixed. Again, thanks a lot !

I just got the same kind of error message in a different scenario, with CoqtailError:
Error detected while processing :
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 162, in step
    self.send_until_fail()
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 276, in send_until_fail
    self.reset_color()
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 620, in reset_color
    _make_matcher((sline + 1, scol), (eline + 1, ecol)),
  File "/Users/vsiles/.vim/bundle/Coqtail/python/coqtail.py", line 734, in matchadd
    vim.command("let b:{} = matchadd('{}', '{}')".format(var, group, zone))
vim.error: Vim(let):E28: No such highlight group name: CoqtailError

I forgot to move CoqtailError highlighting with the other Coqtail groups. Should work now.

I confirm that master is fixed, thank you !


Gracefully handle absence of sources in VM

Certain VM code calls Script::Source() and does not expect it to return null. When running from app-jit snapshot, source is not retained but observatory and debugger are still present. In such case, in Dart 1, VM generated the artificial sources from token streams. However, in Dart 2 Script::Source() returns null if source is not available.
We should fix all callers of Script::Source() to check result for null and handle this case gracefully. This includes debugger and observatory which should not crash if source is not available.
Another option is to generate artificial sources from kernel.
For example, test service/next_through_call_on_field_test crashes in the following way in app-jitk mode:
tools/test.py --print-passing-stdout -m debug -c app_jitk --strong service/next_through_call_on_field_test

>testee>err> ../../runtime/vm/object.h: 7379: error: expected: raw() != null()
>testee>err> Dumping native stack trace for thread 373ca
>testee>err>   [0x000056340e5a7d6f] dart::Profiler::DumpStackTrace(void*)
>testee>err>   [0x000056340e5a7d6f] dart::Profiler::DumpStackTrace(void*)
>testee>err>   [0x000056340e85c282] dart::Assert::Fail(char const*, ...)
>testee>err>   [0x000056340e307d46] Unknown symbol
>testee>err>   [0x000056340e4d0448] dart::Script::TokenRangeAtLine(long, dart::TokenPosition*, dart::TokenPosition*) const
>testee>err>   [0x000056340e41f0cf] dart::Debugger::BreakpointLocationAtLineCol(dart::String const&, long, long)
>testee>err>   [0x000056340e41f2bb] dart::Debugger::SetBreakpointAtLineCol(dart::String const&, long, long)
>testee>err>   [0x000056340e6335d2] Unknown symbol
>testee>err>   [0x000056340e628b3d] Unknown symbol
>testee>err>   [0x000056340e626059] dart::Service::InvokeMethod(dart::Isolate*, dart::Array const&, bool)
>testee>err>   [0x000056340e626ae3] dart::Service::HandleIsolateMessage(dart::Isolate*, dart::Array const&)
>testee>err>   [0x000056340e43cf1b] dart::IsolateMessageHandler::HandleMessage(dart::Message*)
>testee>err>   [0x000056340e4783fd] dart::MessageHandler::HandleMessages(dart::MonitorLocker*, bool, bool)
>testee>err>   [0x000056340e478e36] dart::MessageHandler::TaskCallback()
>testee>err>   [0x000056340e66aee1] dart::ThreadPool::Worker::Loop()
>testee>err>   [0x000056340e66a9bc] dart::ThreadPool::Worker::Main(unsigned long)
>testee>err>   [0x000056340e548ee5] Unknown symbol
>testee>err> -- End of DumpStackTrace

If this particular crash is fixed (Script::TokenRangeAtLine and KernelLineStartsReader::TokenRangeAtLine are changed to handle null source), observatory still crashes with exception:
NoSuchMethodError: The method '-' was called on null.
Receiver: null
Tried calling: -(0)
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:46:5)
#1      Script.getLine (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:3537:23)
#2      Script._addBreakpoint (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:3720:5)
#3      Breakpoint._update (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:2394:17)
#4      ServiceObject.updateFromServiceMap (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:401:5)
#5      Isolate.getFromMap (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:1499:11)
#6      _upgradeList (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:4789:23)
#7      _upgradeMap.<anonymous closure> (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:4778:7)
#8      __InternalLinkedHashMap&_HashVMBase&MapMixin&_LinkedHashMapMixin.forEach (dart:collection/runtime/libcompact_hash.dart:363:8)
#9      _upgradeMap (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:4774:7)
#10     _upgradeCollection (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:4767:5)
#11     Isolate._update (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:1642:5)
#12     ServiceObject.updateFromServiceMap (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:401:5)
#13     ServiceObject.reload.<anonymous closure> (file:...dart/sdk/runtime/observatory/lib/src/service/object.dart:359:11)

These crashes cause many service/* tests to fail in app-jit mode and may also cause sporadic timeouts on app-kernel-linux-debug-x64 bots.
/cc @a-siva @rmacnak-google

Do we have any preference whether we update the callers of Script::Source() to handle null properly or generate artificial sources from kernel? Without the actual source, I'm wondering if it would even be useful for the debugger to display any artificial source information.

I don't think we have a way to generate sources from kernel, I would think gracefully handling null would be the way to go.

@a-siva, I didn't think we did but just wanted to check. I'll look into where we aren't handling null properly with Script::Source().


fix: get OpenAI models only if OpenAI API Enabled; timeout for querying OpenAI models

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[x] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

fix: Bug fix or error correction

Changelog Entry
Description
See https://github.com/open-webui/open-webui/discussions/5292 for issue details(video included).
This PR ensure only fetch OpenAI models if ENABLE_OPENAI_API is false in Admin Connection tab.
Added timeout for fetching OpenAI models.
Fixed

Fetch OpenAI models only if OpenAI API Enabled
Add timeout for querying OpenAI models

Good catch, Thanks!


libfontconfig1 as dependency or supply one?

We have an application that needs to render fonts and does not run with adoptopenjdk until the libfontconfig1 package (debian) is installed. What would be the ideal solution?
Adding libfontconfig1 as package dependency for deb and rpm packages?
Add an own libfontconfig1 to adoptopenjdk tarballs like it is done with libfreetype?
I found out that the libfontconfig1 package needs libfreetype. I don't know how coupled they are. The adoptopenjdk tarballs and thus also the debian packages provide and use its own version of it. But the debian libfontconfig1 package depends on debians libfreetype package and thus adds a systemwide libfreetype library as well. When adoptopenjdk only uses libfreetype it uses its own one. When it uses libfontconfig then it uses the debian libfreetype from the debian package as well.

Personally, I'd rather see the OS packages use the OS dependencies than adding yet another bundled dependency. As a consequence, I'd like to drop libfreetype, too.
I've asked whether this would be possible on the #build channel on Slack because I don't know the answer.

What does Debian currently do in this space?

@aahlenst
Thank you for the asking in the Channel. As i have written, i don't know how coupled they are. The don't have many transitive dependencies:
https://packages.debian.org/stretch/libfreetype6
https://packages.debian.org/stretch/libfontconfig1
@karianna
Debian has a hard dependency to libfreetype6 AND libfontconfig even in the headless package:
https://packages.debian.org/stretch/openjdk-8-jre-headless
https://packages.debian.org/buster/openjdk-11-jre-headless
So that is no problem there. The headless package also depends on a lot of X11 packages.
The "headfull" package depends on the headless package and adds some more X11, font, audio, grahic library, etc. dependencies

Seems related: https://github.com/AdoptOpenJDK/openjdk-build/issues/693. https://github.com/AdoptOpenJDK/openjdk-build/issues/693#issuecomment-458694375 suggests replacing the shipped libfreetype plus depending on libfontconfig could solve the issue and not trigger additional problems.
But: I'm not comfortable adding those changes blindly, though. I want tests that exercise the critical codepaths. I'm happy to incorporate those, just pointing me to some failing code would be enough. Running some multi-platform with the AdoptOpenJDK packages installed on the respective OS tests that cover installer-specific changes is on my to-do list anyway.

I found a minimal example how to check font sizes with awt on stackoverflow and made a minimal executable of it:
import java.awt.Font;
import java.awt.font.FontRenderContext;
import java.awt.geom.AffineTransform;
class AWTestTSize {
public static void main(String[] args){
String text = "Hello World";
AffineTransform affinetransform = new AffineTransform();
FontRenderContext frc = new FontRenderContext(affinetransform,true,true);
Font font = new Font("Tahoma", Font.PLAIN, 12);
int textwidth = (int)(font.getStringBounds(text, frc).getWidth());
int textheight = (int)(font.getStringBounds(text, frc).getHeight());
}
}

With libfontconfig installed the program exits with 0 and without it exits with a NPE:
Exception in thread "main" java.lang.NullPointerException
	at sun.awt.FontConfiguration.getVersion(FontConfiguration.java:1264)
	at sun.awt.FontConfiguration.readFontConfigFile(FontConfiguration.java:219)
	at sun.awt.FontConfiguration.init(FontConfiguration.java:107)
	at sun.awt.X11FontManager.createFontConfiguration(X11FontManager.java:774)
	at sun.font.SunFontManager$2.run(SunFontManager.java:431)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.font.SunFontManager.<init>(SunFontManager.java:376)
	at sun.awt.FcFontManager.<init>(FcFontManager.java:35)
	at sun.awt.X11FontManager.<init>(X11FontManager.java:57)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.lang.Class.newInstance(Class.java:442)
	at sun.font.FontManagerFactory$1.run(FontManagerFactory.java:83)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.font.FontManagerFactory.getInstance(FontManagerFactory.java:74)
	at java.awt.Font.getFont2D(Font.java:491)
	at java.awt.Font.access$000(Font.java:224)
	at java.awt.Font$FontAccessImpl.getFont2D(Font.java:228)
	at sun.font.FontUtilities.getFont2D(FontUtilities.java:180)
	at sun.font.StandardGlyphVector.initFontData(StandardGlyphVector.java:1126)
	at sun.font.StandardGlyphVector.init(StandardGlyphVector.java:1115)
	at sun.font.StandardGlyphVector.<init>(StandardGlyphVector.java:172)
	at java.awt.Font.getStringBounds(Font.java:2421)
	at java.awt.Font.getStringBounds(Font.java:2331)
	at AWTestTSize.main(AWTTestSize.java:12)

Related: https://github.com/AdoptOpenJDK/openjdk-build/issues/682

@nudgegoonies Thanks for the code.
For reference, I've checked Zulu 8. They don't bundle freetype with their tar.gz. And they specify freetype and fontconfig as required dependencies for their prebuilt packages.

Any news about the supplied freetype? It would be great to have the dependency correct in the new 8u222, 11.0.4, 12.0.2 and 13.0.0 Versions.

The fix should be ready for 13 (and at the same time for all other versions). Needs extensive testing and I haven‘t found the time yet. The plan is to strip freetype from all Linux builds and releases (even tarballs).

Thank you for the answer. Very good. I know, that needs a lot of testing. But is this not part of the TCK tests during the build of the tarballs?

Thank you for the answer. Very good. I know, that needs a lot of testing. But is this not part of the TCK tests during the build of the tarballs?

 The bundled freetype isn't an invention of AdoptOpenJDK but the upstream OpenJDK. Ideally, we replace freetype before running the test suite.

FYI - It's unlikely we'll make this decision so close to the next quarterly release.

Ok, thank you for that explantation.

I will adjust the branch according to the decision by adding libfreetype to my MR or removing both libfreetype and libfontconfig.

Does setting the milestone to "October 2019" mean, we may expect this PR to be merged this month?

No, that does not mean it. Martijn just does this every month.
It's not moving forward because I'm completely swamped with work. What's needed to make some progress:

Take an empty machine (VM, container, whatever) without any dependencies, especially without libfontconfig and libfreetype, put our binary builds (not a Linux package) onto them and run the AdoptOpenJDK test suite on it. Are there any font-related test errors? If not, see that tests are added to the test suite that cover this because we currently have problems without libfontconfig.
On the same machine, remove the bundled libfreetype from binary builds. Install the distribution package for libfreetype, libfontconfig and run the test suite. Everything green? Then I'm happy to merge this pull request plus remove the bundled libfreetype. Otherwise we have to investigate further.

Should be tested at least with JDK 8, 11 and 13.

Superseded by #282.

Superseded by #282.


fix: bug with : and invalid searches

Closes #41 thanks for the report!
Could you test it on your system @krfl ?

Spamming ::::::::: still causes it to seemingly hang or become blocked. All completions seem to be blocked for a while and then suddenly starts working again after 5-15 seconds or so.

Spamming ::::::::: still causes it to seemingly hang or become blocked. All completions seem to be blocked for a while and then suddenly starts working again after 5-15 seconds or so.

Thanks! I'm able to reproduce with that rather insane ;) test input :)
I've added timeouts to all completion requests now, should be more solid even if a few weird searches slip through (like searching for a : user)

3e4e17e did the trick. I'm unable to crash it with previously used methods.


Cannot view status of a single running container despite others working fine

Bug description
All containers are running fine, except for the nginx one as shown in the screenshot below.  The container itself is running fine, has been for two years, and used to be shown normally in the portainer UI.
docker container ls | grep nginx                                                                            [±master ●]
6ad0fbf71b12        numat/nginx                     "nginx -g 'daemon of…"   2 years ago         Up 8 months             <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:443->443/tcp         nginx

The problem has persisted through a 2.9.3 -> 2.11.0 upgrade.
It's possible this is actually a docker bug, since various docker commands (such as docker exec or docker container logs) hang.  HOWEVER, in that case I would expect portainer to report e.g. that is cannot communicate with docker.
Expected behavior
If a portainer bug: I expect the container status to be shown normally.
If a docker bug: I expect portainer to report a more useful container status.
portainer logs

level=info msg="2021/12/13 17:25:02 [INFO] [internal,ssl] [message: no cert files found, generating self signed ssl certificates]"
2021/12/13 17:25:02 server: Reverse tunnelling enabled
2021/12/13 17:25:02 server: Fingerprint dc:89:db:15:e1:95:fc:b7:62:47:b9:2b:4a:8c:0c:7d
2021/12/13 17:25:02 server: Listening on <IP_ADDRESS>:8000...
level=info msg="2021/12/13 17:25:02 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]"
level=info msg="2021/12/13 17:25:02 [INFO] [cmd,main] Starting Portainer version 2.11.0"
level=info msg="2021/12/13 17:25:02 [DEBUG] [internal,init] [message: start initialization monitor ]"
level=info msg="2021/12/13 17:25:02 [INFO] [http,server] [message: starting HTTPS server on port :9443]"
level=info msg="2021/12/13 17:25:02 [INFO] [http,server] [message: starting HTTP server on port :9000]"
level=info msg="2021/12/13 17:25:07 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)"
level=info msg="2021/12/13 17:25:07 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)"
level=info msg="2021/12/13 17:25:07 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)"
level=info msg="2021/12/13 17:25:07 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)"
level=info msg="2021/12/13 17:25:20 [DEBUG] [internal,init] [message: canceling initialization monitor]"
level=info msg="2021/12/13 17:25:20 [DEBUG] Shutting down tunnel service"
level=info msg="2021/12/13 17:25:20 [DEBUG] [http,server] [message: shutting down http server]"
level=info msg="2021/12/13 17:25:20 [DEBUG] [internal,snapshot] [message: shutting down snapshotting]"
level=info msg="2021/12/13 17:25:20 [DEBUG] [http,server] [message: shutting down http server]"
level=info msg="2021/12/13 17:25:20 [DEBUG] Stopping scheduler"
level=info msg="2021/12/13 17:25:20 [INFO] [cmd,main] Http server exited: http: Server closed"
level=info msg="2021/12/13 17:25:20 [DEBUG] [internal,init] [message: start initialization monitor ]"
level=info msg="2021/12/13 17:25:20 [DEBUG] [internal,init] [message: shutting down initialization monitor]"
2021/12/13 17:25:20 server: Reverse tunnelling enabled
2021/12/13 17:25:20 server: Fingerprint 3f:24:e7:a2:f2:f6:0f:9b:8b:46:7b:0f:a8:7a:49:a5
2021/12/13 17:25:20 server: Listening on <IP_ADDRESS>:8000...
level=info msg="2021/12/13 17:25:20 [INFO] [cmd,main] Starting Portainer version 2.11.0"
level=info msg="2021/12/13 17:25:20 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]"
level=info msg="2021/12/13 17:25:20 [DEBUG] [internal,init] [message: start initialization monitor ]"
level=info msg="2021/12/13 17:25:20 [INFO] [http,server] [message: starting HTTPS server on port :9443]"
level=info msg="2021/12/13 17:25:20 [INFO] [http,server] [message: starting HTTP server on port :9000]"
level=info msg="2021/12/13 18:07:51 http error: Unable to proxy the request via the Docker socket (err=context canceled) (code=500)"
level=info msg="2021/12/13 18:43:45 http error: Unable to proxy the request via the Docker socket (err=context canceled) (code=500)

Steps to reproduce the issue:

Go to the list of containers.
Click on the container in question.

Technical details:

Portainer version: 2.11.0
Docker version 18.09.0, build 4d60db4 (not managed by portainer)
Platform (windows/linux): Linux server 4.15.0-140-generic #144-Ubuntu SMP Fri Mar 19 14:12:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Command used to start Portainer (docker run -p 9443:9443 portainer/portainer):
Browser: Chrome 96.0.4664.93
Use Case: Using Portainer in a Commerical setup.
Have you reviewed our technical documentation and knowledge base? Yes, docs and github issues

@edgardgomez

@alexrudd2
Thanks for raising this issue. I can not re-produce this in my test env at this stage.
Can you please open Developer Tools in your browser and look for any errors when clicking on. that specific container.

The container page has no console errors.  Clicking on any of [Logs], [Inspect], [Stats], etc gives:
stateService.ts:524 Transition Rejection($id: 0 type: 6, message: The transition errored, detail: Error: Param values not valid for state 'docker.containers.container.logs'. Invalid params: [ id ])
_defaultErrorHandler @ stateService.ts:524
stateService.ts:526 Error: Param values not valid for state 'docker.containers.container.logs'. Invalid params: [ id ]
    at r (invalidTransition.ts:15)
    at e.invokeHook (transitionHook.ts:93)
    at Function.e.invokeHooks (transitionHook.ts:230)
    at e.run (transition.ts:693)
    at e.transitionTo (stateService.ts:371)
    at e.go (stateService.ts:261)
    at stateDirectives.ts:76
    at angular.js:21661
    at Qr.completeTask (angular.js:21299)
    at angular.js:6879
_defaultErrorHandler @ stateService.ts:526

@alexrudd2
I'll forward the error message to our engineering, they might be able to shed some light on what is happening.
Meanwhile, can you try access Portainer from a different browser or incognito window to see if the same happens.
Thanks

The browser makes no difference (tried Chrome incognito and Safari), and unfortunately as stated docker container logs hangs.  Thanks!

Thanks Alex,
It does seem to be an issue with logs (as the error suggests). I understand that the container is up for a long time and working fine as such, if it's possible please restart the container to see if it helps clear the issue with logs.

The container was stuck so bad I had to kill -9 the underlying process (thanks TeddyBailey at StackOverflow), rebuild the image, and create a new container.  Now everything is working fine.
As I put in the initial report, my expected behavior for portainer would be a more useful display.  "Cannot communicate with container" perhaps? graying out the Start button?  error messages when clicking on links instead of silent failures?  I notice that on an initial page load of a working container, for a split-second the screen looks exactly like my screenshot of the stuck container.  So it looks like the UI state could be "reproduced" by simply not giving the UI refresh scripts any data.


ipset v7.1: Kernel and userspace incompatible

Description
After upgrade to Typhoon v1.23.0 (upstream) Calico v3.21.2 is crash looping with
[ERROR][4764] felix/ipsets.go 574: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v7.1: Kernel and userspace incompatible: settype hash:ip,port with revision 6 not supported by userspace.\n"

Pod to pod communication is broken.
Expected behavior
Calico is not crashing. Pod to pod communication works.
Environment

Platform: bare-metal
OS: fedora-coreos 35.20211029.3.0
Release: Typhoon v1.23.0 (upstream) 39da5b5

Possible Solution
Waiting with the release of Typhoon v1.23.0 until Calico v3.22.0 is released.
Incompatible ipset protocol version (7) will cause problems

Yes, I'm already aware of this. Also I've not released Typhoon v1.23 yet, please use the current release v1.22.4.

Closing, as it was just a heads-up.

Thanks for the heads up

@dghubble Calico v3.22.1 was released (https://github.com/projectcalico/calico/issues/5011), at least for amd64. Will Typhoon update the dependency? Probably after the fix will also be released for arm?


⚠ SceneTime has degraded performance

In f6b167f, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1426 ms

Resolved: SceneTime performance has improved in 51ff00a after 7 minutes.


Core setting "Scrolling Status Text" is ignored by _onUpdate in dnd5e.mjs

A check should be added here:
https://github.com/foundryvtt/dnd5e/blob/077da87dab22b9b50e234ff0ecc496408ceb0af8/dnd5e.mjs#L9719
Or here:
https://github.com/foundryvtt/dnd5e/blob/077da87dab22b9b50e234ff0ecc496408ceb0af8/dnd5e.mjs#L9731

That check is already being performed by core inside createScrollingText, so the system doesn't need to do anything.


Step 8.1 missing code

Make the Send button context-aware step in 8 of the Building Beautiful UIs with Flutter is missing a line of code.
The message list is missing, see code:
class ChatScreenState extends State<ChatScreen> with TickerProviderStateMixin {
  final TextEditingController _textController = new TextEditingController();
 bool _isComposing = false;
should be:
class ChatScreenState extends State<ChatScreen> with TickerProviderStateMixin {
  final TextEditingController _textController = new TextEditingController();
  final List<ChatMessage> _messages = <ChatMessage>[];
 bool _isComposing = false;

Thanks so much, @tiborrr, for reporting that bug! Thanks for adding that line, @Hixie!
Fixed.


In a newly created SAML app subject attribute field shows an invalid value in console app

Describe the issue:
By default the subject attribute field of SAML application is not set, the user_id will be taken. When viewing the subject attribute field of a newly created saml app from the console app, it says subject attribute=username. The persistant data record and the management console also says the subject attribute field is not set.
Update: It is the BE API that sends the username as subject attribute.
console app:

management console:

How to reproduce:

create a new saml application from the console (any console) (do not set the subject attribute)
login to console app
view the newly created saml app
go to user attribute section
view subject attribute field

Expected behavior:
Should display its is not set.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 6.0.0
OS: macOS 12.5
Database: MSSQL, H2
Userstore: LDAP, JDBC

Optional Fields
Related issues:

Suggested labels:

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Old version of configmap-reload referenced

Looking at this line it appears the configmap-reload and digging into the quay repo it appears the image is 2y old. Implies the running binary contains some CVE's that have recently been patched in Go.
https://github.com/coreos/prometheus-operator/blob/master/bundle.yaml#L117
Should this be updated to the version below or a new build generated and re-pushed (e.g. 0.2.1-go112)?
https://hub.docker.com/r/jimmidyson/configmap-reload/tags

Could you do a pull request replacing it with the latest upstream image? If tests just pass I'm happy to bump it, and remove us having to sync with upstream.

Fixed by #2952


100 instances of each resource

Generation of 100 instances of each resource for some users

added program to generate 100 instances of each resource for a few random users
- users selected from a sample list
added test cases

All commits must have sign off not just one commit.


Move out of deislabs organization

As part of the acceptance of our CNCF sandbox application, we are moving out of the deislabs github organization into one that we created a while back just for this purpose: https://github.com/getporter/
Our larger set of tasks for the application is being tracked in https://github.com/cncf/toc/issues/533.
https://docs.github.com/en/github/administering-a-repository/transferring-a-repository

[ ] Create teams in the new organization that reflect our current teams:

@deislabs/porters -> @getporter/contributors - Members of this group have merged a PR and can have issues assigned to them and be mentioned.
@deislabs/porter-contributor -> @getporter/TBD - Members of this group have helped for a while and have triage rights so that they can apply labels. We are still working on this role and how to make it useful with github's permissions honestly. There's more work to be done here.
@deislabs/porter-maintainers -> @getporter/maintainers - Members of this group have maintainer on the repositories. They can merge pull requests.
@deislabs/porter-admins -> @getporter/admins - Members of this group have admin on the repositories and can modify dangerous repository settings.

[ ] Invite members of old teams to new teams.
[ ] Transfer repositories, removing the porter prefix. For example, deislabs/porter-packages becomes getporter/packages. The main repo keeps the same name, deislabs/porter -> getporter/porter.
[ ] Edit netlify /src redirects to to go to the new github organization. These redirect https://porter.sh/src/CODE/PATH to a github code file.
[ ] Find raw github paths and swap them for the netlify /src redirects when possible as that is easier to manage, especially on the website.
[ ] Update porter-vanity to use new organization. This is used by the go client when locating our source code. This organization move is why we have a vanity import path, get.porter.sh, so that we don't need to update code.
[ ] Update text on all assets to change to new organization.
[ ] Update builds on Azure Pipelines to reference new repository locations. Pretty sure we can't "update" and it actually is delete job, recreate from relocated repo.

Create new pipelines org, getporter
Look into import/export
Recreate and attach variable group

pretty sure Azure Pipelines is a delete/recreate as well as it's based off the org name and it would change based on location. Leaving it even if it works might be problematic.

Ah okay yeah makes sense. I'll make a new pipelines org called getporter and recreate them there.

@vdice By assets I just meant URLs, github markdown, website text, etc. I think this is covered by everything you have been doing for the past few days so when you think you are done, feel free to close.

Although some PRs still await reviews, all the work in this ticket has been implemented!  Closing.


Bounty: fix links

@MCSH Fixed links.

Can you fix the file conflicts @Tyson-a

Hey @Tyson-a, we are going to close this pr because there is a bug. We will rewarding you the points and doing the changes ourselves.


nixos/bitwarden_rs: add test

Motivation for this change
The bitwarden ecosystem is currently untested in NixOS, and the server (bitwarden-rs) is somewhat important for those that rely on it.
This test provides coverage for all three database backends of bitwarden_rs, as well as bitwarden_rs-vault under Firefox and bitwarden-cli. The electron client bitwarden remains untested.
My original goal was to just use the cli, but it does not support account creation, so I ended up using webdriver to interact with the web UI. This approach is borrowed from nixos/tests/nginx-etag.nix. I expect that this will break at some point if the web UI is heavily modified -- I have added myself as maintainer to signal my intention to fix breakages.
As I note in a comment, the same tests should work without modification on the official bitwarden server, if we ever package that. (#51212).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@ofborg test nixosTests.bitwarden

@ofborg test nixosTests.bitwarden.sqlite nixosTests.bitwarden.postgresql nixosTests.bitwarden.mysql

@ofborg test bitwarden

@ofborg test bitwarden.sqlite bitwarden.mysql bitwarden.postgresql


Issue when hovering over map region

There is an issue when hovering over map that is contained inside another region. Seems like regression as it was working in ECharts 2.x.
Example (ECharts 3.1.7):

Note that "Praha" region can't be selected on hover as soon as another region is already hovered.
Example (ECharts 2.x)

This example works as expected.
GeoJSON used: https://gist.githubusercontent.com/jarben/6fe145bc8db35063638060666a3118cf/raw/dba59a4e186ef54e97ae541e69ed276582d7a818/czech_geo_example

Any chance to fix this one @pissang?

Hi @jarben, I will try to locate the problem.

Thank you @pissang, looks like the mouseenter can't be triggered without mouseleave from previous region? Which happens when region is nested.. Thanks for looking at it..

Sorry @pissang, any update on this one?

Hi @jarben. It's a "point in path" bug in zrender. Fixed it and it will be right in next version. Sorry for the late replay

Hi @pissang , that's great this is fixed now, thanks heaps!


unison: build 2.51.3 with ocaml 4.12

Add patch which fixes builds with (at least) ocaml 4.12.0, and
remove build constraint for 4.09. Fixes interop with unison
built with ocaml 4.12.

Motivation for this change
unison in nixpkgs is currently built with ocaml 4.09, but when built against ocaml 4.09, unison is
not compatible with unisons built with ocaml 4.12. Unpatched unison 2.51.3 does not build
with ocaml 4.12, but there is a patch which allows unison 2.51.3 to be built with ocaml 4.12.
This PR applies that patch and also removes the ocaml 4.09 restriction. The resulting
unison has been tested successfully against unison 2.51.3 installed with Homebrew on MacOS 11
(the patch was found in the Homebrew recipe).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 127310 at 7282b4fc run on aarch64-linux 1

2 packages built successfully:

unison
usync

Should this be backported to 21.05?

On Jun 24, 2021, at 4:02 AM, Vincent Laporte @.***> wrote:
Should this be backported to 21.05?

I would say so, yes. Looks like that's being done -- thank you. --Michael


Add support for needsOffscreenAlphaCompositing on iOS

Currently on iOS in UIKit and in RN all views are by default set to allowsGroupOpacity=true. Any view that has all of the following

allowsGroupOpacity set to true
opacity greater than 0.0 and less than 1.0
have any subviews

will be rendered off screen (on CPU). See this link for more details.  Which means performance will be decreased and may affect the user experience. Therefore it makes sense to allow the developers to override this property.
This pull request allows for changing allowsGroupOpacity via needsOffscreenAlphaCompositing. Android already supports this. This is not a new name or variable. See https://facebook.github.io/react-native/docs/view.html#needsoffscreenalphacompositing.
Test Plan

var styles = StyleSheet.create({
  alphaCompositing: {
    justifyContent: 'space-around',
    width: 100,
    height: 50,
    borderRadius: 100,
  },
});

class OffscreenAlphaCompositing extends React.Component<{}, $FlowFixMeState> {
  state = {
    active: false
  };

  render() {
    return (
      <TouchableWithoutFeedback onPress={this._handlePress} >
        <View>
          <Text style={{paddingBottom: 10}}>Blobs</Text>
          <View style={{opacity: 1.0, paddingBottom: 30}} needsOffscreenAlphaCompositing={this.state.active} >
            <View style={[
              styles.alphaCompositing,
              {marginTop: 0, marginLeft: 0, backgroundColor: '#FF6F59'}
            ]}>
            </View>
            <View style={[
              styles.alphaCompositing,
              {marginTop: -50, marginLeft: 50, backgroundColor: '#F7CB15'}
            ]}>
            </View>
          </View>
          <Text style={{paddingBottom: 10}}>Same blobs, but their shared container have 0.5 opacity</Text>
          <Text style={{paddingBottom: 10}}>Tap to {this.state.active ? "activate" : "deactivate"} needsOffscreenAlphaCompositing</Text>
          <View style={{opacity: 0.8}} needsOffscreenAlphaCompositing={this.state.active} >
            <View style={[
              styles.alphaCompositing,
              {marginTop: 0, marginLeft: 0, backgroundColor: '#FF6F59'}
            ]}>
            </View>
            <View style={[
              styles.alphaCompositing,
              {marginTop: -50, marginLeft: 50, backgroundColor: '#F7CB15'}
            ]}>
            </View>
          </View>
        </View>
      </TouchableWithoutFeedback>
    );
  }

  _handlePress = () => {
    this.setState({active: !this.state.active});
  };
}

Related PRs
https://github.com/facebook/react-native-website/pull/343
Release Notes
On iOS allowsGroupOpacity can be set via needsOffscreenAlphaCompositing
[IOS][FEATURE][View] - Added support for needsOffscreenAlphaCompositing

@hfossli CI has been in a pretty bad shape lately sorry about that, the failure is probably not related to your changes.


density() datalimits do not adjust for different columns

The density() function by default works in the minimal data space.
But when I want to plot per columns the values of all the columns are being considered.
using RDatasets, AlgebraOfGraphics
AoG = AlgebraOfGraphics
set_aog_theme!()

iris = dataset("datasets", "iris")

props = filter(!=(:Species),propertynames(iris))[:,:]

The behavior of AoG:
let
	plt = data(iris) * AoG.density() * mapping(props, col=dims(1), color = :Species)
	draw(plt)
end

But if I plot each column discrete and then plot the result I get the desired output
let
	fig = Figure()
	plts = [data(iris) * (mapping(prop, color = :Species)) * AoG.density() for prop in props]
	[draw!(fig[1,i], plts[i]) for i in 1:length(props)]
	fig
end

I think the first case should generate something similar to the second case.

By design the data limits of the density are computed over the whole data. If you want to only show the density within the extrema of the data (on a group by group basis), you can use
AoG.density(datalimits=extrema)

instead. (You would also need to unlink the axes of the facet to get the second plot with a unique call.)