text:
(maint) Windows 2003 registry test fails

Changes were introduced in b46ede7
to work around string encoding issues discovered internal to
Ruby 2.1.5 Registry handling.  Additional tests were added to
demonstrate the behavior around round-tripping Unicode characters
properly.  Interestingly, this test caused a test failure only
in Windows 2003.

On Windows 2003, the following behavior was observed:

Calls to create generated registry keys under
HKLM\SOFTWARE\Wow6432Node
This is equivalent to passing KEY_WOW64_32KEY to RegCreateKeyEx

Calls to open try to open registry keys under
HKLM\SOFTWARE
This is equivalent to passing KEY_WOW64_64KEY to RegOpenKeyEx

This generates a test failure because the key created is not the same
one that the code later attempts to open, and hence the handle is
invalid, and the key cannot be deleted.
Strangely, other operating systems do not encounter this behavior,
which may mean that advapi32.dll has different default values for
the registry redirection configuration values with Windows 2003.
The fix here is to always specify the 0x200 / KEY_WOW64_32KEY to
be explicit about opening the same key.

Prior to Merge
Windows 2003 R2 x64 + SP2
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\puppet>ruby --version
ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]

ruby.exe	2576	RegCreateKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	2576	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	KeySetInformationClass: KeyWow64FlagsInformation, Length: 4, Wow64Flags: 0x1
ruby.exe	2576	RegSetValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\570a3507-b687-40e2-b74a-2831a94b4695	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2576	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	2576	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 0, Length: 288
ruby.exe	2576	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	2576	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Index: 0, Name: 570a3507-b687-40e2-b74a-2831a94b4695, Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2576	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\570a3507-b687-40e2-b74a-2831a94b4695	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2576	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\570a3507-b687-40e2-b74a-2831a94b4695	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2576	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 1, Length: 220
ruby.exe	2576	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	2576	RegOpenKey	HKLM\SOFTWARE\Puppet Labs\PuppetRegistryTest	NAME NOT FOUND

Windows 2012 R2 x64 + Ruby 2.1.5 x86
C:\Users\ADMINI~1\AppData\Local\Temp\puppet>ruby --version
ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]

ruby.exe	1668	RegCreateKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Desired Access: Read/Write, Create Link
ruby.exe	1668	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
ruby.exe	1668	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: HandleTags, HandleTags: 0x400
ruby.exe	1668	RegSetValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\a2b16ee6-c88d-49c5-bddb-536b66d81775	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1668	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	1668	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 0, Length: 288
ruby.exe	1668	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	1668	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Index: 0, Name: a2b16ee6-c88d-49c5-bddb-536b66d81775, Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1668	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\a2b16ee6-c88d-49c5-bddb-536b66d81775	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1668	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\a2b16ee6-c88d-49c5-bddb-536b66d81775	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1668	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 1, Length: 220
ruby.exe	1668	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	1668	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Desired Access: Delete
ruby.exe	1668	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
ruby.exe	1668	RegDeleteKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	1668	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS

With Patch
Windows 2003 R2 x64 + SP2 + Ruby 2.1.5 x86
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\puppet>ruby --version
ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]

ruby.exe	1848	RegCreateKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	1848	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	KeySetInformationClass: KeyWow64FlagsInformation, Length: 4, Wow64Flags: 0x1
ruby.exe	1848	RegSetValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\40ef107a-02b1-41be-904c-250fbc71ff9f	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1848	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	1848	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 0, Length: 288
ruby.exe	1848	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	1848	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Index: 0, Name: 40ef107a-02b1-41be-904c-250fbc71ff9f, Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1848	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\40ef107a-02b1-41be-904c-250fbc71ff9f	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1848	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\40ef107a-02b1-41be-904c-250fbc71ff9f	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	1848	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 1, Length: 220
ruby.exe	1848	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	1848	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	1848	RegDeleteKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	1848	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS

Windows 2012 R2 x64 + Ruby 2.1.5 x86
C:\Users\ADMINI~1\AppData\Local\Temp\puppet>ruby --version
ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]

ruby.exe	2588	RegCreateKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Desired Access: Read/Write, Create Link
ruby.exe	2588	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
ruby.exe	2588	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: HandleTags, HandleTags: 0x600
ruby.exe	2588	RegSetValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\22e9888f-01d9-41ef-a4b0-eb7b17fe00ba	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2588	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	2588	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 0, Length: 288
ruby.exe	2588	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	2588	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Index: 0, Name: 22e9888f-01d9-41ef-a4b0-eb7b17fe00ba, Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2588	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\22e9888f-01d9-41ef-a4b0-eb7b17fe00ba	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2588	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\22e9888f-01d9-41ef-a4b0-eb7b17fe00ba	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	2588	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 1, Length: 220
ruby.exe	2588	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	2588	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Desired Access: Delete
ruby.exe	2588	RegDeleteKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	2588	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS

Windows 2012 R2 x64 + Ruby 2.1.5 x64
C:\Users\ADMINI~1\AppData\Local\Temp\puppet>ruby --version
ruby 2.1.5p273 (2014-11-13 revision 48405) [x64-mingw32]

ruby.exe	836	RegCreateKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Desired Access: Read/Write, Create Link
ruby.exe	836	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
ruby.exe	836	RegSetValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\0068c98a-d927-4cf9-844a-4ace388bfa17	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	836	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	836	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 0, Length: 288
ruby.exe	836	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Query: Cached, SubKeys: 0, Values: 1
ruby.exe	836	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Index: 0, Name: 0068c98a-d927-4cf9-844a-4ace388bfa17, Type: REG_SZ, Length: 6, Data: –™
ruby.exe	836	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\0068c98a-d927-4cf9-844a-4ace388bfa17	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	836	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest\0068c98a-d927-4cf9-844a-4ace388bfa17	SUCCESS	Type: REG_SZ, Length: 6, Data: –™
ruby.exe	836	RegEnumValue	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	NO MORE ENTRIES	Index: 1, Length: 220
ruby.exe	836	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	836	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS	Desired Access: Delete
ruby.exe	836	RegDeleteKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS
ruby.exe	836	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Puppet Labs\PuppetRegistryTest	SUCCESS

Ok @joshcooper, I'm happy with the validation results here.  The only explanation for the differing behavior under Windows 2003 are internal defaults for RegCreateKeyEx and RegOpenKeyEx when REGSAM is left unspecified.

/cc @ferventcoder

CLA signed by all contributors.

This can't be merged until RC1 packages ship and merges are allowed against Puppet master branch.

RC1 packages tagged and ready to go, feel free to merge now.

:+1:

authors: Iristyle joshcooper puppetcla

repo: puppetlabs/puppet


text:
(maint) Remove F20 from build targets

Fedora 20 is now EOL, so we should no longer be building packages for
it.

Wheee, fun appveyor failure! But, unrelated to this PR.

source: gharchive/pull-request

authors: kylog melissa

license_type: permissive

license_source: github-api


text:
Pup 7046 update dnf provider

The dnf provider will only work with a pre-defined list of Fedora releases.  To avoid having to update this provider every time there is a new Fedora release this patch updates the defaultfor argument to a range which will work until Fedora 31 is released.

CLA signed by all contributors.

@Iristyle I agree it would be better to avoid using version numbers since they often change and this issue will just come back later.  I'll have to do some testing to see if the :feature option will work.

@Iristyle Looks like :feature doesn't work in puppet 4.2.1, I'm getting an error when I run the agent as follows.
Error: Could not autoload puppet/provider/package/dnf: undefined local variable or method supports_dnf' for Puppet::Type::Package::ProviderDnf:Class
Did you mean?  supports_parameter?
Error: Could not retrieve local facts: Could not autoload puppet/provider/package/dnf: undefined local variable or method supports_dnf' for Puppet::Type::Package::ProviderDnf:Class                                                                                Did you mean?  supports_parameter?                                                                                Error: Failed to apply catalog: Could not retrieve local facts: Could not autoload puppet/provider/package/dnf: undefined local variable or method supports_dnf' for Puppet::Type::Package::ProviderDnf:Class
Did you mean?  supports_parameter?`

Apparently the string has to be quoted.  I changed the defaultfor line to look like this and puppet is working now.
defaultfor :operatingsystem => :fedora, :feature => 'supports_dnf'

I've updated the file as suggested.  dnf should now be used as the default provider on any platform that supports it.

CLA signed by all contributors.

@blackknight36 looks like you still need to add the actual supports_dnf feature, similar to how it's done here: https://github.com/puppetlabs/puppet/blob/937505096316f2389d5ba0c7f13b3da4eef36e0f/lib/puppet/feature/base.rb#L11-L14
IIRC, in tests we used which dnf to determine if dnf was the suitable provider, but it's been a while and you may need a more robust check (or not, not sure) :)

See also https://github.com/puppetlabs/puppet/pull/5069

@blackknight36 did yo mean to close this?

@joshcooper Yeah, I just can't figure out how to make this work.  Adding a feature really only moves the problem to another class, there would still be a need to determine which Fedora release is being used, we can't just assume dnf should be the default just because it is installed.  What happens when Fedora switches from dnf to something else?  etc. etc.

authors: blackknight36 joshcooper puppetcla whopper


text:
(PUP-6405) Use pip freeze --all

https://tickets.puppetlabs.com/browse/PUP-6405
This pull request adds management of the "core" pip packages. The current special case only handles the pip package while this pull request will take care of all the others.
I would feel better if I receive confirmations about a few topics:

Someone double check the unit tests: I am not experienced in Ruby.
Make sure version 8.1.0 of pip is really the one that implemented the freeze --all option: the jira issue explains more why I am confused about this.

CLA signed by all contributors.

authors: SamK puppetcla


text:
(PUP-7366) Fail when hiera_xxx methods are called with dotted key

Hiera 3 would fail if a key containing unquoted dots was used in a call
to hiera_array, hiera_hash or hiera_include. This commit reinstates
that failure to ensure backward compatibility.

CLA signed by all contributors.

authors: puppetcla thallgren


text:
(PUP-5800) Don't file expand uniquefile's prefix

Uniquefile is based on Ruby's Tempfile and it was already fixed in Ruby[1]
[1] https://github.com/ruby/ruby/commit/6f8bce9eff15b527c87e1b13312db2fbf0b504f4

jenkins please test this on redhat7-64a,windows2019-64a with servertests


text:
Update regexp for rabbitmq_nodename fact

rabbitmqctl status returns node status without trailing points
on rabbitmq: 3.6.10, e.g:
root@rabbitmq:~# rabbitmqctl status
Status of node rabbit@rabbitmq
[{pid,16527},
....
So let's align regexp as well

This is definitely needed. @SergK Can you check the tests?
This PR could be related to https://tickets.puppetlabs.com/browse/MODULES-3376

@baurmatt I'd love to merge this PR, but the first step - we need to merge fix for CI https://github.com/puppetlabs/puppetlabs-rabbitmq/pull/546 and after rebase this PR become green. So I need at least some feedback from core reviewers

btw, we can merge https://github.com/puppetlabs/puppetlabs-rabbitmq/pull/548 as well to fix CI

@hunner could you please review and comment, thank you

authors: SergK baurmatt

repo: puppetlabs/puppetlabs-rabbitmq

license_source: bigquery


text:
It is a Blank Window

Issue Templates

Search the currently opened issues and past issues before posting a new one.
Escalate issues by making a reaction of :+1: at the first comment on the issue (the issue author's)
Be clear and try to open one issue for one problem at a time (open multiple issues if you have multiple problems :sob:)
@include the people :family: who are maintaining the repo or a feature to bring them to focus if there are excessive delays :alarm_clock:
Include the console logs from the app if there are any errors.

Let me check it on my end again. Are you using a newer version of nwjs to test it out?

Let me check it on my end again. Are you using a newer version of nwjs to test it out?

@taomylife521 can you also tell me the nwjs version?

@taomylife521 can you also tell me the nwjs version?

source: gharchive/issue

repo: puranjayjain/youtube-dl-gui

license: MIT


text:
Tweaks for v1

Use type (~>)  in a few more places
Rename mapF to hoistFree
Rename liftCoyonedaT to hoistCoyoneda
Add hoistYoneda

This can be updated again if the purescript/purescript-control#30 proposal goes ahead, as the hoists can be defined in class instances instead.

👍 Looks great!

Core tests still passing FYI.

repo: purescript/purescript-free


text:
Generalizes callCC to be rank 2

See: https://github.com/purescript/purescript-transformers/issues/73

Looks good to me! Unfortunately this'll be a breaking change so we'll probably hold off releasing it for a little while, since there are some other breaking changes in the core libraries that need to go out, and it would probably be good to put them all out in one go.

authors: garyb jqyu

repo: purescript/purescript-transformers


text:
Zoho Provider implementation

Description
Implementation of the Zoho OAuth provider.
Motivation and Context
We use Zoho products so we need this provider
How Has This Been Tested?
Tested on Centos 7 server and currently being used on production.
Checklist:

[X] My change requires a change to the documentation or CHANGELOG.
[X] I have updated the documentation/CHANGELOG accordingly.
[X] I have created a feature (non-master) branch for my PR.

@JoelSpeed i tryed the OIDC but could not make it work as intended. Zoho doesn't support open id and i need to get the email address from the token.
Should i retry using Oidc in a different way?

@smiziara I think you're right. If they do not support OpenID in the scope then you will indeed need a separate provider for this. I will review what you've done
@syscll @steakunderscore WDYT of this? Also, we really really need to set up a better way to handle providers to make this easier

authors: JoelSpeed smiziara


text:
unistd.h:10:16: fatal error: io.h: No such file or directory

Hello,
I run "git clone --recursive https://github.com/pushkalkatara/darknet_ros.git"
and then "catkin bt", but I've got this error.
"ros/src/darknet_ros_prv/darknet/src/unistd.h:10:16: fatal error: io.h: No such file or directory
compilation terminated."
Do you have any idea ?
(I use ros-kinetic on ubuntu16.04)

Hi,
Simple removing the unistd.h from darknet solves the issue.
cd darknet_ros
cd darknet/src
rm -rf unistd.h

It works. Thank you !

authors: nyxrobotics pushkalkatara


text:
Add DeleteResolver and DefaultDeleteResolver

Closes #99
@nikitin-da please review carefully

To prevent compatibility issues, if we will want — we'll be able to open
constructor later
сб, 14 марта 2015, 15:40, Dmitrii Nikitin notifications@github.com:

Merged #111 https://github.com/pushtorefresh/storio/pull/111.
—
Reply to this email directly or view it on GitHub
https://github.com/pushtorefresh/storio/pull/111#event-253612461.

repo: pushtorefresh/storio


text:
⚠ Plex has degraded performance

In 471e056, Plex ($SITES_URL_PLEX) experienced degraded performance:

HTTP code: 523
Response time: 3344 ms

Resolved: Plex performance has improved in 10273f6 after 40 minutes.


text:
Update page title on navigation

Show what cipher you're looking at i.e.
Puzztool - Braille
Puzztool - Morse
etc.
Right now all pages just show "Puzztool".

Does this mean the title in the tab or the title on the page itself, I realize now it's not clear.

authors: beckbria kfarnung

repo: puzztool/puzztool


text:
"spectral irradiance" variable defintion/standardisation suggestion

Is your feature request related to a problem? Please describe.
The user guide definition of variables and symbols section (found here) does not currently have a standard definition for "spectral irradiance".
Describe the solution you'd like

Agree a standard definition for spectral irradiance as a variable
I think having a standard "root" variable that can have super/subscripts added to for function-specific requirements would be good, for example, something like ghi / ghi_extra, aoi / aoi_projection , or temp_air / temp_cell / temp_dew (the "root" here being ghi, aoi, and temp)

Add the definition to the user guide

Update existing code if required

Additional context

pvlib.spectrum.calc_spectral_mismatch_field takes e_sun and e_ref as arguments for field and reference spectral irradiance, respectively.
pvlib.spectrum.spectrl2 and pvlib.spectrum.get_reference_spectra both use spectra inside the code (no spectral  irradiance user-facing argument)
pvlib.spectrum.average_photon_energy (PR) could also benefit from this

Suggestions:
si,    si_sun,    si_ref
spectral_irr,    spectral_irr_sun,    spectral_irr_ref
e,    e_sun,    e_ref
e_sun and e_ref make sense in calc_spectral_mismatch_field() but, for a function that doesn't require the _sun/_ref specification, e alone might be ambiguous. I like spectral_irr as it's clear, but it is potentially too long? A shorter alternative is si.
Thoughts? Other suggestions?

Any irradiance quantity could have a corresponding spectral variable. Broadband irradiance (a single number) is an integration over wavelength of a vector of wavelength-dependent values. I think the plane and nature of the measurement matter. Perhaps "_spectral" is a modifier on ghi, dni, etc.

Maybe the lack of experience or the language barrier, but personally I find spectrum or spectra stand-alone reasonable. In the context of PV I doubt there is a spectrum other than of irradiance, and I've always (again, inexperience disclaimer) seen it as $W/m^2/[\mu , n]m$ so it's pretty normalized I think.

Perhaps "_spectral" is a modifier on ghi, dni, etc.

I don't dislike that possibility either, but I don't want to clog a name.
Regarding spectral_irrad, usually it is pythonic to write full words. So if you pursue that path, I recommend spectral_irradiance

Any irradiance quantity could have a corresponding spectral variable.

I think the plane and nature of the measurement matter. Perhaps "_spectral" is a modifier on ghi, dni, etc.

Good point, I hadn't considered it in that way. However, this formulation might not be as useful at this time since we do not currently have any functions that require the user to specify individual components of spectral irradiance. We do, however, have functions that operate on any spectral irradiance component as an input, so we still need some general variable to represent any spectral irradiance data (eg function 1 and 3 in the additional context of original post)

Regarding spectral_irrad, usually it is pythonic to write full words. So if you pursue that path, I recommend spectral_irradiance

Fair enough. Feels good as a function argument for the user but a bit long for writing out calculations (but maybe I am just lazy when I write code)
si / spectral_irradiance remove the singular/plural aspect, unlike spectrum/spectra, but I guess that's not a major issue. I think I could be on board with spectra if not spectral_irr or si

+1 to spectrum for a general variable (not specific to plane or aperture of the measurement). Spectrum "is the intensity of light as it varies with wavelength or frequency." (Brittannica). So a value of spectrum is a vector of ordered pairs (wavelength/frequency, intensity), or a function F intensity=F(wavelength)  spectra would be more than one "value".  We should give some thought as to preferred units, and how to represent the pair of vectors (or vector of pairs) of values.
I'm still favor adding ghi_spectral to the dictionary but after a need arises.

+1 to spectrum for a general variable (not specific to plane or aperture of the measurement)

Okay based on the discussion so far this sounds reasonable.
One question: could there be any conflict due to the package being called spectrum as well?

I still favor adding ghi_spectral to the dictionary but after a need arises.

Agreed, I do too (you are ahead of your time Cliff!)

We should give some thought as to preferred units, and how to represent the pair of vectors (or vector of pairs) of values.

Current functions in pvlib.spectrum handle wavelength in nm, so I lean towards Wm^-2nm^-1 as the units of spectral irradiance. I think this is common outside of pvlib too but by no means universal, e.g. (IIRC) NSRDB FARMS-NIT simulations express wavelength in um.
If I understood your point about representation correctly, I think it would be okay to stick with the current pvlib convention for now (wavelength index for a single pandas.Series spectrum, wavelength column headers for multiple spectra in a pandas.DataFrame)

@kandersolar you might be interested in this discussion

One question: could there be any conflict due to the package being called spectrum as well?

Since I now see spectrum as a variable does not work with from pvlib import spectrum, which is used in all pvlib spectrum tests (and I for one find very convenient to use in my own work) I am not in favour of spectrum as a variable. I think spectra, si, or even spectral_irr / spectral_irradiance would be better.
I have left spectrum in #2140 (but not the tests) as that currently has the most votes but perhaps this issue could be left open for a bit longer to see if anyone else has any thoughts before concluding/closing and adding something to the user guide variables page.

Since the function is designed to work with spectra (multiple spectrum) as input, I yield, spectra can be the variable.

Thoughts on the second and third bullet points in the original post?

Add the definition to the user guide
Update existing code if required

Is a user guide variable entry necessary, and should existing functions/tests be revised to all use the same spectra (Wm⁻²nm⁻¹) variable?

Is a user guide variable entry necessary

It is helpful but not necessary

should existing functions/tests be revised

The different input parameter names in spectrum.calc_spectral_mismatch_field seem harmless to me. I'm more concerned that the spectrum.spectrl2 output parameter is named spectra. This parameter is a dict of arrays. A user may expect that the output of spectrl2 (clear-sky spectral irradiance) should "fit" into the input of e.g. average_photon_energy.

It is helpful but not necessary

I am now stuck in a loop of wanting to be helpful but not be unnecessary

I'm more concerned that the spectrum.spectrl2 output parameter is named spectra. This parameter is a dict of arrays. A user may expect that the output of spectrl2 (clear-sky spectral irradiance) should "fit" into the input of e.g. average_photon_energy.

Ah good observation, I had not noticed that. Since the input for both spectrum.calc_spectral_mismatch_field and spectrum.average_photon_energy is pd.Series or pd.DataFrame, rather than changing the inputs there would the appropriate remedy be to modify the output of spectrum.spectrl2 to be a dataframe of spectra? I'd be happy to work on this. It would be good to have cross-compatibility, especially since now the variable (for at least two) is the same.

modify the output of spectrum.spectrl2 to be a dataframe of spectra?

I don't think we want to do that. There are multiple arrays in the output of spectrl2, for the different irradiance quantities, and each array can be a 2D array, with the columns corresponding to timestamps. Bundling the different irradiance quantities into a single Dataframe makes that Dataframe 3D, and that just feels awkward.
The simplest change would be to remove the word spectra from the docstring of spectrl2, i.e.,
Returns
--------
    dict

I don't think we want to do that. There are multiple arrays in the output of spectrl2, for the different irradiance quantities, and each array can be a 2D array, with the columns corresponding to timestamps. Bundling the different irradiance quantities into a single Dataframe makes that Dataframe 3D, and that just feels awkward.

Ah of course, you are right

The simplest change would be to remove the word spectra from the docstring of spectrl2

#2168

I will have a think about modifying / how to modify average_photon_energy to accept more input types at a later date.

authors: RDaxini cwhanse echedey-ls

repo: pvlib/pvlib-python


text:
inconsistent broadcasting of outputs from singlediode methods

The issue was raised in some comments in #410 and #409 that the rules for broadcasting outputs are inconsistent among the single diode methods

singlediode will only broadcast the output if photocurrent is an sequence, array or series

float -> OrderedDict of float
array or sequence -> OrderedDict of array or sequence
Series -> DataFrame

i_from_v will broadcast the smallest size of either voltage, photocurrent, or resistance_shunt
v_from_i will broadcast the smallest size of either current, photocurrent, or resistance_shunt

In those same comments @cwhanse proposed:

to expand singletons when any parameter input is a vector, and to fail (gracefully) if two parameters are vectors of unequal length

I agree with this idea, and both i_from_v and v_from_i already have some boilerplate code to address this (note this snippet is lifted from v_from_i, with variable names suited for that function, change the
arguments to other methods like singlediode or mpp):
    # find the right size and shape for returns
    args = (current, photocurrent, saturation_current,
            resistance_series, resistance_shunt, nNsVth)  <-- list the args allowed to broadcast here
    size, shape = 0, None  # 0 or None both mean scalar
    for arg in args:
        try:
            this_shape = arg.shape  # try to get shape
        except AttributeError:
            this_shape = None
            try:
                this_size = len(arg)  # try to get the size
            except TypeError:
                this_size = 0
        else:
            this_size = sum(this_shape)  # calc size from shape
            if shape is None:
                shape = this_shape  # set the shape if None
        # update size and shape
        if this_size > size:
            size = this_size
            if this_shape is not None:
                shape = this_shape

Now knowing the size and/or the shape one can let numpy.vectorize cast the output as proposed:
    if size <= 1:
        V = v_from_i_fun(*args)
        if shape is not None:
            V = np.tile(V, shape)  <-- hacky way to make either array(V), array([V]), array([[V]]), ...
    else:
        # np.vectorize handles broadcasting, raises ValueError
        vecfun = np.vectorize(v_from_i_fun)
        V = vecfun(*args)
    if np.isnan(V).any() and size <= 1:
        V = np.repeat(V, size)
        if shape is not None:
            V = V.reshape(shape)

On a related note: @cwhanse I realize now I misread your comment and made i_from_v and v_from_i fail silently instead of gracefully, oops!. This might cause some confusion, in the short term, but maybe we can address it in this issue here?
@wholmgren is there a PVLibException class? What exception would you expect here, maybe ValueError('All arguments must be either scalar or the same size.')?

I would prefer to fail verbosely and see an error message when the code for finding output shape etc. is presented with incompatible inputs.  The code is going to fail at some point but it's a challenge for many users to walk back though the stack dump and see what they did wrong.

✔ addressed in f976f61 - fails verbosely if can't broadcast all inputs for i_from_v or v_from_i

I'm curious if numpy.broadcast_arrays() gives errors that make sense to a user when the inputs don't jibe well together?

IMO the error it raises is terse, but not opaque:

ValueError: operands could not be broadcast together with shapes (3,) () () (2,) () ()

Oh Python, how I spend too much of my life sorting out your dynamic types!

I don't fully understand this issue.
singlediode returns multiple kinds of data. The pvlib style is to return labeled data in these situations. That means a DataFrame when the returned data is 2D and the input is a Series or DataFrame; OrderedDict if not. singlediode handles at least some kinds of numpy 2D+ inputs that I've used just fine. So, my experience with singlediode is that it already handles broadcasting for reasonable inputs. Maybe someone posted specific example of where it didn't do what you expected and I missed it in the flurry of discussion. Either way, could you (re)post it here?
i_from_v and v_from_i return one kind of data each, so they don't need the labeling machinery. I am surprised to read that they broadcast to the smallest of voltage, photocurrent, or resistance_shunt. That sounds like a bug. Perhaps that's due to something about np.broadcast_arrays that I don't understand (I don't have any experience with this function). Again, reproducible examples in this issue would help me to keep track of the status.

Sorry @wholmgren I think this is specific to #409 proposed methods that didn't seem to be broadcasting correctly?
I've tested the existing methods in the master branch with different size inputs and they seem to broadcast okay, as long as numpy arrays are used. There does seem to be some preferential treatment for photocurrent as it can be a list or an array.
Here are some examples:
singlediode

list of photocurrents, all other inputs scalar - works!
singlediode([6, 7, 8], 1e-7, 0.001, 10, 1.23*0.026*72)
same size arrays of photocurrents and shunt resistance, others scalar - works!
singlediode(np.array([6, 7, 8]), 1e-7, 0.001, np.array([10, 11, 12]), 2.3)
array of shunt resistance, all others scalar - works!
singlediode(6, 1e-7, 0.001, np.array([10, 11, 12]), 2.3)
same size arrays of shunt and series resistance, others scalar - works
singlediode(6, 1e-7, np.array([0.001, 0.002, 0.003]), np.array([10, 11, 12]), 2.3)

i_from_v

list of photocurrents, all other inputs scalar - works!
i_from_v(10, 0.001, 2.3, 0.5, 1e-7, [6, 7, 8])
same size list of voltages and photocurrents, others scalar - works!
i_from_v(10, 0.001, 2.3, [0.4, 0.45, 0.5], 1e-7, [6, 7, 8])
list of voltages, others scalar - works!
i_from_v(10, 0.001, 2.3, [0.4, 0.45, 0.5], 1e-7, 6)
same size array of Rsh and voltages, others scalar - works!
i_from_v(np.array([10, 11, 12]), 0.001, 2.3, np.array([0.4, 0.45, 0.5]), 1e-7, 6)

I've change the title to make it specific to PR #409

I did add various combinations like these to the v_from_i() and i_from_v() unit tests when I added ideal device support. It’s certainly not exhaustive though.

@mikofski can you confirm that this issue is closed by these lines: for Bishop88 with newton; here and here for LambertW methods.
Given how long this has been open and the absence of other complaints about broadcasting, I'm inclined to just close this.

authors: cwhanse mikofski thunderfish24 wholmgren


text:
Add retrieval function for ERA5 reanalysis data

[x] I am familiar with the contributing guidelines
[x] Tests added
[x] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Description
ERA5 is the reanalysis dataset provided by the ECMWF and provides hourly irradiance data for the entire world starting in 1970.
The proposed function retrieves ERA5 data from the Climate Data Store (CDS) using the cdsapi.

In order to test ERA5, CDSAPI_KEY needs to be saved as an environment variable.
The API key can be obtained by creating a CDS account. Note the tests do not need a local file with the key info as described here.
@wholmgren Sorry to bother, but I think maybe you're the only one who has access to the pvlib email and email?

@wholmgren said in https://github.com/pvlib/pvlib-python/issues/1214#issuecomment-902819052 that we should think through how xarray and dask are used in pvlib, and now that 0.9.0 is out I guess we can do that.  This PR as it currently stands adds three new optional dependencies: xarray, dask, and cdsapi.  #1274 currently needs pydap as well.  I assume that what needs to be thought through is whether we are willing to add these new dependencies; if there are other questions to answer please point that out.  Here are my thoughts:
In the context of this PR, as I understand it (@AdamRJensen please correct any errors), I think dask is only needed for reading multiple files in a single read_era5 call, so we might be able to drop dask without losing much functionality.  And if we do restrict to single files, I suspect we could drop xarray as well and replace it with a lower level netcdf library (can h5py read netcdf?) combined with something like pvlib.forecast.ForecastModel._netcdf2pandas.
#1274 is less clear.  MERRA2 data retrieval is supposed to be done using OpenDAP instead of basic HTTP requests like most APIs.  My very limited understanding of OpenDAP suggests that it is advisable to use a dedicated library for it instead of just using requests like we normally do.  xarray combined with pydap is one way to access the data, but I am pretty reluctant to use pydap: the project seems abandoned and we could only get things working with an unreleased development version.  I think there are alternatives worth looking into but I don't know yet whether xarray will need to be involved.

authors: AdamRJensen kanderso-nrel


text:
Shooting Star Info - F2P Xp/Hr incorrect

Currently doesn't do the half xp change, includes prospectors, and includes the celestial ring in the calculations.

Fixed in v1.1.1


text:
IllegalStateException in LollipopScanStrategy

java.lang.IllegalStateException: BT Adapter is not turned ON        at android.bluetooth.le.BluetoothLeUtils.checkAdapterStateOn(BluetoothLeUtils.java:136)        at android.bluetooth.le.BluetoothLeScanner.stopScan(BluetoothLeScanner.java:206)        at com.github.pwittchen.reactivebeacons.library.scan.strategy.lollipop.LollipopScanStrategy$1.call(LollipopScanStrategy.java:43)        at rx.subscriptions.BooleanSubscription.unsubscribe(BooleanSubscription.java:71)        at rx.internal.util.SubscriptionList.unsubscribeFromAll(SubscriptionList.java:136)        at rx.internal.util.SubscriptionList.unsubscribe(SubscriptionList.java:125)        at rx.Subscriber.unsubscribe(Subscriber.java:98)        at rx.internal.util.SubscriptionList.unsubscribeFromAll(SubscriptionList.java:136)        at rx.internal.util.SubscriptionList.unsubscribe(SubscriptionList.java:125)        at rx.Subscriber.unsubscribe(Subscriber.java:98)        at com.sminq.user.services.BleBeaconService.onDestroy(BleBeaconService.java:219)        at android.app.ActivityThread.handleStopService(ActivityThread.java:3327)        at android.app.ActivityThread.-wrap27(ActivityThread.java)        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1570)        at android.os.Handler.dispatchMessage(Handler.java:102)        at android.os.Looper.loop(Looper.java:154)        at android.app.ActivityThread.main(ActivityThread.java:6077)        at java.lang.reflect.Method.invoke(Method.java)        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

Hi,
Thanks for reporting this issue.
It looks like Bluetooth is turned off. Please, take a look at the Good Practices section in README.md file. You should fulfill requirements mentioned in this section:

update Manifest
check BLE support
request Bluetooth access
request Location access for API 23 and higher
request runtime permissions for API 23 and higher

Take a look at the exemplary code snippet and examplary app.
Regards,
Piotr

authors: kshitij-sminq pwittchen

repo: pwittchen/ReactiveBeacons


text:
iphone 8 ios 12.4 don't want to be jailbreak anymore !?!?!

i was on iphone 8 with ios 12.4 and its was jailbroken with the last version of unc0ver 3.6.0 and after refresh with the new one : 3.6.2+1.gb9c17cb ,,,, my iphone work for 1 hour and do a restart ,,, after that try to jailbreak again and when i press JAILBREAK he start the operation and reboot after juste 1 second ,, help me please !!!

Before clicking jailbreak, go into settings of uncover and make sure you select “sock puppet” and not “sock port” as the used exploit. Then try again.

Also, it WILL reboot when jailbreaking sometimes. That’s normal. As for the restarts, that’s probably a tweak issue.
Sent with GitHawk

authors: Randomblock1 Shadowgar sebaswrx


text:
Restart by no reason

Describe the bug
To Reproduce
Steps to reproduce the behavior:
There are no steps, I got jailbreak and then randomly  in a random time I reboot
Screenshots
No screenshots, just restarts at an unexpected time
Device (please complete the following information):

iOS Versión: 13.3 build 17C54
iOS Device: iPad Air 6,11
unc0ver Version: 4.3.1

Place an "x" between the brackets if true:

[x ] this is a bug others will be able to reproduce (note: I probably don’t know I am not an expert but at least I know how to jailbreak and use iOS)
[x ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[x ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

Duplicate of #1890

authors: Cryptiiiic luixiuno


text:
Failed to extract bootstrap

iPhone 6s - iOS 12.1.1 - unc0ver 3.0.0 b41
This issue has been present on my 6s on all the unc0ver iOS 12 betas so far making it impossible to complete the jailbreak. It seems the "failed to extract bootstrap" popup occurs at the same part of the jailbreak everytime, while working on the libssl package. I have restored RootFS before each and every attempt to ensure a clean device.
I have attached the last few lines of the visible log below, but please get back to me if you need me to try to export the diagnostics data or if I in some other way can assist in identifying the core issue.
To Reproduce
Steps to reproduce the behavior:
Initiate jailbreak. Will fail when reaching 'libssl' package.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version: 12.1.1
iOS Device: iPhone 6s
unc0ver Version: 3.0.0 b41

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[X] this issue is present after a rootfs restore
[X] this issue is present on the latest version of unc0ver

Logs
[] runCommandv(255): update-alternatives: using /usr/libexec/ldid_wrapper to provide /usr/bin/ldid (ldid) in auto mode
[] runCommandv(255): Setting up com.ps.letmeblock (0.0.1) ...
[] runCommandv(255): Setting up readline (7.0.5-2) ...
[] runCommandv(255): dpkg: ldid: dependency problems, but configuring anyway as you requested:
[] runCommandv(255): ldid depends on libssl1.0; however:
[] runCommandv(255): Package libssl1.0 is not installed.
[] runCommandv(255):
[] runCommandv(255): Setting up ldid (2:2.1.1+elucubratus1) ...
[] runCommandv(255): Errors were encountered while processing:
[] runCommandv(255): /var/containers/Bundle/Application/D7962853-D9D7-476D-900F-304FF66C409E/Undecimus.app/apt/libssl1.0_1.0.2q-1_iphoneos-arm.deb
[] runCommandv(255) completed with exit status 1
[] __assert(2:installDebs(debsToInstall, true))@JailbreakViewController.m:1693[jailbreak]

Open

I'm receiving the same error. ios 12.1.2 iphone 5S

Somewhat happens to me on iPhone six after I jailbroke, attempted to install a certain BootLogo, and iOS... unjailbroke itself? Now I get this error when retrying. Might try RootFS later.

The way I fixed it.
1- set Airplane mode on, Turn off load tweaks and load daemons.
2- restore the Rootfs, Jailbreak till it successfully restored, Device will restart now.
3- Turn Off the restore Rootfs and Jailbreak, it will restart will it take snapshot.
4- Jailbreak again until the bootstrap installments succeed.
5- Jailbreak now to install Cydia (make sure you keep the option of load tweaks and daemons off)
6- You should find Cydia on the board, now enable the load tweaks and daemons then jailbreak.

I want it to be true but this doesn’t help in every situation. For example i have an error on line 1711 and i tried with deamons on and off, reload system deamons on and off, airplane mode on and off and getting the same error.

After trying

The way I fixed it.
1- set Airplane mode on, Turn off load tweaks and load daemons.
2- restore the Rootfs, Jailbreak till it successfully restored, Device will restart now.
3- Turn Off the restore Rootfs and Jailbreak, it will restart will it take snapshot.
4- Jailbreak again until the bootstrap installments succeed.
5- Jailbreak now to install Cydia (make sure you keep the option of load tweaks and daemons off)
6- You should find Cydia on the board, now enable the load tweaks and daemons then jailbreak.

Now it gets stuck on [*] Extracting Cydia...
(Tried several times)

OP here. I still have this annoying issue. Still happening on the libssl step, so I still haven't managed to jailbreak my iPhone 6S successfully. If I can assist with logs or similar just hit me up.

@moks84: I have tried your suggestion but still receive the bootstrap error on the libssl task. Is it understood correctly that load tweaks and daemons should be off until step 6. In step 4 you do not mention it so I’m not sure about whether it should be reactivated in that step and then deactivated again in step 5 although that wouldn’t really make any sense?
I wonder why the error constantly occurs on the libssl part in my device as I haven’t seen anybody else mentioning it to fail on that specific component. If I could just pass that step or something it would be awesome. It seems like there’s an earlier version it tries to replace, perhaps a leftover from an earlier jailbreak but I can’t see what I can do about that component specifically...sigh...

There are release for unc0ver ~b48, please give it a try, it had a good improvements.
insure the airplane is on until cydia is installed.
switch back the daemons and tweaks only after cydia installation (step 6), and insure they are turned off for all steps until Cydia is installed.

I would suggest you to watch this video. hope this will solve your problem
https://www.youtube.com/watch?v=0mdX-PcsZpk&t=195s


text:
Create Bot Brodcast l By FaZeMetro

Are you fucking retarded?


text:
[test only] Add csp jenkinsfile [databricks]

test only

buildcsp

buildcsp

buildcsp

buildcsp

buildcsp

build

buildcsp

buildcsp

buildcsp

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

build

repo: pxLi/spark-rapids


text:
Unpin numpy

https://github.com/py-why/dowhy/commit/ca340303e993fa4be1831f74afccf9161e19a9d8
Numpy is currently pinned due to something related to Numba. Can we unpin this? It really makes dowhy impossible to add to other packages and forces very specific environments.

This also means that dowhy is only compatible with a single numba version.

repo: py-why/dowhy


text:
No Proxy IP [Bug]/[New Features]

Hey, i been using this app for about 2 to 3 weeks now. At first it was working perfecting and I was able to tether my WiFi through my phone. But recently it started to pop up saying: "NO IP ADDRESS" in the section where the proxy's IP should be.

Also I would love to see the devices I have connected to the hotspot that is created and I feel like it would be extremely helpful if there was a way to block certain internal and external IP address or URLs from being able to connect.

Hi,
Showing connected devices has an issue and is in progress.
Odd that it can't find an IP address. Usually I think it defaults to 192.168.49.1
Once the hotspot is running the app fires off a call asking what the IP address is - so if that is not coming back something is non standard with your device.
Does the network still work if you assume the Proxy URL is at 192.168.49.1?

If you switch to 2.4 GHz band, does the IP address come back?

I change the Band to 2.4 GHZ it still does not work, it shows the same thing. I tried to connecting to the HTTPS proxy but it seems like it doesn't want to connect. I also tried: restarting my devices. clearing cache and data, uninstalling and reinstalling the app. But still the same issue reappears. Is there any google related components it uses? Since I been de-googling my phone recently it might of caused the bug.

There are no google dependencies at least relating to the hotspot broadcast.
The hotspot relies purely on WiFi Direct on your phone.
Did it ever work? The code for populating the IP address has not changed since the initial release, so I wonder what's going on

Yes, it worked for able two weeks and then it started to show this bug yesterday.

If you want I can run ADB logging to get you more specific details.

Odd, OK
Again, the network code hasn't changed for a bit so I'm unsure if this is caused by your device (though I doubt it)
I will look to trying to make the IP resolution more reliable.
Just to be sure, you are able to

Run the hotspot
See the WiFi network and connect to it from another device.

But you are unable once connected to setup a proxy because you are missing the Proxy URL, right?

I ran a check if there is a Gateway IP Address that the hotspot puts out. But it doesn't seem to have one, its broadcasting the Band but not giving out a Gateway IP Address.

Hello
When you have the chance, I've uploaded release version 20 to Github and the Play Store. This release adds some additional in-app debugging which may show for you if something goes wrong when retrieving the hotspot info from WiFi Direct on the device.
Please update when you can, and see if anything changes about your situtation, thanks.

Ah ive  also just noticed from your screenshot, you have a VPN running on your Android device.
If you turn off the VPN first and then attempt to connect to TetherFi does your IP address get populated?

Sorry for late reply i been busy

Hmm interesting, this could be one of two issues.
One, race condition, the app is asking for Connection info too early, and we just need to wait a little longer
Or two, WiFi direct is failing to fully setup, and so there just is no available connection info ever.
I will implement some code that asks for connection info slower, hoping that this is just case 1.
Thanks for testing the new in-app error dialog feature too! :stuck_out_tongue:

Recent updates have added a "Refresh Hotspot" button which should attempt to ask the underlying Wifi system to get the IP address again. Please see if this refresh action solves your problem of missing an IP address, thank you!

repo: pyamsoft/tetherfi


text:
CYCLICMAP table in DPF

Hi,
it's currently impossible to access the CYCLICMAP table (which shows the low and high boundary node connections in a cyclic symmetry) using DPF.
Would it be possible to add this access?
Thanks.

@CCHEMAI let me check if we have a service allowing having access to this.

authors: CCHEMAI rlagha

repo: pyansys/pydpf-core


text:
ability to write matml as string

the writer only supports writing to file. I would like to support writing to string in order to avoid having to write a temp file for the onscale integration

@da1910 We could make the CI/CD testing matrix include python <3.9 to fully cover indent in codecov, but I'd say it's not worth the trouble.

Agreed, at some point I can add minidom as a way to indent code on python 3.8 but for the moment it's fine as-is. Just wanted to cover the indent method in some form.

repo: pyansys/pymaterials-manager


text:
add EV3 Game program

Dear @laurensvalk and @dlech,
I am submitting my EV3 game program for your review.
The robot code is hard but it is fun to play with.
The robot code is very long and has a lot of functions so it took me a lot of time.
My dad helped me with some math and variables. He found a big bug in the execute_move function and fixed it for me.
Thank you very much! :)
Antoni

Thanks Antoni, this is great! I've merged it :tada:
I noticed in some of your programs, ev3_brick is added as a class attribute. There's nothing wrong with that per se, but it might not be needed if you use the EV3 brick methods directly.
For example:
ev3_game.ev3_brick.light.on(color=Color.GREEN)

might be easier to understand as:
ev3.light.on(color=Color.GREEN)

because then users will quickly see that this is a standard function.
I think you might have taken apart most of the models already, so don't worry about it for these pull requests :)

Hi @laurensvalk,
Do you mean we should split the EV3Brick out as a separate entity from the robot? We have been using the "has a" pattern re: the EV3Brick, after our discussion here https://github.com/pybricks/pybricks-projects/pull/7#issuecomment-679268461. Do you prefer the ev3 brick being outside the class instance instead?

I think it's fine to leave these programs unchanged, it's just an idea for future projects. The "has a" pattern, is certainly useful for methods like these, which are useful indeed:
    def display_level(self):
        self.ev3_brick.screen.clear()

        self.ev3_brick.screen.print('Level {}'.format(self.level))

        wait(300)

It was mainly a thought for the case where the ev3 mehods are currently accessed directly through the attribute. Part of it is abstracted as above, and part of it is not:
        if correct_choice:
            ev3_game.ev3_brick.light.on(color=Color.GREEN)

            ev3_game.ev3_brick.speaker.play_file(file=SoundFile.CHEERING)

Another way to do it would be something like:
        if correct_choice:
            ev3_game.show_correct_choice()

Again, don't worry about it, it's not a requirement at all, just an idea. :)

@laurensvalk I see -- it's about the abstraction levels for the robot actions then. We'll look for opportunities for such further abstractions when programming the new robots or when refactoring the existing then.
The approach @AntoniLuongPham and I have been taking is as follows:

As-Is Translation: We first look at the original blocks-based code (Scratch for Home, LabVIEW for Home Bonus) and translate the code as faithfully as possible to Python (PyBricks/EV3Dev) to see if it works. In particular, when the original author has "My Blocks", we first translate those My Blocks to separate class methods. The original author's main program is usually first parked under our def main, if __name__ == '__main__' or in a separate script.

Parameter Tuning: adjust parameters if the initial as-is translation of the Scratch/LabVIEW code doesn't work -- e.g. because of Python's different processing time.

Refactoring: we try to identify opportunities for abstracting certain code sections to class methods (similar to the case you pointed out above) or shorten the code using the more powerful Python APIs. There are definitely opportunities we have missed. Let us relook at the programs during the holiday season and do a round of further refactoring. :)

repo: pybricks/pybricks-projects


text:
Create a task to install package in editable mode

It would be great to have a task to install the distribution in editable mode.
Like pip install --editable .

Hi, @slitayem
pip intall -e requires completed setup.py which is generated by PyB. In this case installed package will reference to target/dist directory which could be easily deleted.
Editable mode is used for developing purpose and could be done manually.

@slitayem I agree with @AlexeySanko. Editable are generally inappropriate for PyB.
What is your development cycle and what are you trying to accomplish?

I agree that editable mode is for development cycle and that is why I wanted to use it. Cause in my case I have two dependent packages and I want to install one of them in editable mode in my virtual env for testing purpose in order to avoid to publish the package before testing properly the new changes required and used in the other package.
IMHO every package goes into development cycle before being released. Then, the editable mode is still needed.
Thanks

Hi.
Just add needed local projects source path to PYTHONPATH into virtualenv.
In my case PyCharm perfectly does it (not advertizing :grin:) - I just need to add some directory as source dir and enjoy all Python packages there.

@slitayem You can just pip install the project into your virtualenv indeed, don't need to manipulate PYTHONPATH at all.

authors: AlexeySanko arcivanov slitayem

repo: pybuilder/pybuilder


text:
uploaded image can view in url on short period, but cannot find in directory using docker

Hi all. I got issue when I upload media file to django cookie cutter. below is the scenario.
1.) After uploaded image, the image can view temporary in url path. The image will fail to find after some time using the path.
2.) the .jpg file cannot find at server directory at all.
models.zip

@weiphang-gdex I'm slightly scared to open that zip file. Mind uploading to a git repository?

@Andrew-Chen-Wang Thank. The issue solved. I not mount to a volume so the image save to memory only.

gotcha. Please close the issue!

authors: Andrew-Chen-Wang weiphang-gdex

repo: pydanny/cookiecutter-django


text:
Docker logs / Kubernetes logs

Question
Is there a simple way to hook collect all logs from docker (or kubernetes) and send to logfire ?

Should we document this? 🤔

It seems both links I provided need to set up the OpenTelemetry Collector. When @adriangb has time to document a page about the importance, and why to use it, then I think we can add those examples and add a link to that page.

authors: Kludex vitalik

repo: pydantic/logfire


text:
add model documentation

Fix #239

Nice, looks great 👍

authors: samuelcolvin sydney-runkle

repo: pydantic/pydantic-ai


text:
Pydantic converts 'list' and 'set' to 'list_iterator' and 'set_iterator' objects. 'collections.abc.Iterable' as type hint must be either explicitly forbidden or supported by Pydantic

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.9.0a2
            pydantic compiled: False
                 install path: /projects/project/venv/lib/python3.10/site-packages/pydantic
               python version: 3.10.1 (main, Dec 21 2021, 17:46:38) [GCC 9.3.0]
                     platform: Linux-5.4.0-91-generic-x86_64-with-glibc2.31
     optional deps. installed: ['dotenv', 'email-validator', 'typing-extensions']

Problem
I use Iterable as a type hint and I pass list or set as arguments, but I get back list_iterator or tuple_iterator.
This Pydantic behavior makes it easy to introduce bugs in a code.
Reproducible code sample
from collections.abc import Iterable

from pydantic import BaseModel

class Foo(BaseModel):
    bars: Iterable[str]

foo = Foo(bars=["spam", "eggs"])
print(foo.dict())

foo_2 = Foo(bars=("spam", "eggs"))
print(foo_2.dict())

Run output:
{'bars': <list_iterator object at 0x7f2e3662ab90>}
{'bars': <tuple_iterator object at 0x7f2e361af190>}

Expected behavior
First option: raise a warning or an error about Iterable usage.
Another option:
Output must be:
{'bars': ["spam", "eggs"]}

(not {'bars': <list_iterator object at 0x7f2e3662ab90>} as I get now).

I have found that typing field as typing.Sequence[str] | typing.Iterable[str] kinda solves the problem. It's interesting that order matters, so using typing.Iterable[str] | typing.Sequence[str] will still convert sequence to iterable using __iter__

This behavior remains in v2 — the way it has been implemented, we convert items passed to fields of type Iterable into a generator, and validate as items are iterated over. This is useful for handling objects that you can't iterate over eagerly (such as infinite generators).
If this behavior is a problem for you, please open a feature request requesting a change in this behavior; you'll need to suggest an alternative approach that also handles generators nicely (I can imagine some, such as calling __iter__ and then deciding what to ultimately return based on whether the resulting value is an instance of Sequence or not).
I think @MentalBlood's suggestion of using typing.Sequence[str] | typing.Iterable[str] as the annotation may be a good workaround if you want to preserve the sequence-ness of the attributes used to instantiate your model.

repo: pydantic/pydantic


text:
model_dump(_json) for a RootModel[list[...]] produces list of empty dicts when using generic TypeVar which is bound to BaseModel

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I'm using RootModel[list[ATypeVar]] and am trying to dump a list of pydantic models in such a root model instance as python dicts or json string using model_dump or model_dump_json respectivly.
Both fail when ATypeVar is bound to BaseModel but it works, when the TypeVar is not bound.
See full example code below.
Example Code
from typing import Generic, TypeVar

import pytest
from pydantic import BaseModel, RootModel

@pytest.mark.parametrize("bind_to_base_model", [True, False])
def test_root_model_dump(bind_to_base_model: bool):
    if bind_to_base_model:
        Foo = TypeVar("Foo", bound=BaseModel)  # the error only occurs in this path
    else:
        Foo = TypeVar("Foo")  # this works fine

    class MyGenericClass(RootModel[list[Foo]], Generic[Foo]):
        pass

    class MyModel(BaseModel):
        foo: str

    my_model = MyModel(foo="bar")
    my_generic_instance = MyGenericClass(root=[my_model])
    my_dict = my_generic_instance.model_dump()
    assert my_dict == [{"foo": "bar"}]

Python, Pydantic & OS Version
pydantic version: 2.3.0
        pydantic-core version: 2.6.3
          pydantic-core build: profile=release pgo=false
                 install path: C:\my-user-name\and\path\.tox\dev\Lib\site-packages\pydantic
               python version: 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)]
                     platform: Windows-10-10.0.19044-SP0
     optional deps. installed: ['typing-extensions']

This happens because when you bind the type var to BaseModel it serializes as if it expected BaseModel instances, which have no fields, hence the empty dict. Try:
from typing import Generic, TypeVar

from pydantic import BaseModel, RootModel, SerializeAsAny

Foo = TypeVar("Foo", bound=BaseModel)  # the error only occurs in this path

class MyGenericClass(RootModel[list[SerializeAsAny[Foo]]], Generic[Foo]):
    pass

class MyModel(BaseModel):
    foo: str

my_model = MyModel(foo="bar")
my_generic_instance = MyGenericClass(root=[my_model])
my_dict = my_generic_instance.model_dump()
assert my_dict == [{"foo": "bar"}], my_dict

Or parameterize the generics before constructing the model.

authors: adriangb hf-kklein


text:
colors in Dataset plot methods

While working on the plot method docstrings (#5285), I (and @keewis) found that the colors kwarg for the Dataset plot methods is not as useful as it could be. In some cases it is silently ignored (warning or error could be raised instead).
For Dataset.plot.scatter, I think it would make sense for a list of colors to be able to be passed to be used for discrete hue_style. Currently, the only way you can control these for discrete hue_style is if hue is numeric and you also pass levels.

My original notes on Dataset.plot.scatter:
Yeah, it seems like the colors argument is not used in ds.plot.scatter. But no error is raised, colors is just silently dropped (ax.scatter would raise AttributeError if it weren't) in most cases. I did find that you can get the marker colors to change by passing color or c with a discrete hue_style.
import xarray as xr
import numpy as np
ds = xr.tutorial.scatter_example_dataset()
ds["c"] = (ds.A.dims, np.random.choice(("r", "g", "b"), ds.A.shape))
ds.plot.scatter("A", "B", hue="c", c=(0, 0, 0))  # works but prints (doesn't raise) warning
ds.plot.scatter("A", "B", hue="c", color=(0, 0, 0))  # works

However, if you have a continuous hue_style, passing c is ignored (since this is done internally), and passing color raises ValueError since it conflicts with c.
It seems like at the moment, colors is really only intended to be used with contour(f) for levels, like how it is in Matplotlib. Maybe in the future it could be used to allow passing colors to be used in the color cycle for discrete hue_style, but it doesn't currently do that. So for now, maybe in the docstring we should note this current behavior (doing nothing or raising error).
levels is also unused in _dsplot functions, maybe could be removed actually I was able to get colors to sort of work with discrete hue_style by also providing levels, but levels only makes sense for numeric type:
ds["c2"] = (ds.A.dims, np.random.choice((1, 2, 3), ds.A.shape))
ds.plot.scatter("A", "B", hue="c2", colors=["r", "g", "b"], levels=[1, 2, 3, 4])  # works (rgb)
ds.plot.scatter("A", "B", hue="c2", hue_style="discrete", colors=["r", "g", "b"])  # `colors` does nothing

Originally posted by @zmoon in https://github.com/pydata/xarray/pull/5285#discussion_r632986368

Seaborn has the palette argument that is used for controlling hue. I wonder if they would make sense for Xarray, too. Certainly it's annoying to need to write a loop just to plot a few different colors on the same axis.

Yeah, having a kwarg that is specifically for the hue variable could make it more clear. It doesn't seem like the Dataset plot methods need to have both cmap and colors. They could be replaced by one, like palette, or keep just colors?

authors: shoyer zmoon

repo: pydata/xarray


text:
Use sphinx-accessors-autosummary

Since I released a initial version of sphinx-accessors-autosummary (to PyPI, conda-forge requires a bit more work), I think we can start using it in xarray, too.
This also extends the docs on accessors to mention that package.

[x] Closes #4152, closes #3361
[x] Passes isort . && black . && mypy . && flake8
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

it seems that worked: the signature and the summary of DataArray.plot are visible

Thanks @keewis !

let's merge, then?

Thanks @keewis

authors: dcherian keewis max-sixty


text:
remove requirement for setuptools.pkg_resources

Fixes #5676
Now depends on importlib-metadata for Python major version < 3.8

[x] Closes #5676
[x] Passes pre-commit run --all-files

is there any reason not to merge this?

the issue is that with conda we can either always install importlib_metadata or not at all: conda doesn't support noarch_python packages with preprocessing selectors (see the comments around https://github.com/pydata/xarray/issues/4295#issuecomment-667657310 for more discussion).
importlib.metadata is included in python>=3.8, which we can officially require from end of December this year.
All of this means that if we want to merge this now we have to decide between not releasing until we can drop python=3.7 or always installing on importlib_metadata (which is what the pint feedstock does). However, I guess the cleanest way would be to wait until we can require python>=3.8.

I don't think that noarch packages are restricted to python version selectors any more. I've tested this locally with a dummy recipe like this:
package:
  name: {{ name|lower }}
  version: {{ version }}

source:
  path: .

build:
  noarch: python
  number: 0
  script: "{{ PYTHON }} -m pip install . -vv"

requirements:
  host:
    - python
    - pip
  run:
    - python
    - importlib_metadata # [ py < 38]

This creates a noarch package as expected with a recent conda/build version.

Thanks @marscher This is a great change.
I see this is your first PR. Welcome to Xarray!

Thanks @marscher This is a great change.
I see this is your first PR. Welcome to Xarray!

Thanks for the warm welcome.

authors: dcherian keewis marscher


text:
String attributes containing colon are not quoted

import pydot
n = pydot.Node('x', fillcolor='red:yellow')
print(n)

Seen:
x [fillcolor=red:yellow];

Expected:
x [fillcolor="red:yellow"];

(dot won't compile without the value being quoted, complaining of Error: file.dot: syntax error in line x near ':')
This behavior has been confirmed on pydot 2.0.0.dev0.

This was originally reported as https://github.com/networkx/networkx/issues/4663

Thanks for reporting. This is probably very related to pydot/pydot#118 and pydot/pydot#224. Even though those issues are about colons in node/edge names and you are reporting about a colon in a DOT attribute value, both are DOT IDs. Not sure yet if this is a complete duplicate, though, so I suggest we keep this issue open so we can include it as another test case.
All these issues should get fixed as part of the next pydot release (2.0.0) in my opinion, though be prepared that it will still be a while before that gets released. Yesterday @MaxHorwood said in pydot/pydot#224 he would try to work on a PR.

That's great; thanks for the update @peternowee!

@peternowee Hope you are doing well 😄 I am still interested in finding a solution for this and it looks like you are too!
Two proposals have occurred to me, and I hope you will indulge me:

Change the README so that this line:
my_node = pydot.Node('a', label='Foo')

becomes:
my_node = pydot.Node('a', label='"Foo"')

and add a little explanation about string literals, so first-time users know how to avoid the problem.

Or a massive refactor to use types to differentiate string literals directly:
As an example, if something like this is added to the library:
StringLiteral = namedtuple('StringLiteral', ['value'])  # May want to use dataclass, but this is shorter
Port = namedtuple('Port', ['something', 'anotherthing'])  # Still don't understand this, sorry
...

Label = Union[StringLiteral, Port, ... etc]  # Don't know what the options are, apologies again

Then the user must be explicit about what type of label they would like, and it could be error handled:
my_node = pydot.Node('a', label=StringLiteral('Foo'))

This would probably involve a lot of work and would make PyDot less of a wrapper, but would enable better error handling and messaging to the user.

I am curious if you or other contributors have proposals for how to address this.

Unfortunately, the workaround function:
def _check_colon_quotes(s):
    # A quick helper function to check if a string has a colon in it
    # and if it is quoted properly with double quotes.
    # refer https://github.com/pydot/pydot/issues/258
    return ":" in s and (s[0] != '"' or s[-1] != '"')

... fails when s is not a string (e.g., a numeric weight).

@laowantong I can't follow you, where is this workaround function. It's your own?

@horvatha Sorry, I should have made myself clearer. This is not my code, but a function of NetworkX:
https://github.com/networkx/networkx/blob/ce692bd3f05900608b829b983838d099b378ca8f/networkx/drawing/nx_pydot.py#L195-L199
I am not sure how it is connected to this project though. My own workaround was to convert to string all the weights of my graph to be able to save it:
    def save(self, stem_or_path):
        # workaround for https://github.com/pydot/pydot/issues/258#issuecomment-1276492779.
        # Convert all edges attributes to strings.
        # The same should be done for nodes attributes, but YAGNI.
        G = deepcopy(self)
        for (x, y, data) in G.edges(data=True):
            for (k, v) in list(data.items()):
                G[x][y][k] = str(v)
        smart_path(stem_or_path).write_text(nx.nx_pydot.to_pydot(G).to_string())

Honestly, IMHO the right fix is to simply ensure that values are quoted by pydot whenever they need to be. I see this still isn't fixed, looks like quote_if_needed needs another upgrade.

authors: ferdnyc horvatha julianfortune laowantong peternowee stefanv

repo: pydot/pydot

license: mit


text:
Use markdown and template actions on blockpages

I guess this is kind of a feature request. It would be nice to use markdown on blockpages. This would open up possibilities for more advanced respons-pages useful for users.

probably it is better to add a redirect directive which takes an URL to redirect any blocked client to that URL.

I will try the redirect directive. Didn't think about that one. Thanks!
I simply prefer writing markdown. Formatting the page is much simpler that way. And I want to fill in some dynamic values, like the clients geoip-location etc. And Caddy comes with nice options to fill variables through Template Actions.

authors: Torbe pyed

repo: pyed/ipfilter


text:
Fix JobType.get_environment()

This PR updates get_environment() a bit so it's more apparent when there's a problem with the configuration.  Before this you could accidentally provide a non-dictionary for jobtype_default_environment and you'd never know unless you looked at the agent logs.

@guidow, PTAL

repo: pyfarm/pyfarm-agent


text:
I merged and fixed most of the issues

Hi @utensil,
I found a weird thing using pygae/galgebra. Some methods return a Mv instance now but a sympy expression is enough and this crashes Sympy 1.3. Sympy just goes into an infinite recursion using its reflection system and finish by raising an exception.
Regards

Since I have your attention here - would you mind responding to this comment (https://github.com/meuns/galgebra/pull/1#issuecomment-558342817)?

I found a weird thing using pygae/galgebra. Some methods return a Mv instance now but a sympy expression is enough and this crashes Sympy 1.3. Sympy just goes into an infinite recursion using its reflection system and finish by raising an exception.

@meuns  Can you make a minimal reproduction of this problem?

I found a weird thing using pygae/galgebra. Some methods return a Mv instance now but a sympy expression is enough and this crashes Sympy 1.3. Sympy just goes into an infinite recursion using its reflection system and finish by raising an exception.

@meuns Can you make a minimal reproduction of this problem?

This is quite easy to reproduce. Just pass any Mv instance to simplify.

That sounds like the issue I filed the other day then.

That sounds like the issue I filed the other day then.

Which one?

If I remember well the dot product, the left and right contractions returned some sympy scalar expressions and now they return scalar Mv instances.

From this description, I can barely recalled that I have done something similar intentionally for consistency. Can't be sure until I grt done to try a reproduce.

If I remember well the dot product, the left and right contractions returned some sympy scalar expressions and now they return scalar Mv instances.

See also #154, which applies this to | too

authors: eric-wieser meuns utensil

repo: pygae/galgebra


text:
Improvements to base materials

Generic parameters:

[x] opacity - 1.0-0.0 float, multiplied with alpha texture map if set. #121
[x] clipping planes (requires check in every material's fragment shader) #124
[ ] stencil buffer options
[ ] alpha testing

@Korijn do we consider stencil-buffer and alpha-testing internal details (not pubic API) for the time being? If so, we can close this if #131 is merged.

Yes, we do consider them internal. We'll revisit the capping example from threejs later

authors: Korijn almarklein

repo: pygfx/pygfx


text:
Doesn't install with Jython

(Original issue 786 created by rtbf*q4L6ZmlUSAa_T902yjBPDQ on 2012-06-25T20:50:02.502913+00:00)
I'm using Jython 2.7a2, the latest.
I've set up a Jython virtualenv, and run 'pip install pygments'. It fails at the following stage:
byte-compiling /home/ian/Applications/jython-env/Lib/site-packages/pygments/lexers/_vimbuiltins.py to _vimbuiltins$py.class

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ian/Applications/jython-env/build/pygments/setup.py", line 61, in <module>
    setup(
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/core.py", line 152, in setup
    dist.run_commands()
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/core.py", line 152, in setup
    dist.run_commands()
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/home/ian/Applications/jython-env/Lib/site-packages/setuptools-0.6c11-py2.7.egg/setuptools/command/install.py", line 56, in run
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/command/install.py", line 517, in run
    self.run_command(cmd_name)
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/cmd.py", line 326, in run_command
    self.distribution.run_command(command)
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/home/ian/Applications/jython-env/Lib/site-packages/setuptools-0.6c11-py2.7.egg/setuptools/command/install_lib.py", line 24, in run
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/command/install_lib.py", line 136, in byte_compile
    byte_compile(files, optimize=0,
  File "/home/ian/Applications/jython2.7a2/Lib/distutils/util.py", line 567, in byte_compile
    compile(file, cfile, dfile)
  File "/home/ian/Applications/jython2.7a2/Lib/py_compile.py", line 96, in compile
    _py_compile.compile(file, cfile, dfile)
  File "/home/ian/Applications/jython2.7a2/Lib/py_compile.py", line 96, in compile
    _py_compile.compile(file, cfile, dfile)
        at org.python.objectweb.asm.MethodWriter.a(Unknown Source)
        at org.python.objectweb.asm.ClassWriter.toByteArray(Unknown Source)
        at org.python.compiler.ClassFile.write(ClassFile.java:124)
        at org.python.compiler.Module.write(Module.java:618)
        at org.python.compiler.Module.compile(Module.java:674)
        at org.python.core.imp.compileSource(imp.java:330)
        at org.python.core.imp.compileSource(imp.java:252)
        at org.python.modules._py_compile.compile(_py_compile.java:28)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)

java.lang.RuntimeException: java.lang.RuntimeException: Method code too large!

Jython can't compile methods over a certain size. One solution is to import pycimport; this requires that a pyc file has been generated by CPython.

(Original issue 786 last updated on 2014-10-07T21:59:30.233463+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2012-08-19T09:14:06.185831+00:00)
Hmm, I'd rather consider this a bug in Jython.

(Original comment by tshatch on 2012-08-28T15:25:03.539096+00:00)
Yes, it's actually a limitation of the JVM, not just Jython however.  In this case, there's a fairly trivial workaround in a file that humans aren't intended to edit, so I think we should do it.
ref: http://docs.oracle.com/javase/specs/jvms/se5.0/html/ClassFile.doc.html#88659
_vimbuiltins.py defines several large tables, and those tables combined are too large for a single method in Java.  Individually though, they're fine.
Pushed http://code.timhatch.com/hg/pygments-tim/rev/913a59849ec1

(Original comment by tshatch on 2012-11-01T16:05:36.455351+00:00)
I believe this should be fixed now -- can you confirm?

(Original comment by tshatch on 2012-11-12T23:05:05.993545+00:00)
I believe I already fixed this -- if not, please reopen.

(Original comment by rtbf*q4L6ZmlUSAa_T902yjBPDQ on 2012-12-27T10:46:36.808788+00:00)
I just tested it again and got the same error. Steps to reproduce:

Download and install Jython 2.7a2 from http://www.jython.org/downloads.html.
Download and install pip in a virtualenv according to http://www.pip-installer.org/en/latest/installing.html.
source the virtualenv and do pip install pygments.

The installation process will error out with "java.lang.RuntimeException: Method code too large!"

(Original comment by tmortagne on 2013-01-10T07:59:46.527169+00:00)
Hi guys, note that I'm using Pygments from Java since a while but I'm still using Jython 2.5.3 and I don't have any issue. I just wrote http://pygments.org/docs/java/ to indicate how I use it if you want to check. Maybe there is something wrong in 2.7 or maybe it's with a parser or a serializer I never used myself yet (did ot checked the detail of your error).

(Original comment by fengxx on 2013-01-14T08:29:17.521872+00:00)
I can not reproduce the error use Jython 2.7a2 with either JDK  1.7.0_05 or 1.6.0_33

(Original comment by rtbf*q4L6ZmlUSAa_T902yjBPDQ on 2013-01-14T22:28:25.571743+00:00)
Well I have 1.6.0_24 (Debian Wheezy) so maybe it's been fixed in newer versions?

(Original comment by tmortagne on 2013-01-22T14:45:29.817203+00:00)
Actually someone reported me that he had the exact same issue but only with the Vim language so it's not a general Pygments issue (not a Pygments issue at all anyway) but something Jython or the JVM does not like about one of the Vim lexer methods when converted to Java bytecode.

(Original comment by tmortagne on 2013-01-22T15:01:00.086034+00:00)
By the way, see http://bugs.jython.org/issue1891 for more details on Jython side about the issue.

(Original comment by birkenfeld on 2014-10-07T21:59:30.246382+00:00)
From the Jython issue:
"For the specific case of Pygments, Jython 2.7 trunk now compiles this just fine."

repo: pygments/pygments-migration-test


text:
Add Lexer for NVIDIA PTX

I'm interested in adding a Lexer for NVIDIA PTX for a project I'm working on. I see that there's some documentation here for adding a new Lexer. Would this be okay to add to the Pygments library?

Sure, we're always happy to include new lexers for new languages! Please create a PR so we can review it.

repo: pygments/pygments


text:
Windows @local/@docker support (Hello World example from tutorial doesn't work)

Describe the bug
I got error as in log below. I repeated command, but the error persist.
PowerShell 7.1.3
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

PS C:\moje\programowanie\projekty2021_2\pyinfra> & c:/moje/programowanie/projekty2021_2/pyinfra/.venv_win/Scripts/Activate.ps1
(pyinfra_venv) PS C:\moje\programowanie\projekty2021_2\pyinfra> pyinfra @docker/ubuntu:18.04 exec -- echo "hello world"
--> Loading config...
--> Loading inventory...

--> Connecting to hosts...
    [@docker/ubuntu:18.04] Connected

--> Proposed changes:
    Groups: @docker
    [@docker/ubuntu:18.04]   Operations: 1   Commands: 1

--> Beginning operation run...
--> Starting operation: Server/Shell (echo hello world)
[@docker/ubuntu:18.04] 'sh' is not recognized as an internal or external command,
[@docker/ubuntu:18.04] operable program or batch file.
    [@docker/ubuntu:18.04] Error
localhost: sha256:3a3098f7fb5bb4affdd2b9a2c31579ea4c83a144d2ca9bbb7bbe8cc803b8b40a
localhost: 45aa42d84b87499a9aa88a9592c241497c4b7466c1c5e3f31cba7737fcd03f9f
    [@docker/ubuntu:18.04] docker build complete, image ID: 3a3098f7fb5b
No hosts remaining!
--> pyinfra error:
(pyinfra_venv) PS C:\moje\programowanie\projekty2021_2\pyinfra>

To Reproduce
pyinfra @docker/ubuntu:18.04 exec -- echo "hello world"
Expected behavior
No error
Meta

Include output of pyinfra --support:

pyinfra --support
--> Support information:

    If you are having issues with pyinfra or wish to make feature requests, please
    check out the GitHub issues at https://github.com/Fizzadar/pyinfra/issues .
    When adding an issue, be sure to include the following:

    System: Windows
      Platform: Windows-10-10.0.19042-SP0
      Release: 10
      Machine: AMD64
    pyinfra: v1.4.11
    Executable: C:\moje\programowanie\projekty2021_2\pyinfra\.venv_win\Scripts\pyinfra.exe
    Python: 3.9.6 (CPython, MSC v.1929 64 bit (AMD64))

How was pyinfra installed (source/pip)?

pip in venv

Include pyinfra-debug.log (if one was created)

not created

Consider including output with -vv and --debug.

 pyinfra -vv @docker/ubuntu:18.04 exec -- echo "hello world"
--> Loading config...
--> Loading inventory...

--> Connecting to hosts...
localhost: >>> docker container inspect ubuntu:18.04
localhost: >>> docker run -d ubuntu:18.04 tail -f /dev/null
    [@docker/ubuntu:18.04] Connected

--> Proposed changes:
    Groups: @docker
    [@docker/ubuntu:18.04]   Operations: 1   Commands: 1

--> Beginning operation run...
--> Starting operation: Server/Shell (echo hello world)
[@docker/ubuntu:18.04] >>> sh -c 'docker exec -i 7a450bc13cd064cf993ab2988ba8775fbdeea08e1349bf91aedf9c9fc01d02f8 sh -c '"'"'sh -c '"'"'"'"'"'"'"'"'echo hello world'"'"'"'"'"'"'"'"''"'"''
[@docker/ubuntu:18.04] 'sh' is not recognized as an internal or external command,
[@docker/ubuntu:18.04] operable program or batch file.
    [@docker/ubuntu:18.04] Error
localhost: >>> docker commit 7a450bc13cd064cf993ab2988ba8775fbdeea08e1349bf91aedf9c9fc01d02f8
localhost: sha256:0b141c126885c0a356078ffad346607dfacd1dbfb82babeef90d2712686502cc
localhost: >>> docker rm -f 7a450bc13cd064cf993ab2988ba8775fbdeea08e1349bf91aedf9c9fc01d02f8
localhost: 7a450bc13cd064cf993ab2988ba8775fbdeea08e1349bf91aedf9c9fc01d02f8
    [@docker/ubuntu:18.04] docker build complete, image ID: 0b141c126885
No hosts remaining!
--> pyinfra error:

pyinfra --debug @docker/ubuntu:18.04 exec -- echo "hello world"
    [pyinfra_cli\main] Deploy directory remains as cwd
--> Loading config...
--> Loading inventory...
    [pyinfra_cli\inventory] Creating fake inventory...

--> Connecting to hosts...
[pyinfra\api\connectors\util] --> Waiting for exit status...
[pyinfra\api\connectors\util] --> Command exit status: 1
[pyinfra\api\connectors\util] --> Waiting for exit status...
[pyinfra\api\connectors\util] --> Command exit status: 0
    [@docker/ubuntu:18.04] Connected
    [pyinfra\api\state] Activating host: @docker/ubuntu:18.04
    [pyinfra\api\operation] Adding operation, {'Server/Shell'}, opOrder=(0,), opHash=784a97bf1955d5f7a2b9dd6c1e371e17b73c42bc

--> Proposed changes:
    Groups: @docker
    [@docker/ubuntu:18.04]   Operations: 1   Commands: 1

--> Beginning operation run...
--> Starting operation: Server/Shell (echo hello world)
    [pyinfra\api\operations] Starting operation Server/Shell on @docker/ubuntu:18.04
[pyinfra\api\connectors\local] --> Running command on localhost: sh -c 'docker exec -i e1f7dbe16ca169f6f33d6f33ca42aa220a249466d26fa35e8cc7556b4da7aaab sh -c '"'"'sh -c '"'"'"'"'"'"'"'"'echo hello world'"'"'"'"'"'"'"'"''"'"''
[@docker/ubuntu:18.04] 'sh' is not recognized as an internal or external command,
[@docker/ubuntu:18.04] operable program or batch file.
[pyinfra\api\connectors\util] --> Waiting for exit status...
[pyinfra\api\connectors\util] --> Command exit status: 1
    [@docker/ubuntu:18.04] Error
    [pyinfra\api\state] Failing hosts: @docker/ubuntu:18.04
localhost: sha256:3c26a9596d24efca7f17e60683f33a4193fc1004fa8b022a01ce87c6d92f9141
[pyinfra\api\connectors\util] --> Waiting for exit status...
[pyinfra\api\connectors\util] --> Command exit status: 0
localhost: e1f7dbe16ca169f6f33d6f33ca42aa220a249466d26fa35e8cc7556b4da7aaab
[pyinfra\api\connectors\util] --> Waiting for exit status...
[pyinfra\api\connectors\util] --> Command exit status: 0
    [@docker/ubuntu:18.04] docker build complete, image ID: 3c26a9596d24
No hosts remaining!
--> pyinfra error:

Hi @karolzlot! I believe this is due to the @docker trying to execute the local docker command insdie a unix sh shell. I've not got Windows access currently but need to double check this - I think that both @docker and @local connectors will be broken due to this.
However - it's possible to override this value via the --shell-executable CLI flag. I've not tested but one of these may work:
pyinfra --shell-executable ps @docker/ubuntu:18.04 exec -- echo "hello world"
pyinfra --shell-executable pws @docker/ubuntu:18.04 exec -- echo "hello world"

I'll be able to test this properly on my Windows laptop over the next few days.

Because this issue related let me put some research on issue and in general how to make @local works on windows:

some facts (Home, Where, Date) force shell-executable=cmd so cli option has no effect and dont work at all because @local use cmd -c  and its wrong syntax

escaping problems...pyinfra send command in single quotes so powershell -c interprets it as string and not command to execute i.e. I've try to rewrite facts that use cmd and cannot execute command because of this

--> Gathering facts...
    [pyinfra\api\facts] Getting fact: windows.Home () (ensure_hosts: None)
[pyinfra\connectors\local] --> Running command on localhost: pwsh -NoLogo -NoProfile -c 'Write-Host $env:HOMEPATH'
[@local] >>> pwsh -NoLogo -NoProfile -c 'Write-Host $env:HOMEPATH'
[@local] Write-Host $env:HOMEPATH
[pyinfra\connectors\util] --> Waiting for exit status...
[pyinfra\connectors\util] --> Command exit status: 0
    [@local] Loaded fact windows.Home

--> Fact data for: windows.Home
{
    "@local": "Write-Host $env:HOMEPATH\r"
}

problems with parsing cli commands in powershell (could be my personal issue or related to 1) i.e.$>pyinfra.exe @local --shell-executable=pwsh exec -- ls
Invalid operations: ('ls',)

same command in cmd works as expected

Moving this to pyinfra-windows for potential support via a new connector specific for Windows @windowslocal or something..

authors: Fizzadar hornyjailfish karolzlot

repo: pyinfra-dev/pyinfra


text:
Add example notebooks for pyiron_base

@muh-hassani Can you add the notebooks from https://github.com/pyiron/pyiron_base/tree/master/notebooks to be included in pyiron_base ? And then they should also be included in the tests.

I will.

authors: jan-janssen muh-hassani

repo: pyiron/docker-stacks


text:
Should we add the Material Digital Workshops?

@samwaseda created a pyiron workshop for material digital :package: and Muhammad did something similar some time ago :package: :memo: :tv:. Should we add those to the list of pyiron workshops?

I see no problem with adding it, @samwaseda could please add the workflow here?

Also adding the DAMASK example would be great https://github.com/materialdigital/pyiron-workflow-damask

We should also add the workshop to precice https://github.com/max-hassani/precice_workshop

We can also add the recent demonstration from @mbruns91 https://github.com/mbruns91/PMD-pyiron_SPARQL_demonstrator

I'm happy if this is added, but please use the fork on https://github.com/materialdigital/PMD-pyiron_SPARQL_demonstrator which is more up-to-date.
Maybe also add a notion, that this repsoitory will undergo larger changes from time to time?

authors: jan-janssen mbruns91 srmnitc

repo: pyiron/workshops


text:
Rename copierlog to copier-answers across the codebase

The initial implementation in https://github.com/pykong/copier/pull/103 was calling the file logfile, but it was renamed to copier-answers later.
However I discovered there are still a few remainders of the old implementation.
Here I remove them.
@Tecnativa TT20357

@Yajo There are conflicts. Can you resolve them?

Yes, done

Merged, LGTME. THX.

authors: Yajo pykong

repo: pykong/copier


text:
[WIP] fix: fix lag in live mode after mda acquisition

I've noticed that after opening napari-micromanager the live mode works well without any lag. However, after running a MDA acquisition, the live mode starts to lag. See video below to see this behavior.
As a proposed solution, I modified the CoreViewerLink class and use the same QTimer pattern that we use in the pymmcore-widgets ImagePreview widget (https://github.com/pymmcore-plus/pymmcore-widgets/blob/d5d38c9cc24bc2ac99b5921ac2593a4037d258fb/src/pymmcore_widgets/_image_widget.py#L18).

CURRENT
https://github.com/pymmcore-plus/napari-micromanager/assets/70725613/3440ba20-afb3-46e9-8c94-8ab5a4863029
FIX
https://github.com/pymmcore-plus/napari-micromanager/assets/70725613/b4c790a2-697f-4103-9685-fca549364e65

I think that ultimately, the problem here is the getExposure with a Hamamatsu camera is returning an artificially high exposure time as of December 14th 2023.  See https://github.com/micro-manager/mmCoreAndDevices/issues/442
So I think this can be closed.

repo: pymmcore-plus/napari-micromanager


text:
Fix --xxxend-only and only kill its related port

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

New Feature Submission:
Changes To Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.

This PR is to fix issue https://github.com/pynecone-io/pynecone/issues/786 and improve something too.
The original code will kill two ports even using --no-backend or --no-frontend.
I changed --no-backend into --frontend-only and fixed the issue I found out above.
In the source code, we know --port is means frontend port, but people may misunderstand here.
So I add --backend-port. When people type pc run --help, they will get the following information.
Usage: pc run [OPTIONS]

  Run the app in the current directory.

Options:
  --env [dev|prod]                The environment to run the app in.
                                  [default: Env.DEV]
  --frontend-only                 Enable execution only frontend.
  --backend-only                  Enable execution only backend.
  --loglevel [debug|info|warning|error|critical]
                                  The log level to use.  [default:
                                  LogLevel.ERROR]
  --port TEXT                     Specify a different frontend port.
  --backend-port TEXT             Specify a different backend port.
  --help                          Show this message and exit.

It makes developers understand quickly without misunderstanding.
In the future, I suggest we can add  --api-url too. It could make the pc run command more friendly to the web app developer.
b. Describe your changes.

--no-backend -> --frontend-only

--no-frontend -> --backend-only

only ask to kill frontend port when using --frontend-only and the port conflict

only ask to kill backend port when using --backend-only and the port conflict
c. Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
closes #786

Close it because I miss the case when
people don't use  --backend-only and  --frontend-only
I will send a new pull request. to handle it

repo: pynecone-io/pynecone