Supplier QR Codes

[ ] - Stop duplicates from forming (Checking suppliershortcode is not in a list).
[ ] - Whatsapp entries still not included as they dont have suppliershortcode and suppliername in harvest Table.
[ ] - Create qrcode_url when opening supplier produce qrcode page just like storage handover page.

Dashboard only shows 3 most recent links for supplierproduce while the table below shows that there are more for each type of produce

qrcode_urls are also created on loading the dashboard similar to loading the storage handover page


Typing issues

The Callable should be able to be tightened up on line 43.
So, that can probably become Callable[[_TSelf[_T]], _T].
However, looking at that, it's defined the _cache as _cache: Dict[str, _T]. Wouldn't that make it impossible to use this decorator multiple times on different values? e.g. If I have a class with a URL and a port as int, then the dict type would need to be dict[str, URL | int], which would then result in both attributes returning URL | int.
So, I think the _cache annotation might need some reworking... I suspect the Generic will need to be dropped from _TSelf and the dict may need to use Any. I'm not sure there's a clear way to do it accurately and type safe.
Originally posted by @Dreamsorcerer in https://github.com/aio-libs/propcache/pull/50#discussion_r1791024397

Following on from that, I tried adjusting the type of the Callable, but just seem to get errors (maybe because the class hasn't been fully defined at the time of the decorator, mypy doesn't recognise the class as matching the protocol?).
However, a quick test also revealed that the typing information is completely broken.
We need to add some assert_type()s to the tests and fix the type errors.
Adjusting the first test to:
def test_under_cached_property(propcache_module: APIProtocol) -> None:
    class A:
        def __init__(self) -> None:
            self._cache: Dict[str, int] = {}

        @propcache_module.under_cached_property
        def prop(self) -> int:
            return 1

        @propcache_module.under_cached_property
        def prop2(self) -> str:
            return "foo"

    a = A()
    assert_type(a.prop, int)
    assert a.prop == 1
    assert_type(a.prop2, str)
    assert a.prop2 == "foo"

Reveals that all properties are Any. I'd also expect to get another error about the dict type, but currently don't.

Hmm, the typing seems to work on aiohttp though, so I'm not sure what I'm doing differently here for it to not work...

Different MyPy version?

I was testing locally with the same instance of mypy on each repo. assert_type() on req.rel_url in an aiohttp test works correctly, but in the above test it fails with Any.

Any future import of annotations anywhere?


Fixes for Arduino IDE 1.6.7

Arduino 1.6.7 (or any prior version) suffered from an issue where the ESP8266 library broke the pre-compiler's automatic function prototyping. See https://github.com/esp8266/Arduino/issues/1066
It looks like you've added most of the function prototypes to overcome this issue, but seemingly not all.
Also, there was a type mismatch on the sendFile() function that threw a compiler error.
Note: Please excuse the incidental trailing whitespace removals - my code linting setup is rather heavy handed. If you'd like to see this PR without them, just go ignore whitespace.

Well spotted Casey, and welcome to the FHTbot project.


Image windows-2022: Microsoft.VCToolsVersion.v143.default.props contains wrong version

Description
As described in azure-pipelines-agent issue #4554 and this Developer Community post, the current windows-2022 runner image has a wrong toolset version in the Microsoft.VCToolsVersion.v143.default.props file, leading to linker errors in certain build configurations.
Specifically, linking a static library calling sleep_for into an executable will cause a linker error such as this:
error LNK2019: unresolved external symbol _Thrd_sleep_for referenced in function "void __cdecl std::this_thread::sleep_for<__int64,struct std::ratio<1,1000> >(class std::chrono::duration<__int64,struct std::ratio<1,1000> > const &)" (??$sleep_for@_JU?$ratio@$00$0DOI@@std@@@this_thread@std@@YAXAEBV?$duration@_JU?$ratio@$00$0DOI@@std@@@chrono@1@@Z)

One of my projects exposes the issue in a very reproducible way: https://github.com/kblaschke/frontend-sdl2/actions
There are lots of other reports on GitHub and elsewhere having the same issue, possibly caused by a broken Visual Studio update. Examples:

https://github.com/mjansen4857/pathplanner/issues/677
https://github.com/microsoft/vcpkg/issues/38003

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Current runner version: '2.315.0'
Example failed build: https://github.com/kblaschke/frontend-sdl2/actions/runs/8619445446/job/23624147736
Is it regression?
2.311.0, https://github.com/kblaschke/frontend-sdl2/actions/runs/7588250886/job/20670360139
Expected behavior
The build should succeed, and the static library linked without an error.
Actual behavior
The build fails due to linker errors, most likely because the different builds steps select different toolset versions due to the broken .props files.
Repro steps

Build a static library using C++11 or higher via vcpkg, and use std::this_thread::sleep_for inside a function. The Poco::File class from the POCO framework is the one exposing an issue in my builds for example.
Build an executable with CMake and call the according function in the static library.

Thanks for the quick response!
I've been able to fix the build for now using the TheMrMilchmann/setup-msvc-dev@v3 action, but it would be nice to have a default setup that "just works" and simply uses the latest toolset automatically. I'll watch this issue and remove the workaround once this has been solved.

Heads up!
We've decided to remove all the VC components duplicates from the Windows-2022 image to avoid this nasty behaviour. Since it is a breaking change for the part of the community it was decided to take a long break before the rollout. Please, track progress here: https://github.com/actions/runner-images/issues/9701
Thanks to everyone involved in the related issues for your patience and information provided.


Feat: [M3-6925] Add Event story + playground

Description 📝
This PR is the first one of a series of tasks aimed to refactor our events (in JSX). Since it's tedious to test events by triggering an action in the UI, the story and playground will facilitate the refactor by ensuring we're not degrading the existing event messages
How to test 🧪

Pull code locally and navigate to http://localhost:6006/?path=/docs/features-events--documentation
Confirm the rendering of the event messages in the story complies with our existing formatting
Confirm the playground helps with crafting accurate event messages

@mjac0bs I have not been able to figure out how to get interfaces JSdoc comments to show up for interfaces imported from api-v4. will make a task for that too


[#15] [Android] [Integrate] As a user, I can see the job information in the job details page

https://github.com/nimblehq/android-kmm-showcases/issues/15
What happened 👀
As we're creating a demo to show job detail, the user should be able to read the details of a job, including price, location, time, etc before deciding to accept the jobs or not.
Insight 📝

Binding data from UiModel to Views

Proof Of Work 📹

@hoangnguyen92dn @lydiasama I updated the base branch to chore/13-restructure-app-modules-structure

@luongvo Sorry man, I've done binding views with the current schema. 🙈


Nothing happens when tryin beautify PHP

Description
Nothing happens when tryin beautify. Window with plugins logo appears, but thats it. No any action,
no errors, alerts.
Expected Results
The beautified code should have looked like: beautifyed code.
any code

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look like beautifyed code!

Debug
Here is a link to the debug.md https://gist.github.com/avknor/278500e4e81a642ccd19d49dde1a3bab
Checklist

[x] I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Generated debugging information and added link for debug.md Gist to this issue

Beautify my issue ;)

From the logs:

2016-04-14T08:45:28.755Z - debug: [beautifiers\beautifier.coffee] spawn C:\OpenServer\modules\php\PHP-5.5\php.EXE 0=C:\Users\KryukovAV.NPR\AppData\Roaming\Composer\vendor\bin\php-cs-fixer.BAT, 1=fix, 2=--level=Symfony, 3=C:\Users\KRYUKO~1.NPR\AppData\Local\Temp\temp116314-15428-ql2s46
2016-04-14T08:45:28.985Z - debug: [beautifiers\beautifier.coffee] spawn done 0  @ECHO OFF
setlocal DISABLEDELAYEDEXPANSION
SET BIN_TARGET=%~dp0/../fabpot/php-cs-fixer/php-cs-fixer
php "%BIN_TARGET%" %*

2016-04-14T08:45:28.985Z - verbose: [beautifiers\beautifier.coffee] spawn result 0 @ECHO OFF
setlocal DISABLEDELAYEDEXPANSION
SET BIN_TARGET=%~dp0/../fabpot/php-cs-fixer/php-cs-fixer
php "%BIN_TARGET%" %*
The issue is the same as found in #903.
See https://github.com/Glavin001/atom-beautify/issues/903#issuecomment-207074273 and the many other related issues that solve this problem :+1:.


chore: Return VC from student card API

It will be hard-coded for now, required by upstream components
Closes #9
Signed-off-by: Sandra Vrtikapa<EMAIL_ADDRESS>

patch set coverage is very low


Automatically add the "waiting: approval/rejection" label

... to PRs matching the following:

Are not draft PRs (i.e. ready for review status)
Are not waiting for author approval
Are passing CI
Are waiting for editor approval

Superseded by an issue I haven't made yet.

Superseded by #110


[.Net] [Internal ID]

Platform
What platform is your issue or question related to? (Delete other platforms).

.NET WPF

Explain your issue. If you just have a question, please post [on StackOverflow instead]
As working on inner show cards, i came across this issue where internal id are null for all elements.
fix is added via inner show card PR, but we need to re-visit and ensure that this works correctly.

@almedina-ms can you make sure that the element id design note includes this aspect of "internal" id's as well?


notes and others

I want to be able to quickly find a bookmark by name, url, topic or whatever.
Then see IF I have ever watched it before, and if so, when. Then, I want to know what I thought about it at certain points in time, i.e. notes ordered by date.


Network zones documentation

Updated and clarify the network zones documentation.

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.10107/

@ru-fu can you mark the specific comments as resolved after you've addressed them in changes? This makes it significantly easier to re-review the branch.

Sure, will do in the future.


Make NetDbg available on releaes builds

Autest quic_poll_timeout fails on release builds because the test relies on the debug output.

@ywkaras @zwoop My understanding is that the debug tag check is faster than before and this change does not affect performance as long as the debug tags are disabled.

[approve ci rocky]


Initial dump of Compositions alpha implementation

This is the initial dump of the Compositions code that we have been demoing in the weekly meetings.
Source: https://github.com/GoogleCloudPlatform/k8s-config-connector/tree/master/experiments/compositions
We want to follow up with commits to:

User guide
Setup precommit tests
Proposal/DesignNotes as a light weight KEP alternative

https://github.com/cloud-native-compositions/compositions/pull/8


enhancement: use enforcer to choose the n-th plan

Proposed changes
use enforcer to choose the n-th plan
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.01 seconds
stream load tsv:          515 seconds loaded<PHONE_NUMBER>9 Bytes, about 138 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          66 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>2 Bytes

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.2 seconds
stream load tsv:          518 seconds loaded<PHONE_NUMBER>9 Bytes, about 137 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.4 seconds inserted 10000000 Rows, about 340K ops/s
storage size:<PHONE_NUMBER>3 Bytes

run buildall


Chapter: Protect privacy

M = Maintainers (@rebeccawoodbury @lukefretwell @marlena-medford)
C = Contributors
Reference:

Chapter doc
Chapter website page
Questions? Ask in chapter doc using comments feature or via contact form

To do
Set-up

[ ] Review contributor request (M - @rebeccawoodbury, @lukefretwell @marlena-medford)
[ ] Create a new issue (M - @lukefretwell)
[x] Send contributors 'Welcome contributors' email (M - @rebeccawoodbury)
[ ] Schedule kick-off meeting (C)
[ ] Add @rebeccawoodbury @lukefretwell @Marlena-Medford to meeting invite (M - @rebeccawoodbury)
[ ] Meet for kick-off (C / M - @rebeccawoodbury @lukefretwell @marlena-medford)
[ ] Create new chapter doc from chapter template (M - @rebeccawoodbury)
[ ] In file title and doc h1, replace 'TITLE' with the title of the chapter (example chapter) (M - @rebeccawoodbury)
[ ] Add link to GitHub issue in chapter doc (@rebeccawoodbury)
[ ] Share edit rights with contributors and maintainers (M - @rebeccawoodbury)
[ ] Create chapter Slack channel, invite contributors (M - @lukefretwell)
[ ] Set two-week [calendar deadline reminder for writing chapter draft (+ add contributors in Proudly Serving calendar / template text - (Chapter draft done: [TITLE] - set for 8:00-8:15 a.m. Pacific Time) (M - @rebeccawoodbury)
[ ] Add doc link to this issue 'Reference' above (M - @lukefretwell)
[ ] Review style guide (C)
[ ] Review code of conduct (C)
[ ] Take the Proudly Serving pledge (team agreement)
[ ] Send contributors 'Kick-off follow-up' email (M - @rebeccawoodbury)

Write draft

[ ] Add bios/social media links to ‘Contributors’ section (C)
[ ] Complete first draft (2 weeks after kick-off)  (C)
[ ] When ready for review, highlight doc h1, add a ‘Ready for review’ comment and assign it to<EMAIL_ADDRESS>(C)
[ ] Set one-week calendar deadline reminder for maintainer review (+ add contributors in Proudly Serving calendar / template text) - (Public feedback done: [TITLE] - set for 8:00-8:15 a.m. Pacific Time) (M - @rebeccawoodbury)
[ ] Review/edit/comment (M - @rebeccawoodbury, @lukefretwell @marlena-medford)
[ ] Notify contributors to review/approve final edits (M - @rebeccawoodbury)
[ ] When ready for public feedback, highlight doc h1, add a ‘Ready for feedback' comment and assign it to<EMAIL_ADDRESS>(C)
[ ] Set up chapter page on website, add to GitHub issue (example) (M - @lukefretwell)

Promote feedback

Content templates

[ ] Blog (M - @rebeccawoodbury)
[ ] Substack (M - @rebeccawoodbury)
[ ] Twitter (M - @marlena-medford)
[ ] LinkedIn (M - @marlena-medford)
[ ] Send email to Contributor asking them to help promote on social (M - @rebeccawoodbury)
[ ] Share on social (C)
[ ] Set one-week calendar deadline reminder for public feedback (+ add contributors in Proudly Serving calendar / template text) (M - @rebeccawoodbury)

Finalize feedback

[ ] Set one-week calendar deadline reminder to finalize chapter (+ add contributors in Proudly Serving calendar / template text) (M - @rebeccawoodbury)
[ ] Respond to all comments and incorporate where appropriate (C)
[ ] When ready for final publish, highlight doc h1, add a ‘Ready to publish' comment and assign it to<EMAIL_ADDRESS>(C)
[ ] Review for copy edits ( M - @marlena-medford)
[ ] Deprecate doc (set to view only, add ‘This document has been deprecated. Visit the Proudly Serving website (https://proudlyservingbook.com/) to learn how to give feedback on this chapter.‘) (M - @lukefretwell)

Publish

[ ] Add contributor(s) to contributor list (doc/website (M - @lukefretwell)
[ ] Doc (M - @lukefretwell)
[ ] Update chapter page on website (M - @lukefretwell)
[ ] Add to /contents page (M - @lukefretwell)

Promote published

Content templates

[ ] Twitter (M - @marlena-medford)
[ ] LinkedIn (M - @marlena-medford)
[ ] Blog (M - @rebeccawoodbury)
[ ] Substack (M - @rebeccawoodbury)
[ ] Send email to Contributor asking them to help promote on social (M - @rebeccawoodbury)
[ ] Share on social (C)
[ ] Send contributors 'Thank you' email (M - @rebeccawoodbury)

dupe of #127


Target creation from toxid should filter by polarity

At the moment it is taking all, but noticed that the files look like:

36,L-Lysine,C6H14N2O2,+,,18.35,1000,1,,,,,
37,L-Arginine,C6H14N4O2,+,,19.93,1000,1,,,,,
38,Phenolsulfonphthalein,C19H14O5S,-,,5.69,1000,1,,,,,
39,Thymidine,C10H14N2O5,-,,6.45,1000,1,,,,,

And therefore include both +ve and -ve entries. Makes no sense to look for -ve entries in +ve mode data? @RonanDaly am I interpreting the files correctly?

Yes, the ToxID files have both polarities.

so, we would only look for + examples in positive acquisition, right?

Yes - that's not to say that it doesn't ionise in negative mode, just that it was never entered into the configuration file - generally the most reliable peak is used, but sometimes both modes are good.

So, in terms of creating a library of MS2 should we include the -ve ones in +ve mode or not?


jdk_custom_0 issue

jdk_custom allows users to set their own CUSTOM_TARGET. But running TARGET=jdk_custom_x (with any suffix) is invalid.
When a user sets TARGET=jdk_custom_0 , the pipeline will try to map it to ${TARGET.toUpperCase()}_TARGET. That is JDK_CUSTOM_0_TARGET
18:13:39  + make _jdk_custom_0 JDK_CUSTOM_0_TARGET=java/lang/Thread/virtual/stress/PinALot.java#id0

But the param that we are replacing is  JDK_CUSTOM_TARGET - java/math/BigInteger/BigIntegerTest.java.
https://github.com/adoptium/aqa-tests/blob/master/openjdk/openjdk.mk#L132
As a result, the Grinder will run the default test BigIntegerTest regardless of the user-provided CUSTOM_TARGET value.
When this happens, there is no clear indication in the console output, especially when the default test passes.
https://openj9-jenkins.osuosl.org/view/Test/job/Grinder/2178/
Even in raw TAP file, it shows CUSTOM_TARGET=java/lang/Thread/virtual/stress/PinALot.java#id0[1], but we actually run
16:42:48  F:/Users/jenkins/workspace/Grinder/aqa-tests/\\openjdk\\openjdk-jdk\\test\\jdk\\java/math/BigInteger/BigIntegerTest.java; \

[1]
# AQACert.log content:
#
# Hostname: win2019-x64-5

#SHA.txt content:
#
# Timestamp: Tue Apr  4 21:25:04 2023 UTC
# CUSTOM_TARGET: java/lang/Thread/virtual/stress/PinALot.java#id0
1..1
ok 1 - jdk_custom_0
  ---
    success rate: 20/20
    duration_ms: 2535798
  ...

We should update the logic to ensure JDK_CUSTOM_TARGET is set correctly. Otherwise, it will be really hard for the users to notice the problem.

The behaviour in this case could be that we accept no suffix after jdk_custom (or any xxxx_custom targets), since they are a unique type of target, that we should also never allow variations in the playlists for (as in remove https://github.com/adoptium/aqa-tests/blob/master/openjdk/playlist.xml#L19-L23).
I often use TARGET=jdk_custom with CUSTOM_TARGET left blank to automatically run a very short test.  The other option here to protect the user from themselves would be to always enforce the need to set CUSTOM_TARGET if using a TARGET that contains '_custom', but that would not be my preference (and does not resolve the current situation being reported).


Documentation downloads not available for 25.1

Hi. Documentation downloads seem to not be available for 25.1 at https://erlang.org/download/. The latest version available is otp_doc_html_25.0.tar.gz. Could they be added?

Yes, they probably should. In the meantime, you can also download them from the github release: https://github.com/erlang/otp/releases/tag/OTP-25.1

I will have a look on why it is missing


Added instructions to build CmdStan utilities.

Improved makefile help text by adding instructions for using 'make build' to build CmdStan utilities used by MatlabStan and JuliaStan.

Thanks!

Jenkins, test this please.


revoke_invitations: Revoke remaining invitations after user register.

If a user receives more than one invitation to join
an organization and accepts one of them, the others
will still be listed in the admin board.
Fixes: #12629

Testing Plan:
GIFs or Screenshots:

This issue was more complicated than I initially thought.
So, the problem was: if a user has received multiple invites to join an organization at Zulip and accepted one of the invitations, the others kept showing at the listing on the admin board of invitations. This happened because when the user accepted one invite and registered, the process_new_human_user function would set all the other PreregistrationUser objects as inactive, which in turn, would make the do_get_user_invites() to return a list of all prereg_users who doesn't have status STATUS_ACTIVE, which means that it would include the PreregistationUser objects that were just deactivated due to user registration.
    # Mark any other PreregistrationUsers that are STATUS_ACTIVE as     # inactive so we can keep track of the PreregistrationUser we     # actually used for analytics     if prereg_user is not None:         PreregistrationUser.objects.filter(email__iexact=user_profile.delivery_email).exclude(             id=prereg_user.id).update(status=0)
`
def do_get_user_invites(user_profile: UserProfile) -> List[Dict[str, Any]]:
days_to_activate = settings.INVITATION_LINK_VALIDITY_DAYS
active_value = getattr(confirmation_settings, 'STATUS_ACTIVE', 1)
lowest_datetime = timezone_now() - datetime.timedelta(days=days_to_activate)
prereg_users = PreregistrationUser.objects.exclude(status=active_value).filter(
    invited_at__gte=lowest_datetime,
    referred_by__realm=user_profile.realm)

`
My first idea was to just delete those other PreregistrationUser that weren't used by the user to register, but that made the test_signup_two_confirmation_links() because the expected behaviour was that when a user created in a link other than the used to register, it should redirect to the login page.
Then I thought about modifying the query that returns the invitations not used yet, but it would be slower I guess. Because I would need to get all the prereg_users that aren't STATUS_ACTIVE and then filter those that aren't related to any registered user.
Finally, I thoght that the best approach would be to create a new status for prereg_users that indicates that that invitation was inactive because that user already registered. It works fine now, but I didn't understood the process of creating a new status, so I just put a magic number 2. Can someone please explain me how should I do this? Is this approach really the best?
@timabbott @rishig

that made the test_signup_two_confirmation_links() to crash because the expected behaviour was that when a user created in a link other than the used to register, it should redirect to the login page.

That test was added in this commit, mainly for coverage of that one line in accounts_register
https://github.com/zulip/zulip/pull/13360/commits/e7939bbb5a38ca7666e82ead7312ff0e667d75cf
and I think should be just changed to test whatever the new correct behavior will be. That may lead to that one line losing coverage, but it can be quickly fixed by writing another tests mocking validate_email_for_realm to raise ValidationError.
Not sure what approach is best, but if the PreregistrationUser is just deleted, it'll automatically delete the Confirmation object, and possibly lead to erroring out here in the registration flow?
@require_post
def accounts_register(request: HttpRequest) -> HttpResponse:
    key = request.POST['key']
    confirmation = Confirmation.objects.get(confirmation_key=key)

which actually brings attention to the fact that we don't do any exception handling here (the get can raise Confirmation.DoesNotExist) - shouldn't that be added here? @timabbott

Yes, if the other PreregistrationUser are deleted, and then some another generated confirmation link is clicked it leads to an error. And the way it is right now, if that happens, the user is redirected to the login page or the chat if the user is already logged.

Finally, I thoght that the best approach would be to create a new status for prereg_users that indicates that that invitation was inactive because that user already registered. It works fine now, but I didn't understood the process of creating a new status, so I just put a magic number 2.

I think this is a good direction after all. It looks like it should be enough to add STATUS_REVOKED = 2 to confirmation/settings.py and use that, to have this done properly.
@arunikayadav42 Do you want to take over finishing this PR?

Sure @mateuszmandera

@zulipbot claim

@mateuszmandera how do I take over this PR? Do I make a new PR referring to this PR after making the necessary changes?

I have created a pull request @mateuszmandera . But somehow my build failed and I am not sure why. I want to create a new issue hence abandoning this . Will keep working on this one. https://github.com/zulip/zulip/pull/14003

@zulipbot abandon

@clarammdantas Posted some comments, could you address them and fix the commit structure? I remember the context around these changes, so I'm able to review from the "Files changed" view, but it'll be confusing for Tim to review without breaking it down into clearer logical steps. Should probably be 3 commits, first two that I commented above on tests, and then the third one with the "real" changes.

@mateuszmandera I've fixed the PR and commit history :)
@timabbott could you take a look at this, please?

Also, Arunika is not appearing as an author on commits after I fixed the history. What can I do to credit her for her work?

Also, Arunika is not appearing as an author on commits after I fixed the history. What can I do to credit her for her work?

git commit --amend --author=... if you want to set her as primary author on any of these commits, and https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors#creating-co-authored-commits-on-the-command-line to set her or yourself as co-author.
Posted a couple of comments, I think this should be ready after they're fixed :slightly_smiling_face:

Co-authored-by isn't right I think, the right format is to with the email inside <>. It'll show Arunika as a co-author in the github UI when it's correct.

Look good to me now. @timabbott Can you review next?

@clarammdantas can you rebase?  I think this conflicts with your other PR that I just merged, so you'll likely be faster than me at rebasing.

@clarammdantas can you rebase? I think this conflicts with your other PR that I just merged, so you'll likely be faster than me at rebasing.

Sure!

It looks like this is failing CI with a relevant test; can you investigate?

It looks like this is failing CI with a relevant test; can you investigate?

Yes, I'm doing that.

This is great, merged, thanks @clarammdantas!


IPython's --no-confirm-exit flag screws with importing kivy somehow

ipython is able to import kivy just fine:
$ ipython
Python 3.5.1 (default, Dec  7 2015, 12:58:09)
Type "copyright", "credits" or "license" for more information.

IPython 4.0.1 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import kivy
[INFO              ] [Logger      ] Record log in /home/jacko/.kivy/logs/kivy_16-01-15_14.txt
[INFO              ] [Kivy        ] v1.9.1
[INFO              ] [Python      ] v3.5.1 (default, Dec  7 2015, 12:58:09)
[GCC 5.2.0]

In [2]:

But if I invoke IPython with --no-confirm-exit, the import causes an error for some reason:
$ ipython --no-confirm-exit
Python 3.5.1 (default, Dec  7 2015, 12:58:09)
Type "copyright", "credits" or "license" for more information.

IPython 4.0.1 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import kivy
[INFO              ] [Logger      ] Record log in /home/jacko/.kivy/logs/kivy_16-01-15_12.txt
[ERROR             ] [Core        ] option --no-confirm-exit not recognized
Kivy Usage: ipython [OPTION...]::

        -h, --help
            Prints this help message.
        -d, --debug
            Shows debug log.
        -a, --auto-fullscreen
            Force 'auto' fullscreen mode (no resolution change).
            Uses your display's resolution. This is most likely what you want.
        -c, --config section:key[:value]
            Set a custom [section] key=value in the configuration object.
        -f, --fullscreen
            Force running in fullscreen mode.
        -k, --fake-fullscreen
            Force 'fake' fullscreen mode (no window border/decoration).
            Uses the resolution specified by width and height in your config.
        -w, --windowed
            Force running in a window.
        -p, --provider id:provider[,options]
            Add an input provider (eg: ccvtable1:tuio,<IP_ADDRESS>:3333).
        -m mod, --module=mod
            Activate a module (use "list" to get a list of available modules).
        -r, --rotation
            Rotate the window's contents (0, 90, 180, 270).
        -s, --save
            Save current Kivy configuration.
        --size=640x480
            Size of window geometry.
        --dpi=96
            Manually overload the Window DPI (for testing only.)

An exception has occurred, use %tb to see the full traceback.

SystemExit: 2

To exit: use 'exit', 'quit', or Ctrl-D.

In [2]:

Ah, I can see what's happening:
[ERROR             ] [Core        ] option --no-confirm-exit not recognized

Kivy is interpreting IPython's flags as its own, by reading sys.argv, and then getting confused by a flag that it doesn't understand. Why is it doing that?

Either your version of IPython doesn't accept that argument, or IPython is leaving that argument in sys.argv. If IPython accepts the argument, it should be removing it from sys.argv - this is an IPython issue.

Thanks, I filed another issue with IPython.
On Fri, Jan 15, 2016 at 4:08 PM, Ryan Pessa<EMAIL_ADDRESS>wrote:

Closed #3918 https://github.com/kivy/kivy/issues/3918.
—
Reply to this email directly or view it on GitHub
https://github.com/kivy/kivy/issues/3918#event-516629003.


Swipe Exception for 'gallery-card'

Could you please make also an exception for 'gallery-card'? See https://github.com/TarheelGrad1998/gallery-card
Thanks in advance!

Yes, I'll add this in the next release. =)

Sorry for the delay. Can you test the last pre-release (v1.12.0)? Everything should be working.

Perfect! It wasn't immediately effective on my mobile, though I had cleared the cache. But some time later it is now working flawless.


Error: could not load

When try run /usr/bin/gitlab-ci-rake or /usr/bin/gitlab-ci-rails I get this error:
/usr/bin/gitlab-ci-rake error: could not load /opt/gitlab/etc/gitlab-ci/gitlab-ci-rc
You can generate it with:   sudo gitlab-ctl reconfigure

Any idea how solve it? Thanks.

How did you install CI?

Solved the issue, thanks @vsizov :+1:
I downloaded wrong OS (Debian) version of gitlab.


Some create document design changes

Move case details to site alongside back button (and remove bold text)
Make the insert skip button primary
Move the draft save buttons inline

I also fixed an issue where "HW" LPAs weren't getting the subtype shown in the case details.
Fixes VEGA-1724 #patch

Codecov Report
Patch and project coverage have no change.

Comparison is base (17fd1b0) 72.94% compared to head (4fcc0c7) 72.94%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #291   +/-   ##
=======================================
  Coverage   72.94%   72.94%
=======================================
  Files          88       88
  Lines        3474     3474
=======================================
  Hits         2534     2534
  Misses        674      674
  Partials      266      266

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Removing unused unnecessary imports

Signed-off by: Sergio Escalante<EMAIL_ADDRESS>

The CI failed because of:
[ERROR] Failed to execute goal org.owasp:dependency-check-maven:3.3.2:check (default) on project aws-serverless-java-container-core:
[ERROR]
[ERROR] One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '7.0':
[ERROR]
[ERROR] slf4j-api-1.7.25.jar: CVE-2018-8088
[ERROR]
but that error is not related to the changes in the PR

Agree. Thanks for the PR. I'll fix the dependencies over the next couple of days and merge your PRs for the next release.

I've merged the changes into the core branch where I'm working on the next release.


Final Touch: Link in the crash info box

overview
The link in the crash info box (from #4410) doesn't go anywhere yet

@howisthisnamenottakenyet please provide links for the separate articles once they're posted

@IanLondon https://docs.google.com/document/d/1kE8qwlx6jVoPmWe0AwNmHVbnDNa4RHnoLCcDTt0SA1s/edit?usp=sharing


docs: Update api-check construct's doc url to lead to correct url

I hereby confirm that I followed the code guidelines found at engineering guidelines
Affected Components

[ ] CLI
[ ] Create CLI
[ ] Test
[x] Docs
[ ] Examples
[ ] Other

Notes for the Reviewer
Actual behavior:
Current doc link leads to a 404 page:

Expected/Proposed behavior:
Link leads to a correct page:

@MikulasMascautanu thanks for reporting this. We are about to release a massive update on our docs and the links should start working again. For that reason I'm closing this PR, but much appreciated anyway.

@MikulasMascautanu thanks for reporting this. We are about to release a massive update on our docs and the links should start working again. For that reason I'm closing this PR, but much appreciated anyway.

@tnolet Oooh, I had that feeling when I glanced through open PRs before doing this one. Good news anyway!


ROX-9094: Create tasks for failing tests

To collect more information about common test failures lets collect them in JIRA tickets.
junit2jira is a small binary the investigate given path and searches for junit xml reports.
It creates issue for every failed test or if issue already exists it adds a comment with all details.
This is a prototype of integration as proper integration will be implemented after migrating to GHA.

/retest

@gavin-stackrox PTAL


CNCF annual review: implement requested changes

This comment provides clear instructions about issues the Kubewarden project must address in order to comply with CNCF standards.
Actions

[x] #678
[ ] #684
[ ] #685
[ ] #686
[ ] Write a GOVERNANCE.md file
[x] Begin tracking adopters.
[x] Make use of GitHub Milestones

For the governance, we already have https://github.com/kubewarden/rfc/blob/main/rfc/0013-governance.md. We can deprecate it and copy it into kubewarden/community.


Log level for package org.wso2.carbon.mediation.dependency.mgt.DependencyTracker shouldn't be INFO

Seeing a lot of logs of this package at the startup:
[2017-05-22 11:51:44,785] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--SCEP Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:44,786] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--SCEP Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:44,824] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--SCEP Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:44,825] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--SCEP Management was added to the Synapse configuration successfully
[2017-05-22 11:51:45,214] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Device Management Administrative Service:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:45,214] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Device Management Administrative Service:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:45,241] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Device Management Administrative Service was removed from the Synapse configuration successfully
[2017-05-22 11:51:45,243] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Device Management Administrative Service was added to the Synapse configuration successfully
[2017-05-22 11:51:45,610] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Configuration Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:45,610] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Configuration Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:45,637] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Configuration Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:45,637] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Configuration Management was added to the Synapse configuration successfully
[2017-05-22 11:51:45,990] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Binary Security Token Service:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:45,990] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Binary Security Token Service:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:46,017] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Binary Security Token Service was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,017] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Windows Binary Security Token Service was added to the Synapse configuration successfully
[2017-05-22 11:51:46,309] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAccessAuthorizationAdminService:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,309] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAccessAuthorizationAdminService:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:46,335] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAccessAuthorizationAdminService was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,335] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAccessAuthorizationAdminService was added to the Synapse configuration successfully
[2017-05-22 11:51:46,609] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagementAdmin:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,609] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagementAdmin:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:46,629] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagementAdmin was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,629] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagementAdmin was added to the Synapse configuration successfully
[2017-05-22 11:51:46,902] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ActivityInfoProvider:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,903] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ActivityInfoProvider:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:46,926] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ActivityInfoProvider was removed from the Synapse configuration successfully
[2017-05-22 11:51:46,926] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ActivityInfoProvider was added to the Synapse configuration successfully
[2017-05-22 11:51:47,241] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--RoleManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:47,241] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--RoleManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:47,260] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--RoleManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:47,260] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--RoleManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:47,561] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:47,561] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:47,583] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:47,583] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:47,879] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ConfigurationManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:47,879] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ConfigurationManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:47,902] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ConfigurationManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:47,902] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ConfigurationManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:48,235] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DevicePolicyManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:48,235] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DevicePolicyManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:48,257] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DevicePolicyManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:48,257] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DevicePolicyManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:48,571] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:48,571] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:48,591] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:48,592] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:48,855] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagementAdmin:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:48,856] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagementAdmin:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:48,873] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagementAdmin was removed from the Synapse configuration successfully
[2017-05-22 11:51:48,874] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--UserManagementAdmin was added to the Synapse configuration successfully
[2017-05-22 11:51:49,202] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,202] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:49,225] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,226] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:49,479] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAnalyticsArtifactUploaderAdminService:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,479] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAnalyticsArtifactUploaderAdminService:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:49,501] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAnalyticsArtifactUploaderAdminService was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,501] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceAnalyticsArtifactUploaderAdminService was added to the Synapse configuration successfully
[2017-05-22 11:51:49,779] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceTypeManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,779] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceTypeManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:49,799] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceTypeManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,799] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceTypeManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:49,997] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ApplicationManagementAdmin:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:49,997] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ApplicationManagementAdmin:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:50,013] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ApplicationManagementAdmin was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,013] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--ApplicationManagementAdmin was added to the Synapse configuration successfully
[2017-05-22 11:51:50,258] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagementAdmin:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,259] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagementAdmin:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:50,276] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagementAdmin was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,276] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--GroupManagementAdmin was added to the Synapse configuration successfully
[2017-05-22 11:51:50,487] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceNotificationManagement:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,487] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceNotificationManagement:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:50,503] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceNotificationManagement was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,503] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--DeviceNotificationManagement was added to the Synapse configuration successfully
[2017-05-22 11:51:50,752] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Operation Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,752] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Operation Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:50,774] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Operation Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:50,774] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Operation Management was added to the Synapse configuration successfully
[2017-05-22 11:51:51,030] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Configuration Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:51,030] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Configuration Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:51,050] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Configuration Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:51,050] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Configuration Management was added to the Synapse configuration successfully
[2017-05-22 11:51:51,438] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management Administrative:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:51,438] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management Administrative:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:51,455] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management Administrative was removed from the Synapse configuration successfully
[2017-05-22 11:51:51,455] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management Administrative was added to the Synapse configuration successfully
[2017-05-22 11:51:51,856] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:51,857] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:51,874] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:51,874] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--iOS Device Management was added to the Synapse configuration successfully
[2017-05-22 11:51:52,155] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management Administrative Service:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,155] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management Administrative Service:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:52,171] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management Administrative Service was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,172] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management Administrative Service was added to the Synapse configuration successfully
[2017-05-22 11:51:52,435] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Event Receiver:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,435] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Event Receiver:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:52,451] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Event Receiver was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,452] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Event Receiver was added to the Synapse configuration successfully
[2017-05-22 11:51:52,700] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,700] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:52,718] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,718] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Device Management was added to the Synapse configuration successfully
[2017-05-22 11:51:52,939] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Configuration Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,939] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Configuration Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:52,955] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Configuration Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:52,955] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Android Configuration Management was added to the Synapse configuration successfully
[2017-05-22 11:51:53,268] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Certificate Management:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:53,268] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Certificate Management:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:53,282] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Certificate Management was removed from the Synapse configuration successfully
[2017-05-22 11:51:53,283] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--Certificate Management was added to the Synapse configuration successfully
[2017-05-22 11:51:53,486] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--android_sense:v1.0.0 was removed from the Synapse configuration successfully
[2017-05-22 11:51:53,486] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--android_sense:v1.0.0 was added to the Synapse configuration successfully
[2017-05-22 11:51:53,501] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--android_sense was removed from the Synapse configuration successfully
[2017-05-22 11:51:53,502] [IoT-Core]  INFO - {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} API : admin--android_sense was added to the Synapse configuration successfully

As this is an informative log where it confirms the API publishing is successfully performed, this needs to be as info logs. Additionally, as this logs are not generated during the runtime operation, it's not harmful or will not fill the disk space.


fix(gateway): rpc_state_reader should return 0 for undeployed contract address

#1789  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Yael-Starkware and the rest of your teammates on  Graphite


Skype for Linux: autostart doesn't work

Skype creates .desktop file with pre-hardcoded path to its binary in /usr/bin. /usr/bin is empty on NixOS and the path needs to be retrieved programmatically instead of being hardcoded.
https://answers.microsoft.com/en-us/skype/forum/sk_acc-sk_settings-sk_linux/skype-for-linux-autostart-doesnt-work-on-nixos/c800a127-49b4-4994-92ea-ab28a284141f
Most likely there is no sane way to fix that on Nix because the source code is not available, though I may be wrong.

Tixati on portable mode has an issue like this. It creates a desktop file on ~/.local/share/applications.
It's annoying AF and the best you can do now is to ignore the shortcut or delete it every time.
For autostart I recommend using the DE/WM provided way passing the command of the program, user systemd units are also an option and are used for apps like flameshot.

I know how to make workarounds, all my life is one big workaround.
Though I still believe that it's good when something what is intended to work works.

You can do it like this:
{
  system.activationScripts.skype = ''
    mkdir -p /usr/bin
    ln -fs /run/current-system/sw/bin/whatever-the-name-is /usr/bin/whatever-the-name-ist
  '';
}


[Part 3 & 4] Tabular: API Refactor

Issue #, if available:
Description of changes:
This PR is part 3 and 4 of the API refactor logic:

[x] Add documentation to __init__
[x] Add documentation to fit
[x] Add documentation to fit_extra
[ ] Resolve all remaining TODOs in TabularPredictor
[ ] Finalize API

Part 1: Majority of logic changes #768
Part 2: Migrate unit tests to use new API #855
Part 3: Remainder of logic changes + deprecate old API (Old API incompatible with the more complex logic changes without significant effort)
Part 4: Documentation of new API
Part 5: Removal of old Tabular API
Part 6: Update Text API to align with new API
Part 7: Update Vision API to align with new API
Part 8: Add tutorials for new functionality
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Left some more comments on docs.
One question is: do we still need task/tabular_prediction/ directory structure?
If we already have autogluon/tabular/... then it does not seem to me that we require task anymore, especially since TabularPredictor does not really sound like a "task". Will future docs/tutorials still be referring to Tabular as a task?

Regarding directory structure: This will be changed in a follow-up PR. We will be removing the task directory name.

Left some more comments on docs.
One question is: do we still need task/tabular_prediction/ directory structure?
If we already have autogluon/tabular/... then it does not seem to me that we require task anymore, especially since TabularPredictor does not really sound like a "task". Will future docs/tutorials still be referring to Tabular as a task?

Regarding directory structure: This will be changed in a follow-up PR. We will be removing the task directory name.

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

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


Adding rbac-lookup package

rbac-lookup is a simple CLI tool that's essentially reverse lookup for RBAC. It allows you to easily find roles and cluster roles attached to any user, service account, or group name in your Kubernetes cluster.

Also thanks to @ahmetb for all the work on Krew to add support for tar.gz files.

@robscott thanks for submitting your plugin to krew. 🎊
The .tar.gz patch is currently not in a tagged release. We're planning to ship it in v0.2 (which accommodates breaking changes introduced with kubectl-1.12 plugin model). This may be still a week out.
Also, we made a breaking change to the plugin YAML format (introduced a bin: field) that specifies the executable of your plugin that krew should symlink for. It will also ship in krew v0.2 (see https://github.com/GoogleContainerTools/krew/issues/33 for progress).

hi @robscott as we're migrating to kubectl 1.12, I think we can now start taking this plugin in. A few things to note about kubectl 1.12 migration:

kubectl will no longer pass you environment variables (to determine namespace etc)
kubectl will no longer use your plugin.yaml (krew will symlink to the right location)
krew now requires a bin field under the platforms field (see DEVELOPER_GUIDE.md).

Let us know if you have any questions.

Thanks @ahmetb! I've made the requested changes to upgrade to v1alpha2, excited for krew 0.2.

Works great! Hope we can prep a release soon so you can distribute it with Krew as well. 🙌


Question:XML3DRotation.setRotation

The manual says that function XML3DRotation.setRotation does following thing.

Replaces the existing rotation with one computed from the two vectors passed as arguments.

How one should understand that?
How the rotation is computed from those two vectors?
Also could you clarify how multiply function works on example - i'm getting some unexpected results with this. (That is the rotations are performed in different order that I get from text):
Lets say i have following code:
camera.orientation =  rot0.multiply(rot1)

Which rotation affects the camera first?

setRotation is usually called fromTo in other math libraries. It computes  the rotation needed to rotate the first vector to be parallel to the second vector. This is useful if you have a camera looking in direction a and want to rotate it to look in direction b for example.
In your example rot0 will be multiplied with rot1 and then the camera's orientation will be set to the result of that multiplication (which will be a new XML3DRotation object). The multiplication order is the same as the text order, so rot0 * rot1.


Revert "Avoid failure in populate_fraction_subsampled.rake"

See if it fixes the build.
Boris, you'll have to reapply "redis locks are no longer necessary"

Making this change indeed fixed the build.


📝 update bookmark styling

Problem
Bookmark styling has some layout issues, like this.

Resolve
Remove .bookmark:nth-child(3n) and adjust the bookmark card width to a more suitable size.
Feature
Bookmark hover effect

[x] Light mode
[x] Dark mode

👍👍👍 合适 看起来不错


Trains's macropad!

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
If you're unsure about the format, make sure to check out the Orpheuspad example and follow the format there.
If this PR isn't a submission, that's okay too! If there's anything about this PR template that seems confusing, let me know in #hackpad on the slack!

I made this on a different repository that was not a fork, so I'm currently just going to the root and doing all of it manually. Please let me do this!

should be good, try again?


need to refresh list of testimonies in MyTestimonies after editing or deleting testimony

Currently this table does not update after testimony is updated or deleted

after an edit, the Text field should update
after a delete the entire testimony line should be removed

https://user-images.githubusercontent.com/67333843/157951429-470e1567-8b78-4b46-91d1-893a974a4ec2.mov


Determine the code block responsible for including the python native docs to the API docs page. Make changes to include the python native docs, build and test locally.

Closing as duplicate of https://github.com/tudat-team/tudatpy/issues/144


#8 Fix clean task

Changes licensed Apache 2.0.
jhansen2015/AboutLibraries#8

thank you very much for your PR


How to calculate focal length?

Hi,
I want to know focal length.
Is it possible to calculate focal length from FOV and image size?
Or is there a fixed value of it?
Thanks in advance

I don't think there's focal length on the current camera, since no blur effect is found in any pixel, regardless of distance of the object.

I found it in P matrix thanks

@neokratia can you please share where the P matrix is that you mention?

@neokratia  Where did you find the P matrix?

@SAmmarAbbas @YashBansod  try #56

How about the calculation of focal length in carla 0.9.x?


Failed: Deploying service web

Bicep version
0.16.2
Describe the bug
Deploying services (azd deploy)
(x) Failed: Deploying service web
ERROR: failed building service 'web': failing invoking action 'build', building container: web at .: building image: exit code: 1, stdout: , stderr: ERROR: failed to solve: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount2859843998/Dockerfile: no such file or directory
: exit code: 1, stdout: , stderr: ERROR: failed to solve: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount2859843998/Dockerfile: no such file or directory
: exit status 1
To Reproduce
Steps to reproduce the behavior:

ran provision from VS Code
received error when selecting Deploy  from the Azure.Yaml file

Additional context
Web.bicep
param name string
param location string = resourceGroup().location
param tags object = {}

param applicationInsightsName string
param containerAppsEnvironmentName string
param containerRegistryName string
param imageName string = ''
param serviceName string = 'web'

module app '../core/host/container-app.bicep' = {
  name: '${serviceName}-container-app-module'
  params: {
    name: name
    location: location
    tags: union(tags, { 'azd-service-name': serviceName })
    containerAppsEnvironmentName: containerAppsEnvironmentName
    containerRegistryName: containerRegistryName
    env: [
      {
        name: 'APPLICATIONINSIGHTS_CONNECTION_STRING'
        value: applicationInsights.properties.ConnectionString
      }
      {
        name: 'PORT'
        value: '80'
      }
      {
        name: 'NODE_ENV'
        value: 'production'
      }
    ]
    imageName: !empty(imageName) ? imageName : 'nginx:latest'
    targetPort: 80
  }
}

resource applicationInsights 'Microsoft.Insights/components@2020-02-02' existing = {
  name: applicationInsightsName
}

output SERVICE_WEB_IDENTITY_PRINCIPAL_ID string = app.outputs.identityPrincipalId
output SERVICE_WEB_NAME string = app.outputs.name
output SERVICE_WEB_URI string = app.outputs.uri
output SERVICE_WEB_IMAGE_NAME string = app.outputs.imageName

-- web.parameter.json
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {
    "location": {
      "value": "${AZURE_LOCATION}"
    },
    "name": {
      "value": "${SERVICE_WEB_NAME}"
    },
    "imageName": {
      "value": "${SERVICE_WEB_IMAGE_NAME}"
    },
    "applicationInsightsName": {
      "value": "${APPLICATIONINSIGHTS_NAME}"
    },
    "containerAppsEnvironmentName": {
      "value": "${AZURE_CONTAINER_ENVIRONMENT_NAME}"
    },
    "containerRegistryName": {
      "value": "${AZURE_CONTAINER_REGISTRY_NAME}"
    }
  }
}

AZURE.YAML
# yaml-language-server: $schema=https://raw.githubusercontent.com/Azure/azure-dev/main/schemas/v1.0/azure.yaml.json

name: azure-remix-stack
services:
  web:
    language: ts
    project: './src/web/GlyphEditor'
    module: app/web
    host: containerapp

From the repro steps and the error message, I think this is an issue with azd. Bicep compilation doesn't use Docker buildkit, and I don't see anything wrong with the Bicep template included in the issue description.
Could you open an issue with azd at https://github.com/Azure/azure-dev/issues/new/choose ? I can't transfer the issue directly to them.


Fix #76 : Update Twitter logo

Hello,
Hope you're doing well
I would like to work on issue #76 too
After making necessary changes, the twitter logo looks something like this in the html pages:
Light Mode:

Dark Mode:

Kindly go through the code changes and let me know if they seem to be fine
Sincere apologies for my mistakes if you find any
Thanks and Regards,
Mohit Kambli

Reviwed Your code It works fine @MohitKambli Don't forget to star the repo and Happy Coding 😄


Go to definition not work

Hi!
I tried to use option+up or option+click but I couldn't go to definition. Could you resolve this issue?
Thanks!

Confirming I am having this problem as well on both Ubuntu 14.04 and Windows 7. When I hover, the word is underlined, but clicking it does nothing.

Hi,
I will certainly need more information. Please, try this:

Restart Atom
Open your Elixir/Mix project (in case it's not opened yet)
Hit ALT+CMD+i to open the console (ALT+CTRL+i on windows/linux, i guess). You should see something like:

[atom-elixir] Initializing alchemist-server for environment "dev" (Elixir version 1.2.0)

If you don't see that, you should see some error message from the alchemist-server. If that's the case, please let me know what the message looks like.
In case the server is has successfully started, make sure your project compiles. Most of the features of atom-elixir only works if you have the related .beam files in the _build folder.

Thanks.

We got the following when trying to navigate to Evergent.authenticate when having a alias Account.Evergent.
[atom-elixir] Initializing alchemist-server for environment "dev" (Elixir version 1.2.4)

server-process.coffee:149 [Server] DEFL { "Evergent,authenticate", "/Users/fyranadm/Code/account/web/controllers/authentication_controller.ex", "/var/folders/15/rt5286951s3c_pxdp98kwbwm0000gn/T/bqu4gssvc", 12 }

If the server has started and your files were successfully compiled, there's no reason not to work. Is it possible for any of you to push to github a minimal project simulating the problem?
Thanks.

+1 on OSX

There's a new version v0.2.1. Please, update and check if the problem is gone. Also remember to restart Atom after update or hit CTRL+ALT-CMD-L on mac.
Thanks for reporting the issue.

Closing this in favor of https://github.com/msaraiva/atom-elixir/issues/35


fix: GetSurface and GetCurve not available prior to 24R2

Description
Fixing 24R1 related issue due to GetSurface and GetCurve APIs
Issue linked
Closes #1170
Checklist

[X] I have tested my changes locally.
[X] I have added necessary documentation or updated existing documentation.
[X] I have followed the coding style guidelines of this project.
[X] I have added appropriate unit tests.
[X] I have reviewed my changes before submitting this pull request.
[X] I have linked the issue or issues that are solved to the PR if any.
[X] I have assigned this PR to myself.
[X] I have added the minimum version decorator to any new backend method implemented.
[X] I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

I believe the comments don't apply @AlejandroFernandezLuces - please review my answers

Thank you both for your reviews!

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.57%. Comparing base (4f4a656) to head (afd7093).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1171   +/-   ##
=======================================
  Coverage   90.56%   90.57%
=======================================
  Files          93       93
  Lines        6987     6992    +5
=======================================
+ Hits         6328     6333    +5
  Misses        659      659

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Switch to guzzlehttp/psr7 factory

as https://github.com/MilesChou/psr/issues/2 explains,
we should switch to the Guzzzle Factory class. This PR does that.

I will edit a compatible conditions both the new version and old after merge PR


[BLE_MESH] How to create sensor network using external MCU as the sensor input? (IDFGH-3029)

Environment

4 x ESP32-WROVER-B
4 x STM32F051R8T6

Issue
I am unsure how to send data to the ESP32-WROVER-B using SPI so that it can be transmitted through a BLE Mesh Network. I am specifically looking for how to modify the input of each node to receive SPI data and communicate that data through the network.
Desired Solution
I would like to set up a BLE Mesh network using the ESP32-WROVER-B as an SPI slave. I am using an STM32F051R8T6 to receive sensor data and send it to the ESP32 using SPI. From there, the ESP32 must send the data to an end node to display the sensor data.

Hi @dhorninger ,
Have you built a sensor network already? I am basically doing exactly things as you do, but I am stuck at creating sensor models using ESP32. Could you please share how to create sensor models?
Best Regards

Hi @sheldon123z ,
I have submitted a MR for sensor server/setup server model examples internally, waiting to be merged. When the MR is merged, it will be synchronized to Github soon.
Thanks for your patience

Hi @Campou
When do you expect the update to Github will appear?

Hi @sheldon123z @dhorninger
Please have a try with the latest idf, I have added sensor server related examples.
Thanks.

Thanks for reporting, will close now, feel free to reopen with more updates. Thanks.


11.0 pos multisession_menu port

In index.rst file: "Tested on Odoo 10.0 community". Please change to actual version and comment enterprise.

check again, please

In index.rst file: "Tested on Odoo 10.0 community". Please change to actual version and comment enterprise.

check again, please
Sorry, in index.html


Wrong view loaded if Default View is selected

Setup a View with less items in Jenkins server
Select this view in IntelliJ

Wrong: Now all Items are loaded
Correct: The item from this view are loaded
Jenkins

IntelliJ:

released with 0.13.19


Delete prep template

https://github.com/biocore/qiita/pull/842 should be merged first.

Coverage decreased (-0.26%) to 78.33% when pulling 1b36d1ef673b8d5e916e34fd435ded889584add7 on antgonza:delete_prep_template into 1ca033a95a29d4843af2663e93a6ae51ebdb213e on biocore:master.

I think you need to pull from upstream/master, but I could be wrong.
On (Feb-12-15|11:31), Antonio Gonzalez wrote:

https://github.com/biocore/qiita/pull/842 should be merged first.
You can view, comment on, or merge this pull request online at:
https://github.com/biocore/qiita/pull/850
-- Commit Summary --

deletes raw data
Merge branch 'master' of https://github.com/biocore/qiita into delete-raw-data
addressing @josenavas, @ElDeveloper and @squirrelo comments
flake8
addressing @josenavas and @ElDeveloper comments
Merge branch 'master' of https://github.com/biocore/qiita into delete-raw-data
fixing sql and test
delete prep template via GUI

-- File Changes --
M qiita_db/data.py (98)
M qiita_db/test/test_data.py (37)
M qiita_pet/handlers/study_handlers/description_handlers.py (63)
M qiita_pet/templates/study_description.html (38)
M qiita_pet/templates/study_description_templates/prep_template_panel.html (5)
M qiita_pet/templates/study_description_templates/raw_data_tab.html (5)

-- Patch Links --
https://github.com/biocore/qiita/pull/850.patch
https://github.com/biocore/qiita/pull/850.diff

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/850

Done.

Coverage decreased (-0.16%) to 78.33% when pulling 8608e82ef3e72b0999c29ca7aa21745321a7be73 on antgonza:delete_prep_template into 3ff89b8fe4f13ba2399b8a14e446298b528e2e8e on biocore:master.

Coverage decreased (-0.11%) to 78.39% when pulling 36f062869b55c5cb5dd950e116b780ae8414e81b on antgonza:delete_prep_template into 3ff89b8fe4f13ba2399b8a14e446298b528e2e8e on biocore:master.

I found another issue. Part of it is out of the scope of this PR but I think is easy enough to fix here too.
The removal of a raw data/prep template can be done independently of the study status. However, if a study is private/public raw data and prep templates can be removed. I don't think this should be allowed, at least if the study is public. If the study is private, however, I can see some discussion. But I would advocate that the user is adding metadata (prep template) so it should be checked...

Coverage decreased (-0.14%) to 78.36% when pulling 1742f8f1d3c3d08e0d3d6c5db6b993fa501274f8 on antgonza:delete_prep_template into 3ff89b8fe4f13ba2399b8a14e446298b528e2e8e on biocore:master.

I see you point but I do not think that's possible because to be able
to make it public you need processed object and if you have one, you
can not remove the preprocessed data, and if you ..., get it?
Either way, I can add that test, but depending where we do the
validation (qiita_db or qiita_pet), we will need to check the study
status. I will like to have it in qiita_db but that will require to
pass/create an study object within those objects. What do you think?

You can have a processed object from one raw data, but not from the other one. And you still will be able to delete that other one... Is just the idea that our "public" data should not be mutable in an easy way (or at least not by a normal user, just by an admin...).
I don't have strong feelings on where to put the check. Although it is a pretty light check on qiita_db that will not require interaction with the server, as the the study_status property is already used extensively in the study_description page. you can potentially propagate that value through the calls to the uimodules, so less DB interactions are needed.
(Also if you feel like it, adding a double check on qiita_db never hurts!)

Coverage decreased (-0.17%) to 78.33% when pulling 8574c3ae5914d49d97d8aa590614349f59dc221e on antgonza:delete_prep_template into 3ff89b8fe4f13ba2399b8a14e446298b528e2e8e on biocore:master.

@josenavas and I discussed his comment offline and realized that we have a bigger issue and it's described here: https://github.com/biocore/qiita/issues/855

Given that we have created another issue to keep track of my concern, I would say that this PR is good to go. So if another developer can review this and agrees with the code, feel free to merge!

Just one comment, looks good otherwise.

OK, the latest push should address your two comments. Note that I completely deactivated the collapse on the prep templates cause (1) I spent a lot of time trying to figure out how to prevent it when you cancel the erase and (2) cause this is really confusing to users and the reason I deactivated by default in the first place.

Coverage decreased (-0.16%) to 78.34% when pulling 5bf313464f50ef2448bd08405b39e519a5fa5da5 on antgonza:delete_prep_template into 3ff89b8fe4f13ba2399b8a14e446298b528e2e8e on biocore:master.

Thanks working in that, but now I can't click the delete button. On the
bright side, the accordion no longer collapses.
On (Feb-14-15| 6:38), Antonio Gonzalez wrote:

OK, the latest push should address your two comments. Note that I completely deactivated the collapse on the prep templates cause (1) I spent a lot of time trying to figure out how to prevent it when you cancel the erase and (2) cause this is really confusing to users and the reason I deactivated by default in the first place.

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/850#issuecomment-74377431

The tests passed but not sure why the PR wasn't updated.

Tested it and it looks good!


#define + #ifdef don't produce the correct output

Hi,
in the file testprep.js, I tried the following variations:
// #define var DEBUG=1
(or)
// #define DEBUG 1
(or)
// #define DEBUG=1
(and then in the same file):
// #ifdef DEBUG
console.log('debug');
// #else
console.log('nodebug');
// #endif
console.log('after');
=======================
However, the output is always the same:
$ preprocess testprep.js
console.log('nodebug');
console.log('after');
============================
So either I'm completely misinterpreting the intent, or it isn't working

Sorry, this project is not maintained anymore. Give https://github.com/dcodeIO/MetaScript a try!

Or you can use forked version: https://github.com/nashdot/Preprocessor.js


haste-boot on Linux fails (building latest)

I have been using haste for quite a while now and it is most excellent!
However I today updated haste-compiler to latest:
$ (git update haste-compiler folder)
$ cabal update
$ cabal install
$ haste-boot --force --local
and the haste-boot command => the following install error (to do with containers-<IP_ADDRESS>):
Building data-default-instances-dlist-0.0.1...
Installed data-default-instances-dlist-0.0.1
Failed to install containers-<IP_ADDRESS>
Build log ( /home/morten/.cabal/logs/containers-<IP_ADDRESS>.log ):
Configuring containers-<IP_ADDRESS>...
Building containers-<IP_ADDRESS>...
Preprocessing library containers-<IP_ADDRESS>...
Stack space overflow: current size 8388608 bytes.
Use `+RTS -Ksize -RTS' to increase it.
cabal: Error: some packages failed to install:
containers-<IP_ADDRESS> failed during the building phase. The exception was:
ExitFailure 2
data-default-0.5.3 depends on containers-<IP_ADDRESS> which failed to install.
data-default-instances-containers-0.0.1 depends on containers-<IP_ADDRESS> which
failed to install.
haste-lib-0.5 depends on containers-<IP_ADDRESS> which failed to install.

What GHC version are you using, and does the problem occur with containers-0.5.5.x as well? I've seen this for GHC 7.6 with recent versions of containers. Not sure about the cause, though it should be fairly straightforward to track down with a little profiling. I hope.

I am using GHC 7.6.3 so yes it sounds like the problem you are mentioning.
And yes it installs OK with containers-<IP_ADDRESS>

I'm on 7.8.3 with containers <IP_ADDRESS> and seeing a similar failure, but I suppose haste-boot is pulling down its own 0.6.x to build.

Fixed on GHC 7.6.3. Closing.


I-11441: appearance: none; on input tags is not cross browser

What should happen?
The appearance property is used to either add or remove styling of an element using a platform-native styling based on the users' operating system's theme.
This property is applied to search, text, password, etc... using the mixin exposed by util/_selector.scss.
For instance, input tags with attributetype set to search in WebKit browsers will, by default, be rendered with rounded corners.
When $global-radius or $input-radius is set to zero, input tags of type search should have 90 degree corners.
What happens instead?
Input tags of type search have rounded corners on iOS devices.
Possible Solution
Add cross-browser styling support for appearance:
        -webkit-appearance: none;
        -moz-appearance: none;
        -o-appearance: none;
        appearance: none;

Test Case and/or Steps to Reproduce

Test Case:

How to reproduce:

Load foundation.min.css
Load foundation.min.js
Add input tag with type equal to search
Open page on iOS device
Observer round corners on search input

Alternatively, open https://jsfiddle.net/aorinevo/wLz9ovk1/3/ on an iOS device.
Context

We have to add cross-browser appearance rules to our css.
Your Environment

Foundation version(s) used: 6.4.4-rc1
Browser(s) name and version(s): Safari, iOS v11.4.1
Operating System and version (desktop or mobile): mobile

Checklist (all required):

[x ] I have read and follow the CONTRIBUTING.md document.
[x ] There are no other issues similar to this one.
[x ] The issue title is descriptive.
[x ] The template is correctly filled.

Foundation requires Autoprefixer that will take care of all vender prefixes. See the Sass installation documentation.

https://github.com/zurb/foundation-sites/pull/11442#pullrequestreview-145473304

Makes sense.
Then there's still the separate issue of inputs of type search having rounded corners on iOS browsers.
Should I open a separate issue for that?

Should I open a separate issue for that?

Yes, please open a new issue with a codepen.

Opened #11476


Update documentation to run the ETL locally

As a developer I want to have updated information about how to run the ETL locally.
The documentation should be in a public place so we can share it with other teams/projects that are interested on running the process.
Acceptance Criteria

[x] Document with the information updated (preferable in the repository)

@zperova done. Information in https://github.com/PDCMFinder/pdcm-etl/wiki


Added tvOS target

This will add a tvOS target which makes swiftCharts build for tvOS.
This is working with Carthage via:
carthage update --platform tvos

Awesome, thanks!


Lambda functions with s3 event sources are publically accessible

Context

AWS Security Hub flags Zappa deployed lambda functions with an s3 event source as allowing public access.
PCI.Lambda.1 Lambda functions should prohibit public access

CRITICAL:
This AWS control checks whether the Lambda function policy attached to the Lambda resource prohibits public access.
Related requirements: PCI DSS 1.2.1, PCI DSS 1.3.1, PCI DSS 1.3.2, PCI DSS 1.3.4, PCI DSS 7.2.1

For directions on how to fix this issue, consult the AWS Security Hub PCI DSS documentation.
https://docs.aws.amazon.com/console/securityhub/PCI.Lambda.1/remediation

Expected Behavior

While I'm not sure this satisfies cases where there are multiple AWS accounts involved, it seems to me the default behavior should be to create private lambda functions by including the AWS:SourceAccount in the lambda resource policy conditions as shown in my steps to reproduce below.
Actual Behavior

Zappa creates lambdas that can be invoked by anyone in control of the s3 bucket leading to AWS Security Hub flagging a security finding.
Possible Fix

I'm still looking into it, but for zappa deploy and update, we call core.create_event_permission. This method calls the lambda client add_permission method. If updated to include the SourceAccount argument with the account id the resource policy is created as expected during deploys and updates.

SourceAccount (string) -- For Amazon S3, the ID of the account that owns the resource. Use this together with SourceArn to ensure that the resource is owned by the specified account. It is possible for an Amazon S3 bucket to be deleted by its owner and recreated by another account.

Steps to Reproduce

Since s3 buckets are involved and names are global, you'll need to edit references to the s3 bucket name in the below steps

Create a zappa_settings.json file as below

{
    "test": {
        "app_function": "my_project_name.lambda_handler",
        "aws_region": "us-west-2",
        "project_name": "my_project_name",
        "timeout_seconds": 900,
        "apigateway_enabled": false,
        "runtime": "python3.8",
        "keep_warm": false,
        "s3_bucket": "zappa-my-project-name",
        "events": [
            {
                "function": "lambda_handler",
                "event_source": {
                    "arn":  "arn:aws:s3:::zappa-my-project-name"
                    "events": [
                        "s3:ObjectCreated:*"
                    ]
                }
            }
        ]
    }
}

create a lambda function file named lambda_handler.py with the following content:

def lambda_handler(event, context):
    pass

zappa deploy test
open the resource policy in the aws console by navigating to the lambda function / configuration / permissions / resource policy
here's an example policy

{
  "Version": "2012-10-17",
  "Id": "default",
  "Statement": [
    {
      "Sid": "redacted",
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-west-2:redacted:function:my-project-name-test",
      "Condition": {
        "ArnLike": {
          "AWS:SourceArn": "arn:aws:s3:::zappa-my-project-name"
        }
      }
    }
  ]
}

note the policy conditions only check if the principal is s3.amazonaws.com. This means anyone in control of the s3 bucket in the event source can trigger your lambda function. For example, if you were to delete the bucket, someone else may create a bucket with the same name, drop an object in it, and trigger your lambda.
If we add the aws account ARN as a condition, the function is no longer publically invokable, and AWS security hub is satisfied

{
  "Version": "2012-10-17",
  "Id": "default",
  "Statement": [
    {
      "Sid": "redacted",
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-west-2:redacted:function:my-project-name-test",
      "Condition": {
        "StringEquals": {
          "AWS:SourceAccount": "575985943108"
        },
        "ArnLike": {
          "AWS:SourceArn": "arn:aws:s3:::zappa-my-project-name"
        }
      }
    }
  ]
}

Your Environment

Zappa version used: 0.53.0
Operating System and Python version: Ubuntu 20.04, python 3.8.10
The output of pip freeze:   argcomplete==1.12.3
boto3==1.18.42
botocore==1.21.42
certifi==2021.5.30
cfn-flip==1.2.3
charset-normalizer==2.0.5
click==8.0.1
durationpy==0.5
future==0.18.2
hjson==3.0.2
idna==3.2
jmespath==0.10.0
kappa==0.6.0
pep517==0.11.0
pip-tools==6.2.0
placebo==0.9.0
python-dateutil==2.8.2
python-slugify==5.0.2
PyYAML==5.4.1
requests==2.26.0
s3transfer==0.5.0
six==1.16.0
text-unidecode==1.3
toml==0.10.2
tomli==1.2.1
tqdm==4.62.2
troposphere==3.0.3
urllib3==1.26.6
Werkzeug==0.16.1
wsgi-request-logger==0.4.6
zappa==0.53.0
Link to your project (optional):
Your zappa_settings.json:
See steps to reproduce

I've had to adjust this manually as well in the past.
I think zappa should add the following condition by default:
      "Condition": {
        "StringEquals": {
          "AWS:SourceAccount": "{Project Creator Account}"
        },