I want to add space on Bottom, Offset is not working

I am using this code to set padding from bottom
bannerView?.showBanner();
bannerView?.setBannerPositionWithOffset(AdPosition.BottomCenter, 0, 50);

Hello, thank you for notification of your issue. We are working on changing the logic of banners and you can use them as widgets in the next update

Sure, Eagerly awaiting for the update.

@Jedures  Any updates regrading this?

Hello, thank you for notification of your issue. We are working on changing the logic of banners and you can use them as widgets in the next update

@Jedures Still not able to use them as widget.


Update configure-artifact-repository.md

change configuration of minion section
Checklist:

[ ] My organization is added to USERS.md.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi,
The problem is when you copy the lines or when you used the link.
in other hand, if you need remark same code is recommended to identify the
type of code. Y mark de code like this:

 brew install helm # mac, helm 3.x
 helm repo add stable
https://kubernetes-charts.storage.googleapis.com/ # official Helm
stable charts
 helm repo update
 helm install argo-artifacts stable/minio --set
service.type=LoadBalancer --set fullnameOverride=argo-artifacts

Ignacio García Ruiz
<EMAIL_ADDRESS>El jue., 5 nov. 2020 a las 14:27, Simon Behar<EMAIL_ADDRESS>escribió:

@simster7 commented on this pull request.
In docs/configure-artifact-repository.md
https://github.com/argoproj/argo/pull/4462#discussion_r518048567:

@@ -18,11 +18,11 @@ Subsequent sections will show how to use it.

Configuring Minio
- -$ brew install helm # mac, helm 3.x -$ helm repo add stable https://kubernetes-charts.storage.googleapis.com/ # official Helm stable charts -$ helm repo update -$ helm install argo-artifacts stable/minio --set service.type=LoadBalancer --set fullnameOverride=argo-artifacts +bash
+brew install helm # mac, helm 3.x
Hmm, we use the $ ... convention across our docs (even in other places in
this same file). In my opinion, what we currently have is easier to parse
and understand.
Do you have a good reason to remove the $ ... convention?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/argoproj/argo/pull/4462#pullrequestreview-524256495,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4WD4JOJTD6UAJME5GVZBLSOKR3JANCNFSM4TLEGHDA
.

Closing. Another PR addressed this.


Async support

Hi,
Is there any async support in this library? I was going to use this with NancyFx async routes, so i was wondering if any async api available?
Thanks

Not yet...its WIP so hopefully soon...


suggestion:  partial render

The following method can realize the partial render mode,  which can improve the render efficiency.
displayObj.render(...)  {
...
if (this.children.length) {
for (var i = 0; i < this.children.length; i++) {
this.children[i].render();
}
else {
....render code
}
...
}
displayObj.clear(...) {
...
if (this.children.length) {
for (var i = 0; i < this.children.length; i++) {
this.children[i].clear();
}
else {
....clear code
}
...
}
thus, we needn't render the total frame but the partial area.

Which complicates things a lot, and it will actually have bad performance in WebGL.
If you want to cache some elements, use RenderTexture or cacheAsBitmap.

I wont explain all point of how wrong is that, but imagine just one: if an element changed place, there's no way to know where was it before, and thus clear() is impossible.

The performance partly depend on the method of the calling.  One can use parent.render, also can use child.render(). I do think that the performance of them is different.
Yes, there are some problem in WebGL. I just give a direction that rendering the changed area instead of the all, no matter WebGL and Canvas. The smaller data-size, the better performance.
It is easy to store the previous position for the movement of the element.

The smaller data-size, the better performance.

Can't be applied to webgl stuff, calculating the overlapping change will take more time.

It is easy to store the previous position for the movement of the element.

previous movement, previous size, all previous filters, whole previous state.

If did implement partial rendering, we would likely use some kind of "dirty rectangle" implementation, similar to browsers.
The reason we didn't do this is two fold:

It is pretty complex to build a dirty-rect rendering system, and it puts a lot of work on CPU. This is a problem because JS is already slow, our bottleneck is almost always CPU; not GPU.

Many of the applications built with JS wouldn't benefit from this optimizations. Most games don't do this because too much changes almost every frame.

Certainly won't be doing this anytime soon. But you can do a simple version yourself with cacheAsBitmap and RenderTextures.


[information_schema] when i run sql to select from information_schema use join, be exit

Steps to reproduce the behavior (Required)
1.run SHOW PROC '/backends'\G
be allive
2.run this sql
select * from information_schema.tables a left join information_schema.columns b on a.TABLE_NAME=b.TABLE_NAME;
3.run SHOW PROC '/backends'\G
be exit
Expected behavior (Required)
return correct results
Real behavior (Required)

be exit

StarRocks version (Required)
Compiled main code
MySQL [(none)]> select current_version();
+-------------------+
| current_version() |
+-------------------+
| UNKNOWN           |
+-------------------+

@leoyy0316 Please include the StarRocks version you are using in the bug report, thanks!

@kateshaowanjou tested main branch code

Can you still reproduce the problem now? I have not reproduced this problem locally? If you can reproduce it, can you provide the stack of be unstacked?

maybe some pr fix it, i can not reproduce it on now main branch, so i will close this issue, thanks

Okay, thanks, sorry we are a little late to see this question, if you have other questions later, welcome to raise issue again


Support custom log attributes via extra logger parameter

Hi!
I am using the aws-lambda-powertools-python logger for a number of projects but also have existing deployments using structured JSON logging implemented with a custom logger. Our custom logger supports the Python logging extra parameter to supply custom attributes. It would be great if the aws-lambda-powertools-python formatter supported custom attributes so we can take advantage of structured logging for additional attributes.
Example
from aws_lambda_powertools.logging import Logger
logger = Logger()
logger.info('Put aggregation result', extra={'key': 'results/sum.csv', 'size': 130425})

Current output:
{
  "level": "INFO",
  "location": "<module>:5",
  "message": "Put aggregation result",
  "timestamp": "2020-12-23 11:00:47,695",
  "service": "service_undefined",
  "sampling_rate": 0
}

Desired output:
{
  "level": "INFO",
  "location": "<module>:5",
  "message": "Put aggregation result",
  "timestamp": "2020-12-23 11:00:47,695",
  "service": "service_undefined",
  "sampling_rate": 0,
  "key": "results/sum.csv",
  "size": 130425
}

This enables us to do effective log queries, filtering and stats using CloudWatch Logs Insights.
For reference:

python-json-logger support custom attributes using extra - https://github.com/madzak/python-json-logger
Usage of the extra keyword argument to add custom attributes to the LogRecord is covered here: https://docs.python.org/3/library/logging.html

Is this something that you would consider supporting?

Hey @eoinsha - Great to hear from you, and thanks for opening this feature request.
We're in PTO so I'll revisit in January - for now, I have one quick question for you:
Logger allows an arbitrary object instead of string today:
logger.info({
'key': 'results/sum.csv',
'size': 130425
})
This will be encapsulated within the message key instead of being top-level keys:
{
...
"message": {
'key': 'results/sum.csv',
'size': 130425}
}
Does this help or you prefer having a string to message plus extra keys as top level keys?
If that helps, we should update the docs to make this more explicit. If not, I also think is fine having an extra key for this purpose for cases where you want to preserve the message

Thanks @heitorlessa! I do have a preference for the extra method as it's consistent with the references, what we do already, makes it easier to switch over. But what you show here achieves the same thing, so it looks like so I can use that on other projects. Thanks again and have a great break! :)

+1 for this feature. Would make it easier to convice people at my org to use it :)

it's be great if there would be no need for extra= but just send a kwargs

Hey @eoinsha - PR created! Could you double check if that helps you moving forward? #257
@risenberg-cyberark we wouldn't be able to do it without extra as it'd break the logging protocol and make it slightly difficult for those moving in or outside Logger.
cc Other folks who opened issues in the past, as this feature might help them out too @papi-tokei @ivamluz @patrickwerz @alvaropc

Hey @eoinsha - PR created! Could you double check if that helps you moving forward? #257
@risenberg-cyberark we wouldn't be able to do it without extra as it'd break the logging protocol and make it slightly difficult for those moving in or outside Logger.
cc Other folks who opened issues in the past, as this feature might help them out too @papi-tokei @ivamluz @patrickwerz @alvaropc

This looks perfect, thanks @heitorlessa !

This looks perfect, thanks @heitorlessa !

Thanks, @heitorlessa ! That covers that scenario I raised in the other PR I opened the other day.

Thanks, @heitorlessa ! That covers that scenario I raised in the other PR I opened the other day.

Merging it now, and it should be released by Friday along with other minor improvements ;)
will circle back when 1.10.0 is available on PyPi this week

Merging it now, and it should be released by Friday along with other minor improvements ;)
will circle back when 1.10.0 is available on PyPi this week

@heitorlessa looking forward to the release. Thanks for your effort.

@heitorlessa looking forward to the release. Thanks for your effort.

This is perfect!
Thank you so much!
Álvaro Ponce Cabrera.
El mar, 12 ene 2021 a las 14:31, Heitor Lessa<EMAIL_ADDRESS>escribió:

Hey @eoinsha https://github.com/eoinsha - PR created! Could you double
check if that helps you moving forward? #257
https://github.com/awslabs/aws-lambda-powertools-python/pull/257
@risenberg-cyberark https://github.com/risenberg-cyberark we wouldn't
be able to do it without extra as it'd break the logging protocol
https://github.com/python/cpython/blob/11d13e83abedabba12b28773317f1a365113e7af/Lib/logging/__init__.py#L1585
and make it slightly difficult for those moving in or outside Logger.
cc Other folks who opened issues in the past, as this feature might help
them out too @papi-tokei https://github.com/papi-tokei @ivamluz
https://github.com/ivamluz @patrickwerz https://github.com/patrickwerz
@alvaropc https://github.com/alvaropc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/issues/253#issuecomment-758656236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGANP567JD6ZUDJXDQHHXCDSZRFLVANCNFSM4VG3IFBQ
.

This is perfect!
Thank you so much!
Álvaro Ponce Cabrera.
El mar, 12 ene 2021 a las 14:31, Heitor Lessa<EMAIL_ADDRESS>escribió:

Hey @eoinsha https://github.com/eoinsha - PR created! Could you double
check if that helps you moving forward? #257
https://github.com/awslabs/aws-lambda-powertools-python/pull/257
@risenberg-cyberark https://github.com/risenberg-cyberark we wouldn't
be able to do it without extra as it'd break the logging protocol
https://github.com/python/cpython/blob/11d13e83abedabba12b28773317f1a365113e7af/Lib/logging/__init__.py#L1585
and make it slightly difficult for those moving in or outside Logger.
cc Other folks who opened issues in the past, as this feature might help
them out too @papi-tokei https://github.com/papi-tokei @ivamluz
https://github.com/ivamluz @patrickwerz https://github.com/patrickwerz
@alvaropc https://github.com/alvaropc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/issues/253#issuecomment-758656236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGANP567JD6ZUDJXDQHHXCDSZRFLVANCNFSM4VG3IFBQ
.

hey everyone - This is now available on 1.10 on PyPi and on SAR :)
Closing this now, and thank you for @eoinsha for raising it!

hey everyone - This is now available on 1.10 on PyPi and on SAR :)
Closing this now, and thank you for @eoinsha for raising it!


Add dynamic naming to Action

See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#name.

Done. See 38199c2.


Incorrect YAML editor help for Push Extension

When editing YAML with the Azure App Configuration Push Extension task the editor gives incorrect assistance / tooltips for the following properties:

ConfigurationFile
Strict

For both it gives the error message:

Value is not accepted. Valid values: "EditableOptions".

Actually "Strict" requires a boolean value and "ConfigurationFile" requires a file path.
(If I understand correctly this task is not open sourced, so I cannot contribute more details to this)

Thanks for reporting this! It looks like there is a fix to be made on our side that we have identified and are working on.

Thanks for reporting this! It looks like there is a fix to be made on our side that we have identified and are working on.

@zhenlan It's still broken in AzureKeyVault@2

@AppFzx are you using Azure App Configuration Push pipeline task? Looks like you are using a Key Vault pipeline task.

Any update on this? We have faced the same issue with AzureKeyVault

@shkumesh this issue, and repo, refers to the Azure App Configuration task, not Key Vault. We have resolved the issue for Azure App Configuration. Did you mean there was an issue with an Azure App Configuration task?

The issue is with AzureKeyVault.

@shkumesh apologies for the confusion. Since this issue is for Azure App Configuration it may not be the best place to resolve an issue you're facing with Azure Key Vault. In that case, the issue should be filed here: https://github.com/microsoft/azure-pipelines-tasks/issues


GDScript error when using get_tree().root.foo = bar (setter called on property with read-only property)

Godot version:
Tested on nightly build and 3.1.1
OS/device including version:
GNU/Linux x64
Issue description:
The engine seems to only throw an error when using get_tree().root.foo = bar, I tried with another object and the script ran fine.

Steps to reproduce:
use get_tree().root.foo = bar in a script
Minimal reproduction project:
GDScriptBug.zip

Possibly because you are trying to access a parent node in _ready within the games main scene. The scenetrees root viewport may not have readied by then.

Possibly because you are trying to access a parent node in _ready within the games main scene. The scenetrees root viewport may not have readied by then.

Probably not since storing the in a variable and using it works as shown in the code and doing the same in _process also causes an error.

Calling get_root() method directly works:
get_tree().get_root().render_target_v_flip = true

When attempted with property, strangely the following hack works: :eyes:
((get_tree().root) as Viewport).render_target_v_flip = true

(this casts the root to viewport before accessing)
The following prints true, though:
print(get_tree().root is Viewport) # true

I think I commented this on another issue.
If you set the last value "property chain" like this
a.b.c.d = new_val_d

Godot will update each property in reverse. Once the d value is set for c the updated value for c will be set for b and then b for a. Like the code gets transformed to this:
var b = a.b
var c = b.c
c.d = new_val_d
b.c = c
a.b = b

So in your code Godot sets a property for root and tries to call get_tree().root = root but the latter is an invalid operation (only read access).
It's been a while though and I don't remember exactly where this behavior applies in GDScript. I think this covers the C++ code that is just exposed.
Calling a get-method will break the chain and is a valid workaround.

This is still reproducible in the current master branch.


⚠ coolviruses.download Firefish has degraded performance

In 396f776, coolviruses.download Firefish (https://coolviruses.download/) experienced degraded performance:

HTTP code: 200
Response time: 6123 ms

Resolved: coolviruses.download Firefish performance has improved in f3d6e1e after 9 minutes.


spec: require matching python3-osbuild version

The osbuild executable requires that the exact same version of the corresponding python library is installed, but this was not enforced in the RPM package. Thus a old version of osbuild could be installed alongside an older version of python3-osbuild, which results in an osbuild crash (see below).
Therefore, enforce that both installed packages have matching versions by specifying the exact version for the python3-osbuild dependency of the osbuild package.
With that patch applied updating osbuild alone wont be possible anymore:
sudo dnf install /home/gicmo/Code/src/osbuild/rpmbuild/RPMS/noarch/osbuild-11-1.20200406gitb08d583.fc32.noarch.rpm

 Problem: conflicting requests
  - nothing provides python3-osbuild = 11-1.20200406gitb08d583.fc32 needed by osbuild-11-1.20200406gitb08d583.fc32.noarch

Example osbuild crash if versions are not matching:
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 791, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (osbuild 10 (/usr/lib/python3.8/site-packages), Requirement.parse('osbuild==11'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/osbuild", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3252, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 585, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 598, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'osbuild==11' distribution was not found and is required by the application

@jrusz this should fix the issue you were seeing.

Hm, jenkins/run_tests.sh: No such file or directory that doesn't look right?

Requires: foobar%{?_isa} = %{epoch}:%{version}-%{release}
We are architecture independent, so the ISA can be dropped. We don't use any epoch, yet, so that can be dropped as well. So yeah, I think this is fine.

That was exactly my start point and my thinking ;)


fix: skip generate if no posts

replicated from https://github.com/hexojs/hexo-generator-feed/pull/107
different from hexo-generator-feed, this only skip when there no posts and pages.

Coverage remained the same at 100.0% when pulling e26d4a152fb41b0bdce24abb31141d7b9b4fdf15 on curbengh:empty-post into 6a5559da33a6993e478bdad83dd138415106e077 on hexojs:master.


PreprocessReader: Make variable references look more like Powershell

PreprocessReader currently allows variable references like:
$<NAME> - references a local variable
$<<NAME>> - references an environment variable
$<<<NAME...>>> - references a secret
We also support alternate forms like ${NAME}, ${{NAME}}, and ${{{NAME}}} when enabled.
I added the last two reference formats over time and frankly, I haven't been super happy with this (seems clunky).
Now that we're going to include this functionality into neon-cli (#1624) for preprocessing manifests, now's probably the time to clean this up.
The idea here is to change the format to be more readable by following the Powershell lead:
$<NAME> - references a local variable
$<env:NAME> - references an environment variable
$<secret:NAME...> references a secret
and we'd also support: ${NAME}, ${env:NAME}, and ${secret:NAME...}
We're using regex patterns to match these so it shouldn't be too difficult to make this change.
We could try to make this change optional for backwards compatibility, but I don't believe that's worth the effort.  I believe this change will impact Loopie and us only and it would be nicer to keep this clean going forward.
NOTE:
The PreprocessReader class also supports variable references like ${...} and $(...).  These have also been modified to use the new format.

DONE


Fix broken LICENSE link in license.md

The https://peak.1902.studio/other/license.html page incorrectly linked to the LICENSE.md instead of the LICENSE file.

Thanks, seems I need to update that page as well, because it's outdated.


Add an action to check that each PR has a referenced issue.

Summary of the Pull Request
What is this about?
Adds an action that will check PR's to see if there is a referenced issue.
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #2427 (b9ebdb1) into main (a6addbf) will increase coverage by 5.45%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2427      +/-   ##
==========================================
+ Coverage   29.85%   35.31%   +5.45%
==========================================
  Files         289      135     -154
  Lines       35084    16959   -18125
==========================================
- Hits        10476     5989    -4487
+ Misses      24608    10970   -13638

Impacted Files
Coverage Δ

src/agent/coverage/src/test.rs
92.85% <0.00%> (-7.15%)
:arrow_down:

src/agent/coverage/src/code.rs
8.29% <0.00%> (-6.12%)
:arrow_down:

src/agent/onefuzz/src/machine_id.rs
51.21% <0.00%> (-5.63%)
:arrow_down:

src/agent/onefuzz/src/sanitizer.rs
69.69% <0.00%> (-2.91%)
:arrow_down:

src/agent/onefuzz-agent/src/worker/tests.rs
99.10% <0.00%> (-0.11%)
:arrow_down:

src/agent/onefuzz/src/asan.rs
0.00% <0.00%> (ø)

src/agent/coverage/src/cache.rs
0.00% <0.00%> (ø)

src/agent/onefuzz-agent/src/setup.rs
0.00% <0.00%> (ø)

src/agent/onefuzz-agent/src/reboot.rs
0.00% <0.00%> (ø)

src/agent/onefuzz/src/input_tester.rs
0.00% <0.00%> (ø)

... and 165 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Release strategy

My motivation to help working on the addon is to get rid of the annoying deprecations pointed out in #715
In the update process:

#711
#712
#714
#715

I figured out that it's not that simple to get it to work with ember >=4 because the addon and probably the dependencies use the old ember imports and private apis that don't work anymore in ember 4.
That raises the question how we should release new versions to have a happy update path. The latest released version is 4.0.0-beta.12 which was released over a year ago. NPM Versions show that most downloads are for the beta releases.
My suggestion would be to release a version 4.0 that supports ember <=3.28.x and after that work on a new 5.0 release for ember >=4. That would allow us to drop support for ember <=3.28.x in the 5.x branch and make things much easier.
We need to highlight breaking changes from the ember-validators dependency.
I'm happy for more input and opinions.

[x] Deprecate volatile option because computed().volatile() is removed:

[x] https://github.com/emberjs/ember.js/pull/19670
[x] https://github.com/adopted-ember-addons/ember-cp-validations/pull/718

[x] Release 4.0.0-beta.13
[x] Fix ember 4.0 issues https://github.com/adopted-ember-addons/ember-cp-validations/pull/717
[x] #720
[x] Release 4.0 for ember <=3.28.x
[x] Release 5.0 for ember >=4
[ ] Replace ember-font-awesome
[ ] Replace ember-data imports
[ ] Enable embroider-safe and embroider-optimized scenarios
[ ] https://github.com/adopted-ember-addons/ember-cp-validations/issues/722

This is a crucial dependency of a project I am attempting to update to Ember 4.0.
I will gladly help if told what is necessary. Is there a todo list?

@andsmedeiros not yet. I'll think about it and update the issue.

Sounds like a fine approach. A new release (even another beta) would be appreciated

Bump to humbly request a beta.13 😅

Once again requesting a beta release 😅  Who has release creds? @offirgolan

@fsmanuel FYI: https://github.com/qonto/ember-cp-validations/pulls?q=is%3Apr+is%3Aclosed

Hey @zeppelin long time no see! I'll have a look at your PRs and anlredy think it'll help a lot.

@fsmanuel thank you for your work. I almost decided to move from ember-cp-validations into other library. You saved us lot of time! Looking forward for 4.x and 5.x versions. We need both of them!

I had made up my mind to move away from ember-cp-validations too because it did not work with Ember 4. Looking forward to the 4.x and 5.x, thanks @fsmanuel !

beta.13 is released. We'll need to replace the deprecated ember-cli-release process, esp since it doesn't work with OTP and the changelog generation seems broken (or maybe the commits aren't properly formatted). Should follow the guidelines in the adopted org.

@knownasilya Thanks a lot.
To all: Would be great to get some help with the release and guidelines as I'm not familiar setting up all that tools.

@gilest @andsmedeiros @enterpub @JenLyndle can you test the 4.0.0-beta.13 release and report bugs or problems if you find any?

@fsmanuel I will be able to test next week. We have a huge app with all kinds of validation, so I'll test it heavily. Thank you so much!

@fsmanuel sure will do! thanks!

@fsmanuel thanks a lot! I'll test it against my application and let you know of what comes out of it.

@knownasilya Seems like there are not bugs or problems with the beta-13 release. I would say we setup the release and changelog process and rerelease master as v4.0 what do you think?

@knownasilya do you want to do the 4.0 release?

@knownasilya If you give me npm access I can do the release.

Released v4.0.0

https://github.com/adopted-ember-addons/ember-cp-validations/pull/717 is looking for reviewers.

Now that #717 has been merged, as we please able to get a release?

@kiwi-josh I'll do a release in the next days and let you know.

@kiwi-josh released 5.0

@enterpub Thanks for the feedback!


The FORCED attribute present when the TYPE is not SUBTITLES

According to the HLS specification, also linked in the documentation, the FORCED attribute should only be present with subtitles: "The FORCED attribute MUST NOT be present unless the TYPE is SUBTITLES."
https://tools.ietf.org/html/draft-pantos-http-live-streaming-16
However, when writing an m3u8 file, it is present with audio as well:
#EXT-X-MEDIA:LANGUAGE="eng",AUTOSELECT=YES,FORCED=NO,TYPE=AUDIO,URI="...",GROUP-ID="audio_aac",DEFAULT=YES,NAME="eng"
Version: 0.2.6

I think the solution is simply changing the containsAttribute() for Constants.FORCED in MasterPlaylistTagWriter.java:
HANDLERS.put(Constants.FORCED, new AttributeWriter<MediaData>() {
    @Override
    public boolean containsAttribute(MediaData mediaData) {
        return mediaData.getType() == MediaType.SUBTITLES;
    }
    // ...
});

(I couldn't yet made a pull request, I'm new here.)


Quality: PowerShell Summit GH-3388

PR Summary

Resolves #3388

PR Checklist

[x] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
[x] Summary: This PR's summary describes the scope and intent of the change.
[x] Contributor's Guide: I have read the [contributors guide][contrib].
[x] Style: This PR adheres to the [style guide][style].

@michaeltlombardi
Ack! I commented on a change and I think my comment disappeared when I committed the suggested changes, oh well I'll re-comment here. Sorry if you get double notified.
There were a ton of things I got wrong here. I think I've made note of them all for future contributions. Sorry about that Michael! Thanks for correcting all my mistakes!
There were a bunch of instances where the VS Code Markdown was marking BoldParameterReferences as as problem and suggesting the change to UnderScored.
https://github.com/DavidAnson/markdownlint/blob/v0.27.0/doc/md049.md
Is there something I can do so that the markdownlinter uses PowerShell style rules?
Also, I've been doing 1 Issue/PR per file, is that the preferred process or would you rather see 1 Issue/PR per module?


vscode configuration?

https://dev.to/selrond/tips-to-use-vscode-more-efficiently-3h6p

https://dev.to/robole/vs-code-you-don-t-need-that-extension-18d7

https://dev.to/jsmanifest/12-vscode-shortcuts-and-tactics-to-ease-development-5856

https://dev.to/iamismile/my-vs-code-setup-4fcd


User Permissions in admin page

it is possible to admit that only certain users to see some things in the system administrator page,
for example: only to see orders and customers ????

Not currently

Thanks!


We should mention how to install the SDK (pip install apify) somewhere in the docs

On the docs page for Apify Python SDK, there is never mention of how to actually install the SDK (pip install apify), not even in the GitHub repo or Getting Started page.
@fnesveda says:
That was kinda intentional, because we wanted to lead people to create actors with Apify CLI or on the platform, and it's a bit confusing that you would pip install apify but then apify create would not work (because you need the CLI installed).
But I agree that we should probably at least mention it somewhere.

Fixed in 76b5dbc84bb7d7c00c2f5c1cbfe870cbbf48cb29


easy-tag 2.4.1

The linker bug has been resolved so no need for the configure patch anymore.

Merged in https://github.com/Homebrew/homebrew-x11/commit/6d2be39a09468f4ef0d30cc9d38fa362551c1e6f. Thank you for your contribution to Homebrew @robotvert; we appreciate it! :smiley_cat:.
@tschoonj Have you potentially moved this somewhere else formula in your tap changes?

See ed6790be51f24a680f31b08717a11bb7f85d4e31 in Homebrew/Homebrew-gui#2
:smile:


added .DS_Store to git ignore

Added .DS_Store to .gitignore file

Hidden folder structure file that shouldn't be commited

Thank you. I didn't realise there was a better way of doing this, Will set global gitingore.


Add flutter version to non-verbose doctor output

Currently flutter doctor gives us:
[✓] Flutter (on Linux, locale en_US.UTF-8, channel master)
This PR adds the version number to produce:
[✓] Flutter (on Linux, locale en_US.UTF-8, channel master, v0.1.3-pre.46)

This does mean that when running in verbose mode the version number will be repeated on the next line:
[✓] Flutter (on Linux, locale en_US.UTF-8, channel unknown, v0.1.3-pre.47)
    • Flutter version 0.1.3-pre.47 at /home/vic/devel/flutter
    • Framework revision 9a7ab6d8fa (8 minutes ago), 2018-02-20 17:45:44 +0200
    • Engine revision 13cf22c284
    • Dart version 2.0.0-dev.27.0-flutter-0d5cf900b0

Would it be better to leave the redundant version or only keep one of them in? [We could have the verbose detail only list the location of the framework]
[✓] Flutter (on Linux, locale en_US.UTF-8, channel unknown, v0.1.3-pre.47)
    • Flutter at /home/vic/devel/flutter
    • Framework revision 9a7ab6d8fa (8 minutes ago), 2018-02-20 17:45:44 +0200
    • Engine revision 13cf22c284
    • Dart version 2.0.0-dev.27.0-flutter-0d5cf900b0

ref: https://github.com/flutter/flutter/issues/14770

I think it may be easier to read if we order the summary line to have version first?
[✓] Flutter (Channel unknown, v0.1.3-pre.47, on Linux, locale en_US.UTF-8)

Updated with the new order.

Thanks very much @xqwzts


Trace forkSyncStateOnTipPointChange

Description
Trace when forkSyncStateOnTipPointChange completes an iteration.
This provides insight into how much time is spent syncing the mempool after a new block has been adopted.

(Pushed only to sign the commit)


Improve documentation of CLI option values

The options of the CLI commands are described like this
-s, --secret=secret          secret values in KEY VALUE format
(https://github.com/adobe/aio-cli-plugin-cloudmanager#aio-cloudmanagerenvironmentset-variables-environmentid)
To me this is highly confusing because I don't understand the part -secret=secret. In fact you can either use option -s or secret but both option need to be followed by space, KEY, space and VALUE. There is no = to be used with those options.

To accomodate different user patterns, oclif flags work with either space or =.
There's no need to use a space, but = is the default recommendation.
Updated the docs with a link to the oclif documentation that explains this.

Still something like
-s=<secret>, --secret=<secret>  <secret > is KEY VALUE (separated by SPACE)

would be way easier to digest IMHO

This would probably be best to raise in https://github.com/oclif/dev-cli
I'm sure oclif has a reason for using this format for the generated documentation and the risk of not generating the documentation is too high IMO.


1.11.2

When it will be available for Sponge 6.0??

This project is discontinued you should use Nucleus instead


Fixed the issue [#1824] - resource deletion issue

@pkdash Can you code review this small PR when you have a chance? I believe it is a regression issue that used to work but does not work now. I have also added relevant unit tests to cover this specific scenario in which an empty resource is created first in hydroshare zone and then files from federated user zone is added into this resource in hydroshare zone. The added unit tests have passed in my local test environment. It'd be great if this PR can be merged to make into the next deploy if not earlier as a hot fix. Thanks.

@pkdash I have addressed your review comment and run federation tests in my local development environment to make sure they all passed. So it is ready for your final review. Thanks.

@pkdash Have addressed your further comment on unit test and ran the test again in my local development environment and all tests have passed. So it is ready for your final review again. Thanks.

+1. Merge after Jenkins checks are successful.


Land angular/devkit #235 (SW support in schematics)

Needed by the CLI before 1.6.0 can be released. Service Worker support for schematics.

PR merged and devkit released.


allow passing in db manually

Just a quick dirty hack to allow users to pass in the db manually (nothing else is changed). Most notably, this opens up the possibility for objection-db-errors to pass in the db during the wrapping process here:
https://github.com/Vincit/objection-db-errors/blob/master/index.js#L9
'cause as it is right now, you need to check up to all 4 db types (mssql/sqlite/pg/mysql) every time you want to wrap an error, and that's inefficient

Oh, and I guess I could've set the type of the db parameter as one of postgres|sqlite|mysql|mssql but I don't know typescript so I just left it as an optional string in the type definition 🤷♀

No thanks. Wrapping the error takes couple of microseconds :smile:

Well, I mean it is a backwards-compatible (won't affect any existing code), and I don't see any downsides to merging this in unless if you have plans to expand the API in the future? I would love to hear your thoughts on this.
Additionally, if "those couple of microseconds" don't matter to you, then you really don't need to be trimming down dependencies on the main objection.js package, either.
@koskimas

Why would I merge this? What benefit does it offer? The performance reason is just wrong. There is no meaningful difference in performance.

Additionally, if "those couple of microseconds" don't matter to you, then in the same vein, you really don't need to be trimming down dependencies on the main objection.js package, either, but we all know which direction 2.0 is heading.

Removing useless dependencies is the same thing as this? So adding a useless code is the same thing as removing useless code?

I... wow. Okay. Sorry I even bothered. I apologize I even asked the question and brought up the PR, but was it really that bad that you had to mark it as spam, and verbally harass me?

Did you really just send an email to Vincit :joy: What did you think you would achieve by that? ps. I haven't worked there in ages.
I marked the PR as spam by accident (hence the un-marking right after that). I also don't see where I verbally harassed you. And actually I don't care. Please don't open any issues here or in objection ever again.  Goodbye.


Feat: R 306 - Binary Search Tree Traversals add

Thank you for contribution @dharsan19
I appreciate it 😊


chore: bdd-nh-import-1584517661 to 0.0.1

chore: Promote bdd-nh-import-1584517661 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  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:

OWNERS

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


Process - Changes Sales Order Lines.

Sales orders in NAV change frequently because customers change their order or due to out of stocks, orders are partly delivered or the truck is filled with another product mix.
When the order is changed in NAV, the order in Samsa needs to change accourdingly.

User case order VO2100075, order was put in for 10 boxes of capps on line 1000, transfer to SAMSA ok. Order was subsequently changed to 5 boxes of capps on line 1000, transfer to SAMSA. Order was changed to 5 but picking task for 10 boxes stayed open and a picking task for 5 boxes was added. Solution change status picking line to completed after update, or change the pickingtask.

User case order VO2100076, instead of changing the order line, shipped 5 boxes via the old procedure, test case for using the old system next to the new. Same result, which is good, because solving the above will solve this problem too.

Fixed now on Picking task id - use same Picktask while not closed - and changes when completed only


Code Review to find problems with too many connections

@tboggiano asked me to have a look at the code to find problems causing too many open connections.
First of all: As you extensively use .ForEach and .Where, it is very hard to know what $psitem (or $PsItem, or the offical $PSItem) is holding at that moment. Sometimes you alias ($Instance = $psitem), but even when you do, you sometimes don't use the alias but $psitem again.
But let me come to dbatools, the main command Connect-DbaInstance and the main parameter -SqlInstance. If you use a string like "SQL01" or "SQL02\TEST" for -SqlInstance, Connect-DbaInstance will connect to that instance with either a brand new connection or a ready to use connection from the connection pool. The command will then build a SMO object and fill it with some initial values from the instance. This SMO object is returned. If you pass the same string as -SqlInstance to following dbatools commands (like you do most of the time in dbachecks), these commands all pass that string to Connect-DbaInstance which will build a brand new SMO and return it to the command to be used there. The SMO is then destroyed at the end of the command and the connection should (!) be returned to the connection pool.
To avoid building all these SMO objects, all commands can use a SMO object as -SqlInstance. This object is then passed to Connect-DbaInstance. But this time, only some additional parameters like -Database are taken into account and maybe change the connection (and yes: In some cases we have to build a brand new SMO - I will not go into detail here, just have a look at the code). At the end, the entering SMO is just returned, which is way faster and should not open new connections.
This way you can also configure the connection by using -NonPooledConnection with Connect-DbaInstance for example - which will not use connection pooling at all.
So I would suggest a complete code refactoring for all lines related to calls to dbatools commands. Depending on how "near" you would like to get to the coding standards of dbatools, I would "copy" some of their naming standards. Maybe central loops like foreach ($instance in $SqlInstance) { } or naming the SMO $server, as the name of the SMO type is "Server" (you do this in Get-DatabaseDetail). Then for every reader it is very clear that $instance may hold a string or a SMO, but $server will always hold a SMO. Then all calls to dbatools commands should use -SqlInstance $server or have a comment with details why not.
But you don't have to, you can also use your current naming $Instance and $InstanceSMO. But you should start to use $InstanceSMO when running dbatools commands instead of $psitem.

Thanks for this @andreasjordan - I hadnt seen that it came in.
In short
My recommendations from above are (unless @andreasjordan says I am wrong

Add -NonPooledConnection with Connect-DbaInstance at the top of Instance, Database and Agent Check files
Ensure all calls to dbatools in Instance, Database and Agent Check files and also in Get-AllInstanceInfo use the InstanceSmo object

Any changes will need documented proof of improvement in speed, reduction of connection pooling errors and to pass all of the AST Pester validation without significant refactoring of it.
More descriptive reasoning below
If we take Instance level checks  - I think that what you are suggesting is that where we make our first call to Connect-DbaInstance here
https://github.com/dataplat/dbachecks/blob/4bfe7136cbf6d7f143fdb553f5b4a7c9a04cad70/checks/Instance.Tests.ps1#L17
we need to add -NonPooledConnection
Which means that the Instance SMO object passed to Get-AllInstanceInfo will not use connection pooling
https://github.com/dataplat/dbachecks/blob/4bfe7136cbf6d7f143fdb553f5b4a7c9a04cad70/internal/assertions/Instance.Assertions.ps1#L89
for each of its calls to the dbatools commands would be beneficial. This builds a single object with all of the results the user ahs asked for and then the Pester validation is run against this object.
I think for the database checks we are suggesting that the call to Connect-DbaInstance here
https://github.com/dataplat/dbachecks/blob/4bfe7136cbf6d7f143fdb553f5b4a7c9a04cad70/checks/Database.Tests.ps1#L13
adds -nonpooledconnection
and each call to a dbatools command uses the $InstanceSMO object declaratively - I think that this file will show the most improvement.
It would be nice to build an object for testing for databases in the same way as was done for the Instances but for right now that be a low-hanging fruit
The Agent Checks are even further behind in coding but would benefit from either the use of InstanceSmo object with none-pooled connection and/or a "testing" object being created
I think the HADR tests are in better shape as they do gather a testing object (this ignores some of the other glaring errors with this set of tests)
The other checks are of lesser performance worries right now.
We do use the methods because they were quicker in testing when the code was written, and we were able to update the minimum PS version requirement in relation to dbatools.
There is also the added complication of the looping being inside of a Pester instance (thats the wrong word for v4) which makes for all sorts of scoping issues.
I would be unwilling to accept the large amount of refactoring that would be required for every check file and the associated Pester test rewrites at present. This would be better done when a rewrite for Pester v5 was implemented.
Coding standards and indeed naming standards are highly enforced by the Pester validation of the AST as to ensure that both versions of the Power Bi file and the storing the results in the database commands work correctly requires some frustratingly annoying regex so I am unwilling to alter any of the current settings without a significant amount of testing.
for example - https://github.com/dataplat/dbachecks/blob/4bfe7136cbf6d7f143fdb553f5b4a7c9a04cad70/tests/Unit.Tests.ps1#L13


V6 MVC routing /3x

Fixes #23169
Internal review URL

@halter73  this was an easy port to the minimal hosting model. Everything seems to work. Are there any minimal hosting changes that impact routing?


pdf error in flutter

platformexception(error, typeerror: cannot read property 'getdocument' of undefined, null , null) error in flutter

Push. This error occurs in flutter web for me.


Add flag for allowing dirty branch

This adds the flag allowDirtyBuild which takes a boolean-string.
When the flag is set to true, versions can be generated based on a dirty branch.
This flag was added when folders like streamingAssets have to be deleted for building for specific platforms.
Resolves https://github.com/webbertakken/unity-builder/issues/89

This PR includes a quick refactor that splits responsibility between Input and BuildParameters to make changes like this possible:

BuildParameters now relies on Input and Version

Input is now a simple model with getters and some basic input sanitisation. Now without any dependencies outside of @actions/core.


Fixed OLD_VERSION variable assignment in seafile-entrypoint.sh

Without this fix, bash tries to run $VERSION as a command.

Also included a commit to replace python-imaging with python-pil in the Docker build.


chore: rsa dep changes

Also removes dependabot duping

Codecov Report

Merging #58 (bc2d112) into main (bf55a3f) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #58      +/-   ##
==========================================
- Coverage   56.02%   55.90%   -0.12%
==========================================
  Files          22       22
  Lines         755      753       -2
  Branches      186      186
==========================================
- Hits          423      421       -2
  Misses        204      204
  Partials      128      128

Impacted Files
Coverage Δ

ucan-key-support/src/rsa.rs
61.11% <100.00%> (-2.05%)
:arrow_down:


Support for --stdout and -

isort uses --stdout argument to write sorted imports to the stdout and also uses - argument to read from stdin.
usort doesn't support this behavior because of which I am unable to auto format in Emacs buffers.
isort behavior
$ isort --stdout -
import sys
import os
sys.stdout.write(os.getcwd() + "\n")
import os
import sys

sys.stdout.write(os.getcwd() + "\n")

usort behavior
$ usort --stdout -
Usage: usort [OPTIONS] COMMAND [ARGS]...
Try 'usort --help' for help.

Error: no such option: --stdout

Try usort format -

Thanks. It worked.


Update tool.py

Hey !  tried using the exisisting code, kept getting some error. I am proposing the changes for the same reason.
Thanks for the resource !

What's the error you're running into?


Aggregate part repos caching bounded to a root instance

This PR resolves the issue and makes AggregateRoot repositories cache non-static.

@armiol PTAL.

@dmytro-grankin please do back-merge and increase the core-java version before pushing.
Other than that, LGTM.


Add meta decorators

Summary
Add meta decorators to all commands, sub-commands, and plugins, and also, be able to attach them to the options, within a command.
Why is this needed?
This is needed because I will not stop bugging you to make it, and it would be useful for others.
Ideal implementation
Here is my idea:
Have some sort of basic decorator, like this:
@arc.add_metadata(arc.Metadata(example="beans"))

but then, if people want to make custom metadata, they can subclass arc.Metadata and add their arguments to it.
I have no idea, how adding them to an option would work, so I will leave that up to you, or we can have a talk about it idk.
Checklist

[x] I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.

I currently do not feel like this fits into the main library in a nice way. Perharps as an extension? Closing for now.


Add header policy when wiremock bootups

Hi Team,
Just wondering do we have any policy for enabling/disabling headers across all the mappings ?
Please see below example of a sample request where we're expecting Authorization in header. I want to make this as plug and play -- make this enable/disable without changing the mappings.
{
"mappings": [{
"request": {
"method": "GET",
"headers" : {
"Authorization" : {
"matches" : "^Bearer\s.{54}$"
}
},
"urlPath": "/xyz"
}
},
"response": {
"status": 200,
"headers": {
"Content-Type": "application/json"
},
"bodyFileName": "xyz.json"
}
}
]
}
Thanks,
Ritesh

You can achieve this by writing a RequestFilter implementation that checks the Authorization header before allowing the call to proceed.
Here's an example of how to write a filter: https://github.com/tomakehurst/wiremock/blob/master/src/test/java/com/github/tomakehurst/wiremock/RequestFilterAcceptanceTest.java#L105


Temporary exclude numpy 1.17.

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Numpy 1.17 breaks hyperspy: exclude last release until it is fixed.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

It looks like the 'hyperspy' output doesn't have any tests.
It looks like the 'hyperspy-dev' output doesn't have any tests.


Product Backlog

false color voxels by component size
Approach: if you choose a size of a ball, then you can color all the points in the
ball based on how many points are in there.
ball size could be very small (the limit to ball size is that points
literally must be adjacent).

Each "product" in the backlog should have a unique issue; not a single issue bloated with lots of unrelated things. close this, and break it out into a new issue? @alee156


Add Third Party Cloud Storage Support

Is your feature request related to a problem? Please describe.
Allow users to use another cloud storage provider other than Microsoft OneDrive. If Google Drive Sync is installed then
Describe the solution you'd like
For example, if Google Drive Backup & Sync is installed, then it should automatically be displayed on the 'Drives' section where OneDrive is. Additionally, if OneDrive is not installed, then it should not be displayed in the 'Drives' section.
Describe alternatives you've considered
The user can manually add cloud storage locations from the settings. For example, the user can go to settings, add a cloud storage provider manually, and locate the folder for cloud storage.
Additional context
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?

@mbeps this is already implemented in v0.21.1, can you fill out the issue template so we can investigate why it's not working on your device?


Schema builder (MySQL): append in the wrong place

What steps will reproduce the problem?
Create a migration like this:
        $this->createTable('table', [
            'name' => $this->string(50)->notNull()->append('CHARACTER SET ascii COLLATE ascii_general_ci')->comment('Property name'),
            'value' => $this->text()->comment('Property value')
        ], 'ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci');

What is the expected result?
The SQL command is execute successfully.
What do you get instead?
An error is generated by MySQL because of the wrong order in the column definition:
Exception 'yii\db\Exception' with message 'SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CHARACTER SET ascii COLLATE ascii_general_ci,
        `value` text COMMENT 'Property va' at line 2
The SQL being executed was: CREATE TABLE `table` (
        `name` varchar(50) NOT NULL COMMENT 'Property name' CHARACTER SET ascii COLLATE ascii_general_ci,
        `value` text COMMENT 'Property value'
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci'

This is happening because the append() function literally appends the given string to the column definition (maybe I'm doing something wrong?). I don't know if it's legal in other RDBMS, but in MySQL it's not.
Additional info

Q
A

Yii version
2.0.9

PHP version
7.0.7

Operating system
Latest Debian testing

MySQL version
5.6.30

Great software and thanks for your help.

This is expected behavior append() method always adds SQL to the end of the column statement.
It does not aware of the method order in the chain, just as well as any other method at ColumnSchemaBuilder.

Fair enough, but you should state that in your docs:
http://www.yiiframework.com/news/102/yii-2-0-9-is-released/
In the release notes there are examples for using append() for column encoding.

@klimov-paul

This is expected behavior append() method always adds SQL to the end of the column statement.

This syntax was designed to set column collate/charset: https://github.com/yiisoft/yii2/issues/11195
I you can't rely on it for setting charset, what is the real use case for append()?

Why asking me? Ask @df2 fro that - it was his improvement.

I am going to the conclusion, that current implementation is buggy and this issue is valid bugreport. If there is no use case for append text after comment declaration, append() behavior should be changed.

Or at least it should be noted somewhere, and probably a new feature request for another function should be opened (since this is a special use-case right?)

Yes, it's a bug. Append should go before comment,

Please be aware that this could vary on the DBMS being used - but I guess you already know that, just a reminder :-)

Please fix this bug.
For now, it's impossible to use "CHARACTER SET" for specific column in ALTER TABLE statement via ColumnSchemaBuilder.
This code:
        $this->alterColumn(
            $tableName,
            $columnName,
            $this->string(500)->null()->defaultValue(null)->append('CHARACTER SET utf8')
        );

appends "CHARACTER SET" to end of colun definition, so MySQL throws error

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax;

Yes, it's a bug. Append should go before comment.

The official documentation says something else:
column_definition:
    data_type [NOT NULL | NULL] [DEFAULT {literal | (expr)} ]
      [AUTO_INCREMENT] [UNIQUE [KEY]] [[PRIMARY] KEY]
      [COMMENT 'string']
      [COLLATE collation_name]
      [COLUMN_FORMAT {FIXED|DYNAMIC|DEFAULT}]
      [STORAGE {DISK|MEMORY}]
      [reference_definition]
      [check_constraint_definition]

But according this documentation the DEFAULT and CHECK keywords are misplaced too...
If we'd like to follow the documentation we would have to change
    case self::CATEGORY_NUMERIC:
        $format = '{type}{length}{unsigned}{notnull}{unique}{default}{comment}{check}{append}{pos}';
        break;
    default:
        $format = '{type}{length}{notnull}{unique}{default}{comment}{check}{append}{pos}';

to
    case self::CATEGORY_NUMERIC:
        $format = '{type}{length}{unsigned}{notnull}{default}{unique}{comment}{append}{pos}{check}';
        break;
    default:
        $format = '{type}{length}{notnull}{default}{unique}{comment}{append}{pos}{check}';

@simialbi have time to implement it?

I think it should be possible


Add LICENSE

#1

Merged! Sorry for the delay – and thanks for adding the license. Hope you find the library useful :)

Thank you so much !!!


share data of opencv mat with arm_compute::Tensor

How do we share data of opencv mat with arm_compute::Tensor

I know how to copy data using execute window ,but it is taking much time.Then I used
' import_memory (Memory(img.data)) '//where img is a opencv mat
but it is giving an error:no matching function for call to 'arm_compute::Memory::Memory(uchar*&)'

Hi @waveajay
What version of the library are you using? 19.05?
Please take a quick look at our unit test for importing memory: https://github.com/ARM-software/ComputeLibrary/blob/master/tests/validation/NEON/UNIT/TensorAllocator.cpp#L106
The test shows how to import memory when using NEActivationLayer.


DESCRIPTION malformed

> install_github("grambank/rgrambank", dependencies = TRUE)
Downloading GitHub repo grambank/rgrambank@HEAD
Error: Failed to install 'rgrambank' from GitHub:
  Line starting 'person("Hedvig", "Sk ...' is malformed!

I haven't yet found what is malformed about that line. Ideas?

FOUND IT! It needed another tab.

False alarm, the old error went away but a new one appeared:

> install_github("grambank/rgrambank", dependencies = TRUE)
Downloading GitHub repo grambank/rgrambank@HEAD
── R CMD build ─────────────────────────────────────────────────────────────
✔  checking for file ‘/private/var/folders/2r/drwc5p6n26ncm5cws9qsntrw0000gr/T/RtmpQhIkGq/remotes7f531e567fe4/grambank-rgrambank-3560f51/DESCRIPTION’ (363ms)
─  preparing ‘rgrambank’:
E  checking DESCRIPTION meta-information ...
   Authors@R field gives more than one person with maintainer role:
     Simon Greenhill<EMAIL_ADDRESS>[aut, cre] (<https://orcid.org/0000-0001-7832-6156>)
     Hedvig Skirgård<EMAIL_ADDRESS>[aut, cre] (<https://orcid.org/0000-0002-7748-2381>)

   See section 'The DESCRIPTION file' in the 'Writing R Extensions'
   manual.
Error: Failed to install 'rgrambank' from GitHub:
  ! System command 'R' failed

This problem still persist, please help @xrotwang @SimonGreenhill

I need to demo this to Angela now so I'm gonna remove myself from author list.

ok so what's happening with this?


can you provide your trained models?

hi, ikhlestov,
you really do a great job. thanks for your share.
can you provide your trained models?

Hi!
Unfortunately they were saved on a production server, to which I do not have access now.

ok, thanks , i just need them for transfer training. now i try to trained it in cifar data myself. thanks again.

I also need the trained model to implement transfer learning. Hoping to provide. Thx!

@EdwardMa12593
@tangyuandanhuang
I use the pytorch code now ,  you can find densenet in torchvison.models,  they provide the trained model.


[KYUUBI #3445] Flaky Test: Temp view should be deleted after test suite

Why are the changes needed?

Fix https://github.com/apache/incubator-kyuubi/issues/3445
temp view should be deleted after test suite, otherwise, some tests which purpose to test show tables will be failure
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

LGTM, pending CI.

This should go branch-1.6 as well?

Codecov Report

Merging #3446 (4f54370) into master (20d1dd4) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #3446      +/-   ##
============================================
+ Coverage     51.42%   51.45%   +0.03%
  Complexity       13       13
============================================
  Files           481      481
  Lines         26705    26761      +56
  Branches       3733     3753      +20
============================================
+ Hits          13734    13771      +37
- Misses        11630    11640      +10
- Partials       1341     1350       +9

Impacted Files
Coverage Δ

.../kyuubi/plugin/spark/authz/PrivilegesBuilder.scala
66.66% <100.00%> (+0.19%)
:arrow_up:

...kyuubi/engine/spark/session/SparkSessionImpl.scala
68.57% <0.00%> (-15.43%)
:arrow_down:

...apache/kyuubi/engine/JpsApplicationOperation.scala
77.41% <0.00%> (-3.23%)
:arrow_down:

...pache/kyuubi/engine/YarnApplicationOperation.scala
66.66% <0.00%> (-1.86%)
:arrow_down:

.../org/apache/kyuubi/session/KyuubiSessionImpl.scala
76.59% <0.00%> (-1.67%)
:arrow_down:

...mon/src/main/scala/org/apache/kyuubi/Logging.scala
52.63% <0.00%> (-1.32%)
:arrow_down:

...yuubi/server/metadata/jdbc/JDBCMetadataStore.scala
89.27% <0.00%> (-0.70%)
:arrow_down:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
97.41% <0.00%> (-0.08%)
:arrow_down:

.../plugin/lineage/events/OperationLineageEvent.scala
64.00% <0.00%> (+0.36%)
:arrow_up:

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
73.10% <0.00%> (+0.84%)
:arrow_up:

... and 1 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks, merging to master


Implement codegen for generating transformed template protos

what is this PR
This PR concludes the work of code generation from Template for everything that the
adapter author is interested in. After this, work related to codegen that plumbs the supported template into mixer framework remains. Will be done in next PRs.

NOTE In this PR, except the mixer framework plumbing code, all hand written generated code is deleted.

what is in this PR

Changes the codege/model/model.go to produce data required to generated a transformed template.proto
Changes the interfacegen/generator.go to produce template.proto files along with the interface.go files.
Update the bazel rule mixer_gen to produce two files (interface go file and modified template proto that contains Type message and the ConstructorParam message)
Delete the handwritten code for existing checked in templates (sample/report and sample/check).

NOTE PR looks big, but most of the change is test changes. To review, I think it will help to start looking in following order:

Go template skeleton on how the generated template (from user's template) will look. tools/codegen/pkg/interfacegen/template/templateproto.go
generated proto baselines : tools/codegen/pkg/interfacegen/testdata/*.golden.proto
generate.bzl changes for how new template proto gets created and used.
All other code...

This change is

Jenkins job mixer/presubmit passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/presubmit passed

jenkins run mixer/e2e-smoketest

Jenkins job mixer/presubmit passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/presubmit passed

Jenkins job mixer/e2e-smoketest passed


fix: remove unused property - port

Fixes #1304

@nicojs we've got a problem >.<

I found the issue. You removed too much. The stryker-karma-runner is still in charge of figuring out the exact port karma is running on. I've restored that part of the code. Should be green now 🤞

@nicojs it's green! <3


Some unmentioned and unexplaned changes in v 1.1.0

[In your commits of v1.1.0] (https://github.com/threema-ch/threema-msgapi-sdk-php/commits/v1.1.0) I saw that you mentioned these things:

support capability check of a identity
public key store implementation (related: https://github.com/threema-ch/threema-msgapi-sdk-php/issues/8)
enable curl safe upload

What exactly do these changes exactly mean?
I've had a quick look over your source code, but you committed many changes at once. So can you please provide a short explanation?

And BTW the change of 'enable curl safe upload' is not included in threema-msgapi-tool.php AFAIK. (because you haven't updated it after the commit where you added the command).

Thank you, the threema_msgapi.phar is now up to date.
The changes of the v1.1.0 are the implementation of the new api methods blob-upload, blob-download and id-capability (see https://gateway.threema.ch/en/developer/api), a new console client environment and the new ThreemaMessage Types Image and File.

id-capability
Ah okay, so with 'support capability check of a identity' you mean the part 'Check file reception capability of an ID'. Okay.
And while looking in #8 I also understand what the public key store is.


High reject rates on multi-GPU systems.

Interesting: pulling out cards seems to reduce reject rates by the same proportions.
Could I be wrongly replicating the starting nonce offset? Possible but then the question would be: why cannot I detect this when using the replicated debug device?
Very interesting.

A note to multi-gpu users.
Leaving aside I am mainly interested in supporting APU+discrete users, this problem has been occasionally investigated in those months. That effort lead to nothing.
On the pro side, with the replicated code across algos growing bigger and bigger, the pattern is pretty obvious at this point. Hopefully once pool compatibilty will be solved and the dispatch subsystem rewritten multi-gpu will work as well. At that point, I might as well mark it for Beta.

As of 5c999bede5fe0c9bf52dcb8740f822b241a31036, some work has been carried out on this and two issues have been identified.
The first issue causes a stream of rejects whatever diff is increased. The system goes back to valid state as soon as new work is received or the remote server pulls back difficulty to the same value. The original sin originated from legacy miners way of managing work units: a similar pattern was originally envisioned in M8M but it has not been enforced.
The second issue is that nonce2 rolling is apparently broken. This has been tested in the past but it has most likely be damaged during some refactoring. As it stands now, nonce2 rolling is completely disabled and utterly broken, producing duplicate shares.
Both issues are expected to be fixed by next version, which will be marked beta.

An user inquired about multi-gpu support status so I guess it's worth updating this.
318fc98128278c9b426ada91cc2c6f9995a35d57 contains a a fix which means multi-gpu should be working now. Previously, rejects were no more but shares were considered stales (miner-side rejected).
This is till not closed as the multi-threaded wait method has been found to be weak in both performance and resilience. Therefore, M8M will transition to the usual one-queue-one-thread approach.


Crash when viewing Orbital Laser Drill Entity

Advanced Rocketry version 1.10.2-1.0.7
LibVuples version 1.10.2-0.1.13
Crash Report: https://gist.github.com/mallrat208/b6c54c24f8105dc067e51b38befa80e2
I've been playing around in creative with the Laser Drill and turned on the ability for it to actually drill the planet below which works as expected. I decided to 'see' it in action and left my station Chunkloaded using chickenchunks. When I got within range of the drilling area I experienced a Client Crash in related to the laserNode entity.

Looks like crash trying to render the shadow/fire of the entity.  Investigating

I did not figure out the exact cause, however because the laser itself should never be on fire or have a shadow I'm just gonna nuke the call to that method so it should prevent this issue from occuring again anyway.


Redirects cause exception if no location header is present

Amazon S3 301 redirects sometimes do not contain a location header (if, for instance, you create a bucket in a non-standard region, and then attempt to access it at the non-region-specific subdomain, though probably in other cases as well).  This seems like strange behavior on S3's part, but superagent probably shouldn't throw an exception when this happens.

Will give an error now: https://github.com/visionmedia/superagent/commit/ecd32cb0d15d291c4262852c369c318ff30a9bf9
You can't redirect with no header


Exclude function not properly working

Hi,
First of all thanks for the plugin! It looks very promising. I am trying to use this with my vue plugin but I am getting a error:
[!] (plugin jscc) Error: Could not load C:\Users\Jessie\projects\vue-scan-field\src\ScanField.vue?rollup-plugin-vue=script.js (imported by C:\Users\Jessie\projects\vue-scan-field\src\ScanField.vue): ENOENT: no such file or directory, open 'C:\Users\Jessie\projects\vue-scan-field\src\ScanField.vue?rollup-plugin-vue=script.js'

This can be because the plugin does not support vue. I pressume this because .vue is not in the extensions list. I had decided to put *.vue in the exclude list but this did not work. This is how my code looks:
    jscc({
      values: { _FRAMEWORK: 'quasar' },
      exclude: '*.vue'
    }),

But I keep getting the same error.

I have now added this and it works properly now. Is this the way it is supposed to work?
    jscc({
      values: { _FRAMEWORK: 'vuetify' },
      include: '*/core.js',
      exclude: '*'
    }),


Travis ignoring commits

since ef9c9740e4b9ea7ba3f17989edd9492148e3e1a9

Apparently it went back in time and fixed itself?


[Gaprindashvili] Backport Admin report and request roles

This PR manually backports to G:

[ ] #17003 (easy backport, we may want to do via normal channels)
[ ] #17444 (treats admin via features and no longer by name)
[ ] #17849 (removes extra role introduced)

There were conflicts (especially in filterer and miq_user_role) since #17768 was applied before this PR
Followup PRs to backport:

[ ] https://github.com/ManageIQ/manageiq-api/pull/385 - use request_admin_user
[ ] https://github.com/ManageIQ/manageiq-api/pull/447 - tests only (corresponds to #17849)
[ ] https://github.com/ManageIQ/manageiq-ui-classic/pull/4489 ( backport of #3993 #4487 )

https://bugzilla.redhat.com/show_bug.cgi?id=1608554

closing for now - deemed this was not a priority to merge to G

#17849

9a63e127f2

#17444

f6c02e812b
2f61692f13 * difficult - overlap with #17768
db76d9632c *
fd13a8ab79 *
83ad831146 *easy
9c9a52f4e0

#17003 - should easily backport

b756550a35

ManageIQ/manageiq-api#385 - should easily backport
ManageIQ/manageiq-api#447 (tests only) - should easily backport
....
ManageIQ/manageiq-ui-classic#4489 (regular version: ManageIQ/manageiq-ui-classic#3993)
User.get_group


Fix broken link to wayland protocol draft

It seems like Github does not forward Gist links from the old username to the new one. This PR changes the username in the link to the current username.

hah, sure I guess, but honestly maybe I should delete this whole paragraph


Support for CloudFront Lambda@Edge

Hi,
I've been using the aws-lambda-go package for integrating API Gateway, S3, DynamoDB and Lambda. It's been great!
One integration I'm really interested in using is CloudFront (Lambda@Edge). It would be great if the request/response types are modeled already so that I don't have to write the boilerplate.
ref; https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-generating-http-responses.html

Lambda@Edge only supports JavaScript Lambda functions

Well that's disappointing :-(

yeah not much fun!

You must create functions with the nodejs6.10 runtime property

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html

Sad times - I made a url redirect function with custom structs as aws don't provide them only to find out golang doesn't work on lambda@edge.
Anyone heard of any developments on this?

Hi there, any news about Go support for Lambda@edge ?

Hi there, any news about Go support for Lambda@edge ?

Sadly, we still have nothing ):
See https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html#lambda-requirements-lambda-function-configuration

I'm surprised this issue for such a long-time open... I just gave a try me too because Go offers ver short execution times and sounds ideal for lambda.
So, I created custom CloudFront event structs because it doesn't exist in the SDK, then I deployed my function and I confirmed is working from the console by sending CloudFront test events. When I tried to attach it on a distribution I got an error that "go1.x" execution environment is not supported only nodejs and python3.7. Be aware of "Viewer request" based events there is a function bundle size limit of 1MB which at the moment is not very clear in the docs, for the "Origin request" I didn't get an error for this limit.
:-(

Despite the disappointment that golang can't be used for edge lambdas happy to have stumbled on this thread. Did find it odd why this library wouldn't support Cloudfront events but everything else. This conversation clears it up nicely.

Glad to know I'm not the only one facing this issue

Just stumbled upon this.
Considering that this issue has been open since 2018, is there any chance we can get an update on any progress or planned support for Lambda@Edge in Go?
Go's efficiency and low resource consumption could significantly benefit companies by reducing costs and increasing speed, which is critical for edge computing scenarios. Likewise, AWS could also see reduced resource usage on their end.
Really appreciate your help in advance

Yearrrp, also stumbled across this looking for the right structs and then found out it's not supported :'(
I'm surprised that Go and Rust runtimes aren't supported considering all Lambda@Edge functions run on Amazon Linux.
Throwing my appreciation behind this feature!

This is turning from a want to a need. Lambda@Edge is a race car with monster-truck wheels - yeah it gets the job done... but with a ton of unnecessary weight. Let us use the fast and nimble racing tires! Let us clock in blazing fast execution while reducing our carbon footprint! Let us GOOOOOOOOOOOO!

Also have run into this. I'd prefer to be able to move our edge functions to go (especially viewer requests since they're hit by every page) rather than just having to increase limits to accommodate more requests / overhead with using node


Add scheduler test for changed input + bug fix

Add a scheduler test to check that changing the Action's input file causes a rebuild.
Fix a bug where a change to the Action's own inputs but only its dependencies would trigger a rebuild.

Duplicate of #148.


Spark - Delta Lake Format Writing Error

Describe the bug
Unable to write to seasweedfs using delta format hdfs client libraries. Parquet format works.
#%%
import pyspark

#%% when not using spark submit
builder = pyspark.sql.SparkSession.builder \
    .master("local[1]") \
    .config("spark.driver.memory", '1G')
spark = builder.enableHiveSupport().getOrCreate()

# %% Write to Seaweedfs directly
data = spark.range(0, 5)
data.write.format("delta").save("/deltalake/tmp/delta-table") # throws error attached to issue
data.write.format().save("/deltalake/tmp/delta-table") # writing non-delta format works
data.write.format("delta").save("file:///home/sparkuser/test") # writing to local file system works
data.write.format("delta").save("file:////mnt/deltalake/tmp/test") # writing to mounted seaweedfs file system doesn't works

Error:
error.txt
System Setup
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

pyspark: 3.3.2
delta-spark: 2.2.0
hadoop: 3.3.1
seaweed: seaweedfs-hadoop3-client-3.33.jar
Weed Version:
version 30GB 3.42 8821d6b16 linux amd64
Expected behavior
The write command to complete and the delta-table files to appear on the file system.
Screenshots

Comments
I see the hadoop jars are on version 3.33, is the jar file still supported?
I could try the s3 connector.

There are too many steps to setup.
Possible to make it into some docker file that I can run towards a SeaweedFS cluster?
3.33 is correct.

I can do that.
I tried s3a and noticed even with that it breaks... I'm starting to think it might be an issue with delta-spark.
What interesting is some files get created... very strange. Could be an issue with the delta-spark libs.

31mPy4JJavaError\u001b[0m: An error occurred while calling o71.save.\n: java.io.FileNotFoundException: No such file or directory: s3a://deltalake/tmp/test/_delta_log\n\tat io.delta.storage.S3SingleDriverLogStore.listFromInternal(S3SingleDriverLogStore.java:236)\n\tat io.delta.storage.

One dockerfile coming right up.

@chrislusf
I'm looking at the seaweedfs-s3 pod logs.
<Error>NoSuchKey<Message>The specified key does not exist.</Message><Resource>/deltalake/tmp/test/_delta_log</Resource><RequestId>1677789004559491052</RequestId><Key>tmp/test/_delta_log</Key><BucketName>deltalake</BucketName></Error>
I0302 20:30:04.561522 s3api_objects_list_handlers.go:44 ListObjectsV2Handler deltalake

I'm guessing here, but I wonder if the _delta_log folder name is causing an issue.

no special treatment to names like _delta_log.

This docker file should replicate the environment.
FROM apache/spark-py:v3.3.2

ARG SPARK_UID=185
ARG SPARK_GID=185

# Keeps Python from generating .pyc files in the container
ENV PYTHONDONTWRITEBYTECODE 1

# Turns off buffering for easier container logging
ENV PYTHONUNBUFFERED 1

# Pyarrow requires this for pandas_udf integration
ENV PYARROW_IGNORE_TIMEZONE 1

ENV CRYPTOGRAPHY_DONT_BUILD_RUST=1

# Reset to root to run installation tasks
USER root

# Install apt-get requirements
RUN apt-get update \
    && apt-get install -y wget curl vim sudo \
    && ln -s /usr/bin/python3 /usr/bin/python \
    && update-alternatives --install /usr/bin/python python /usr/bin/python3 1 \
    && rm -rf /var/lib/apt/lists/*

RUN pip install --upgrade pip

# Download hadoop-azure, azure-storage, and dependencies (See above)
RUN wget --quiet https://repo1.maven.org/maven2/org/codehaus/jackson/jackson-core-asl/1.9.13/jackson-core-asl-1.9.13.jar \
    -O /opt/spark/jars/jackson-core-asl-1.9.13.jar
RUN wget --quiet https://repo1.maven.org/maven2/org/codehaus/jettison/jettison/1.1/jettison-1.1.jar \
    -O /opt/spark/jars/jettison-1.1.jar
RUN wget --quiet https://repo1.maven.org/maven2/io/delta/delta-core_2.12/2.2.0/delta-core_2.12-2.2.0.jar \
    -O /opt/spark/jars/delta-core_2.12-2.2.0.jar
RUN wget --quiet https://repo1.maven.org/maven2/io/delta/delta-storage/2.2.0/delta-storage-2.2.0.jar \
    -O /opt/spark/jars/delta-storage-2.2.0.jar
RUN wget --quiet https://repo1.maven.org/maven2/org/wildfly/openssl/wildfly-openssl/1.0.7.Final/wildfly-openssl-1.0.7.Final.jar \
    -O /opt/spark/jars/wildfly-openssl-1.0.7.Final.jar
RUN wget --quiet https://repo1.maven.org/maven2/com/github/chrislusf/seaweedfs-hadoop3-client/3.33/seaweedfs-hadoop3-client-3.33.jar\
    -O /opt/spark/jars/seaweedfs-hadoop3-client-3.33.jar && \
    wget --quiet https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-bundle/1.11.901/aws-java-sdk-bundle-1.11.901.jar \
    -O /opt/spark/jars/aws-java-sdk-bundle-1.11.901.jar && \
    wget --quiet https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-aws/3.3.1/hadoop-aws-3.3.1.jar \
    -O /opt/spark/jars/hadoop-aws-3.3.1.jar

WORKDIR /home/sparkuser

# Create sparkuser and set home to working directory
RUN adduser -u ${SPARK_UID} \
    --disabled-password \
    --gecos "" \
    --home "$(pwd)" \
    --no-create-home \
    sparkuser

RUN echo 'sparkuser ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/sparkuser

# Install pip requirements
RUN python -m pip install --no-cache-dir pyspark==3.3.2 delta-spark==2.2.0

RUN chown -R ${SPARK_UID}:${SPARK_GID} /opt/spark
RUN chown -R ${SPARK_UID}:${SPARK_GID} /home/sparkuser

USER ${SPARK_UID}

I am looking into if I setup the Static and dynamic provisioning correctly.
so I created a new bucket and s3a works
data.write.save("s3a://sandbox/tmp/test") # works

After creating the docker image, I am not sure what's next.
The problem is no free volumes left for {"collection":"deltalake","replication":{"node":1},"ttl":{"Count":0,"Unit":0},"disk":"ssd"}. Need to have volumes matching the requirement of replication 001 and disk is ssd.

Looks like the issue is because the client needs to implement https://github.com/delta-io/delta/blob/master/storage/src/main/java/io/delta/storage/LocalLogStore.java for it to be compatible as a file system that delta can write to.
This is more of a feature request now than a bug.

@chrislusf is this something the project would still be interested in?

Yes. Do you want to help? Maybe start with a unit test.

Sure! What's the best channel of communication for questions?


New Data replacing current data instead of extend it and LoadMore function only run once

Container:
import React, { Component } from 'react';
import { connect } from 'react-redux';
import { actions, getBrands } from '../reducer';
import Infinite from 'react-infinite';
import InfiniteScroll from 'redux-infinite-scroll';
import SearchBox from '../components/SearchBox';
import CardList from '../components/CardList';

const { fetchBrands } = actions;

class BrandList extends Component {

    componentDidMount() {
        this.props.fetchBrands({ page: 1 });
    }

    renderList() {
        const brands = this.props.brands;
        return brands.map((brand) => {
            return (
                <CardList key={brand.id} name={brand.name} avatar={brand.avatar.thumbnail} follower={brand.follows_count} />
            );
        });

    }

    toggle() {
        return this.props.isFetching;
    }

    loadMore() {
        const {lastPage, currentPage} = this.props;
        const nextPage = currentPage ? parseInt(currentPage) + 1 : 1;
        if(currentPage && currentPage <= lastPage){
            this.props.fetchBrands({page: nextPage});
        }
    }

    render() {
        return (

                <SearchBox />

                    <InfiniteScroll
                        items={this.renderList()}
                        loadMore={this.loadMore.bind(this)}
                        />

        );
    }
}

function mapStateToProps(state) {
    return {
        brands: getBrands(state),
        isFetching: state.brand.isFetching,
        currentPage: state.brand.currentPage,
        lastPage: state.brand.lastPage
    };
}

export default connect(mapStateToProps, { fetchBrands })(BrandList);

Reducer:
import axios from 'axios';
// Define Types
export const types = {
    // brand list
    FETCH_BRANDS: 'fetch_brands',
    FETCH_BRANDS_SUCCESS: 'fetch_brands_success',
    FETCH_BRANDS_ERROR: 'fetch_brands_failure',
    FETCH_BRAND: 'fetch_brand',
    FETCH_BRAND_SUCCESS: 'fetch_brand_success',
    FETCH_BRAND_ERROR: 'fetch_brand_failure',
};

const { FETCH_BRANDS, FETCH_BRANDS_SUCCESS, FETCH_BRANDS_ERROR } = types;

// Define Reducer
export const INITIAL_STATE = { brands: [], brand: {}, isFetching: false, error: null, currentPage: 1 };

export default function (state = INITIAL_STATE, action) {
    switch (action.type) {
        case FETCH_BRANDS:
            return { ...state, isFetching: true };
        case FETCH_BRANDS_SUCCESS:
            return { ...state, brands: action.payload.brands.data, currentPage: action.payload.brands.current_page, lastPage: action.payload.brands.last_page };
        case FETCH_BRANDS_ERROR:
            return { ...state, error: action.payload };
        default:
            return state;
    }
}

// Define Actions
export const actions = {
    fetchBrands: ({page, count = 15}) => {
        return (dispatch) => {
            dispatch({ type: FETCH_BRANDS });
            axios.get(`brands?page=${page}&count=${count}`)
                .then((response) => {
                    const {data} = response;
                    if (data.code == 200) {
                        dispatch({ type: FETCH_BRANDS_SUCCESS, payload: data });
                    }
                });
        };
    }
};

// SELECTOR
export const getBrands = (state) => state.brand.brands;

I inspect element it run next api (page 2) but it not extend current list, it replace it instead.

loadmore function only run once. it should run 10 times.

Any solution to make it scroll? Or do I miss something on my code?

The ReduxInfiniteScroll page doesn't alter or save any data that is passed to it, you need to properly manage that yourself:

case FETCH_BRANDS_SUCCESS:
            return { ...state, brands: brands.concat(action.payload.brands.data), currentPage: action.payload.brands.current_page, lastPage: action.payload.brands.last_page };

Try that and then let me know what errors you are getting.   You can also reference this page: http://realscout.github.io/redux-infinite-scroll/ and this code: https://github.com/RealScout/redux-infinite-scroll/blob/gh-pages/main.jsx

yes It works.
How about number 2?
First time page is load, it run 2 API instead of 1. and after I scroll to very bottom it won't load anymore.

Have you looked at this? https://github.com/RealScout/redux-infinite-scroll#important

If you are using an element as the scrollable component, rather than the window, you MUST pass a fixed height to the containerHeight prop (many issues will be fixed by following this step).

If your element is the one that should listen to the scroll, then you must pass a containerHeight value:
<InfiniteScroll
                        items={this.renderList()}
                        loadMore={this.loadMore.bind(this)}
                        containerHeight={200}
                        />

If your element isn't scrollable, and you want to listen to the scrolling of the window, then you need to set elementIsScrollable to false:
<InfiniteScroll
                        items={this.renderList()}
                        loadMore={this.loadMore.bind(this)}
                        elementIsScrollable={false}
                        />

@dcurletti I've update my code usingelementIsScrollable={false}  is still the same

    loadMore() {
        console.warn('test')
        const {lastPage, currentPage} = this.props;
        const nextPage = currentPage ? parseInt(currentPage) + 1 : 1;
        if(currentPage && currentPage <= lastPage){
            this.props.fetchBrands({page: nextPage});
        }
    }

Add that your loadMore function and then take a screenshot of your console after you scroll the page.

Here is the console.warn

ok do this:

export const INITIAL_STATE = { brands: [], brand: {}, isFetching: false, error: null, currentPage: 1, hasMore: true };

case FETCH_BRANDS_SUCCESS:
            const hasMore = action.payload.brands.current_page && action.payload.brands.current_page < action.payload.brands.last_page;
            return { ...state, hasMore: hasMore, brands: state.brands.concat(action.payload.brands.data), currentPage: action.payload.brands.current_page, lastPage: action.payload.brands.last_page };

function mapStateToProps(state) {
    return {
        hasMore: state.brand.hasMore,
        brands: getBrands(state),
        isFetching: state.brand.isFetching,
        currentPage: state.brand.currentPage,
        lastPage: state.brand.lastPage
    };
}

    loadMore() {
        const {lastPage, currentPage} = this.props;
        const nextPage = currentPage ? parseInt(currentPage) + 1 : 1;
        this.props.fetchBrands({page: nextPage});
    }

<InfiniteScroll
                        items={this.renderList()}
                        loadMore={this.loadMore.bind(this)}
                        elementIsScrollable={false}
                        hasMore={this.props.hasMore}
                        />

Looks like it should work, but at first load it always run page 1 and page 2 together and make page 2 become error (react error because of same key). I've tried set the threshold but no luck.

<InfiniteScroll
                        items={this.renderList()}
                        loadMore={this.loadMore.bind(this)}
                        elementIsScrollable={false}
                        hasMore={this.props.hasMore}
                        isLoadingMore={this.props.isFetching}
                        />

case FETCH_BRANDS_SUCCESS:
            const hasMore = action.payload.brands.current_page && action.payload.brands.current_page < action.payload.brands.last_page;
            return { ...state, isFetching: false, hasMore: hasMore, brands: state.brands.concat(action.payload.brands.data), currentPage: action.payload.brands.current_page, lastPage: action.payload.brands.last_page };

Thanks a lot for your help.
Right now I still try to find out why every time I load the page, it request all pages together without scroll anything.
But you help a lot!. Thanks.

So after you added the 'isLoadingMore' you are now getting all the pages, as opposed to just the first two?


Release v231

To pick up:

#1437
#1439

GUS-W-12346556.
GUS-W-13011106.
GUS-W-13013203.
Changelog entry
Title
Python updated setuptools and wheel
Body
The packaging tools used during the build of Python apps have been updated as follows:

setuptools updated from 67.5.0 to 67.6.1 (changelog)
wheel updated from 0.38.4 to 0.40.0 (changelog)

Of note, setuptools v66+ now rejects package versions that do not adhere to PEP 440 and PEP 508. If the build of your application now fails due to this, check whether there are newer versions of the affected package available that includes a fix, and if not, report the issue to the maintainers of that package.
In addition, setuptools v64+ has improved the way package imports and isolation works for projects installed in editable mode (when -e or --editable is used in the requirements file). However, in rare cases these improvements can cause previously working project layouts to fail with import errors. If your application uses editable mode and now encounters import errors, check setuptools' list of editable mode limitations and either adjust the project directory layout or switch away from using editable mode.
If you need to temporarily switch back to the previous setuptools and wheel versions until issues can be fixed, then pin your application's Python buildpack version to the previous release. To do this, use a buildpack URL of https://github.com/heroku/heroku-buildpack-python.git#v230 . Make sure to return to the recommended heroku/python buildpack URL/alias once your app is compatible with the new setuptools version. For more information, see setting a buildpack on an application, or if your app uses multiple buildpacks, see the steps here.

$ make publish
Deploy as version: v231 [y/n]? y

Tagging commit adff223b8d03acafc6595b8a93c367d1e0e452ed with v231...
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/heroku/heroku-buildpack-python
 * [new tag]         v231 -> v231

Publishing to the buildpack registry...
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful

 Version Released At              Status
 ─────── ──────────────────────── ─────────
 231     2023-04-12T07:14:08.150Z published


Snapshot version details should be in version instead of release

What happened? What is the problem?
Got hit by this in fmf because the downstream release is >1 which affects the ordering when packit overrides the version + release from %autorelease to 1.<snapshot_details>, making them lower than downstream.
Instead the versioning guideline should be used and place the snapshot details in the version so that <version>^<snapshot_details> always orders after.
What did you expect to happen?
Packit upstream version is always ordered after downstream.
There is the edgecase where downstream also uses snapshots and can create downstream snapshot after an upstream build, but this is both temporary and highly unlikely since upstream would be working together with downstream when having packit integration.
The other case is if you build PR builds in a single project, but that would also not be supported with the current release overwriting, and it breaks in various other ways.
Other than those, I don't think there are other workflows that would break.
Example URL(s)
https://github.com/teemtee/fmf/pull/265#issuecomment-2514537255
Steps to reproduce
1.
2.
3.

Workaround

[ ] There is an existing workaround that can be used until this issue is fixed.

Participation

[X] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Hi, it should be possible to work around this issue by using the get-current-version action:
https://packit.dev/docs/configuration/actions


Mobile responsiveness

Fixed: Bug raised for responsiveness on a mobile screen
https://vaultbank.atlassian.net/browse/VL-2729

LGTM


smpl data correction

I note in zju_mocap.py, you correct the smpl data like this.
        # Use camera extrinsic to rotate the simple to each camera coordinate frame!

        # the R,t is used like this, stored in cam
        # i.e. the T stored in cam is actually p_c = T_cw @ p_w
        # def get_rays(H, W, K, R, T):
        #     # calculate the camera origin
        #     rays_o = -np.dot(R.T, T).ravel()
        #     # calculate the world coodinates of pixels
        #     i, j = np.meshgrid(
        #         np.arange(W, dtype=np.float32), np.arange(H, dtype=np.float32), indexing="xy"
        #     )
        #     xy1 = np.stack([i, j, np.ones_like(i)], axis=2)
        #     pixel_camera = np.dot(xy1, np.linalg.inv(K).T)
        #     pixel_world = np.dot(pixel_camera - T.ravel(), R)
        #     # calculate the ray direction
        #     rays_d = pixel_world - rays_o[None, None]
        #     rays_d = rays_d / np.linalg.norm(rays_d, axis=2, keepdims=True)
        #     rays_o = np.broadcast_to(rays_o, rays_d.shape)
        #     return rays_o, rays_d

        # ! the cams R is in a very low precision, have use SVD to project back to SO(3)
        for cid in range(num_cams):
            _R = self.cams["R"][cid]
            u, s, vh = np.linalg.svd(_R)
            new_R = u @ vh
            self.cams["R"][cid] = new_R

        # this is copied
        smpl_layer = SMPLLayer(osp.join(osp.dirname(__file__), "../data/smpl-meta/SMPL_NEUTRAL.pkl"))

        # * Load smpl to camera frame
        self.smpl_theta_list, self.smpl_trans_list, smpl_beta_list = [], [], []
        self.meta = []
        for img_fn in self.ims:
            cam_ind = int(img_fn.split("/")[-2])
            frame_idx = int(img_fn.split("/")[-1].split(".")[0])
            self.meta.append({"cam_ind": cam_ind, "frame_idx": frame_idx})
            smpl_fn = osp.join(root, "smpl_params", f"{frame_idx}.npy")
            smpl_data = np.load(smpl_fn, allow_pickle=True).item()
            T_cw = np.eye(4)
            T_cw[:3, :3], T_cw[:3, 3] = (
                np.array(self.cams["R"][cam_ind]),
                np.array(self.cams["T"][cam_ind]).squeeze(-1) / 1000.0,
            )

            smpl_theta = smpl_data["poses"].reshape((24, 3))
            assert np.allclose(smpl_theta[0], 0)
            smpl_rot, smpl_trans = smpl_data["Rh"][0], smpl_data["Th"]
            smpl_R = axangle2mat(
                smpl_rot / (np.linalg.norm(smpl_rot) + 1e-6), np.linalg.norm(smpl_rot)
            )

            T_wh = np.eye(4)
            T_wh[:3, :3], T_wh[:3, 3] = smpl_R.copy(), smpl_trans.squeeze(0).copy()

            T_ch = T_cw.astype(np.float64) @ T_wh.astype(np.float64)

            smpl_global_rot_d, smpl_global_rot_a = mat2axangle(T_ch[:3, :3])
            smpl_global_rot = smpl_global_rot_d * smpl_global_rot_a
            smpl_trans = T_ch[:3, 3]  # 3
            smpl_theta[0] = smpl_global_rot
            beta = smpl_data["shapes"][0][:10]

            # ! Because SMPL global rot is rot around joint-0, have to correct this in the global translation!!
            _pose = axis_angle_to_matrix(torch.from_numpy(smpl_theta)[None])
            so = smpl_layer(
                torch.from_numpy(beta)[None],
                body_pose=_pose[:, 1:],
            )
            j0 = (so.joints[0, 0]).numpy()
            t_correction = (_pose[0, 0].numpy() - np.eye(3)) @ j0
            smpl_trans = smpl_trans + t_correction

            self.smpl_theta_list.append(smpl_theta)
            smpl_beta_list.append(beta)
            self.smpl_trans_list.append(smpl_trans)

Do this correction has any reference? Since during the correction, camera pose is used, it means one frame has different smpl data in different views. It feels quiet strange...

Thanks for your interest. I'm not exactly sure which "correction" you are referring to, but I guess most likely you are saying why the SMPL poses are different in viewpoints: t_correction = (_pose[0, 0].numpy() - np.eye(3)) @ j0. This is usually a tricky practical problem when rotating the SMPL. When rotating a SMPL, one can add some axis angel to the first joint rotation, but the SMPL will rotate around its first joint, not the object space origin, so the translation needs to be updated to mitigate this different rotation origin. Here j0 = (so.joints[0, 0]).numpy() is the first joint position in the object space, which the SMPL is rotated around, and it's used to correct the translation.


Set tunnel.Host after the tunnel is running

Fixes using with Host being empty after Create returns

👍 it works


"Updated Alpine image version to 3:20 to remove security vuln"

Updated Alpine image version to 3:20 to remove security vuln

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Implementation Generation Script Tool

To generate a script for GStreamer CLI
Implementation generation script tool w/ python
discussion for preparation
discussion for test environment

Update script for support audio