[CO-432] Extending PrefilteredBlock

Description
At this moment prefiltering comes down to filtering out the relevant inputs and so the regular call to updatePending fails to see that the foreign transaction that got removed. Up till now we were looking at the outputs instead of the inputs not because of any fundamental difference between regular and foreign pending transactions, but rather because prefiltering is removing some information that we need and so we look at the outputs as a (somewhat poor) substitute instead. As a consequence we have updatePending and updateForeign removing corresponding inputs and outputs, respectively.
Here, the following changes are proposed:

We adopt lookup seeking one of our currently tracked foreign transaction to appear in the block's inputs, and if so, make sure it appears in the prefiltered block
(a) getters for foreign pending block are added
(b) in prefilterTxForWallets we search inputs for transactions that have the same id as the foreign transation in the respective pending set
(c) PrefilteredBlock is extended by pfbForeignInputs and populated if search of point 1b is successful
(d) refactoring of updatePending in such a way that it works also with pfbForeignInputs and service both input and foreign input checkpoint
(e) update of both (wallet-new/src/Cardano/Wallet/Kernel/DB/Spec/Update.hs) - applyBlock and applyBlockPartial is done in the context of the change of point 1d
updateForeign is removed
updateUtxo is changed in such a way that it includes rather (Set.union pfbInputs pfbForeignInputs) than pfbInputs

Linked issue
https://iohk.myjetbrains.com/youtrack/issue/CO-432
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[x] I have read the style guide document, and my code follows the code style of this project.
[x] If my code deals with exceptions, it follows the guidelines.
[x] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Pull Request Test Coverage Report for Build 60

44 of 66 (66.67%)  changed or added relevant lines in 6 files are covered.
32 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.2%) to 50.18%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Cardano/Wallet/Kernel/DB/Spec/Update.hs
5
8
62.5%

src/Cardano/Wallet/Kernel/Restore.hs
0
8
0.0%

src/Cardano/Wallet/Kernel/PrefilterTx.hs
34
45
75.56%

Files with Coverage Reduction
New Missed Lines
%

src/Cardano/Wallet/Kernel/CoinSelection/Generic.hs
1
60.28%

src/Cardano/Wallet/Kernel/PrefilterTx.hs
1
83.77%

src/Cardano/Wallet/API/Request/Sort.hs
2
10.29%

src/Cardano/Wallet/Kernel/DB/Spec/Pending.hs
3
83.33%

src/Cardano/Wallet/API/Request/Filter.hs
3
36.89%

src/Cardano/Wallet/WalletLayer/Kernel/Wallets.hs
22
38.89%

Totals

Change from base Build 58:
0.2%

Covered Lines:
4034

Relevant Lines:
8039

💛  - Coveralls


river/mode: new module

This module shows river's current mapping mode (e.g. normal, locked).
ref https://github.com/riverwm/river/pull/614

Thanks!
Can you update the github wiki?

Can you update the github wiki?

Sure, done.


The application “Visual Studio Code.app” can’t be opened.

While this may seem like a duplicate to https://github.com/Microsoft/vscode/issues/21230, I am having the same issue and it is not a company policy problem or Archive Utility. I was able to download and install perfectly on another machine.

VSCode Version: 1.24
OS Version: OSX 10.11.6

Steps to Reproduce:

Downloaded latest version of VS Code

Replaced App in Applications folder

Tried opening the App and got this message

I have restarted my machine

re-downloaded

Deleted the App from Applications

gone through steps to remove CODE from Application Support, as well as any other files I could find like .vscode

re-downloaded and tried the Insiders Build.

Console Output
6/8/18 10:56:24.067 AM Finder[1011]: spawn_via_launchd() failed, errno=111 label=[0x0-0x55055].com.microsoft.VSCode path=/Users/<username>/Desktop/Visual Studio Code.app/Contents/MacOS/Electron flags=1 : LaunchApplicationClient.cp #963 LaunchApplicationWithSpawnViaLaunchD() q=com.apple.root.default-qos

6/8/18 10:56:24.067 AM Finder[1011]: spawn_via_launchd() failed, errno=111 label=[0x0-0x55055].com.microsoft.VSCode path=/Users/<username>/Desktop/Visual Studio Code.app/Contents/MacOS/Electron flags=1

If you run it directly in the Terminal, what's the full output? E.g:
/Users/<username>/Desktop/Visual Studio Code.app/Contents/MacOS/Electron

Did you try running it in the Terminal?

I doesn't do anything. I get the popup and the command finishes.

Ok. I deleted the app. Downloaded it again, for the nth time, opened it from the terminal (iTerm2) and it worked....

I clicked "Open" and a new terminal (Terminal) window opened along with the Application.

Not sure why it worked this time, but it did. Hopefully this helps someone else out in the future.
Thanks for your assistance.


nameusage search gives usages with datasetKey that is not found in taxon info

This search gives two usages
https://api.catalogueoflife.org/nameusage/search?datasetKey=2083&facet=datasetKey&facet=rank&facet=issue&facet=status&facet=nomStatus&facet=nameType&facet=field&facet=authorship&facet=authorshipYear&facet=extinct&facet=environment&facet=origin&limit=50&offset=0&q=Cortinarius&rank=genus&sortBy=taxonomic
Trying to get taxon info for a usage says "Dataset 2083 does not exist"
https://api.catalogueoflife.org/dataset/2083/taxon/5f1b8978-f0d5-4443-92d3-3b9ffc715e37/info

Weitd. The usage returns, its driven by the db.
https://api.catalogueoflife.org/dataset/2083/taxon/5f1b8978-f0d5-4443-92d3-3b9ffc715e37


iberopuebla.txt

Adding Ibero Puebla

http://www.iberopuebla.mx/

@RodrigoIbarraSanchez
$ host -t mx ibero_puebla.mx
Host ibero_puebla.mx not found: 3(NXDOMAIN)

If you wish to add iberopuebla.mx domain, the file path for it has to be /lib/domains/mx/iberopuebla.txt. Please note that .txt extension is mandatory.
Please rename the file accordingly, if my guess about what do you wish to add is right. Thank you!

Hello! Thanks for your reply! I have changed the name of the file to iberopuebla.txt. Greetings! 👍

@RodrigoIbarraSanchez No, you changed just the title of the request. Please change the FILE PATH in the request. You can create a new request, if it is a problem for you to change the file path. Thank you!

@RodrigoIbarraSanchez I am closing this request because the issue is resolved as a request #2303. Thank you!


Fix: migrations being generated when settings are altered

Versions:
$ pip freeze
...
Django==3.2.11
djangorestframework==3.13.1
django-rest-durin==1.1.0
...

There are two settings changes which can generate new migrations inside the installed durin files currently.
The first one is when you change the DEFAULT_AUTO_FIELD setting in django to something other than models.BigAutoField, it can be detected by django as a change in the durin provided models, which can lead to migrations being generated for durin models.
This happens since durin does not explicitly provide an AppConfig class with the default_auto_field property set. See this SO question for another explanation of the problem.
The second is when you change one of the values which is directly referenced in one of the fields default argument (Client.token_ttl field with DEFAULT_TOKEN_TTL). If you change the value of these settings, it's interpreted as a change in the value of the argument, and it generates a migration.
This one can be fixed by changing the arg to reference a function which reads the setting at run time.
Example migration generated inside the durin migrations directory when you change some of this settings:
settings.py:

from datetime import timedelta

DEFAULT_AUTO_FIELD = "django.db.models.AutoField"

REST_DURIN = {
    "DEFAULT_TOKEN_TTL": timedelta(hours=6),
}

# Generated by Django 3.2.11 on 2022-11-25 18:02

import datetime
from django.db import migrations, models

class Migration(migrations.Migration):

    dependencies = [
        ('durin', '0002_client_throttlerate'),
    ]

    operations = [
        migrations.AlterField(
            model_name='authtoken',
            name='id',
            field=models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='client',
            name='id',
            field=models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='client',
            name='token_ttl',
            field=models.DurationField(default=datetime.timedelta(seconds=21600), help_text='\n            Token Time To Live (TTL) in timedelta. Format: DAYS HH:MM:SS.\n            ', verbose_name='Token Time To Live (TTL)'),
        ),
    ]

Thamls for this! The tests will pass in master as the CI file has been fixed.


Delete empty subnetworks if they are empty after deleting an IED

Describe the bug
When deleting an IED via the IED editor, if the IED has SubNetworks which only existed in this IED, then these are left behind and result in an empty SubNetwork.
This is schema invalid if I understand correctly, a SubNetwork must have at least one AccessPoint in it:

This can be replicated using the attached file. It has a single IED with multiple SubNetworks. If the IED is deleted then the SubNetworks are empty but still exist without any ConnectAP elements.
Schema_Valid_B30.scd.zip
This doesn't seem to happen if the IED has a single access point where the behaviour is correct.
I have not looked in detail. I should not be surprised if this is related to the ServerAt directive.
Expected behavior
OpenSCD should strive to keep files schema compliant. The user should not worry about this where possible.
OpenSCD should check if SubNetworks have become empty as a result of the deletion event and delete any new empty SubNetworks.
I think OpenSCD does do this correctly where a device is only present in one SubNetwork.

When you start a new project, if will always start with an invalid schema. Removing a subnetwork because it is empty is not my proference. If the subnetwork needs to be reused for other IED's, if would nice if it can stay.
What we can do is ask the user if he likes to remove the subnetwork as well.

As discussed today 7 November 2022; In de long run, it would be nice if the user gets an option to fix invalid files. For now, we keep it as it is. It is not a big issue for now.


Built-in support for Index metadata

Index metadata should be treated specially.

If one or more documents in a module result set have an Index value, the engine should sort all result documents based on their Index values
The OrderDocuments module and all other modules that produce ordered results should simply clone and set the Index value and let the engine do the actual ordering

This will ensure the set keeps the ordering after other modules, including third-party ones

The AsOrdered call being used in base modules for parallel operations can be removed since the documents will get ordered by the engine so preserving order during parallel operations isn’t important

This was kind of a silly idea in retrospect. Given that the new base module types now preserve ordering for both sequential and parallel operations, it should be up to the modules to make sure they don't reorder inputs whenever possible.


test: migrate clean to snapbox

Part of #14039, migrating tests/testsuite/clean.rs to snapbox.

Thanks a lot!
@bors r+

:pushpin: Commit 1794ce42f43c040eabd6d83928080e2f3d105988 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 1794ce42f43c040eabd6d83928080e2f3d105988 with merge c81c32bf2a891b2e4a71442eaac59926173f5866...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing c81c32bf2a891b2e4a71442eaac59926173f5866 to master...


To show the test points list which can be selected by users.

The list data: link
We need to name for every point to describe the position in SWJTU XiPu Zone. It is amazing for users. 😉😉😉
Just be in Chinese.
e.g
103.985729, 30.771025 ~> 北区奇味干锅旁丁字路口

You can get the real address position by Baidu Mapping Tools: Position Get

You can get the name of points from application data.
(Android devices) Database file: /data/data/com.zjwh.android_wh_physicalfitness/database/sport
->Table:runPoint
Col"desc" are names, "lat"&"lon" are coordinates.

llz fix it! thx!


Clone of korels repository

Signed-off-by: Korel Ucpinar<EMAIL_ADDRESS>

@KorelU  can you please fix DCO error and add description to your commits

Closed pull request because DCO error and comment descriptions were added by Royal

@KorelU can you please fix DCO error and add description to your commits

Should now be Addressed

As a point of note Taras, the changes you recommended to Royal in the previous PR he will be implementing in the following pull request which covers his contributions.


Callback conversion fix for older devices

One some older devices (guessing some 32bit androids) Dart callback does not come in form of a Long but is instead converted to another type (guessing an Int), causing the Kotlin code to break since .toLong() needs to be called and "as Long" does not work.
This PR fixed the upper issue.
Please review and merge.

@Yukams Can we get this PR reviewed, merged and pushed to pub.dev?

@Yukams @Haris2v Any update on this? Sorry to push, I'm looking to using this plugin from upstream as soon as possible. Thanks for taking a look.


Allow static definition of server in agent config

This cookbook appears to assume that there would be only one Go server. If more than one server is found in the search, then it uses the first one found. If I want to allocate a go cd cluster per team, this would be problematic.
Perhaps provide an attribute called node['gocd']['server'] and set to nil, consequently allowing users to set this value. If they don't, then have logic that falls back on existing search logic.

This is not entirely true.
This cookbook does not support provisioning multiple servers - you'll have to setup those differently.
But agents LWRP can have go server host and port specified.
I believe the attribute you would want to have is node['gocd']['agent']['go_server_host'] here
But anyway you don't need an attribute in gocd cookbook. Instead I would recommend using go_agent lwrp like this
gocd_agent 'my-go-agent' do
  go_server_host node[:wrapper_cookbook][:go_server]
  go_server_port 80
  ...
end

@miroswan Let me know if this fits your use case.

This looks good. I was actually looking at master which looked a little different.


node bot.js does not work after reviewing all issues from the past 4 months

I have an auth.json with token, a bot.js, a package.json, Git installed, discord.js, winston, and that woor/discord.io#gateway_v6 one. When I say "node bot.js" without quotes, this appears

Am I missing something obvious?

Same, please someone answer

i have the exact same problem, anyone able to help?

Are you running the command in the same directory where the bot.js file is in? Use "dir" command to check if you see bot.js in the directory.


Symbol class

There should be a Napi::Symbol class, implemented with napi_create_symbol(). And probably also a Napi::Name class that is a common base class for Symbol and String, because there are several APIs that can accept either a string or symbol.

#16? ;) I might be able to do this over the weekend.

Oops closing as duplicate of #16


updated memory from 64m to 63#

updated memory from 64m to 63# justinzyw/ui-toolchain-demo-1482143938691#2

looks good to me


how to add email sender credentials in opensearch-keystore which is hosted on kubernetes?

./bin/opensearch-keystore add plugins.alerting.destination.email.<sender_name>.username ./bin/opensearch-keystore add plugins.alerting.destination.email.<sender_name>.password,
These are the commands mentioned in documentation to add alerting notifications, at run time we can get inside a container and we can add them. But how to add it in configuration of opensearch?

[Triage]
Hey @chasegame-alpha there is a keystore setting for the chart, but I do see this is little tricy as it does not contain the key value pair, @TheAlgo @DandyDeveloper @smlx @PaulLesur can you please add an example here?
@bbarani @rishabh6788

[Triage] Hi @opensearch-project/alerting-plugin , @opensearch-project/notifications Can you look into this issue?

I see an example in the values.yml from the code directory that @prudhvigodithi linked above:
https://github.com/opensearch-project/helm-charts/blob/af9e379b18b5cdc1f72c51fba376bab29753d9c9/charts/opensearch/values.yaml#L419-L421
Looks like it supports the key value pair to me

@Flyingliuhub  I guess we have done this for datasources config. can you help here?

you can create a key value pair secrets for Kubernetes based on the json file or individual value, please see sample below:
kubectl create secret generic opensearch-dashboards-sample --from-file=plugins.query.federation.datasources.config=input.json
and then use those secretName in your opensearch.yaml file's keystore.
keystore:
  - secretName: opensearch-dashboards-sample

hey @Flyingliuhub   @prudhvigodithi @qreshi @gaiksaya @vamsi-amazon
hello all, thanks for responding to the issue. But even after adding them as secrets, and adding the secret to the keystore, but that didnt worked for me.
how to add to the keystore(credentials)  opensearch nodes running in kubernetes (pods), and how to add them to each node without restarting the deployments.
Even after adding to the keystore how can we update(credentials) them without restarting the deployments.
is there any REST call to do all this for opensearch?
thankyou.

If the keystore settings were added after OpenSearch has come up, you can call the reload API to have the credentials changes reflected in Alerting without restarting. The credentials do need to be added to the keystore per node but the API will refresh all nodes.
Also, if you are using OpenSearch 2.0 or greater, I recommend using the updated setting for Notifications keystore settings:
opensearch.notifications.core.email.<sender_name>.username
opensearch.notifications.core.email.<sender_name>.password

The legacy ones you've mentioned above will still work in 2.x but will be removed in 3.0. Using the new namespace now will allow you to avoid the sudden migration on upgrading to 3.0 in the future. It seems the documentation isn't reflecting the newer setting. I'll ask the team to update the documentation.

@qreshi
hello qureshi, thanks for replying to the issue. Where can i find the updated setting for Notifications Keystore settings, in deployment files, as we are following with helm deployment. I am not able to add the keystore settings and configure email to send alerts.
where can i add these two settings for the pods deployed in kubernetes with helm installation.
opensearch.notifications.core.email.<sender_name>.username
opensearch.notifications.core.email.<sender_name>.password
Thankyou.

I followed these steps to add SMTP credentials to Helm with a keystore:

Create the secrets in k8s:

kubectl create secret generic -n <my_np> notifications-core-mail --from-literal=opensearch.notifications.core.email.<sender_name>.username=<my_email_account>
kubectl create secret generic -n <my_np> notifications-core-password --from-literal=opensearch.notifications.core.email.<sender_name>.password=<my_password>

In helm, add these new secrets:

keystore:
  - secretName: notifications-core-password
  - secretName: notifications-core-mail

Upgrade the Helm configuration.

To check if the secret is added to the keystore, run the following command:

kubectl exec -it -n <my_np>  <my_pod_name> -- /bin/bash
opensearch-keystore list

adding to @danielcastropalomares, you can add the secrets to the extraObjects object in values.yaml like this:
extraObjects:
  - apiVersion: v1
    data:extraObjects:
  - apiVersion: v1
    data:
      opensearch.notifications.core.email.<sender_name>.username: <username_base64_encoded>
    kind: Secret
    metadata:
      name: notifications-core-email
      namespace: opensearch
  - apiVersion: v1
    data:
      opensearch.notifications.core.email.<sender_name>.password: <password_base64_encoded>
    kind: Secret
    metadata:
      name: notifications-core-password
      namespace: opensearch
      opensearch.notifications.core.email.<sender_name>.username: <username_base64_encoded>
    kind: Secret
    metadata:
      name: notifications-core-email
      namespace: opensearch
  - apiVersion: v1
    data:
      opensearch.notifications.core.email.<sender_name>.password: <password_base64_encoded>
    kind: Secret
    metadata:
      name: notifications-core-password
      namespace: opensearch

Then, reference the secrets added in the keystore object in the values.yaml:
keystore:
  - secretName: notifications-core-email
  - secretName: notifications-core-password


Reduce ModPacket header size

ModPacket uses 5 bytes of network overhead
1 byte for Terraria's id 250
2 bytes for netId
2 bytes for length (safety tradeoff)
we can reduce the netId to one byte if the user has less than 255 mods, and we can use a 7bit encoded int for length as most packets are small
This puts the header for small packets at 3 bytes

As much as I'd like to use a 7bit encoded int for length, that would be quite an intrusive change to Terraria's packet system, since length is handled at the top level, so alas, it's 4 bytes overhead 751650af599a3c1d57a16394d472a26ac8f8abbd


TypeError: XMLHttpRequest is not a function

No matter how I try I'm unable to use the web3.eth or even the instantiated contract["eth"] in any way that reaches out via XMLHttpRequest
Hash: 09f3e4cee5c2c24ee28e
Version: webpack 1.13.0
Time: 6183ms
    Asset    Size  Chunks             Chunk Names
bundle.js  502 kB       0  [emitted]  main
   [0] multi main 28 bytes {0} [built]
    + 88 hidden modules
C:\repo\ethereum-webpack-example-dapp\bundle.js:16073
            var request = new XMLHttpRequest();
                          ^

TypeError: XMLHttpRequest is not a function

import { tokenRecipient, MyToken, web3 } from '.\\MyToken.sol';
let currentBlock = web3.eth.blockNumber;
console.log(currentBlock);

@genecyber Do you have the full code or package somewhere where this error can be reproduced?

So I forgot to mention I'm running this outside of a browser.
First I cloned the ethereum-webpack-example-dapp
npm install
npm start
verified that the bundle worked in the browser (It worked)
I then commented out the window bits and re ran npm start
/**
 * Individual contracts are available instantiated
 * Also avaialble is initialized web3 object
 */
import { tokenRecipient, MyToken, web3 } from './contract/MyToken.sol';

/*window.onload = () => {
  renderWeb3Details();
  renderTokenDetails();
};

function renderWeb3Details() {
  document.getElementById('provider').innerHTML = web3.currentProvider.host;
  document.getElementById('latest-block').innerHTML = web3.eth.blockNumber;

  const accounts = web3.eth.accounts;
  let html = '';
  for (let account of web3.eth.accounts) {
    html += `${account}<br>\n`;
  }
  document.getElementById('list-accounts').innerHTML = html;
}

function renderTokenDetails() {
  document.getElementById('token-name').innerHTML = MyToken.name();
  document.getElementById('token-symbol').innerHTML = MyToken.symbol();
  document.getElementById('total-supply').innerHTML = MyToken.totalSupply();
  document.getElementById('version').innerHTML = MyToken.version();
}*/
console.log(web3.eth.blockNumber)
console.log(web3);
console.log(MyToken);
console.log(tokenRecipient);

I also added
console.log(web3.eth.blockNumber)

upon successful webpaking I ran node bundle.js and got this error
 node bundle.js
C:\repo\ethereum-webpack-example-dapp\bundle.js:16072
            var request = new XMLHttpRequest();
                          ^

TypeError: XMLHttpRequest is not a function
    at HttpProvider.prepareRequest (C:\repo\ethereum-webpack-example-dapp\bundle.js:16072:20)
    at HttpProvider.send (C:\repo\ethereum-webpack-example-dapp\bundle.js:16086:25)
    at RequestManager.send (C:\repo\ethereum-webpack-example-dapp\bundle.js:338:33)
    at Eth.get [as blockNumber] (C:\repo\ethereum-webpack-example-dapp\bundle.js:12252:63)
    at Object.<anonymous> (C:\repo\ethereum-webpack-example-dapp\bundle.js:81:31)
    at __webpack_require__ (C:\repo\ethereum-webpack-example-dapp\bundle.js:20:30)
    at Object.<anonymous> (C:\repo\ethereum-webpack-example-dapp\bundle.js:47:19)
    at __webpack_require__ (C:\repo\ethereum-webpack-example-dapp\bundle.js:20:30)
    at C:\repo\ethereum-webpack-example-dapp\bundle.js:40:18
    at Object.<anonymous> (C:\repo\ethereum-webpack-example-dapp\bundle.js:43:10)

Also noteworthy I'm on windows 10

@genecyber You'll have to add target: 'node' to webpack.config.js so that the code will run in non-browser mode.

Thanks much that fixed it.

I m facing  this error
> web3.setProvider(new web3.providers.HttpProvider('http://localhost:8545'));
undefined
> var coinbase = web3.eth.coinbase;
TypeError: 'XMLHttpRequest' is not a function
    at web3.js:4241:21
    at web3.js:4257:19
    at web3.js:6188:18
    at get (web3.js:6091:38)
    at <unknown>


Tried to run Main.py & ended with error

Please help on this.
Tried to run Main.py & ended with error
from models.hft_model import HFTModel
File "C:\Users\Raji\Downloads\High-Frequency-Trading-Model-with-IB-master\models\hft_model.py", line 378
except Exception, e:
^
SyntaxError: invalid syntax

This code is in python 2 syntax. Are you running on python 3?


error while evaluating conditional: ansible_distribution_version

I get this failure when building on a ubuntu trusty host:
PLAY [dockerubuntu] ***********************************************************

GATHERING FACTS ***************************************************************
ok: [localhost]

TASK: [angstwad.docker_ubuntu | Fail if not a new release of Ubuntu] **********
fatal: [localhost] => error while evaluating conditional: ansible_distribution_version|version_compare(12.04, '<') or ansible_distribution_version|version_compare(12.10, '=')

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/root/docker.yaml.retry

localhost                  : ok=1    changed=0    unreachable=1    failed=0

ansible -m setup localhost full output here:
http://sprunge.us/SRKH
with the relevant section here:
        "ansible_distribution": "Ubuntu",
        "ansible_distribution_release": "trusty",
        "ansible_distribution_version": "14.04",

the execution line:
  virtualbox-iso: Executing Ansible: cd /tmp/packer-provisioner-ansible-local && ANSIBLE_FORCE_COLOR=1 PYTHONUNBUFFERED=1 ansible-playbook /tmp/packer-provisioner-ansible-local/docker.yaml --limit localhost -c local -i /tmp/packer-provisioner-ansible-local/hosts

repo with packer build that is my exact setup on how I got this error:
https://github.com/joshuacox/dacksible
anyone should be able to cd into the packer directory and make vbox to get the exact error as above.  Given that you have virtual box, vagrant, and packer installed amongst any other dependencies I'm forgetting.
I'm sure I'm doing something wrong as I'm still abit new to Ansible, but if anyone can shed some light on why this is failing I'd love to figure it out.

Is your ansible version below 1.6?

well locally:
> ansible --version                                                                                ~/git/dacksible/packer(master)@stealth
ansible 1.8.4
  configured module search path = /usr/share/ansible

But the error is from the one packer is using:
https://www.packer.io/docs/provisioners/ansible-local.html
which I imagine is pretty new, but I'll rebuild the machine again in debug mode and get a ansible --version from it

That's gotta be the issue.  You're missing the version_compare remotely in the packer VM.

ok, so you guys nailed it. the version was 1.5.4, and packer may be controlling it, but it's the ansible inside the VM actually doing the work so I guess trusty is too old already, changing my install procedure from:
#/bin/sh
apt-get update
apt-get install -y sudo ansible python-apt python-pycurl python-pip python-virtualenv

to:
#/bin/sh
apt-get install software-properties-common
apt-add-repository ppa:ansible/ansible
apt-get update
apt-get install -y sudo ansible python-apt python-pycurl python-pip python-virtualenv

that should get me a newer ansible and clear this up.

Glad to hear it that was the issue.  Hit us up if you encounter more stuff.  :smile:


Authenticate the URL in pool metadata

It's currently very easy to impersonate another pool, and fraud stakers. Here are proposed solutions for it:

Check the website DNS for a TXT record with the pool id in it. Only show the pool in Daedalus if the pool id is present in the metadata URLs TXT record. This way, a delegator simply has to verify that the URL is correct.

Check if the pool metadata file is hosted on the domain that i listed in the metadata. If the pool metadata json file is not hosted on the domain listed in the metadata, the pool should not be shown in Daedalus. This way, a delegator simply has to verify that the URL is correct.

This should work with previous submission already on the backlog ref https://github.com/input-output-hk/cardano-node/issues/1354)

@dcoutts has this been implemented on the cardano-node side?


No hint that postDebugTask doesn't exist

re #45305

configure a post debug task that doesn't exist (mistype the name)
debug till termintation
🐛 there is no hint that the post debug task didn't work (while we have something very prominent for pre debug task)

This is a fair request, assigning to April to tackle then.

@why are you reporting a missing "preLaunchTask" differently (modal) than a "postDebugTask" (non-modal)?

Because I felt like the postDebugTask is not something that is blocking. Your debug session start depends on preDebugTask, but nothing depends on postDebugTask. I can change it for consistency if you prefer that.

That explanation makes sense to me.


Skip Rush Audit for iTwinjs-Core and Docs PR Validations

Skip this step to avoid unnecessary blockage for users.

The reason that ecpresentation tests take too much time (around more than 20 hours) is that we have around 2500 tests in this part and each test is executed 6 times. In total it becomes 15000. Also the comparison and symbols also take large amount of time.


Add a publishing profile view is not in the same navigation concept

Is your feature request related to a problem? Please describe.
"Create new resources" and "Hand off to admin" view has a back button but "Import existing resources" back button is missing
https://user-images.githubusercontent.com/16264167/115420680-a14d6800-a1fb-11eb-8725-131d402213fc.mp4
"Import existing resources" view also add the back button.
Describe alternatives you've considered

Additional context

@cwhitten not sure this is bug or feature request.

@Dewain27 FYI

Getting resolved in next release.


Add gif: flag to all image commands

Describe the request
Add a gif:true/false flag to image editing commands to convert the image to a gif in one step to edit images and make them saveable in one step
Is your feature request related to a problem? Please describe.
No response
Additional context
No response

Added in 10b80f2, should be on the main bot by the end of the month


Add option to allow Select interaction logic to select overlapping features

The original default behaviour of the Select interaction is to "Replace the currently selected feature(s) with the feature at the pixel". I made this code change to change the semantics to "Replace the currently selected feature(s) with the feature(s) at the pixel". I could not find a way to configure to get the desired behaviour with add/remove/toggle conditions).
This PR is a proposal with some unanswered questions. The "no change" condition was and is at fault since it only compares the first of the current selected features. I'm prepared to rework the PR if the questions can be resolved.
What is a sensible default behaviour?
Should the default behaviour be configurable?

Anyone wants to review this for 3.2? I'll move it to v3.3.0 if not reviewed by tomorrow Wednesday.

Thanks for the review @fredj, I've fixed those and squashed to a single commit. Travis CI build fails and I can get the same error locally but I don't understand what it means or how it can be related to my branch.

Thanks @gberaudo, don't know why I missed that. Fixed with updated squashed commit.

Thanks @fredj, fixed missing curly brace, and that seem to have made Travis happy. Will try to avoid similar typos in the future.

LVGTM, thanks @bjornharrtell

It looks like this introduced a regression in behavior.  See #3218 (and a mailing list issue which may or may not be related).

The intention was to keep the existing behaviour and I when looking at the changes I don't understand what is causing the regression. The feature that gets selected should be the last one returned by forEachFeatureAtPixel both before and after this change.

In the previous implementation, the first feature was returned by map.forEachFeatureAtPixel not the last (i just figured it out now).
The reason is that if something "truthy" is returned by the function the loop stops.
See #3221 for a fix


Location StreamController doesn't fire data

Hi, I'm trying to listen to onLocationChanged stream in GpsPlugin class but it never initialize correctly, so, it doesn't add positions when user change location. I've seen that in the initialize method, this line never comes true:
if (_locationSubscription == null && _overriddenLocation == null)
cause _locationSubscription is always != null.
Please can you check it? Or if maybe I'm missing something?. Thanks in advance.

Ah ha.  Yep, I totally inverted that logic.  Should have been if (_overriddenLocation == null) { ... }.  Just fixed with a push tonight on v1.0.1.
Let me know if this solves your issue.


file upload using createFromUrl does not work or hangs

We're using the @datocms/cma-client-node package with the createFromUrl function to upload images from a url.
If we run our code locally the execution hangs on the createFromUrl invocation.
After this log statement it just hangs:
[2] x-api-version: 3
[2] x-environment: primary-...
[2] x-queue-time: 0ms
[2] x-ratelimit-remaining: 58
[2] x-request-id: acb5f46f-f607-483e-80e6-9e9b06dd7dbd
[2] cf-ray: 81ca8bf6888ef96d-BRU
[2] {
  "data": {
    "id": "/61856/1698405594-image.jpg",
    "type": "upload_request",
    "attributes": {
      "url": "https://datosrl-images.s3.eu-west-1.amazonaws.com/61856/1698405594-image.jpg......"
    }
  }
}

Mh, our tests are green both on Node 16 and 18, and they cover this scenario.
Can you share a minimal script reproducing the issue? Did you upgrade to the latest package? What is the Node and npm version? Can you share your package-lock.json?


Add input-profile component

add input-profile.js component and update it on index.js for bundling

Since this is a new component, it would be nice to also make it a TypeScript component directly, so we don't need to convert it later

A profile often contains both left and right, it could make sense to cache them in a static variable on the InputProfile component to avoid re-downloading and parsing the same json for both hands

Two tiny comments and LGTM :)


Crash with Optifine and Optifabric

Origins mod in 1.17 if is opened with optifabric crashes.

Same here

I won't actively work towards compatibility with OptiFabric. However, the OptiFabric devs seem to be enjoying fixing the messes I make, so you might see them fixing compatibility again in the future.


test against ruby 2.4.2

Hey @stadelmanma
I want to use sablon with ruby 2.4.2, so let's also test against that now.

@siegy22 good call on adding 2.4 to the test suite, I've been using it for awhile now but forgot to add it to Travis CI. I don't think we need to pin the ruby version down to be patch specific judging by the example in the Travis docs and if not I'd rather relax that constraint since I can't think of a good reason to pin things back unnecessarily.
Since were already modifying the CI config would you mind to go ahead and update the rvm section to look like this?
rvm:
  - 2.1
  - 2.2
  - 2.3
  - 2.4

After that I'll go ahead and merge this.

@stadelmanma done :+1:

@siegy22 Thanks!  :+1:


Report git's output when git fails

Fixes #124

Codecov Report

Merging #125 into master will decrease coverage by 0.58%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
- Coverage   93.25%   92.67%   -0.59%
==========================================
  Files          15       15
  Lines         623      628       +5
  Branches       61       61
==========================================
+ Hits          581      582       +1
- Misses         26       30       +4
  Partials       16       16

Impacted Files
Coverage Δ

src/towncrier/check.py
85.1% <42.85%> (-7.76%)
:arrow_down:

Continue to review full report at Codecov.

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

@exarkun could you merge this forward? I'm assuming that the create_project change would work in the other tests?

@hawkowl Done


Adapt for Qtum

This PR adapts rust-bech32 crate to work with Qtum bech32 format.

Sorry, wrong repo.

It looks like whatever you're doing here is changing the set of standard HRP types and nothing else. You should be able to do this by just depending on this library, creating your own KnownHrp type with conversions to Hrp, and then using the existing functionality. There should be no need to fork the whole library.
At most you may need to fork/duplicate the segwit module. But the rest is designed so that if you are using a BCH code (even a non-bech32 one!) that uses the bech32 alphabet, everything should Just Work no matter how much stuff you change.
I don't think we'll be able to directly help you much because your project looks like it's technically and morally out of scope for rust-bitcoin, but hopefully this hint will let you avoid a repo fork and possibly allow us to share a bit of development energy.

Sorry again, I accidentally pushed the PR into Bitcoin rust-bech32 repo instead of Qtum one which I am working on at moment.
I also don't like the idea of forking the whole lib just to change some constants, but considered it as the easiest approach. Thank you very much for giving a direction to look into.


add github links to public npm packages

For the sake of completeness, let's do them all.

@TimoGlastra thank you for this PR!


Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstTcamBin:tcambin0/GstTcamSrc:tcambin-source: Internal data flow error.
Additional debug info:
gstbasesrc.c(2948): gst_base_src_loop (): /GstPipeline:pipeline0/GstTcamBin:tcambin0/GstTcamSrc:tcambin-source:
streaming task paused, reason not-negotiated (-4)
Execution ended after 0:00:07.759286915
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
please help me.
on ubuntu 16.04 nvidia Tx1,Linux version 4.4.38-tegra,with camera DFK 72BUC02

Hello
please use "ximagesink" instead of "autovideosink".
Also please please let me know

camera model
Linux distribution
computer model

Stefan

Hello
I would like you to try smaller video formats too:
gst-launch-1.0 tcambin  ! video/x-raw, format=BGRA,width=640,height=480,framerate=15/1 ! videoconvert ! ximagesink
And see. what happens.


[escrow-dashboard] update network selector on escrow-dashboard

Description
Implemented network select dropdown on escrow-dashboard.
Summary of changes
Removed the previous tab selector, and implemented dropdown selector for multiple chains.
Here's Figma link - https://www.figma.com/file/u81GKebVavmQW8zGHb5Jgo/Dashboards---Everything-Apps?type=design&node-id=1394-21680&t=7AGG1hoatTJAXwCa-0

Total supply is duplicated, one in network section and another in token section. Also, in mainnets this data in network section is disabled

Yes, it's fine, already discussed with @ansaqib  before.


Exception when hosting in rexster-server-2.6.0 not able to load com.thinkaurelius.titan.tinkerpop.rexster.TitanGraphConfiguration

Have setup rexster-server-2.6.0 and pointed to a Titan 1.0.0-Hadoop 1 instance that runs on a hbase 2 node cluster backend.
I am able to access the graph using titan gremlin shell as well as able to perform graph functions but rexster server is not able to load the graph.
I have copied the jar from lib of titan to the ext folder titan as instructed in
http://s3.thinkaurelius.com/docs/titan/current/server.html
Section 7.2.2. Downloading Rexster and Titan separately
Can anyone let me know which jar this file is present under? In the previous version the class
com.thinkaurelius.titan.tinkerpop.rexster.TitanGraphConfiguration is present under the jar titan-rexster-0.4.4.jar
as discussed under
https://groups.google.com/forum/#!msg/aureliusgraphs/SxMW2ae72-0/YV5AggnBsTwJ

Seems this dependency is indeed missed in the distributable for 1.0.0-Hadoop 1. I took the 0.5.4 version of  titan-rexster-0.5.4.jar and dropped it under titan and this started working
http://search.maven.org/#search|ga|1|fc%3Acom.thinkaurelius.titan.tinkerpop.rexster.TitanGraphConfiguration

Is the titan-rexster-0.5.4.jar the right one to use can it connect to the new version of the graph Titan 1.0.0-Hadoop 1

Just realized that titan-rexster is being replace with Gremlin Server and Titan 1.0.0 Hadoop1 is waiting for the actual release which is currently under incubation.
http://tinkerpop.incubator.apache.org/

Just to be clear, TinkerPop released 3.0.0 months ago.  Titan 1.0 ships with Gremlin Server.

@antonpious , what should I put under titan folder ?
I couldn't understand your last comment. Can you please explain a bit ?


merge from arlac77/template-github-action,arlac77/template-kronos-component

package.json

chore(deps): add ^3.11.0 remove ^3.10.1 (devDependencies.ava)

Codecov Report

Merging #991 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #991   +/-   ##
=======================================
  Coverage   91.99%   91.99%
=======================================
  Files          10       10
  Lines        1474     1474
  Branches      168      168
=======================================
  Hits         1356     1356
  Misses        118      118

Continue to review full report at Codecov.

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


Shader failure on Mali GPU

I'm certain this is a GPU driver bug that is merely exposed by Filament, but I wanted to steal 10 seconds of your attention in case you've seen anything like it before. Feel free to close this as "not our problem".
If I take the lit cube demo project and make it split-screen, with two cameras and two views side-by-side, I get a curious problem on my RK3288 with a Mali-T760 GPU (driver versions 11 or 14) as shown in this video. Basically the first view that gets rendered (the left) has all black pixels. My Pixel 1 shows both cubes fine and the Intel-based device shown on the right in the video also works perfectly.
I think I've narrowed it down to a silent crash in the fragment shader whenever it tries to read FrameUniforms or LightsUniforms. For example, a shader that should just draw red or green depending on the value of frameUniforms.time will draw black. If I extend to four cameras and four views, only the last one is drawn and the first three are all black.
I suspect that during the various uniform buffer allocations some sort of synchronization guarantee is not being honoured by the driver and previous allocations become corrupt. I'm trying to make the simplest reproduce possible independent of Filament, but in the meantime I wondered if anyone has seen anything like it before?

Thank you. This looks very similar to an issue we've had in the past on Mali GPUs. We have a workaround but it may just not be enabled for your particular variant of Mali. @pixelflinger is checking what the workaround is right now.

We ran in a problem that looks very similar on Mali GPU before. It affected only the Mali-T series.
The workaround we found at the time was to disable "early fragment test" in the shaders. It had something to do with optimizations in the compiler.
However, since then, we have removed that feature (early_fragment_tests) from all our shaders because we ran into other problems. So, the workaround for Mali-T became obsolete. It looks like you found a new way to trigger this problem :-\

Do you have a suitable target device for testing? I can attach the repo project if it would help. Either way I can try and confirm the issue here.

Here's the modified version of sample file /filament/android/samples/lit-cube/app/src/main/java/com/google/android/filament/litcube/MainActivity.kt
Note that the problem is only present when isPostProcessingEnabled is false. There is a known issue with the depth buffer not being allocated in this state and coupled with what @pixelflinger said about the early_fragment_tests it's possible that the GPU is bug is depth related.
Obviously I would prefer to always run with post-processing enabled, but the Mali GPU is just too slow.

I believe I have narrowed it down now and I finally have a
small repo project that is independent of Filament.
The problem is buffer related and occurs only when several buffers are mapped to uniforms. The problem appears to go away if you don't call glFlush() until the very end of the draw cycle.
I'll post the repo project to ARM for comment and for now I've just removed the call to glFlush() in the OpenGL driver in my local copy of Filament. Opinions are welcome on whether this is safe and/or if I should still flush after all render calls are complete (perhaps in endFrame).

Thank you for investigating. We use flushes to kick off GPU tasks as early as possible to maximize concurrent work, but it's not necessary. That could be the workaround on specific Mali GPUs.

Wow. Thank you for the repro.  I will make more tests for this as well as implement the workaround -- however, in the meantime, would you be able to try to replace the glFlush() with a glReadPixels() of just 1x1? -- this should cause a flush too --.
Also, is the viewport call needed after the flush for the problem to happen?

@pixelflinger Thanks for the quick responses to this (as always from Team Filament)
I substituted the glFlush call for this:
val pixelBuffer = ByteBuffer.allocateDirect(4).order(ByteOrder.nativeOrder())
GLES20.glReadPixels(0, 0, 1, 1, GLES20.GL_RGB, GLES20.GL_UNSIGNED_BYTE, pixelBuffer)

and the problem went away.
Removing the glViewport calls made no difference though: the first triangle was still black.
FYI: I've posted the question to ARM now.

Okay, one more thing to try -- I promise :-) What about glFinish() instead?  (glReadPIxels is going to be more similar to a glFinish() than a glFlush()).

glFinish instead of glFlush also works.

Okay great. I'm going to implement the "don't call glFlush" workaround for now. Thanks!

I've pulled those changes down and they work fine. Thanks again!


MSYS coreutils

Hey, is there a way to install MSYS coreutils? The build process I'm trying to run requires target cat (or rather cat.exe). Trying to install coreuitls I get
# make install coreutils
Makefile:440: *** Unknown package or package alias: 'coreutils'.  Stop.
Makefile:902: *** Unable to execute `make  -r __database_nodeps __database_allow_aliases PKG@@coreutils`, exit code 2.  Stop.

@lockie If you manually copy cat.exe from a Windows MSYS2 installation, is Wine able to run it? Last time I checked, executables belonging to the MSYS environment (aka from packages not prefixed with mingw-w64-) didn't work.
Currently there's no way of installing packages from the MSYS environment, but if cat.exe ends up working for you, I can add support for that.

I haven't tried the one from MSYS2; ended up replacing cat with bat instead (cat.exe from GnuWin32 was giving me weird-ass errors about input being the same as output).


Snappy Fix - Locations Component

Snappy Fix

this is more of a work-around than a "fix"

This pull request removes the locations component from the main page since it is "jumpy". I am not sure why, but when scrolling around the locations component, (only downwards) it causes the page to jump farther down like someone bumped your scroll bar. By putting the locations component on its own page, this is no longer an issue.

.deploy


Add slidingWindowSum

slidingWindow typically helps write only functions with
complexity around O(n*k), where n is the number of elements
in the stream and k is the size of the window. In many cases,
this can be reduced to O(n) by looking not at the window itself
but instead the sum of that window in some Semigroup. This can
be used, for example, to implement moving averages such as
arithmetic, geometric, or harmonic means.

A couple concerns:
My biggest concern is that for a number of purposes, the size of the window is quite important. If the stream proves to be smaller than the window, we need to know that. For example, if we're taking a moving average, and the stream comes up very short, then we'd naively end up with a total garbage result. Should we have variants that add a return value indicating something about this?
Another concern: it seems rather useful to use this with newtypes from Data.Semigroup. Mapping over the stream once to apply the newtype and again to remove it seems potentially pricy. Do we want a version that maps over its input and its output?

Yet another question: do we want a By version that lets the user provide the semigroup operation directly?

The CI failure is some GHC HEAD nonsense.

@andrewthad I know you've stepped away from this package, but I'd very much appreciate your thoughts on this one.

My biggest concern is that for a number of purposes, the size of the window is quite important. If the stream proves to be smaller than the window, we need to know that. For example, if we're taking a moving average, and the stream comes up very short, then we'd naively end up with a total garbage result. Should we have variants that add a return value indicating something about this?

Instead of a return value, perhaps members of the original stream up to the first full window could be re-yielded before starting with the windows themselves. Something like:
slidingWindow :: Monad m => Int -> Stream (Of a) m b -> Stream (Of a) m (Stream (Of (Seq a)) m b)

For cases in which there aren't enough elements to form a window, the isolated elements would be re-yielded but the stream with the window results would be empty.
Also, this way we don't need to keep whole windows in memory in order to report "incomplete" windows.

Pardon my ignorance in this area, but here are the things that confused me. This internal data structure looks a lot like a finger tree, but it differs from Patterson's finger tree:

The left digit and right digit have different size restrictions from one another.
The original finger trees have digits max out at size 4. This implementation uses 2 and 1.
The tree itself has an extra data constructor.

But I guess that's not what it's actually based on. The documentation says that this is "an implementation of Okasaki's implicit queues holding elements of some semigroup". It would be kind of nice to have a link to a reference implementation of Okasaki's implicit queues in Haskell so that someone could look at it and see how the data structure differs, but I don't know if there is a good library where this has already been done.
After figuring out what was going on with the data structure, I think this seems fine though, and it's the ideal "purely functional" solution to the problem. It's a little sad that the Semimeasurable abstraction is not exposed to the user in any way, but I think it would only be appropriate to do that if Semimeasurable were provided by a different library. I guess there's the Measured class from the fingertree library, but it's really not what you want here. It would be cool if there were a way to factor those out and unify them, but that's a complication for another way.

@andrewthad, I really just mashed up Okasaki's structure with Hinze and Paterson's and checked that it was still okay. Yes, the structures are quite closely related, with Okasaki's simpler and less flexible. Which is faster for the purpose? Dunno. It does rather feel like it belongs in Some Other Library. semimeasure is really a convenient hack, and I wouldn't want to expose it as is. Better to expose an idea like one of these for general use:
semimeasure' :: a -> Maybe s
semimeasure'' :: r -> (s -> r) -> a -> r

I just went with the bare minimum I needed here.
@danidiaz, I really don't know enough about what people need to feel like I can evaluate whether your idea is the right approach.


Not stable in position mode

We use GitHub issues only to discuss PX4 bugs and new features. For
questions about using PX4 or related components, please use PX4 Discuss.
Thanks!

In my case , in the position mode on increasing the throttle above 50 percent it stabilize for a sec and then starts increasing altitude and throttle on his own...
what could be the posssible error??

Please follow the issue template.


Update Formality to v.0.1.209

Update Formality version using dev as base.

[x] Update version and fix bugs
[x] Fix errors in test
[x] Update master
[ ] Update provit.fm

[ ] fix delay to parse a file @MaiaVictor

[x] fix delay to parse a file @MaiaVictor

Fixed by Amorim


Allow generating a changelog, starting with configured tag.

Is your feature request related to a problem? Please describe.
When creating a changelog for an existing project (not using conventional commits so far) it creates a changelog with empty sections.
Describe the solution you'd like

Allow to disable generating empty releases until the first release with content was found (might be a reasonable default)
Allow to configure the starting point manually

Describe alternatives you've considered
None.
Additional context

Good point, having a release without changelog information is not that usefull, unless one would want to manually change the resulting file. Maybe we could add a flag --skip-empty. If you use conventional commits, there should not be any empty sections, unless you configure to only show features and have a release with only fixes.

I made a pull request to skip empty releases.

Allow to configure the starting point manually
Here I don't know if it is worth to add it in config as you could use vx.y.z.. in your CI to create the changelog excluding everything  <= x.y.z

Here I don't know if it is worth to add it in config as you could use vx.y.z.. in your CI to create the changelog excluding everything <= x.y.z

That is good to know. I will try that, thanks!


Release @google-cloud/talent v0.1.0

This pull request was generated using releasetool.

@JustinBeckwith let's hammer this so our 404 doc woes disappear!

I like that you call out the fact n the README that this library uses semantic versioning ... could we ask folks to use conventional commits pretty soon too 😄

Absolutely!  Instead of asking in the README though, I want to talk about requiring it in a pre-submit check.  I want something like this:
https://probot.github.io/apps/commitlint/

Release is at https://github.com/googleapis/nodejs-talent/releases/tag/v0.1.0

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Remove pre-1.0 release warning

Sorry that this got misplaced. Since fixed by https://github.com/Polymer/lit-html/pull/952.


Pinned all dependencies

:wave: Hello!
We’re all trying to keep our software up to date, yet stable at the same time.
This is the first in a series of automatic PRs to help you achieve this goal. It pins all of the dependencies in your package.json, so you have complete control over the exact state of your software.
From now on you’ll receive PRs whenever one of your dependencies updates – in real time. This way you get all the benefits of up-to-date dependencies, while having them pinned at the same time. This means:

No more surprises because some of your dependencies didn’t follow SemVer. Your software is always in a state you know about, regardless of when someone does $ npm install.
If you have continuous integration set up for this repo, it’ll run automatically. Ideally, it will pass and you'll stay up to date with the press of a button. If the updated dependency does break your software, it won’t affect your users, because their dependencies are still pinned to the working state.
You can immediately identify which dependency updates break your software, because each one is tested in isolation. You’ll also have a branch ready to work on, so adapting to new APIs is way faster.

Merge this PR and you’ll have up-to-date software without the headaches :sparkles:

This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan!
You'll also get your pull requests faster :zap:

@jgeewax this is a robot that's going to take care of our dependencies for us (like it said). Do robots need to sign the CLA?

On second thought, this might be a bad idea. npm3 will have deduplication, which this would disable. We also might be getting PRs all day every day since we have so many.


Add Prisoner Dilemma Dialogue Feature

Description
I have implemented two agents using the Camel framework to simulate the choices and responses in the Prisoner's Dilemma, reproducing part of the experimental results from the paper[ "Playing repeated games with Large Language Models."](https://arxiv.org/abs/2305.16867)
Motivation and Context
Verification and Replicability: By replicating the experiments described in the paper, it allows for the verification of the reported results. It helps ensure that the findings presented in the paper are reliable and reproducible, strengthening the credibility of the research.
Understanding Model Behavior: Implementing the agents provides an opportunity to gain a deeper understanding of how large language models behave in repeated game scenarios, specifically in the context of the Prisoner's Dilemma. It allows researchers and practitioners to observe the decision-making processes and strategies employed by the models, providing insights into their capabilities and limitations.
Add More Function to CAMEL
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (update in the documentation)
[x] Example (update in the folder of example)

Implemented Tasks

[x] Add a new Agent type ''Player Agent''
[x] Add Prisoner Dilemma  prompt
[x] New Role Type and New Task Type
[x] New Role Play Session For Prisoner Dilemma
[x] Test File

Checklist

[x] I have read the [CONTRIBUTION](https://github.com/camel-ai/camel/blob/master/CONTRIBUTING.md) guide. (required)
[x] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

Sorry, I did not get a chance to review this PR yet. But I guess we still want to get it in. Let's not close it. Thanks!


Adding rename table test

Since customers has problems with renaming tables, created a test to measure how much time it takes to rename a table with multiple partitions.
The test actually do 2 renames, so the end state of the test is the same as the start state. This way we do not have to create and drop the table every time.
(This is my first pull request, so feel free to guide me if something can be done better :) )

Created a new request to have the issue id in the commit message. Closing this


Bug in Siamese Example Accuracy Calculation

The siamese network example for mnist (https://github.com/fchollet/keras/blob/master/examples/mnist_siamese_graph.py) uses the following function to compute accuracy
def compute_accuracy(predictions, labels):
    '''Compute classification accuracy with a fixed threshold on distances.
    '''
    return labels[predictions.ravel() < 0.5].mean()

This seems flawed to me. For example:
import numpy as np
labs = np.array([0,0,0,0,0,1,1,1,1,1])
pred = np.array([1,1,1,1,1,0,0,0,0,0])
print(compute_accuracy(pred, labs))
# >>> 1.0

Surely the order of the predictions is important? In the example above, all of the predictions are different from the labels, and yet the compute_accuracy returns 100%.
Am I missing something obvious, or is this a mistake.

[X] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[X] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[X] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

Prediction of the siamese model in this example is distance between pairs, therefore the calculation of accuracy is taking "distance (predictions) < 0.5" as True.

Ok I picked a bad example, but I still believe that the function has problems.
import numpy as np
labs = np.array([0,1,0,1,0,1,0,1,0,1])
pred = np.array([1,1,1,1,1,1,1,1,1,0])
print(compute_accuracy(pred, labs))
# prints 1.0

import numpy as np
labs = np.array([0,1,0,1,0,1,0,1,0,1])
pred = np.array([0,0,0,0,0,0,0,0,0,1])
print(compute_accuracy(pred, labs))
# prints 0.4444

import numpy as np
labs = np.array([0,1,0,1,0,1,0,1,0,1])
pred = np.array([1,1,1,1,1,1,1,1,1,1])
print(compute_accuracy(pred, labs))
acc.py:4: RuntimeWarning: Mean of empty slice.
  return labels[predictions.ravel() < 0.5].mean()
/usr/local/lib/python3.6/site-packages/numpy/core/_methods.py:80: RuntimeWarning: invalid value encountered in double_scalars
  ret = ret.dtype.type(ret / rcount)
nan

Surely this is not correct?

Agree, should be
def compute_accuracy(predictions, labels):
    return np.mean(np.equal(predictions.ravel() < 0.5, labels))

# * Accuracy on training set: 99.53%
# * Accuracy on test set: 97.03%

What about the loss function, and similarity labels? Is it correct or not? @joelthchao @sixhobbits

@aryopg Should be correct. Any concern?

i got a suggestion from stackoverflow to "modify" the equation of contrastive loss and the sequence of the labels just like in this paper. But when i tried to aplly it, it gives me a bad result. But when i use the original keras example, it gives me a good result. Can you explain how can the code given by keras can accomodate the equation from the paper while the other code cannot?


Summary causes neovim to hang until it completes scanning

Thanks for your work first of all, this is a fantastic plugin.
I have a question/feature request:
is it possible to run the summary scan in the background/asynchronously?
At work we have a monorepo with 6000+ test files 😅 and when opening the summary for the first time it causes neovim to hang for upwards of 30-40 seconds until it finishes parsing all the files (at least that's what I assume is happening, I haven't really looked through the inner workings of neotest much). It doesn't hang the entire terminal, just neovim, so I figured it must just be blocking until it's done.
Setting concurrent to 1 for discovery doesn't help.
This could also be happening because I am using the neotest-vim-test adapter since there is no available adapter that supports mocha currently, haven't put any neotest "native" adapters through that torture yet.
Sorry if this has been asked/answered before, I couldn't find anything on this.
Nbd if there isn't something that can be done - everything still works great, this is just a minor annoyance.
Version info:
Neovim: v0.8.1 release
Neotest: commit https://github.com/nvim-neotest/neotest/commit/274d9f016c7a68991904972475a5f9d00e25fb84
Term: kitty 0.26.5
OS: macOS Ventura 13.0.1 on M1 Pro

Yeah this is due to using the vim-test adapter. It's not to do with the summary at all, that just kicks off the scanning. You'd have the same if you tried to run a test.
The issue is that because vim-test is implemented vimscript, all calls to it must be made synchronously and because it does a lot of regex parsing it is very heavy. I wouldn't recommend using it for such a large repo right now to be honest. There is new functionality to run code in a separate neovim process internally so that could be a potential solution to this but I'll have to investigate.
The best solution is to use a first class adapter. I'm not sure how different mocha would be from jest/vitest but that could be useful places to start for writing one yourself :smile: Getting a basic adapter started shouldn't be too difficult and it would perform far better

Makes sense, I'll look into putting together an adapter for mocha then. Thanks!
Feel free to close this 🙂

The latest change to neotest-vim-test now uses a separate process to run vim-test functions so the editor should now not block when parsing. It won't speed it up at all and the recommended solution is still to use a better adapter but for those stuck with vim-test it should at least be a better experience :smile:


Vue.config.errorHandler can not catch error throw in data function

Vue.js version
2.2.4
Reproduction Link
https://jsfiddle.net/githoniel/gL3f27eg/

Steps to reproduce
throw error in data function
What is Expected?
Vue.config.errorHandler can catch it
What is actually happening?
Vue.config.errorHandler can not catch it

Is my question too plain?
I think that  throwing error in vue instance's data function is very common. Many people may come across this problem.
In my view, it seems verbose to write try catch  in every data function.

imo errors in data should be handled too because errors in computed are already handled

Apologize in advance for the hijacking, but I'm really too lazy to open a new issue...
Seems errors in directives are not caught: https://jsfiddle.net/gL3f27eg/4/

This comment on a closed issue will likely be drowned in the stream of notifications, so don't expect this issue to be fixed.


bmi+tcp plugin doesn't support SM routing

Describe the bug
Is not possible to use the bmi+tcp plugin with the shared memory routing enabled auto_sm = HG_TRUE
To Reproduce
Just run the server test with shared memory routing -m and the bmi+tcp plugin:
hg_test_server -m -c bmi -p tcp

And you'll get the following error:
# Using info string: bmi+tcp://localhost:22222
# HG -- Error -- /mercury/src/mercury_core.c:3665
 # HG_Core_context_create_id(): Auto SM mode not supported with selected plugin
# HG Util -- Error -- /mercury/src/util/mercury_poll.c:402
 # hg_poll_remove(): Could not find fd in poll_set
# HG -- Error -- /mercury/src/mercury_core.c:3835
 # HG_Core_context_destroy(): Could not remove NA poll descriptor from poll set
# HG -- Error -- /mercury/src/mercury.c:1295
 # HG_Context_create_id(): Could not create context for ID 0
# HG -- Error -- /mercury/src/mercury_core.c:3968
 # HG_Core_context_set_data(): NULL HG core context

Right and it won't be supported unless we either force busy polling (which could be enabled) or spawn a thread internally (which we don't do). Is there any reason for you to use bmi+tcp instead of ofi+tcp?

Right and it won't be supported unless we either force busy polling (which could be enabled) or spawn a thread interofi/verbs is not thread-safe and requires a global lock to be internally acquired when accessing the libfabric API, hence should be considered as experimental.
onally (which we don't do). Is there any reason for you to use bmi+tcp instead of ofi+tcp?

Ok, I'll try with ofi+tcp.
Is this the same as ofi+sockets?
I've got a little bit confused by the documentation because in the OFI plugin section it first says:
The plugin currently supports sockets/psm2/verbs/gni providers

Then it talks about the tcp/sockets provider and then it uses the combination ofi/sockets.
And in the table there is not sockets among the supported protocol for OFI but only ofi+tcp.
Probably a more consistent naming will help stupid developer like me :)
In any case, is there any place in the documentation that says which plugin support the 'auto shared memory routing' feature?

OK I'm working on the documentation now, hopefully will clarify that. That feature was introduced after version 0.9.0 and the documentation was just simply not updated.


add Fibonacci_Sequence.py

Hi,
I'm a beginner, I'm still learning.
Please accept me as a contributor.
File add
"Hackerrank / Fibonacci_Sequence.py"
with the fibonacci sequence code.

File add
"Hackerrank /Very-Big-Sum.py" and  "Hackerrank/Compare-the-Triplets-2.py"


makemessages: Fix string with unnamed arguments in analytics/views.py.

Automated message from Dropbox CLA bot
@rishig, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @rishig!


Apply scheduling policies to catalog services

How could I apply scheduling policies to the Gluster FS Stack deployed from Catalog?
Is it possible to do this?

I've made this PR: https://github.com/rancher/rancher-catalog/pull/85 to make possible to the user to choose where to put all of the deployed stack's containers....

+1

Duplicate of https://github.com/rancher/rancher/issues/2852


Emulator doesn't throw error when creating tables with same name but different casing

Which service(blob, file, queue, table) does this issue concern?
table
Which version of the Azurite was used?
3.15.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
16.13.1
What problem was encountered?
The emulator does not respond with an error when creating a table using an existing name with different casing.
For example, if a table named "table01" exists, I expect an error to be returned by the emulator if I try to create a table named "TABLE01".
According to the Azure documentation, table names are supposed to be case-insensitive.
Steps to reproduce the issue?

Install and run Azurite.
Use the Azure SDK for JavaScript to create a table named "table01":const client1 = TableClient.fromConnectionString("<DEV CONNECTION STRING>", "table01", { allowInsecureConnection: true });
await client1.createTable();

Use the Azure SDK for JavaScript to create a table named "TABLE01":const client2 = TableClient.fromConnectionString("<DEV CONNECTION STRING>", "TABLE01", { allowInsecureConnection: true });
await client2.createTable();

Have you found a mitigation/solution?
No

Have written tests to cover all these cases.
Should have a PR soon.


Cache

Many request for fpm load IO ... any cache mechanism ?

Not that I'm aware. However I'm surprised your OS doesn't already handle caching of this file if it gets hit so often.

OS layaer is not depend of processing env file and etc.. php variables better to be export via var_export into script then via opcache we have performance ... unless any read or write in php script will be load io ...

If you don't mind generating a php file when you put your code in production (as part of your deployment pipeline for example), you could write a script that will create a php file by reading the .env file and creating an array out of the resulting variables. Then you can call Loader::setEnvironmentVariable to restore the variables.

We can imagine using something like: https://github.com/php-cache/array-adapter as an internal caching solution when loading variables ?
There is also: https://github.com/php-cache/filesystem-adapter if you prefer files 👍

The recommended usage of this library would be to one-time load the env file, and use it to populate config, such as in Laravel, and so runtime performance of this library is not critical. That said, I think the performance is pretty quick, such that I don't see how any sort of cache would improve things?


Update README

Edit sample link to make it non-clickable

@stevestein,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


File rules

What does this PR do?
While building/updating plugins I started to notice a lot of services creating paths and rules for targets files, so I created a new way to handle that: The targetsFileRules service.
The new service can give you a dictionary with rules and paths so you can use to find specific files for a target:
const myTarget = targets.getTarget('something');
const rules = targetsFileRules.getRulesForTarget(myTarget);

Done, you now have rules to find JS files, SCSS stylesheets, CSS stylesheets, images, fonts, etc; for an specific target.
The rules format is fully documented on the typedef.js file, so you can get more description there.
How should it be tested manually?
npm test
# or
yarn test

Pull Request Test Coverage Report for Build 145

83 of 83 (100.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 143:
0.0%

Covered Lines:
1558

Relevant Lines:
1558

💛  - Coveralls


Is the website down?

I started getting 404 from metadataapi.net since yesterday, is it gonna be a short maintenance?

server is down, need to wait when Chalupa is come to restore it

server is down, need to wait when Chalupa is come to restore it

You're doing great work! appreciate and big thanks!🙏


Unable to tell Punch The Clown if my fortune is useful

To whom it may concern:
After getting a fortune from Punch The Clown it asks me if the fortune was useful.  At present that seems like a rhetorical question as there is no way to give an answer via the screen.  If that is a bug, it needs to be fixed.  If it is a feature to be rhetorical, please ignore.
Regards,
Madison

Fixed!

What is the resolution?
On Wed, Feb 24, 2021 at 5:28 PM daveklotz<EMAIL_ADDRESS>wrote:

Fixed!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/daveklotz/PunchTheClownIssues/issues/2#issuecomment-785461807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMKABJ67SDY7Q3BWGZ5J5LTAWDQ5ANCNFSM4W7G4DNA
.


Add tests for the es5.1 profile to tools/run-tests.py

JerryScript-DCO-1.0-Signed-off-by: Peter Marki<EMAIL_ADDRESS>

@pmarkee please rebase your PR.

@LaszloLango done

@LaszloLango @pmarkee I've created the #2228 PR to try and resolve the too big travis output problem.

@pmarkee could you please rebase the PR? The test runner quiet mode has landed which should fix the Travis output problem(s).

LGTM


[KeyVault][Cryptography] Add JWK->PEM converter

For the ability to offload some of our cryptography calls to local node crypto, we'll need to be able to use the PEM key format. Right now, our keys are in JWK and require translation to PEM.

Completed as part of #5150


view not changing

all module blade file change not reflecting in browser, i have clear all the cache form the script, manually delete views cache folder. still same problem

If its a public project, share the link. I can take a look for you


[BUG] Longhorn 1.2.0 - wrong volume permissions inside container / broken fsGroup

Describe the bug
After upgrade longhorn to 1.20, some container are unable to start corectly (e.g prometheus).
Looks like root cause is wrong Longhorn volume permisions inside container when container is not running as root.
Even with fsGroup specified, permissions are not set for volume.
To Reproduce
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: broken-longhorn
  namespace: default
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  storageClassName: longhorn

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: broken-longhorn
  namespace: default
  labels:
    app.kubernetes.io/name: broken-longhorn
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app.kubernetes.io/name: broken-longhorn
  template:
    metadata:
      labels:
        app.kubernetes.io/name: broken-longhorn
    spec:
      containers:
        - name: broken-longhorn
          image: ubuntu:focal-20210723
          command:
          - "/bin/sh"
          - "-ec"
          - |
            tail -f /dev/null
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - mountPath: /data
              name: data
      securityContext:
        runAsUser: 65534
        runAsNonRoot: true
        runAsGroup: 65534
        fsGroup: 65534
        fsGroupChangePolicy: Always
      volumes:
        - name: data
          persistentVolumeClaim:
            claimName: broken-longhorn

% kubectl get pvc broken-longhorn -o yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{},"name":"broken-longhorn","namespace":"default"},"spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"longhorn"}}
    pv.kubernetes.io/bind-completed: "yes"
    pv.kubernetes.io/bound-by-controller: "yes"
    volume.beta.kubernetes.io/storage-provisioner: driver.longhorn.io
  creationTimestamp: "2021-09-01T07:48:46Z"
  finalizers:
  - kubernetes.io/pvc-protection
  name: broken-longhorn
  namespace: default
  resourceVersion: "25249959"
  uid: 9ab5ca66-0794-4ad2-8aa5-73e96fa603fc
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  storageClassName: longhorn
  volumeMode: Filesystem
  volumeName: pvc-9ab5ca66-0794-4ad2-8aa5-73e96fa603fc
status:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 1Gi
  phase: Bound

% kubectl get pv pvc-9ab5ca66-0794-4ad2-8aa5-73e96fa603fc -o yaml
apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    pv.kubernetes.io/provisioned-by: driver.longhorn.io
  creationTimestamp: "2021-09-01T07:48:48Z"
  finalizers:
  - kubernetes.io/pv-protection
  - external-attacher/driver-longhorn-io
  name: pvc-9ab5ca66-0794-4ad2-8aa5-73e96fa603fc
  resourceVersion: "25250154"
  uid: d4db7690-4763-45bf-a5c7-9b7ae0b5d584
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 1Gi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: broken-longhorn
    namespace: default
    resourceVersion: "25249908"
    uid: 9ab5ca66-0794-4ad2-8aa5-73e96fa603fc
  csi:
    driver: driver.longhorn.io
    volumeAttributes:
      fromBackup: ""
      numberOfReplicas: "3"
      staleReplicaTimeout: "30"
      storage.kubernetes.io/csiProvisionerIdentity:<PHONE_NUMBER>980-8081-driver.longhorn.io
    volumeHandle: pvc-9ab5ca66-0794-4ad2-8aa5-73e96fa603fc
  persistentVolumeReclaimPolicy: Delete
  storageClassName: longhorn
  volumeMode: Filesystem
status:
  phase: Bound

% kubectl get csidriver driver.longhorn.io -o yaml
apiVersion: storage.k8s.io/v1
kind: CSIDriver
metadata:
  annotations:
    driver.longhorn.io/kubernetes-version: v1.20.7+k3s1
    driver.longhorn.io/version: v1.2.0
  creationTimestamp: "2021-08-31T17:47:21Z"
  name: driver.longhorn.io
  resourceVersion: "24953648"
  uid: 274cd12a-6aca-47a9-bfd8-32261eb5033a
spec:
  attachRequired: true
  fsGroupPolicy: ReadWriteOnceWithFSType
  podInfoOnMount: true
  volumeLifecycleModes:
  - Persistent

$ kubectl exec -t -i broken-longhorn-c4ccbbb6f-79djg -- bash
nobody@broken-longhorn-c4ccbbb6f-79djg:/$ ls -la /data/
total 24
drwxr-xr-x 3 root root  4096 Sep  1 07:49 .
drwxr-xr-x 1 root root  4096 Sep  1 07:49 ..
drwx------ 2 root root 16384 Sep  1 07:49 lost+found
nobody@broken-longhorn-c4ccbbb6f-79djg:/$ touch /data/test
touch: cannot touch '/data/test': Permission denied

Expected behavior
When fsGroup is provided, it should be used to chown destination mount.
Environment:

Longhorn version: 1.20
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3os/k3s
Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): baremetal

Additional context
% kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:52:14Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7+k3s1", GitCommit:"aa768cbdabdb44c95c5c1d9562ea7f5ded073bc0", GitTreeState:"clean", BuildDate:"2021-05-20T01:07:13Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}

I can confirm this happens for automatically provisioned volumes as well (i.e. statefulsets)
[hubbe@ma3a ~]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:45:37Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4", GitCommit:"3cce4a82b44f032d0cd1a1790e6d2f5a55d20aae", GitTreeState:"clean", BuildDate:"2021-08-11T18:10:22Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}

statefulset example:
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: pvc-ownership-test
spec:
  selector:
    matchLabels:
      app: pvc-ownership-test
  serviceName: pvc-ownership-test
  template:
    metadata:
      labels:
        app: pvc-ownership-test
    spec:
      securityContext:
        runAsUser: 1000
        runAsGroup: 1000
        fsGroup: 1000
      containers:
        - image: docker.io/library/busybox:latest
          name: pvc-ownership-test
          command: ["/bin/sh"]
          args: ["-c", "sleep 6000000"]
          volumeMounts:
            - name: test
              mountPath: /test
  volumeClaimTemplates:
    - metadata:
        name: test
      spec:
        accessModes: [ "ReadWriteOnce" ]
        resources:
          requests:
            storage: 1Gi
        storageClassName: longhorn

[hubbe@ma3a ~]$ kubectl exec -it pvc-ownership-test-0 -- sh

/ $ id
uid=1000 gid=1000 groups=1000
/ $ ls -ahl /test
total 24K
drwxr-xr-x    3 root     root        4.0K Sep  1 09:38 .
drwxr-xr-x    1 root     root        4.0K Sep  1 09:38 ..
drwx------    2 root     root       16.0K Sep  1 09:38 lost+found

I seem to be hitting this as well.

Has anyone found a work around for this issue or can we expect an emergency patch as this seems to be a show stopper for me and is currently blocking us. Every pod deployed now gives a message similar to;
Memory limits: min=256m, max=512m
/opt/startZk.sh: line 71: /opt/zookeeper/data/myid: Permission denied

Agreed, this is a showstopper. I had to roll back to 1.1.x. Fortunately this was only a dev environment and it's no biggie to blow away the storage.

Workaround: manually add a new flag --default-fstype=ext4 to the csi-provisioner deployment in longhorn-system namespace. It should look like this:
...
      containers:
      - args:
        - --v=2
        - --csi-address=$(ADDRESS)
        - --timeout=1m50s
        - --leader-election
        - --leader-election-namespace=$(POD_NAMESPACE)
        - --default-fstype=ext4
        env:
 ...

Root cause:

The field fsType is missing in the PV created in Longhorn v1.2.0. And this prevents Kubernetes from changing the volume ownership and permissions, link
The problem of missing fsType in PVs seems to come from the csi-provisioner. In the old csi-provisioner (v1.6.0), the defaultFSType is hard-coded to ext4, link.  However, in the new csi-provisioner (v2.1.2) it is empty by default, link.

Test steps:

Install/Upgrade Longhorn using kubectl/helm
Deploy statefulset at https://github.com/longhorn/longhorn/issues/2964#issuecomment-910117570
Exec into the pod and verify that /test/ has correct permission and can read/write new files to /test

Verified with Longhorn-master and v1.2.x-head 09/08/2021
Validation - Pass

Is pointing people to a workaround enough if 1.2.1 is still weeks away? This is a fatal enough flaw I'd think 1.2 should either be pulled or re-released with the fix.

@mstrent While this issue has indeed high impact:

The workaround is non-intrusive and should solve the problem immediately without side effects.
We're accelerating the release of v1.2.1 to less than 2 weeks from now (09/24), to fix this issue and a few other issues we've found after v1.2.0 release.

Retag or re-released a version is generally a bad idea, since there is no way to upgrade from and to the same version, and there won't be helpful to any existing users already hit the bug. It's going to be lots of things mixed up if we choose to do that.
Sorry for the inconvenience. v1.2.1 will be there soon.

Retag is usually a no-go, but you can still release 1.2.1, then just go with 1.2.2 for whatever is "planned" for 1.2.1.
This is also fixed in the helm package, what about at least upgrading that? The version of the helm-chart and app-version is not the same.

This bug still exists even with the workaround in https://github.com/longhorn/longhorn/issues/2964#issuecomment-910969543 or similar one.
LAST SEEN   TYPE      REASON        OBJECT                     MESSAGE
15m         Normal    error         helmrelease/influxdb       reconciliation failed: upgrade retries exhausted
6m43s       Warning   FailedMount   pod/influxdb-influxdb2-0   Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[data kube-api-access-hbpq2]: timed out waiting for the condition
2m25s       Warning   FailedMount   pod/influxdb-influxdb2-0   MountVolume.MountDevice failed for volume "pvc-fb7df8b3-0090-4fdf-b74f-309fd8056563" : rpc error: code = Internal desc = format of disk "/dev/longhorn/pvc-fb7df8b3-0090-4fdf-b74f-309fd8056563" failed: type:("ext4") target:("/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-fb7df8b3-0090-4fdf-b74f-309fd8056563/globalmount") options:("defaults") errcode:(exit status 1) output:(mke2fs 1.45.5 (07-Jan-2020)
/dev/longhorn/pvc-fb7df8b3-0090-4fdf-b74f-309fd8056563 is apparently in use by the system; will not make a filesystem here!
)

/dev/longhorn/pvc-fb7df8b3-0090-4fdf-b74f-309fd8056563 is apparently in use by the system

@samip5 I believe you have a different problem. Something is hijacking the Longhorn block device. There are some debugging steps here https://github.com/longhorn/longhorn/issues/2983

/dev/longhorn/pvc-fb7df8b3-0090-4fdf-b74f-309fd8056563 is apparently in use by the system

@samip5 I believe you have a different problem. Something is hijacking the Longhorn block device. There are some debugging steps here #2983

https://github.com/longhorn/longhorn/issues/1210#issuecomment-671591451:
Those instructions are not applicable, as there is no major:minor version befode device name?

I also encounter this bug. I tried to install Hashicorp Vault through a helm chart. This one does not allow custom fsGroup settings and I can see that the main directory is not set to the vault user.
I also tried setting the fsType through the storage class but it does not help.

@GeroL
Did you try the workaround https://github.com/longhorn/longhorn/issues/2964#issuecomment-910969543?


Configure LFH API in Kong API Gateway

Implement the Kong API Gateway for Linux for Health. The initial implementation should provide a single API ingress for LFH services.
Example below. These aren't necessarily the intended mappings but illustrate that the API gateway provides a nice "flat" URL scheme that maps to the underlying Camel URIs.
http://lfh.org/fhir/r4/resource -> maps to host:8080/fhir/r4/resource
http://lfh.org/images -> maps to host:9090/orthanc/images

The function in the description exists today, but the goal of this issue is to specifically define each LFH API in Kong, vs. one definition for all LFH APIs in Kong.


New feature — Single root inheritance

This feature allows to store children subclasses in the same collection as the parent, as well as properly handle types of classes when storing and fetching them in the DB.

Hey!
I decided to rework a few things and moved your commits to the new branch. It will be merged in this PR: https://github.com/roman-right/beanie/pull/395

Hey! I decided to rework a few things and moved your commits to the new branch. It will be merged in this PR: #395

Hi.
I used https://github.com/roman-right/beanie/tree/feat/inheritance and  https://github.com/Vitalium/beanie
Found something different.
https://github.com/Vitalium/beanie/blob/main/docs/tutorial/inheritance.md
Vitalium
white_vehicles = await Vehicle.find(Vehicle.color == 'white').to_list()
# [
#    Bicycle(..., color='white', frame=54, wheels=29),
#    Car(fuel='diesel', ..., color='white', body='crossover'),
#    Bus(fuel='diesel', ..., color='white', body='bus', seats=80)
# ]

feat/inheritance
white_vehicles = await Vehicle.find(Vehicle.color == 'white').to_list()
# [
#    Vehicle(..., color='white'),
#    Vehicle(..., color='white'),
#    Vehicle(..., color='white'),
# ]

Hey @hgalytoby
Please, be aware, this feature in feat/inheritance is not finished yet. Some implementation and even API details could be changed. And not all the corner cases are tested there. I plan to invest a week or two there, as I need to unify interfaces to work with sync documents.
Regarding your question: please follow this line to have the expected result: https://github.com/roman-right/beanie/blob/feat/inheritance/tests/odm/documents/test_inheritance.py#L31
Probably you will need to rewrite data in the database, as the way of generating the _class_id value was changed.

Hey @hgalytoby Please, be aware, this feature in feat/inheritance is not finished yet. Some implementation and even API details could be changed. And not all the corner cases are tested there. I plan to invest a week or two there, as I need to unify interfaces to work with sync documents.
Regarding your question: please follow this line to have the expected result: https://github.com/roman-right/beanie/blob/feat/inheritance/tests/odm/documents/test_inheritance.py#L31 Probably you will need to rewrite data in the database, as the way of generating the _class_id value was changed.

Thank you, I understand.

Implemented in https://github.com/roman-right/beanie/pull/395


Sounds not working in web build

It is bigger problem than I thought. Basically web browser automatically blocks any sound if user hasn't clicked anything. So for work around I basically set up starting screen for webbrowser that says to play a game click any button and then splash screen happens.

Stimulating click like in jQuery's $('background').click() is not an option?

Unfortunately not, it detects that this was not actual interaction from client. It has to be some kind of interaction, click, mouse move, etc. We cannot rely on mouse move so we have to listen for clicks.

What about making an animation (.mp4 file) and playing it? Can you auto-start MP4, MKV etc. video with sound without any user interaction?

Yes, we can start a muted video any time. We just cannot play sounds without user interaction, as it is seen as "annoying" for the user.

But again, without any interaction from user, even video end it will just not work.

OK, I am working on some idea. Just give me some time.
What about second movie / sound / effect / animation / video? If user clicks and you successfully show our logo with sound and then you would like to play some other audio file (on the same screen), can you trigger it automatically (after first "user interaction" / click)? Or we must have user click / tap / press key) any time we want to trigger some mp3 playout?

So basically it is limited only to first interaction. So after user clicks something once we can play any sound we like.
Therefore what I did is before splash screen I created (for now) empty screen with text click anything to start a game. It only shows in browsers, so electron app is not affected by that, as there we can play any sounds we like. The same mobile version.

I can't think of any other workarounds for the moment - and for what I have found on internet it seems that this is "desired" workaround. We could listen for mousemove for example, but we cannot guarantee that user will move it at all, therefore I would prefer to use on browser this starting screen before splash.
It is as well most likely to not change in the future, as other workarounds might marked as not desired and blocked later.

I totally understand this and eagerly agree with this blockade. As a web user / web game player I don't want anything to play by itself when it is opened in some tab, before I actually interact with it. So the below is not a way for looking for an workaround, but rather a kind of _lessons learnt" for future.
Ideas:

See, if you can listen for DOMContentLoaded event or use $(document).bind('ready', function() {}); and trigger playing sound from there (unless you have already checked it; then skip this point).

Check, if you can listen for main window's resize? Chances that you start game with exactly the same dimensions as user currently have its browser set are minimal. I have heard that onResize() event is triggered by Javascript / DOM any time new URL loads.

See, if you can listen for visibilitychange event and make use of it.

Check, if you can auto-play audio (or video) muted and then use Web Audio API (in one of the above events?) to increase volume to some level?

See, if this old trick with playing silence in an iframe is going to work for you.

BTW: Last page (5) has a bug (or an intentionally hidden content). When you open it, it seems empty. Open Dev Tools in your browser (Ctrl+Shift+C) click on "empty" page, locate
 in page source and hit Del to delete this HTML element. Then you'll have full access to page content.
The trick does work (when you click on the example links and go to https://olafwempe.com/ the background music truly auto-starts), but again the entire page is hidden behind empty full-screen overlay. This is most likely this "silence"-iframe that the article talks about.
If this will work in our game and provided that you DO WANT to break browser limitations and auto-start logo tune then you maybe forced to hide/close this iframe (or
 element) programmatically.
If you don't want to break the rules / limitations then consider this task as completed / closed. And we will re-use that additional screen (that you have prepared already, with "click to start") to display "early alpha game" info.

Already tried 4 of the first steps, nothing of it does work. 5 step should work, but in that case I would prefer to use official solution so wait for user click, as iframe may break in future.
Will leave it as closed and done and we should be able to use this screen as info popup as well, I just need to modularize it, as for now it just display static text without any graphics.
I'll use for that tasj ticket that already existst.


Fixes a bug in the ElementBatch.CalcRenderBounds implementation

It's a little bit saddening that this didn't cause a test to fail... :/


GDPR laws

          This is really important to notify in the NPM repository or the GitHub itself.

As some developers need the packages and with the current GDPR Europe Laws we can't make this into production without a signed agreement between the two companies.
Originally posted by @dlh2 in https://github.com/dveldhoen/easyinvoice/issues/4#issuecomment-1527582299
As commented in this issue, invoices usually include sensitive data as prior to the principles there must be a way that the user that uses the package knows that somehow this data is being sent into another place and then resent back for the purpose of the package.

We will look into it, but since we are swamped with work and this is a free package we don't have the time at the moment. For now if this is a concern for you, best not use the package.


Remove blocklist platform category wildcard all

As of #225 all blocklist rules are platform specific. Per-platform driver discrepancies mean blocks should always be platform dependent.
There was one exception briefly (Switch Pro) but Linux and Android now ship kernel drivers for it. Seems good practice generally to specify platform.

Merged #225, all done

Handling stuff can go -- https://github.com/offalynne/Input/blob/dev/scripts/__input_gamepad_set_blacklist/__input_gamepad_set_blacklist.gml#L14-L39
Can author PR later

Accepted #233, thank you kindly


Players with number in the name

Some players have numbers in the name, so search is not correct.
Examples:

m0nesy
s1mple
k0nfig
b1ad3
w0nderful
dav1deus
n0thing
f1ku
s1ren

For example, dev1ce's name in the data is device, so maybe we can change those names in the data.
Other option could be to add flag for the users whether they want to interpret numbers as letters.

Some numbers could match multiple letters is something to consider. For example b1ad3 = blade but s1mple = simple. In the context of using them for just a few letters to make up a longer word I suppose they could be used either way, if you wanted si or sl you could use the s1 from s1mple.