Add spotify downloader

file for spotify downloader

script for spotify downloader
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #607 (issue_no)
Replace issue_no with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] My documentation follows Template for README.md
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@Sibasish-Padhy you copied your code from here. Only few parameter names have been changed, rest everything is same.

@santushtisharma10 Actually @Sibasish-Padhy contacted me on discord that he needs help to refine the code that' why I told him to create a draft PR so that we can suggest to him how he can create different code other than the already available implementation. Therefore, it is not the case of plagiarism, this was a draft PR and not the final PR

okay @kaustubhgupta

Thank you sir for all your help but last night unfortunately I went through some laptop issues and hence my laptop's under repair right now I don't wanna waste much of your value worth time right now and so I request you all to unassign me this issue and assign it to someone else .I will take a couple of days and then I will be back to claim on some other issue.Thank you @kaustubhgupta sir for giving me a chance to work on this beginner friendly issue and sorry for letting you down.It was great fun to learn about this script .Please do give me the same opportunities ahead to contribute to your projects ahead in the 3 months journey.Thank you @kaustubhgupta sir

@Sibasish-Padhy If you want, we can give you a week extra for this. Let me know your final decision

Sir my laptop will be back till Tuesday and I can again start working on it from Wednesday so I think I will be able to draft A pr till Friday/next weekend .Thank you sir yes , I would certainly opt for it @kaustubhgupta sir.thank you

@Sibasish-Padhy any updates?

@kaustubhgupta sir will try to darft a PR till Sunday.. My laptop's still under repair.. If it wouldn't be possible then I would update you about it on saturday... And then you can reassign this issue. Thank you

@kaustubhgupta sir you can reassign this issue to someone else.I will get my laptop back today evening.. So it wouldn't  be possible I think. Thank you for giving me the opportunity will work again on another issue soon


[1.16.1]reload the datapack causes the command to fail

This needs more info, logs etc.

I found nothing useful after reloading in 1.16.3 sadly, only this
reload
Reloading!
Registering 1 commands.
Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
Reloading ResourceManager: Default, PumpkinPotions-1.16.3-1.0.3.jar, cucurbita-1.16.3-1.0.13.jar, forge-1.16.3-geckolib-2.1.2.jar, jei-1.16.3-<IP_ADDRESS>.jar, AttributeFix-1.16.3-8.0.2.jar, spookarms-<IP_ADDRESS>.jar, EyesInTheDarkness-1.16.3-0.7.0.jar, Splashy-1.16.3-5.0.1.jar, immortuoscalyx-1.1.4.jar, Clumps-<IP_ADDRESS>.jar, FastWorkbench-1.16.3-4.4.0.jar, Controlling-<IP_ADDRESS>.jar, Placebo-1.16.3-4.3.3.jar, froglins-1.16.3-<IP_ADDRESS>.jar, LibX-1.16.3-1.0.2.jar, Bookshelf-1.16.3-8.7.20.jar, Tips-1.16.3-2.0.13.jar, Undercover Witches 1.0.1.jar, FastFurnace-1.16.3-4.3.0.jar, spooky-autumn-forests.jar, paranoia-1.16.3-<IP_ADDRESS>.jar, Toast-Control-1.16.3-4.3.0.jar, lorespawn-1.16.3-0.0.4.jar, mystical_pumpkins-0.1.4.jar, CorruptedLand-1.1d.jar, forge-1.16.3-34.1.35-universal.jar, PumpkinSpiceEverything-1.0.8.jar, OpenLoader-1.16.3-7.0.3.jar, quickspawns-1.16.2-1.0.1.jar, quickhomes-1.16.3-1.2.6.jar, spark-forge-1.16.3.jar, Morpheus-1.16.3-4.2.63.jar, travellers_map-1.16.2-0.6.4.jar
Loaded 10 recipes
Registered 0 additional loot tables.
Loaded 940 advancements
Registered 0 additional recipes.
Using new advancement loading for net.minecraft.advancements.PlayerAdvancements@62fac30f
Could not serialize net.minecraftforge.server.command.ModIdArgument@7b75f9a9 (class net.minecraftforge.server.command.ModIdArgument) - will not be sent to client!
Could not serialize net.minecraftforge.server.command.EnumArgument@76e320c9 (class net.minecraftforge.server.command.EnumArgument) - will not be sent to client!
Saving the game (this may take a moment!)
Saved the game

Hmmm, does reload unregister commands? If so it's probably because it is only registered in setup. Is there an event for command registration?

I'm not sure after 1.12 myself, I've a PR waiting to be finished/commented on by Lukas for client side commands because after 1.12 is WAAAy out of my area sadly Prod him on Discord or I can link you to his PR for one of my mods if that might be of any use to you

Found this from https://github.com/sinkillerj/ProjectE/issues/2128. The issue is that FMLServerStartingEvent is still being used to register commands instead of RegisterCommandsEvent. This means that when vanilla nukes the existing DataPackRegistry and creates a new instance your commands are not present as they aren't being registered again to the new DataPackRegistry

Yeah. I'd known about this. Thanks for letting me know though, in case I hadn't!
Don't really get around to updating this set of mods much. Most of the work is doing the actual release and not the fixes :3

I was gonna say xD I had completely forgotten this was open myself 😹

Is it really much more complicated than a find & replace?


Jetbrains IDE .idea

The configuration directory of IDE's Jetbrains .idea don't works.
I suggest you put /.idea. Because it worked for me.

I did not find any issue with this information. If there is one like that already, I'm sorry.

Can I close this then?


Remove render() calls from API tests.

Removing render() calls from BasicFormBuilderTest.php tests (they should auto-render).  If render() is not required in practical use:
{!! BootForm::inlineRadio('Hidden', 'visibility') !!}

Then render() should not be called in your BasicFormBuilderTest.php tests.  Thoughts?

Coverage increased (+0.38%) to 89.39% when pulling c756557b42e986d1754df3c240f425660c917b9d on JerseyMilker:why-render into c4190c4430b6581f1a6d9d97905243848fe45244 on adamwathan:master.

Like we talked about last night, I think I'd rather keep the expicit render calls, because each of those functions returns some sort of object, not a string, the object just happens to implement __toString() and PHPUnit happens to try and coerce the object into a string if it's comparing it to a string.
Without render, we are saying:
$this->assertEquals('some string', $someObject);

...which is a bit deceiving.
They'll auto render if cast to a string, but that's a different behavior that I think should be covered by another test for each specific element.

Fair.  I understand your viewpoint there.  I just think it's valuable to test the API as it's intended to be used, which is without render().
// User doesn't call render() method in their templating:
$bootforms->text('Label', 'field');

This came up because your test was passing for my inlineRadio() PR, despite my error in forgetting to render the returned label object:
public function render()
{
	if ($this->inline === true) {
		// This returns label object, so I need to chain render() onto label.
		return $this->label;
	}

	// ...
}

Laravel throws error, but tests are still passing because the test itself calls render() explicitly.  Hence the reason I suggested testing the API as it's intended to be used.

Well what Laravel is doing when you call {!! BootForm::text('Label', 'field') !!} is actually calling echo BootForm::text('Label', 'field') which is actually calling echo (string) BootForm::text('Label', 'field') which is actually calling echo BootForm::text('Label', 'field')->render(), so it's not that it's intended to be used without calling render, just the opposite really. It only works when you call render, haha... There just happens to be ways of calling render without calling it explicitly.
This set of tests is what makes the most sense to me:
public function test_inlining_a_radio_button_returns_a_check_group()
{
    $inline = $bootform->radio()->inline(); // or whatever
    $this->assertInstanceOf('CheckGroup'); // or whatever
}

public function test_check_groups_can_be_rendered_through_casting()
{
    $inline = $bootform->radio()->inline(); // or whatever
    $this->assertEquals($inline->render(), (string) $inline);
}

public function test_can_inline_radio_button()
{
    $result = $bootform->radio()->inline()->render(); // or whatever
    $this->assertEquals('<some>html</some>', $result);
}

Know what I mean?

If you did $this->assertSame($expected, $nonRenderedElement) you'd get a failing test too, because you're comparing a string to an object, it's just a lucky coincidence that PHPUnit casts it to a string for you.
I dunno. I think it's confusing to look at the test and see it being compared to a string, because it makes you think it's returning a string, but it's not.

Ahh lol. Gotter otter!


Recovery Mode due to a Configuration Error

Whenever I try to do my assignment it says that it is in recovery mode due to a configuration error. Could you please help me fix this issue?
Version: 1.95.2
Commit: e8653663e8840adaf45af01eab5c627a5af81807
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

do my assignment

Please use your course support channel.
/question


CI build hangs during pod installation after adding rndi.

Summary
Hey guys, I added react-native-device-info to my project, some really useful data, thank you! I stumbled upon this issue however, this library adds following pod 'RNDeviceInfo', :path => '../node_modules/react-native-device-info' for some reason it also relies on React pod?
When I'm running my build in CI, my pod install step hangs at this bit
Installing RNDeviceInfo (0.17.4)
Installing React (0.11.0)

Any ideas on the fix? Why are we installing React pod by the way? It was deprecated.

Version
^0.17.4

Affected OS
iOS

OS Version
10

Current behavior
pod install hangs.

Expected behavior
Should install pods without any issues

Hi @IljaDaderko, never used pods so I'm not sure what to do here.
Would you like to open a PR to remove the React pod if that's the problem?

@machour sorry for late response, I attempted it here
https://github.com/rebeccahughes/react-native-device-info/pull/361
Tested locally seems to be working fine, but same as you my knowledge of cocoapod space is limited, I'm not sure why it was needed as dependency in this projects podspec, but React pod was deprecated looooong ago and it is not recommended at all to use it.

Pod::Spec.new do |s|
  s.name         = "RNDeviceInfo"
  s.version      = "0.21.5"
  s.summary      = "Device Information for react-native"

  s.homepage     = "https://github.com/rebeccahughes/react-native-device-info"

  s.license      = "MIT"
  s.authors      = { "Rebecca Hughes" =><EMAIL_ADDRESS>}
  s.ios.deployment_target = '8.0'
  s.tvos.deployment_target = '10.0'

  s.source       = { :git => "https://github.com/rebeccahughes/react-native-device-info.git" }

  s.source_files  = "ios/RNDeviceInfo/*.{h,m}"

  s.dependency 'React'
end

please remove dependency of react -  still appears - is it not removed yet?

Hi, please don't comment on closed issues.


Add more examples on how to use the actions

🐞 Problem
So far, each one of the actions contains a small gist explaining how to use it. These examples are quite trivial, containing only one step.
However, most of the projects within PyAnsys require to install a server to access all the logic through the Python library. How to combine this step with the pyansys/actions is not explained, even though it is a simple task.
💡 Idea
We could create a Examples section showing more complex jobs or add more examples next to each one of the actions.

This idea came to me after discussing with @GuillemBarroso how to combine pyansys actions with dpf actions.

That is an excellent idea @jorgepiloto and @GuillemBarroso . It will help all the teams for sure.

The specially critical one is the testing and documentation actions. Those are typically dependent on running a server... It's going to be difficult to sample this behaviour on a standalone repo (like the dev docs, sphinx theme etc). We need a server-based project (PyMAPDL, PyFluent, PyAEDT, PyGeometry... ).

Ha! You're totally right @jorgepiloto! Let's do that!


Consider removing direct dependency on DataFrames

DataFrames is an heavy dependency. Currently, it is used only in the neural snow model (which we can move to an extension) and in the PFTs (https://github.com/CliMA/ClimaLand.jl/blob/main/src/standalone/Vegetation/pfts.jl)
It would be great if we could avoid using DataFrames in pfts.jl as that would allow us to remove the dependency

@Espeer5 do you think it would be possible/easy to implement the pft module without using DataFrames.jl?

DataFrames was removed as direct dependency in #749


Improve the sandbox

remove faucet in mainnet mode
work on all the things 💪🏼

would be great to also review https://github.com/blockstack/explorer/issues/290 as part of this

would be great to also review https://github.com/blockstack/explorer/issues/290 as part of this


job was getting redefined in for loop (fix to #191)

After some debugging, I realised that my earlier pull request https://github.com/ivx/yet-another-cloudwatch-exporter/pull/191 had a problem with jobs handling (I had four jobs, 10 metrics, but only got results from one job). After debugging, I realised that go coroutines in scrapeAwsData also need job variable as parameter, so that for loop will not change its value while the coroutines while the scraping is going on.
On a fix, I had to rename job to discoveryJob or staticJob, because I couldn't define go func(job job, ...)

Thanks!


docs: Use reproducible Nix expression

Hi Victor @l0b0 thank you for this pull request.
If you could answer the question from Nissar @funilrys that would be great.
Take note: we have 16 different main readme.md files in this repo, one for each variant.  All those readme.md are generated from the readme_template.md file in the root of this repo.  So that's where this change should go, presuming it's justifiable on merits. 👍🏻

Seeing no followup, I am closing this.


Twitter: “No webmention targets” for tweet with target

Hi @snarfed,
this tweet has a backlink to my site in it, but Bridgy doesn't catch the link: https://twitter.com/beep/status/831136280465522689

Is this the relevant part of the poll log?
Original post discovery found original posts set([u'https://matthiasott.com/articles/patterns-beyond-context']), mentions set([])
Demoting original post links because user tag:twitter.com,2013:m_ott doesn't match author tag:twitter.com,2013:beep
starting posse post discovery with syndicated https://twitter.com/beep/status/831136280465522689
requests.head https://matthiasott.com/ {'headers': {'User-Agent': '...'}}
fetching author url https://matthiasott.com/
requests.get https://matthiasott.com/ {'headers': {'User-Agent': '...'}}
No h-feed found, fallback to top-level h-entrys.
posse post discovery found no relationship for https://twitter.com/beep/status/831136280465522689

It works like charm for other tweets linking to the same URL, though:
https://twitter.com/m_ott/status/831047069251039232
https://twitter.com/c_huggins/status/831148577544138754
https://twitter.com/chopeh/status/831141013582405632
Thanks for any help, Ryan  – and also huge thanks for Bridgy!

thanks for reporting!
not sure what's up here. the usual first stop for debugging these is https://brid.gy/about#missing , but bridgy clearly found this tweet, and backfeed similar tweets with links to the same post, so you're comfortably beyond the things to check in that docs link. i'll look soon.

Thanks Ryan! If there is anything I can do to help, just let me know.

looks like this finally made it through to your site! https://matthiasott.com/articles/patterns-beyond-context#webmention-source
tentatively closing. feel free to reopen.


Error in "python setup.py install"

What should I do in such a situation?
/home1/pan-internship-1/anaconda3/envs/pytorch/lib/python3.6/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  setuptools.SetuptoolsDeprecationWarning,
/home1/pan-internship-1/anaconda3/envs/pytorch/lib/python3.6/site-packages/setuptools/command/easy_install.py:159: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  EasyInstallDeprecationWarning,
running bdist_egg
running egg_info
writing index_max.egg-info/PKG-INFO
writing dependency_links to index_max.egg-info/dependency_links.txt
writing top-level names to index_max.egg-info/top_level.txt
reading manifest file 'index_max.egg-info/SOURCES.txt'
writing manifest file 'index_max.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
building 'index_max' extension
Emitting ninja build file /home1/pan-internship-1/3D/SO-Net/models/index_max_ext/build/temp.linux-x86_64-3.6/build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
1.10.2.git.kitware.jobserver-1
g++ -pthread -shared -L/home1/pan-internship-1/anaconda3/envs/pytorch/lib -Wl,-rpath=/home1/pan-internship-1/anaconda3/envs/pytorch/lib,--no-as-needed /home1/pan-internship-1/3D/SO-Net/models/index_max_ext/build/temp.linux-x86_64-3.6/index_max.o /home1/pan-internship-1/3D/SO-Net/models/index_max_ext/build/temp.linux-x86_64-3.6/index_max_cuda.o -L/home1/pan-internship-1/anaconda3/envs/pytorch/lib/python3.6/site-packages/torch/lib -L/home1/pan-internship-1/cuda/cuda_10.1/lib64 -L/home1/pan-internship-1/anaconda3/envs/pytorch/lib -lc10 -ltorch -ltorch_cpu -ltorch_python -lcudart -lc10_cuda -ltorch_cuda -lpython3.6m -o build/lib.linux-x86_64-3.6/index_max.cpython-36m-x86_64-linux-gnu.so
g++: error: /home1/pan-internship-1/3D/SO-Net/models/index_max_ext/build/temp.linux-x86_64-3.6/index_max.o: No such file or directory
g++: error: /home1/pan-internship-1/3D/SO-Net/models/index_max_ext/build/temp.linux-x86_64-3.6/index_max_cuda.o: No such file or directory
error: command 'g++' failed with exit status 1```

I have solved this problem. I reinstalled a new conda environment and succeeded with torch 1.2.


updates README, corrections

Codecov Report

Merging #207 (2880e18) into main (a3656fb) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #207   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           55        55
  Lines         5123      5122    -1
=========================================
- Hits          5123      5122    -1

Impacted Files
Coverage Δ

blacksheep/server/authentication/jwt.py
100.00% <100.00%> (ø)

blacksheep/server/authentication/oidc.py
100.00% <100.00%> (ø)

blacksheep/server/controllers.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Bug on handling conversion from a choice type

The following cql results in the following c#:
define "Initial Population":
  (AgeInYearsAt(start of "Measurement Period") >= 16) and exists("Injury due to falling rock within measurement period")

	private IEnumerable<Condition> Injury_due_to_falling_rock_within_measurement_period_Value()
	{
		CqlValueSet a_ = this.Injury_due_to_falling_rock();
		IEnumerable<Condition> b_ = context.Operators.RetrieveByValueSet<Condition>(a_, default);
		bool? c_(Condition C)
		{
			DataType e_ = C?.Onset;
			object f_ = context.Operators.LateBoundProperty<object>(e_, "value"); // REF#1
			CqlInterval<CqlDateTime> g_ = this.Measurement_Period();
			bool? h_ = context.Operators.In<CqlDateTime>(f_ as CqlDateTime /* REF#2 */, g_, default);

			return h_;
		};
		IEnumerable<Condition> d_ = context.Operators.Where<Condition>(b_, c_);
		return d_;
	}

The latebound property returns a choice type (REF#1). At this stage we do not have a C# equivalent type for this, so object is used. Unfortunately this can easily allow one to make assumptions when casting, such as at REF#2, where a safe cast is made to CqlDateTime. At runtime, the actual type was a string, so this did not work.
Instead, when choice types are to be converted, the runtime ICqlOperators.Convert<T>(object) must be invoked.

The CQL in the issue doesn't match the generated C#.  What is the CQL for "Injury due to falling rock within measurement period"?
I don't believe the proposed fix is correct.
Specifically:

At runtime, the actual type was a string, so this did not work.

Things are allowed to not work if the runtime type is not correct.  I do not think invoking any kind of conversion is correct in this case.

RR23_LIB_Umbrella_Measure.json
Here’s the library that we used for testing


Support additional directories in module search path

I am using the app-module-path package in my app, and there is something I'd love to be able to configure in jsconfig.json so I can navigate between files more easily.
Consider this structure:
// a/foo.js
require('app-module-path').addPath(process.cwd());

var bar = require('b/bar')

bar()

// b/bar.js
module.exports = function () { console.log('bar') }

$ node a/foo.js
"bar"

Unfortunately hovering require('b/bar') or CMD+Click on b/bar doesn't open b/bar.js.
Is there a way we could enter these kinds of re-mapped paths in jsconfig.json (or other)?

This issue was moved to Microsoft/TypeScript#10127


Support for ROS Melodic?

Hi Marina,
I am trying to integrate your lattice planner (alongside the entire human aware navigation package) into my current project which runs on ROS Melodic and porting issues (since it's originally written for ROS Indigo) have been a headache as I just started learning ROS. As it is a shared project with many other researchers, running in ROS Indigo is not quite an option.
Wonder if this package has support for ROS Melodic or do you have any tips that you can share? I would gladly appreciate it.
Regards,
Marcus

Hi Marcus,
I am not actively using this code at the moment, thats why it is taking a bit. I am on it to make it work for melodic. Give me a few days.
Best,
Marina

Hi Marcus,
I updated the code for melodic. Please look at the human_aware_navigation wiki to check how to get the melodic code and run the framework with toy example. I hope everything works out, please test it and close the issue if it all works as expected. If you run into problems, let me know.
Best,
Marina


Update the Friend bot page

I have added content to the Friend Bot page under Tutorials > Examples > Advanced section. Also, I have updated the Friend bot link in Tutorials > Overview to point to the correct page.
The page looks like this:

Tag #891

@Rohitesh-Kumar-Jain and @proudofsimin I think this PR can be added to #1056

ping @Rohitesh-Kumar-Jain

@sbis04  pls resolve the conflict, and then ping for merge

@Rohitesh-Kumar-Jain I have fixed the merge conflict. Please merge this, after that I'll fix the merge conflict of #1155 as well


Feature Request: Support a flag to specify whether to authenticate as a user or machine

Checklist

[X] I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved
While recently updating our quickstart guides to use the CLI, I noted an area of improvement that would be great to address.
It would be helpful if users could provide a command line flag when using the login command to specify whether to authenticate as a user or machine rather than requiring input. This would simplify our documentation by keeping guidance in a copy-and-paste format without extra direction and reducing the chances of a user overlooking said direction and needing clarification on which to choose (which has happened, based on recent QS feedback.)
Describe the ideal solution
auth0 login accepts a command line flag to specify signing in as a user or machine without input.
Perhaps something like auth0 login --as user/auth0 login --as machine, or a direct alias like auth0 login --user/auth0 login --machine.
Alternatives and current workarounds
No response
Additional context
No response

Dear valued user,
We had considered those exact flags during initial implementation of the login function. However, we realized that there were flags that allowed you to "skip" the choice of login mechanism:
As User: auth0 login --domain <tenant-domain> --client-id <client-id> --client-secret <client-secret>
As Machine: auth0 login --no-input
Admittedly, the --no-input flag is not immediately intuitive and a --as-user could certainly be added in the future.
Does the above help?

Hey @willvedd! 😆
The "as user" guidance example you provided would definitely work, but this would require more leg work for the end user than would be ideal, from a DX perspective anyway.
There's a bit of a chicken-and-the-egg situation, too. If you take a look at how I wrote the quickstart as an example, they won't have that information before authenticating the CLI to be able to do this: https://auth0.com/docs/quickstart/webapp/laravel/01-login#sdk-configuration
(No fires on this (and my other) suggestion by the way, just rough areas I noticed that we could consider improving to ease CLI adoption for use with the SDKs! ❤)


postmessage data invalid json:  SyntaxError: Unexpected token F(…)

I am getting a console log with the following message upon loading the iframe sent from seamless.parent.min.js:2
postmessage data invalid json:  SyntaxError: Unexpected token F(…)

Cannot reproduce. Please try latest version.

I guess that error is also occurs in the browser console when you accesses the page of the library
http://travistidwell.com/seamless.js/


Define forward and backward differentiation rules for contract on EinExpr

Closes #12

Backward derivation rules are on the way.

@emapuljak @jofrevalles I've finished implementing the reverse derivation rule. I'm merging directly since the structure of the tests is more or less the same as with frule.
If you have any suggestion or question, ask me through Mattermost or write an issue.


Beacon node active handles after close sequence is completed

Describe the bug
In some rare cases when the node is running for a longer time it does not exit when receiving a exit signal.
Active handles
[WTF Node?] open handles:
- File descriptors: (note: stdio always exists)
  - fd 2 (tty) (stdio)
  - fd 1 (tty) (stdio)
  - fd 0 (tty)
- Sockets:
  - <IP_ADDRESS>:9000 -> undefined:undefined
  - <IP_ADDRESS>:9000 -> undefined:undefined
.... (45 more)
  - <IP_ADDRESS>:9000 -> undefined:undefined
  - <IP_ADDRESS>:9000 -> <IP_ADDRESS>:45906
  - <IP_ADDRESS>:9000 -> <IP_ADDRESS>:9252
- Servers:
  - <IP_ADDRESS>:9000 (TCP)
    - Listeners:
      - connection: bound onSocket @ file:///home/devops/goerli/lodestar/node_modules/@libp2p/tcp/src/listener.ts:78
- Timers:
  - (30000 ~ 30 s) (anonymous) @ /home/devops/goerli/lodestar/node_modules/retimer/retimer.js:25

The Sockets that show <IP_ADDRESS>:9000 -> undefined:undefined can probably be ignored as those are also there if beacon node exits correctly.
Debug logs
Jun-14 09:58:42.886[network]       verbose: Failed to send goodbye peer=16...3dHdMu Timeout
Error: Timeout
    at timeoutPromise (file:///home/devops/goerli/lodestar/packages/utils/src/timeout.ts:15:11)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at processTimers (node:internal/timers:512:7)
    at withTimeout (file:///home/devops/goerli/lodestar/packages/utils/src/timeout.ts:19:12)
    at PeerManager.goodbyeAndDisconnect (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/peers/peerManager.ts:648:7)
    at async Promise.all (index 50)
    at PeerManager.goodbyeAndDisconnectAllPeers (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/peers/peerManager.ts:223:5)
    at NetworkCore.close (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/core/networkCore.ts:255:5)
    at Network.close (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/network.ts:197:5)
Jun-14 09:58:42.887[network]       verbose: Req  done method=goodbye, version=1, encoding=ssz_snappy, client=Lighthouse, peer=16...3dHdMu, requestId=1769
Jun-14 09:58:42.887[network]       verbose: Failed to send goodbye peer=16...GW2Ein Timeout
Error: Timeout
    at timeoutPromise (file:///home/devops/goerli/lodestar/packages/utils/src/timeout.ts:15:11)
    at withTimeout (file:///home/devops/goerli/lodestar/packages/utils/src/timeout.ts:19:12)
    at PeerManager.goodbyeAndDisconnect (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/peers/peerManager.ts:648:7)
    at async Promise.all (index 54)
    at PeerManager.goodbyeAndDisconnectAllPeers (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/peers/peerManager.ts:223:5)
    at NetworkCore.close (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/core/networkCore.ts:255:5)
    at Network.close (file:///home/devops/goerli/lodestar/packages/beacon-node/src/network/network.ts:197:5)
    at BeaconNode.close (file:///home/devops/goerli/lodestar/packages/beacon-node/src/node/nodejs.ts:316:7)
    at EventTarget.abortController.signal.addEventListener.once (file:///home/devops/goerli/lodestar/packages/cli/src/cmds/beacon/handler.ts:137:11)
Jun-14 09:58:42.889[network]         debug: network sent goodbye to all peers
Jun-14 09:58:42.889[network]       verbose: Req  done method=goodbye, version=1, encoding=ssz_snappy, client=Teku, peer=16...GW2Ein, requestId=1773
Jun-14 09:58:42.932[network]         debug: network peerManager closed
Jun-14 09:58:42.934[network]         debug: network gossip closed
Jun-14 09:58:43.038[network]         debug: Dialing discovered peer peer=16...HRUh4M
Jun-14 09:58:43.038[network]         debug: Dialing discovered peer peer=16...zqJUKj
Jun-14 09:58:43.130[network]         debug: network reqResp closed
Jun-14 09:58:43.146[network]         debug: Error dialing discovered peer peer=16...m56aPB All promises were rejected
AggregateError: All promises were rejected
Jun-14 09:58:43.146[network]         debug: Error dialing discovered peer peer=16...MS9Luf All promises were rejected
AggregateError: All promises were rejected
Jun-14 09:58:43.146[network]         debug: Error dialing discovered peer peer=16...HRUh4M All promises were rejected
AggregateError: All promises were rejected
Jun-14 09:58:43.152[network]         debug: Error dialing discovered peer peer=16...zqJUKj All promises were rejected
AggregateError: All promises were rejected
Jun-14 09:58:43.152[network]         debug: Error dialing discovered peer peer=16...yH119U All promises were rejected
AggregateError: All promises were rejected
Jun-14 09:58:43.153[network]         debug: network lib2p closed
Jun-14 09:58:43.153[network]         debug: network core closed
Jun-14 09:58:43.649[chain]         verbose: Archived finalized state finalizedEpoch=182885
Jun-14 09:58:44.617[]                debug: Beacon node closed

What looks really suspicious is that we are dialing peers after network is already closed
Jun-14 09:58:43.038[network]         debug: Dialing discovered peer peer=16...HRUh4M
Jun-14 09:58:43.038[network]         debug: Dialing discovered peer peer=16...zqJUKj

Expected behavior
Beacon node should always exit process after close sequence succeeds. No explicit process.exit should be required.
Steps to reproduce
Run beacon node for a while with the following command (or similar)
./lodestar beacon \
    --dataDir /home/devops/goerli/data/beacon \
    --rest \
    --rest.address "<IP_ADDRESS>" \
    --rest.namespace '*' \
    --metrics \
    --execution.urls http://localhost:8551 \
    --jwt-secret /home/devops/goerli/data/jwtsecret \
    --logLevel info \
    --network goerli \
    --checkpointSyncUrl "https://beaconstate-goerli.chainsafe.io/"

CTRL + C to exit gracefully and observe that it is not shutting down even though close sequence is executed successfully.
Operating system
Linux
Lodestar version or commit hash
unstable (bf5842733a738c59a6f9aa147496806fb2d4c98f)

The issue seems to be fixed with upgrade to libp2p to 0.45.9 in 7280234bea66b49da3900b916a1b54c4666e4173.
The PR that fixed the issue:

https://github.com/ChainSafe/js-libp2p-gossipsub/pull/438

Reopening as issue does not yet seem to be resolved.
Looks like we are pinging peers after sending goodbye
Jun-25 02:58:27.655[network]         debug: Req  dialing peer method=goodbye, version=1, encoding=ssz_snappy, client=Lighthouse, peer=16...VYqoz3, requestId=295952

Jun-25 02:58:27.903[network]         debug: Req  received method=ping, client=Lighthouse, peer=16...VYqoz3, requestId=295961
Jun-25 02:58:27.903[network]       verbose: Resp done method=ping, client=Lighthouse, peer=16...VYqoz3, requestId=295961

or still dialing peers while disconnecting (goodbyeAndDisconnectAllPeers)
Jun-25 02:58:28.311[network]         debug: Req  dialing peer method=metadata, version=2, encoding=ssz_snappy, client=Unknown, peer=16...ohL5Xo, requestId=295963

Based on the current network close sequence it looks like we close the peer manager after disconnecting peers which could explain this behavior
https://github.com/ChainSafe/lodestar/blob/85ff3cf17e9f8338865cc66f129f9e60e0ec029b/packages/beacon-node/src/network/core/networkCore.ts#L253-L256
as only after closing, the intervals and event listeners are removed
https://github.com/ChainSafe/lodestar/blob/85ff3cf17e9f8338865cc66f129f9e60e0ec029b/packages/beacon-node/src/network/peers/peerManager.ts#L203-L212
Changing the order of the closing sequence will likely fix the issue, but extensive testing is required as this issue is hard to reproduce.

Potential fix has been merged to unstable

https://github.com/ChainSafe/lodestar/pull/6015

It is hard to verify if this actually fixed the issue due to the fact that it  is not really reproducible and happens rarely.
Two things have to be done to confirm a fix

set --network.useWorker false and
explicit exit has to be removed
https://github.com/ChainSafe/lodestar/blob/ab2dfdde652b0b0e4e9b2b96f8d8ee08fec6b720/packages/cli/src/cmds/beacon/handler.ts#L136
then run beacon node for multiple hours and shutdown process, likely after a week of doing that without hanging process we can be confident enough and close this issue

Note: there is a chance that the process would also hang with --network.useWorker true set (https://github.com/ChainSafe/lodestar/issues/5775 <-- this issue was still observed recently) but this happened even less often, hence it is harder to confirm a fix of the issue.

@nflaig I think this issue is resolved now?

I don't think so, did libp2p releae a fix for this? Since we switched to running libp2p in a worker we get a differnet issue https://github.com/ChainSafe/lodestar/issues/5775 but this one should be reproduce by setting --network.useWorker false


[chore]: bump CI cache version

I think the switch from using actions-rs/toolchain to the default version of rust affected the build artifacts.

Looks like there was no effect from switching from actions-rs/toolchain to the default install of rust.


Need Help on React-Dropdown

Thanks for awesome lib. Im using React-Dropdown On the table I want to display drop-down in inside the table column name. when I click the icon it's showing menu inside the column only.   I'm not able to see full menu need to append in Body please help me on this

outside table its showing correctly

Your table container have the "overflow: hidden" proprty so that dropdown menu it getting clipped. You have to fix this problem on the your table component.

Thanks for Response If I remove overflow hidden getting dropdown. but the table rows and columns collapsed. There is any alternate solution @cheton  :(

You may have to allow custom styling for dropdown, not applying the rule to the whole table.

A hack for modifying the style of its parent node:
<Dropdown
    ref={node => {
        if (node) {
            const dropdownElement = ReactDOM.findDOMNode(node);
            dropdownElement.parentNode.style.overflow = 'initial';
        }
    }}
>
    :   :   :
</Dropdown>


[Solution] -Leetcode Two Sum in C++

Description
1. Two Sum
The problem asks for two indices in an array of integers such that the elements at these indices add up to a given target value. The initial thought is to use a hash table (unordered_map in C++) to keep track of elements and their indices while iterating through the array. This approach allows us to efficiently check if a complement (the value needed to reach the target) exists in the array.
DSA Problem
Given an array of integers nums and an integer target, return indices of the two numbers such that they add up to target.
You may assume that each input would have exactly one solution, and you may not use the same element twice.
You can return the answer in any order.
Example 1:
Input: nums = [2,7,11,15], target = 9
Output: [0,1]
Explanation: Because nums[0] + nums[1] == 9, we return [0, 1].

kindly provide the link to the problem

https://leetcode.com/problems/two-sum/description/

make sure you read the CONTRIBUTING.md file to understand how to contribute to this project

next time wait for assigned to you :)

I read and followed the instructions

make sure you read the CONTRIBUTING.md file to understand how to contribute to this project

I read and followed the instructions. Please, did I leave anyone out?

next time wait for assigned to you :)

Alright.


localStorage polyfill for Safari private browsing

localStorage polyfill  doesn't work properly for the Safari private browsing case
it only check the existance of localStorage but not the localStorage  accessibility ( setItem/getItem doesn't work unless localStorage object exist)

@PfxMobile We are happy to accept a PR which improves our feature detection inside the polyfill :-)

if(!("undefined"!==typeof window.localStorage&&"undefined"!==typeof window.sessionStorage)){loadJS("./cdn/polyfills/0.1/js/Storage.fixed.min.js");}
?

try {
// Test webstorage existence.
if (!window.localStorage || !window.sessionStorage) throw "exception";
// Test webstorage accessibility - Needed for Safari private browsing.
window.localStorage.setItem('storage_test', 1);
window.localStorage.removeItem('storage_test');
} catch (e) {
This is how it's done in https://github.com/AgentME/webstorage-polyfill

@PfxMobile I tested that on win 10 fedora 24 and abdroid 4.3. Cant speak for IOS if I got it right.

That's really an issue of Safari Private mode - localStorage exist but the setItem/getItem method throws an error

@PfxMobile Can you submit that as a pull-request?

Sure,will  try to provide it this week. Created this just to track an issue in case of someone already interested in the same

This would be awesome, I'm currently handling this manually. Important to note that Safari is weird, and I'm not sure the existing polyfill would suffice. See: https://github.com/AgentME/webstorage-polyfill/blob/master/index.js#L105

PR for this work https://github.com/Financial-Times/polyfill-service/pull/1345

localStorage polyfill doesn't get detected in Safari 10 (private mode). I think we might need to update config.json to include safari 10 ?


3277503: How to read a file line-by-line into a list in Python

Write a detailed tutorial to read a file line by line into a list in Python
Refer following stackoverflow link
https://stackoverflow.com/questions/3277503/how-to-read-a-file-line-by-line-into-a-list
Read the contributing guidelines
https://github.com/arungudelli/python.shiksha/blob/f2e70e57e90988b3db839041a472ea6db3a1b262/CONTRIBUTING.md
Have a look at the sample article.
https://python.shiksha/tips/check-substring-in-string_python/

@arungudelli  can you assign this to me

@arungudelli  I can do this can you assign me this?

@pavankumarraju13 Please Read the contributing guidelines and sample article and start working..

@botketan
Can u work on
https://github.com/arungudelli/python.shiksha/issues/56 ?

@arungudelli

Getting error how to start npm .Could you please help me out?

@pavankumarraju13
Run npm install in the root directory it will install required node_modules then you have to run the application using npm run start.
You should be able to see node_modules folder inside root directory after running npm install

@pavankumarraju13 Let me know if you face any issues

@arungudelli Thank you, sure got it.

@arungudelli  i add md file.
i created pull request it shows atleast one review needed to merge. could you please review the work and what are changes needed can i know?


proposal: Go 2: only give special properties to unsafe.Pointer if package imports unsafe

One of the difficulties of unsafe.Pointer is that if a package gets a value of type unsafe.Pointer then it can convert that pointer to other pointer types, or uintptr.  This is true even if the package does not itself import "unsafe", but gets the unsafe.Pointer value by calling some other package.  This is the reason that reflect.Value.Pointer returns uintptr rather than unsafe.Pointer.
For Go 2 I propose that we change the language to say that values of type unsafe.Pointer only have their special properties in packages that explicitly import "unsafe".  If a package does not import "unsafe", then a value of type unsafe.Pointer may not be converted to other type.
If we make that change, then, Go 1 compatibility rules aside, we can safely permit reflect.Value.Pointer to return unsafe.Pointer.

Presumably this will also let us redefine reflect.StringHeader and reflect.SliceHeader to use unsafe.Pointer instead of uintptr.

I like this one.

Under this proposal, in order to determine whether a conversion expression T(x) may be an unsafe.Pointer conversion, the reader still needs to know three things that may not be locally obvious:

whether the operand is a pointer or uintptr type,
whether T is an alias for unsafe.Pointer, and
whether the current source file has imported package unsafe.

(1) and (2) may be arbitrarily distant in the code (even across package boundaries); (3) is fairly easy to find within the source file, but still requires the reader to jump from the current context to the import block and back.
In contrast, with a function-based unsafe API (such as the one @griesemer and I discussed in #20171), I believe all of that information could be present within the conversion expression itself.
(I do agree that this proposal is a strict improvement over the status quo, but in the space of “fixes for unsafe.Pointer” it seems like the low-cost/low-benefit solution. I wonder whether we could get a much larger benefit for an only marginally higher cost.)

If we make that change, then, Go 1 compatibility rules aside, we can safely permit reflect.Value.Pointer to return unsafe.Pointer.

I don't find this argument compelling. I think we can safely permit reflect.Value.Pointer to return unsafe.Pointer today anyway (again, Go 1 compatibility rules aside).
The Go toolchain no longer supports "safe" mode, so there's no builtin functionality that restricts access to package unsafe. So this argument is implicitly assuming some external safety-validation tool that restricts access to package unsafe.
But then I don't see any reason such an external tool can't just look for unsafe.Pointer->*T conversions in addition to disallowing import "unsafe". That's really no different than what cmd/compile, gccgo, and go/types would all be required to do anyway.
I think a security-oriented subset of Go a la Joe-E or Caja would be fun to work on, but I don't think trying to one-off tackle individual issues is going to get us there.
That said, we already tie other unsafe features like //go:linkname to import "unsafe", so it's not like this is without precedent.
So overall I'd say I'm weakly opposed.

Note that reflect.NewAt allows converting unsafe.Pointer values to any pointer type even without compiler magic: https://play.golang.org/p/w-6sabmpnz9

@mdempsky's comment does seem like a show-stopper: there's not much point in taking away tp := (*T)(u) if you can still write tp := reflect.NewAt(reflect.TypeOf((*T)(nil)), u).Interface().(*T) instead.
So probably this proposal should be declined.
Now that there are no longer any environments penalizing unsafe (in particular, App Engine does not reject unsafe anymore), we could add reflect.Value.UnsafePointer returning unsafe.Pointer.

Retracting.


Reading refs concurrently

Reading 29 refs (using "op read" one by one) now takes 20-25 seconds. It would be great if we could cut this time by reading all refs concurrently (Promise.all?). Reading them this way takes around 2-3 seconds. Is it possible to implement in this action?

Hi @gskierk thank you for your suggestion!  I believe this is a good optimization to add.  The community is currently working to transition from the op CLI to using the SDK directly, which you can follow here: #80 #82
Once that effort is complete, this suggestion could be implemented by tweaking the code in extractSecrets to fetch all references simultaneously.


[Worker] Message getting passed to worker even when worker define to accept other data type params

In following code[1], the worker has defined to accept boolean type param, But It accepts message type variable "msg". No issues observing at deploy or execution level.
[1] Code:
import ballerina.lang.system;
import ballerina.net.http;
@BasePath ("/passthrough")
service passthrough {
@GET
resource passthrough (message msg) {
  worker sampleWorker (boolean a)  {

      system:println("Hello in worker");
      system:println(a);
      xml payload=`<?xml version="1.0" encoding="UTF-8" ?>
  	   <name>chanaka</name>`;
      message mn={};
      http:ClientConnector stockEP = create http:ClientConnector("http://www.mocky.io/v2/");

      message reponse={};
      reponse = http:ClientConnector.post(stockEP, "589c7d22250000350a80560e", mn);
      reply reponse;
    }

    message result2={};

    // boolean mama=true;
    // mama ->  sampleWorker;

    msg -> sampleWorker;
    system:println("I am 1");

    result2 <- sampleWorker;
    system:println("I am 2");
    reply result2;

}
}

This code is not valid anymore. Worker syntax has been changed to not accept any parameters at the time of the definition.


ci-multi-pool: Use ip-masq-agent for masquerading

Now that #26262 has been fixed, we can use disjunct CIDRs for the IP pools. This will make the testing a bit more realistic, as we expect users to define IP pools from different CIDR ranges.
CI run with these changes is green:

:heavy_check_mark:  https://github.com/cilium/cilium/actions/runs/5403357970/jobs/9816045998?pr=26538

The changed workflow is green, no need in running the rest of CI since it's unaffected. Marked ready to merge.


Add support for KVM_GET_DEVICE_ATTR ioctl

Pulled Latest code from rust-vmm/kvm-ioctls.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing in favor of #6


remove lit-html from grid internals

remove lit-html from grid internals
This will give me more control and make it easier to make it faster.
Will do this over several phases

[x] Phase x: (1-2 weeks)
Most of grid, but not menus/filter/grouping
Main part here is to get the body part working well with scrolling

[x] Phase x: (1-2 weeks)
Menus

[x] Phase x: (1-2 weeks)
Everything except menus

[ ] Phase x: (1-2 weeks)
cleanup

also remove @simple-html/core from depencies


Running codegen fails for aws-lambda-go>=v1.13.0

$ cargo run -- --input ../../aws-lambda-go --output ../aws_lambda_events/src/generated --overwrite
thread 'main' panicked at 'not yet implemented', aws_lambda_events_codegen/go_to_rust/src/lib.rs:599:18

With some additional diagnostics:
thread 'main' panicked at 'not yet implemented: interface{}
interface(6173, 6184)', aws_lambda_events_codegen/go_to_rust/src/lib.rs:599:18

As this panic is occurring in parse_go_type_array, the underlying Go code must be []interface{}.


Issue from website page 在Flutter中构建布局

From URL: https://flutterchina.club/tutorials/layout/
the link for main.dart is unvailable (https://raw.githubusercontent.com/flutter/website/master/_includes/code/layout/lakes/main.dart)

@santa0000 thank you for report! I believehttps://github.com/flutter/website/blob/master/examples/layout/lakes/step2/lib/main.dart is supposed to be there.

thanks

@santa0000 Apparently we can't fix the link, please file it to https://github.com/flutterchina/website/issues.


Add sane set_log_level behavior following CASSANDRA-10241

This PR implements the set_log_level behavior proposed in Issue #387.
In short, recent changes to Cassandra 2.2.2 and above add a separate debug.log.  These broke CCM set_log_level. The previous fix simply set both log levels to the same level, which nullified much of the benefit of adding a separate debug.log. This fix adds behaviors that still retain a sensible amount of information in debug.log based on the log level set.
I've tested this with a few dtests and run it through autopep8.

Seems like reasonable behavior to me, +1


FEATURE REQUEST: Comparing assignments

Would be really nice if you could compare between two or multiple groups which assignments are the same or different.

Great Idea for a Feature @royklo.
Working on it next.


Add TempFileStorage

I realized while implementing form-data-parser in a project that LocalFileStorage is a bad fit for apps that process uploads before persisting them elsewhere. I wanted something that wrote to a temporary directory that was removed at the end of the request handler and was only initialized if the form data contained a file. So I wrote TempFileStorage and wanted to contribute it back for others to use 😄
The biggest uncertainty I have about this change is the support for AsyncDisposable in the general node ecosystem.

I have added use as a method to get automatic cleanup without await using and improved the documentation and tests on the class in the hopes it makes the class more generally useful. I can definitely publish this on my own if you prefer, but I believe that it's generic and useful enough to belong in the base package.


ZuulFilterInitializer not compatible with @HystrixCommand annotations

When using the javanica HystrixCommand annotations with a custom ZuulFilter you get a classcast on line 58 of the filter initializer:
registry.put(entry.getKey(), entry.getValue());

The filter that is registered if actually of type com.sun.proxy.Proxy, not com.netflix.zuul.ZuulFilter. This results in not being able to use annotation based hystrix commands.
Sample code available at:
https://github.com/aditzel/zuul-javanica-hystrix-classcasterror

You can use concrete type (subclass proxies) if you just set spring.jmx.proxy-target-class=true. I imagine that would fix it the immediate problem. But Zuul is highly thread bound so I expectr it will blow up in other ways unless you can stick to SEMAPHORE isolation.

I tried using that property but the application still fails to load with a class cast exception.

There isn't really enough information there to diagnose an actual problem, but it sounds like just a classpath issue probably (and unrelated to the original question). Did you check your dependencies? Stick to latest snapshots if you can.

Turns out it's not a classpath issue. Since Javanica uses AspectJ you can get your application to proxy the target classes by adding this to one of your @Configuration classes.
@EnableAspectJAutoProxy(proxyTargetClass=true)


Feature - show or hide - landscape and portrait

I would love to see a show/hide-mobile-landscape - show/hide-mobile-portrait  etc, feature added for media rich content especially htm5 ebooks. Great work guys.
-shawn

I'm looking at the Documentation page on my iPad, and when I rotate between portrait and landscape, the page doesn't rezoom properly. In landscape, everything seems way larger than it should be, and bleeds off the screen... any ideas?

Hey Aaron,
Unfortunately the bug is out of our hands - there's a bug in mobile safari that scales things incorrectly if you don't arbitrarily restrict the user's ability to scale using pinch / zoom. Filament Group documented this a little while back: http://filamentgroup.com/examples/iosScaleBug/
We'll keep an eye on it, hopefully the problem will just get resolved, but so far no luck :(
FTW
Jonathan

Jonathan Smiley
ZURB | Design Lead
<EMAIL_ADDRESS>408.540.8667
Build for Every Device
http://foundation.zurb.com
On Nov 4, 2011, at 9:55 PM, Aaron Collegeman wrote:

I'm looking at the Documentation page on my iPad, and when I rotate between portrait and landscape, the page doesn't rezoom properly. In landscape, everything seems way larger than it should be, and bleeds off the screen... any ideas?

Reply to this email directly or view it on GitHub:
https://github.com/zurb/foundation/issues/61#issuecomment-2638975

Hey Shawn,
I think I neglected to reply to this. Because of the way we're handling those classes right now coupled with how devices report their size this could bea little tricky. I haven't had a chance to dive into the support different devices have for the orientation query, but I'll flag this to check it out. Thanks for the suggestion, I like the idea of it.
FTW
Jonathan

Jonathan Smiley
ZURB | Design Lead
<EMAIL_ADDRESS>408.540.8667
Build for Every Device
http://foundation.zurb.com
On Nov 1, 2011, at 9:16 AM, shawnsandy wrote:

I would love to see a show/hide-mobile-landscape - show/hide-mobile-portrait  etc, feature added for media rich content especially htm5 ebooks. Great work guys.
-shawn
--
Reply to this email directly or view it on GitHub:
https://github.com/zurb/foundation/issues/61


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=605184116
https://github.com/Azure/azure-cli-extensions/commit/20e4dd6318087e2cab3530aca223a38a6da5a9e2

Docs Build status updates of commit a4d462f:
:clock10: Full build: the average full build time is 7 min(s), this is based on the last 245 build(s) for this repository.

Docs Build status updates of commit a4d462f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


FiWare UPC-UA support

Summary
Deploy and configure the FiWare UPC-UA agent.
Intended outcome
The agent service becomes available to devices outside the platform.
How will it work?
The agent gets deployed from our repo through K8s manifests and an Argo CD app. Routing gets extended to allow external clients to push data into the agent. The security policy needs an update too so we can check JWTs for this new service.

Notice the FIWARE stock OPC UA agent only supports connecting to one OPC UA server at a time. So we'll need to tackle security and routing on a case-by-case basis. Hence the general purpose routing and security approach we initially thought to implement is not feasible.


Implement PalHijack for Unix in PAL

Thread hijacking is necessary e.g. for GC stack walking.

Hi @janvorli.
Is there any progress on this, or would it be possible to work around the hijacking of threads? Right now a process on OSX/Unix will crash once the GC starts to suspend the threads, since it eventually calls PalHijack.

@christianscheuer I am sorry for the late response, I had vacation for the last two weeks. I am glad @jkotas has provided a quick workaround for that. I have worked on implementing the hijacking in the past, but then I've realized that there are some other necessary changes that needed to be done first in order to make the hijacking work. Also, the GC was not working at that point, so there was no way to verify the change.
But those prerequisities are now in, so I can finish the hijacking work.

Hi @janvorli. Thank you for getting back to me, and yes the workaround definitely helps a lot. Looking forward to seeing how you will implement this, given the limitations of the Unix platform wrt. thread suspension.


Remove standard-format. fixes #340

With this PR standard has around 250 fewer dependencies when installing.

haha, lgtm :sparkles:

@mafintosh does this break standard --format?

@dcousens Yes, it will. We're going to recommend that folks install standard-format separately from now on. The dependencies for standard-format are just too many and it makes install take way too long, even more-so with npm 3.

@mafintosh This looks good, but I want to print a friendlier message to people who try to run standard --format. Maybe something like:
Code formatting is available in a standalone package: "standard-format". To install it, run "npm install -g standard-format".

ACK :+1:

This has been merged into the v6 branch.


Add GlobalProtect 6.0

Based on information at https://www.paloaltonetworks.com/services/support/end-of-life-announcements/end-of-life-summary.

Had noticed this yesterday, and it was added and removed back.
Looks like it is finally announced. Thanks a lot 👍🏽

Yeah I've been waiting for them to get around to announcing the date for it! Been a bit of a pain with so many people wanting to jump to it (better UI and the likes).

Couldn't find release notes for 5.1, but added them for the rest. Should be helpful to users upgrading. Merging 💯


twig date filter features not working as expected

When using date filter in Timber 1.14, {{ "now"|date }} returns the time in UTC, which appears to be my default set timezone (checked with date_default_timezone_get()), although my PHP default timezone is set to America/Los_Angeles (checked with php --ri date from command line).  It does not utilize the timezone set in my Wordpress settings in the admin backend.
When I use date_default_timezone_set(), that doesn't change (not expecting it to, just stating for reference).  When I specify the timezone (e.g. {{ "now"|date('g:ia', 'America/Los_Angeles') }}), it still returns the time in UTC.
This method as suggested in the Twig docs didn't have any affect:
$twig->getExtension( \Twig\Extension\CoreExtension::class )->setTimezone('America/Los_Angeles');

Closing this as stale and since it's already tackled in 2.x


Add RELEASING.md

Description
Add RELEASING.md
Issues Resolved
Follow up on https://github.com/opensearch-project/opensearch-testcontainers/pull/114#issuecomment-1819835888
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@gaiksaya @peterzhuamazon please, adding RELEASING.md, thank you

@gaiksaya mind please taking one more look? thank you.


Vulnerability roundup 98: go-1.4-bootstrap-20161024: 1 advisory [5.6]

search, files

[ ] CVE-2020-29510 CVSSv3=5.6 (nixos-20.09)

Scanned versions: nixos-20.09: aa5b9cd16b9.
Cc @cstrahan

See also: #106194, #88315, #99778, #73643, #96786, #93989

See also: #106194, #88315, #99778, #73643, #96786, #93989


ci: use platform-specific worker nodes

This is an attempt to fix #581 and #582 by building the launcher bundles on platform-specific worker nodes.

I strongly suspect the issue is from our gradle distribution tasks, not the environment.

You might be right, this does not help (tested at https://github.com/skaldarnar/TerasologyLauncher/actions/runs/299619401).. Closing this.


fix(support-bundle): revert master node taint tolerations

Fix this upstream instead.
https://github.com/longhorn/longhorn/issues/5631
https://github.com/longhorn/longhorn/issues/5614

Need to backport to 1.4.x.

Test result: https://github.com/longhorn/longhorn/pull/5747#issuecomment-1508273603

@Mergifyio backport v1.4.x


Contributor Spotlight - update Mark's avatar

Mark's current avatar shot appears to cut off a bit awkwardly so I have resized the image and adjusted the post metadata to account for the filename change.

Thanks very much @krisstern and @alyssat !


update field typo of kubernetesenv

According to https://istio.io/docs/reference/config/policy-and-telemetry/adapters/kubernetesenv/, the field should be kubeconfigPath instead of kubeconfig_path

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

Needs approval from an approver in each of these files:

install/OWNERS
mixer/OWNERS

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

Hi @harryge00. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

Needs approval from an approver in each of these files:

install/OWNERS
mixer/OWNERS [douglas-reid]

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

@harryge00: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
9b395062225a7cfaf9ce853529b21d8b6536c563
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@harryge00: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
9b395062225a7cfaf9ce853529b21d8b6536c563
link
/test e2e-simpleTests-cni

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9b395062225a7cfaf9ce853529b21d8b6536c563
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest @istio-testing
/retest

/retest

/retest why even fixing typo failed ci?

/test istio-pilot-e2e-envoyv2-v1alpha3

@harryge00: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
9b395062225a7cfaf9ce853529b21d8b6536c563
link
/test e2e-simpleTests-cni

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9b395062225a7cfaf9ce853529b21d8b6536c563
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add contribution docs

Adds CONTRIBUTING.md per discussion in https://github.com/faker-ruby/faker-bot/issues/40

@akabiru I applied your suggested changes. Let me know if you see anything else


[Feature Request] "Iteration" over empty tuple

Hi,
Currently trying to iterate over an empty tuple raises a typing error. Luckily there is a workaround (see below) so this is not entirely a deal breaker. But maybe it would be possible to generate some kind of generic empty iterator (or prune the loop entirely) such that no error is raised? (I hope I am not overlooking some weird consequences that could have)
EDIT: I just noticed that the workaround breaks if the empty tuple is nested inside another tuple (I guess that this is due to how the branch pruning works). This slightly raises the importance of tackling this issue.
Cheers
PS: Somewhere in the back of my mind I feel like I may have adressed this before, but I cannot seem to find an issue, sorry if this is a duplicate :-)
Reproducer
from numba import njit

@njit
def f_guarded(x):
    if len(x)>0:
        for c in x:
            pass

@njit
def f_unguarded(x):
    for c in x:
        pass

@njit
def f_guarded_nested(x):
    if len(x[0])>0:
        for c in x[0]:
            pass

cases = {
    "Guarded iterator with filled tuple": lambda: f_guarded((1,2,3)),
    "Guarded iterator with empty tuple": lambda: f_guarded(tuple()),
    "Unguarded iterator with filled tuple": lambda: f_unguarded((1,2,3)),
    "Unguarded iterator with empty tuple": lambda: f_unguarded(tuple()),
    "Guarded iterator with nested empty tuple": lambda: f_guarded_nested( ((),) )
}

for desc, c in cases.items():
    try:
        c()
        print(desc + ": success")
    except Exception as e:
        print(desc + ": failed")
        print(e)
    print()

Output
Guarded iterator with filled tuple: success

Guarded iterator with empty tuple: success

Unguarded iterator with filled tuple: success

Unguarded iterator with empty tuple: failed
Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of getiter with parameters (Tuple())

During: typing of intrinsic-call at bugs/iter_empty_tuple.py (12)

File "bugs/iter_empty_tuple.py", line 12:
def f_unguarded(x):
    for c in x:
    ^

Guarded iterator with nested empty tuple: failed
Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of getiter with parameters (Tuple())

During: typing of intrinsic-call at bugs/iter_empty_tuple.py (18)

File "bugs/iter_empty_tuple.py", line 18:
def f_guarded_nested(x):
    <source elided>
    if len(x[0])>0:
        for c in x[0]:
        ^

I can't find anything in the issue tracker about iterating over an empty tuple - typing issues to do with the construction of empty lists / dicts have come up before - could that be what you're thinking of?

Turns out it was on Gitter :-P https://gitter.im/numba/numba?at=5f3e7a078b8d4f633e03aea4
My original question was about closures, and I ran into this again while working with closures, I had just simplified it here to not convolute things too much. But that might have been an oversimplification since the closure seems to fail even with guarding. (I just reran Stuart's code from the Gitter thread with 0.54.0rc2)
from numba import njit
import numpy as np

def close(t):
    @njit
    def foo():
        if len(t) == 0:
            print("don't iterate")
        else:
            for x in enumerate(t):
                print(x)
    return foo

close(())()
close((1, 2, 3))()

TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<class 'enumerate'>) found for signature:

 >>> enumerate(Tuple())

There are 2 candidate implementations:
  - Of which 2 did not match due to:
  Overload of function 'enumerate': File: numba/core/typing/builtins.py: Line 1001.
    With argument(s): '(Tuple())':
   No match.

During: resolving callee type: Function(<class 'enumerate'>)
During: typing of call at <ipython-input-1-93b2004ba3c9> (10)

File "<ipython-input-1-93b2004ba3c9>", line 10:
    def foo():
        <source elided>
        else:
            for x in enumerate(t):
            ^

also on my wish list.

This is a WIP starter patch:
from numba import njit, types
from numba.core import ir, postproc
from numba.core.compiler import CompilerBase, DefaultPassBuilder
from numba.core.compiler_machinery import (FunctionPass, register_pass,
                                           PassManager)
from numba.core.untyped_passes import (IRProcessing, GenericRewrites,
                                       DeadBranchPrune,
                                       RewriteSemanticConstants)
from numba.core.analysis import compute_cfg_from_blocks
from numba.core.ir_utils import guard, get_definition, simplify_CFG
from numba.core.typed_passes import PartialTypeInference

@register_pass(mutates_CFG=True, analysis_only=False)
class DeadLoopElimination(FunctionPass):
    _name = "dead_loop_elimination"

    def __init__(self):
        FunctionPass.__init__(self)

    def run_pass(self, state):
        mutated = False

        while True:
            kill = set()
            # run as subpipeline to get type information into the state and do
            # some basic opt
            pm = PassManager("PTI")
            pm.add_pass(GenericRewrites, "Generic Rewrites")
            pm.add_pass(RewriteSemanticConstants, "Semantic const")
            pm.add_pass(DeadBranchPrune, "Dead branch prune")
            pm.add_pass(PartialTypeInference, "performs partial type inference")
            pm.finalize()
            pm.run(state)

            func_ir = state.func_ir
            cfg = compute_cfg_from_blocks(func_ir.blocks)
            loops = cfg.loops()
            dominators = cfg.dominators()

            # search the IR for loops which have an iterator over a ConstSized
            # type which has len of 0
            for lbl, loop in loops.items():
                header_lbl = loop.header
                header = func_ir.blocks[header_lbl]
                iternext = header.body[0].value
                if isinstance(iternext, ir.Expr) and iternext.op == 'iternext':
                    iterable_var = iternext.value
                    iterable_def = guard(get_definition, func_ir,
                                         iterable_var.name)
                    if iterable_def:
                        ty = state.typemap.get(iterable_def.value.name, False)
                        # There is a known type for this iterable, is it
                        # something that creates a dead loop?
                        if isinstance(ty, types.ConstSized) and len(ty) == 0:
                            kill.add((loop, tuple(dominators[header_lbl]),
                                     iterable_def))

            # if nothing was found, escape
            if not kill:
                break

            # for each dead loop, make the loop header body simply an
            # unconditional jump to the exit and scan the dominators for the
            # getiter assignment, swap them for something safe (None) such that
            # type inference is ok.
            for loop, dom, idef in kill:
                # sort out header
                header_lbl = loop.header
                header = func_ir.blocks[header_lbl]
                branch = header.body[-1]
                exit_lbl = branch.falsebr
                header.body.clear()
                header.body.append(ir.Jump(exit_lbl, branch.loc))

                # sort out getiter assignment
                for d in dom:
                    blk = func_ir.blocks[d]
                    for asgn in blk.find_insts(ir.Assign):
                        if asgn.value is idef:
                            asgn.value = ir.Const(None, asgn.value.loc)
                            break
                    else:
                        continue
                    break

            # Clean up CFG/state
            cfg = compute_cfg_from_blocks(state.func_ir.blocks)
            for dead in cfg.dead_nodes():
                del state.func_ir.blocks[dead]
            post_proc = postproc.PostProcessor(state.func_ir)
            post_proc.run()

            state.func_ir.blocks = simplify_CFG(state.func_ir.blocks)

            # reset typemap
            state.typemap.clear()
            mutated = True

        return mutated

class MyCompiler(CompilerBase):

    def define_pipelines(self):
        pm = DefaultPassBuilder.define_nopython_pipeline(self.state)
        pm.add_pass_after(DeadLoopElimination, IRProcessing)
        pm.finalize()
        return [pm]

@njit(pipeline_class=MyCompiler)
def empty_things():
    for c in ():
        if c:
            break
        else:
            pass
    for d in []:
        if d:
            break
        else:
            pass
    for e in (((),)[0]):
        if e:
            break
        else:
            pass

empty_things()


Chore/dep audit

Dep audit
With UI toolkit not being so dependent on some libraries we can now considerably reduce our bundle size
Before

After

Can we get rid of any of the following somehow:

graphql
bignumber.js
bn.js
hash.js
js-sha3
scrypt-js
aes-js
@ethersproject
javascript-time-ago
date-fns

Some of them are crypto modules we shouldn't have, there are two modules with big numbers (do we use any?), there seems to be three or four modules to do time manipulation, and a very large chunk for iconSvgPaths.js?

Looking at the pictures again, maybe you swapped the before and after?


Use AWS ELB Proxy Protocol

Currently, when the CLOUD_PROVIDER is set to aws, a new Service is created for the Ingress of type LoadBalancer by default.
The behavior I desire is for the LoadBalancer Service to use the "service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*" annotation to enable the Proxy Protocol on the AWS ELB, so that the proper headers like X-Real-IP and X-Forwarded-For are set correctly.
Here are my deployments:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: voyager-operator
  namespace: default
  labels:
    run: voyager-operator
spec:
  replicas: 1
  selector:
    matchLabels:
      run: voyager-operator
  template:
    metadata:
      labels:
        run: voyager-operator
    spec:
      containers:
      - name: voyager-operator
        image: appscode/voyager:1.5.4
        args:
        - --cloud-provider=$(CLOUD_PROVIDER)
        - --cluster-name=$(CLUSTER_NAME)
        - --v=3
        ports:
        - containerPort: 1234
          name: zero
          protocol: TCP
        env:
        - name: CLOUD_PROVIDER
          value: aws
        - name: CLUSTER_NAME
          value: mcclusterface

---

kind: Service
metadata:
  name: voyager-operator
  namespace: default
  labels:
    run: voyager-operator
spec:
  ports:
  - name: zero
    port: 1234
    targetPort: zero
  selector:
    run: voyager-operator

Seems like this is simply adding the annotation when CLOUD_PROVIDER = 'aws' into the Service template?
Or allow for custom annotations for the Voyager Service within the Ingress.
      serviceAnnotations:
      - "service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*"
      - "prometheus.io/scrape": "true"
      - "prometheus.io/port": "8090"

@julianvmodesto, I have filed a new issue to track the work for custom annotation #103 .
One question I have, are you using CoreOS' prometheus operator to setup your exporter? We are considering running a side car container with the HAproxy to expose its metrics. I would like to hear how you see this work.

The ful,l suite of annotations available in 1.5.x are:
https://github.com/kubernetes/kubernetes/blob/release-1.5/pkg/cloudprovider/providers/aws/aws.go#L79

As @sadlil mentioned in https://github.com/appscode/voyager/issues/103#issuecomment-302680075, users will be able to provide custom annotations as they see fit with 1.5.5 release.
We are going to cut a release early next week.

@TamalSaha appreciate your help here, love your project and looking forward to 1.5.5.
Re: prometheus, the sidecar for haproxy stats looks like a pretty good solution to me.

@TamalSaha I added the annotation below to a new Ingress, and the annotation was added!
    ingress.appscode.com/annotations.service: '{"service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*"}'

Two issues, though:

updating an existing Ingress with the above annotation doesn't cause an update the service by the controller
actually enabling the AWS Proxy Protocol seems to cause HAProxy 400s. I tested by removing and re-adding the service.beta.kubernetes.io/aws-load-balancer-proxy-protocol annotation from the Voyager service

We are going to look into that and get back to you.

Ack, sorry, regarding the second issue I have w/ 400s, I think I just need to figure out how to configure HAProxy to accept the Proxy Protocol.

How would I be able to attach accept-proxy to the bind below?
frontend http-frontend
    bind *:80 accept-proxy

You can't add options to the bind https://github.com/appscode/voyager/blob/master/pkg/controller/ingress/template/template.go#L140..
We are going to push a new updated this fixed this week. @sadlil , I found some more docs here: https://jve.linuxwall.info/ressources/taf/haproxy-aws/

Great, thanks in advance Tamal!

Created https://github.com/appscode/voyager/issues/115.

@julianvmodesto , just to clarify one thing, with 1.5.6, you only need to add
ingress.appscode.com/keep-source-ip: true annotation to ingress. Voyager operator will automatically add "service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*" annotation to service and enable PROXY protocol in HAPRoxy for "aws" provider.


Update the game over message

Update the game over message so people know how to play again

I discovered that there are issues surrounding branches and how merging to an existing branch can help elevate any problems with progress.
self defining is key to understanding how i can improve my progress and knowledge base


Upgrade to dataflow 1.0.2

After 1.2.0.RELEASE

Closed via 194425f483e0020dcfb8aa3abbb01b7997886c23


Add push constraints

This constrains PUSH internal reads to be bytes, by delegating the check to BytePackingStark
closes #1150
closes #1325 as this won't be an issue anymore after this.

Good point, just added it!

@hratoanina Good point, just added it!


Yet not working

Internal Error: Unable to load this plugin class \Kanboard\Plugin\Template\Plugin

On which version, 1.0.32?

(And during (new) install or upgrade)

@CoMPaTech new install, 1.0.32 yes!

Ack, looking into it

@CoMPaTech it was my mistake. I did install it wrongly! Everything is fine now, thank you!

Ok then, enjoy!


Use Preferred username over email as 'user' property

Fixes #22271

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.002%) to 41.951%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/azurecore/src/account-provider/auths/azureAuth.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
28807

Relevant Lines:
63751

💛  - Coveralls


Clarify OpenSSL update on changelog

What does this PR do?
Clarifies that OpenSSL only got updated on Linux and macOS (not on Windows).
Motivation
The release notes are misleading for Windows users, as the version of OpenSSL is updated differently.
Additional Notes
Once merged I will be follow this up by updating the release notes on GitHub to match.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Tracing improvements

Update code to ensure that the "tracing" is only enabled for the server process (not the worker process!)

I do not understand the value of this change; having spans of all server actions seems valueable. Can you be more specific what the benefit is here?

The tracing only monitors external API function calls, right? Or do internal processes (e.g. the background worker) get traced too?
Aside from this question, I think it makes sense to disable tracing for other "temporary" processes like importing data or running migrations, yes?

@SchrodingersGat every general process get's traced - so background workers should show up too. That might depend on the data backend though.

(Even if we close that pr, I think we should keep the added invoke task (already would needed that a while ago) and the two guard functions.)

@SchrodingersGat every general process get's traced - so background workers should show up too. That might depend on the data backend though. If tracing is enabled I would trace everything possible to be able to find performance bottlenecks. The overhead is not too high on performant machines (esp with fast network).

Ok, fair enough. What are your thoughts on disabling tracing for operations such as "import" or "migration"? My justification is to simplify the running code in these parts, as this is where we get a lot of problems.


[BUG]

Details
Spigot Version:  Tuinity version git-Tuinity-"df76b3c" (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
please run /ep debug and attach a screenshot

Describe the bug
A player ran the /ep settings command and when it did not show up for a while, they ran it again and suddenly lost the ability to interact with anything along with these errors popping up.
[12:20:12 WARN]: [EasyPrefix] An error occurred while using EasyPrefix. If you think this is an error, please report following exception to GitHub!
[12:20:12 WARN]: [EasyPrefix] ------ ERROR ------
[12:20:12 WARN]: net.minecraft.server.v1_16_R3.CancelledPacketHandleException
[12:20:12 WARN]: [EasyPrefix] ------ END OF ERROR ------
[12:20:12 WARN]: [EasyPrefix] An error occurred while using EasyPrefix. If you think this is an error, please report following exception to GitHub!
[12:20:12 WARN]: [EasyPrefix] ------ ERROR ------
[12:20:12 WARN]: net.minecraft.server.v1_16_R3.CancelledPacketHandleException
[12:20:12 WARN]: [EasyPrefix] ------ END OF ERROR ------
[12:20:12 WARN]: [EasyPrefix] An error occurred while using EasyPrefix. If you think this is an error, please report following exception to GitHub!
[12:20:12 WARN]: [EasyPrefix] ------ ERROR ------
[12:20:12 WARN]: net.minecraft.server.v1_16_R3.CancelledPacketHandleException
[12:20:12 WARN]: [EasyPrefix] ------ END OF ERROR ------
[12:20:12 ERROR]: Could not pass event InventoryClickEvent to EasyPrefix v1.7.7
java.lang.NullPointerException: null
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Player's POV

Bug doesnt seem to fix until restart but it happens on a regular basis to a few random players

This issue should be fixed.
Please make sure that you've installed Java 16.


Add union type parameters

Description of change
This adds the UMethodQuery and UDID (naming convention open to change) Typescript union types. This pattern allows us to create analogues for generic types in function parameters, such as MethodQuery which takes either an IotaDIDUrl or String. This is to enhance the developer-friendliness of our Wasm API by removing unnecessary toString invocations and allowing pseudo-generic, polymorphic function parameters.
export type UMethodQuery = DIDUrl | string;
export type UDID = DID | string;

With this change, all of the following work:
doc.signSelf("did:iota:example#sign-0");                // CURRENT
doc.signSelf(doc.defaultSigningMethod().id.toString()); // CURRENT
doc.signSelf(doc.defaultSigningMethod().id);            // NEW

doc.resolveMethod("did:iota:example#sign-0");                // CURRENT
doc.resolveMethod(doc.defaultSigningMethod().id.toString()); // CURRENT
doc.resolveMethod(doc.defaultSigningMethod().id);            // NEW

let resolved = await client.resolve("did:iota:example"); // CURRENT
let resolved = await client.resolve(doc.id.toString());  // CURRENT
let resolved = await client.resolve(doc.id);             // NEW

let history = await client.resolveHistory("did:iota:example"); // CURRENT
let history = await client.resolveHistory(doc.id.toString());  // CURRENT
let history = await client.resolveHistory(doc.id);             // NEW

The alternative for Client::resolve and Client::resolveHistory would be to enforce taking in a WasmDID only, but error handling is more unwieldy than in Rust and users may extract DIDs as strings from JSON objects like credentials. The proposed pattern would still be useful for UMethodQuery which matches the behaviour in Rust. Note this is only possible when all types in the union serialise to the same representation, since we use serde to handle the conversion. Different union types are possible but would require an intermediary untagged enum to handle deserialisation with this method.
Added

UDID union type to take either DID or a string as a parameter.
UMethodQuery union type to take either DIDUrl or a string as a parameter.
WasmNetwork::name getter.

Changed

Document::resolveMethod parameter changed from string to UMethodQuery.
Document::revokeMerkleKey parameter changed from string to UMethodQuery.
Document::signSelf parameter changed from string to UMethodQuery.
Document::diff parameter changed from string to UMethodQuery.
Client::resolve parameter changed from string to UDID.
Client::resolveHistory parameter changed from string to UDID.
WasmDID::network is no longer a getter, just a regular function.
WasmDID JSON representation changed to match IotaDID.
WasmDIDUrl JSON representation changed to match IotaDID.

Type of change

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

How the change has been tested
Wasm tests and examples pass locally.
Change checklist

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

The only problem I see with this change is that the type in the method signature became harder to understand.
for example:
signSelf(key_pair: KeyPair, method_query: UMethodQuery): void

Developers must go to the method declaration to see what UMethodQuery actually includes, and that's a string can be passed as an argument.
In a perfect world, the method should look like:
signSelf(key_pair: KeyPair, method_query: DIDUrl | string): void

I'm not sure removing toString() is worth the complexity the new method signature has. But also having polymorphic arguments is an improvement.

The only problem I see with this change is that the type in the method signature became harder to understand <...>
signSelf(key_pair: KeyPair, method_query: DIDUrl | string): void

Turns out wasm-bindgen does actually support generating such a function signature via typescript_type! https://github.com/rustwasm/wasm-bindgen/issues/2155
I forgot about the above since I was just looking at their guide: https://rustwasm.github.io/docs/wasm-bindgen/reference/attributes/on-rust-exports/typescript_type.html
/// Duck-typed union to pass either a string or WasmDID as a parameter.
#[wasm_bindgen]
extern "C" {
  #[wasm_bindgen(typescript_type = "DID | string")]
  pub type UWasmDID;
}

/// Duck-typed union to pass either a string or WasmDIDUrl as a parameter.
#[wasm_bindgen]
extern "C" {
  #[wasm_bindgen(typescript_type = "DIDUrl | string")]
  pub type UWasmMethodQuery;
}

With the revised code the Typescript function signature is as-expected:
* @param {KeyPair} key_pair
* @param {DIDUrl | string} method_query
*/
  signSelf(key_pair: KeyPair, method_query: DIDUrl | string): void;

Thanks for the catch!


test_get_exif_tags and test_exif_gps fail with sigal 2.1 and pillow >= 7

When rebuilding sigal for tests against python-pillow >= 7.0.0 I'm running into the following issues:
=================================== FAILURES ===================================
______________________________ test_get_exif_tags ______________________________

    def test_get_exif_tags():
        test_image = '11.jpg'
        src_file = os.path.join(CURRENT_DIR, 'sample', 'pictures', 'dir1', 'test1',
                                test_image)
        data = get_exif_data(src_file)
        simple = get_exif_tags(data, datetime_format='%d/%m/%Y')
>       assert simple['fstop'] == 3.9
E       KeyError: 'fstop'

tests/test_image.py:148: KeyError
----------------------------- Captured stderr call -----------------------------
Unknown format for ExposureTime: 0.00100603
------------------------------ Captured log call -------------------------------
INFO     sigal.image:image.py:350 Unknown format for ExposureTime: 0.00100603
________________________________ test_exif_gps _________________________________

tmpdir = local('/tmp/pytest-of-builduser/pytest-0/test_exif_gps0')

    def test_exif_gps(tmpdir):
        """Test reading out correct geo tags"""

        test_image = 'flickr_jerquiaga_2394751088_cc-by-nc.jpg'
        src_file = os.path.join(CURRENT_DIR, 'sample', 'pictures', 'dir1', 'test1',
                                test_image)
        dst_file = str(tmpdir.join(test_image))

        settings = create_settings(img_size=(400, 300), copy_exif_data=True)
        generate_image(src_file, dst_file, settings)
        simple = get_exif_tags(get_exif_data(dst_file))
>       assert 'gps' in simple
E       AssertionError: assert 'gps' in {'Make': 'HTC-8900', 'Model': 'HTC-8900', 'dateobj': datetime.datetime(2008, 4, 6, 14, 55, 2), 'datetime': 'Sun 06 Apr 2008 02:55:02 PM '}

tests/test_image.py:255: AssertionError
----------------------------- Captured stderr call -----------------------------
The 'autorotate_images' and 'copy_exif_data' settings are not compatible because Sigal can't save the modified Orientation tag.
Failed to read GPS info
------------------------------ Captured log call -------------------------------
WARNING  sigal.image:image.py:98 The 'autorotate_images' and 'copy_exif_data' settings are not compatible because Sigal can't save the modified Orientation tag.
INFO     sigal.image:image.py:377 Failed to read GPS info
=========================== short test summary info ============================
FAILED tests/test_image.py::test_get_exif_tags - KeyError: 'fstop'
FAILED tests/test_image.py::test_exif_gps - AssertionError: assert 'gps' in {...
================= 2 failed, 69 passed, 2 deselected in 23.76s ==================

Full build log:
sigal-2.1-build.log
I tried reverting to a pillow < 7.0.0 (we provide python-pillow6 for this), but python-pilkit can not import from it...).
I'm not entirely sure whether these issues are really caused by pillow >= 7.0.0 but it would at any rate be great to support it in the upcoming release to be on the safe side.

Yes, it seems that Pillow 7.2 changed the way EXIF metadata are returned, the cron build started to fail a few days ago (https://travis-ci.org/github/saimn/sigal/builds/704972432). I'll have a look during the weekend.