[8.0] Message cells refactor / redesign

⚠ Depends on finishing #453 first
For 8.0 release:
Goals:

Improve and refine cell APIs and layout
Better support for custom cells

Todo:

[ ] Dedicated cell factory class for generating cells
[ ] Provide a configuration to map cell classes and identifiers
[ ] Remove the cellTopLabel, cellBottomLabel, etc. 8.0 will be moving to a section-based layout. This means each cell will be in its own section, thus each cell can have it's own headers and footers.
[ ] Remove some existing hacks that make media cells work

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


[Sample Onboard Request] Teams Conversation Bot

Owner:
@frankqianms
ID:
bot-conversation-python
Title:
Teams Conversation Bot using Python
Description:
This bot has been created using Bot Framework. This sample shows how to incorporate basic conversational flow into a Teams application. It also illustrates a few of the Teams specific calls you can make from your bot.
Tags:
You can give your samples a set of tags so that users can easily locate your sample from a group of samples. Those tags can be:

Python
Bot
Bot Framework
Local debug
You can customize the tag you used for your sample, the recommended number of tags is less than 5.

Time:
5mins to run
Configuration:
Manual configurations required.
Users need to manage virtual environments and pip install dependencies before local debug.
This python bot sample only supports local debug currently.
(Source code NOT in this Repo) Sample URL:
Teams Conversation Bot
Thumbnail
./Images/2.WelcomeCard.PNG
https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/bot-conversation/python/Images/2.WelcomeCard.PNG
(Optional) Demo GIF:
./Images/BotConversation.gif
https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/bot-conversation/python/Images/BotConversation.gif

Can we update the title to indicate it's using Python: Teams Conversation Bot using Python

Can we update the title to indicate it's using Python: Teams Conversation Bot using Python

Sure. "Teams Conversation Bot using Python" or "Teams Conversation Python Bot"? Which one is better?

Can we update the title to indicate it's using Python: Teams Conversation Bot using Python

Sure. "Teams Conversation Bot using Python" or "Teams Conversation Python Bot"? Which one is better?

Teams Conversation Bot using Python would be better I think.

For source code:

please help run validation tool (https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/validation-tool) against this sample
Better use latest manifest version TTK supported, i.e. 1.16 in Teams manifest file
Better update .env.local and teamsapp.local.yml to include APP_NAME_SUFFIX variable to align with latest change

Finished running validation tool, and got the result.

There are several failed validations.

Since it is a python sample, there is no package.json.
Since it is an external sample and the Microsoft-Teams-Samples team insists to use appManifest/ rather than appPackage/ for there considerations, there are three failed validations on that.
Since this sample only supports local debug now, there is no env/.env.dev now.

This sample onboarded successfully, close the ticket


Recipe 12.9 Managing etcd

With etcd 3.2.24 in my Kubernetes 1.12 cluster, when I used 'curl localhost:2379/v2/keys/registry', result is empty.
From comment of this recipe I knew that newer Kubernetes is using etcd3 and probably etcd v3 API, however, even I tried to use 'curl localhost:2379/v3/keys/registry', still I got no output.
Is there any other things changed which readers should know?

Correction, my etcd3 is still using API v2

@bennybhlin I will repeat it again: we're using 1.7 in the book and all recipes are against this version. Having said this, I'll earmark this issue to remind ourselves to update this recipe in a potential new edition of the book and for now, if you follow this blog post you should get by?

@bennybhlin I've added you as a collaborator to this repo now so you can assign the enhancement label to issues you think should be addressed in a new version of the book. We will then select the ones for respective milestone.

Hahaha, sure Michael; all I want to do is to clarify any possible difference for readers, and tell them in my comments how to get rid of any error caused by difference. No offence.
It's close to the end of my own examples review; I promise you won't be bothered by me again for just a few more days :-D

Hum, we need to check this again, because latest version have etcd over TLS so you can talk to it straightup like this, you need to pass the certs.

Using this way still got no effect.
$ curl --cacert /etc/kubernetes/pki/ca.crt https://<IP_ADDRESS>:2379/v2/keys/registry
curl: (35) gnutls_handshake() failed: Certificate is bad


FE: Expose cluster ACL list

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Add ACL List component
Support ACL APIs
Extend useConfirm parameters
Extend Table component props, fix column sizing

Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[x] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

SonarCloud Quality Gate failed.
  0 Bugs   0 Vulnerabilities   0 Security Hotspots   5 Code Smells
 71.1% Coverage  11.0% Duplication

Hey, @Haarolean do I need to pay attention to it? Dupes are new UI Theme fields

@NeiruBugz nope


Cannot save setting to setting.json and keybindings.json if they are symlink. (Windows and Linux)

VSCode Version: 1.33.1
OS Version: Ubuntu 18 LTS and Windows 10 ENT

Steps to Reproduce:
On Windows, I use this cmd to create symlink:
mklink %APPDATA%\Code\User\keybindings.json %USERPROFILE%\.xxx\keybindings.json
mklink %APPDATA%\Code\User\settings.json %USERPROFILE%\.xxx\settings.json
On Linux, I use this cmd to create symlink:
ln -s $HOME/.xxx/settings.json $HOME/.config/Code/User/settings.json
ln -s $HOME/.xxx/keybindings.json $HOME/.config/Code/User/keybindings.json
On both OS, I tried to change font size from 14 to 13. Bot VS Code prompt error saying the change to json file cannot be saved.

Does this issue occur when all extensions are disabled?: Yes, not plug related.

.xxx\keybindings.json is a file in git repro. However, I don't think it's related to git, because notepad can open/save the change.

I don't think it's the same as this one, https://github.com/Microsoft/vscode/issues/37591, since I can repro the issue on both OS.

As far I know symlink only allows you to read data not write data. 🤔

As far I know symlink only allows you to read data not write data. 🤔

no. it's writable.
on Linux,
touch 1.txt
ln -s 1.txt 1
1 can be changed/saved by any text editor. And 1.txt will have the change.

I think that this is the same as https://github.com/Microsoft/vscode/issues/37591#issuecomment-341669901, it just exists on both platforms.
You may be able to work around this if the whole User folder is a symlink to another folder.

Thanks. But "User folder" has many files which I don't care (don't want to keep in git.)

Add them to .gitignore?

Thanks. Should work. But I would say it's a workaround instead of a solution.

@bpasero I use file service to do the changes, any reason why it is not working in this case?

I cannot reproduce when I tried on macOS with links. On Windows, the way you create symbolic links for files is not supported by node.js, so that is expected. I do not think there is an issue with VSCode here.

@bpasero Assigning it to you as it is related to file service.


Project sidebar UX improvements

Highlights:

[x] Updates the title to be a dropdown that switches organizations.
[x] Adds a new section that can be used to filter the files of a Project (documents, collections)
[x] Adds a search input for the projects list
[x] Adds a link to Insomnia subscriptions

TODO:

[x] Update playwright tests
[x] Clean up style={} to styled components
[x] Sidebar style update breaks styles in other pages

@gatzjames I fixed all the TODO list


Enhancement: Be able to create new entity cloning existing one

Is your feature request related to a problem? Please describe.
We need to create new records, just like existing ones but 3 or 4 fields need to be changed. It is very tedious to create a new entity and type everything (copy/paste). Especially in non-normalized legacy tables.
Describe the solution you'd like
I would like to be able to create a new entity/record, based on an existing one. I would like to just edit the fields that need to be changed.
Describe alternatives you've considered
Maybe one more icon, just like the "eye" and the "pencil", which then takes me to a CREATE screen, pre-populated with the cloned values?
Maybe select 1 with the checkbox and choose an action at the top, similar to delete? This approach is tacky because the user could have chosen N records, and this particular action only applies to 1 record. Maybe take the first one selected?
Maybe the VIEW screen could have a CLONE button? It would open a new screen where I would be editing a new entity, populated with the same values. Just the ID field would be different, of course.
Additional context
After having typed all options above, I think the most elegant is to have a CLONE button in the VIEW page. Perhaps between EDIT and DELETE.

I think we can add a new button 'save as new' on the edit page, similar to Django-admin, which would create a new item instead of editing the existing one.

That would be a great feature.

Is this feature can be implemented with row actions?


Zooming does not have momentum

Is this a bug report?
No. (feature request)

Have you read the Installation Instructions?
Yes.
Environment
"react": "16.3.1"
"react-native": "0.55.4"
"react-native-maps": "0.22.0"
I am referring to the functionality using GoogleMaps. I have not used the native iOS maps SDK to know if it functions the same.

Steps to Reproduce

Quickly pinch-to-zoom on a map view

Expected Behavior

Zoom movement should maintain momentum. In other words, if you move your fingers quickly while pinching-to-zoom it should continue to zoom after releasing with decaying speed.
Actual Behavior

Zooming stops immediately after lifting your fingers.
Reproducible Demo

To understand this issue, look at how zooming works on the official Google Maps app. Zooming is very intuitive because the speed of your "pinching" increases the speed of the zoom.
With the current implementation of react-native-maps, zooming from the highest level to the lowest could take about 10 pinches. On Google Maps it would be around 3.
I tried to get a good screen-capture, but couldn't find an app that worked well. So, let me know if my explanation was not clear.

@rborn Is this feature available now in the latest version, or why was it closed? Thanks.

I don't think it is, I just cleanup the repo from very old issues and yours was a victim of this.
If you think is important please open a new one following the new template.
Thanks and sorry for any annoyance 😻


'quantize' vector for inference

I running inference with the trained vq embedding matrix.  In the example ipynb only gives training instructions. I wonder if the edits I made to the source code are valid.
In vqvae.py, quantized vector is defined as below, and
LINE 98
quantized= self.quantize(encoding_indices)

The it then gets updated through the following lines,
LINE 100 to LINE 104
e_latent_loss = tf.reduce_mean((tf.stop_gradient(quantized) - inputs) ** 2)
q_latent_loss = tf.reduce_mean((quantized - tf.stop_gradient(inputs)) ** 2)
loss = q_latent_loss + self._commitment_cost * e_latent_loss

quantized = inputs + tf.stop_gradient(quantized - inputs)

And it seems that for inference, a non-updated version of this vector must be fed into the decoder instead.
So I made the following edits to the code, to return the non-updated quantize vector as well.
LINE 98
quantized= self.quantize(encoding_indices)
quantized_frozen = quantized

LINE 111
    return {'quantize': quantized,
            'quantize_frozen':quantized_frozen,
            'loss': loss,
            'perplexity': perplexity,
            'encodings': encodings,
            'encoding_indices': encoding_indices,
            'wmatrix':w,}

Thank you!

As I checked, I found them valid.


No colors in debug mode after 0.20.4 update

Environment
Knex version: 0.20.4
Database + version: Postgres
OS: Windows
Bug
After 0.20.4 update there are no colors in debug mode.
Version 0.20.3:

Version 0.20.4:

https://github.com/knex/knex/commit/65e1a3a3d0fd2107059d22736ec8c7379c3095a9
Maybe that commit could mess them if color codes does use % char for something... I suppose with debug mode you mean the debug attribute in knex config (there is also environment variable DEBUG=knex:*  which adds debug prints).

Released in 0.20.5


When typing in a hidden input field for a radio button, keystrokes are not filtered out.

Pressing any of the hotkey letters causes the input to lose focus and the radio button to change it's value.

@pmanko this was the reason for the use of the special-case changeFocusDirect function. It's been working fine, I assume you're playing around with this in response to issue #292

@krand7 Sorry about that, I didn't think I changed when changeFocusDirect was called.
When you get a chance, could you take a look through the most recent surveyAnimation.js.coffee file? Everything seems to be working except for the keystroke filtering issue for radio buttons, and I'm not sure how I broke it. I might not be adding the hidden inputs to radio buttons correctly, since I tested it before only on checkbox inputs.
I also am now submitting answers on input .change events instead of in the nextQuestionScroll function. This seems to be working well, except that I had to add custom triggers for changes to radio button inputs, as they are indirectly changed with javascript, which does not trigger the event.

Nice! I started doing the same thing with .change events, but noticed the same issue with custom events on radio buttons, so used a temporary fix in 1500ebb77895a29f28b77d97033fc7a8bf24dedb and 7beea73670d78f4684ff66d32c6319931121d836. Glad you got it working!
You're right, the current js file is probably too specific to have picked up on hidden fields with the radio input. I'll clean it up a bit and make sure it works, and will be more adaptable in the future.

Just a thought, Firefox handles .change events differently than other browsers (especially when navigating backwards to an existing page), so we may want to add this as a specific thing to check for in the test/integration/integration_checklist.md that @pmanko has compiled.

All is set on the front end, @pmanko can you address @remomueller 's suggestion to make tests for this?


Re-visit CI cloud integration tests

Cloud integration tests are run in CI with WESTMALLE: BETTER_THAN_LA_TRAPPE env var, which should trigger mock soda cloud creation and usage. There is no log/test output that would indicate that this actually happens, these tests just pass the same way as any other tests with no intention of testing the cloud integration. What should be done:

Make sure it is actually testing comprehensively what needs to be tested (=the cloud integration)
Ensure clear output of the integration tests to indicate what is being tested.

We need to analyze further and agree on what we do now vs what we postpone for later.  Options are
a) Do nothing: the current CI will run the test suite on postgres with WESTMALLE env var enabled.  Which means it will run activate Soda Cloud mock for all tests.  This adds a bit of coverage.  @m1n0 mentions this does not show in the logs.  We could add a logging to demonstrate in the test suite execution logs that soda cloud mock indeed is active.  But I don't think this logging adds extra coverage.
b) Add test(s) that verifies Soda Cloud interactions using a mock.  @vijay what is the status of Soda Cloud testing atm?
c) Integration tests that runs Soda Core & Soda Cloud: probably heavy to set up.  Might be included in as part of the Soda Cloud integration tests.

Just a note to
a) it indeed does not add extra coverage, but currently to verify whether we actually do what we want to in the test one has to go into code, understand it and debug it. Adding logs about what the mock integration test does surfaces this to anyone examining test logs, making the test less "mysterious"


Allow using float value in memory and cpu config

Issue #39, if available:
Description of changes:
change parse logic to Number from parseInt
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@DmitryGulin thank you for you review. I gonna split a method into parseInt and parseFloat.

@DmitryGulin I added a argument for parsing only int. Could you review it again?


chore(backend): add connector and account service

Changes proposed in this pull request

move connector and account service into backend
remove interledger package/workspace
decompose account service into separate services

Context

fixes #129 (see diagrams)
fixes #121
Checklist

[x] Related issues linked using fixes #number
[x] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass

The one concern I have currently is there is a few places were balances are adjusted. We have the transfer service and then transferFunds in the account service.

Yeah, I was debating where to put transferFunds. A few alternatives:
a) The functionality could be moved to the connector's balance middleware since that's currently the only thing calling it. We'd also use it for a transfer mutation, but maybe we could just do outgoing payments instead transfers? (It seems like intra-wallet transfers might make less sense in Rafiki with your proposed account model.)
b) transferFunds' transfer(s) setup could be a utility function (that maybe lives in the proposed liquidity service?). The balance middleware (and potential transfer mutation, etc) could call:
const transfers = liquidityService.setupTransfers({
  sourceAccount,
  destinationAccount,
  sourceAmount,
  destinationAmount
})
const error = transferService.create(transfers)
if (!error) {
  transferService.commit(transfers.map(t => t.id))
}

We'd lose transferFunds' more informed errors (like InsufficientLiquidity), but the balance middleware isn't even checking the error type.

Also I wonder if its worth not having separate withdraw and deposit services and rather having a singular liquidity service?

It's funny. In one iteration of the "after" diagram for #129 I had the deposit and liquidity service together in a single box to save space. 🤔 What if we keep those services as is for now, with the expectation of them (and other services) likely changing for your proposed account model?

Ok, lets leave as is for now to get this PR in and then resolve later


p4c-xdp: Build and install p4c-xdp compiler

This loads the p4c-xdp compiler extension, builds it, and instals it as
a part of the host native install. Useful for experimenting with P4 to
XDP.
Signed-off-by: Kyle Mestery<EMAIL_ADDRESS>

Closing for now.


Update delete-your-organization.md

The permissions section is inaccurate. While org owners can delete orgs, so can pca's. (and all org owners are pca's)

@pazand : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Postman Collection/Examples

Hey, what if we had an official Postman documentation for this API, with examples of requests and responses?
I just stumbled on this old one:
https://documenter.getpostman.com/view/18988925/UVeNni36#intro
Any sugestions?

Baileys is not an API, Baileys is a "tool" to create your own API.
If you want to use or create an API based on Baileys I suggest you take a look at https://github.com/salman0ansari/whatsapp-api-nodejs or many others available.


PlaceholderAPI NBT-API outdated.

Getting this on every startup of CrazyCrates:
[21:59:43] [Server thread/INFO]: [PlaceholderAPI] Successfully registered expansion: crazycrates
[21:59:43] [Thread-23/WARN]: [NBTAPI] [NBTAPI] The NBT-API at 'package me.badbones69.crazycrates.nbtapi' seems to be outdated!
[21:59:43] [Thread-23/WARN]: [NBTAPI] [NBTAPI] Current Version: '2.6.0' Newest Version: 2.6.1'
[21:59:43] [Thread-23/WARN]: [NBTAPI] [NBTAPI] Please update the nbt-api or the plugin that contains the api!

Both CrazyCrates and PlaceholderAPI are latest as of this report.

I am having the same issue with this.

I am having the same issue with this.

Fixed in latest.

Fixed in latest.


Cannot auth with restclient library

I'm trying to play around with the Restserver and Client that you've so wonderfully offered, but can't seem to understand why this isn't working.
My API controller is at base_url()/api and the following is trying to access the api.
		$this->load->helper('url');

		// REST Client
		$this->load->spark('restclient/2.0.0');
		$this->load->library('rest', array(
			'server' => base_url('api'),
			'http_user' => 'admin',
			'http_pass' => '1234',
			'http_auth' => 'digest' // or 'digest'
		));

        $user = $this->rest->get('api/user', array('id' => 1), 'json');

		$this->rest->debug();

The problem I have is that I'm passing the right credentials, but it doesn't auth. When I hit base_url('api'), the auth prompt shows up and I can log in just fine; it's just when I'm doing it through the REST client that I can't access the api.
I'm sure it's a simple issue, but one that I'd appreciate some help with. Thank you!

Downloaded the whole package again and it works!


Setup testing framework and improve type checking

Tasks

Introduce testing framework/tools (e.g. jest) to facilitate the writing of unit tests for the many API endpoints in the SDK.

Setup file structure and provide initial testing cases for a handful of endpoints

Improve type checking to properly match docs.zebedee.io/api

There are too many any types at the moment)
Properly segregate types into separate files

/bounty 30

/attempt #1
gonna start working on this one.

Amazing!

Since accessing the API endpoints requires an API key, I think it would be easiest if we had a key specifically for the purposes of testing - would it be possible to create one with the appropriate permissions? Should I just create one with my own zebedee dev account?

Hey @haruncurak that's perfectly fine. I've created this one for you: 8qJxln3JVJsQM0IOJhfnJopO0JSiLdlK. Let me know if you need access to the full dashboard.

@andrerfneves Hi - any updates on this issue?

@haruncurak so sorry about the delay here. Going to review and figure payout tomorrow 🫡

Thank you thank you 👍


Checkpoint III Submission

[x] Allow for CRUD operations on bucketlists
[x] Allow for  CRUD operations on items
[x] Implements authentication using JWT for API endpoints
[x] Has a client (website) consuming the API

bonus

[x] Uses twitter authentication

Git / Commit Messages

Consistent commit messages

README / Comments

The README is ok
Good: Has additional instruction on deploying to Heroku with templates

Code Quality

Code quality is good, with one minor nitpicks by Quantified Code.

Testing

Good: 95% test coverage.

Functionality

Code works as expected

UX/UI

Good: use of favicon
Work on the landing page (fixed on resubmission)
Nitpick: save the user extra clicks to accomplish a goal


Ability to retrieve version of the manifest (if Maven manifest) use by the session

In case manifest coordinates given to ChannelSession are Maven GA coordinates, prospero might be interested in knowing what is the actual resolved version of the manifest(s).
The use case is that during the update operation, prospero would compare current and target versions of the manifest(s), and refused the update operation (or requested further confirmation) if the update constitutes a downgrade to an earlier manifest version.

I think this will help you.
https://mega.co.nz/#!B31G2LaZ!uBBOCp9hLC7bq9kP8NC6s4DanQJJZuoFRr5FI_jkeic
I put the necessary dlls in the archive


⚠ ClamAV has degraded performance

In 2456626, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 58 ms

Resolved: ClamAV performance has improved in d862cea.


Fix data race in  query factory initialisation

For tracking purposes and if someone else is searching for answers related to this problem can you add a short description about the addition, and what your use case was?

For tracking purposes and if someone else is searching for answers related to this problem can you add a short description about the addition, and what your use case was?

Done


Move openeye imports inside functions that need them

By importing openeye at top level, we guarantee that the fragmenter package cannot be imported if the openeye toolkits are installed even if we are using components of fragmenter that do not require openeye. This also causes problems for testing packages built and deployed via omnia.
To enable package testing and use of the non-openeye components, we can move the import openeye statement inside of methods that actually need it.

Addressed via #42


[iTMSTransporter] - Transporter transfer failed.

New Issue Checklist

[ ] Updated fastlane to the latest version
[x] I read docs.fastlane.tools
[x] I read the Contribution Guidelines
[x] I searched for existing GitHub issues

Issue Description
**❯ bundle exec fastlane ios beta --env staging **
With this command from the local computer (client) is builds in a way that I succeed building.but when i start the installation via gitlab i get this error in the last step.
I added these files separately to the Fastfile file

before_all do
ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t Signiant"
end

  ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t Signiant"

  ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t DAV"

  ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = " "

Network Log
If you look at the log below, the endpoints used by apple have the response '200' so there is no block
<IP_ADDRESS> - - [15/Jul/2020:13:51:54 +0200] "CONNECT contentdelivery02.itunes.apple.com:443 HTTP/1.1" 200 5515 "-"

 "iTMSTransporter/2.0.0 (Mac OS X; 10.15.5; x86_64; Java 1.8.0-u131-b11) SmartClient/0.1.0" TCP_TUNNEL:HIER_DIRECT

 [13:52:59]: Transporter transfer failed.
 [13:52:59]:
 [13:52:59]: [iTMSTransporter] [2020-07-15 13:52:58 CEST] <main> DBG-X: Setting the throttle to 12500000 bytes per second.
 [13:52:59]: [iTMSTransporter] [2020-07-15 13:52:58 CEST] <Transport Protocol>  INFO: The Signiant transfer engine's status is CONNECTING
 [13:52:59]: [iTMSTransporter] Exception in thread "Transport Protocol Seeker" [2020-07-15 13:52:58 CEST] <Transport Protocol>  INFO: The Signiant transfer engine's status is DISCONNECTED
 [13:52:59]: [iTMSTransporter] java.lang.ArrayIndexOutOfBoundsException: 1
 [13:52:59]: [iTMSTransporter] 	at com.signiant.interactivetransfer.engine.TransferEngine$5.run(TransferEngine.java:3603)
 [13:52:59]: [iTMSTransporter] [2020-07-15 13:52:58 CEST] <main> ERROR: Could not start delivery: all transports failed diagnostics
 [13:52:59]: [iTMSTransporter]
 [13:52:59]: [iTMSTransporter]
 [13:52:59]: [iTMSTransporter]
 [13:52:59]: [iTMSTransporter] Package Summary:
 [13:52:59]: [iTMSTransporter]
 [13:52:59]: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:
 [13:52:59]: [iTMSTransporter] 	/var/folders/l2/x8wzywcd47zfxfzbj03dlyf40000gp/T/d20200715-4418-rchkba/975830741.itmsp - Error Messages:
 [13:52:59]: [iTMSTransporter] 		Could not start delivery: all transports failed diagnostics
 [13:52:59]: [iTMSTransporter] [2020-07-15 13:52:59 CEST] <main> DBG-X: Returning 1
 [13:52:59]: iTunes Transporter output above ^
 [13:52:59]: Could not start delivery: all transports failed diagnostics
 Return status of iTunes Transporter was 1: Could not start delivery: all transports failed diagnostics
 The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

🚫 All error Log 🚫
[13:51:02]: ▸ -----------------------------------------
[13:51:02]: ▸ {
[13:51:02]: ▸   "method": "app-store"
[13:51:02]: ▸ }
[13:51:02]: ▸ -----------------------------------------
[13:51:02]: $ /usr/bin/xcrun /Users/gitlabrunner/tmp-fastlane-ci-bundle/ruby/2.7.0/gems/fastlane-
2.128.1/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist
'/var/folders/l2/x8wzywcd47zfxfzbj03dlyf40000gp/T/gym_config20200715-4418-n34us8.plist' -archivePath
/Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname]\ 2020-07-15\ 13.36.51.xcarchive -exportPath
'/var/folders/l2/x8wzywcd47zfxfzbj03dlyf40000gp/T/gym_output20200715-4418-1msaci4' APP_IDENTIFIER='se.xx.xxx.test'
CODEPUSH_KEY='xxx' -allowProvisioningUpdates -allowProvisioningDeviceRegistration
[13:51:31]: Mapping dSYM(s) using generated BCSymbolMaps
[13:51:31]: $ dsymutil --symbol-map /Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname]\ 2020-
07-15\ 13.36.51.xcarchive/BCSymbolMaps /Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname]\
2020-07-15\ 13.36.51.xcarchive/dSYMs/[appname].app.dSYM
warning: /Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname]2020-07-15
13.36.51.xcarchive/BCSymbolMaps/[appname]-armv7.bcsymbolmap: No such file or directory: not unobfuscating.
warning: /Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname] 2020-07-15
13.36.51.xcarchive/BCSymbolMaps/[appname]-arm64.bcsymbolmap: No such file or directory: not unobfuscating.
[13:51:33]: Compressing 1 dSYM(s)
[13:51:33]: $ cd '/Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname] 2020-07-15
13.36.51.xcarchive/dSYMs' && zip -r
'/Users/gitlabrunner/builds/xxxxxxxxx/0/reactnative/[appname]/[appname].app.dSYM.zip' *.dSYM
[13:51:37]: ▸   adding: [appname].app.dSYM/ (stored 0%)
[13:51:37]: ▸   adding: [appname].app.dSYM/Contents/ (stored 0%)
[13:51:37]: ▸   adding: [appname].app.dSYM/Contents/Resources/ (stored 0%)
[13:51:37]: ▸   adding: [appname].app.dSYM/Contents/Resources/DWARF/ (stored 0%)
[13:51:37]: ▸   adding: [appname].app.dSYM/Contents/Resources/DWARF/[appname] (deflated 74%)
[13:51:37]: ▸   adding: [appname].app.dSYM/Contents/Info.plist (deflated 52%)
[13:51:37]: Successfully exported and compressed dSYM file
[13:51:37]: Successfully exported and signed the ipa file:
[13:51:37]: /Users/gitlabrunner/builds/xxxx/0/reactnative/[appname]/[appname].ipa
[13:51:37]: ----------------------------------
[13:51:37]: --- Step: upload_to_testflight ---
[13:51:37]: ----------------------------------
[13:51:37]: Login to App Store Connect<EMAIL_ADDRESS>[13:51:38]: Login successful
[13:51:42]: Ready to upload new build to TestFlight (App: xx)...
[13:51:54]: iTunes Transporter successfully finished its job
[13:51:54]: Going to upload updated app to App Store Connect
[13:51:54]: This might take a few minutes. Please don't interrupt the script.
[13:52:59]: Transporter transfer failed.
[13:52:59]:
[13:52:59]: [iTMSTransporter] [2020-07-15 13:52:58 CEST]  DBG-X: Setting the throttle to 12500000 bytes per second.
[13:52:59]: [iTMSTransporter] [2020-07-15 13:52:58 CEST]   INFO: The Signiant transfer engine's status is CONNECTING
[13:52:59]: [iTMSTransporter] Exception in thread "Transport Protocol Seeker" [2020-07-15 13:52:58 CEST]   INFO: The Signiant transfer engine's status is DISCONNECTED
[13:52:59]: [iTMSTransporter] java.lang.ArrayIndexOutOfBoundsException: 1
[13:52:59]: [iTMSTransporter] 	at com.signiant.interactivetransfer.engine.TransferEngine$5.run(TransferEngine.java:3603)
[13:52:59]: [iTMSTransporter] [2020-07-15 13:52:58 CEST]  ERROR: Could not start delivery: all transports failed diagnostics
[13:52:59]: [iTMSTransporter]
[13:52:59]: [iTMSTransporter]
[13:52:59]: [iTMSTransporter]
[13:52:59]: [iTMSTransporter] Package Summary:
[13:52:59]: [iTMSTransporter]
[13:52:59]: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:
[13:52:59]: [iTMSTransporter] 	/var/folders/l2/x8wzywcd47zfxfzbj03dlyf40000gp/T/d20200715-4418-rchkba/975830741.itmsp - Error Messages:
[13:52:59]: [iTMSTransporter] 		Could not start delivery: all transports failed diagnostics
[13:52:59]: [iTMSTransporter] [2020-07-15 13:52:59 CEST]  DBG-X: Returning 1
[13:52:59]: iTunes Transporter output above ^
[13:52:59]: Could not start delivery: all transports failed diagnostics
Return status of iTunes Transporter was 1: Could not start delivery: all transports failed diagnostics
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
+-----------------------------------+--------------------------------------------------------------------------------------------------------+
|                                                                Lane Context                                                                |
+-----------------------------------+--------------------------------------------------------------------------------------------------------+
| ENVIRONMENT                       | test                                                                                |
| PLATFORM_NAME                     | ios                                                                                |
| LANE_NAME                         | ios beta                                                                                |
| GET_INFO_PLIST_VALUE_CUSTOM_VALUE | 2.2.3                                                                                |
| LATEST_BUILD_NUMBER               | 31                                                                                |
| LATEST_TESTFLIGHT_BUILD_NUMBER    | 31                                                                                |
| BUILD_NUMBER                      | 32                                                                                |
| IPA_OUTPUT_PATH                   | /Users/gitlabrunner/builds/xx/0/reactnative/[appname]/[appname].ipa                             |
| DSYM_OUTPUT_PATH                  | /Users/gitlabrunner/builds/xx/0/reactnative/[appname]/DGFonder.app.dSYM.zip                    |
| XCODEBUILD_ARCHIVE                | /Users/gitlabrunner/Library/Developer/Xcode/Archives/2020-07-15/[appname] 2020-07-15 13.36.51.xcarchive |
+-----------------------------------+--------------------------------------------------------------------------------------------------------+
[13:52:59]: Error uploading ipa file, for more information see above
+------+------------------------------------+-------------+
|                    fastlane summary                     |
+------+------------------------------------+-------------+
| Step | Action                             | Time (in s) |
+------+------------------------------------+-------------+
| 1    | cocoapods                          | 35          |
| 2    | update_app_identifier              | 0           |
| 3    | get_info_plist_value               | 0           |
| 4    | latest_testflight_build_number     | 3           |
| 5    | increment_build_number             | 0           |
| 6    | update_project_team                | 0           |
| 7    | cd .. && ./scripts/patchInstall.sh | 26          |
| 8    | build_ios_app                      | 893         |
| 💥   | upload_to_testflight               | 82          |
+------+------------------------------------+-------------+
[13:52:59]: fastlane finished with errors
[!] Error uploading ipa file, for more information see above

Environment
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.15.3

Ruby
2.6.3

Bundler?
false

Git
git version 2.24.2 (Apple Git-127)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.3 (19D76)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.4.1

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
fastlane_require 'dotenv'
fastlane_require 'spaceship'

platform :ios do

  desc 'Push a new build to TestFlight'
  lane :beta do

  before_all do
    ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t Signiant"
  end
    cocoapods(
      podfile: 'ios/Podfile'
    )

    # To make sure the build numbers never collide, fetch current
    # build number from testflight for this version

    update_app_identifier(
      xcodeproj: 'ios/xxx.xcodeproj',
      plist_path:'../ios/xxx/Info.plist',
      app_identifier: ENV['APP_IDENTIFIER']
    )

    version = get_info_plist_value(
      path:'ios/xxx/Info.plist',
      key: 'CFBundleShortVersionString'
    )

    current_build_number = latest_testflight_build_number(
      app_identifier: ENV['APP_IDENTIFIER'],
      username: ENV['TESTFLIGHT_USERNAME'],
      team_id: ENV['FASTLANE_ITC_TEAM_ID'],
      version: version
    )
    increment_build_number(
      xcodeproj: 'ios/xxx.xcodeproj',
      build_number: current_build_number + 1
    )

    update_project_team(
      path: 'ios/xxx.xcodeproj',
      teamid: ENV['DEVELOPMENT_TEAM']
    )

    sh('cd .. && ./scripts/patchInstall.sh')

    build_ios_app(
      workspace: 'ios/xxx.xcworkspace',
      scheme: 'xxx',
      configuration: ENV['CONFIGURATION'],
      silent: false,
      xcargs: "APP_IDENTIFIER='" + ENV['APP_IDENTIFIER'] + "' CODEPUSH_KEY='" + ENV['CODEPUSH_KEY'] + "' -allowProvisioningUpdates -allowProvisioningDeviceRegistration"
    )

    upload_to_testflight(
      username: ENV['TESTFLIGHT_USERNAME'],
      skip_waiting_for_build_processing: true
    )
  end
end

platform :android do
  desc 'Submit a new Beta Build to Crashlytics Beta'
  lane :beta do

    gradle(
      project_dir: 'android',
      task: 'clean ' + ENV['GRADLE_BUILD_TASK'],
      properties: {
        "sign.xxx.android.keystore" => ENV['KEY_RELEASE_LOCATION'],
        "sign.xxx.android.storepass" => ENV['KEYSTORE_RELEASE_PASS'],
        "sign.xxx.android.alias" => ENV['KEY_RELEASE_ALIAS'],
        "sign.xxx.android.keypass" => ENV['KEY_RELEASE_PASS']
      }
    )
          firebase_app_distribution(
              app: ENV['FIREBASE_APP_ID_ANDROID'],
              testers<EMAIL_ADDRESS>              release_notes: "",
              firebase_cli_path: "/usr/local/bin/firebase"
          )
  end

  lane :tag do
    version_tag = "android/" + android_get_version_name(
      gradle_file: "android/app/build.gradle"
    )
    if !git_tag_exists(tag: version_tag)
      add_git_tag(
        tag: version_tag
      )
      push_git_tags()
    else
      raise "Git tag " + version_tag + " already exists"
    end
  end

  lane :playstore do
    gradle(
      project_dir: 'android',
      task: 'clean ' + ENV['GRADLE_BUILD_TASK'],
      properties: {
        "sign.xxx.android.keystore" => ENV['KEY_RELEASE_LOCATION'],
        "sign.xxx.android.storepass" => ENV['KEYSTORE_RELEASE_PASS'],
        "sign.xxx.android.alias" => ENV['KEY_RELEASE_ALIAS'],
        "sign.xxx.android.keypass" => ENV['KEY_RELEASE_PASS']
      }
    )
    supply(
      track: 'production'
    )
  end
end

`./fastlane/Appfile`
# Android parameters
json_key_file("supply_key.json") # Path to the json secret file - Follow https://docs.fastlane.tools/actions/supply/#setup to get one
package_name("se.xxx.android") # e.g. com.krausefx.app

# iOS parameters
#<EMAIL_ADDRESS># Your Apple email address

itc_team_id("xxx") # App Store Connect Team ID
team_id("xxx") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.128.1
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

faraday
0.17.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.7

gh_inspector
1.1.3

mini_magick
4.10.1

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

faraday_middleware
0.14.0

naturally
2.2.0

simctl
1.6.8

jwt
2.1.0

uber
0.1.0

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types
3.3.1

multi_json
1.14.1

signet
0.14.0

memoist
0.16.2

os
1.1.0

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-core
1.5.0

digest-crc
0.5.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

nanaimo
0.2.6

colored2
3.1.2

claide
1.0.3

CFPropertyList
3.0.2

atomos
0.1.3

xcodeproj
1.17.0

tty-screen
0.8.0

excon
0.75.0

json
2.3.0

bundler
2.1.4

declarative
0.0.20

mime-types-data
3.2020.0512

google-cloud-env
1.3.2

google-cloud-errors
1.0.1

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

generated on: 2020-07-15

Please update to the latest fastlane version and try again.

The problem was caused by a proxy. I solved the problem by adding 'DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS' as a variable to 'gitlab> Settings> CI / CD> variables'.
Key =>      DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS
Value =>  -Dhttp.proxyHost=proxy.xxxx.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy.xxxx.com -Dhttps.proxyPort=3128 -t DAV #
Type | Key(Click to sort Descending) | Value | Protected | Masked | Environments |
-- | -- | -- | -- | -- | -- | --
Variable | DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS | ********************* |   |   | All (default) |


Organise test data generation

Currently, at least

TypicalPersons
LogicManagerTest#TestDataHelper
some methods in TestUtil (e.g. getSamplePersonData())

have methods relating to generate test data.
Also, we have PersonBuilder. So for example, I think methods relating to generate test persons should be moved to there. Similarly, we might want to have AddressBookBuilder etc.

@yamgent is there a need to shift test generation data from TypicalPersons to PersonBuilder? I'm not sure hmm

I think they should all belong in a same class, but not necessary PersonBuilder. Put them all in TestDataHelper class?

So TestDataHelper contains PersonBuilder, TypicalPersons and AddressBookBuilder?

I mean the variables and methods should at least be in one cohesive class such as TestDataHelper. The classes PersonBuilder, TypicalPersons, etc, should not be inside another class.

ps don't get what you're saying. Can you list some examples of variables and methods that should be inside TestDataHelper?

Sorry I read this issue wrongly. The main problem is no longer valid as LogicManagerTest#TestDataHelper no longer exist, and you are removing the methods for TestUtil in #560 (because they are just duplicate of TypicalPersons). I am fine with everything being in TypicalPersons for now.

Noted, that way my PR fixes this issue as well then :)


Incorrect line numbers in Airbrake backtrace

When an exception occurs, the backtrace in Airbrake gives me incorrect line numbers
Here are some examples I got from the backtrace of one of my exceptions:
Synchronisation:1165 in SynchroniserProduits (Correct line number is 120)
Synchronisation:189 in SynchroniserInventaire (Correct line number is 63)
Synchro:125 in ProcessRequest (Correct line number is 24)
There does not seem to be a pattern to the line number differences.
Hypothesis: could the faulty line numbers be from the Common Intermediate Language (CIL) code?

I am experiencing this same problem - we are using NLog.Airbrake (which uses SharpBrake) and the line numbers reported in Airbrake are regularly way off.  I normally end up needing to log to two sources so I can use Airbrakes fantastic interface AND get the correct line numbers.
Please let me know if you would like any more info.

Please give it another chance with a new version of our notifier. A lot of new features and bug fixes have been added, and we hope that the problem with incorrect line numbers is fixed as well. But if it's still there, please create new issue with some details on your app/configuration (e.g. you are using some inline optimization techniques, code obfuscating or code fragments are generated dynamically, etc.) and we will try to fix it as soon as possible.


Export QEMU command can't be executed

Describe the issue
I discovered this feature via this issue, by searching for "headless qemu UTM". I tried it out, on a simple VM that works fine when launched by UTM, but the command it exported didn't work.
First, the command issued an argument with a path to a non-exist terminal file/device:
qemu-system-aarch64: -chardev pipe,id=term0,path=/Users/<me>/Library/Group Containers/WDNLXAD4W8.com.utmapp.UTM/8169C503-2646-4317-BE65-7F931B70884F.terminal: Could not open '/Users/<me>/Library/Group Containers/WDNLXAD4W8.com.utmapp.UTM/8169C503-2646-4317-BE65-7F931B70884F.terminal': No such file or directory

I found that there was a pair of files ending in .terminal.in and .out in that directory, so I tried editing the command to refer to the ...terminal prefix instead, and got this error:
qemu-system-aarch64: -chardev spicevmc,name=usbredir,id=usbredirchardev0: 'spicevmc' is not a valid char driver name

Thinking that perhaps the qemu-system-aarch64 command UTM uses has added new drivers, I looked for the one run by UTM (by examining the output of ps auwwx, and found this one: /Applications/UTM.app/Contents/Frameworks/qemu-aarch64-softmmu.framework/Versions/A/qemu-aarch64-softmmu, but when I try to run that command, I get zsh: exec format error. At this point I decided to chime in here.
Configuration

UTM Version: 3.1.3
OS Version: 12.2.1
Intel or Apple Silicon? - M1Max

Here's the complete (anonymized) exported command:
qemu-system-aarch64 -L /Applications/UTM.app/Contents/Resources/qemu -S -qmp tcp:<IP_ADDRESS>:4444,server,nowait -nodefaults -vga none -nographic -chardev "pipe,id=term0,path=/Users/<me>/Library/Group Containers/WDNLXAD4W8.com.utmapp.UTM/E3459327-D6AC-409C-ABCA-08EAAC345F57.terminal" -serial chardev:term0 -cpu host -smp cpus=8,sockets=1,cores=8,threads=1 -machine virt,highmem=off -accel hvf -accel tcg,tb-size=256 -drive if=pflash,format=raw,unit=0,file=/Applications/UTM.app/Contents/Resources/qemu/edk2-aarch64-code.fd,readonly=on -drive "if=pflash,unit=1,file=/Users/<me>/Downloads/Debian ARM.utm/Images/efi_vars.fd" -boot menu=on -m 1024 -device intel-hda -device hda-duplex -name "Debian ARM" -device nec-usb-xhci,id=usb-bus -device usb-tablet,bus=usb-bus.0 -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -device qemu-xhci,id=usb-controller-0 -chardev spicevmc,name=usbredir,id=usbredirchardev0 -device usb-redir,chardev=usbredirchardev0,id=usbredirdev0,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=usb-controller-0.0 -device virtio-blk-pci,drive=drive0,bootindex=0 -drive "if=none,media=disk,id=drive0,file=/Users/<me>/Downloads/Debian ARM.utm/Images/debian.qcow2,cache=writethrough" -device usb-storage,drive=drive1,removable=true,bootindex=1,bus=usb-bus.0 -drive if=none,media=cdrom,id=drive1 -device rtl8139,mac=26:31:64:F0:F0:28,netdev=net0 -netdev user,id=net0 -uuid 8169C503-2646-4317-BE65-7F931B70884F -rtc base=localtime

Hi, sorry for the confusion but the command isn’t meant to be executable. You’re right in that we’ve made changes to QEMU so it won’t work as-is. That option is meant purely as a debugging/support mechanism to determine what’s happening “under the hood”. Advanced users can pick and choose the arguments they care about (say path to the disk image) but that’s about it.

Aha, so the "running UTM headless" pointers that lead to that feature were a red herring. Understood.

#2280 will be implemented in the next update

Hi, sorry for the confusion but the command isn’t meant to be executable. You’re right in that we’ve made changes to QEMU so it won’t work as-is. That option is meant purely as a debugging/support mechanism to determine what’s happening “under the hood”. Advanced users can pick and choose the arguments they care about (say path to the disk image) but that’s about it.

Hi @osy would it be possible to modify the export QEMU command so that it uses the QEMU built by UTM? I have successfully migrated UTM VM's to QEMU, but it involves pulling out some of the options that the upstream QEMU complains about. It would be great if it were seamless. Thank you!

Or that it sanitises the call to work with vanilla QEMU?


Optimize performance further

This pull request builds on top of #24
This PR contains two additional performance optimizations:

Access keys() as a Stream. This makes it unnecessary keep a copy of all keys in memory at the same time if all we want is to, say, count them in getLoad().
Avoid redundantly storing relation member ways' tiles. The updated code uses a Set instead of a Map to remember which ways belong to a relation (necessary for --complete-relations or --complete-areas). The Map was previously used to store which tiles these ways are in, but that's redundant, as this information is already available in wmap. According to my profiling runs last year, the extra lists and boxed primitives in the redundant Map would, with some input files, consume the second-largest chunk of memory after the core nmap/wmap/rmap data structures.

@tordanik would you be happy with releasing the current state as an update?


Command description

Is your feature request related to a problem? Please describe.
There is no way to put a command description when registering a command through chimera. When using /help, the command appears with no description.
Describe the solution you'd like
A way to register a command description.

It has been on the back-burner for a long time now and kinda slipped my mind. The implementation I had in mind was to provide an additional description field in Literal and Argument, falling back to the usage text in the case where a LiteralCommandNode or ArgumentCommandNode is used (since Brigadier's  CommandNodes do not contain descriptions). Does this satisfy your use-case?

Yes, awesome!


Update IdentityModel from 1.12 to 2.8

While testing out this project I found that one of the NuGet dependencies was a major version behind.  I bumped it and checked out the source of the new IdentityModel to see what's different.  After making some small edits, it seems to all work correctly.  I am still quite new to Okta/OIDC so any help or review is appreciated.

Hey @mreishus! Thanks for your PR. I just rebuilt the sample from scratch in #14 (to fix some other issues) and upgraded IdentityModel in the process.
Sorry for the slow process on this. If you see any more improvements, please send more PRs! 👍


Change sourcemap setting in dev webpack config

I've been working on a modest project using the boilerplate and my rebuild times average around 4-5 seconds. Changing the source map setting to "eval" brought it down to 1-2 seconds. This has been a huge boost to my productivity.

You are correct it makes a difference in build speed, but without it you don't get soucemaps and becomes harder to debug.
Some more info:
https://webpack.github.io/docs/configuration.html#devtool
I'm going to close this and add a note in readme about it.


Soft Actor-Critic: is Q2 redundant in current implementation?

I am unable to find any place in the code, where Q1 and Q2 would be used asymmetrically, which makes me think: is Q2 completely redundant?

It's hard to say. It's the sort of thing that could benefit from deeper ablation analysis. My guess is that it isn't redundant all the time---I think it staves off some overestimation issues that would otherwise arise early in training. But, I also suspect that it becomes useless later in training, as Q1 and Q2 converge towards each other.
I recommend you try out some experiments where you remove it and see what happens.


Open with button to only show apps a user has selected

To avoid the random appearance of any app any user has made public in HydroShare (that was a problem e.g. #1132) establish the following model for users to "activate" apps that they want to use.  Only apps a user has "activated" show up on the open with button presented to a user.

The "Activate" feature for app resources should be similar to the "Favorite" feature for any resource.  The system should maintain a list of app resources each user has activated (or a list of users who have activated each app resource - internal implementation suggested to be the same as Favorite).
Activating an app resource should add it to the users My Resources page.  The My Resources page should let a user activate and deactivate an app resource similar to the way a user can favorite and unfavorite a resource.
An app resource landing page should include a button (suggest top right with other buttons) for a user to "Activate".
This implementation would mean a user has to look at an app landing page and activate any app they want to have on their "Open with" button.  The abstract on an App landing page then serves to inform users selection based on what the App does, an important mechanism for communication of this functionality and education of users.
All apps set for a resource type show up in the Web Apps tab of a resource landing page.  I suggest a heading similar to "Community apps you may choose to use with this resource" and an info link that goes to the app landing page and run link that launches the app.  The web apps tab thus serves as a way for users to discover relevant apps, and to run them if they wish without having to Activate (and without necessarily having to be logged in if the app permits this).

Another potentially much simpler option is to simply let anyone publish and share an app.  But we as the HydroShare team review them and put the best ones (and by "best" I mean working and doing something useful) in the list.

I am trying to avoid a solution where "we" the hydroshare team have to moderate this as it limits scalability.  But as an initial solution, I would be happy to have an approved app list, especially if you are willing to be the moderator who reviews it.

If we had masses of app developers developing apps, I would worry more about scalability.  And, considering how much development time it would probably take to implement the system above - I think we have to consider other options, until scalability becomes an issue.

@shawncrawley I am assigning this to you initially. Feel free to reassign if needed.

I am bumping this up in priority and assigning to BYU team @danames to prevent the rogue appearance of improper apps on all pages such as the "Trophic State HydroServer" that is really just a web page that is currently in HydroShare.
I suggest the following,
The Open with menu should hold only:

Apps that have been approved by the developer team.  This requires establishing functionality for an admin to check a setting on the app instance to enable this.
Apps that a user has identified that they want to use by either adding them to “My Resources” or  “Favoriting” them.

This should be an additional layer of filtering that goes on top of whether the user has permissions on the app and whether the app is configured for the type of resource the user has open.
Also, since we will shortly have resources with file types, the app instance settings need to be extended to be enabled when a resource has a file type that the app can handle.  In this case there may be merit in having Open with on the file right click menu in addition to at the resource level.
All apps that have been enabled based on resource or file type should still appear under the web apps tab where there should also be functionality to perform the action (add to my resources or favorite) that puts them on the "Open With" menu (and a few words that explain how to do this).

@alvacouch please add your suggestions here.

@danames @dtarb
To simplify this a little bit. can we directly use the existing "Add to my resource" button?
I am thinking the "Open With" dropdown should list the following webapp resources:

all webapp resources that appear on a user's "My Resource" page including
a) webapps this user owns;
b) webapps shared with this user;
c) webapps this user discovered and added to his "My Resource" page through "Add to my resource button"

webapps approved by system Admin: add a new admin-editable metadata field to control this.

@zhiyuli - This is getting better (narrower), but still leaves the possibility that apps can appear in the "Open With" list for a resource where the app has no clue how to actually open that resource.
Or is your condition all apps that meet conditions 1 and 2 AND know how to actually open the resource? Is there a setting or attribute on Apps that designates which resource/file types they can operate on?

@horsburgh
Currently the "file type" concept is not implemented in webapp yet. But we already have "supported resource type" concept implemented, so a webapp only shows up on resource landing pages of those supported types ("open with" dropdown and "webapp" tab page)
The above 2 conditions are to further limit which webapps should show up in the "open with" dropdown.

Oh - sweet. This seems reasonable to me and uses our existing model for users adding things to their resources, which I think is consistent with what @dtarb suggested.

@zhiyuli indicated that this functionality has been implemented and demo's but not merged and deployed due to not having an easy way to mark a web app as Approved.
I suggest we use a HydroShare resource to hold a list of approved apps (e.g. as a CSV text file with their name and resource ID).  Then access to editing this resource can be managed through HydroShare access control.  Then Open With functionality can read this file to obtain approved apps.  The same file could be used to generate a simple web page for launching apps as described in #2301 instead of each app requiring a Tethys implementation to just provide a launching button which is cumbersome for non-Tethys apps.

I think we implement a new page for managing apps and provide a menu option (MANAGE APPS) on the upper navigation bar to access this page. This page should list all web apps similar to listing of resources in my resources page (allow sorting). For each web app provide a checkbox for approval. Each row of web app should provide necessary information (title, purpose, web app author etc) about the web app to help in making the approval decision for the app. For each web app we should track who approved and the date of approval. Only users in the 'Manage Apps' group can have access to the MANAGE APPS menu. Since the approved status is maintained as part of the web app, then we can list only the approved apps for the specific resource type/file type/mime type when the Open With option is selected.
This obviously involves more work then what @dtarb has suggested above. However, I think in the long run this is the kind of functionality at a minimum we need for managing apps.

@danames @dtarb @horsburgh
@aphelionz has added a new "ShowOnOpenWithList" checkbox in his PR for “app replacement app”. Since the business logic of checkbox is unclear, we decided to remove that checkbox from that PR for now.
I then reminded @danames of a simplified workflow we discussed in April (see early conversations in this issue), which was to re-use existing “Add Favorite” button instead of adding any new checkbox.
The workflow is:
An app will show up in the Open-With-List on a resource landing page a user is viewing at, if this app supports this Resource Type, and meets any of the following 2 conditions:

This app resource is on this user's "My Resource Page"
This app is public/published, and has been marked as a "approved app" by admin

An app will meet condition (1) if
a)this user is the Owner of this app, regardless of its sharing status  (published/public/discoverable/private)
or,
b)this app has been explicitly shared with this user regardless of app’s sharing status  (published/public/discoverable/private)
or,
c)this app is public/published, and this user has discovered this app through discover page and added it as his favorite resource
@danames  supports this approach.
I would like to check with @dtarb and @horsburgh
Thanks

I think that the idea suggested by @danames in #2336 and @aphelionz in #2322 of a specific button "Show on Open With" is better than the approach I initially suggested in #1161 of having show on open with behavior determined through being added to "My Resources" or "Favoriting".  I think that a check box explicity labeled by what it does will be clearer to users than having to do something labeled something else.  Therefore I suggest the following implementaiton and business logic (Note that this is somewhat similar to the Activate concept at the very beginning of this issue, but updated, simplified and repeated for completeness):
The system should maintain a list of app resources each user has selected for "Show on Open With" (or a list of users who have activated each app resource - internal implementation I leave to a developer to choose what is best).
An app resource landing page should include a check box "Show on Open With" for a user to select if they want that web app to be on their open with menus.
This "Show on Open With" checkbox should be visible and able to be checked or unchecked for any web app resource that a user can open the landing page for in view mode.  Checking this box is not an edit action on a resource so does not require edit permissions, and should be possible in view mode.  It does not matter whether the resource is public or has been shared explicitly with a user.
Business logic for whether a web app should appear on "Open with" menu

Check that the user has permission to view the web app resource (it has to be public or they have to have explicit view permission).
If the web app resource has been CUAHSI approved it can appear on the "Open with" menu.  This takes precedence over whether or not a user has explicitly checked "Show on Open With".  If a web app resource is CUAHSI approved there is no evaluation of "Show on Open With", and whether or not show on open with is checked has no effect.
If point 2 is not met, but a user has explicitly checked "Show on Open With" it can appear on an "Open with" menu

Once the above 3 points have been evaluated the rules based on resource and file type as set for the web app resource instance (by the owner or user with edit permissions for the web app instance) need to be checked

Check whether the resource type matches the type for which the web app is configured.  This relies on existing web app metadata that lets a web app be configured to apply to specific resource types.
Check whether there are requirements for specific file types to be present in the resource and whether these requirements are met.  A web app may be configured to apply to specific file types within a multitype resource (such as a composite resource).  This configuration should indicate whether the web app should appear on the resource level open with menu (making the menu entry only appear if there is a file of the specified file type in the resource) or at the file type level (making the app appear on a file level open with menu for a specific file type).

There also need to be resource app entries that specify App-launching URL patterns separately for both resource level and file level open with actions, because the action for a resource level open with may need to be different from the action for a file level open with. This point also links to additional metadata needed for a web app resource to support this functionality that is addressed in #1610 or #2336.  Additional metadata is needed to support this business logic, and app launching URL patterns.
Note that the above suggestions decouple the concept of "Show on Open With" from other resource concepts "Favorite" and "Add to my resources".  I think that this decoupling makes things simpler and avoids potential user confusion, and also means that implementation can ignore changing anything related to these other concepts.
Note also that I decided that using an app required view access to the full resource.  Access to only the metadata (as would be the case if it was only discoverable) would not be sufficient.  I could have gone the other way in this (and could easily be persuaded to change), as an app resource is really a metadata only resource so discoverable and public are equivalent.

Wow. This seems really complicated. How many CUAHSI approved apps are there going to be? How is a user supposed to know an App exists so they can go to its landing page and tick a box for that App to appear? Seems like all the complication of vetting apps should be done before they are CUAHSI approved. On the user end, it should just be as simple as choosing to include an app in the "Open with" list or not.
Why not do that action right on the "Open with" button - e.g., click the button and there would be an option of "Edit this list". Then the user would get a pop up that allows them to tick boxes next to the apps that are CUAHSI approved and appropriate for the type of resource they are viewing. We would curate the list of approved Apps.

@dtarb
I have 2 question about this statement:
"Check whether there are requirements for specific file types to be present in the resource and whether these requirements are met. A web app may be configured to apply to specific file types within a multitype resource (such as a composite resource). This configuration should indicate whether the web app should appear on the resource level open with menu (making the menu entry only appear if there is a file of the specified file type in the resource) or at the file type level (making the app appear on a file level open with menu for a specific file type)."

The initial implementation I demo'd 2 weeks ago allows WebApp owner/editor to associate a webapp with one or more FileTypes. If being associated with more than one FileTypes, the relationship is "OR", which means this webapp can work separately with any of the selected FileTypes. Not to support "AND" or combination usecases, e.g a WebApp only works with a composite resource that has 2 raster filetypes + 1 feature filetypes). Are we on the same page?

With that said, since webapp only works with one instance of a FileType at a time, should the WebApp only show on filetype-level openwith list?

@zhiyuli we are on the same page on point 1.  On point 2 it may be that a web app can work at resource level as long as there are certain file types present, perhaps more than 1.  An example is multiple netCDF files.  Open with from the resource level may want to point to a URL such as http://hyrax.hydroshare.org/opendap/31acb0c0a66f4de08f541077bdf3e1d2/data/contents/contents.html that provides an entry into the top level resource contents that would may have folders for multiple files.  But open with from the file level may go down to a file such as http://hyrax.hydroshare.org/opendap/36ca923a48b94114a9e1fe9651c7dc9e/data/contents/SWE_time/SWE_time.nc.html
I am suggesting that the web app writer should be able to specify separate URL launching patterns for resource level and file level entry if that makes sense for their particular application.

@horsburgh the idea of this being editable from the open with list itself is appealing.  Speaking to @zhiyuli he suggested it be a second UI phase of the work, that could use the same backend functionality as what he could implement more easily for a "Show on Open With" check box.
The comment about CUAHSI approved misses the point, because CUAHSI approved apps will always appear on Open With (step 2 in the business logic).  Step 3 is to enable a user to add an app that they want to use that is not CUAHSI approved, which is the point of much of this.  If we decided to not allow open with ever for non CUAHSI approved apps this would be simpler, but that negates the scalability of the app resource type that @danames team developed, and I think limits uses.

@pkdash @alvacouch @Maurier @dtarb
I reviewed "hs_lable" code and got the following findings (correct me please):

hs_lable supports 3 functionalities:
a) "Add to my resource": user actively discovers a public/published resource over which he has NO explicit permission, and then adds this resource to his "My Resource Page"
b) "Mark as Favorite": User marks a resource on his "My Resource Page" as favorite
c) "Label a Resource": User first creates labels, and then labels resources on his "My Resource Page"

(a) and (b) store user-resource-flag relations in the same table UserResourceFlags, where flag value has only 2 choices: 'MINE' for (a), and 'FAVORAITE' for (b)
(c) stores user-resource-label relations in table UserResourceLabels, where label value can be any user-defined text.

I think I have 3 options here:

reuse current view functions and table UserResourceFlags, just to add a third flag choice-- "OPEN_WITH_APPS". Will this new flag choice make migration difficult?
reuse current view functions and table UserResourceLabels, just hard code a label value -
"MyOpenWIthApps", in which case this label value is reserved for internal user only (User should not create this label any longer)
create a new Table to store user-app relation and add new necessary view functions

What do you think? Thanks

My (weak) intuition is that option 1 seems best, but I would really prefer to defer to @pkdash @alvacouch @Maurier who know this code.

@dtarb @horsburgh @danames
This feature has been deployed on riverdev.hydroshare.org for testing.

I believe this issue has been addressed in current deployments.  Closing.  @zhiyuli if there is remaining functionality needed here, I suggest you open a new issue with just that functionality.


svg and path are missing from Dom_Html

These are both defined in Dom_svg, where I think they ought to be?

Oh, silly me. I was defaulting on opening Html and totally miss it.


Add meaningful string representations for resolution invariants

Description of the change:
Original description:

During dependency resolution, invariants are enforced for
one-operator-per-package and one-provider-per-api. Their user-facing
string representation (shown when they prevent resolution from
succeeding) had re-used the same representation as constraints on
Subscriptions out of convenience.

Recently, the messaging of Subscription-related constraints was
changed to be more descriptive which inadvertently made the invariant
messaging misleading. This patch improves constraint messaging for all
dependency relationships except bundle dependencies.

This rebase of #1994 adds additional tests when multiple subscriptions
exist for the same package. Those tests uncovered a weird UX for an
edge case: if two subscriptions are present for the same package, and
the resolver manages to find an operator that satisfies both.
This is not likely or common today, but since it is a potential source of
confusion I updated the resolver to ensure that in that case, both
subscriptions are updated to point to the operator that satisfies both.
Prior to that change, only one of the subscriptions that matched would
be picked (whichever came first in the query).
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/test unit

/hold
The failure in the unit tests looks unrelated to this change, but it seems to happen consistently

The unit test passed locally for me

/test unit

/hold cancel

/cherry-pick release-4.7


Canon PTZ CR-N300 - https with password

I am trying to connect a Canon CR-N300 camera to Companion. The camera is using http at 443 with a user / password. Is there any way to use this module to connect to this camera? I just get an error in Companion (instance(canon-ptz): Error from PTZ: ECONNRESET).

Why can't you use port 80?


Add Information about Webpack usage in the Readme or Docs

For webpack users it may be difficult to get xterm running with es6 modules. Most libraries use prebuild files on npm that do not need transpiling.
Additionally, a lot of webpack configs in the internet exclude the node_modules from transpiling, which results in errors with pure es6 modules.
Maybe drop a hint for webpack config like this:
Remove the exclude rule for node_modules and instead use a custom include rule. Just specifying a include rule will not work as exclude has precedence over include. This also avoids complex regular expressions in exclude especially with more es modules to come.
...
    loaders: [
      {
        test: /\.js$/,
        include: [
          // We explicitly include all directory, otherwise, this will break
          path.resolve(__dirname, 'YOUR_SRC_DIR'),
          path.resolve(__dirname, 'MAYBE_ANOTHER_ONE'),

          // Add all npm modules that need to be transpiled!
          // Include xterm module
          /\bxterm\b/,
        ],
        loader: 'babel-loader',
        query: {
          presets: ['es2015', 'react']
        }
      }
    ]
...

Hi @waywaaard es6 modules are not included in a release yet. They will be included in 2.0, which needs a few things yet to be implemented and it will include transpiled files in the dist directory.
A PR including documentation for using with Webpack in the README file would be more than welcome 😊 .

I guess, then we should wait until the es6 modules are ready and then I can make a PR.

@parisk should this be on the v2 milestone?

That would be great, but as I have no experience with webpack right now, let's leave it outside.
Unless @waywaaard could prepare a PR for https://github.com/xtermjs/xtermjs.org 😊 .

I can try make one.

That would be great. Use branch xtermjs-2-0 as your base.

IMO it makes much more sense for users to just use dist/xterm.js rather than trying to configure Webpack with the same transpiler setup xterm has. xterm's transpiler configuration could change over time, so needing to sync it up could be annoying. Also, the dist version is what you'll get if you simply require('xterm') because that's what package.json's main points to.
Using the dist JS works fine, expect for an annoying warning about xterm.js being a pre-built JavaScript file. That warning apparently has something to do with Browserify; see https://github.com/webpack/webpack/issues/1617. Fortunately, xterm has no external dependencies, so you can suppress the warning by adding this to your Webpack config:
noParse: [
	/xterm.js$/
]

I think that documenting how to use the built xterm.js with Webpack at https://github.com/xtermjs/xtermjs.org based in @rdicroce's comment should be enough.

I'm consolidating all bundling/loadAddon related issues into https://github.com/sourcelair/xterm.js/issues/1018, please comment on that issue if you have thoughts :smiley:


[WIP] Update log injection semantics

Updates log injection semantics

Field
Serilog format
Common format

Service name

"service.name"

Service version (new)

"service.version"

Environment

"deployment.environment"

Tracer ID

"trace_id"

Span ID

"span_id"

Log lib
Key syntax
Status

ILogger
CorrelationIdentifier.Serilog
:x:

Log4Net
CorrelationIdentifier.Common
:heavy_check_mark:

NLog
CorrelationIdentifier.Common
:heavy_check_mark:

Serilog
CorrelationIdentifier.Serilog
:x:

Log4Net example output
2021-11-12 21:32:49,860 [1] INFO LogsInjection.Log4Net.Program {deployment.environment: "(null)", service.name: "(null)", service.version: "(null)", trace_id: "(null)", span_id: "(null)"} - [ExcludeMessage]Entering Datadog scope.
2021-11-12 21:32:50,269 [1] INFO LogsInjection.Log4Net.Program {deployment.environment: "(null)", service.name: "(null)", service.version: "(null)", trace_id: "(null)", span_id: "(null)"} - Calling the PluginApplication.Program in a separate AppDomain
2021-11-12 21:32:51,485 [1] INFO LogsInjection.Log4Net.Program {deployment.environment: "(null)", service.name: "(null)", service.version: "(null)", trace_id: "(null)", span_id: "(null)"} - Returned from the PluginApplication.Program call
2021-11-12 21:32:51,538 [1] INFO LogsInjection.Log4Net.Program {deployment.environment: "(null)", service.name: "(null)", service.version: "(null)", trace_id: "(null)", span_id: "(null)"} - [ExcludeMessage]Exited Datadog scope.


Question about loading data?

Hi, I have been really trying to understand the CUDA kernel provided and am slightly confused about why you are loading data in using cub::BLOCK_LOAD_WARP_TRANSPOSE. I am confused why data is stored in stripped format and not just direct format, and where this is happening. To me, all the checks in selective_scan.cpp make me think that data should be stored in a direct format. I understand how vector loading is working, but then am still confused why being directIO causes us to load in a direct form rather than a stripped form. Any guidance on this would be amazing, and thank you so much for the help and great work!

Data is stored contiguously (i think that's what you mean by direct). You can just print things out (with printf) to see which thread is loading what.

Thank you, I printed stuff out a realized I was being silly, you load the data in a stripped format and then transpose to make it direct. I think to improve access speeds. Thanks for the help!


display three letter of day of week instead of two letter day of week

What are you trying to do?
I want the table header of day of week to have three letter of day
"Sun Mon Tue Wed Thu Fri Sat"
Reproduction
https://angular-k7qpfp-material-datepicker-day-of-week-names.stackblitz.io
Steps to reproduce:

click the calendar icon
see the header day of week: "Su Mo Tu We Th Fr Sa"

Environment

Angular: 8.0.0
CDK/Material: 8.0.0
Browser(s): chrome
Operating System Windows

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.

Hold on... Why there is a template for troubleshooting issue?
@josephperrott do you know how to display three letter day of week in the date picker?

Hey @cls-yzhang - Joey's response was just a standard canned message we used to put on troubleshooting issues. The troubleshooting template is a new thing for us so we're still getting used to it :)
Moment provides its own locale strings which are the two-letter weekdays that you see. If you want to override it, you can simply extend the MomentDateAdapter and override the function getDayOfWeekNames to return whatever you'd like.

class CustomDateAdapter extends MomentDateAdapter {
  getDayOfWeekNames(style: 'long' | 'short' | 'narrow') {
    return ['Sun', 'Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat'];
  }
}

Here's your example with the three-letter days: https://stackblitz.com/edit/angular-k7qpfp-material-datepicker-day-of-week-names-yrp4hr?file=src/app/app.component.ts

@andrewseguin thanks a lot!


the substrate-node helmchart services p2p port is named http

fixed in https://github.com/threefoldtech/tfchain/commit/55ed2a7fb2bdabda2fb1b5f1d9f8e42f84dfe67e


tsPCRAnalyzer.cpp is not compiling with gcc 9.1 under Ubuntu

Dear @lelegard
I upgraded my GCC to version 9.1.0, but when I compiled the sources with make it has stopped with the folllowing messages:
make CC=gcc-9.1 GCC=gcc-9.1 CXX=g++-9.1 AR=gcc-ar-9.1 NODTAPI=1
[CXX] tsPCRAnalyzer.cpp
tsPCRAnalyzer.cpp: In constructor 'ts::PCRAnalyzer::PCRAnalyzer(size_t, size_t)':
tsPCRAnalyzer.cpp:46:1: error: 'ts::PCRAnalyzer::_packet_pcr_index_map' should be initialized in the member initialization list [-Werror=effc++]
46 | ts::PCRAnalyzer::PCRAnalyzer(size_t min_pid, size_t min_pcr) :
| ^~
cc1plus: all warnings being treated as errors
../../Makefile.common:898: recipe for target 'release-x86_64/tsPCRAnalyzer.o' failed
make[2]: *** [release-x86_64/tsPCRAnalyzer.o] Error 1
I have some suggestions for this error: in line 46 all values are declared without _packet_pcr_index_map. With which one value I have to add this starting variable?
Best regards

Hi @haronix-bg
Thank you for reporting this. The member field _packet_pcr_index_map was added in a very recent code contribution. The addition was not tested yet with all compilers and versions. This is fixed now.

Dear @lelegard
Thanks for the fast reply and quickly fix. I'm not saw the bug fix from yesterday.


Ability to add permissions to users.

Sometimes some users need much more granular authorization that what roles can provide.  Currently, if a user needs anything a role doesn't provide, it would require creating a unique role just for them.  If permissions could be assigned to a user, then they could be given a role, in addition to a permission or two that they might also need.  I think it would be a relatively simple addition that would provide much greater functionality.

Sorry to revive an old issue but I just wanted to point out that I've written a guide to bringing user-based permission support to Entrust.
This is probably forward compatible if Entrust's API doesn't change drastically. Use it at your own risk / mental state.
https://gist.github.com/uzegonemad/38608e137f7e8f95d933


Update readme to reflect changes to config structure in Strapi stable

This PR changes the readme to reflect the changes in the Strapi stable release regarding the config structure. By default there is no environment folders and the middleware is now a javascript file instead of a json.
Users can now also use .env (dotenv), I included links to the Strapi documentation for that.

Looks great, thanks :)


Pre-compile application on kitto.new

As the CLI is built out more, to lower the barrier of entry, when running mix kitto.new the application should get compiled to make all mix tasks immediately available.

I like the idea, though in order for the dependencies to be compiled they have to be fetched before via: mix deps.get which is currently optional in mix kitto.new.
The best option seems to me to split the currentFetch and install dependencies? [Yn] question in 2 parts:

Fetch and install Elixir dependencies? [Yn]
Fetch and install JavaScript dependencies? [Yn]

When the user chooses to install Elixir dependencies we can also mix deps.compile to make the mix tasks available.

Another option for building this is to code it into kitto_new instead of Kitto core.


Problems to retrieve Gitolite hook parameters in Gitolite config 'namespace : multimailhook'

Hi,
I was installing the latest version on a new machine, everything went smoothly until I've checked in the Config Test tab, where there are plenty of red exclamation marks. In particular, all the entries in hooks installed and in Mailer parameters installed are red.
I've followed exactly the same procedure I've used two weeks ago without any problem, but now it doesn't work. It is true that I had to move to the devel branch for both boostrap_kit and git_hosting, because the .x version did not work at all -- whereas they were working two weeks ago.
If I check in the logfile, the only thing I can see is the following:
2015-03-24 15:20:30 +0100 [INFO] Testing if Redmine user 'redmine' can sudo to Gitolite user 'git'...
2015-03-24 15:20:30 +0100 [INFO] OK!
2015-03-24 15:20:30 +0100 [ERROR] Problems to retrieve Gitolite hook parameters in Gitolite config 'namespace : multimailhook'
2015-03-24 15:20:30 +0100 [INFO] Installing Redmine Gitolite mirroring SSH keys ...
2015-03-24 15:20:31 +0100 [INFO] Done !
Can you please help me solve this issue?
Thanks a lot in advance!
Rob

Solved! I regressed the git_hosting version to v.1.1.x and the bootstrap_kit v.0.2.x, and for the moment it seems to work (when using the devel version for bootstrap_kit, I was having an error at compile time).
Thanks anyway!
Cheers,
Rob


chore: clean up

Adds provider_token example
Adds middleware example
Tries to make middleware token refreshing work correctly (it does seem to work locally, but not sure if it'll work correctly on the edge)...

Is it possible to add a provider_token client side example? I can't figure that out. Is the provider_token only available server_side with this package?


Central force problem

Definition
A generic central force problem.

Lagrangian
Equation of motion

References

https://www.damtp.cam.ac.uk/user/tong/relativity/four.pdf

Landau vol 1, sec. 14
If we reduce to 2d, $$L = \frac{m}{2} \left(\dot{r}^2 + r^2 \dot\phi^2\right) - V(r)\,.$$
$L$ does not contain $\phi$ explicitly, making $\phi$ a cyclic variable. We have an integral of motion $l \equiv m r^2 \phi$.
$L$ does not contain $t$ explicitly. We have a second integral of motion, the energy
$$E = \frac{m}{2}\left(\dot r^2 + r^2 \dot\phi^2\right) + V(r) = \frac{m}{2} \dot{r}^2 + \frac{l}{2mr^2} + V(r)\,.$$
We can derive
$$\frac{\mathbb{d}t}{\mathbb{d}r} = \left(\frac{2}{m}\left(E-V(r)\right) - \frac{l^2}{m^2 r^2}\right)^{-1/2}\,.$$

For future reference:
https://www.aanda.org/articles/aa/full_html/2018/11/aa33162-18/aa33162-18.html

After some explorations in #50 , I have a feeling that a generic numerical integral of arbitrary initial condition and parameters are time consuming for our purpose.
I propose we reduce this into different scenarios and provide more dedicated formulations.

[ ] Circular/elliptical orbits
[ ] Parabolic orbits

Free fall is not interesting for our use case.


[composer] presence not working

composer 0.3.7 candidate on staging
have two windows pointing to the same object, waited a good few minutes, no presence indicators

#5100

Will restore viewers w/ #5174


Cannot stop health check once started

Checklist

[ ]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
8.18.0
ZwaveJS version
10.23.1
Describe the bug
Once you start an health check it's impossible to stop it, which is especially annoying if you are doing multiple rounds:

Clicking on the close button doesn't stop it.
To Reproduce
Click on Network Graph, any node, diagnose, select multiple runs, start, close. Then look at the looks: it's still running.
Expected behavior
Either close should stop the health check or a stop button should be added.
Additional context
The browser is Chromium and the screen resolution is 2560x1440, OS is Gentoo Linux ppc64le (Raptor CS Talos 2).

cc @AlCalzone


lib64 is not included in the path

When I build the portable python in the docker image of centos 7.9, I notice when I enable libffi or specify openssl 3.x, the libraries are generated and located in /build/deps/lib64. And this folder is not configured to read when compiling, so it is already failed.
I have checked the source code,and only find all of the lines which use lib are missing lib64, e.g.:

https://github.com/codrsquad/portable-python/blob/v1.9.1/src/portable_python/__init__.py#L510-L511
https://github.com/codrsquad/portable-python/blob/v1.9.1/src/portable_python/__init__.py#L523-L525
https://github.com/codrsquad/portable-python/blob/v1.9.1/src/portable_python/__init__.py#L532-L534

This potentially related with #41

Oh, don't know which part generates that, IIRC I only ever stated {build}/deps/lib (not lib64...).
Hmm. Should we do something like this?
lib64 = self.deps / "lib64"
if lib64.exists():
    return lib64

return self.deps / "lib"

Only the libraries of libffi and openssl are in lib64, so we still need to keep lib for other dependencies.
I did several tries about add lib64, but no lucky, the commit is here:

https://github.com/grammy-jiang/portable-python/commit/bd1775b3360c23caf44555a6040c1188907c7401

The deps folder structure becomes like this with libffi and openssl enabled in the docker image of centos 7.9:
foo@bar:~$ /tmp# ls -l build/deps
total 12
drwxr-xr-x.  2 root root 4096 Apr  9 05:14 bin
drwxr-xr-x. 17 root root 4096 Apr  9 05:14 docs
drwxr-xr-x.  7 root root  278 Apr  9 05:14 include
drwxr-xr-x.  3 root root 4096 Apr  9 05:14 lib
drwxr-xr-x.  4 root root  110 Apr  9 05:11 lib64
drwxr-xr-x.  3 root root   18 Apr  9 05:09 man
drwxr-xr-x.  5 root root   40 Apr  9 05:11 share
foo@bar:~$ /tmp# ls -l build/deps/lib64
total 6576
drwxr-xr-x. 2 root root       6 Apr  9 05:11 engines-1.1
-rw-r--r--. 1 root root 5591940 Apr  9 05:11 libcrypto.a
-rw-r--r--. 1 root root  106478 Apr  9 05:09 libffi.a
-rwxr-xr-x. 1 root root     875 Apr  9 05:09 libffi.la
-rw-r--r--. 1 root root 1026826 Apr  9 05:11 libssl.a
drwxr-xr-x. 2 root root      61 Apr  9 05:11 pkgconfig


Document _versions endpoint

Document undocumented _versions endpoint.

Good first test of a fast docs-only CI run!

@big-r81 should we merge this?

@nickva
Of course, can you check why the CI is failing? Am on vacation…

@big-r81 ah no worries, enjoy your vacation.
The issue is the json document is not regular json and the latest sphinx does check that
It doesn't like this part:
                    "sha256",
                    ...
                ]

I'll fix it and merge it.


feat: support stored values in with! and update!

This adds support for using both signals and stored values in the with! and update! macros, without needing to use with_value! and update_value!.
(also modified the doctests a bit to match the doctests used on signals)
I'm not that great with traits, so feel free to change up the implementation if you see a better way :)

Nice! Thanks!


Use official windows build

Checklist

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

Drop the cmake build system on Windows. Use the official build with conda posix package instead of cygwin.
This fixes #37
I built successfully locally but got some issue depending on the python version (some mix with the python installed with conda and the host env). This MR is to test the build on conda-forge.
I had to:

replace /manifest with -manifest and DUMPBIN.EXE /SYMBOLS with DUMPBIN.EXE -SYMBOLS, otherwise the / is replaced by the conda env path (is it because of the ROOT env variable set to that path?).
change the path of sort
changed the DLL name (compiler_version_suffix empty and remove minor and patch from SharedLibraryDllNameTemplate) to keep the same name as in the previous build. I was hoping to make the build compatible but there has still issues. See below. If max_pin='x.x' is correct, we could have the minor version, but not the patch one.
added -MACHINE:X64 based on https://github.com/tango-controls/omniorb-windows-ci/blob/master/appveyor.yml

To build, we have to pass 2 variables (done in bld.bat):

PYTHONPATH: windows style path to the host env python site packages
PYTHONPATHOMNI: cygpath style python exe path (used in config.mk)

One issue is that the result isn't binary compatible with previous build... At least cpptango needs to be re-compiled.
Trying to run an existing TangoTest with this new build raises: The procedure entry point ??1TypeCode_member@CORBA@@QEAA@XZ could not be located in the dynamic link library tango.dll.
After recompiling cpptango, I could run TangoTest without recompiling the binary.
I see 2 options:

If we don't want to break compatibility, we apply this change only on omniORB 4.3. We have to wait for cpptango support to use it.
Merge this and rebuild cpptango. If people install last build from cpptango and omniorb, no pb. If they update cpptango without omniorb (or omniorb without cpptango), that will break their env.

Looking at packages who need omniorb or omniorb-libs on Windows, only cpptango should be impacted.

 Other failed with:

../../../bin/x86_win32/oidlwrapper.exe -gnuwin32 -T -bcxx -Wbh=.hh -Wbs=SK.cc -p../../../src/lib/omniORB/python3 -I../../../idl -Wbdebug -Wba -p../../../src/lib/omniORB/python3 -I../../../idl -Wbdebug -v -ComniORB4 ../../../idl/Naming.idl
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = 'D:\bld\omniorb_1681904925966\_h_env;'
  program name = 'python'
  isolated = 0
  environment = 1
  user site = 0
  import site = 1
  sys._base_executable = 'D:\\bld\\omniorb_1681904925966\\work\\bin\\x86_win32\\omniidl.exe'
  sys.base_prefix = 'D:\\bld\\omniorb_1681904925966\\_h_env'
  sys.base_exec_prefix = 'D:\\bld\\omniorb_1681904925966\\_h_env'
  sys.executable = 'D:\\bld\\omniorb_1681904925966\\work\\bin\\x86_win32\\omniidl.exe'
  sys.prefix = 'D:\\bld\\omniorb_1681904925966\\_h_env'
  sys.exec_prefix = 'D:\\bld\\omniorb_1681904925966\\_h_env'
  sys.path = [
    'D:\\bld\\omniorb_1681904925966\\_h_env',
    '',
    'D:\\bld\\omniorb_1681904925966\\_h_env\\python38.zip',
    'D:\\bld\\omniorb_1681904925966\\work\\bin\\x86_win32',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00000518 (most recent call first):
<no Python frame>
PYTHONPATH=%PREFIX%;
%SRC_DIR%\bin\x86_win32\omniidl -T -bcxx -Wbh=.hh -Wbs=SK.cc -p..\..\..\src\lib\omniORB\python3 -I..\..\..\idl -Wbdebug -Wba -p..\..\..\src\lib\omniORB\python3 -I..\..\..\idl -Wbdebug -v -ComniORB4 ..\..\..\idl\Naming.idl
make[2]: *** [omniORB4/Naming.hh] Error 1

Looks like some python path is missing... More debugging to do.

Regarding the ABI incompatibility. This is a problem which others should have as well or? What is the standard conda procedure? On linux you would go from package name libabcd" to libabcd1and makelibabcd1conflict withlibabcd` (very rough summary).

Regarding the ABI incompatibility. This is a problem which others should have as well or? What is the standard conda procedure? On linux you would go from package name libabcd" to libabcd1and makelibabcd1conflict withlibabcd` (very rough summary).

conda handles that differently. In the recipe you specify how a package is compatible using:
      run_exports:
        - {{ pin_subpackage('omniorb-libs', max_pin='x.x') }}

maxp_pin could be x or x.x.x depending on the package.
max_pin='x.x' means that if you compile a package with omniorb-libs 4.2.5, it will add the run requirement omniorb-libs >=4.2.5,<4.3.0a0.
This is what we have today. If we switch to omniorb 4.3, there is no issue.
Problem here is that this PR introduces a new way to build omniorb that breaks ABI compatibility with the same version (just a different build number). It's not really supposed to happen.

Great work, @beenje!
I also think we should merge this and rebuild cpptango.  The whoneeds query shows that only cpptango is affected on Windows, and we (Tango Controls Community) want this issue fixed for Tango Controls on Windows.

Thanks for the feedback @t-b and @ajoubertza . Merging!


Graph missing current time highlight

There is no highlight for current hour in graph while it was before, please fix! :)

This issue was caused by the "daylight saving" time to end which returns 2 of the 3am prices making the graph get confused.
I've implemented a back-end change to fix this issue.