Travis CI: report to coveralls failed

Copy of that - https://travis-ci.org/Markette/Gopay/jobs/59558874
Load coverage clover log:

/home/travis/build/Markette/Gopay/coverage.xml
Found 17 source files:
0.00% Api/CountryCode.php
20.00% Api/GopayConfig.php
17.55% Api/GopayHelper.php
0.00% Api/GopayHttp.php
0.24% Api/GopaySoap.php
0.00% Api/PaymentMethodElement.php
0.00% Api/PaymentMethods.php
94.12% Extension.php
100.00% GopayException.php
100.00% GopayFatalException.php
100.00% GopayHolder.php
100.00% IPaymentButton.php
100.00% ImagePaymentButton.php
100.00% Payment.php
100.00% PaymentButton.php
100.00% ReturnedPayment.php
81.15% Service.php
Coverage:  31.54% (299/948)
Collect git info
Read environment variables
Dump uploading json file: /home/travis/build/Markette/Gopay/coverage.json
PHP Catchable fatal error:  Method Contrib\Bundle\CoverallsV1Bundle\Entity\JsonFile::__toString() must return a string value in /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Api/Jobs.php on line 107
PHP Stack trace:
PHP   1. {main}() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/composer/bin/coveralls:0
PHP   2. Symfony\Component\Console\Application->run() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/composer/bin/coveralls:34
PHP   3. Symfony\Component\Console\Application->doRun() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Application.php:126
PHP   4. Symfony\Component\Console\Application->doRunCommand() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Application.php:195
PHP   5. Symfony\Component\Console\Command\Command->run() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Application.php:874
PHP   6. Contrib\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->execute() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:257
PHP   7. Contrib\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->runApi() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:103
PHP   8. Contrib\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->dumpJsonFile() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:152
PHP   9. Contrib\Bundle\CoverallsV1Bundle\Api\Jobs->dumpJsonFile() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:263
PHP  10. file_put_contents() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Api/Jobs.php:107
Catchable fatal error: Method Contrib\Bundle\CoverallsV1Bundle\Entity\JsonFile::__toString() must return a string value in /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Api/Jobs.php on line 107
Call Stack:
0.0002     241440   1. {main}() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/composer/bin/coveralls:0
0.0187    2049568   2. Symfony\Component\Console\Application->run() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/composer/bin/coveralls:34
0.0232    2451032   3. Symfony\Component\Console\Application->doRun() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Application.php:126
0.0234    2451928   4. Symfony\Component\Console\Application->doRunCommand() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Application.php:195
0.0234    2452352   5. Symfony\Component\Console\Command\Command->run() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Application.php:874
0.0238    2455600   6. Contrib\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->execute() /home/travis/build/Markette/Gopay/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:257
0.0378    3695016   7. Contrib\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->runApi() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:103
0.0935    5127664   8. Contrib\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->dumpJsonFile() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:152
0.0936    5127768   9. Contrib\Bundle\CoverallsV1Bundle\Api\Jobs->dumpJsonFile() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:263
0.0936    5127816  10. file_put_contents() /home/travis/build/Markette/Gopay/vendor/satooshi/php-coveralls/src/Contrib/Bundle/CoverallsV1Bundle/Api/Jobs.php:107
Done. Your build exited with 0.

@haltuf @hranicka Do you know where problem is?

The problems started with build #4, which is strange - I don't see many relevant changes: https://github.com/Markette/Gopay/compare/ec961e83f9a9...71dc0070e0ba

I'm examining more the log files between Build 3 (when it worked) and Build 4 (when it stopped working). I found another difference, in failed build, there are following messages in the part, when satooshi/php-coveralls are installed:
Downloading: connection...    Failed to download psr/log from dist: Could not authenticate against github.com Now trying to download from source
This might be solved (probably?) using this: http://help.pagodabox.com/customer/portal/questions/6193893-failed-to-download-doctrine-common-from-dist-could-not-authenticate-against-github-com/
(last post)
But it could be the cause of the problems only in the case, if dist differs from source (I'm new in this stuff, don't know if it's possible at all)
Please also note, that in your Pull request #31, you should change the .coveralls.yml file (src_dir) to reflect the new directory structure.

@f3l1x Ok, all my hypothesis proved to be nonsense. The satooshi/php-coveralls used for code coverage report generating and send stopped working in PHP 5.5 & 5.6 for no obvious reason (I can't debug it directly in Travis, probably even impossible, and don't have 5.5+ on my localhost).
It works in 5.4, though.
I guess after some change, coverage.xml generated by Nette\Tester contains something, that satooshi simply cannot handle and fails. It's still strange, though, since most people I saw, use coveralls on PHP5.6 without problems...

@f3l1x Allright, I digged even deeper and found the real cause of the problem: GopayHolder.php is not in UTF-8. This is the reason why JsonFile::__toString() returns FALSE instead of json format in PHP5.5+ (json_encode returns error code 5 with message "Malformed UTF-8 characters, possibly incorrectly encoded")
After fixing the encoding of the file, my PR #33 is not neccessary any more.

Oh, thanks for that. PhpStorm probably changed my encoding. Great!


Horizontal scroll bar appears at bottom when casting

May cause TV burnin. Possibly due to receiver app selecting incorrect width.
(confirmed no scroll bar when casting from YouTube app or put.io website)

I'm using the default cast receiver and just passing a stream to the video. Could it be the source video you're using? Or understand?

I suspect it is the receiver because I can cast the same video to the same Chromecast connected to the same TV, and when I use the app I see the scroll bar, but when I cast from the put.io website I do not. I'm not sure if put.io is using the default receiver as well. I've sent Chromecast feedback to see if it's an issue on the Google side.

Could you take a picture of the scroll bar?
On Wed, Jan 20, 2016 at 11:33 PM Vivek Sekhar<EMAIL_ADDRESS>wrote:

I suspect it is the receiver because I can cast the same video to the same
Chromecast connected to the same TV, and when I use the app I see the
scroll bar, but when I cast from the put.io website I do not. I'm not
sure if put.io is using the default receiver as well. I've sent
Chromecast feedback to see if it's an issue on the Google side.
—
Reply to this email directly or view it on GitHub
https://github.com/DSteve595/Put.io/issues/42#issuecomment-173448729.

I'm still having this issue, do you still need a picture of the scrollbar?

same issue here, casting to a chromecast 1 from android app I get a grey scroll bar on bottom of screen, not present when chromecasting from put.io website

Really weird. I'm looking into it.

I've found that if the filename I am casting from the app is really long, the scroll bar appears. If I rename the file via the app to something shorter, I can cast it without scroll bars appearing. The filename element in the receiver page might not be fixed width.

Well now I feel dumb.
Easy fix, I'll have it out soon.
On Sat, Apr 23, 2016, 7:28 PM Vivek Sekhar<EMAIL_ADDRESS>wrote:

I've found that if the filename I am casting from the app is really long,
the scroll bar appears. If I rename the file via the app to something
shorter, I can cast it without scroll bars appearing. The filename element
in the receiver page might not be fixed width.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/DSteve595/Put.io/issues/42#issuecomment-213852731

Pushed.


[4305] Set UUID fields when importing from Apply

Context
https://trello.com/c/3ccIySaQ/4305-m-set-uuid-fields-when-importing-from-apply
Changes proposed in this pull request

DB migration to add uk_degree_uuid, subject_uuid and grade_uuid to degrees table
Update Degrees::MapFromApply to use DfE::ReferenceData
Fix various specs that broke after using DfE::ReferenceData. DfE::ReferenceData is slightly different than the DTTP codesets data. For example, mames are sentence case, not titlecase.
Add new database fields to analytics.yml

Important business

[x] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[x] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 [M] Set UUID fields when importing from Apply


Problems calling 'to_base_units' within metpy.calc

I just downloaded MetPy today and intended to work through the examples to see how the code works. I used pip to install, so I have metpy-0.3.0, and pint-0.7.2. When I run, for example, the first cell in the Simple Sounding example notebook, I get an error: 'Unit' object has no attribute 'to_base_units'. Code:
import matplotlib.pyplot as plt
import numpy as np

from metpy.cbook import get_test_data
from metpy.calc import get_wind_components
from metpy.calc import tools
from metpy.plots import SkewT

and error message:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-4-9a0e9b5d96dc> in <module>()
      3
      4 from metpy.cbook import get_test_data
----> 5 from metpy.calc import get_wind_components
      6 from metpy.calc import tools
      7 from metpy.plots import SkewT

/Users/watkdani/anaconda/lib/python3.4/site-packages/metpy/calc/__init__.py in <module>()
      6
      7 from .basic import *  # noqa
----> 8 from .kinematics import *  # noqa
      9 from .thermo import *  # noqa
     10 from . import turbulence  # noqa

/Users/watkdani/anaconda/lib/python3.4/site-packages/metpy/calc/kinematics.py in <module>()
      6 import numpy as np
      7 from ..package_tools import Exporter
----> 8 from ..constants import g
      9 from ..units import atleast_2d, concatenate, units
     10

/Users/watkdani/anaconda/lib/python3.4/site-packages/metpy/constants.py in <module>()
     80 with exporter:
     81     # Earth
---> 82     earth_gravity = g = units.gravity.to_base_units()
     83     Re = earth_avg_radius = 6.37e6 * units.m
     84     omega = earth_avg_angular_vel = 2 * units.pi / units.day

AttributeError: 'Unit' object has no attribute 'to_base_units'

pint 0.7 broke some things in MetPy, which I've fixed in master. The easiest way to get you back to working is to install pint == 0.6. Did you install using pip?

Yeah, I used pip. Switching to pint 0.6 did the trick. Thanks for the quick response!

On May 12, 2016, at 9:55 AM, Ryan May<EMAIL_ADDRESS>wrote:
pint 0.7 broke some things in MetPy, which I've fixed in master. The easiest way to get you back to working is to install pint == 0.6. Did you install using pip?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/metpy/MetPy/issues/144#issuecomment-218818786

No problem. Let me know if you have any more problems.


brew-cask: upgrade to 0.60.1

Over at Homebrew we've accidentally caused an edge-case problem for some Caskroom users. We recently merged https://github.com/Homebrew/homebrew/commit/915ac06d which is much stricter on empty installations, failing during install rather than just shouting about it in the audit.
We'd prefer not to revert the change there because it's quite a positive change that's much more obvious about installation problems, given installations shouldn't be empty. There's also the likelihood that if we revert, wait 3 months to add the check back, someone out there will wait 4 months before upgrade and we'll run into this again.
However, this causes some issues with Cask because when Mike rewrote the formula he left def install an empty hole, which was fine at the time. Anyone who hasn't updated between December 9th 2015 and January 9th 2016 will now run into a fatal error on upgrading the Cask formula, as seen in: https://github.com/Homebrew/homebrew/issues/47929
I was wondering if the Cask would be kind enough to tag one very last bug fix release, or even retag the existing tag with a similar fix to this. You may want to do this yourself rather than using this PR; this was an easy way to both explain the problem and propose a fix without sticking a diff blob in the middle of the text.
Obviously, if tested by Travis here this build will likely fail because there is no 0.60.1 tag. Apologies for the accidental mess here. It's one of those things we'll probably get better at if/when we can bring the two projects closer together and do more unified testing.
CC @mikemcquaid for thoughts.

:+1: from me.

Pinging @caskroom/maintainers

@jawshooah You commented (and I agree) about having a round number for the last release (0.60.0) and I concur it makes sense. Shall we make this 0.70.0?

@vitorgalvao Up to you but given this is just a patch around a Homebrew bug in the interests of semver I'd leave it as a .1.

I don't care much about the version tag; not like we've been sticking to semver anyway (plenty of breaking changes in the project's history, not a single major version bump). @vitorgalvao, any objection to me pulling this down, tagging and pushing?

Let me know if you want me to make any changes.

@vitorgalvao, any objection to me pulling this down, tagging and pushing?

No objection at all.

Other than the suggested wording changes, it LGTM

Made some wording tweaks.

I'm going to keep the wording the same between install and caveats if it's all the same to you guys.

Feel free to make whatever changes you want to to anything I've done here.

Closed in b4c92f3658d47712aa6114fb29be50a763cf78ee.

Thanks!


Support extend a custom auth type

What changes are proposed in this pull request?
Support extend a custom auth type.
Why are the changes needed?
With this PR, we can use custom auth type for a new auth implementation, otherwise, we have to add a new auth type to the AuthType enum and proto.
Does this PR introduce any user facing changes?
alluxio.security.authentication.custom.provider.class=
alluxio.security.authentication.custom.sasl.client.handler.class=
alluxio.security.authentication.custom.sasl.server.handler.class=

This change breaks the existing custom authentication support.
Did you check below property key already and see if it serves whatever you're planning to achieve with custom sasl-handlers?
public static final PropertyKey SECURITY_AUTHENTICATION_CUSTOM_PROVIDER_CLASS =
new Builder(Name.SECURITY_AUTHENTICATION_CUSTOM_PROVIDER_CLASS)
.setDescription("The class to provide customized authentication implementation, "
+ "when alluxio.security.authentication.type is set to CUSTOM. It must "
+ "implement the interface "
+ "'alluxio.security.authentication.AuthenticationProvider'.")
.setConsistencyCheckLevel(ConsistencyCheckLevel.WARN)
.setScope(Scope.ALL)
.build();

@ggezer Thanks for your reply.
alluxio.security.authentication.custom.provider.class=
alluxio.security.authentication.custom.sasl.client.handler.class=
alluxio.security.authentication.custom.sasl.server.handler.class=

The three key about custom auth type here, the first one is the existing custom provider, but we have two implementations  else, one extended from SaslServerHandler, the other extended from SaslClientHandlerPlain, so that we have to create this PR to extend custom auth type to let our implementation works.

@yyongycy Could you take a look at this PR? Thanks!

@yyongycy Thanks for your suggestion, I push a new commit, PTAL.

@jiacheliu3 Thanks for your review, accepted your suggestion, and push a new extra commit to solve the other naming issue.

@jiacheliu3 Thanks for reminding me, I push a new commit to address your comment. PTAL


Added aliases file for PowerShell

I added an arg for the generate_aliases.py script to generate a PowerShell file:
./generate_aliases.py --output powershell | Out-File -Encoding ascii kubectl_aliases.ps1
# or
./generate_aliases.py --o ps1 | Out-File -Encoding ascii kubectl_aliases.ps1

A generated kubectl_aliases.ps1 was added and the README file was updated.

@shanoor thanks for your work.
this complicates the readme 2x for 90% of the users.
Also I won't be able to maintain these powershell aliases well.
Do you mind forking my project, and calling your fork kubectl-aliases-powershell and then maintaining powershell stuff there?
I'd be happy to link to your fork from my repo for PS users.

I don't mind at all, the fork is up: https://github.com/shanoor/kubectl-aliases-powershell 😃
I'm closing this PR.

Great! I linked to it from README.


Triage finschia-sdk#138

The subject of the triage:

Finschia/finschia-sdk#138

We don't need this PR, because the config would have the appropriate value (cointype 438) in v0.50.2 based Finschia/finschia-sdk.


What do you think about using react-bootstrap?

Is there any reason you might not want to integrate this into your boilerplate?
I am using this boilerplate for my portfolio website now - it is really cool. Would you like me to commit a version where bootstrap is replaced with react-bootstrap?

In my opinion it shouldn't be added to this boilerplate, this should be just a simple starting point.
Altho there is a bootstrap included in the boilerplate, it's not exactly the main point. Upto @anorudes.
If you wish to make a pull request, please do it against development branch

+1 for not including it. This is just react + redux boilerplate.
don't become react-redux-universal


Send a dummy input to clear the read block

fixed #452.
When switching nonBlocking, a dummy input is sent to process read
and clear the read block.

There may be other ways to solve this problem. This is an idea.

This turns out not to be necessary.  Please see my "tty" branch for a likely solution.

See #459 for my approach that I think sorts this.

I've merged #459 into master which addresses this problem, and makes this PR obsolete.


warning dialog header has an orange background color

Should it be orange text color instead?

@nathanwomack

yes, warning should be orange and error should be red.


Reduce number of caching layers

This follows Docker best practices.
See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#run

Thx @sliverc 👍


update build.zig to work with the latest zig master

This PR changes to use std.ChildProcess.run instead of the Build type's exec function.
Sovles:
build.zig:25:30: error: no field or member function named 'exec' in 'Build'
    const git_commit_hash = b.exec(&.{"git", "rev-parse", "HEAD"});

Also changed var's to const's as the new version of zig errors on variables that are not being mutated.
Solves:
src\main.zig:317:13: note: consider using 'const'
src\main.zig:416:13: error: local variable is never mutated
        var index = lowerBound(Link, chain_id, links, {}, S.first);

Hi, thanks for the PR and for checking out Habu!
Unfortunately, Habu targets stable Zig releases only to avoid churn, so I'm afraid I can't merge this. If you want to build with master you will have to maintain your own branch/fork, hope that is OK 🙏


Test CI

xref https://github.com/dask/dask-ml/pull/944

Okay, so CI is running here. It looks like https://github.com/dask/dask-ml/pull/944 might have just been a blip on the GitHub side of things.

@jrbourbeau do you still need this PR or can we close it?

Can definitely close. Thanks for following-up


Update cats-effect, cats-effect-laws to 3.2.6

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 3.2.4 to 3.2.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: test-library-update, semver-patch

Superseded by #231.


Make dynamic scheduler scaling more robust and configurable

Prior to this commit, dynamic scheduler scaling was not quite as
robust as we might like. When it came to waking sleeping threads,
the logic would send multiple wake signals in the hope that one
of them would work successfully and wake any sleeping thread that
might still be asleep. It was possible that even with sending
multiple signals, they could all be missed resulting in a thread
staying suspended when it should be awake.
This commit changes the logic to add a "check variable" that is
updated by threads after they wake up. This "check variable"
(active_scheduler_count_check) is a mirror of the current
active_scheduler_count and is used to confirm that a sleeping
thread has successfully woken up. This commit also changes the
logic to ensure that when threads are being woken up, they are
only sent a single signal (to minimize unnecessary work). If that
signal is missed, then scheduler thread 0 would notice that
active_scheduler_count != active_scheduler_count_check and send
another signal until the thread wakes up and updates the check
variable. This should ensure that it is not possible to have a
hanging thread due to missed signals. Overall, these changes
should make dynamic scheduler scaling more robust, including
allowing for scheduler thread 0 to also suspend. (Scheduler
thread 0 suspension is experimental because @slfritchie ran into
an issue related to programs hanging when using network IO and
suspending scheduler thread 0 a few months ago. This commit
should in theory resolve this due to the "check variable" but I
haven't had an opportunity to test and confirm whether it
actually does so or not.)
This commit also adds in a new command line option for dynamic
configutation of the threshold after which a thread is allowed to
suspend (and also separates it from the scheduler block threshold.
This new option is called --ponysuspendthreshold. This option
is needed because the current suspend threshold (about 1 ms) is
very aggresive and @slfritchie noted that scheduler threads
suspend and don't wake up even under high network load. This
option allows for the threshold to be increased (or decreased)
on a per application run time basis. Additionally, it likely
makes sense to change the default to be something more
"appropriate and balanced" based on some sort of fancy
heuristics/tests done with different values for the threshold.

@sylvanc I am (based on my limited testing). But then again, I tend to be overconfident to a fault. It's probably better to have someone not-me do some sort of check to ensure I didn't break something without realizing it.
Also... rebased to fix merge conflict.


[BUG] Line chart does not animate to new values when all are replaced

I am using a chartjs line chart showing time data where I want to update with new values from an ajax call.
I have time on the X axis (1 days on 15 minutes intervals) , and just numbers for the Y axis.
However, if I replace the data, and then call update(), I get no animation. Example can be seen at
http://codepen.io/peterjc/pen/YVKyXG?editors=1111 where using a timer to emulate an incoming ajax call.
Expected Behavior
Would like the line to animate to the new values, perhaps just adding those extra (the new data first few entries are the same as the original data)
Current Behavior
The graph redraws with no animation
Possible Solution
Steps to Reproduce (for bugs)
Can reproduce as shown at http://codepen.io/peterjc/pen/YVKyXG?editors=1111
Context
Want to show a graph that sometimes gradually has data added, but other times all data will be replaced, but would still like this to animate
Environment
Was using in an Ionic 2 project, but happens anywhere (eg in Chrome, Edge etc)

Thanks for reporting this. Currently this is a duplicate of #3952 so I'm closing in favour of the older issue.


prepare_command not converted

I'm trying to make use of https://cocoapods.org/pods/OpenSSL, but the generated build doesn't produce an artifact. Looking at the BUILD file, it seems to be missing something that corresponds to the s.prepare_command directive.

Hey @joprice  - thanks for filling this! You're right, it doesn't automatically run the prepare_command. The tradeoff is made for reproducibility and security reasons.
The current convention is to run prepare_command's via the install_script attribute of new_pod_repository, for example:
new_pod_repository(
  name = "OpenSSL",
  ...
  install_script = """
    # Run the `prepare_command` of OpenSSL
    VERSION=\"1.0.2j\"\nSDKVERSION=`xcrun --sdk iphoneos --show-sdk-version 2> ....

     # Generate the `BUILD` file
     __INIT_REPO__
  """
)

I took a look at the podspec and it seems like it should work. Based on the popularity of this pod, it could be a good fit for a test case example.
As a follow up to this issue, I think we should add a note about prepare_command's in the README in addition to install_script usage.

This need...Some adoption. Espacially for large project.
The podspec.prepare_command may be different in different Pods. But now we have to use scripts to generate the new_pod_repository args.
Not a good pain because we already customize the PodToBuild and surrounding tools. But I think, supports prepare_command may be a better idea.


formally release 1.0

is anyone waiting for some acceptance?
what should be involved?

[ ] tag release on github
[ ] publish docker instances?
[ ] publish widget at some repo?

@cedricdcc for tagging the release, please note that multiple repos are involved
I did a quick scan to identify the 1.0 commits for each of them:

https://github.com/vlizBE/vocabserver-frontend/commit/53ba0ff7015b7a51d5f65b3c19bdfafe5c74a442
https://github.com/vlizBE/vocabserver-app/commit/1864c4e77601d0e5620f711b3ed794376fb764e7
https://github.com/vlizBE/vocabserver-webcomponent/commit/b2c61195eb40bfcc9e309004ce87681e5293c144

please also close the "1.0 milestone" in github

Also see https://github.com/vlizBE/vocabserver-app/issues/52


[PDI-13953] Excel Input Dialog Browse XLSX

Fix a typo to allow showing Excel 2007 files

The POI and SAX_POI options are shown in the Dialog as only for Excel 2007 formatted files, whereas the JXL option is for the older Excel format.  Removing the extensions for POI/SAX_POI should help to avoid confusion, as they'll need to select the appropriate parser for the file type that is to be selected.


[UWP][Burger Menu][Full Screen] Burger menu closing animation is not smooth when in full screen

Current behavior

Expected behavior

How to reproduce it (as minimally and precisely as possible)

Launch UWP app
Put app in Full Screen
Open and then close the burger menu
Notice that burger menu closes and then icons shift up

Environment

Nuget Package:
Package Version(s):
Affected platform(s):

[ ] iOS
[ ] Android
[ ] WebAssembly
[x] UWP

Anything else we need to know?

Can not reproduce in uwp, do you have a lot of tabs open and processes, might be a context switching/process slow computer thing

I will retest with everything closed and see if I can reproduce it

I was able to reproduce on UWP after a fresh restart of my computer. Only thing that was open was Visual Studio 2019 (16.6.1)

@NicolasChampagne this issue looks to be similar to #122, I am able to reproduce the issue on my home computer but not on my remote computer


api: Fix undefined variable reference from previous commit.

Fixes travis failures.

@timabbott Without this fix, travis is broken for mypy, and so is usage of RandomExponentialBackoff.
I haven't looked into this implementation as I assume it was reviewed OK, but this LGTM as a fix.


different number same result "hashids/hashids": "^3.0",

`        $hashids = new Hashids('megas',30);
    echo $hashids->encode(215).'
';
    echo $hashids->encode(1315).'
';`

WyZxRAb9Y6aJ0waL3gBo4VzPXKlM7N
 WyZxRAb9Y6aJ0wal3gBo4VzPXKlM7N

use latest version
3.0

It does not seem like you've added the failing tests to the test suite?

I wanted you to submit a pull request with your code. This way we can see if this is actually a bug or if this is something with your environment. When you've added the failing code to this project it will automagically be processed by Travis and it will show either red or green depending on if it fails or not.

yes thank you .


Unexpected indentation level after newline with 0.50.0

With version 0.50.0, the below code now produces an error because of the lack of newline after the {:
{ size -> icon?.getBitmap(size)?.await() }

What seems odd to me is that the "correct" formatting looks like the below:
{
        size ->
    icon?.getBitmap(size)?.await()
}

This plays out the same for larger code blocks as well where the first line after the bracket is indented further over than all subsequent ones if there's a separator involved. It seems to me that if anything, we'd want to invert that indentation to something more like:
{
    size ->
        icon?.getBitmap(size)?.await()
}

This problem has the same root cause as #2106 and will be fixed via that issue.
The double indentation of parameters inside the lambda looks indeed weird at first sight. It is based on (but not identical to) the default formatting of IntelliJ IDEA.
Given the functional literal below (note that it contains multiple parameters on separate lines):
val foo = { a,
        b,
        c ->
    doSomething()
}

It is formatted by IntelliJ IDEA formatter as:
val foo = { a,
            b,
            c ->
    doSomething()
}

Analog to formatting of functions having parameters on separate lines, ktlint formats this as:
val foo = {
        a,
        b,
        c ->
    doSomething()
}

The format above should only be applied when having a function literal with parameters on separate lines. As result of the bug in #2101, your parameter list was wrapped and as of that changed into a multiline parameter list. As a result of that, the indentation of a multiline parameter list was applied. With fix of #2106 you original code sample will be kept unchanged.

Thanks for the update, I appreciate the response!


can't search with rg --no-ignore

I would like a way to search a directory or a project through ripgrep using the option --no-ignore.
For example +default/search-from-cwd use +ivy/project-search-from-cwd which search all files when passing the universal argument but the doom's wrapper never pass the argument forward instead it use it to specify a directory to search from. Maybe there should be different functions for searching in the current directory/project and another one where you need to specify the directory/project first.

By passing the prefix argument to SPC / d and SPC / p you will be prompted for the directory/project to search:

SPC u SPC / d will let you select a directory to search from
SPC u SPC / p will prompt you for what known project to search

As for the your --no-ignore issue, simply start your search with --no-ignore -- <search terms>. Or, a shorter version: -u -- <search terms>

Oh, nice! Writing the parameters in the search field is good enough for me. Thanks again.

Happy to help! As a side note: 9ffb740 adds SPC / D and SPC / P as aliases for SPC u SPC / d and SPC u SPC / p.


New feature: cities!

Summary
👋 your task, should you choose to accept it, is to add cities to Cryptozoologist.
Acceptance criteria

As a user of the Cryptozoologist gem, I can call the method Cryptozoologist.city and be provided with a string that uses the internal dictionaries (your choice which dictionaries!) to make a city name (Slothlandia, Turtleneck City, Unicornville - your choice)
As a user of the Cryptozoologist gem, I can find documentation in the README for how to use the new method
As someone curious about the Cryptozoologist gem, I can view the version bump for these changes in the CHANGELOG
As a contributor to the gem, I can run all of the tests and they pass!

Technical requirements

If you want to add a new dictionary, you can, but make sure you follow the current namespacing patterns
All new code should be tested, but I welcome in progress PRs for feedback on your code before you write tests (this is optional!)

@acgillette go for it!


NEW OTSIM900LINK STATE MACHINE!!!! + fixed garbagetest

Still needs a fix for:
char temp;
while ('A' == temp) temp = char(random() & 0xff);
which may never set temp and h=just use whatever (possibly fixed) value was in it.
Bad test!  Bad test!


Memory on GPU not cleared after transcription

Hi, I have a use case where after a script that transcribes an audio file still needs to run also after it finished the transcription process.
The question I have is why doesn't the GPU memory get fully cleared after the transcription process is over?
When I try to delete the faster-whisper model object, there seems to be about 312 MiB GPU memory still occupied but I don't know by what. There is a sample screen shot from the nvtop command and the code to replicate this behaviour. The "running" after the transcription process is imitated by the time.sleep(20) command and during those 20 seconds you can see that the GPU memory is still occupied by those 312 MiB, and gets only released when the script is fully finished.

from faster_whisper import WhisperModel
import time

def create_model(model_size) -> WhisperModel:
    """
    Instantiates a new Whisper model and returns it.
    """
    transcriber = WhisperModel(
        model_size_or_path=model_size,
        device="cuda",
        device_index=0,
        compute_type="int8",
        cpu_threads=1
    )
    return transcriber

model = create_model("medium")

segments, info = model.transcribe("english4.mp3")
for seg in segments:
    print(seg.text)

print("Finished transcribing")

del model
print("Deleted faster-whisper object")

print("Wait 20 sec")
time.sleep(20)

can you try that in a loop? i.e. repeating the experiment to see if each model instance created and deleted leaves a residue in memory and not a once-in-a-runtime issue
also try using a gpu ram clearing function such as torch.cuda.empty_cache() or anything similar to see if it solves the issue

That's likely the memory held by the cuda runtime, which iirc, cant really be freed unless the entire process is killed.
Do you notice if loading/unloading the model a few times in a row always results in the same amount of memory remaining? If so, its probably very likely the runtime.

Yes, always the same amount of memory for all models.


Confirm all packages listed in requirements.txt are needed for the project to work

Remove any packages that are not needed.

just went through it and no unnecessary ones on my end 👍


Merge Smoke test for version 1.7.0

Docs Build status updates of commit 9851dbc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

prosepy/docs-ref-conceptual/knownissues.md
:white_check_mark:Succeeded

prosepy/docs-ref-conceptual/relnotes.md
:white_check_mark:Succeeded

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


minor code improvements

Improved an instance of if/else conditions and removed usage of attr as a variable.

I shall re-open this after fixing a typo and agreeing to the Github CLA.


Java 17 unsupported, 1.3 and 1.4 only work with Java 21

Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve io.github.coordinates2country:coordinates2country:1.4.
     Required by:
         project :
      > No matching variant of io.github.coordinates2country:coordinates2country:1.4 was found. The consumer was configured to find a library for use during compile-time, compatible with Java 17, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally but:
          - Variant 'apiElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a library for use during compile-time, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'javadocElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about its elements (required them preferably in the form of class files)
          - Variant 'runtimeElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a library for use during runtime, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'sourcesElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about its elements (required them preferably in the form of class files)

Most important line here is:
Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17

Is it possible to let this library run on the Java 17 and not only Java 21?

Any chance you can switch your project to Java 21?
If not, could you try downgrading Gradle's version until it works for you?

Also, please paste here the full error (as text, not only screenshot) when you try to use 1.4 with Java 17. Thanks!

Any chance you can switch your project to Java 21?
If not, could you try downgrading Gradle's version until it works for you?

No, it is not possible to switch project to Java 21, that is why I am hoping the library would support Java 17 etc.
Gradle version, tried 8.0, 8.1, 8.2, 8.3, 8.4 and 8.5, not working.

Also, please paste here the full error (as text, not only screenshot) when you try to use 1.4 with Java 17. Thanks!

Execution failed for task ':compileJava'.

Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve io.github.coordinates2country:coordinates2country:1.4.
     Required by:
         project :
      > No matching variant of io.github.coordinates2country:coordinates2country:1.4 was found. The consumer was configured to find a library for use during compile-time, compatible with Java 17, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally but:
          - Variant 'apiElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a library for use during compile-time, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'javadocElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about its elements (required them preferably in the form of class files)
          - Variant 'runtimeElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a library for use during runtime, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'sourcesElements' capability io.github.coordinates2country:coordinates2country:1.4 declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about its elements (required them preferably in the form of class files)

Could you please try with 1.5?
I am able to build the sample program that calls it, with Java 17 :-)
coordinates2country-sample nicolasraoul$ JAVA_HOME=`/usr/libexec/java_home -v 17.0.9` ./gradlew build

BUILD SUCCESSFUL in 592ms

I will try! Thanks.
On Fri, Dec 15, 2023, 14:23 Nicolas Raoul @.***> wrote:

Could you please try with 1.5?
I am able to build the sample program that calls it, with Java 17 :-)
coordinates2country-sample nicolasraoul$ JAVA_HOME=/usr/libexec/java_home -v 17.0.9 ./gradlew build
BUILD SUCCESSFUL in 592ms
—
Reply to this email directly, view it on GitHub
https://github.com/coordinates2country/coordinates2country/issues/5#issuecomment-1857875655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APBCGJXDSURKNZVZQLYDSETYJRFLTAVCNFSM6AAAAABASIHLLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXHA3TKNRVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

It works now with Java 17, thanks for the update!

Glad to hear that, you're welcome!
Please let me know if there is anything else to improve. :-)


Feature Suggestion: (Semi)Automatic first comment on youtube with the specific dissenter link.

Is there a way to implement a one or two button solution for content creators to (semi)automatically create a first comment for every uploaded video with the following content:
"Uncensored comment section: Dissenter-URL for that video
Get the Dissenter browser Extension here"
I think this could help getting more exposure and more people to use Dissenter.

Hi @BunnyTheLifeguard thanks for the feature request. This is a good idea. We will be working through a few potential ideas for this and will be sure to keep you posted when a decision is made.
Will be keeping this issue open until that time comes.


(#1025) Updated cactoos dependency to version 0.44

This PR is for #1025

@fanifieiev/z this pull request is too small, just 8 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @paulodamaso/z please review this and merge or reject

@rultor merge

@rultor merge

@paulodamaso OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@fanifieiev @paulodamaso Oops, I failed.

Locales to be generated: 804e16dc39e237089a753b0b16ed8164a7537fa6fb23eb33133d5d70c64d421a
'pid' file is absent, something was broken

@paulodamaso Please try merging again

@fanifieiev done!

Job gh:yegor256/takes#1033 is not assigned, can't get performer

This job is not in scope


Useless use of vec!

Clippy complains about this line in the codebase, saying it's a useless use of vec! (which it is). This can be pretty easily fixed like so:
fn to_tokens(&self, tokens: &mut TokenStream) {
    let dependencies = &self.0;
    let num_deps = dependencies.len();
    tokens.extend(quote! {
        {
            let mut dependencies = Vec::with_capacity(#num_deps);
            #( #dependencies )*
            dependencies
        }
    })
}

Just add a line and change vec! to a Vec::with_capacity call, fixing the warning and slightly improving performance. There may be a slightly better/cleaner way, but I'm not that well-versed in proc macros, so this at least works and is faster.
I found this issue through Lemmy, which uses ts_ts v6.2.1 - there are literally hundreds of these warnings in the codebase because of how many structs derive TS - and I would really appreciate if this fix was applied to both the main branch and a temporary one so we could get a v6.2.2 or something.
Please let me know if there's anything I can do to help make this happen.

fixed on master, and in 0.7 to be released soon


Run azd provision error on Windows

Describe the issue:
When running azd provision on Windows, an error is displayed indicating a syntax rule error in the hook script as follows:

Repro Steps:

Clone the project.
Run python -m venv .venv and .venv\Scripts\activate.
Run pip install -r requirements.txt.
Run azd auth login.
Run npm i.
Run npm run env:init.
Run azd provision.

Environment:

Azd version: azd version 1.9.6 (commit 0b1a8ad350177078312141f4465ad72205d7c077)
OS: Windows desktop.

Expected behavior:
Run azd provision successfully.
@hemarina and @cwaddingham for notification.

@cwaddingham The issue described above can still be reproduced according to the latest code test. A code review found that the problem is preprovision.ps1 file  in the code , where bash syntax was incorrectly used instead of powershell syntax.

@NanaXiong00 please try it again.

@NanaXiong00 please try it again.

@cwaddingham Based on the latest code retest, the following error occurred:

Run command npm run env:init:

Run command azd provision:

@NanaXiong00 given the number of issues that have come up with running this template on Windows we're going to remove support for that OS from it. Going forward, it will be supported on MacOS and Linux. We may revisit this in the future, but for now, this first iteration will be POSIX-only.

@cwaddingham While testing the template on macOS according to the instructions in README.md, the following issues were encountered:

It is recommended to include dependency installation steps in the README.md to prevent these issues.


feat: add code coverage report

Pull Request Guidelines
Our guidelines for submitting a pull request.
Before submitting a Pull Request, please make sure you have verified the following:

[x] The commit message follows our guidelines:

A good commit message should be two things: meaningful and concise. It should not contain every single detail, describing each changed line—we can see all the changes in Git—but, at the same time, it should say enough to avoid ambiguity.
We use Microverse's commit message convention
The convention stablish that a commit message has to be in the present tense, imperative and lowercase.
Example: fix typo in README.md

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[x] Other... Please describe: adding codecov ci

What is the current behavior?
Please describe the current behavior that you are modifying, or link to a relevant issue.
No CI action for code coverage
Issue Number: N/A
What is the new behavior?
Describe the new behavior or link to a relevant issue.
codecov action coverage
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications below.
Other information
Any other information that is important to this PR.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


add link to marketplace offering

Job PR-561-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-561/4/index.html


update transcript processing to support multibyte characters

name: update transcript processing to support multibyte characters
about: arabic transcripts were failing due to characters being multibyte
title: "Fix Arabic Transcription"
labels: ''
assignees: ''

description
brief description of the changes in this pr.
related issue: #451
type of change

[x] bug fix
[ ] new feature
[ ] breaking change
[ ] documentation update

how to test

Launch screenpipe
Play some Arabic Audio / Speak arabic
query transcript

checklist

[x] i have read the CONTRIBUTING.md file
[x] i have added the custom cursor AI prompt to my settings as mentioned in CONTRIBUTING.md and used to write this PR
[x] my code follows the project's style guidelines
[x] i have performed a self-review of my code
[ ] i have updated the documentation if necessary
[x] my changes generate no new warnings
[ ] i have added tests that prove my fix is effective or that my feature works
[x] all tests pass locally with my changes

additional notes
Where should I document that Arabic is not supported by deepgram?

@louis030195


Sending to 403 Forbidden after creating BREAD

Version information

Laravel: 5.7.12
Voyager: 1.1
PHP: 7.1.19
Database: [MySQL] [5.7.23]

Description

After creating a new table in the database, making the model, and adding bread, I am presented with a 403 'Sorry, you are forbidden from accessing this page.' error when attempting to browse the bread for the just created table.
Roles are all checked off for the user, so this is not the issue.
Steps To Reproduce
Steps to reproduce the behavior:

Go to admin
Click on /admin/whatever I just created
See error

Expected behavior
Should be presented with the proper page to browse the table and add/edit etc.

Roles are all checked off for the user

Just confirming, do you mean "permissions" and "role" instead of "roles" and "user"?
There shouldn't be anything else involved.  If BREAD exists, the policy will be attached to the model class defined in BREAD.  Any time an action is auth-checked against an instance of that model, the policy gets checked, which (by default) only checks whether Auth::user()'s role has the necessary permission.
Can you say more about what you've done? Perhaps share a screenshot of the BREAD settings? Do you have anything custom (policy class, etc.)?

Yes, permissions (under the roles tab) are all checked off giving the user permission to access all areas of the table. I don't think there should be anything else either, I have built many things using voyager and have never had an issue.
The issue comes in when I create a new table, create the model, and add the BREAD. Then if I try and click on 'edit bread', I get the 403 error. I have nothing custom, the admin panel at the moment is almost completely a fresh install. I have even tried creating a new app and this issue is still there. Could it perhaps be something to do with my localhost setup?

This may be among the weirdest things I've experienced in my career, but it seems after changing nothing and doing the exact same thing, over the weekend all is working fine now...
I wish I could offer more insight in case somebody else experiences this issue. Thanks @fletch3555 for offering some insight!

Correct, I was doing it through the UI in this instance. If I ever figure out what it was I will share!

Just in case anyone has the same issue. How to reproduce (I think there are more ways):

Create table with a capitalized name, e.g. "Offers"
Create a BREAD
View BREAD and see that
Panic and manually rename the table to "offers" (lowercase). Also change the row in data_types.
Forget to edit permissions to "offers" as well.
Voilà

Can confirm that a bug is still present and caused by model binding for routes
Route::model('attribute', \App\Models\Attribute::class);
Route::model('product', \App\Models\Product::class);
Route::model('category', \App\Models\Category::class);

Check the name of your models inside Voyager; make sure they match the model EXACTLY in laravel


Migrations: Allow shared columns and constraints within a hierarchy

The behavior on metadata conflicts is undefined. (See #4074)
Fixes #3061

:shipit:


WSA windows are not adjusting to the custom canvas created in FancyZones

Microsoft PowerToys version
0.55.2
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Create a custom canvas in FancyZones
Press Shift to adjust Windows Subsystem for Android's window to it.
✔ Expected Behavior
Two windows should be adjusted to the custom canvas area when snapping to
❌ Actual Behavior
One of them adjusted to the custom canvas area when snapping to but the other one is taking minimized form.
Other Software
WSA

@curtkas Same as #10942?

yes  /dup #10942

actually, just in case, lets /dup #14538

actually /dup https://github.com/microsoft/PowerToys/issues/10942


Error head tag and error enable_page_level_ads

Hi. I had this error enable_page_level_ads appear in my sentry but not in my devtools console (on v1.3.0).
Then i try to upgrade to the latest version which is v1.4.0. this error appear on my console.

Has anyone experienced the same error?
and is there a solution?
Thank you.

I have same issue as well.

@narendra087 Did you add an ads.txt file to your site? I added this file and it seems to have fixed this issue that I was also having. Here's some Google documentation: https://support.google.com/adsense/answer/7532444
#56

Can you show me how you implement this module? Thanks

Hi @narendra087 sure, I implemented Google Adsense on my personal blog:

Link: https://briancaffey.github.io
Source: https://github.com/briancaffey/briancaffey.github.io
Article about implementing AdSense and AdBlock detector: https://briancaffey.github.io/2021/10/31/how-and-why-i-added-adsense-and-adblock-blocker-to-my-website/

Warning: there are ads on my site, and you need to disabled your AdBlock to read my blog

Hi @narendra087 sure, I implemented Google Adsense on my personal blog:

Link: https://briancaffey.github.io
Source: https://github.com/briancaffey/briancaffey.github.io
Article about implementing AdSense and AdBlock detector: https://briancaffey.github.io/2021/10/31/how-and-why-i-added-adsense-and-adblock-blocker-to-my-website/

Warning: there are ads on my site, and you need to disabled your AdBlock to read my blog

Thank you,
I have checked your site but the error 'enable_page_level_ads' is still there in the console.

I have the same issue as well.

same issue

I've had the same issue, but only when I ran nuxt without SSR. In production where SSR is enabled, it seems to work.

Same issue

same issue


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.4.21 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Boxes should be centered

When using the boxes key, the resulting boxes should be centered in the card so that the appearance is symmetrical.

I disagree - most of the other content is left-aligned. We could add alignment as an option though.


Floppy build fix

Description
This fixes the build for the floppy image to properly use Nix and docker.
Why is this needed
The build is currently broken and it's all my fault.
How Has This Been Tested?
Tested on both a NixOS Linux machine and an x86 Mac.

Needs to be refactored after #89 lands. Most will not be needed.

No longer needed as written thanks to #89.
#92 opened to get the newer partitioning.


Drag and drop dialogue box - Team 6

Description
Task: Drag and drop display box .
Feature: Features
Creating a display box to place different options in a game is a common user interface design element that allows players to interact with various in-game choices or settings. In context to our game this box would contain the types of towers so that the user is allowed to drag and place the towers in the map to be able to facilitate the game play.
Dependencies

[ ] @design commitee (#xx)
[ ] Map team so that the positioning is deemed perfect (@team3)
[ ] the tower team so that the actual types of towers are given to be put it up on the screen ( @team2)

Milestones
List of steps that need to be completed for this task.

[x] Create the dialogue box in the game screen ( sep 2 )
[x] insert the different images of the towers to the display screen for the user to select( sep5)
[x] position the tile in the game lanes accordingly so that after a tower is selected it doesn't disrupt the whole
display box design ( sep 8)
[x] Test and Intergrate( sep 8)

Completion Deadline: Sep 8
Documentation

Main description of feature
JavaDoc
...

Member

Vansh Mittal (@V4N5HM)

The different types of tower are displayed at the top of the screen so that the user can choose one to input in his game play


Remove useless parameters

Please make sure these boxes are checked before submitting your PR, thank you!

[ no docs change] Make sure you follow Element's contributing guide (中文 | English).
[yes ] Make sure you are merging your commits to dev branch.
[yes ] Add some descriptions and refer relative issues for you PR.

Remove the useless parameters of the closeMenu method, in el-menu component.

Thanks. Please also remove the second param of this line in submenu.vue.


Incorrect Network

I was setting up the frontend to work with my testnet deployment.  even though i changed the neccessary configs to testnet i still get the attached error message.
what could be doing wrong?

The testnet configs are used if the url includes testnet or if you pass it as an argument.
Try this url in chrome
http://localhost:7000?testnet=true

Awesome!!. its worked.  Thank you so much :)


added: contributor profile socialLink#71

@rishipurwar1 review this, added social link

@Bivas-Biswas Please resolve the merge conflict

Still showing me @Bivas-Biswas

it's running ok

Hey @Bivas-Biswas
Can you please test your changes in the website?
Is everything working as expected?
One more thing can you please add target=”_blank” rel=”noopener noreferrer” to the social link so that link will open on a new tab securely.

@rishipurwar1 All looks fantastic.
I am working on next

Thanks! I thought I messed up all the PR.
Just fix the above-mentioned issue and then move on next.

Thanks! I thought I messed up all the PR. Just fix the above-mentioned issue and then move on next.

Yes,  I also confused my all branch. I was working many things on same.
Next, I will doing one by one.
Thanks 🙂


wip unifying the configs

Pull Request Test Coverage Report for Build 425682462

2 of 7 (28.57%)  changed or added relevant lines in 2 files are covered.
50 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.5%) to 34.843%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/util/logConfig.go
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/util/logConfig.go
11
11.54%

pkg/util/logger.go
39
11.22%

Totals

Change from base Build 423005895:
-1.5%

Covered Lines:
1423

Relevant Lines:
4084

💛  - Coveralls


MNT Standardise modules

Issue https://github.com/silverstripeltd/product-issues/issues/570

prf-low job failed


Debugging Custom Istio Adapter

Describe the bug
Currently there is no documentation to help debug custom Istio (mixer) adapters
Expected behavior
It would be great to have a prescribed document on how to debug custom adpaters for the following scenarios:

Local development. (This exists)
Run the Mixer, ie. policy and telemetry containers independently and then be able to run check and report calls directly using mixc against a running mixer (i.e mixs is my guess).

Steps to reproduce the bug
I currently have Istio deployed along with my custom mixer container. However, I am unable to get to talk to my mixer. I am making requests but also getting many errors.
Version
1.10.5-gke.4
Is Istio Auth enabled or not?
Yes
Environment
GKE
Error
<sup
2018-08-15T17:07:23.896946Z	warn	testhandler.mysampleadapter.istio-system unable to unmarshal: unknown field "metrics" in config.Params, {"metrics":[{"name":"requestcount.metric.istio-system","type":"COUNTER"},{"name":"requestduration.metric.istio-system","type":"DISTRIBUTION"},{"name":"requestsize.metric.istio-system","type":"GAUGE"},{"name":"responsesize.metric.istio-system","type":"GAUGE"}]}
2018-08-15T17:07:23.897215Z	error	Failed to convert testhandler.mysampleadapter.istio-system an event: unknown field "metrics" in config.Params
and
2018-08-15T17:07:22.859843Z	error	Handler not found: handler='testhandler.mysampleadapter'

@guptasu @mandarjog Can you please help. I've been stuck on this for close to a month.

What does your config proto look like?  And have you run the required generation steps, etc.?

I followed all the steps outlined in: https://github.com/istio/istio/wiki/Mixer-Compiled-In-Adapter-Walkthrough
When I test it locally it works. (with the mixs and mixc)
However, when I push it to a running Istio deployment I get the errors shown above.
My config.proto is:
syntax = "proto3";
package adapter.mysampleadapter.config;
import "google/protobuf/duration.proto";
import "gogoproto/gogo.proto";
option go_package="config";
message Params {
// Path of the file to save the information about runtime requests.
string file_path = 1;
}

I'm confused. Your config.proto doesn't show any metrics field. Shouldn't it include a metrics field for this all to work?

I was approaching this in a phased manner. As I mentioned, I followed the custom adapter walkthrough example. And following got me to the point of running the mixs and the mixc and I could see my adapter being invoked.
My assumption was that if I built the mixer and updated the mixer policy and telemetry pods with my new image and if I ran some traffic against my app with all the right configs (that is with handler, instances, operatorconfigs etc), that this same thing would invoke my custom adapter and would have the same behavior.
Am I not in right in that assumption. If not can you point me to some documentation or examples which ties all these aspects together?
Thank you for the responses.

I'm not sure I follow your plan -- my apologies.
If you have istio config for your handler (you've kubectl apply -f'd some YAML) and it has config for metrics (as appears), then this cannot work unless you add a field to your config proto for metrics of the correct type, etc.
Please post your handler config here for confirmation.
Picking an adapter at random, we'll use circonus to explain:

Note the metrics field in the config.proto: https://github.com/istio/istio/blob/master/mixer/adapter/circonus/config/config.proto#L59
Note the handler config in their example operatorconfig yamls: https://github.com/istio/istio/blob/master/mixer/adapter/circonus/operatorconfig/circonus.yaml#L62-L80

Does that help?

@vinayvenkat It would be great if you write your adapter as out-of-process.
https://github.com/istio/istio/wiki/Mixer-Out-of-Process-Adapter-Walkthrough
It decouples you from mixer itself and arguable easier to test.
You can install a stock istio / Mixer release and then deploy your adapter independently.
Here is a sample adapter including its integration test.
https://github.com/istio/istio/blob/master/mixer/test/prometheus

@douglas-reid We are following this defect as well. We followed all the steps in https://github.com/istio/istio/wiki/Mixer-Out-of-Process-Adapter-Walkthrough and configured a custom adapter to build a new adapter. Since we coded our custom adapter inside the mixer folder, we were wondering how could we deploy our adapter independently from the mixer. And if the mixer container is inside the telemetry and the policy pods, how do we compile this adapter independently. We have been following this guide https://github.com/istio/istio/wiki/Mixer-Using-a-Custom-Adapter to build an out-proc adapter, but in Step 2 we dont seem to find our custom adapter in the CRD definitions listed. Do you know the reason why?

@sputtag1 a guide on deploying OOP adapters would be very useful, I agree. would you mind filing a separate issue to cover this need? we'd want to cover best practices, etc. and add to it as bits like auth and security are incorporated.
RE: the missing CRD
I believe you have to add the adapter to the adapter inventory for the mixs crd command to be aware of it. @mandarjog is this the intended dep? Is there another way we can support generation?
RE: template -> API
The generated go code for a template should directly contain the details needed for implementation. For the metric template, this includes:
service HandleMetricService {
    // HandleMetric is called by Mixer at request-time to deliver 'metric' instances to the backend.
    rpc HandleMetric(HandleMetricRequest) returns (istio.mixer.adapter.model.v1beta1.ReportResult);

}

Does that help?

An example OOP adapter with a deployment can be found in mixer/test/prometheus/cmd. My suggestion would be to start with that as a guideline on how to get something working.

@douglas-reid Thankyou, we followed the steps that you have mentioned. We were able to build the image, push it and apply it. But when the pod is starting we are running into this error: "container_linux.go:247: starting container process caused “exec: \“/usr/local/bin/mygrpcadapter\“: permission denied”". So why is it searching for the image at /usr/local/bin, while we have a different path set in the Dockerfile add. Is this path hardcoded by any chance?
Our Dockerfile content:
FROM scratch ADD mygrpcadapter /root/adapter ENTRYPOINT ["/root/adapter"]

You should probably consult the docker docs at this point, but you might try:
FROM scratch ADD mygrpcadapter /usr/local/bin/ ENTRYPOINT ["/usr/local/bin/mygrpcadapter"]

@douglas-reid That dint work either. https://github.com/istio/old_issues_repo/issues/179 - our issue is similar to this one. We are using istio 1.0.0

@douglas-reid We have successfully deployed our custom adapter. But when we apply the handler/rules/instances in sample_operator_cfg.yaml.
We are running into this error:
2018-08-24T21:42:31.168799Z	info	Publishing 3 events
2018-08-24T21:42:31.172676Z	error	adapter 'mygrpcadapter' not found
2018-08-24T21:42:31.173335Z	error	template 'metric' not found
2018-08-24T21:42:31.179011Z	error	Handler not found: handler='h1.istio-system'
2018-08-24T21:42:31.179063Z	error	No valid actions found in rule
2018-08-24T21:42:31.179232Z	info	Built new config.Snapshot: id='2'```
Could you please help us through it ?

Can you provide your Service, Deployment, handler, instance and rule configuration?

You need to register metric as a dynamic template and you also need to register your adapter.
Look At Prometheus.yml in the test directory that you used earlier for an  sample of adapter.
For metric template apply this file: https://github.com/istio/istio/blob/master/mixer/template/metric/template.yaml

Hi @douglas-reid @mandarjog:
Question about the running the mixer server.
I run it with:
/home/ec2-user/go/out/linux_amd64/release/mixs server --configStoreURL=fs://$(pwd)/mixer/adapter/mysampleadapter/testdata
When it runs it outputs the default config:
MaxConcurrentStreams: 1024
APIWorkerPoolSize: 1024
AdapterWorkerPoolSize: 1024
APIPort: 9091
APIAddress:
MonitoringPort: 9093
EnableProfiling: true
SingleThreaded: false
NumCheckCacheEntries: 1500000
ConfigStoreURL: fs:///home/ec2-user/go/src/istio.io/istio/mixer/adapter/mysampleadapter/testdata
ConfigDefaultNamespace: istio-system
ConfigIdentityAttribute: destination.service
ConfigIdentityAttributeDomain: svc.cluster.local
====
So the ConfigIdentityAttribute is set to: destination.service and the
ConfigIdentityAttributeDomain is set to: svc.cluster.local
Now when I send a report command:
/home/ec2-user/go/out/linux_amd64/release/mixc report -s destination.service="svc.cluster.local" -t request.time="2017-02-01T10:12:14Z"
everything works.
However, I am unable to change the arguments i pass into the report call.
For example, I can't seem to run this command:
/home/ec2-user/go/out/linux_amd64/release/mixc report -s source.labels="app:vv_app" -t request.time="2017-02-01T10:12:14Z"
Error:
2018-08-16T22:58:10.083301Z     info    pickfirstBalancer: HandleSubConnStateChange: 0xc420063980, READY
Report RPC returned Unknown (1 error occurred:

preprocessing attributes failed: identity parameter not found: 'destination.service')

How can I test other parameters that I send to the server? Can you please advise?

Hi there,
Which version of istio are you using?
We have mostly deprecated the use of destination.service attribute. From
version 1.0, the configuration resolution is scoped to a namespace of the
source or destination, depending on the direction of the call.
Best,
--kuat
On Thu, Sep 6, 2018 at 10:55 AM Vinay Venkataraghavan <
<EMAIL_ADDRESS>wrote:

Hi @douglas-reid https://github.com/douglas-reid @mandarjog
https://github.com/mandarjog:
Question about the running the mixer server.
I run it with:
/home/ec2-user/go/out/linux_amd64/release/mixs server
--configStoreURL=fs://$(pwd)/mixer/adapter/mysampleadapter/testdata
When it runs it outputs the default config:
MaxConcurrentStreams: 1024
APIWorkerPoolSize: 1024
AdapterWorkerPoolSize: 1024
APIPort: 9091
APIAddress:
MonitoringPort: 9093
EnableProfiling: true
SingleThreaded: false
NumCheckCacheEntries: 1500000
ConfigStoreURL: fs:///home/ec2-user/go/src/
istio.io/istio/mixer/adapter/mysampleadapter/testdata
ConfigDefaultNamespace: istio-system
ConfigIdentityAttribute: destination.service
ConfigIdentityAttributeDomain: svc.cluster.local
====
So the ConfigIdentityAttribute is set to: destination.service and the
ConfigIdentityAttributeDomain is set to: svc.cluster.local
Now when I send a report command:
/home/ec2-user/go/out/linux_amd64/release/mixc report -s
destination.service="svc.cluster.local" -t
request.time="2017-02-01T10:12:14Z"
everything works.
However, I am unable to change the arguments i pass into the report call.
For example, I can't seem to run this command:
/home/ec2-user/go/out/linux_amd64/release/mixc report -s
source.labels="app:vv_app" -t request.time="2017-02-01T10:12:14Z"
Error:
2018-08-16T22:58:10.083301Z info pickfirstBalancer:
HandleSubConnStateChange: 0xc420063980, READY
Report RPC returned Unknown (1 error occurred:

preprocessing attributes failed: identity parameter not found:
'destination.service')

How can I test other parameters that I send to the server? Can you please
advise?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/7952#issuecomment-419185159, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxrpD82CF3dGkd39f3G_orlkQvIhGks5uYWGbgaJpZM4V-4c1
.

Hi!
I am using Version: 0.8.0
: ~ >istioctl version
Version: 0.8.0
GitRevision: 6f9f420f0c7119ff4fa6a1966a6f6d89b1b4db84
User: root@48d5ddfd72da
Hub: docker.io/istio
GolangVersion: go1.10.1
BuildStatus: Clean
I will upgrade. Thanks.

I also figured out the problem:
The command needs to be invoked as:
/home/ec2-user/go/out/linux_amd64/release/mixc report -s destination.service="svc.cluster.local" --stringmap_attributes source.labels=app:vv_app -t request.time="2017-02-01T10:12:14Z"
I'll also close this ticket. I think all the issues have been addressed. Thank you for all the help.


bug fixes

possible fix for OUSD balance animation
fix for sell input field doesn't have the persistent "0" number
fix for sometimes wrong redeeming stablecoin values
fix a bug where:

user already had an ousd value to sell and stable coin redeem info present
would rapidly alter the ousd to sell and quickly press the sell button
transaction detail would show the old stable coin info (before the latest change)
fix for this: sell button is disabled as long as the latest stable coin info is not displayed

Connected issue: https://github.com/OriginProtocol/origin-dollar/issues/328

@micahalcorn just for info, also (possibly) fixed the OUSD balance animation in this PR. And beside the bugs we were discussing yesterday, found another sell form bug and included it into this PR.


get or put

If there are multiple screens where I need the same controller. How to make sure if I am seeing this screen for the first time or nor?
As per the docs:
GetBuilder<Controller>(
  init: Controller(), // INIT IT ONLY THE FIRST TIME
  builder: (_) => Text(
    '${_.counter}',
  ),
)

// INIT IF ONLY THE FIRST TIME
How would I know if its first time or not? It would nice if there is something like :
getOrCreate()

It depends on the architecture of your project. If you don't know how to do this, just use Bindings, and start your controllers there.

Suppose I have
FirstScreen() , SecondScreen(), ThirdScreen()
And in my app, it is possible to navigate to 1 to 2, 1 to 3
and I need a controller in both 2nd and 3rd screen.
How can I achieve this?

on FirstScreen:
GetBuilder<Controller>(
  init: Controller(),

It's done.

Ok. It's like I need to put it one level upper in the widget tree.
Would not it be nice if we can query if the controller has an active instance or not?

Ok. It's like I need to put it one level upper in the widget tree.
Would not it be nice if we can query if the controller has an active instance or not?

https://github.com/jonataslaw/getx#bindings

There is some api for this, you can use GetInstance ().IsRegistred();
But I do not recommend it, if you need to check if a controller is registered, it is because you are doing something wrong. Use Bindings if you need to know where Controllers are starting.

ok. Using Get for first time. We try to understand it better.
Thank you for this aweseome framework.

ok. Using Get for first time. We try to understand it better.
Thank you for this aweseome framework.

I understand, Get really has different approaches and in the beginning you will have several questions until you understand how everything works. I will provide links to community communication channels so that answering questions will be easier soon.

Well, I believe that this is already resolved.
Closing it.


ld: framework not found Reveal

I'm trying to run the sample project but I get this error
ld: framework not found Reveal
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Have you solved it?

just remove Reveal.framework from Frameworks folder on Xcode solved this problem @smidaharoun

@MemetiDrak Thanks for the info


Add guardrails to doc and query JSON inputs

Description
Naturally, the JSON schema of both the sample documents and the query have downstream impact on the ingest and search pipelines, respectively. To help prevent accidental changes, and to make the user make a more explicit choice when editing such fields, this moves those inputs into modals. Users have a readonly view of the values, but must click on an explicit 'Edit' to change the values.
More specifics:

adds modals to SourceData (ingest) and ConfigureSearchRequest (search) components, and moves the form configuration inside such modals. Readonly codeblocks are added to the base form page for users to see the current values
updates the search request to be formally integrated into the form and UI config. It is now consistent with other JSON form values, like index mappings and index settings. Note we store them as raw strings, and parse or stringify them when converting to / from the Formik form on the UI
adds a useful default match_all query
nit: adds constants for help links / URLs that were hardcoded within the component
nit: finishes removing the unnecessary fields stored in the IConfigField interface as these have moved within the components themselves and are no longer persisted in ui_metadata.

Demo video, showing the readonly views, and the flows for editing the doc and query fields (button texts and modal titles subject to change)
screen-capture (10).webm
Issues Resolved
Makes progress on #23
Check List

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

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

Seems some issue in core OSD causing the test failure. My older version of OSD is working. It is just a single test case:
 PASS  public/pages/workflows/workflows.test.tsx (37.268 s)
  Workflows
    ✓ renders the page (336 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        38.255 s
Ran all test suites.
✨  Done in 40.10s.

Seems some issue in core OSD causing the test failure. My older version of OSD is working. It is just a single test case:
 PASS  public/pages/workflows/workflows.test.tsx (37.268 s)
  Workflows
    ✓ renders the page (336 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        38.255 s
Ran all test suites.
✨  Done in 40.10s.

and same issue on #232 to confirm it's unrelated.


How to manually control the theme without setting the system?

I want to know how to customize the switch to control the theme so that users can choose freely. If you have a good way, please let me know, thank you very much!

Wrap your app in a ColorSchemeProvider and pass a value.

thank you for your reply. I almost know how to do it


Suggestion：Please don't use location.hash so the library can be compatible with angular HashLocationStrategy.

Suggestion：Please don't use location.hash so the library can be compatible with angular HashLocationStrategy.

I've followed your suggestion and change the history from hash to a dummy location. That is required by supporting the "back button" on android or other devices.


Repository Hooks

Potentials Hooks:

Forks

[x] Latest Release
[x] Release by Tag
[x] List Forks

Collaborators

[x] List Collaborators

Stats

[x] Views
[x] Clones

List Collaborators
Views
Clones

are not possible yet because of auth


A heading immediately after a list element is parsed as an item of that list

Originally reported to prettier: https://github.com/prettier/prettier/issues/3247
See http://astexplorer.net/#/gist/e3eaf84774057db35a17b3065aa3f8a3/69aa50de7bc313fad863946ebe318aa88d288afa

Would you be interested in working on this?
As a pointer, you can add tokenisers to interruptList!


Timezone resets to UTC when removing tzdata as per wiki

I'm using node:10.1-alpine.
Following the steps from this Wiki page to setup the OS timezone: https://wiki.alpinelinux.org/wiki/Setting_the_timezone
I'm noticing that the system timezone gets reset to UTC if I cleanup and delete the tzdata package once I'm done setting up and confirming the correct timezone.
Not sure if the last step in that wiki needs to be removed or if I did something incorrectly to maintain the timezone preference?
Will result in image with UTC:
RUN apk add --update tzdata && cp /usr/share/zoneinfo/America/New_York /etc/localtime && echo "America/New_York" > /etc/timezone && apk del tzdata && rm -rf /var/cache/apk/* &&  rm -rf /usr/local/share/.cache
Will result in image with EDT:
RUN apk add --update tzdata && cp /usr/share/zoneinfo/America/New_York /etc/localtime && echo "America/New_York" > /etc/timezone && rm -rf /var/cache/apk/* &&  rm -rf /usr/local/share/.cache

The you are probably using:
aarch64	Bump version 3.8.1	23 days ago
armhf	Bump version 3.8.1	23 days ago
ppc64le	Bump version 3.8.1	23 days ago
s390x	Bump version 3.8.1	23 days ago
x86	Bump version 3.8.1	23 days ago

23 Days ago there was a change setting the default timezone to UTC check:
https://github.com/gliderlabs/docker-alpine/blob/master/versions/library-3.8/aarch64/Dockerfile
https://github.com/gliderlabs/docker-alpine/blob/master/versions/library-3.8/armhf/Dockerfile
https://github.com/gliderlabs/docker-alpine/blob/master/versions/library-3.8/ppc64le/Dockerfile
https://github.com/gliderlabs/docker-alpine/blob/master/versions/library-3.8/s390x/Dockerfile
https://github.com/gliderlabs/docker-alpine/blob/master/versions/library-3.8/x86/Dockerfile

I have the same problem and I confirm that when not remove tzdata at the end, timezone is working.


editors, lines and cols

When launching an editor in mesos-term

nano returns an error Error opening terminal: unknown., we have to manually set the TERM env  TERM=linux nano
vim, nano, and I guess most editors use 24 lines and 80 cols, regardless the window size.

2 questions :
1 / shouldn't TERM=linux be injected in the environment if not present ?
2 / how can we use the full window with text editors ?

The latest xterm.js release may help solving this issue
https://github.com/xtermjs/xterm.js/releases/tag/3.11.0

Hello @vixns , this problem is resolved with the following PR that has been merged these days: https://github.com/clems4ever/mesos-term/pull/17.

Regarding the resizing problem, we need to try the upgrade of xtermjs on our side.

After more testing, I found it only occurs when running mesos-term within a container.
It seems related to signal propagation, /resize... ajax calls are ignored, the SIGWINCH  signal is fired but the python program does not receive it when running within docker, so stty is not called.
On my development laptop within docker stty is called only once on load, on each resize without docker.
Running in a mesos container, resize is never called (race condition on the first call? this is probably a separate issue).
Workaround :
Open the browser's inspector's network tab, resize the window, you'll see the cols and rows values in /resize... calls. Send the command stty cols XXX rows XXX using these values.

The culprit was alpine, rebasing the image on node:lts-slim, which is debian, fix the signal propagation issue.

hello @vixns , I'm rewriting MesosTerm in React to integrate sandbox browsing to the application. I tested resizing and it seems to work in the new version: https://github.com/clems4ever/mesos-term/pull/28.

Closing this issue, feel free to reopen if the issue persist.


SystemParamBuilder - Support dynamic system parameters

Objective
Support building systems with parameters whose types can be determined at runtime.
Solution
Create a DynSystemParam type that can be built using a SystemParamBuilder of any type and then downcast to the appropriate type dynamically.
Example
let system = (
    DynParamBuilder::new(LocalBuilder(3_usize)),
    DynParamBuilder::new::<Query<()>>(QueryParamBuilder::new(|builder| {
        builder.with::<A>();
    })),
    DynParamBuilder::new::<&Entities>(ParamBuilder),
)
    .build_state(&mut world)
    .build_system(
        |mut p0: DynSystemParam, mut p1: DynSystemParam, mut p2: DynSystemParam| {
            let local = p0.downcast_mut::<Local<usize>>().unwrap();
            let query_count = p1.downcast_mut::<Query<()>>().unwrap();
            let entities = p2.downcast_mut::<&Entities>().unwrap();
        },
    );

Thank you to everyone involved with the authoring or reviewing of this PR! This work is relatively important and needs release notes! Head over to https://github.com/bevyengine/bevy-website/issues/1679 if you'd like to help out.


Add context manager implementation for name stack handling

TLDR; This PR adds a parallel context manager implementation for name stacks, gated by the jax_experimental_name_stack config flag. named_call uses this new context manager rather than a call primitive. Another public API to access and manipulate the name stack will be in a forthcoming PR along with more detailed documentation.
Approach
The name stack is a data structure (a stack) that keeps track of both name scopes and transformations. Both scopes and transformations are pushed and popped off the stack. A stack that looks like [foo, vmap, bar] will produce the following OP metadata: 'foo/vmap(bar)', indicating that the bar stack is transformed by a vmap transformation. The jvp and transpose transformations are also example transformations that can be on the name stack.
Part 1: Annotations in jaxprs
The name stack mechanism needs to somehow record information into jaxprs, to ensure it's preserved through transformations that stage out Python code into a jaxpr and reinterpret that jaxpr.
How do we use a context manager to annotate jaxprs? Let’s say that each jaxpr equation has a new name_stack field that records the desired XLA HLO annotations we want when the jaxpr is lowered. How do we populate the name_stack field with a context manager?
First let’s implement a simple context manager API:
@contextmanager
def extend_name_stack(name):
  # appends `name` to the active name stack

def current_name_stack(name):
  # returns the current name stack

A simple use case for this function is annotating primitives within a function.
def f(x):
  with extend_name_stack('bar'):
    return x * 2.

We hope that when this function is staged out to a jaxpr we get the following annotations (represented in brackets after the equation).
{ lambda a:float64[] .
let b:float64[] = mul a 2.0 # [bar]
in ( b ) }

We can modify the trace that builds jaxprs to call current_name_stack() when it’s creating an equation to populate the name_stack field.
This is a simple strategy for propagating information from a context manager into the staged out jaxpr. In practice, we utilize the source_info tracking already present in JAX and augment the SourceInfo with a name stack field.
Part 2: Final style transformations
What’s the desired behavior when functions with extend_name_stacks in them are transformed? When a particular primitive is reinterpreted under a transformation we’d like to modify the name stack to include information about the transformation.
Take the following vmap example:
@vmap
def f(x):
  with append_name_stack('bar'):
    return x * 2.

We’d like the following annotated jaxpr:
{ lambda a:float64[2] .
let b:float64[2] = broadcast [ axes=[0] shape=[2] ] 2.0 # [vmap(bar))]
    c:float64[2] = mul a b # [vmap(bar)]
in ( c ) }

See how we have vmap(bar) annotations for both the broadcast and the mul. How do we modify our context manager for this use case? Let’s support adding “transformations” to the name stack.
@contextmanager
def transform_name_stack(name):
  # appends `name` to the active name stack as a transformation

In our vmap implementation we can do something like this:
def vmap(f):
  def wrapped(*args, **kwargs):
    with append_transform_stack('vmap'):
      out = …
    …
  return wrapped

When we vmap a function we’ll have a transform on the name stack which we can then postprocess to produce the vmap(bar) annotation we desire. We can do the same for all final-style transformations, i.e. the transformations implemented as Traces vs jaxpr interpreters (e.g. jvp).
Part 3: Initial style transformations
Initial style transformations like grad or the control flow primitives first trace a function out into a jaxpr, then reinterpret it in some interesting way. grad, for example, traces the partially evaluated jvp of a function into a jaxpr and interprets the resulting jaxpr backwards to obtain gradients.
This brings up a potential issue with adding annotations using a dynamically scoped name stack. Recall that we add annotations to jaxpr eqns via the DynamicJaxprTrace looking up the currently active name stack. If we’re staging out a jaxpr while inside of another transformation (which is the case in initial style transformations), we’ll include that transform’s annotation in the stack. For example, consider a no-op initial style transformation that stages out and immediately evaluates a jaxpr.
def reinterpret(f):
  def wrapped(*args):
    jaxpr = make_jaxpr(f)(*args)
    return eval_jaxpr(jaxpr, *args)
  return wrapped

We could imagine that if there's a foo name stack active outside of the call to reinterpret, we'll bake foo into the name stacks in the jaxpr and then add yet another foo when calling eval_jaxpr. Furthermore, what do we do with the name stacks backed into the jaxpr themselves? We have to be careful about how we treat name stacks in this setting.
eval_jaxpr
How does eval_jaxpr handle annotations? We have a couple choices. We could have it just inherit the current active name stack, i.e.:
def eval_jaxpr(jaxpr, *args):
  …
  for eqn in jaxpr.eqns:
    …
    ans = eval_eqn(eqn, …)
  …

However, if the equations we’re evaluating have name stacks, they will be discarded and we will lose information. We need to somehow preserve the name stacks in the jaxpr we’re evaluating. We could instead re-use that information, throwing away the current name stack info using a set_name_stack context manager.
def eval_jaxpr(jaxpr, *args):
  …
  for eqn in jaxpr.eqns:
    …
    with set_name_stack(eqn.name_stack): # overrides current name stack
      ans = eval_eqn(eqn, …)
  …

This is also incorrect, however. We want to use the current active name stack as well since we might be transforming eval_jaxpr from the outside. We thus need to prepend the current active name stack to the one from the equation.
def eval_jaxpr(jaxpr, *args):
  …
  for eqn in jaxpr.eqns:
    …
    with set_name_stack(get_current_stack() + eqn.name_stack):
      ans = eval_eqn(eqn, …)
    …

make_jaxpr
Now consider the following example.
@vmap
@reinterpret
def f(x):
  with append_name_stack('bar'):
    return x * 2.
f(jnp.ones(2))

In principle, we should obtain the same annotations as before (vmap(bar)). However, in our currently implementation we first obtain a jaxpr in reinterpret. Since that jaxpr is using dynamically scoped annotations, it will annotate the mul with a vmap(bar) even though we’re not actually doing a vmap – we’re just staging out an unbatched function. The actual vmapping happens when we call eval_jaxpr. If we’re staging out the entirety of f into jaxpr, the vmap will still be on the stack when we call eval_jaxpr and we will get a doubly-annotated vmap(vmap(bar)), an incorrect annotation. This is a huge problem!
This pattern of transforming an initial style transformation occurs everywhere (vmap(grad) is an example of this). How do we modify our implementation to get the right annotations?
First, while building the jaxpr, we need to start with an empty active name stack rather than the current active name stack. We can accomplish this with another context manager that essentially clears the active name stack:
@contextmanager
def reset_name_stack():
  # sets the current name stack to be empty

Right before we build a jaxpr, we make sure to clear the active name stack.
def make_jaxpr(f):
  def wrapped(*args):
    with reset_name_stack():
      jaxpr = …
    return jaxpr
  return wrapped

The jaxpr we now stage from the example will no longer have a vmap(bar) annotation (it will just have a bar annotation). When we eval_jaxpr, the vmap on the name stack will be prepended to the bar to produce the appropriate vmap(bar).
This strategy of disabling the name stack when staging out to a jaxpr and prepending the active name stack to the one from the jaxpr equation generalizes to other instances of staging out and reinterpreting, for example with control flow primitives. We need to make sure that when tracing out a body function to a jaxpr, for example, it is staged out without the active name stack. When the body is reinterpreted in the context of a loop, eval_jaxpr will add the active name stack back in.
Part 4: partial_eval
Partial evaluation is a particularly tricky case because it both evaluates and stages at the same time. We thus need to be careful about how we annotate both the evaluated primitives and the staged out ones. We can use the same principles from before though: disable the name stack when we stage out and enable when we are evaluating.
How do we emulate this when we’re in a final style transformation though? In an initial style transformation, the distinction between staging and evaluation is very clear and there are obvious places to disable and enable the name stack. In a partial eval trace, when we evaluate a primitive there will be names on the stack from outside of the partial eval trace and from inside. When we stage out, we want to annotate the jaxpr equation with the names from the “inside”, not the “outside”. Here’s an example:
@vmap
@partial_eval
def f(x, y):
  with append_name_stack('foo'):
    x = x + 1
  with append_name_stack('bar'):
    y = y + 1
  return x, y

Let’s say this partial_eval transformation treats x as known and y as unknown. We thus want to evaluate x + 1 and stage y + 1 into a jaxpr. When we evaluate x + 1 we’d like it to be annotated with vmap(foo) but when we stage out y + 1 we want it to be staged out with just bar, not vmap(bar).
When we’re inside of the partial eval trace, we need to distinguish between the names that are added outside of the partial eval (vmap in this case) and the ones inside (foo and bar). We can accomplish this by recording the name stack before the partial eval trace and removing it when staging out a jaxpr eqn.
def partial_eval_flat(f, pvals_in):

  outer_stack = current_name_stack()
  with new_main(PartialEvalTrace, outer_stack) as main:
    outs = …
  return jaxpr, pvals_out, consts

Any names added to the stack while doing the partial eval will be the inside names. Inside of the process_primitive for partial eval, we can do the following:
def process_primitive(self, primitive, tracers, params):
  if all(t.pval.is_known for t in tracers):
      return bind(primitive, *map(full_lower, tracers), **params)
  …
  # grab the portion of the name stack that extends beyond the outer name stack
  name_stack = current_name_stack()[len(self.outer_name_stack):]
  eqn = JaxprEqnRecipe(..., name_stack)
  …

If we evaluate inside of partial eval, we use the full stack (outer + inner). If we stage out, then we just use the inner names.
Implementation details
The goal of this implementation is to preserve the previous mechanism and enable the context-manager behind a config flag. To accomplish this, we have two parallel mechanisms keeping track of the name stack and decide to use one or the other when lowering.

To add a name scope to the name stack, we use source_info_util.extend_name_stack, a context manager that pushes a name onto the stack and pops it off after the context manager exits. There is also source_info_util.transform_name_stack that pushes a transformation onto the stack.
When we lower a jaxpr to HLO (xla_subcomp), we, by default, use the current mechanism for adding OP metadata to the HLO. If jax_experimental_name_stack is enabled, however, we use the name stack from the SourceInfo (i.e the jaxpr equation). We make sure to thread an equation's name stack into any sub contexts use to generate HLO for say call primitive jaxprs.
To inspect and debug name stacks, you can now do jaxpr.pretty_print(name_stack=True) to have name stacks print for each equation.

This is really nice! One thought is that we are very keen in Haiku to turn on names by default (this will help a lot of our users) but it would probably not be appropriate for us (as a library) to force (or set) the new global config flag to be on. I see a couple of options:

If the flag is going to be flipped on by default soon (O(weeks) after submitting), then we'll be patient and just wait.
If the rollout will be slower than this, can we have an option in named_call (or similar) to opt into the new behaviour at the call site (perhaps as well as globally?). This would allow Haiku (and other libraries) to opt our internal usages into the new behaviour while letting users control the behaviour of the rest of their program.

Hi all, any ETA on this change landing? We would love to take advantage of it in Haiku.

Sorry for the delay, I've rebased it and will soon investigate the internal failures that blocked it previously.