urlBase stopped working from 1.8.0 to latest

Describe the bug
I installed pigallery2 from github (clone repository), and let pigallery2 generate a new fresh config.json. Everything works as expected. After modifying config.json to use publicUrl and urlBase, site stopped working when accesing using the reverse proxy.  Same configuration works ok in 1.8.0, so I think this is a regression.
Using the console view from chrome, shows that no urlBase is getting appended to host when requesting styles...css, runtime...js,  polyfills...js or main...js. The server returns 404.
It wass correctly appended in 1.8.0. Calls to api/notifications get the urlBase appended to the host.
Environment (please complete the following information):

OS: debian
Browser: doesn't matter, tried Chrome and Explorer

Used app version:

compiled from source (git clone).

Hi,
Thank you for reporting, I know about the issue a fix should come shortly.
On Mon, Sep 7, 2020, 01:59 diego torres<EMAIL_ADDRESS>wrote:

Describe the bug
I installed pigallery2 from github (clone repository), and let pigallery2
generate a new fresh config.json. Everything works as expected. After
modifying config.json to use publicUrl and urlBase, site stopped working
when accesing using the reverse proxy. Same configuration works ok in
1.8.0, so I think this is a regression.
Using the console view from chrome, shows that no urlBase is getting
appended to host when requesting styles...css, runtime...js, polyfills...js
or main...js. The server returns 404.
It wass correctly appended in 1.8.0. Calls to api/notifications get the
urlBase appended to the host.
Environment (please complete the following information):

OS: debian
Browser: doesn't matter, tried Chrome and Explorer

Used app version:

compiled from source (git clone).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bpatrik/pigallery2/issues/178, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZKA5RK5KRINKEB6KQRSHLSEQO7JANCNFSM4Q5C53BQ
.

The latest commit should fix this

I can confirm this. Thanks!!

i'm seeing this on the current nightly-stretch docker container

Hi,
Sorry, I'm still facing this issue, I guess that's similar actually.
Loading URL in browser and getting "Loading" with icon of missing image... then nothing else.
Describe the bug
css, runtime...js, polyfills...js or main...js. The server returns 404.
Environment (please complete the following information):

OS: Ubuntu
Browser: doesn't matter, tried Chrome and Firefox
Apache2 as reverse proxy including conf:

       ProxyPass /pigallery2/ http://<IP_ADDRESS>:8085/
       ProxyPassReverse /pigallery2/ http://<IP_ADDRESS>:8085/

Used app version:

Docker image: bpatrik/pigallery2:latest
Apache2 as reverse-rpxoy

Hi,
Sorry, I'm still facing this issue, I guess that's similar actually.
Loading URL in browser and getting "Loading" with icon of missing image... then nothing else.
Describe the bug
css, runtime...js, polyfills...js or main...js. The server returns 404.
Environment (please complete the following information):

OS: Ubuntu
Browser: doesn't matter, tried Chrome and Firefox
Apache2 as reverse proxy including conf:

       ProxyPass /pigallery2/ http://<IP_ADDRESS>:8085/
       ProxyPassReverse /pigallery2/ http://<IP_ADDRESS>:8085/

Used app version:

Docker image: bpatrik/pigallery2:latest
Apache2 as reverse-rpxoy

Thanks. I'll look into it.
In the mean time pls. make sure that you set up your urlBase the proper way in the settings.

Thanks. I'll look into it.
In the mean time pls. make sure that you set up your urlBase the proper way in the settings.

Thanks for looking into this issue.
Checked the config.json file:
        "urlBase": "/pigallery2",

Thanks for looking into this issue.
Checked the config.json file:
        "urlBase": "/pigallery2",

Can you check if this still an issue with the nigthly build ? (or with 1.8.5)
I think this should work now.

Hello,
Unfortunately, problem persists.
I've updated my docker-compose.yml to use bpatrik/pigallery2:nightly-alpine and cleaned my browser cache but I'm still facing this issue...

That is odd. It works for others (https://github.com/bpatrik/pigallery2/issues/264#issuecomment-823156514).
Did you also explicitly pull this newer version, docker does not do that for you.
Is it properly set up? (like no typo, right place in the json) If you can open the app, you can double check it on the UI (if it shows up, it works)

I'm getting crazy.
I've removed all docker images related to pigallery2.
Checked config.json file.
Checked Apache configuration:
        <Location /pigallery2>
                ProxyPass http://<IP_ADDRESS>:8085
                ProxyPassReverse http://<IP_ADDRESS>:8085
        </Location>

Started container based on bpatrik/pigallery2:nightly-alpine.
I'm still facing the same issue.
I don't get it.
BTW, when I use web developer function in Firefox, I get some errors like:
GET https://www.mydomain.com/assets/icon.png
Status404
Not Found
VersionHTTP/2
Transferred402 B (276 B size)
Referrer Policystrict-origin-when-cross-origin

(mydomain.com has been changed for this report)

Does this help? https://github.com/bpatrik/pigallery2/issues/152#issuecomment-614459658
I never used apache, so I'm not sure how to set that up.
This:
GET https://www.mydomain.com/assets/icon.png
Status404

means that you do not have a urlBase setup:
"publicUrl": "",
 "urlBase": "",

Otherwise if  "urlBase": "/test", the request would have been  https://www.mydomain.com/test/assets/icon.png

OK problem fixed !!! Thanks.
Here, what I did:

Stop container
Backup config.json file
Delete config.json file
Start container (an "empty" config.json file is generated)
Stop container
Update config.json file according to my configuration (publicUrl and urlBase settings only)
Start container
Access pigallery2 interface
Rulez !
Thanks!!

Super! I'm happy to hear!


A numpy/cupy project on top of Directml

Hi, I'd like to know if the team behind directml has plans to release a like-numpy/cupy library using Directx 12 for computing, this would open up for a lot of possibilities, since a lot of numerical libraries use numpy for computing, having an option to accelarate such operations, I can see pandas using this, and many researchers implementing tools for this.
I also would like to have info on how to use the low-level math ops from directml.

@limapedro Thanks for the suggestion. We currently have no plan for a Cupy-like library on DX, but it's an interesting thought. I can see how that can be useful to libraries already supporting numpy semantics but want compute to run on all the GPU.
As for your last sentence, it sounds like you're asking how to access directml core functionality without passing through TensorFlow? Can you tell me more about the scenario you have in mind?

@wchao1115 I'm also very interested in using low-level math ops from directml. Our team developped an algorithm realies heavily on numpy's tensor / matrix operations like einsum, tensordot, matmul etc. because the numpy APIs are so easy to get started. Now we need to speed up the algorithm to meet real-time needs in a production environment that has no Nvidia GPUs. So we are looking into directml now but can't figure out how to do tensor (matrix) multiplications with directml.


revert redesign for corp

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 83.352%

Totals

Change from base Build<PHONE_NUMBER>4:
-0.01%

Covered Lines:
10246

Relevant Lines:
11297

💛  - Coveralls


Slovenian data missing Postal Name

Hi,
99% of time when people write address in Slovenia they include postal name, see examples:
Government of the Republic of Slovenia, Gregorčičeva 25, 1000 Ljubljana
Pliskovica 11, 6221 Dutovlje
Jezero 79a, 1352 Preserje
So Ljubljana, Dutovlje and Presereje are basically postal names and postal codes like 1000, 6221 and 1352 are codes for those cities. (Notice that one Postal Name can have multiple codes, for example Ljubljana).
Problem is, that today in openaddresses data for Slovenia, postal name is missing. city property is used for settlement name(village, town city...), which I agree makes most sense, but district is used for multicipality(which is never? used for addresses) and region is used for statistical regions.
But neither district nor region, really fits as postal name, so my question is... Where should postal name be? Omitting it completely also feels wrong.
Thank you,
David

Some background:
The postal areas in Slovenia are described with 4-digit zip code + matching area name.
Unlike some countries (eg UK) there are fewer postal areas () than cities () in Slovenia
Postal areas are defined by the Post of Slovenia and smaller places (villages are typically joined in the postal area named after the largest nearby town)
Some postal codes are not geographical, but dedicated to a company which receives a lot of mail (mail order
Interestingly there are cases where not even street + housenumber + zip code + zip area name are not uniquely describing an address, but it becomes unique by including the city name in the address.
The list of 4 digit codes and area names are published in https://www.posta.si/naslavljanje under the "Dokumenti" section.
Current implementation
The current address conform for Slovenia is:
https://github.com/openaddresses/openaddresses/blob/cfe057a56fbc2525778fe6fff6cc1caf6fe598f4/sources/si/countrywide.json#L26-L47
Possible fix
We could easily join the 4-digit zip code (POSTNI_OKOLIS_SIFRA) and corresponding area name (POSTNI_OKOLIS_NAZIV) into the same postcode field, separated by a single space using join attribute function. Not ideal, but could be easily split if needed.
                    "postcode": {
                        "function": "join",
                        "fields": ["POSTNI_OKOLIS_SIFRA", "POSTNI_OKOLIS_NAZIV"],
                    },

Hi! This confirms that address formats vary a lot from country to country. In fact, address formats change from town to town within the same country. We need to have an Address Format for every jurisdiction. This is what we have done at AddressForAll. We have a table that describes the Address Format for every jurisdiction in text. This address format may also contain some code that interprets how to parse the string with the full address into different fields.


[GHSA-r45x-ghr2-qjxc] #[zeroize(drop)] doesn't implement Drop for enums

Updates

CVSS
CWEs
Description
Severity

Hi @xfix, thank you for the contribution! Do you have a source for the CVSS score that you can link me to?

Right, I will admit that I calculated this myself. That said, I just noticed that a CVE was filled for this with CVSS score of 9.8 on CVE-2021-45706. Personally I don't see how impacts Integrity or Availability, so I think I will contact NVD about that, and will try to get a more reasonable score for this vulnerability.
Anyway, it seems like GHSA-c5hx-w945-j4pq and GHSA-r45x-ghr2-qjxc are the same vulnerability, so I think it may make sense to merge those if that's possible.

I contacted NVD about CVE-2021-45706, and they assigned CWE-459.

@xfix Thanks for bringing the duplicate advisory to our attention. We can't deduplicate advisories, but we have updated the description to point users to the original advisory that is attached to the CVE. Your community contribution credits appear on GHSA-c5hx-w945-j4pq and GHSA-r45x-ghr2-qjxc.


metric: Avoid memory leak/increase in cilium-agent

Description
This commit is to make sure that the processed item in pod deletion queue is removed by explicitly call Done() function as per suggestion in godoc^1 .
The impact of not having this change will be increasing of memory in cilium agent when the hubble metrics are enabled. This might take days (if not weeks) to observe in a normal Cilium deployment due to low number of Pod deletion events (i.e. in high churn environment, the memory will be increasing in a faster pace).
Testing is done before and after the changes as per below.
Sample workload to simulate high number of pod deletion events
apiVersion: batch/v1
kind: Job
metadata:
  name: pod-churn-job
spec:
  completions: 50000000
  parallelism: 100
  template:
    metadata:
      labels:
        app: pod-churn-job
    spec:
      containers:
      - name: churn-app
        image: sandeshkv92/highpodchurn:linux_amd64
      restartPolicy: Never

Before this change, the cilium agent memory keeps increasing from 150MB to ~500MB in less than 3 hours, while with the same workload configured and this change, the memory is quite stable for a longer period (e.g. 5 hours).
Fixes: 782f934641df5bafd4a9ee737e00872f65f56b64
Testing
Testing was done with the above workload, please refer to the below dashboard for visualization.
Before

After

/test

/test

After dashboard seems to be missing 👀

After dashboard seems to be missing 👀

Thanks, I have updated the PR description, will let it run for some more time before marking this ready to review.


Improve login flow.

Here are few things which are currently going on.

Currently new account is added as soon as user enters realm url.
Currently active account is decided based the index of the account list.
If account is at top of the list, then it is active.

Problems associated with it:
If user is in account of realm lets say A and start process of adding another account (on realm B).
Clicks Switch Account -> Clicks Add new account -> Enters another realm url -> (Optional) Select auth type -> (Optional) enters wrong password. -> Navigate back -> back -> back

Optional here means, this steps can be skipped

Logically the new account has not setup up, but as per our current implementation, this new account is at the top of the list and thus active.
On navigating back stream, users, messages etc of account of realm A are present,

but if user tries to find his/her active account in Account pick screen (after clicking Switch Account), it is showing this newly added account as active in realm B (not completely logged in)
if user tries to fetch new messages, send message they will not succeed as now auth of this half logged in account is active.
if user closes app and re-open, they he is transferred to account pick screen, but I was expecting it to be at home screen of account with realm A, as user has not completely logged in new account.

Solution:
Add account only after he successfully logs in. Send realm url to auth screen & further via screen props instead of via Global state.
As https://github.com/zulip/zulip/commit/383c62fb03267ce09dccb5e0780ebe27075b62fb got merged, so (in dev login) realm url to which user is registered is also included in the user object. (which may not be the same as entered in the realm screen). Basically then app will also support multiple realm on single server.
@zulipbot claim

From reading the issue description, I imagine this is still an active bug. It may make sense to just go ahead with the proposed solution, but this might be an appropriate time to also consider whether we'd like to keep the array-ordering method of identifying the active account.

Linking https://github.com/zulip/zulip-mobile/issues/1411.

I ran into a symptom of this today:

Create two accounts for the same realm.
Log out.
Attempt to log in to the second realm using a password.

The e-mail shown at the password entry screen will be that of the first account. Changing the e-mail in that field will, fortunately, not mutate that account.

[...] this might be an appropriate time to also consider whether we'd even like to keep the array-ordering method of identifying the active account.

Offhand I'd say not – but that alone wouldn't fix the above.

Add account only after he successfully logs in. Send realm url to auth screen & further via screen props instead of via Global state.

This definitely sounds like a good idea to me. It would make a lot of sense for "account we're in the middle of trying to log into" to be treated as (local) UI state, held by a component that's a common ancestor through the login flow and passed down to the other parts of that flow as props. Currently it's treated as (global) app state, held inside the Redux state.
However:

On navigating back stream, users, messages etc of account of realm A are present,

This sounds like a bug, even in the context of the current way we model this data. I think it should be possible to fix straightforwardly, before any big refactor. Does this bug reproduce today?
When you hit "Switch account" and then actually switch to an existing other account, we dispatch an ACCOUNT_SWITCH action, and that causes us (in the various reducers) to clear all our server data. ... Hmm, I see, but despite the names, it looks like that doesn't happen when you simply hit the "Switch account" button, and in particular it won't happen if you do that and then attempt a new login instead of picking an existing account to switch to. So that probably means this bug does still reproduce.
One relatively local way to fix this would be to make it so that when you hit "Add new account", we go ahead and clear all server data just like we do on ACCOUNT_SWITCH. Or maybe more to the point: just like LOGOUT, with the one difference that in accountsReducer we wouldn't discard the API key. (The one somewhat tricky bit is that we'd want to ensure you couldn't then simply navigate back and end up on the main screen without triggering a new initial fetch. Hence LOGOUT as a model: it has the same need, and see navReducer.js for how we take care of it.)
That fix isn't very complicated, but also isn't trivial. I'd be glad to see a PR that did that fix; and either way, if there were a PR to carry out this issue's proposal of keeping the partly-logged-into account out of state.accounts until it's logged into -- and if that PR were itself reasonably simple -- that'd be great.

I've filed #4416 with a more detailed version of the plan described above.

I've filed #4416 with a more detailed version of the plan described above.


e2e framework tests are failing

Link to the failed run https://github.com/open-component-model/ocm-e2e-framework/actions/runs/8962120188/job/24610543597

Actually, the whole runner is out-of-date with recent changes, because we decided that it's a framework that shouldn't run tests and shouldn't contain tests. So the individual projects have their own tests. Meaning, I'm going to disable this runner all together. The MPAS repository contains e2e test runner.


Can't use string ("562") as a SCALAR ref while "strict refs" in use at Taxonomy.pm

I just followed the installation procedure (in a fresh Docker container) and tried the following command to test the installation:
gorap -q 13 -c 8 -k bac -s 562 -r 543 -i $GORAP/db/example/ecoli.fa -a ecoli -l ecoli_ncrna -o results

terminal output
Gorap started - 24.3.2020-14:28:35
Reading FASTA files
/gorap-install/db/example/ecoli.fa
Generating chunks
Searching taxonomy for related species
Can't use string ("562") as a SCALAR ref while "strict refs" in use at /gorap-install/conda/envs/gorap/lib/site_perl/5.26.2/Bio/Gorap/DB/Taxonomy.pm line 163.

Do I miss something?

Update: the command is working when I leave out the -s and -r taxonomy information.


Refactor em strong to consolidate code and fix issue #792

This refactors em strong logic into two processors: one for asterisks and one for underscores.  All logic for the respective emphasis convention is consolidated, and a new pattern is added to handle **strong*em*** and __strong_em___ respectively.

Tests are still needed for the new, fixed case.

Current tests are now passing, but will have to address coverage as well.

PyYaml 5.1 wrecking Python 2 tests 😡 .

PyYaml 5.1 wrecking Python 2 tests.

That is annoying. I understand why PyYAML made the changes they did, but we were relying on the fact that the PyYAML and json libs both used the same API and PyYAML could parse JSON. Now we need a more complicated implementation to account for the differences between the libs' APIs.

Do you know why it is only failing on Python 2?

Do you know why it is only failing on Python 2?

I do not. The lowdown on the changes are here. I suppose we could simply disable the warning as an easy fix. We only use the YAML loader in the CLI so if there is a vulnerability there, the user has much worse problems that arbitrary code injected in a YAML config file.

The PyYAML issue has been addressed in #806. Feel free to rebase your work on master now.

Ugh, everything broke for some reason... Probably need to rebase maybe

Tests appear to be broken due to the latest tox 3.8+.  By forcing 3.7 tox, tests begin passing again.

Maybe related to https://github.com/tox-dev/tox/issues/1236.

Let's see what tox does before we address this. If they fix it quickly in the next release, then we might not need to do anything.

Yeah, I'm obviously in no hurry as I've been taking my time. The current work around was just to identify what I figured was the problem, it isn't meant to be the official solution unless we are desperate.

Okay, I finally got around to rebasing this. Obviously tox is no longer broken, so I reverted the workaround. I'm pretty much done with the work here unless there are further requests. In the future, maybe the NOT_STRONG_RE logic could be incorporated into this, but that would really require rewriting some of the existing patterns which I'm not looking to do at this time.

Look good. Just needs a note in the release notes. Feel free to added a new release-3.2.md file.

As we are removing many existing inline processors and replacing them with two new ones, I think we probably need to make mention of that in the release notes.  For example, if an extension is removing all of the existing inline processors, the dev will need to do some work to make it compatible. The release notes needs to call this out. That's why I suggested 3.2 rather than 3.1.1 for the release.

Makes sense. I'll adjust within the next day or two.


Fix cross-references

Jenkins, test this please.

Jenkins CI test (for commit 5c6a07e0111029973009d071b9f0c1913fc0bd2b) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 5c6a07e0111029973009d071b9f0c1913fc0bd2b) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 4e67f990d4fd5b1cbc1bc75fec5de111329f5f60) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

LGTM! Test failures are not related to this PR.

I squashed the commits.

Jenkins, test this please.

Jenkins CI test (for commit fdfabff81f2e5a27f78cbb0004a21628561b5c2c) succeeded without errors!


Update eval_science_qa.py

Use a set for split_indices and predictions to speed up lookup times.
Read files in a more efficient manner using with statements to ensure proper file handling.
Simplify the loop by combining conditions and removing redundant checks.
Use list comprehensions for filtering and counting.

Can we merge this pull request?


Transactions Invoices support in Invoice service

Describe the bug
Invoices service should support URLs like:
https://invoices.opencollective.com/{collectiveSlug}/transactions/{UUID}/invoice.pdf
It's currently handled by the website codebase that we want to turn off.
https://website.opencollective.com/{collectiveSlug}/transactions/{UUID}/invoice.pdf
This URLs are currently used in a lot of emails, see:
https://github.com/opencollective/opencollective-api/search?q="invoice.pdf"++path%3A%2Ftemplates%2F&unscoped_q="invoice.pdf"++path%3A%2Ftemplates%2F
We will need to migrate these.

Forwarded to invoices service in:
https://github.com/opencollective/cloudflare-workers/pull/6


[Global] Chore: Automate stale issues and PRs (30 days to stale, then 5 days till closing)

PR-Codex overview
This PR adds a GitHub Actions workflow to automatically close stale issues and pull requests after a specified period of inactivity.
Detailed summary

Introduced a new workflow in .github/workflows/stale.yml named 'Close stale issues and PRs'.
Configured the workflow to trigger on a schedule using a cron job.
Set the job to run on ubuntu-latest.
Utilized actions/stale@v9 for managing stale issues and PRs.
Configured messages for stale issues and PRs.
Defined days-before-stale as 30 and days-before-close as 5.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Merge activity

Nov 1, 8:58 PM EDT: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Example in ReactJS

Is there any example of how to implement it in a reactjs application with typescript, there is no example on the internet, and the example in the documentation I didn't find clear

Checkout this example: https://github.com/authts/sample-keycloak-react-oidc-context
It uses Keycloak as the identity provider, but the React app is generic enough.


Allow changing initial state of ToggleButton

Adds a toggled parameter to gui.ToggleButton that determines the initial toggled state of the widget.

Sorry for the delay.
To avoid the extra code in the library, the value property exists for this purpose. All Widgets contain this property to be used for manually setting the value (such as initial value). For example:
my_pushbutton = PushButton(...)
my_pushbutton.value = True

Oh alright, didn't know that. Thanks.


Add project name, package and port to front generator

related to https://github.com/jhipster/jhipster-lite/issues/984

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Quentin France seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Wrapper: find/findAll accepts ref options object

This PR relates to https://github.com/vuejs/vue-test-utils/issues/67
It adds the .ref('someRefName') method to the main wrapper.
This returns a WrapperArray with wrappers for any vnodes that have the specified ref. Additionally, .ref will only match vnodes with refs that exist on the wrapper.vm.$refs.

Do we want to just have a single ref function or do we want to split it into findRefs / findAllRefs? Right now, this only returns a wrapper array.

I haven't implemented tests yet because I wanted to make sure I was going in the right direction first.

The find-matching-vnodes-by-ref.js file that is added here uses some of the functionality from the existing find-matching-vnodes.js file. Should I pull out some of those functions into a more generic vnode traversal file or something?

I'm not sure on the API.  Ideally we would be able to extend find and findAll to handle refs. Let's discuss in #67
That's fine, but we'll need some before me merge
Yes 🙂

Ok, @eddyerburgh, so I know we're waiting on the discussion to resolve in #67 about whether or not the find by $ref functionality should be implemented for all methods that take a "Selector," but this PR implements that functionality in the case that we do decide to move forward with that.
A few notes:

Importing flow-types from vue does not seem to work correctly. Selector was defined as

declare type Selector = string | Component

but it looks like the global imports in flow/vue.js may not actually get imported. So, anywhere that accepted a Selector type was actually accepting any. What should be done about this?

is throws an error if an options object { ref: 'someName' } is passed in because we can't assert that an element matches the $ref selector without access to the component that has that $ref property. (it would be like asking: "is this component a ref of this component")

We throw errors when when trying to select by $ref on non-Vue components.

The naming of this new selector type is currently RefSelector. There may a better way to refer to it

Will need to update docs

As you said, we should hold off until we've had more input from the community. But it looks great so far 🙂

I'll look into this
OK that makes sense
Good
I think that's fine
OK, are you able to do this?

re: 5. Yep, this is in the PR now.

@eddyerburgh Do you have a link to the discussion that is happening around this? Would love to see this land!

@kaicataldo here — https://github.com/vuejs/vue-test-utils/issues/67

Hey @matt-oconnell , are you able to fix the merge conflicts? Then I'll merge

Ok, resolved 👍

Thanks @matt-oconnell 😀


Avoid deprecation warning

Was caused by use of bare variables

Fixed the whitespace issue

Thanks for the PR. You might be interested in an alternative to this role in the form of native Ansible module. The yum_repository module is merged into the upstream Ansible and should be released in the Ansible v2.1. There is  currently no support for the "Managed Mode" in the upstream although a PR for this feature is under discussion. Please feel free to join the discussion if you want to see this feature in the future release.


fix: Fix Ref printing

coverage: 87.289% (+0.3%) from 87.002% when pulling 3a7063ca7a202f21e45baec8459b33fb3a4c7a73 on fix_ref_printing into 67d64694cb2bf6bfda3cf52c3742795fc81c7c65 on main.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.03 :tada:

Comparison is base (67d6469) 87.27% compared to head (3a7063c) 87.31%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   87.27%   87.31%   +0.03%
==========================================
  Files          12       12
  Lines         998     1009      +11
==========================================
+ Hits          871      881      +10
- Misses        127      128       +1

Impacted Files
Coverage Δ

ext/TestingUtilitiesDataFramesExt.jl
98.36% <100.00%> (-0.23%)
:arrow_down:

src/show_values.jl
90.35% <100.00%> (+3.44%)
:arrow_up:

... and 1 file with indirect coverage changes

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


Modify Aggregate Pseudo-Column Comment (Tooltip) Default

Currently we're creating the default tooltip for aggregate pseudo-columns by adding a prefix to the underlying column's displayname. These are the prefixes for each aggregate function:

min: "Minimum"
max: "Maximum"
cnt: "Number of"
cnt_d: "Number of distinct"
array: "List of"
array_d: "List of distinct"

So for example assume you're writing a pseudo-column for table T1 that another table T2 has a foreign key to. If you want to show  array_d pseudo-column of T2.RID, we're going to say "List of distinct RID" but this is not the same as display heuristics. Since the display heuristics will show a list of T2 row-names.
A simple improvement is using the table's displayname instead of underlying column's displayname. In this case we would say "List of distinct T2".

This has been done in this commit.


Crash after entering the Nether.

There seems to be a bug that causes minecraft to crash when entering the nether. this isn't an immediate crash, occurs after 3-5 seconds the first time, if you attempt to reload the world the crash is instantaneous.
Mod List is Baubles-1.12-1.5.2 and Thaumcraft-1.12.2-6.1.BETA15.
Forge version is forge-1.12.2-<IP_ADDRESS>03
Operating system is Windows.

Can't tell for certain without a crashlog, but very likely a duplicate of #858

I don't think so. I have run several tests and the crash only occurs when you enter the nether, while #858 seems to be about some animations involving nitor (I may be wrong though).

Does the crashlog say something about this?
java.lang.UnsupportedOperationException 	at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(Unknown Source)
If so it's definitely a dupe of #858 because CopyOnWriteArray doesn't allow remove, which is used this way in the code... ^^

Yep, that line is in there. sorry for not including the crash report earlier, I've only just returned to minecraft after a long break.


Added graphs with information about deliveries

In this pull request, the dashboard now displays graphs that show the cumulative number and size of delivered files over three-month periods.

Replaced by PR Conabio-Monitoreo/sipecam_points/pull/#9


feat: add with syntax to PrintManager

Purpose
Allow the use of the with statement with the PrintManager.
What the code is doing
__enter__ and __exit__ functions are added, as documented in https://docs.python.org/3/reference/compound_stmts.html#the-with-statement.
Usage Example/Visuals
Previously, if we wanted to block print for a block of code, we needed to do something like:
>>> pm = PrintManager()
>>> pm.block_print()
>>> demand = scenario.state.get_demand()
>>> pm.enable_print()

Now, the same commands can be accomplished via a shorter syntax:
>>> with PrintManager():
...     demand = scenario.state.get_demand()

Time estimate
5 minutes.

I think this will be useful as we refactor PostREISE; we don't necessarily need to be printing to the user all the details of what's going on under the hood.


When pressing L to place and name a label, it's not named under Details.

When pressing L to place and name a label, the default label_#### name is shown under Details. Until another label is selected, then the named one again, the (re)name is also shown under Details.

This should be fixed now

Fixed


fix: parse pinned file paths correctly

Use vscode.Uri.file to parse file paths, rather than vscode.Uri.path.
Fixes #1040 .

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

v0.131.1
v0.131.1
GitHub release

Your semantic-release bot :package::rocket:


crash when trying to connect with mongo atlas cluster

Environment

VerneMQ Version: 1.7.1 installed with yum
OS: centos 7
Erlang/OTP version (if building from source):
VerneMQ configuration (vernemq.conf) or the changes from the default
connect to mongo atlas cluster ( I couldn't find a way to connect to the cluster. I connected to the primary node. any way to specific cluster than  a single node : dev-XXXX-shard-00-00-gigz1.mongodb.net which resolves to ip address)
I have read the other bugs about the script dependency from vmq_commons.  I didn't find such file
Cluster size/standalone:
stand alone

Expected behavior
vmq is running
Actual behavior
crash.log
2019-03-17 17:36:49 =CRASH REPORT====
crasher:
initial call: mc_worker:init/1
pid: <0.538.0>
registered_name: []
exception error: {{badmatch,{error,closed}},[{mc_connection_man,recv_all,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,102}]},{mc_connection_man,request_raw,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,87}]},{mc_connection_man,read_one_sync,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,52}]},{mc_worker_api,sync_command,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl"},{line,217}]},{mc_worker_logic,get_version,3,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl"},{line,31}]},{mc_worker,auth_if_credentials,5,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,217}]},{mc_worker,init,1,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,54}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
ancestors: [<0.435.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,<0.414.0>]
message_queue_len: 0
messages: []
links: [<0.435.0>,#Port<0.104>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1764
neighbours:
console.log
2019-03-17 17:36:31.884 [info] <0.204.0>@vmq_metadata:start:27 Try to start vmq_plumtree: ok
2019-03-17 17:36:32.852 [info] <0.327.0>@vmq_reg_trie:handle_info:204 loaded 0 subscriptions into vmq_reg_trie
2019-03-17 17:36:32.857 [info] <0.228.0>@vmq_cluster:init:121 cluster event handler 'vmq_cluster' registered
2019-03-17 17:36:32.924 [error] <0.350.0> Failed to start Ranch listener {{10,136,118,95},44053} in ranch_tcp:listen([{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}]) for reason eaddrnotavail (can't assign requested address)
2019-03-17 17:36:32.926 [error] <0.350.0> CRASH REPORT Process <0.350.0> with 0 neighbours exited with reason: {listen_error,{{10,136,118,95},44053},eaddrnotavail} in ranch_acceptors_sup:listen_error/4 line 56
2019-03-17 17:36:32.926 [error] <0.348.0> Supervisor {<0.348.0>,ranch_listener_sup} had child ranch_acceptors_sup started with ranch_acceptors_sup:start_link({{10,136,118,95},44053}, 10, ranch_tcp, [{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,...}]) at undefined exit with reason {listen_error,{{10,136,118,95},44053},eaddrnotavail} in context start_error
2019-03-17 17:36:32.927 [error] <0.334.0>@vmq_ranch_config:reconfigure_listeners_for_type:214 can't reconfigure vmq listener({10,136,118,95}, 44053) with Options [{max_connections,10000},{nr_of_acceptors,10},{mountpoint,[]}] due to {{shutdown,{failed_to_start_child,ranch_acceptors_sup,{listen_error,{{10,136,118,95},44053},eaddrnotavail}}},{child,undefined,{ranch_listener_sup,{{10,136,118,95},44053}},{ranch_listener_sup,start_link,[{{10,136,118,95},44053},10,ranch_tcp,[{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}],vmq_cluster_com,[]]},permanent,infinity,supervisor,[ranch_listener_sup]}}
2019-03-17 17:36:33.715 [info] <0.419.0>@vmq_diversity_app:start:71 enable auth script for mongodb "/usr/share/vernemq/lua/auth/mongodb.lua"
2019-03-17 17:36:33.853 [error] <0.447.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.447.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.854 [error] <0.451.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.451.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.854 [error] <0.450.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.450.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.855 [error] <0.449.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.449.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
error.log
2019-03-17 17:36:32.924 [error] <0.350.0> Failed to start Ranch listener {{10,136,118,95},44053} in ranch_tcp:listen([{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}]) for reason eaddrnotavail (can't assign requested address)
2019-03-17 17:36:32.926 [error] <0.350.0> CRASH REPORT Process <0.350.0> with 0 neighbours exited with reason: {listen_error,{{10,136,118,95},44053},eaddrnotavail} in ranch_acceptors_sup:listen_error/4 line 56
2019-03-17 17:36:32.926 [error] <0.348.0> Supervisor {<0.348.0>,ranch_listener_sup} had child ranch_acceptors_sup started with ranch_acceptors_sup:start_link({{10,136,118,95},44053}, 10, ranch_tcp, [{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,...}]) at undefined exit with reason {listen_error,{{10,136,118,95},44053},eaddrnotavail} in context start_error
2019-03-17 17:36:32.927 [error] <0.334.0>@vmq_ranch_config:reconfigure_listeners_for_type:214 can't reconfigure vmq listener({10,136,118,95}, 44053) with Options [{max_connections,10000},{nr_of_acceptors,10},{mountpoint,[]}] due to {{shutdown,{failed_to_start_child,ranch_acceptors_sup,{listen_error,{{10,136,118,95},44053},eaddrnotavail}}},{child,undefined,{ranch_listener_sup,{{10,136,118,95},44053}},{ranch_listener_sup,start_link,[{{10,136,118,95},44053},10,ranch_tcp,[{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}],vmq_cluster_com,[]]},permanent,infinity,supervisor,[ranch_listener_sup]}}
2019-03-17 17:36:33.853 [error] <0.447.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.447.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.854 [error] <0.451.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.451.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.854 [error] <0.450.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.450.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.855 [error] <0.449.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.449.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-17 17:36:33.856 [error] <0.448.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.448.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
erlang.log
=CRASH REPORT==== 17-Mar-2019::17:36:49.826142 ===
crasher:
initial call: mc_worker:init/1
pid: <0.537.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.434.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.414.0>]
message_queue_len: 0
messages: []
links: [<0.434.0>,#Port<0.105>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1764
neighbours:
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
=SUPERVISOR REPORT==== 17-Mar-2019::17:36:50.653158 ===
supervisor: {local,gr_counter_sup}
errorContext: child_terminated
reason: killed
offender: [{pid,<0.122.0>},
{id,gr_lager_default_tracer_counters},
{mfargs,{gr_counter,start_link,
[gr_lager_default_tracer_counters]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
=SUPERVISOR REPORT==== 17-Mar-2019::17:36:50.653484 ===
supervisor: {local,gr_param_sup}
errorContext: child_terminated
reason: killed
offender: [{pid,<0.121.0>},
{id,gr_lager_default_tracer_params},
{mfargs,{gr_param,start_link,[gr_lager_default_tracer_params]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]

Please include minimal steps to reproduce the issue, if possible.
1.setup vmq 1.7.1 on centos as per instructions
2.configure mongo access to connect to the primary node of an atlas cluster

watch it crash and fill the logs

@milamber-ls thanks for reporting!
@dergraf, @larshesel does the mc_connection_man error ring a bell?
I agree on the remark regarding connections to a MongoDB cluster. It's a matter of priorities and resources here, anyone feel free to research & implement this.

Hi, not sure about everything here, but it seems VerneMQ is configured to start listeners on an IP which is not available on the node where VerneMQ is running: ranch_tcp:listen([{ip,{10,136,118,95}},{port,44053},{nodelay,true},{linger,{true,0}},{send_timeout,30000},{send_timeout_close,true}]) for reason eaddrnotavail (can't assign requested address). Perhaps if you fix this issue the others go away or at least we'd not have to think about if they play a role here.

this is the actions that i have performed and the corresponding results:

I turned off mongo auth and turn on file auth and file acl. vmq came back up, and responded to messages. Logs reported the port error and stopped growing. vmq seems operational
it seems the the eth1 interface related to the internal network was down (10.x.x.x). I brought it back up and added 44053 to firewall. This is the report from netstat
tcp        0      0 <IP_ADDRESS>:44053     <IP_ADDRESS>:*               LISTEN      997        73227      748/beam.smp
I turned on mongo auth and turn off file auth and file acl. vmq came back up, and responding to messages. It seems that it was able to communicate with mongo although i
got  [warning] <0.563.0>@vmq_mqtt_fsm:check_user:558 can't authenticate client {[],<<"XXXXXX">>} from Y.Y.Y.Y:51099 due to invalid_credentials
I used https://www.browserling.com/tools/bcrypt with 10 passes create the password that looks like $2a$10$zaNzcfc7VLzvUaGzXXXXXXXXXXXXXXXX. can you point me to a correct way to produce this hashes?

Logs reported errors and continue growing so i have stopped vmq. vmq is not operational
This is the contents of the logs
console.log
2019-03-19 13:25:37.224 [info] <0.206.0>@vmq_metadata:start:27 Try to start vmq_plumtree: ok
2019-03-19 13:25:37.684 [info] <0.330.0>@vmq_reg_trie:handle_info:204 loaded 1 subscriptions into vmq_reg_trie
2019-03-19 13:25:37.687 [info] <0.233.0>@vmq_cluster:init:121 cluster event handler 'vmq_cluster' registered
2019-03-19 13:25:39.114 [info] <0.424.0>@vmq_diversity_app:start:71 enable auth script for mongodb "/usr/share/vernemq/lua/auth/mongodb.lua"
2019-03-19 13:25:39.608 [error] <0.454.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.454.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 13:25:39.609 [error] <0.452.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.452.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 13:25:39.610 [error] <0.450.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.450.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 13:25:39.611 [error] <0.453.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.453.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 13:25:39.612 [error] <0.451.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.451.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 13:25:40.730 [error] <0.477.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.477.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
crash.log
2019-03-19 13:48:46 =CRASH REPORT====
crasher:
initial call: mc_worker:init/1
pid: <0.8071.0>
registered_name: []
exception error: {{badmatch,{error,closed}},[{mc_connection_man,recv_all,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,102}]},{mc_connection_man,request_raw,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,87}]},{mc_connection_man,read_one_sync,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,52}]},{mc_worker_api,sync_command,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl"},{line,217}]},{mc_worker_logic,get_version,3,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl"},{line,31}]},{mc_worker,auth_if_credentials,5,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,217}]},{mc_worker,init,1,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,54}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
ancestors: [<0.435.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.435.0>,#Port<0.7471>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1525
neighbours:
2019-03-19 13:48:46 =CRASH REPORT====
crasher:
initial call: mc_worker:init/1
pid: <0.8072.0>
registered_name: []
exception error: {{badmatch,{error,closed}},[{mc_connection_man,recv_all,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,102}]},{mc_connection_man,request_raw,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,87}]},{mc_connection_man,read_one_sync,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,52}]},{mc_worker_api,sync_command,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl"},{line,217}]},{mc_worker_logic,get_version,3,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl"},{line,31}]},{mc_worker,auth_if_credentials,5,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,217}]},{mc_worker,init,1,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,54}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
ancestors: [<0.7823.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.7823.0>,#Port<0.7472>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1529
neighbours:
2019-03-19 13:48:46 =CRASH REPORT====
crasher:
initial call: mc_worker:init/1
pid: <0.8073.0>
registered_name: []
exception error: {{badmatch,{error,closed}},[{mc_connection_man,recv_all,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,102}]},{mc_connection_man,request_raw,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,87}]},{mc_connection_man,read_one_sync,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl"},{line,52}]},{mc_worker_api,sync_command,4,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl"},{line,217}]},{mc_worker_logic,get_version,3,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl"},{line,31}]},{mc_worker,auth_if_credentials,5,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,217}]},{mc_worker,init,1,[{file,"/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl"},{line,54}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
ancestors: [<0.433.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.433.0>,#Port<0.7473>]
dictionary: []
trap_exit: false
status: running
=====

===== LOGGING STARTED Tue Mar 19 14:10:16 EDT 2019
=CRASH REPORT==== 19-Mar-2019::14:10:16.483058 ===
crasher:
initial call: mc_worker:init/1
pid: <0.15053.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.434.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.434.0>,#Port<0.14308>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1525
neighbours:
=CRASH REPORT==== 19-Mar-2019::14:10:16.554958 ===
crasher:
initial call: mc_worker:init/1
pid: <0.15054.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.14550.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.14550.0>,#Port<0.14309>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1525
neighbours:
=CRASH REPORT==== 19-Mar-2019::14:10:16.632689 ===
crasher:
initial call: mc_worker:init/1
pid: <0.15055.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.436.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.436.0>,#Port<0.14310>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1529
neighbours:
=CRASH REPORT==== 19-Mar-2019::14:10:28.162491 ===
crasher:
initial call: mc_worker:init/1
pid: <0.15117.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.435.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.435.0>,#Port<0.14370>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1529
neighbours:
=CRASH REPORT==== 19-Mar-2019::14:10:28.312055 ===
crasher:
initial call: mc_worker:init/1
pid: <0.15118.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.433.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.433.0>,#Port<0.14371>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1529
neighbours:
=CRASH REPORT==== 19-Mar-2019::14:10:28.726223 ===
crasher:
initial call: mc_worker:init/1
pid: <0.15119.0>
registered_name: []
exception error: no match of right hand side value {error,closed}
in function  mc_connection_man:recv_all/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 102)
in call from mc_connection_man:request_raw/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 87)
in call from mc_connection_man:read_one_sync/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_connection_man.erl, line 52)
in call from mc_worker_api:sync_command/4 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/api/mc_worker_api.erl, line 217)
in call from mc_worker_logic:get_version/3 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker_logic.erl, line 31)
in call from mc_worker:auth_if_credentials/5 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 217)
in call from mc_worker:init/1 (/opt/vernemq/distdir/BUILD/1.7.1/_build/default/lib/mongodb/src/connection/mc_worker.erl, line 54)
ancestors: [<0.434.0>,<0.432.0>,auth_mongodb,vmq_diversity_sup,
<0.419.0>]
message_queue_len: 0
messages: []
links: [<0.434.0>,#Port<0.14372>]
dictionary: []
trap_exit: false
status: running
heap_size: 2586
stack_size: 27
reductions: 1525
neighbours:
heap_size: 2586
stack_size: 27
reductions: 1529

neighbours:
error.log
2019-03-19 14:11:04.533 [error] <0.15313.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15313.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 14:11:04.627 [error] <0.15314.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15314.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 14:11:04.914 [error] <0.15315.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15315.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 14:11:05.083 [error] <0.15316.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15316.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 14:11:05.449 [error] <0.15317.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15317.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 14:11:05.557 [error] <0.15318.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15318.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102
2019-03-19 14:11:05.663 [error] <0.15322.0>@mc_connection_man:recv_all:102 CRASH REPORT Process <0.15322.0> with 0 neighbours crashed with reason: no match of right hand value {error,closed} in mc_connection_man:recv_all/4 line 102

Hi, sorry for not getting back to this earlier. Mongo Atlas is the managed/hosted solution from Mongo, right? Perhaps you can see on the logs on their side why the connection is closed when the client is connecting? I haven't seen this issue on self-hosted mongodb so far. How is the Atlas cluster configured? And how was mongodb configured in  the vernemq.conf file?

Hello, does VerneMQ support TLS for connecting to Mongo?


[Question] What happens when v1.12 LTS ends?

Based on a question from the slack community, this issue is to try and help clarify what happens when the current cert-manager LTS ends.
We discussed on this morning's cert-manager standup that an Issue would be useful so we can document whatever route is taken next.
This is not a wish list issue, but if you have relevant insights please share.
If you still use LTS (v1.12.13) as opposed to the latest an greatest v1.16 we would be keen to know why.

I've opened an internal ticket to know a little bit more: VC-37137.


[INVALID PR] Integration of NeMo models into LM Evaluation Harness library

This PR adds support for NeMo models to be run locally from Eleuther's LM Evaluation Harness Library.
The main contribution is the lm_eval/models/nemo.py script, which leverages NeMo framework to run .nemo model checkpoints. It also supports multi-gpu and multi-node tensor, pipeline and data parallelism. An example to run a NeMo model is:
lm_eval --model nemo \
    --model_args path=<path_to_nemo_model> \
    --tasks hellaswag

We have added documentation about installing NeMo, leveraging a NVIDIA container and multi-gpu/node evaluation in the README.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.sergiop seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing this PR since I set up the commit from a non-GitHub account, and you need a GitHub account to be able to sign the CLA.


Require gold on linux and freebsd by default.

This commit just changes the default to require gold. The user can still override from the command line if they choose to.
The reason why I am making this change is to match Swift's behavior here. There
really isn't any good reason to have separate linkers compiling separate parts
of the same build.
rdar://39456714
(cherry picked from commit 931da81e3fb4f34bea71d0bf37f8bcf3fc473283)

@swift-ci test

@swift-ci please test and merge


different score results from different no_of_poses parameter setting

I tested with different "no_of_poses" parameter values, then vina scores turn different values quite a lot (e.g. ~2kcal/mol)
Are there any other randomness or heuristic things during docking besides the seed. I fixed the all other parameters but "no_of_poses"

Are scores different for the first pose, or only from the second and subsequent poses?

I have done two individual dockings with the same seed but different value(1, 20) of the "no_of_poses" parameter.
The first pose 's scores from two dockings were compared: one score from the "no_of_poses" set to 1 and another score from the default(20) with the same input and the same seed.

Tried with a system and can't reproduce. Got very similar first poses and very similar scores (-7.090 vs -7.063). Could you share your files and commands/scripts to reproduce?

In my tests v.energies()[0][0] and v.score()[0] match exactly. This is the value that is printed to "REMARK VINA RESULT" in output PDBQTs both in v1.1.2 and v1.2.*. Not sure why your average scores (and SDs) differ.
Docking runs local search internally, both during the docking and then again at the end of docking. Thus, v.optimize() should have no noticeable effect, but there is another variable at play, which is whether or not the precalculated grid maps are used to calculate interaction energies involving receptor atoms. The alternative to that is to calculate interactions directly between pairs of atoms, which is slower because receptors typically have many atoms. The local search at the end of docking uses direct interactions, while v.optimize() uses grid maps. We should eventually use direct interactions in v.optimize() (as requested in #67 ) but didn't get to it yet. That is why v.optimize() returns systematically worse (higher) energies.

Which score should I use for the score assessment ?

Use v.energies()[0][0]. No need to call v.score() as it is called inside v.dock() to populate the energies that are returned by v.energies().


provide a typefaceStyle property on Text nodes for Android

I'm not actually sure if I want this in the common library


Modified the Endpoints in Crouton_Client

-Added filter to the get method to filter out users by email, username or any other field.
-Filters will be added if no item_id found
-Modified all the endpoints such as the get, put, post and delete for asynchronous implementation
-Modified all the endpoints  synchronous implementation such as the api_get_call, api_post_call, api_put_cal and api_delete_call

addresses issue #5


non-deterministic order when using NestedModel

Hi there, me again :)
Looks like we have some issue retaining order when using Meta.ordered = True with nested models.
Here's some code to illustrate what I mean:
test.py
from marshmallow_objects import *

test_data = """
{"subfields": {
    "test": {
        "field_one": "one",
        "field_two": "two"
        }
    }
}
"""

class Base(Model):
    class Meta:
        ordered = True

class SubModel(Base):
    field_one = fields.Str()
    field_two = fields.Str()

class TestModel(Base):
    subfields = fields.Dict(keys=fields.Str(), values=NestedModel(SubModel))

print(
    TestModel.load_json(test_data)
)

 $ python3 ./test.py
OrderedDict([('subfields', {'test': {'field_two': 'two', 'field_one': 'one'}})])
 $ python3 ./test.py
OrderedDict([('subfields', {'test': {'field_two': 'two', 'field_one': 'one'}})])
 $ python3 ./test.py
OrderedDict([('subfields', {'test': {'field_one': 'one', 'field_two': 'two'}})])

Note the random field ordering.
I'm really not sure what is causing this, but it seems to be limited to NestedModel being used as the values of a fields.Dict field. I have a hunch that this is caused by the fact that the NestedModel field relies on deserializing into models via the model's __init__ method, which just passes in the incoming dict as kwargs (and therefore casting it from an OrderedDict to a regular one) but I am not certain.
Any help would be appreciated!! I'll update this thread if I find anything else.

Hi, thank you, I need a time to figure out how to fix it

I believe I've narrowed it down to something happening in the schema property of the Nested field type (in Marshmallow upstream, not your library, though it maybe a combination of things).
https://github.com/marshmallow-code/marshmallow/blob/3.0.0b20/src/marshmallow/fields.py#L432
Namely, this line:
self.__schema.ordered = getattr(self.parent, 'ordered', False)

I think that self.parent never has an 'ordered' attribute when using marshmallow-objects.
However, it also appears that in the latest marshmallow release that line has been removed! I can confirm that I can no longer repro using the latest Marshmallow (3.0.0rc6) and master of marshmallow-objects. Do you mind cutting a new release to pypi with the compatibility fixes for rc6? Thanks!

Here's where it was removed https://github.com/marshmallow-code/marshmallow/commit/b66dafea5ca1ad78d04711df5ac2f75dfc94d6dc

Hi

Do you mind cutting a new release to pypi with the compatibility fixes for rc6? Thanks!
I did it yesterday, but it wasn't uploaded to pypi :(

figured out, the regex for branches was changed by mistake

Done. Here it is: https://pypi.org/project/marshmallow-objects/1.0.20/

thanks so much!


Matrix fields?

Is there a way to make this work when the footnote is added a Matrix field? I'm not sure what the syntax would be for the line that converts footnotes into numbers without repeating it for every Matrix block:
{{ entry.handle_of_redactorfield | footnotes }}

Sorry for the late response. I am not quite sure what you mean exactly. Could you explain a bit more, please?
(I woke up at 4 am this morning for no reason, as of writing this it's 6 am and I doubt being able to have a lucid mind right now. 😅)

The docs say:
{# when accessing Redactor fields in your Twig template use the new filter #}
{{ entry.handle_of_redactorfield | footnotes }}

But that assumes that the footnotes have been entered into a standard Redactor field. My site has the redactor field inside a Matrix block, so entry.handle_of_redactorfield doesn't work.
I'm sure there's a way to make it work with Matrix fields but I don't know what it would be.
In short, how would you use this plugin when your field that holds the footnotes is in a Matrix block?

Ah, thanks. Without trying I think it should work to simply iterate your Matrix blocks and add the footnotes filter to each block's Redactor field.
{# by accessing the matrix field a query object is retrieved #}
{# therefore call `all()` to get all blocks #}
{% for block in entry.handle_of_matrixfield.all() %}
  {# now simply access the redactor field as usual #}
  {{ block.handle_of_redactorfield | footnotes }}
{% endfor %}

That should do it. As said, I didn't try it, but I am slightly optimistic about it in general. 😁 Let me know if it worked.
PS: Pardon me any misspelled code or something, I am currently working a lot on a Symfony based project, thus I am not doing much Craft right now, unfortunately.

I did try something like that, but it results in the footnotes being repeated multiple times throughout the page because it's running that footnotes filter again every time it encounters a Matrix block.
I appreciate the help with it anyway. The inability to include hyperlinks in the footnotes themselves is a dealbreaker for my client, so I don't think this plugin is right for me.
Thank you for contributing to the Craft ecosystem though!

Okay, sorry that I can't help apparently. Feel free to fork it and add new features.
Also try that other footnote plugin from https://github.com/carlcs/craft-footnote:
https://plugins.craftcms.com/footnote
That plugin has a different approach on adding footnotes (it also supports links in footnotes). Maybe that helps.


Develop marketplace as a mobile application

As a user I want to use the marketplace software also as an app so it works fine on mobile phone / pads and so one.
This task needs to clarify what has to be done to use marketplace sw as a mobile app. In the clarify process we need to know which program language we will use, how we organice the project in kanban, branches. When we got the basics done, we will describe more tickets in detail about the next steps.
DoR:

[ ] A software developer is selected and confirmed to handle this ticket

Acceptance Criteria:

[ ] AC1: We have the knowhow, how to handle it on the kanban board
[ ] AC2: We have the knowhow, how we can develop the software for mobile app
[ ] AC3: The documentaion about roadmap, tools and new tickets is available

DoD:

[ ] We got the knowhow how to handle it on the kanbanboard
[ ] We got the knowhow how to develop the software for mobile app
[ ] With a demonstration about the roadmap, all members of the team knows what is to do next
[ ] The next steps are cleary specified

Cristian has some ideas about to handle it.


Adjust logging for config.url

There are many instances where config.url is being logged.  This url will often include login credentials in the form:
mongodb://my-user:my-password@mongos.example.com:27075/my_database?ssl=true

Login credentials should not be surfaced in the logs.  This needs to be updated immediately and therefore I propose that all logging of config.url be removed entirely. Perhaps in the future a more sophisticated logging method that redacts the credentials can be developed.
See: https://github.com/digitalbazaar/bedrock-mongodb/blob/master/lib/index.js#L101

Work on this should be based on the branch associated with this PR: https://github.com/digitalbazaar/bedrock-mongodb/pull/57

+1.


test: add basic auth server tests

builds off of #2272
Closes #2262
adds a few sanity rpc tests for the engine api

Codecov Report

Merging #2278 (690de04) into main (d1162db) will decrease coverage by 52.97%.
The diff coverage is 34.05%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2278       +/-   ##
===========================================
- Coverage   72.08%   19.11%   -52.97%
===========================================
  Files         472      472
  Lines       56777    57057      +280
===========================================
- Hits        40928    10907    -30021
- Misses      15849    46150    +30301

Flag
Coverage Δ

integration-tests
19.11% <34.05%> (+0.73%)
:arrow_up:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

bin/reth/src/args/rpc_server_args.rs
0.00% <0.00%> (-53.20%)
:arrow_down:

bin/reth/src/node/mod.rs
0.00% <0.00%> (-11.87%)
:arrow_down:

crates/rpc/rpc-builder/src/lib.rs
44.72% <0.00%> (-20.67%)
:arrow_down:

crates/rpc/rpc-engine-api/src/lib.rs
0.00% <ø> (-100.00%)
:arrow_down:

crates/rpc/rpc/src/layers/jwt_validator.rs
28.81% <ø> (-71.19%)
:arrow_down:

crates/rpc/rpc/src/lib.rs
0.00% <ø> (-100.00%)
:arrow_down:

crates/rpc/rpc-builder/src/auth.rs
46.95% <68.75%> (+46.95%)
:arrow_up:

crates/rpc/rpc/src/layers/jwt_secret.rs
16.59% <100.00%> (-80.27%)
:arrow_down:

... and 319 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[BUG] Exporting Data using FromQuery with a larger dataset adds a random column

Prerequisites

[ X] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[X ] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[X ] Checked that your issue isn't already filed.
[ X] Checked if no PR was submitted that fixes this problem.
[X ] Filled in the entire issue template

Versions
PHP version: PHP 7.2.19 (cli) (built: May 29 2019 13:58:59) ( ZTS MSVC15 (Visual C++ 2017) x64)
Laravel version: Laravel Framework 5.8.28
Package version: 3.1.14
Description
Exporting (using a FromQuery Export object) a larger dataset (+-17 000 records) causes the CSV file to have an additional column at the end of it, starting with a value 0f 10001 which increments all the way to the end of the file (the records before that all contain a null value for the phantom column). The weird thing is that my underlying data does not contain that data, it's as if the export process adds this extra column.
I also use WithHeadings, which seems to add this phantom column header as "" (an empty header)
Herewith a sample of the output file header:
"occupation","sector","guild","salary_day",""
Steps to Reproduce
Try to export a large dataset of 17000 rows or more.
Expected behavior:
All rows are exported to the CSV without a random column been added to the end of the file
Actual behavior:
A random column gets added to the CSV with mostly null values for the first 10000 records, then it fills in a value of 10001 which it increments for each column thereafter.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Anyone else experiencing this issue?

@SuperlativeEntity  Does this issue still happen on the latest version? Is this a queued export?
About your side note, 500 records might mean there's only 1 chunk being inserted.

I remember resolving the issue with some hack, but I haven't tried the latest version as yet.

@SuperlativeEntity could you share the hack with me? Perhaps it helps me figure out what's happening.


Tabs: make conditional rendering of panel optional

This had  some unintended consequences for people relying on keeping the state (such as scroll position) of the tab-panels, so we should instead restore it as an optional prop  conditionalRender or something

conditionalRender will be an optional prop on <Tabs.Panels conditionalRender> so the default will be display: none, restoring the original behaviour


Beta Test: Phone element on HTML and CSS Waypoints crossing over the footer.

When scrolling down the phone is in a fixed position and crosses over the footer.

@silentfox91 Thanks!

Can't reproduce. Are you still seeing this @silentfox91 ?

I'm still see it, I'm using Firefox for Ubuntu canonical 1.0 and I'm seeing it on Chrome as well.
I have checked another computer and the issue isn't there. The two major differences is age and screen size (mine is a few months old & 13" while the other is a good five years old and 15")

potential fix for this issue https://github.com/FreeCodeCamp/freecodecamp/pull/1152


ATMOS audio tool

Hi! First of all thanks a lot for your work on this, it is a very nice tool. I am wondering if it would be possible to have something similar for atmos audio, so we can extract the atmos information from a truehd audio and then add it to a eac3 audio as a JOC.

Why do you think Atmos is relevant to this project? It isn't.


Added Mk2 wrist folder

Contains:

Simmechanics model
Simulink control system configured for decoupler embedded code generation
Mathematics of spherical wrist documentation

This is a PR relevant to @marcoaccame @sgiraz @mfussi66.
/remind in 7 days to clean up our internal repo of physical models

I'm closing and reastarting since the workflow is messed up because of missing lfs management.

Follow-up in #26


Check for illegal characters before running codegen

This PR checks the type name for illegal characters before generating code.

Thanks! checkIllegalName seems not to be used anywhere though :P
Also, could you move the function to Util.hs or perhaps Formatting.hs?
FWIW, if something like this has a tendency to complicate the core code in TH.hs, it could also make sense to do it as part of the formatting step, e.g. the formatTSDeclaration function. At the formatting stage, the data types and logic are simpler and the TS names for things are more apparent. Might need an API change to allow formatTSDeclaration to error out in that case, although a pure exception doesn't seem out of the question--maybe a new function formatTSDeclarationEither. This all depends on whether it can be done cleanly in TH.hs of course.

Lol oops!
I put the function in the Util module as requested, and refactored it so it could be tested a bit more easily.
🤔
Right now, there's no option to customize the Haskell type name. So its definitely going to be a problem if we have any illegal characters there, and we can easily report the error as soon as we have the Name of the type we're deriving for.
I've modified the PR to also check datatype constructors.

And at this point I recognize that I've got a problem - the formatting options allow you to modify the interface and type names, which happens well after TemplateHaskell is done. That's a problem! We can't actually check at compile-time that the generated TS will be "correct" because we might change the typescript that actually gets written - getTypeScriptDeclarations for a given type isn't guaranteed to return the same typescript code that is actually printed by the app.
With this patch, anyone that is currently doing filter ('\'' ==) as a name modifier would get a compile-time error that doesn't really apply to them.
Oof.
I'd propose to modify the FormattingOptions and move those name formatters into the ExtraTypeScriptOptions. That gives you better consistency over the generated names, as well as allowing you to know at compile-time if the names are invalid.

Oh right, that's unfortunate. I don't love the idea of a breaking change to the name formatters API, although in hindsight it seems like the ExtraTypeScriptOptions might have been a better place for them. FWIW here's the PR that added the formatters: https://github.com/codedownio/aeson-typescript/pull/5.
As an alternative hack, what about just replacing all invalid characters with underscores at formatting time? :)

As an alternative hack, what about just replacing all invalid characters with underscores at formatting time? :)

I think our linter complains about trailing _ 😅
A default name formatter that throws an error on an invalid character + tells you how to fix it may be the least invasive solution - we can change the formatter to be something like:
defaultNameFormatter str = do
  case NonEmpty.nonEmpty str of
    Nothing -> error "Name cannot be empty"
    Just nameChars -> case checkIllegalNameChars nameChars of
      Just badChars -> error $ concat ["The name ", str, " contains illegal characters: ", toList badChars, "\nConsider setting a default name formatter that replaces these characters." ]
      Nothing -> str

Obviously would want to trace the "how did i get here" so users can backtrack to exactly what failed + which name formatter needs to be invoked.
I do think the best choice is moving the formatting options to the TH side. Then you'd get a compile-time error, with a note to modify the name transformation field or the type itself. Given two steps, it wouldn't be a hard migration for end users:

Next major version: Release the new name transformation fields on ExtraTypeScriptOptions and deprecate the formatter fields w/ good migration messages
Major version after that: Delete the formatters.

Setting the default name formatter to error out as you describe sounds like a good first step. Maybe that would be sufficient to close #34 ?
If you get an informative error message at the formatting stage, would you still feel strongly about moving those options to the TH side?

Yeah, I generally want problems reported ASAP.
At least for our codebase, the derivation happens well before code generation, which is a totally separate step. I wouldn't want to introduce a runtime dependency on tsc for our test suite just to ensure that our generated code is well-formed.

I wouldn't want to introduce a runtime dependency on tsc

Huh? There's no tsc involved in the idea of erroring out at the formatting stage by using checkIllegalNameChars.
Just thinking through the implications of moving the formatting options -- it could harm at least one workflow I can imagine. What if you have lots of primed types like Foo' and Bar', and you're accustomed to bulk-formatting them by calling formatTSDeclarations' with an interfaceNameModifier that does T.replace "'" "Prime"? If we move the options, then such a user would have to individually apply formatting options to all their types at the deriveTypeScript call. (Assuming most people  derive instances individually and format in bulk, like I do.) I suppose if we go through the deprecation process then people will be free to complain at that point.

Yeah, that would require a migration of code - but it shouldn't have to be a hard one. At work we consolidate our default options, so we can easily control what that default is by altering a single value in a single module. Factoring out the duplication in argument passing wouldn't be a huge problem.

All right, what do you think of the following?

In this PR, do the erroring defaultNameFormatter
Make a subsequent PR moving the formatting functions to the ExtraTypeScriptOptions, and maybe ask for comments from @Reisen

Sounds good! I'll make the relevant changes.

OK, should be ready for review :)

Sorry, this fell off my radar -- merging now!

Automatic merge failed, manually rebased and merged in ba5d998


Terminal will not open in the main panel

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.64.2
OS Version: Linux

Steps to Reproduce:

ctrl ^ ~
terminal opens in new 'side panel' instead of the main panel
terminal can not be dragged or otherwise moved to the main panel on the left
nor are there any terminal settings to enable this, what used to be common functionality

You could try the View: Reset View Locations setting.
You are not able to drag the little icon at the top left of the Side Panel representing the terminal?  It works for me.

No but after hours of research, I managed to discover amongst the commands lists "move views from side panel to panel" which seems to have restored some kind of normality, so you can close this issue if you like, thanks.
I still consider this extremely user unfriendly though, as there does not seem to be any way of doing it easily and directly.

P.S. I have tried dragging just about everything at the top of the Side Panel with no luck, before I created this issue. Maybe I just missed that particular little icon or maybe it does not work unless the main panel is already opened, I do not know.


Cannot install

Hi! Should I create netlify.toml file before this step? And what should I change here? Should I change your vault link to mine in toml?

Tried like this:

but getting error when deploy

Please note that you do not need to make changes to the build.command field in netlify.toml. You can compare your file with that from the example repo. Please let me know if there are further issues :)

Thank you! Followed this tip, however still having the following troble:

It might be smth with config file, however I didnt create it at all on my side.

You also need to set your SITE_URL in netlify.toml to your website's address.

Added and this worked!

Great! I will close the issue then, have fun with your website!


Drawnode issue on Android 4.2.x

adxe version: 1
devices test on: Asus ME173X (Android 4.2.2)
developing environments

NDK version: r19c
Xcode version: 12.4
VS/msvctools version: Visual Studio 2019(16.11)/14.29.30133
cmake version: 3.23.0-rc1
Steps to Reproduce:

Copy paste this code in HelloWorld
Test under iOS or Mac
See the difference on Android 4.2.x (nothing is drawn)

// testDrawNode
void HelloWorld::testDrawNode()
{

    //
    log(" - works on MacOs 11+ but not on Android 4.2.2");
    log(" - should trace some drawings in the scene");

    //
    auto size = Director::getInstance()->getVisibleSize();
    auto origin = Director::getInstance()->getVisibleOrigin();
    float scaleFactor = Director::getInstance()->getContentScaleFactor();
    log(" - size: %.0fx%.0fpx", size.width, size.height);
    log(" - scaleFactor: %.2f", scaleFactor);

    //
    float pad = 40.0f;

    auto pointBL = Vec2(pad, pad);
    auto pointTR = Vec2(size.width-pad, size.height-pad);

    auto pointA = Vec2(pad, size.height-2*pad);
    auto pointB = Vec2(2*pad, size.height-2*pad);
    auto pointC = Vec2(2*pad, size.height-pad);
    auto pointD = Vec2(pad, size.height-pad);

    auto draw = DrawNode::create();
    draw->setContentSize(size);
    draw->setPosition(origin);

    // draw a rectangle
    draw->drawSolidRect(pointBL, pointTR, Color4F(1.0f,1.0f,1.0f,0.20f));

    // draw a rectangle
    draw->drawSolidRect(pointA, pointC, Color4F(1.0f,1.0f,1.0f,1.0f));

    // drawQuadBezier
    draw->drawQuadBezier(pointA, pointB, pointC, 10, Color4F(1.0f,1.0f,1.0f,1.0f));

    // draw polygons
    Vec2 points[] = { pointA, pointB, pointC, pointD };
    draw->drawPolygon(points, sizeof(points)/sizeof(points[0]), Color4F(1.0f,0.3f,0.0f,1.0f), 4, Color4F(0.0f,1.0f,1.0f,0.3f));

    // draw segment
    draw->drawSegment(pointA, pointC, 10, Color4F(0.0f, 1.0f, 0.0f, 1.0f));

    addChild(draw, 50);
}

I have no android 4.2.2 device， does the virtual device also have this issue?

No, the emulator is working fine under Jelly Bean 4.2 API 17. Note that is also working on Cocos v3.17.2 on physical devices.

Does other android physical devices with different Android version have the issue, It is difficult to diag the problem reason, because I have no Android 4.2.2 physical device. And does there have any avaiable logcat for this issue?

I think everything under SDK 17 - include - is having the issue. Min SDK is already 17 in adxe, if I test under SDK 15, I also have the issue. Nothing relevant in logcat. Didn't tested SDK 18. SDK 19 is fine.

Note: under cocos v3 last version, I'm able to have Min SDK 14 without any known issue.

I tried out of pure free time on my old galaxy note 3 (which I didn't update and it's still on 4.2.2) And yes it has the issue surprisingly! It also happens with the godot engine when drawing lines except that they stutter (some frames they show and sometimes they don't, sometimes they show artifacts) is it an OpenGL ES issue?

It's very rare that anyone still uses these devices cuz they're OLD AS TIME

Yes, the min sdk have maybe to be raised up.
Anyway, I've notified this DrawNode  issue, I will notify some others.

I will notify one here as it also concern the same versions of Android:
ScrollView issue on Android SDK 17-

adxe version: 1
devices test on: Asus ME173X (Android 4.2.2)
developing environments
NDK version: r19c
Xcode version: 12.4
VS/msvctools version: Visual Studio 2019(16.11)/14.29.30133
cmake version: 3.23.0-rc1

Steps to Reproduce:

Copy paste this code in HelloWorld
Test under iOS or Mac or Android > SDK 19
See the difference on Android 4.2.x (nothing is drawn)

    //
    float pad = 20.0f;
    //
    auto origin = Director::getInstance()->getVisibleOrigin();
    //
    auto size = Director::getInstance()->getVisibleSize();
    auto sizeScroll = Size(size.width*0.33f, size.height-2*pad);
    auto sizeVeryHigh = Size(size.width*0.33f, size.height*4.0f);

    // Create the scrollview by vertical
    //ui::ScrollView* scrollView = ui::ScrollView::create();
    ScrollView* scrollView = ScrollView::create();
    scrollView->setContentSize(sizeScroll);
    scrollView->setInnerContainerSize(sizeVeryHigh);
    scrollView->setScrollBarWidth(4);
    scrollView->setScrollBarPositionFromCorner(Vec2(2, 2));
    scrollView->setScrollBarColor(Color3B::WHITE);
    scrollView->setGlobalZOrder(200);
    addChild(scrollView, 10);

    //
    scrollView->setPosition(Vec2(size.width*0.66f - pad, pad) + origin);

    //
    LayerColor *layerColor = LayerColor::create(Color4B(155, 255, 255, 255));
    layerColor->setContentSize(sizeVeryHigh);
    layerColor->setPosition(sizeVeryHigh/2.0f);
    scrollView->addChild(layerColor, 10);

    for (int i=0; i<12; i++) {
        Sprite* sprite = Sprite::create("HelloWorld.png");
        sprite->setPosition(Vec2(sprite->getContentSize().width/2, sizeVeryHigh.height - (i+0.7f) * sprite->getContentSize().height));
        scrollView->addChild(sprite, 2);
    }

Yes, the min sdk have maybe to be raised up. Anyway, I've notified this DrawNode issue, I will notify some others.

@appakabar
Have you the same behavior using cocos2d-x 4.0?

@aismann

Have you the same behavior using cocos2d-x 4.0?

Yes.

Can you see any other stuff if you put it on the center of the screen?

If you mean a DrawNode, no those are not drawn at all. For the ScrollView issue I think my test in already in the center of the screen.

So nothing is drawing?
Do you think this is really a axys/cocos2dx 4.0 issue?
I think your device is too old.

So nothing is drawing?
-> for the Drawnode, yes nothing is drawn. Pretty sure that the other issue (Scrollview) is related.
Do you think this is really a axys/cocos2dx 4.0 issue?
-> yes, 100% sure. Related to the changes on the renderer engine I think.
I think your device is too old.
-> yes, those are (I've 2 or 3 like that), it's something like 1 or 2% of Android users I think. So not a big issue at all. But If the issue is not fixed, the min SDK have to be raised for a better engine quality.
Bigger issue I have with axys/cocos2dx 4.0 is the fact that third libs are not precompiled for Mac OS Silicon/Mx chip series...  Do you think I should open a ticket about this or some guy is already working on it? (I've already work a bit on it but I'm not good a that).. Thank you!

Bigger issue I have with axys/cocos2dx 4.0 is the fact that third libs are not precompiled for Mac OS Silicon/Mx chip series... Do you think I should open a ticket about this or some guy is already working on it?

-> Thats the sense of an issue.
Write one and hope it will answered or better send the fix with a PR bei yourself.

The Apple M1 already supported, see also: https://github.com/axys1/axys/issues/803

Do you think this is really a axys/cocos2dx 4.0 issue? -> yes, 100% sure. Related to the changes on the renderer engine I
think.
@appakabar
Use cocos2dx 3.1x for this device plz.

Can we close this issue?

Use cocos2dx 3.1x for this device plz.
ok noted

Can we close this issue?
Yes for sure. Thank you for all.

@halx99
plz close


Set up E2E tests

Set up E2E tests to ensure maven plugin could work with the latest function host

Codecov Report

Merging #425 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #425   +/-   ##
========================================
  Coverage    53.68%   53.68%
========================================
  Files           67       67
  Lines         1885     1885
  Branches       212      212
========================================
  Hits          1012     1012
  Misses         805      805
  Partials        68       68

Continue to review full report at Codecov.

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

@pragnagopa Comments resolved, besides, i've sent a invitations to you to join the group of appveyor, and then you could trigger this test here (For now it will build the e2etest branch, which will be changed to develop after merge)


Purpose of NavHostActivity

Hi, would you help me understanding the purpose of the following line? I am quite new to NAC and I don't really understand the goal of NavHostActivity.
Thanks!
https://github.com/igorwojda/android-showcase/blob/29ac9262958a63939b6ec7a101dace7c68969104/app/src/main/res/layout/activity_nav_host.xml#L8

thx for the answer @clevertrevor.
I think we can close the issue.