Improve messages of code analysis tooltip

See:

@ccordoba12 since these calltips disappear, we cannot add the docs for the different errors. We would need to add either shortcut (and hint the use of it) or make them stay if moving away from the line number area.

since these calltips disappear, we cannot add the docs for the different errors

Ok, then don't worry about it. We just need to make clear that C0304, etc are code errors.

@ccordoba12  do we need to display that things come from pylint or pyflakes?
What should we do with duplicated messages (from pylint + pyflakes etc..)?
Do we want a dedicated Icon for each line depending on the severity?
I think the actual message plus the severity is what is important (the code, or what tool found is not super important)
How about:
[SEVERITY ICON] Statement seems to have no effect (PyLint Code W0104)

Where (PyLint Code W0104) would be smaller and in italics.

My answers:

do we need to display that things come from pylint or pyflakes?

No

What should we do with duplicated messages (from pylint + pyflakes etc..)?

Pyflakes and Pylint should be mutually exclusive. Since the PyLS doesn't provide an option to turn off Pylint, I restricted our dependency on it to versions that doesn't include Pylint for now (i.e. < 0.25)

Do we want a dedicated Icon for each line depending on the severity?

This is pretty good suggestion! Since a line can have several types of errors, in LineNumberArea we should only display a single icon, the one corresponding to the most critical message reported by the PyLS (in this order: errors first, then warnings and finally hints). But in the tooltip we should show all messages with their associated icons.

[SEVERITY ICON] Statement seems to have no effect (pylint code W0104)

I like this better.

Where (PyLint Code W0104) would be smaller and in italics.

I like this too.

do we need to display that things come from pylint or pyflakes?

No

Sorry, to clarify this: I'd like to see the source of the error at the end of message and next to the error code.

I am using the same icon for now while donig some tests. This requires using the images at the moment, I am checking to see if we could use font awesome instead.
It would look something like this:

Looking pretty good already. Thanks!


[Bug] The bidi package is loaded too early

Hi !
Thanks for this template, it is a very impressive piece of work.
I'm currently trying to use it for a document written in Persian with Right-to-Left (RTL) writing. The original document is located here:
https://github.com/OWASP/owasp-masvs/tree/master/Document-fa
I created a minimal example document.md containing this :
---
mainfont: 'Nazli'
---
<div dir="rtl" markdown="1">

انقلاب‌های فناورانه می

</div>

Note that I don't speak or read Persian myself so my knowledge on this topic is limited.
I am able to build successfully a pdf artefact using the default pandoc latex template like this:
$ pandoc --pdf-engine=xelatex examples/language-persian/document.md -o examples/language-persian/document.pdf

However with eisvogel I get the following error:
$ pandoc --template=eisvogel --pdf-engine=xelatex examples/language-persian/document.md -o examples/language-persian/document.pdf
Error producing PDF.
! Package bidi Error: Oops! you have loaded package caption after bidi package.
 Please load package caption before bidi package, and then try to run xelatex o
n your document again.

See the bidi package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.251 \begin{document}

After looking into the template I have found 3 problems:

The caption package is loaded after bidi (Line 601)
https://github.com/Wandmalfarbe/pandoc-latex-template/blob/master/eisvogel.tex#L601

The mdframed package is loaded after bidi (Line 610)
https://github.com/Wandmalfarbe/pandoc-latex-template/blob/master/eisvogel.tex#L610

The polyglossia package is loaded after bidi (Line 557  and it is also loaded before on line 434)
https://github.com/Wandmalfarbe/pandoc-latex-template/blob/master/eisvogel.tex#L557
https://github.com/Wandmalfarbe/pandoc-latex-template/blob/master/eisvogel.tex#L434

The template seems to work with the following modifications:

Move the caption and mdframed section before bidi
Comment the second polyglossia load

Here's my working version of eisvogel:
https://github.com/daamien/pandoc-latex-template/blob/bug_bidi_persian/eisvogel.tex
Thanks again for your time, let me know how I can help fixing this...
EDIT: fixed links

See PR #231 with my changes


ceph-crash: add support cluster name

add cluster name to CEPH_ARGS env var to support custom cluster name
this can change as an arg to ceph-crash when https://github.com/ceph/ceph/pull/47836 released
Signed-off-by: Seena Fallah<EMAIL_ADDRESS>

jenkins test centos-non_container-all_daemons

jenkins test centos-non_container-purge

jenkins test centos-non_container-update

jenkins test centos-non_container-switch_to_containers

@guits Do you have any idea about the failures?

@guits Do you have any idea about the failures?

yes, this is because of https://github.com/nfs-ganesha/nfs-ganesha/issues/848

@clwluvw custom cluster name is no longer supported

@clwluvw custom cluster name is no longer supported

I know it's not but for backward compatibility, I think we should support as ceph cli is still supporting it (either ceph-ansible)


pillar support

utf8_encode(quote = NA), meaning "quotes if needed"
enhance utf8_encode(escapes = ...) to support subtle quotes, perhaps passage of full open-close strings, and perhaps fix #34 by offering an alternative option
Understand difference between utf8_encode() and utf8_format(); only the latter has a chars argument (but #33?), only the former has escapes
When abbreviating, never break escapes and honor wide characters

For https://github.com/r-lib/pillar/issues/563.
CC @patperry.

I don't remember the exact details but encode and format are meant to follow base R (encodeString and format). The former is for encoding control characters. The latter is for formatting a string immediately prior to printing.


How to add multiple opponents?

Describe your problem here.
I want to try and add multiple opponents to one side of the game, with different charts so they sing different things at the same time. For example five opponents against BF or vice versa
I’ve tried a few things, but none of them seem to work!
Are you modding a build from source or with Lua?
Lua
What is your build target?
Mac
Did you edit anything in this build? If so, mention or summarize your changes.
I added a few characters and a song with an edited JSON file

In lua you can do it by making the extra characters part of the background and make a note type to play it's sing animations


SOLR-16158: Remove server jars from solr-core

https://issues.apache.org/jira/browse/SOLR-16158

Move SolrJettyRunner to test framework. Solr-core now no longer has jetty server deps.
This is a slight back-compat concern, but I'm not sure the SolrJettyRunner is used widely enough for it to warrant keeping this from 9x
server/lib/ext now contains the following jars:

logging
metrics
Shared server & core dependencies

The web-app is now setup so that "server" jars can be used by the Solr webapp. We no longer have to duplicate these jetty "server" jars between server/lib and WEB-INF/lib.
This is also a slight back-compat concern, but we are already changing our jetty xml files for the jetty 10 upgrade, so this change is likely ok too.
The solr-core & solr-server dependencies now just work, and shouldn't require special setup.

Most of the files are just changing the location of SolrJettyRunner. If you want to see the actual changes here, then just look at the */build.gradle and solr/server/contexts/solr-jetty-context.xml files.

Note: the jetty-server jar is in lib/ext even though Solr core/SolrJ should not need it. We can hunt that down in a separate issue though if need be.

@dsmiley @risdenk can I get a quick check on my upgrade notes? https://github.com/apache/solr/pull/1179/commits/1fea79bc61f61a6fde5e0f4fb06ed9e91aac4aac

The CHANGES.txt text speaks of duplicated JARs but does not mention any.  If this was actually a problem in 9.1 (I forget?) then okay -- could you list at least one there?  If that was not a released problem (e.g. happened after 9.1) then don't mention it; keep it in the commit notes, though.

Ok listed 2, and expanded a bit in both sections.


Prevent install / uninstall  programmatically

Description
I would need to programatically allow or disallow both installation, and same for uninstalls
User click install link either from slack directory --> We validate the emails/slackuser that did the request --> Accept / Reject install.
Because atm we do a check inside the installation store but when we reject and show an error message it is still installed.
What type of issue is this?

[x] question

Hi @adelin-b 👋🏻
Unfortunately, you cannot programmatically allow/disallow installing/uninstalling a Slack app. The Slack API allows you to:

Listen for the uninstall event, so that you can remove the team's data from your database
Programmatically uninstall the app so that you can offer an uninstall feature inside your app

If you need to allow/disallow the installing of the app, you would need to approach it from a functionality perspective. For example, a team may install your app but it will not do anything until meets your requirements (e.g. connects to a third-party service or upgrades to a paid subscription for your app).
Likewise, you cannot prevent a team from uninstall the app. Any team member with proper admin privileges will be able to uninstall your app. So, it's good idea to listen for the uninstall event so that you can do any clean up that's necessary.
Hope that helps!

👋 @adelin-b let us know if you need more help here! We'll close this issue after waiting for your response for a few more days.


External Markdown Links are pointing to physical location of HTML

I'm currently using 0.5.0 and I'm having an issue with the PDF generation of a pretty large documentation base. We are using a lot of internal links between our documentation pages and sections and we're seeing something new in our PDF generated file (We are almost certain that this works, at some point...).
When using a link like the following in our documentation [Topic](topic.md), this works nicely in our website but produces a link to the physical generated file (file:///Users/vsts/agent/2.144.0/work/1/s/site/topic/). It does that in our CI/CD environment and does it also in all our local builds.
Anything we should change to make sure the links are clickable through the PDF document?
Thanks!

I am seeing a new behaviour now where links within a document are now broken again with 0.5.2b2. Is there any specific format we should use for our links within the HTML that would be picked up when generated in PDF? I'm currently using the following :
[title of the article](../folder/article.md).
The result is that I'm seeing is a link to an relative link like an URL instead of an anchor withint the PDF document :

Thanks!


Remove dependence on local_settings.py file

This change modifies how the import_reg management command works by removing a dependence on a nonexistent local_settings.py file and instead using an explicit command-line option, e.g.
./manage.py import_reg -r ../regulations-xml 1013

This makes the source of regulations more explicit and removes a setup step when using this repository either manually or as part of an automated process.
This change also modifies import_diff to use  django.conf.settings instead of eregs.local_settings to check the DEBUG flag.
It also fixes the passing of multiple regulations on the command line, e.g.
./manage.py import_reg -r ../regulations-xml 1003 1005 1013

Finally, it also modifies the bulk_create call in import_xml to use a batch size of 100; by default Django uses only a single query to insert but if the amount of data to insert is excessive this can fail.
By setting a (hopefully reasonable) bulk batch size, this will avoid errors when loading large regulations.
Additions

New command line parameter for local regulations root.

Changes

Fixed support for importing of multiple regulations at once.
Make bulk_create in import_xml use a batch size to support larger input files.

Testing

Try the above command lines.

Checklist

[X] Changes are limited to a single goal (no scope creep)
[X] Code can be automatically merged (no conflicts)
[X] Code follows the standards laid out in the front end playbook
[X] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

@grapesmoker yes, I iterate over that list in this line.

Ah, I see. I missed the loop because I assumed it would be in handle.


Server don't generate logs

Rasa NLU version: 0.13.7

[ ]

Operating system: Linux
Issue:
Server don't generate logs. I tried with -w flag and creating a folder first but no results. I'm using a venv, could be that a problem?

Please provide some more details like what command you're running exactly and also what kind of logs you're looking for

I run:
python -m rasa_nlu.server --path ./models -w ./logs
and get
2018-11-13 16:30:04+0100 [-] Log opened.
2018-11-13 16:30:04+0100 [-] Site starting on 5000
2018-11-13 16:30:04+0100 [-] Starting factory <twisted.web.server.Site object at 0x7f6409c127f0>

then I do a post from postman and no logs is generated in logs folder, I tried without -w but same result

try adding the --debug flag and see if the logs get written then

now I get this:
Logging of requests is disabled. (No 'request_log' directory configured)
I thought request logs was active by default...

Here says it's by default meanwhile with --hlep says
--response_log RESPONSE_LOG
                        Directory where logs will be saved (containing queries
                        and responses).If set to ``null`` logging will be
                        disabled.

maybe it was default in older versions

Hmm, the link you sent me is to the evaluation page. In any case, seems like you found the solution, there's no default value for that flag so you need to pass it when launching the server

In that link say:
the Rasa NLU server will log every request made to the /parse endpoint to a file. By default these are saved in the folder logs.
But it's not by default


(version 2.0.2) - Wrong days are displayed for August 2021 so far (wrong offset in DateRange Picker - Litepicker lib)

Steps to reproduce
You can reproduce this directly on the demo preview : https://startbootstrap.com/previews/sb-admin-pro
(Click in menu UI Toolkit > Components > Forms > Date Range Picker)
Problem identified

You can see that August's start on Monday 1st, even though it started on Sunday this month. As a result, all the dates are with a wrong offset.
I've only seen this bug within this current month, all other months seem fine.
Troubleshooting : How to be sure it's not a Litepicker's related bug?

Here's a JS fiddle to prove the lib's working well: https://jsfiddle.net/7zbmtwyq/ (August starts on a Sunday)
If you remove the Litepicker's CSS override directives from file scss/admin/plugins/_litepicker.scss, you'll see that everything is working perfectly (even though we loose the SB Admin CSS for this input)

So I guess there is something wrong with these CSS directives

In addition to the last troubleshooting, I've found something interesting:
Within _litepicker.scss, if you remove the margin directive (margin: 2px;) from &__days { >div, > {...} }  (line 141 on my file), everything works well again (even though the CSS rendering is not nice, I guess this margin is important but it creates this bug)
Forgot to mention that I've tested this on Chrome & Firefox
Thanks


[BUG] VersionUnavailable: GLX: Failed to create context: BadValue (integer parameter out of range for operation)

Describe the bug
The application doesn't start properly. If started from gui, the hass icon bounces a moment and then nothing happens. If started from terminal VersionUnavailable: GLX: Failed to create context: BadValue (integer parameter out of range for operation) error appears and the program runs forever.
To Reproduce
Steps to reproduce the behavior:

Download go-hass-agent-0.0.2-1-x86_64.pkg.tar.zst
Install with 'sudo pacman -U go-hass-agent-0.0.2-1-x86_64.pkg.tar.zst '
Open Terminal and start 'go-hass-agent'
See error

Expected behavior
I expected the application to start normaly.
Logs
A log will be very helpful to look into this bug report. To get the log:

Run go-hass-agent from a terminal or command-line with the --debug flag:

3:52PM DBG Debug logging enabled.
3:52PM INF Starting agent.
3:52PM DBG /home/joshua/git/go-hass-agent/internal/agent/config.go:74 > Setting language to [de].
3:52PM DBG /home/joshua/git/go-hass-agent/internal/config/config.go:94 > Config seems invalid.
3:52PM WRN No suitable existing config found! Starting new registration process
3:52PM INF Looking for Home Assistant instances on the network...
3:52PM DBG /home/joshua/git/go-hass-agent/internal/agent/register.go:52 > Found a record <IP_ADDRESS>:8123
2023/04/12 15:52:27 Fyne error:  window creation error
2023/04/12 15:52:27   Cause: VersionUnavailable: GLX: Failed to create context: BadValue (integer parameter out of range for operation)
2023/04/12 15:52:27   At: /home/joshua/gocode/pkg/mod/fyne.io/fyne/v2@v2.3.1/internal/driver/glfw/driver_notwindows.go:9

Desktop (please complete the following information):

OS: Arch-Linux

Thank you in advance for your trouble.

Hey @dflvunoooooo thanks for trying out go-hass-agent. I'm unsure what could be the cause of this error, except maybe a problem with the fyne UI toolkit I use on your system.
Does the fyne_demo app run for you (see instructions for installing here)?
Is your system up to date with drivers and packages? Does this happen after you reboot?

Thank you for your quick answer. It was indeed something with my nvidia graphics driver. I had problems with that yesterday. I reinstalled the drivers, rebooted and it is working. Thanks a lot.


Improve changes uri creation

Thank you for the beautiful contribution.
The most of changes look smarter than before.


Remove old datasources, shim enough to keep UI functioning

This just removes the old Datasources code, type definitions, etc. so that we can implement the new spec documented in #404. I left a very basic implementation in place for the legacy version just to let the UI continue functioning while we work on implementing it for real.
Signed-off-by: Luke Tillman<EMAIL_ADDRESS>

Nice :).
Maybe for this one, let's try to connect FE and BE directly. WDYT ?
Hopefully next week we should be able to deliver the new implem of thé datasource BE side

Nice :). Maybe for this one, let's try to connect FE and BE directly. WDYT ? Hopefully next week we should be able to deliver the new implem of thé datasource BE side

Yeah, definitely possible. My plan is to basically do the implementation with stubbed out API calls so we can just swap it out for a real fetch call to connect them.

My plan is to basically do the implementation with stubbed out API calls so we can just swap it out for a real fetch call to connect them.

Interesting ! Do you think it would be possible to do the same for the loading of the dashboard ?

My plan is to basically do the implementation with stubbed out API calls so we can just swap it out for a real fetch call to connect them.

Interesting ! Do you think it would be possible to do the same for the loading of the dashboard ?

Yeah, probably could do the same there. One thing I'd love to do when we want to make that change is to add a proper URL/route to the UI for a dashboard so we could grab the "dashboard ID" from the URL path.

One thing I'd love to do when we want to make that change is to add a proper URL/route to the UI for a dashboard so we could grab the "dashboard ID" from the URL path.

Totally inline with that.
From my side a proposition for the URL would be /projects/<project_name>/dashboards/<dashboard_name>.
With project_name and dashboard_name you are able to find/get the dashboard.


Collaboration with covid19india

As an institution Srijan is actively trying to do COVID-19 related Initiative. We primarily deal with community and collaborative platforms. We are deeply interested in supporting Covid-19 initiative. We have identified a few issues with the covid19india ongoing project

Collaboration Interface(Google Sheet)
Platform project has fewer activity
Patients Data APIs has been partitioned into multiple APIs

We have already built a platform to solve the above issues and we are interested to give it as a pro bono. We can host the application for you. We can also build a highly maintainable API gateway service and data module over it. You can make a rest API on the Complete patient database. It will solve some of the problems of data which the consumers of the current platform have been facing.
Over and beyond we can also put effort to set-up the graphQL and OData layer over it if you promise to use it. Whatever application we have built we are ready to open-source.
We are actively working on publicising this data with the state governments. Also, trying to reach out to the research institute for research activity based on patient data for similar outbreaks.
 You can access the application using the below link : https://covid19database.srijan.net

@jyoti291 Hi! This is interesting. Is the code open source? We have kept everything open for everyone to view so we would like it to continue that way :). Also, some of the things pointed out by you as issues are actually choices we've made to reduce complexity and maintenance for data updates. Thanks for this initiative :)

@bee-rickey : This application is build for open source community.The code is not public but we can make it public if you want to have a look on it.We would like you to view the system and if you find it useful, you can use it to maintain the patient's data in the application itself.Let me know if you have any inputs on the same.

@jyoti291 I had a quick look at the website link you provided. Great job!
However, our data update process is just too dynamic to be relied upon an external software. We make do with the functionality of Google sheets and around it. For now, it has to remain that way, so that we can adapt to change scenarios. Thanks for reaching out.


adding response log hook

updated the Go SDK version to latest v75.
added the response log hook.
routingAPI.GetRoutingQueues() has some new parameters so I updated accordingly.

Take a look at the tests, looks like the GetRoutingQueues change has caused some issues


FIX Ignore differences in silverstripe/admin dist files

Issue https://github.com/silverstripe/.github/issues/235
Related issue https://github.com/silverstripe/gha-run-tests/issues/11
Works around the admin dist files being randomly different e.g. https://github.com/silverstripe/silverstripe-admin/actions/runs/8993547176/job/24712604208#step:12:604.
Testing locally, subsequent runs on yarn build have dist files with different sha1 sums. I've put more details on this issue.
I have no idea how to get an older version of webpack to behave. Given that the git diff failing when it should, we should instead just ignore the git diff for CMS 4 admin IMO.  There's now less than 12 months of support for CMS 4 admin and its veeeery unlikely that we'll actually need the git diff functionality for anything practical at this point.
This PR also deletes the "copy dist file that was different to artifacts dir" functionality that doesn't actually work, and instead just sends exit code 2.

The git diff check is really there to avoid malicious actors from manually injecting payloads into dist files. Given we aren't going to accept any PRs from anyone outside the CMS Squad for CMS 4 due to the current support level, this seems fine.


App hassgraph: fix case of unknown values

App HASS Graph:
This PR makes the App skip unknown values from HA.
@vincentezw : Hope you approve.

@vincentezw Assuming this is cool to merge? Seems uncontroversial.

LGTM


⚠ Bofrost.be has degraded performance

In c7e6b80, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1212 ms

Resolved: Bofrost.be performance has improved in b59d440.


Create CSV_To_MYSQL.md

📝 Description
Adding CSV To MYSQL
Develop an application utilizing ILLA Cloud which empowers users to upload a CSV file and seamlessly store its contents into their MySQL database.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
Try Now: https://illa.ai/app/ILAfx4p1C7CI/detail
Online Demo: https://youtu.be/WxXmkYnWi8s

Solves #2860


Use async instance tracker methods in TaskKiller

Related to: #3031 #4693

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

What tests failed? It's passing on my machine and travis https://travis-ci.org/janisz/marathon/builds/187161861

@janisz sbt scapegoat is failing. See these logs. Would you mind fixing the reported issues?

@jeschkies fixed

@jasongilanfarr would you like to rereview? I think I fixed all issues.


Update indy-vdr version (time crate related issue)

The version of indy-vdr we are using has a dependency on time crate which is pinned to a version that has issues with rust 1.80+. We should update indy-vdr to a newer version where that bad time crate version is not pinned (0.3.36+).
See here: https://github.com/hyperledger/indy-vdr/issues/324
Unfortunately the current release of indy-vdr (0.4.3) does not have this change within it yet, so we may have to continue using git hashes (pre-releases) depending on how urgently we want this.

FYI — the delay in getting the Indy VDR update (and Askar) is the pinning of Rust for the react-native/Android wrapper requirements — getting in the updates needed so that there is a combination of dependencies that will compile. We hope to have that resolved Real Soon Now — bumping the NDK and Rust versions and anything else that is needed. If anyone has experience with Android+ReactNative wrappers for Rust, please jump in to help.


(CONT-339) Update CI for ruby 2.5

The whole issue with this is that it pulls in puppetlabs_spec_helper, which is done for acceptance tests. However, it creates a circular dependency. IMHO it must be removed. If you want to do real testing, use something that doesn't need a whole VM. This is just a gem and you control the environment, so you can consider a framework like cucumber.
I see this was already merged while I was writing https://github.com/puppetlabs/puppet-lint/pull/89 but please consider to get rid of Litmus here.


Use document title name for window

The title of the PDF Viewer should be the name of the document it is rendering, instead of a static "View PDF"
Fixes: https://github.com/Djphoenix719/PDFoundry/issues/122

Hey @saif-ellafi - After merging this I'm actually unsure what the goal here was, PDF names are already included in the title prior to this PR.

Hey @saif-ellafi - After merging this I'm actually unsure what the goal here was, PDF names are already included in the title prior to this PR.

Hi hi :) no, they were not. Unless I was doing something really wrong.
Before

After

In the code you can see window title was hardcoded to "View PDF"


One project's deployment is cancelled, and I don't know why ?

Before submitting your issue, please make sure that you've checked all of the checkboxes below.

[ x ] I'm running the 0.0.46 version of Deployer.
!  I'm running PHP 5.6.3 instead of PHP 5.6.4
[ x ] I've ran composer install --no-dev from the root of my installation.
[ x ] I've ran npm install --production from the root of my installation.
[ x ] You've ran rm -rf bootstrap/cache/* from the root of your installation.
[ x ] I have restarted the queue listener and node socket server.

Expected behaviour
The deployment to be successful (or, at least, get a verbose message of what's going on).
Actual behaviour
So...
I got a setup with like ... 20 different projects.
All of them were working fine but since yesterday : we got one of our projects which doesn't work (by that I mean, cannot be deployed) anymore.
Actually, the process doesn't even start, it only prints "cancelled" in the first step (which is "Create new release"). Image below.

The weird stuff is, I got 2 others projects located on the same server, with the same user and same conf.
Only the bitbucket repositories are different so I don't know how it is possible that I can deploy the 2 projects successfully, but not the 3rd ?
Steps to reproduce
Click on the deploy button :)
Environment info

Operating System: Linux (debian)
PHP Version: 5.6.3
Node Version: 1.4.21
Database: MySQL Ver 14.14 Distrib 5.5.55

I tried a lot of things before coming here (also checking other similar issues) but nothing worked.
Thanks for your help :)

up !

up again, I tried to create a new project with the same repo and I still have the problem. The other new projects are fine tho.

Apologises for the delay, I've been out of the country without a computer and I'm still catching up
Are you using the HTTP URL for the repository or the SSH URL? If the latter, have you remembered to add the SSH key to the repository?
Can you turn on debugging by running php artisan app:debug on and then try again, then posting the log file, specifically the storage/logs/cli-2018-03-06.log one?

No problem !
I'm using the SSH url, the configuration is the same for all my projects. Yes I added it ; if not the error will be displayed explicitly anyway so I'm 100% sure it is not the case here. Also, the project has also been deployed successfully multiple times before this problem's first occurence.
Here come the log :
[2018-03-06 11:00:01] production.DEBUG: ### Run script locally
bash -s << 'EOF'
    # Turn on quit on non-zero exit
    set -e
    ### Mirror git repository
chmod +x /home/www/deployer/storage/app/tmp/sshCnPSH0
export GIT_SSH=/home/www/deployer/storage/app/tmp/sshCnPSH0

if [ ! -d /home/www/deployer/storage/app/mirrors/git_bitbucket.org_leoogit_yara-es.git ]; then
    git clone --mirror git@bitbucket.org:leoogit/yara-es.git /home/www/deployer/storage/app/mirrors/git_bitbucket.org_leoogit_yara-es.git
fi

cd /home/www/deployer/storage/app/mirrors/git_bitbucket.org_leoogit_yara-es.git

git fetch --all --prune
EOF

[2018-03-06 11:00:02] production.DEBUG: ### Run script locally
bash -s << 'EOF'
    # Turn on quit on non-zero exit
    set -e
    ### Get commit details - 763
cd /home/www/deployer/storage/app/mirrors/git_bitbucket.org_leoogit_yara-es.git

git log master -n1 --pretty=format:"%H%x09%an%x09%ae"
EOF

[2018-03-06 11:00:02] production.DEBUG: ### Run script locally
bash -s << 'EOF'
    # Turn on quit on non-zero exit
    set -e
    ### Create release archive - 763
git clone --depth 1 --recursive /home/www/deployer/storage/app/mirrors/git_bitbucket.org_leoogit_yara-es.git /home/www/deployer/storage/app/tmp/clone_16_20180306110001
cd /home/www/deployer/storage/app/tmp/clone_16_20180306110001
git checkout 81eb51984024f877fc3b0698a6fbab0d2f072e71
/home/www/deployer/resources/scripts/tools/GitArchiveAll.sh --tree-ish 81eb51984024f877fc3b0698a6fbab0d2f072e71 --format tar.gz --verbose /home/www/deployer/storage/app/16_20180306105958.tar.gz
cd -
rm -rf /home/www/deployer/storage/app/tmp/clone_16_20180306110001
EOF

Hmm, odd
Bit of a hack but can you edit app/Jobs/DeployProject.php and on line 118 put
\Illuminate\Support\Facades\Log::error($error);
then restart the worker with php artisan queue:restart
then try again and then post the log, looks like there is an error occurring which is unexpected but being caught.

Ok so I got it.
It seems that someone in my team committed a git submodule (a part of it actually) in the project. And deployer does not seem happy with it :)
We are removing this submodule (it should not have been here in the first time). It will probably fix the error. I'll report the result to you.
Anyway, Deployer was not alerting us about the error and I thing it's a feature/fix to work on, someday maybe :)
(Here come the error that shows up with your hack:)
[2018-03-07 17:34:43] production.ERROR: exception 'RuntimeException' with message 'Could not get repository info - Cloning into '/home/www/deployer/storage/app/tmp/clone_16_20180307173440'...
warning: --depth is ignored in local clones; use file:// instead.
done.
No submodule mapping found in .gitmodules for path 'src/Leoo/CatalogBundle'
' in /home/www/deployer/app/Jobs/DeployProject/ReleaseArchiver.php:61
Stack trace:
#0 [internal function]: REBELinBLUE\Deployer\Jobs\DeployProject\ReleaseArchiver->handle(Object(REBELinBLUE\Deployer\Services\Scripts\Runner))
#1 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(30): call_user_func_array(Array, Array)
#2 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#3 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#4 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/Container.php(539): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#5 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(94): Illuminate\Container\Container->call(Array)
#6 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(114): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}(Object(REBELinBLUE\Deployer\Jobs\DeployProject\ReleaseArchiver))
#7 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(REBELinBLUE\Deployer\Jobs\DeployProject\ReleaseArchiver))
#8 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(98): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#9 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(75): Illuminate\Bus\Dispatcher->dispatchNow(Object(REBELinBLUE\Deployer\Jobs\DeployProject\ReleaseArchiver))
#10 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Foundation/Bus/DispatchesJobs.php(17): Illuminate\Bus\Dispatcher->dispatch(Object(REBELinBLUE\Deployer\Jobs\DeployProject\ReleaseArchiver))
#11 /home/www/deployer/app/Jobs/DeployProject.php(105): REBELinBLUE\Deployer\Jobs\DeployProject->dispatch(Object(REBELinBLUE\Deployer\Jobs\DeployProject\ReleaseArchiver))
#12 [internal function]: REBELinBLUE\Deployer\Jobs\DeployProject->handle(Object(REBELinBLUE\Deployer\Services\Filesystem\Filesystem))
#13 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(30): call_user_func_array(Array, Array)
#14 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#15 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#16 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/Container.php(539): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#17 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(94): Illuminate\Container\Container->call(Array)
#18 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(114): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}(Object(REBELinBLUE\Deployer\Jobs\DeployProject))
#19 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(REBELinBLUE\Deployer\Jobs\DeployProject))
#20 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(98): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#21 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(43): Illuminate\Bus\Dispatcher->dispatchNow(Object(REBELinBLUE\Deployer\Jobs\DeployProject), NULL)
#22 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(69): Illuminate\Queue\CallQueuedHandler->call(Object(Illuminate\Queue\Jobs\BeanstalkdJob), Array)
#23 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(317): Illuminate\Queue\Jobs\Job->fire()
#24 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(267): Illuminate\Queue\Worker->process('beanstalkd', Object(Illuminate\Queue\Jobs\BeanstalkdJob), Object(Illuminate\Queue\WorkerOptions))
#25 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(113): Illuminate\Queue\Worker->runJob(Object(Illuminate\Queue\Jobs\BeanstalkdJob), 'beanstalkd', Object(Illuminate\Queue\WorkerOptions))
#26 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(102): Illuminate\Queue\Worker->daemon('beanstalkd', 'deployer-high,d...', Object(Illuminate\Queue\WorkerOptions))
#27 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(86): Illuminate\Queue\Console\WorkCommand->runWorker('beanstalkd', 'deployer-high,d...')
#28 [internal function]: Illuminate\Queue\Console\WorkCommand->fire()
#29 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(30): call_user_func_array(Array, Array)
#30 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#31 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#32 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Container/Container.php(539): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#33 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Console/Command.php(182): Illuminate\Container\Container->call(Array)
#34 /home/www/deployer/vendor/symfony/console/Command/Command.php(264): Illuminate\Console\Command->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#35 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Console/Command.php(168): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#36 /home/www/deployer/vendor/symfony/console/Application.php(869): Illuminate\Console\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#37 /home/www/deployer/vendor/symfony/console/Application.php(223): Symfony\Component\Console\Application->doRunCommand(Object(Illuminate\Queue\Console\WorkCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#38 /home/www/deployer/vendor/symfony/console/Application.php(130): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#39 /home/www/deployer/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(122): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#40 /home/www/deployer/artisan(46): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#41 {main}

Yes, it does work now. Thanks for the help !
I'd close the issue, but since the error is not displayed for the user I'm not sure if I should do it or not ?
So feel free to do it if you want to :)
Have a nice day !

wow, that is very interesting, yeah sounds like there should be some sort of way to report on such errors with git so leave this open and I'll see if I can some up with some ideas


Observatory timeline broken

I haven't used it for a few months, but the timeline in the observatory seems broken. I used Chromium.

Dart SDK Version: 2.5.0-dev.0.0
Debian 9.9
Chromium 73

I get the following error when trying to refresh (fetching timeline from Dart VM)
timeline.js:657 Uncaught TypeError: Cannot read property 'timeOriginMicros' of undefined
    at XMLHttpRequest.<anonymous> (timeline.js:657)

This looks like a duplicate of a prior issue that was fixed here
https://dart-review.googlesource.com/c/sdk/+/107926


Conda: ModuleNotFoundError: No module named 'python_griddly'

I'm trying to build a clean conda environment with Griddly manually installed from the repo. (The latest griddly version on PyPI is 1.6.7, which has some incompatibilities with gymnasium -- and I still have the Apple Silicon / Vulkan error from #286 which I'm hoping to resolve soon.)
I've spent a couple hours on this but still can't get past what seems to be a path error.
Python 3.10.12 | packaged by conda-forge | (main, Jun 23 2023, 22:39:40) [Clang 15.0.7 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import griddly
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/grandg/mit/Griddly/python/griddly/__init__.py", line 16, in <module>
    gd = importlib.import_module("python_griddly")
  File "/opt/anaconda3/envs/gridtheory/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named 'python_griddly'

I tried the os.environ['PYTHONPATH'] hack from #126, but it didn't resolve the issue.
Minimal steps to reproduce:

conda create -n griddly python=3.10
conda activate griddly
Follow manual build instructions from README
python -m pip install -e .
import griddly in Python interpreter

Hey @Bam4d, thanks for the heads-up about the switch to poetry! Unfortunately, even after running poetry install and activating the environment with poetry shell, I'm still getting the above error. I've tried both installing within a pre-existing conda environment, and also installing on top of my base conda environment.
I noticed that even with the griddly poetry environment activated, poetry show reveals that griddly is not in the list of installed packages.
Do you have any suggestions? I'm pretty new to poetry so I'm not sure if I might be missing something.

I was hitting this with python 3.10 on my mac, but it went away when i switched to python 3.11


cls_token

All samples in a batch share the same cls_token(because in the code, the cls_token is repeated for batch_size), but how they change to be different during loss backward? As the cls_token was used as the classifier input, then all samples in a batch will be classified as the same label?

the CLS token is passed through the layers of attention and aggregates information from the rest of the tokens as it makes its way up

there's no metaphor i can make to CNNs, since such a concept doesn't exist in that field

I had the same question here and here is my illustration about it. Please remind yourself that cls_token is a parameter, not a feature of input. Actually we can consider it as the starting point to give final label through self-att & mlp as info-aggregating procedures. By comparing the y_hat=f(cls_token, params|input) and true label y, cls_token and other params would be updated to be able to learn the effective way for aggregating infos from input.


Properly pass proxy to inbound sidecar creation

This caused a bug in 1.8: https://github.com/istio/istio/pull/30443.
Today, the function does not actually end up mattering much, since we
only support 1.9 proxies in 1.10 (master) istiod. however, it will avoid
future bugs that assume proxy is non-nil.
additionally, copy the additional testing that was added in the original
PR. The tests pass before and after this change, which is expected as
this should have no impact
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
9df6461c997e51eb17018a853347dfc289241ec2
link
/test integ-pilot-multicluster-tests_istio

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

/retest


Question: getting the error: "File<EMAIL_ADDRESS>for ios not found in compilation assets"

Hi, my images folder is located in the root project diretory under the "images" folder (and not under "assets/images"), how can I change the target location for repack? I tried to change the assetsPath to several options, but all faild
Happy for your help!
(using the latest version, v4.0.0 with react native 0.72.14

Hi @oferRounds,
you should be able to import the assets normally into your project even from outside of your project - all you have to do is configure asset loader to include that path and then import the asset in your code.
Can you please describe the details of this scenario? Like, how are you importing these assets, and your assets-loader configuration?

Thank you @jbroma! so in my project folder, I have the following hierarchy:

, which includes the `index` file and `app`, etc.
    , which contains all the images (same level as "src")

And this is my webpack.conflig.mjs file:
import { createRequire } from 'node:module';
import path from 'node:path';
import TerserPlugin from 'terser-webpack-plugin';
import * as Repack from '@callstack/repack';

const dirname = Repack.getDirname(import.meta.url);
const { resolve } = createRequire(import.meta.url);

/**
 * More documentation, installation, usage, motivation and differences with Metro is available at:
 * https://github.com/callstack/repack/blob/main/README.md
 *
 * The API documentation for the functions and plugins used in this file is available at:
 * https://re-pack.dev
 */

/**
 * Webpack configuration.
 * You can also export a static object or a function returning a Promise.
 *
 * @param env Environment options passed from either Webpack CLI or React Native CLI
 *            when running with `react-native start/bundle`.
 */
export default (env) => {
  const {
    mode = 'development',
    context = dirname,
    entry = './index.js',
    platform = process.env.PLATFORM,
    minimize = mode === 'production',
    devServer = undefined,
    bundleFilename = undefined,
    sourceMapFilename = undefined,
    assetsPath = '.',
    reactNativePath = resolve('react-native'),
  } = env;

  if (!platform) {
    throw new Error('Missing platform');
  }

  /**
   * Using Module Federation might require disabling hmr.
   * Uncomment below to set `devServer.hmr` to `false`.
   *
   * Keep in mind that `devServer` object is not available
   * when running `webpack-bundle` command. Be sure
   * to check its value to avoid accessing undefined value,
   * otherwise an error might occur.
   */
  // if (devServer) {
  //   devServer.hmr = false;
  // }

  /**
   * Depending on your Babel configuration you might want to keep it.
   * If you don't use `env` in your Babel config, you can remove it.
   *
   * Keep in mind that if you remove it you should set `BABEL_ENV` or `NODE_ENV`
   * to `development` or `production`. Otherwise your production code might be compiled with
   * in development mode by Babel.
   */
  process.env.BABEL_ENV = mode;

  return {
    mode,
    /**
     * This should be always `false`, since the Source Map configuration is done
     * by `SourceMapDevToolPlugin`.
     */
    devtool: false,
    context,
    /**
     * `getInitializationEntries` will return necessary entries with setup and initialization code.
     * If you don't want to use Hot Module Replacement, set `hmr` option to `false`. By default,
     * HMR will be enabled in development mode.
     */
    entry: [
      ...Repack.getInitializationEntries(reactNativePath, {
        hmr: devServer && devServer.hmr,
      }),
      entry,
    ],
    resolve: {
      /**
       * `getResolveOptions` returns additional resolution configuration for React Native.
       * If it's removed, you won't be able to use `<file>.<platform>.<ext>` (eg: `file.ios.js`)
       * convention and some 3rd-party libraries that specify `react-native` field
       * in their `package.json` might not work correctly.
       */
      ...Repack.getResolveOptions(platform),

      /**
       * Uncomment this to ensure all `react-native*` imports will resolve to the same React Native
       * dependency. You might need it when using workspaces/monorepos or unconventional project
       * structure. For simple/typical project you won't need it.
       */
      // alias: {
      //   'react-native': reactNativePath,
      // },
    },
    /**
     * Configures output.
     * It's recommended to leave it as it is unless you know what you're doing.
     * By default Webpack will emit files into the directory specified under `path`. In order for the
     * React Native app use them when bundling the `.ipa`/`.apk`, they need to be copied over with
     * `Repack.OutputPlugin`, which is configured by default inside `Repack.RepackPlugin`.
     */
    output: {
      clean: true,
      hashFunction: 'xxhash64',
      path: path.join(dirname, 'build/generated', platform),
      filename: 'index.bundle',
      chunkFilename: '[name].chunk.bundle',
      publicPath: Repack.getPublicPath({ platform, devServer }),
    },
    /**
     * Configures optimization of the built bundle.
     */
    optimization: {
      /** Enables minification based on values passed from React Native CLI or from fallback. */
      minimize,
      /** Configure minimizer to process the bundle. */
      minimizer: [
        new TerserPlugin({
          test: /\.(js)?bundle(\?.*)?$/i,
          /**
           * Prevents emitting text file with comments, licenses etc.
           * If you want to gather in-file licenses, feel free to remove this line or configure it
           * differently.
           */
          extractComments: false,
          terserOptions: {
            format: {
              comments: false,
            },
          },
        }),
      ],
      chunkIds: 'named',
    },
    module: {
      /**
       * This rule will process all React Native related dependencies with Babel.
       * If you have a 3rd-party dependency that you need to transpile, you can add it to the
       * `include` list.
       *
       * You can also enable persistent caching with `cacheDirectory` - please refer to:
       * https://github.com/babel/babel-loader#options
       */
      rules: [
        {
          test: /\.[cm]?[jt]sx?$/,
          include: [
            /node_modules(.*[/\\])+react\//,
            /node_modules(.*[/\\])+react-native/,
            /node_modules(.*[/\\])+@react-native/,
            /node_modules(.*[/\\])+@datadog/,
            /node_modules(.*[/\\])+@native-html/,
            /node_modules(.*[/\\])+native-base-shoutem-theme/,
            /node_modules(.*[/\\])+rn-emoji-keyboard/,
            /node_modules(.*[/\\])+rn-placeholder/,
            /node_modules(.*[/\\])+@react-navigation/,
            /node_modules(.*[/\\])+@react-native-community/,
            /node_modules(.*[/\\])+@expo/,
            /node_modules(.*[/\\])+pretty-format/,
            /node_modules(.*[/\\])+metro/,
            /node_modules(.*[/\\])+abort-controller/,
            /node_modules(.*[/\\])+@callstack\/repack/,
            /node_modules(.*[/\\])+@gorhom\/bottom-sheet/,
            /node_modules(.*[/\\])+@gorhom\/portal/,
            /node_modules(.*[/\\])+@segment\/analytics-react-native/,
          ],
          use: 'babel-loader',
        },
        /**
         * Here you can adjust loader that will process your files.
         *
         * You can also enable persistent caching with `cacheDirectory` - please refer to:
         * https://github.com/babel/babel-loader#options
         */
        {
          test: /\.[jt]sx?$/,
          exclude: /node_modules/,
          use: {
            loader: 'babel-loader',
            options: {
              /** Add React Refresh transform only when HMR is enabled. */
              plugins:
                devServer && devServer.hmr
                  ? ['module:react-refresh/babel']
                  : undefined,
            },
          },
        },
        /**
         * This loader handles all static assets (images, video, audio and others), so that you can
         * use (reference) them inside your application.
         *
         * If you want to handle specific asset type manually, filter out the extension
         * from `ASSET_EXTENSIONS`, for example:
         * ```
         * Repack.ASSET_EXTENSIONS.filter((ext) => ext !== 'svg')
         * ```
         */
        {
          test: Repack.getAssetExtensionsRegExp(Repack.ASSET_EXTENSIONS),
          use: {
            loader: '@callstack/repack/assets-loader',
            options: {
              platform,
              devServerEnabled: Boolean(devServer),
              /**
               * Defines which assets are scalable - which assets can have
               * scale suffixes: `@1x`, `@2x` and so on.
               * By default all images are scalable.
               */
              scalableAssetExtensions: Repack.SCALABLE_ASSETS,
            },
          },
        },
      ],
    },
    plugins: [
      /**
       * Configure other required and additional plugins to make the bundle
       * work in React Native and provide good development experience with
       * sensible defaults.
       *
       * `Repack.RepackPlugin` provides some degree of customization, but if you
       * need more control, you can replace `Repack.RepackPlugin` with plugins
       * from `Repack.plugins`.
       */
      new Repack.RepackPlugin({
        context,
        mode,
        platform,
        devServer,
        output: {
          bundleFilename,
          sourceMapFilename,
          assetsPath,
        },
      }),
    ],
  };
};

@oferRounds ok I think I know what you mean now, you're talking about the output path for images. All images found within a project are always put inside of the assets directory in inside of the build and there is no way to configure that atm.
May I ask what is your use-case here? Why does the path matter in this case?
With all of that said, we're planning a big refactor to the assets loader API so it's more aligned with Webpack - this alignment would make something like this possible (as long as this is what you need)


[Share] Why am i not able to add image in the share plugin?

There are few share plugins for flutter. Most of them are not up to date.
This Share plugin is maintained by flutter and very easy to use.
I want to share text along with an image to invite friends.
But Share plugin is limited and unable to send image.
Can you please consider to add this feature in Share plugin?

Hi @maheshkumar2150
Please follow up on https://github.com/flutter/flutter/issues/9817, https://github.com/flutter/flutter/issues/19607, https://github.com/flutter/flutter/issues/36894
I'm closing the current one as duplicate.
If you disagree please write in the comments and I will reopen it.
Thank you

I just checked those links sir.
I am really disappointed. Such a beautiful framework which lacks an important feature.
Many flutter developers have already requested this feature.
I have half finished flutter and disappointed to see that there is no good plugin for image sharing.
Have to drop this project from flutter and move to react
But i got motivated myself and learning android from udacity :-)
Thank you sir.
No need to open. It has been discussed already and your team is not convinced.


Client doesn't receive UserGroup messages unless membership has TTL

Describe the bug
Client who is a member of a UserGroup doesn't receive messages sent to UserGroups unless their membership has a TTL set.
We didn't see this behavior until we released to our production environment. It worked properly until the deployment.
This might be something we caused on ourselves but I've been unable to find any real documentation on SignalR Serverless UserGroups. It's been really hard diagnosing this and any suggestions for debugging techniques would be greatly appreciated.
To Reproduce
Setup

Use Azure SignalR in Serverless mode.
Use Microsoft.Azure.SignalR.Management to manage hubs.
Have a client already connected with the userId and listening for messages.return ServiceManager.GenerateClientAccessToken(hubName, userId);

Steps

Add user to UserGroup without specifying TTL.await hub.UserGroups.AddToGroupAsync(userId, groupName, ct);

Send message to Group.await hub.Clients.Group(groupName).SendCoreAsync(methodName, args, ct);

Client doesn't receive the message.

Note: Setting a TTL in step 1 fixes the issue. Eg:
await hub.UserGroups.AddToGroupAsync(userId, groupName, ttl, ct);

Further technical details

Microsoft.Azure.SignalR v1.5.1
Microsoft.Azure.SignalR.Management v1.5.1
@microsoft/signalr v3.1.10

@BryceBarbara
I think it should be message out-of-order.
AddToGroupAsync only return 202 (Accept), the AddUserToGroup operation is still on the way, when you sending group broadcast.
There are two ways to fix the issue:

If you can know the connection id, use add connection to group, it will return 200 (OK), and ensure the operation is completed.
Still use AddToGroupAsync, but check user status by IsUserInGroup, and wait for true, then sending broadcast.

It turned out the problem actually did still remain even with the TTL set so I'll be closing this issue since it was invalid. I'll open a new one specific to this issue without assuming a solution.
@vwxyzh Thank you for your suggestion! I actually have a couple broadcasts going to the group every minute or so and none of them are received. If I understand you correctly, then the users should be receiving the later broadcasts but they aren't.
I think our production server is just unable to add users to groups... but I have no idea why? I don't know how to debug it since the Azure SignalR service is essentially a black box so I'm a bit at a loss.


Upgrade for COMPAT with slate 0.23+ [WIP]

Only one test failing at the moment, weird selection bug with removing a table that I can't seem to figure out.
everything else checks out so far

it looks like the shorthand of node.length used to work, but now it's required that we do node.text.length

OK, everything is good, except the selection at the end of the test undo-remove-table.
It should be on the cell Col 1, Row 1.
Using<EMAIL_ADDRESS>it is instead on the cell Col 0, Row 1 (weird).
Using<EMAIL_ADDRESS>it is not restored, and stays on the paragraph before the table that was removed (sensible... but maybe not ideal).
I think the issue comes from Slate. We really don't do any magic when removing the table, we just removeNodeByKey on the table node.
I suggest that we change the test to take this into account, and maybe file an issue about this small behavior change.

Awesome totally agree!


Optimized transpilation. Completed more of Send Event action type.

Description
I've improved the transpilation of the library modules to reduce the amount of emitted overhead code. I've completed the Send Event action type except for two things:

It doesn't have UI tests. I want to see what it would take to set up TestCafe using the extension sandbox in order to test the extension's UI. I'll work on that next.
The user will eventually be able to configure multiple Alloy instances from the extension configuration view and then select which instance should be used on the Send Event view. This experience is still being designed by UX, so right now the Send Event action type just assumes it should use the alloy instance.

Related Issue
https://jira.corp.adobe.com/browse/CORE-29012

Motivation and Context
As an example, without these optimizations we get overhead like this:
var _createSendEvent = _interopRequireDefault(require("./createSendEvent"));
var _getInstance = _interopRequireDefault(require("../getInstance"));
function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { "default": obj }; }
module.exports = (0, _createSendEvent["default"])(_getInstance["default"]);

With the optimization, it's reduced to this:
var _createSendEvent = require("./createSendEvent");
var _getInstance = require("../getInstance");
module.exports = (0, _createSendEvent.default)(_getInstance.default);

How Has This Been Tested?
Automated and manual tests.

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

I'm closing this because it causes the following error while running unit tests:
Error: Rollup requires that your Babel configuration keeps ES6 module syntax intact. Unfortunately it looks like your configuration specifies a module transformer to replace ES6 modules with another module format. To continue you have to disable it.

Most commonly it's a CommonJS transform added by @babel/preset-env - in such case you should disable it by adding `modules: false` option to that preset (described in more detail here - https://github.com/rollup/rollup-plugin-babel#modules ).
    at error (/Users/aahardy/dev/rea/node_modules/rollup/dist/rollup.js:3866:30)
    at Object.error (/Users/aahardy/dev/rea/node_modules/rollup/dist/rollup.js:17317:17)
    at Object.error (/Users/aahardy/dev/rea/node_modules/rollup/dist/rollup.js:17750:31)
    at /Users/aahardy/dev/rea/node_modules/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:73:9
    at /Users/aahardy/dev/rea/node_modules/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:202:20

I think the best way to handle this is to not use ES6 modules in our library code.


Don't ignore folders which only contain a .gitignore file

Command
e.g. cf push my-laravel-app

What occurred, incl. error and/or stack trace
cf push ignores all empty folders and treats folders which only contain a .gitignore file as empty. This leads to problems when pushing Laravel applications: https://github.com/laravel/framework/issues/16243

What you expected to occur
I would expect the CLI to push folders which only contain a .gitignore file as empty folders.

CLI Version
6.22.2+a95e24c-2016-10-27

CC API Endpoint Version
2.63.0

Platform & Shell Details
Mac OS X 10.12.1, iTerm2

Thanks! We'll investigate.
Note that if you add a .cfignore file in the root of the app with the following, the "cache" folder is pushed as well.
!/bootstrap/cache

good idea, thanks @dkoper!

This also happened to me today as Symfony is using .gitignore files too. See https://github.com/symfony/recipes/pull/83
The reason is this: https://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-deploy.html#exclude
I think CF should not magically ignore files - I would prefer to have full control.

@dkoper Any chance to get this fixed? Anything I can do? :)

@rogamoore I hope to publish a refactored push that addresses this and other push related issues in the next few weeks. As for what you could do, try it out when we release (I'll add a comment in this story) and let us know if it resolves your issue!
cf push has been magically ignoring certain files for as long as I know. Maybe it should not have, but it does, I assume for good reasons, so I don't want to change that. Skipping folders with only a .gitignore file however sounds like something we should investigate as a bug.

@rogamoore @mastertinner Do you mind trying with v2-push (cf CLI 6.33.0) for your specific use case?

@dkoper Will try this until the end of the week! Thanks!

@dkoper, I can confirm that v2-push doesn't ignore empty directories anymore. Yay! However, if I have a directory containing only a .gitignore file, the directory gets pushed but the .gitignore file it contains doesn't... So when I cf ssh into the container, I can see the directory which contained a .gitignore file on my local machine but I cannot see the .gitignore file it contained.

@mastertinner .gitignore file is ignored by default, as expected according to http://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-deploy.html#ignore-unnecessary-files-when-pushing, right?

Thanks for the clarification, @dkoper.

Also works for me. Thanks @dkoper !


Impossible to use a new Spyder 4.2+

Problem Description
Hi, please, I have a Windows machine and Anaconda installation.
My goal is to update spyder from version 4.1.5 to 4.2.3.
All I simply do is I open the Anaconda Prompt, and all I simply do is running "conda install spyde=4.2.3
This triggers the error message: PackageNotFoundError.
So, test number 1 doesn't work.
Now, I manually installed the 4.2.3 installer. Installation was successful.
However, there's not a single post that shows how to launch this new spyder version.
Just to make things even more clear, using the Windows installer has not uninstall the current version of Spyder (4.1.5).
So, this is a total mess.
Is there any way somebody can show clearly and easily how I can use the new Spyder?
I'm a mix between being desperate and about simply to completely uninstall spyder and move to PyCharm.
I hope somebody here could understand my frustration and provide a simple working solution.
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: 4.1.5
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

@ccordoba12 I did it. Same thing. Spyder doesn't even open.
I checked what the link it's supposed to do, this is what it shows:
C:\bin\Spyder4.2.3\Python\pythonw.exe "C:\bin\Spyder4.2.3\Spyder.launch.pyw"
and both files seem to be there.

Closing because this probably no longer applies to our latest version.


Background Color for Header

Hi
Is there a possibility of having background color in the headers
I tried including this in the example (https://github.com/PejmanNik/puppeteer-report/blob/master/examples/basicWithJs/index.html) , but wasn't able to get the background color
<script>
            function onChange(element) {
                const pageNumberElement = element.getElementsByClassName('pageNumber')[0];
                const totalPagesElement = element.getElementsByClassName('totalPages')[0];

                if (pageNumberElement.textContent === totalPagesElement.textContent) {
                    element.style.color = 'red'
                    element.style.background = '#ececec'
                }
            }
</script>

I was able to find the solution to the above from this
https://github.com/puppeteer/puppeteer/issues/2182
Hence, closing this. Thanks


Check if data exists

Adding an object that can be used to determine if data exists or not!
Example:
  SleekDB::store($store, $directory)
      ->where("email", "="<EMAIL_ADDRESS>      ->exists()
      ->fetch();

This will return a true or false based on the existence of the data that you are looking for.
One of the benefit of using exists() method will be that it can skip extra document checks when all you need to know if a document with some conditions exists or not.
It will also ignore the join operations(if any) of the query.
📢 Join our Telegram channel here: https://t.me/joinchat/LDAP_B1pyu3iZazrBl37Ow

With #68 the exists() method returns the result.

@Timu57 Should it return a boolean response instead since we have first method?

Yes 😊 I meant that it returns boolean instead of a SleekDB object.

Added in SleekDB 2.0!

Added in SleekDB 2.0!


Port-forwarding not working in VPC Virtual Router

ISSUE TYPE

Bug Report

COMPONENT NAME

VR in VPC

CLOUDSTACK VERSION

4.19

CONFIGURATION

Advanced networking, VPC network
OS / ENVIRONMENT

N/A
SUMMARY

It looks like that, starting with CS version 4.19, the VR is not properly forwarding traffic to the VM when a port-forwarding rule is created on a secondary IP assigned to the VR.
STEPS TO REPRODUCE

Create a VPC (or use an existing one).
Create a new network tier.
Create a new VM in the tier.
Assign a new Public IP address to the VR and configure a pf rule on it.
Create a new ACL rule allowing traffic on the public port selected.
Try to reach the service exposed on the VR.

EXPECTED RESULTS

You should be able to reach the service

ACTUAL RESULTS

You can't reach the service. Executing a tcpdump on the VR I saw that traffic is not forwarded to the VM behind it and no nat rules were created in iptables.
Rebooting the VR or re-creating it doesn't resolve.

As a work-around (still a poor one) you can use LB service on the VR instead of PF. Haproxy works as expected.

@cdfgallo
the issue looks same as an issue I reported before: #8366

@weizhouapache it looks similar but it's not related to the VM configuration but on the VR configuration.
The issue is present if any configuration is applied on any other additional IP of the Virtual Router.

@weizhouapache it looks similar but it's not related to the VM configuration but on the VR configuration. The issue is present if any configuration is applied on any other additional IP of the Virtual Router.

oh, I did not notice it, sorry @cdfgallo
are the public port and private port the same ?
can you share the output of iptables-save command in the VPC VR in both scenarios (lb and pf) ?

@cdfgallo I was able to reproduce the issue.
However, I think the ACL rule should use the private port, not the public port. If use private port, both LB/PF should work
The major issue in my testing is, LB on additional public IP range always works, even if the ACL rule list is set to "default_deny".
can you test and confirm it ? @cdfgallo

@cdfgallo I was able to reproduce the issue. However, I think the ACL rule should use the private port, not the public port. If use private port, both LB/PF should work

@weizhouapache
using LB I was able to have it working allowing the public port in ACL rules, insted with port-forwarding it looks like it works with the private port, I'll keep that in mind.

The major issue in my testing is, LB on additional public IP range always works, even if the ACL rule list is set to "default_deny". can you test and confirm it ? @cdfgallo
I'll try that @weizhouapache

@cdfgallo I was able to reproduce the issue. However, I think the ACL rule should use the private port, not the public port. If use private port, both LB/PF should work

@weizhouapache using LB I was able to have it working allowing the public port in ACL rules, insted with port-forwarding it looks like it works with the private port, I'll keep that in mind.

my finding is, the LB always works, no matter what ACL rules are. I have created an issue #9054

The major issue in my testing is, LB on additional public IP range always works, even if the ACL rule list is set to "default_deny". can you test and confirm it ? @cdfgallo

I'll try that @weizhouapache

thanks @cdfgallo
If port forwarding works with the ingress rule with private port , can we close this issue ?

my finding is, the LB always works, no matter what ACL rules are. I have created an issue #9054

I'd guess that LB works because its iptables rules are in the "INPUT" chain which is checked before the "FORWARD" chain (where the ACL for the tier resides).

The major issue in my testing is, LB on additional public IP range always works, even if the ACL rule list is set to "default_deny". can you test and confirm it ? @cdfgallo

I'll try that @weizhouapache

thanks @cdfgallo If port forwarding works with the ingress rule with private port , can we close this issue ?

@weizhouapache yes, we can close the issue!

my finding is, the LB always works, no matter what ACL rules are. I have created an issue #9054

I'd guess that LB works because its iptables rules are in the "INPUT" chain which is checked before the "FORWARD" chain (where the ACL for the tier resides).

agree @cdfgallo
thanks for the points.

The major issue in my testing is, LB on additional public IP range always works, even if the ACL rule list is set to "default_deny". can you test and confirm it ? @cdfgallo

I'll try that @weizhouapache

thanks @cdfgallo If port forwarding works with the ingress rule with private port , can we close this issue ?

@weizhouapache yes, we can close the issue!

closing


Facilitate documenting platform-exclusive classes

This allows generating documentation templates for plaform-exclusive APIs based on duplicate noop-definitions in an api directory per platform.
Definitions of platform-exclusive classes must be duplicated in platform/<platform>/api/api.h without implementation. This makes the classes available in the editor, which then allows dumping the doc templates per doctool.
Documentation for the JavaScript singleton in the HTML5 platform is included.

I'm not fond of the idea of making a dummy class just for documentation sake. If the dummy class and the real singleton gets out of sync, it'll be very confusing for users.

I think this is the best way actually, because it also makes it work for
code completion.
On Thu, Nov 16, 2017 at 12:52 AM, George Marques<EMAIL_ADDRESS>wrote:

I'm not fond of the idea of making a dummy class just for documentation
sake. If the dummy class and the real singleton gets out of sync, it'll be
very confusing for users.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/12961#issuecomment-344807827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z26C0cSzZplVHAUvzfISwhiEYkNPoks5s27GMgaJpZM4Qf5Wk
.

and not only that, lets you write code that may work for multiple platforms
and still compiles
On Thu, Nov 16, 2017 at 9:36 AM, Juan Linietsky<EMAIL_ADDRESS>wrote:

I think this is the best way actually, because it also makes it work for
code completion.
On Thu, Nov 16, 2017 at 12:52 AM, George Marques<EMAIL_ADDRESS>
wrote:

I'm not fond of the idea of making a dummy class just for documentation
sake. If the dummy class and the real singleton gets out of sync, it'll be
very confusing for users.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/12961#issuecomment-344807827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z26C0cSzZplVHAUvzfISwhiEYkNPoks5s27GMgaJpZM4Qf5Wk
.

Wouldn't it possible to use the same class definition for both the real singleton and the dummy one, then protect the implementation under compiler guards? The api.h header here is almost the same as the real singleton at javascript_eval.h.
If there isn't a simple way to do it, then I'm okay with this.

Don't merge yet, I'm trying something

Updated to avoid duplication


openssl broken on darwin

Basic info

Kernel: Darwin yoneda.local 15.0.0 Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64 x86_64
Nix version: 1.10
Nixpkgs version: 16.03pre-git

openssl is broken on darwin
% nix-env -i openssl                                                                                ✭
installing ‘openssl-1.0.2f’
these derivations will be built:
  /nix/store/bsr4hs13qnywhn03zcnfhybwyll53jn0-openssl-1.0.2f.drv
building path(s) ‘/nix/store/ljlwsz12xzychazgvrk0b6jj4vnxv9kq-openssl-1.0.2f-man’, ‘/nix/store/ryqsi5hxbdpkh8mn7mzzl1rn8cl6kas3-openssl-1.0.2f’
unpacking sources
unpacking source archive /nix/store/3sni74rpjihw3scr68q1267s4iyn06m6-openssl-1.0.2f.tar.gz
source root is openssl-1.0.2f
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file openssl-1.0.2f/tools/c_rehash
patching sources
applying patch /nix/store/k8vd1ipx16i7biim8h1hq6n4w53ih1xm-use-etc-ssl-certs.patch
patching file crypto/cryptlib.h
Hunk #1 succeeded at 81 with fuzz 1.
applying patch /nix/store/gsh35p2jcp7nvgmk8zskm2vw06hlzjrc-darwin-arch.patch
patching file Configure
Hunk #1 FAILED at 579.
1 out of 1 hunk FAILED -- saving rejects to file Configure.rej
builder for ‘/nix/store/bsr4hs13qnywhn03zcnfhybwyll53jn0-openssl-1.0.2f.drv’ failed with exit code 1
error: build of ‘/nix/store/bsr4hs13qnywhn03zcnfhybwyll53jn0-openssl-1.0.2f.drv’ failed

This problem is apparently introduced by  917ca8920da46b94867a01590423f66390a152c0 and cc2cec63007f6974130a7ba8a491761be5887528

@edolstra can you have a look at those ?

Doing a nix-channel --update and a nix-env -i openssl on OS X did simply download the openssl-1.0.2f binary and install fine for me.

@knedlsepp  uuhm.. well I happened to do a nix-shell -p nodejs-5_x which tries to build openssl and fails with the output I pasted above. I'm the newbie here so if I am doing something silly which is entirely possible I am all ears ;)

@knedlsepp  uuhm.. well I happened to do a nix-shell -p nodejs-5_x which tries to build openssl and fails with the output I pasted above. I'm the newbie here so if I am doing something silly which is entirely possible I am all ears ;)

@knedlsepp: that's a different openssl version. We have 1.0.1* as the default and 1.0.2* for a few cases including nodejs.

Ah, I'm sorry, I looked wrong and got confused about our defaults by attribute and nix-env names aren't always consistent.

Added the full build output for openssl above

I can't see the full log. (Note: I won't really debug this myself, as I don't even have any darwin machine.)

@vcunat what other info can I provide?

@gilligan I also only started using nix recently. What was really helpful in finding problems was to follow these instructions: https://nixos.org/wiki/Debugging_a_Nix_Package "Step Through Build Phases" and then view the step by step output. You should try to find out why "patching file Configure
Hunk #1 FAILED at 579."

No use stepping here. The patch doesn't apply. It probably did before some version bump but no longer does. Someone has to decide if it's still needed and either drop it or port it to the new version.

@knedlsepp @vcunat yes the actual error is obvious: the patch fails. I am just not able to judge this. Since @edolstra made the last changes I hope he could shed some light on this.

cc @copumpkin

@domenkozar will try your fix. Building will just take some time ...

@domenkozar openssl builds just fine now. I did the silly mistake of wanting to try this via nix-env -i nodejs_5-x which is how I initially noticed the problem but that lead to compilation that went on through the whole night and still has not fnished ..
Anyway .. nix-shell -p openssl just finished without any issue and installed openssl-1.0.1-r

Anyway .. nix-shell -p openssl just finished without any issue and installed openssl-1.0.1-r

That's a different openssl version. The one with problems would be tested by nix-shell -p openssl_1_0_2.

Sorry, my bad. Tried again now building the correct version. Works
[nix-shell:~/nixpkgs]$ openssl
OpenSSL> version
OpenSSL 1.0.2f  28 Jan 2016
OpenSSL>
───────────


Remove default package name of com.example in boot new command

This allows for the repo to be cloned 'as is' and not force a change of package name.

resolved in d5be9811b46128a0474de1b2f0b6dab0cd88e06b


Feature Request: Save web images as attachments not links to it

Please add feature to Save web images as attachments not to links to it on web.
This is usefull for example for offline viewing article.
Sorry for my english.

I find this especially useful for future-proofing saved articles. Web pages and as a result the links to pictures change by time. An option to save the images instead would be very useful.


how to this...?

OMG... Help me please.
I use React-Native with JSHint
But! See error.
I did Google search. Through the setup, the grammar of es was also applied. But there is an error.
Issues found : https://github.com/Microsoft/vscode-jshint/issues/29

JSHint can't parse JSX syntax, but the extension is running JSHint on the entire file, so it is erroring on the JSX syntax. This is a bug that isn't easy to fix, but as a workaround for now you could use /* jshint ignore:start */ and */ jshint ignore:end */ above and below the render method.
type Props = {}; looks like Typescript to me, should this be a .tsx file?

This file is React-Native example file and "*.js/javascriptreact".
I see. I use /* jshint ignore:start */ and */ jshint ignore:end */ above and below the render method.
type Props = {};
Let's find another solution to this.
Thank you so much for answering. :)
Have a nice day~~~

And although there is still a bug(*JSX Parsing bug) left, I will close this issue.


Docs: Possibly outdated memory64 support status in contributing-architecture.md

I'm new to everything WASM, but I suspect this part of the documentation is outdated 😊:
https://github.com/bytecodealliance/wasmtime/blob/367bdc8c66df62d6854966a90564b42692a3f023/docs/contributing-architecture.md?plain=1#L391-L393
https://github.com/bytecodealliance/wasmtime/blob/367bdc8c66df62d6854966a90564b42692a3f023/docs/stability-wasm-proposals-support.md?plain=1#L26

Thanks! memory64 is indeed supported so I've opened https://github.com/bytecodealliance/wasmtime/pull/6868 to update the docs.


Add python-serial entry for focal

Needed for rosserial release in Noetic.

No response for a month, so closing.  Do feel free to fix up the issues pointed out in review and reopen.  Thanks for the contribution.


Backport 2.7:  Fix minor typos and spelling mistakes

Description
This is a backport of #2371.
The PR fixes numerous spelling mistakes and typos in the source code and documentation.
Note - all spellings are to 'International English' (eg. American).
Fixes #2370.
Status
READY

Pinging @Patater for review, as this PR is targeted for 19.02.


External lfs server handling is inconsistent

Description
I added an external lfs server to my repo and then added gitea as secondary remote and pushed to it via git push gitea.
Gitea throws an error in the UI when LFS objects are accessed: getFileReader, LFS Meta object does not exist, even though the data in .lfsconfig should be enough to access them.
The lfs settings panel shows no lfs objects in the repo (as expected) but if I click on Find Pointer Files the objects are marked as "Exists in store"
I reproduced it on gitea.com here: https://gitea.com/tionis/external-lfs-server-bug
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker-compose
Database
None

Can you create a example repository in Github so that we can know how Github handle it?

I also tried to push a demo repo to gitlab but it flat out refused to accept my push due to missing lfs files and I can't seem to find a way to disable this pre-receive hook


Cosmos DB cannot update throughput DTU at database level

Although you can set the throughput when you create a database using:
az cosmosdb database create --throughout 500
If you run the create command again you will get an error stating the resource already exists, which makes sense. So we need something like:
az cosmosdb database update --throughput 500

There are two issues here:

Missing an update command (feature request)
A create command is not idempotent, which is violation of the CLI standards. https://github.com/Azure/azure-cli/blob/dev/doc/command_guidelines.md#standard-command-types

Good point.
Ideally, i should just be able to run the create command again with a new throughput, and it will know the database already exists and just update the throughput.
Otherwise, I need to check for existence first, then run either create or update, which is more difficult. (obviously not impossible):
databaseExists=$(az cosmosdb database exists --resource-group $resourceGroup --name $cosmos --db-name $cosmos_database )
if [ "$databaseExists" = false ]; then
   echo "Creating cosmos database [$cosmos_database]"
   out=$(az cosmosdb database create --resource-group $resourceGroup --name $cosmos --db-name $cosmos_database --throughput $cosmos_throughput)
   echov "$out"
else
    echo "Cosmos database [$cosmos_database] exists"
    ## run update command (which currently does not exist)
fi

Hi @Dave76, thank you for raising this issue. We are currently working on changing the way databases and collections are accessed by the CLI. Currently, the CLI uses "azure-cosmos", which is a data-plane python package. Soon, the CLI will instead access collections and databases through our resource provider.
When this change is made, you will be able to update database level throughput. The target date for completion of this work item (416566) is September. We will keep you updated as work progresses.

Thanks @shurd. Please let me know when this work item is complete.

Hi @Dave76, in version 2.0.71 of the CLI, we released a preview version of the new database and collection management. As a part of this change, you can update database level throughput.
Creating a MongoDB database with shared throughput:
az cosmosdb mongodb database create --account-name {account_name} -n {database_name} --throughput 500 -g {resource_group}

Updating throughput:
az cosmosdb mongodb database throughput update -a {account_name} -n {database_name} -g {resource_group} --throughput 600

If you run the same "create" command and attempt to update throughput via that command, you will get a bad request exception as we do not allow throughput update through that codepath. Running the same exact "create" command twice (with no throughput update) no longer throws an exception.


#12 issue solved - Changes done in the UI of  home page better user Interaction.

📋 Description

🔨 Changes Made

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] I have followed all the guidlines mentioned in CONTRIBUTING.md.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] Bug fix (non-breaking change which fixes an issue) 🐛

[ ] New feature (non-breaking change which adds functionality) ✨

[x] UI enhancement (non-breaking change which enhances UI) 🎨

[ ] Documentation update 📚

Fixes #

📸 Screenshots (if applicable)

Thank you for contributing to Research Nexus! We look forward to reviewing your PR and getting it merged!

Okay @Harshdev098 I'll do that

Hello @Harshdev098 I have done the changes . Please Check it out.

Are the background image that you have set in the screenshot is not working

@Harshdev098 actually it's working fine at my end, I have set the right path for it.

@Harshdev098 I have done all the changes as you said
changed the path for background image [x]
the input size of search box is increased about 22vw. [x]
The notification btn is working fine now. [x]

@SoumyaU25 Delete the .vscode folder

Okay @Harshdev098

Done @Harshdev098


Typos in Comments correction

Added little more descriptive comment. This one is the follow up to the PR that was 4 months old and i had to close it because it had redundant commits.

👍


Sleuth support for binders with embedded headers

Hi,
I've been investigating using Sleuth and Zipkin with Spring Cloud Stream.
It seems that Sleuth's headers (like most headers) are discarded for binders with embedded headers (e.g. Kafka) so that those messages are never included in a trace.
This is not an issue with things like Rabbit, since it natively supports headers, and it works nicely.
I know that Kafka's lack of headers means this isn't an ideal situation, but there is currently a mechanism to include content-type as an embedded header. Any thoughts on extending that support to Sleuth?
Thanks

@barrycommins Spring Cloud Sleuth already uses the header embedding mechanism for Kafka and configures the binder accordingly.

@barrycommins perhaps https://github.com/spring-cloud/spring-cloud-sleuth/issues/282 is related?

Hi @mbogoevici ,
does it? I'm willing to concede that it was something I've misconfigured :-)
What I'm seeing is that the headers are set correctly in the Spring Integration Message , but are not passed to the payload in the Kafka message, e.g. X-B3-TraceId, X-B3-SpanId, etc.
Edit:
@donovanmuller 's answer looks like a workable solution though.
Thanks guys

@barrycommins - you are welcome.  If would be good to know if this doesn't work out of the box and why, because the original issue should have been fixed via https://github.com/spring-cloud/spring-cloud-sleuth/issues/284.

@mbogoevici I've had a quick look at this again, and at the moment I'm using Kafka as a messaging broker, but not using it to send traces to Zipkin (I'm using HTTP).
I have spring-cloud-starter-stream-kafka on my classpath, but not spring-cloud-sleuth-stream, so the fix in StreamEnvironmentPostProcessor is applied.
Perhaps this isn't really a valid use case?

@barrycommins Ah, ok - the original issue referenced Sleuth, which is why I went that route. The configuration for transported headers is here: http://docs.spring.io/spring-cloud-stream/docs/Brooklyn.BUILD-SNAPSHOT/reference/htmlsingle/#_kafka_binder_properties
And that is consistent with @donovanmuller 'suggestion (thanks!). We do require headers to be configured explicitly with the Kafka binder.

@mbogoevici , sorry for any confusion. This has all been useful information.
I think I have enough to proceed, so I'll close this issue.
Thanks again.


DNN-9232: upgrade jquery to 3.1.1.

Note for compatible with jquery UI and other jquery plugin, the jquery migration plugin is required when register jquery.

This should be updated to jQuery 3.2.1.

code review done


bug: Android "arrow-forward" not showing up for <button

Type: bug
Ionic Version: 2.x
Platform: android 5.1 webview
When I create a button list-item, on iOS it shows the arrow-forward icon on the right, but on Android it does not.
Here's an iOS example: http://cl.ly/3p3j291y1I2r
Here's an Android example: http://cl.ly/451X3K0u023w
As you can see, without the arrow-forward it makes it impossible to know which areas are clickable.
Is this a bug, or intentional?  If intentional, it seems like it might be worth reconsidering.
Cordova CLI: 5.4.1
Gulp version:  CLI version 3.9.0
Gulp local:
Ionic CLI Version: 2.0.0-beta.15
Ionic App Lib Version: 2.0.0-beta.8
ios-deploy version: Not installed
ios-sim version: 5.0.4
OS: Mac OS X El Capitan
Node Version: v5.2.0
Xcode version: Xcode 7.2 Build version 7C68

Sorry.. this is better as a discussion on the forums.


Update to 1.12.2

The mod is flagged on Curse as being for 1.12 only, stopping it from being installed on Twitch launcher or being used in modpacks. Could you flag it as being available for 1.12.2?

Done.


Wrong handling  of key pressing in input

Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
Input value changed after click and press "Up" button
What is the expected behavior?
Input value should not be changed
How would you reproduce the current behavior (if this is a bug)?
import { Selector, ClientFunction } from 'testcafe';

fixture `fixture`
    .page `http://dolzhikov-w8/172/RegressionTestsSite/ASPxEditors/ASPxDateEdit/T187651.aspx`;

test('test', async t => {
    const input = Selector("#ASPxDateEdit1_I");

    await t.click(input);

    var oldValue = await input.value;

    await t
        .pressKey("up")
        .expect(input.value).eql(oldValue);
});

Specify your

testcafe version: 0.18.6-dev20171222

I'm working on this

The issue will be closed after updating testcafe-hammerhead.