IGAPP-1179: Poi categories native

Show Poi Category on native app

Code looks good, but getting visual bugs, see attached screenshots Navigating to Berlin, everything looks fine:  Clicking on Joan Miro, berlin icon is just a black circle  Selecting Berlin, Joan Miro icon is dark
Also i get a lot of  Mapbox [info] Request failed due to a permanent error: Canceled {"level": "warning", "message": "Request failed due to a permanent error: Canceled ", "tag": "Mbgl-HttpRequest"} errors in the console.

@SteffiStuffel these look like common emulator bugs on android. could you please test (and maybe confirm) this issue on real device. We receive this warning error in all devices even if it works. Is a maplibre issues (happens f.e. also in entitlementcard)


HTTPS support

It seems we only have http support for now with this image.
nginx-proxy is using a VIRTUAL_PROTO environment variable https://github.com/jwilder/nginx-proxy/blob/985c46d8b56f2ee4652e9d75b49c128c14bee328/nginx.tmpl#L134
And sets a bunch of configs in https://github.com/jwilder/nginx-proxy/blob/985c46d8b56f2ee4652e9d75b49c128c14bee328/nginx.tmpl
I personally have no ideas what these config mean and how to properly configure nginx so I won't be able to propose a PR, but I believe cherry picking his code would be enough.
Also, would the ELB forward port 443 to port 80 of nginx or to port 443?

I think that depends where you terminate the SSL connection. In my case I am using SSL to the LB and then go without SSL from the LB to the nginx. If you terminate at nginx then probably forward to 443.
I wouldn't like to just copy paste the code without understanding it.
Would need to make some certs and set up a test instance to figure it out.

makes sense. I'm going to close that as that's enough. I believe you're loading wildcard certificates on your ELB why gives you SSL traffic for all your containers, right?

Exactly.


[$1000] Web - Assignee name and avatar is not dynamically updating after renaming from account B

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open two new accounts (account A and account B)
Go to account B and copy the email
Go to account A and click on FAB > assign task > give a title > click next
Click on assignee and paste the copied email and select it
Go to account B and click on settings > name > rename it
Click on the profile picture and give it a profile picture

Expected Result:
Both assignee and share somewhere avatar and name should dynamically update after renaming from account B
Actual Result:
Only share somewhere gets updated and assignee doesn't update dynamically.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.36-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/03455a6f-5037-4243-86f1-94b3452376d0
https://github.com/Expensify/App/assets/93399543/f544288c-db02-46f2-a218-499cc70f57e1
Expensify/Expensify Issue URL:
Issue reported by: @Nathan-Mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688449071046279
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0138dda630214da2a7
Upwork Job ID:<PHONE_NUMBER>664472064
Last Price Increase: 2023-08-17

Looks good!

I tried pulling the main branch, this is not reproducible on main

Heads up, I just closed a related issue with the same root cause: https://github.com/Expensify/App/issues/22481. It's the same behavior, but on a different page (the task assignee contact list). Let's make sure that the fix here also fixes that other page.

Heads up, I just closed a related issue with the same root cause: #22481. It's the same behavior, but on a different page (the task assignee contact list). Let's make sure that the fix here also fixes that other page.

has the root cause been identified or just the behaviour?

@Swor71 just the behavior, but the issue is the same, so I still think we should try to investigate both and fix together.

Great!  Assigning you @Swor71 !

not overdue. I found the root cause and I am working on a proposal.

@Swor71 is this on your radar?

@slafortune hey, yes I am aware of this, unfortunately this seems a bit more entangled than I originally thought. I might actually reach out in slack to discuss this further.

the issue and some suggested solutions are currently in an internal discussion

the proposal is in an internal discussion

Proposal
Please re-state the problem that we are trying to solve in this issue.
During the process of assigning a task to a user, if that assignee’s name changes, it is not reflected in the UI. This happens for new users only.
What is the root cause of that problem?
I believe the root cause for this issue is the whole process of creating an optimistic user account (userToInvite in optionsListUtils) when doing a ‘look up’ while assigning the task. From the optimisticAccountID a lot of other entries are spawned like report’s participantAccountIDs, icon/avatar, task’s assigneeAccountID among others. The assigneeAccountID in task (Onyx) is not the correct id for the account we’re assigning the task to, and it is never changed. Additionally, the personalDetailsList entry created from userToInvite is not cleaned up.
What changes do you think we should make in order to solve the problem?
The quick fix is to reassign the task’s assigneeAccountID as well as report’s participantAccountIDs to the correct ID for a given account. This should be done in NewTaskPage component.
In my opinion, however, the better fix would be to address the ‘fake’ look up as that is the root of the problem. If the look up worked as an actual feature, we’d already have the correct id and every following action of creating the report, setting correct avatar, task’s assignee id, participant account ids and else, would work as intended. To my mind, creating the incorrect optimistic account and sprouting the above from it only to patch it a moment later feels wrong. Not to mention the odd UX for looking up an account, only to see a random avatar being created, assigned and then flipped to the correct one when data arrives from the pusher.

@eVoloshchak can we move forward with this?

Just wanted to inform you that I will be OOO for the next two weeks due to planned holidays. One of my colleagues from Callstack will pick this one up. I have pushed my changes for the quick fix since the proper fix needs discussion on the part of Expensify team.

Checking on this - https://expensify.slack.com/archives/C02NK2DQWUX/p1690811805490969

@Swor71, thank you for such a thorough investigation!

In my opinion, however, the better fix would be to address the ‘fake’ look up as that is the root of the problem. If the look up worked as an actual feature, we’d already have the correct id and every following action of creating the report, setting correct avatar, task’s assignee id, participant account ids and else, would work as intended. To my mind, creating the incorrect optimistic account and sprouting the above from it only to patch it a moment later feels wrong.

I totally agree with this. I'm not sure if we need to apply a quick fix for this, since we're technically working around a bigger problem as you've described.  Let's fix the actual root cause instead, that will also ensure we don't have the same problem on other pages/flows

Hey all, I'll be taking this over for the time being until @Swor71 is back from ooo

I've assigned you to the GH now @arthurmfgtab  - I'll update the tags again.  It would great to get this one resolved 👍

Still getting up to speed on Marcin's solution..

Update: we have a draft PR that we're discussing internally. It follows Marcin's proposal but it's not fully ready yet.

@slafortune We have this draft PR that uses the solution discussed in the proposal.
The solution requires that Pusher sends a complete response to user 1 when user 2 updates his/her name. Right now only firstName, lastName and displayName are being send, but we also need login (containing the user's email).
Do you think we could talk to the backend folks to include that extra info on the response?

@eVoloshchak @slafortune could you guys take a quick look at the comment above? :)

Not oversue, waiting for @eVoloshchak and @slafortune answers

Thanks for calling this out @arthurmfgtab - I'll defer to @eVoloshchak on this, they will be best to answer this.

Getting an internal engineer assigned (Melvin must have missed that at some point) to help answer and push this forward.

@arthurmfgtab just to confirm, you want to include the login in the response from the API when the user modifies their display name (which ends up calling UpdateDisplayName), right?

@NikkiWines correct!

PR is up + approved, should be deployed to prod early next week

Hey all, I'll look into this today

Hi! Sorry, I'm coming into this way late, but would someone mind explaining to me why we need the login in order to be able to update the avatar/display name of the task assignee? I would think that having the accountID should be enough, but I'd love to understand better why that isn't the case. Thanks in advance!

Hey @slafortune , 2 things I noticed today as I was working on this

"login" doesn't seem to be on production yet (see image below)

Did we remove the "fake lookup" feature? (showing an account regardless of whether that account really exists on the backend), (see video below)

https://github.com/Expensify/App/assets/55854142/026bf524-d938-47b9-9f66-224a9465651e

Thanks for the link @arthurmfgtab. I would think that what should happen is:

We use the optimisticID in all the various place while creating the task
The server returns all the Onyx data with the correct optimisticID
in the successData for the API call, we clear out the data that we set using the optimisticID

Can we do that? That should make it so that we don't need the login field but still get the task pointed to the correct account.

@puneetlath thanks for the suggestion and sorry about the delay on replying ya
About the steps you proposed: from my understanding your solution requires that the optimisticID and the ID of the actual user created on the backend (that will be then sent to the frontend by pusher) are the same, correct?
If so, that's the whole point of the ticket. We need a field that's shared by both objects (the local one created on the frontend and the real one on the backend) so we can use that field to merge the right objects.
Does that make sense?

Ah, that's not quite what I was suggesting. I was suggesting that it's fine if the accountIDs are different. So the flow would be:

I create task and assign it to<EMAIL_ADDRESS>Since I don't yet "know" that email within Expensify, we optimistically assign the task to accountID1234
So now we have taskID=1 assigned to optimistic accountID=1234
The API returns taskID=1 assigned to real accountID=5678 along with public personal details for account 5678 (doesn't include email)
SuccessData clears out optimistic user 1234

Would that not work? Is it because tasks currently use mentions for showing who is assigned and mentions are login-baed instead of accountID-based?

@arthurmfgtab thoughts on this?
Also, I'm out on sabbatical so adding a new BZ member.

Bumping @arthurmfgtab to address Puneet's comment here

Hey team, I'll look into this today

@arthurmfgtab just a friendly bump to move this one along cheers!

Hey @jliexpensify , sorry about this, I'll test Puneet's idea and give a feedback

Bump @arthurmfgtab - how are you going? Let's move this one along!

Hey @puneetlath , about your suggestion here
So, basically, as soon as the api returns the real user data we start "pointing" to it and delete the optimistic one (user 1234), instead of replacing the optimistic object with the real data, correct?
If so, I don't see how we would know which object to delete as soon as the real one is pushed to the frontend because, as far as I can see, the objects don't share any value:

@puneetlath I dropped a message to you on Slack so we can try to syncronously talk about this and try to find a solution together :)

Also, @jliexpensify , do you have insight on the #2 question here? Just want to confirm whether something has changed because I used to be able to assign tasks to fake emails but now I can't 🤔
https://github.com/Expensify/App/assets/55854142/5bbe9374-0da4-40c9-bafa-fb10130a2e9a

I'll be ooo tomorrow but I'm getting back to this on Monday

@arthurmfgtab yeah, it looks like a change was made a month ago here: https://github.com/Expensify/App/pull/25806

Any thoughts @arthurmfgtab?

taking a look at this, will share my thoughts in a few

@arthurmfgtab any updates?

@jliexpensify I tested the feature and indeed the "fake look up" was removed, which I think solves our issue because the assignee name and avatar not being changed was a problem for "local users" (the ones with fake data that would eventually be overwritten by an object with the proper user data).
If, for instance, account A adds someone to a workspace and, while holding on the "Assign Task" action, the account B changes his/her information those are properly updated on the account A's screen, so it's working fine I think:
https://github.com/Expensify/App/assets/55854142/26f5c47c-f899-414e-b2ac-b723c90e14aa

@puneetlath , I'm sorry, do what exactly? 😄

Bumping @puneetlath here - this comment sounds like the issue is fixed?

Waiting on Puneet - comment

Not overdue

Bumping @puneetlath to confirm that we can close this issue.

Sorry for the delay! Sounds like we can indeed close the issue as long as everything is working as expected!

Thanks Puneet - I'll just need to pay out the reporter first.
PAYMENT SUMMARY

BUG REPORTER: @Nathan-Mulugeta $250

NEW UPWORKS JOB

Hello all! I would like to contribute to this issue, can i be assigned?

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/chaddhayash

Hello all! I would like to contribute to this issue, can i be assigned on this one?

@yashchaddha sorry, this issue is about to be closed.

Oh Okay no problem @jliexpensify , saw it today on upwork, hence applied for it.
Thankyou

Ah sorry for the confusion - I created an issue to pay out the bug reporter. Just waiting for him to accept and it'll be closed out!

No problem @jliexpensify

Offer accepted @jliexpensify

Paid and job closed!


Mypy plugin can't handle mypy development builds

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.9.0
            pydantic compiled: True
                 install path: C:\Users\Clock\.virtualenvs\Penny-Dreadful-Tools-AXkPbsJM\Lib\site-packages\pydantic
               python version: 3.10.2 (tags/v3.10.2:a58ebcc, Jan 17 2022, 14:12:15) [MSC v.1929 64 bit (AMD64)]
                     platform: Windows-10-10.0.19043-SP0
     optional deps. installed: ['dotenv', 'typing-extensions']

Mypy Version: 0.940+dev.b3752a60af3f8e6a1b17c4ebc90ed554cb934288
Steps to reproduce:
# Install a development build of mypy
git clone https://github.com/python/mypy.git
cd mypy
python3 -m pip install --upgrade .

# cd to your project, and run mypy
mypy .

Output:

mypy.ini:2:1: error: Error importing plugin "pydantic.mypy": could not convert string to float: '0.940+dev.b3752a60af3f8e6a1b17c4ebc90ed554cb934288'  [misc]
Found 1 error in 1 file (errors prevented further checking)

https://github.com/samuelcolvin/pydantic/pull/3783
https://github.com/samuelcolvin/pydantic/pull/3845

I'm seeing the following in my CI:
mypy.ini:2: error: Error importing plugin "pydantic.mypy": could not convert string to float: '1.0.1'  [misc]

It seems to work fine locally and only encounters this in TeamCity (of course). My mypy.ini lines are as follows
[mypy]
plugins = sqlalchemy.ext.mypy.plugin,pydantic.mypy
...

Here's the output of python -c "import pydantic.utils; print(pydantic.utils.version_info())" on my CI:
               pydantic version: 1.9.1
03:55:39               pydantic compiled: True
03:55:39                    install path: /opt/buildagent/work/a6b7174e1ff9fed1/venv/lib/python3.8/site-packages/pydantic
03:55:39                  python version: 3.8.12 (default, Nov 17 2021, 16:58:51)  [GCC 10.2.1 20210110]
03:55:39                        platform: Linux-5.15.0-60-generic-x86_64-with-glibc2.2.5
03:55:39        optional deps. installed: ['dotenv', 'typing-extensions']

So essentially the same thing, except this is trying to turn 1.0.1 into a float somewhere? :thinking:

This was fixed at some point, you need to upgrade pydantic, afraid I'm afk and can't remember in which release it was fixed.

Nah, This was resolved in 1.10

Pydantic made a fix some time ago to accept version formats which aren't valid as floats.

Yeah, I did it. #3783

Oh great, sorry I was on my phone and missed that. Your change was included in v1.10.
I think that's the problem @Kartstig was having - they're using an older version of pydantic.

Looks like it's working fine with 1.10.5 but now I have some new errors to resolve :sweat:
Thanks for the response and clarification!


Vagrant hypervisor Ruby issues

So I kept meaning to open an issue for this, but I thought it was only happening to me because I had a weird boxen setup, but I've seen it happen to two other people @terrimonster and @zacharyalexstern who didn't have boxen (but did have rbenv, which I assume is the issue)
So heres a summary:
Have rbenv installed. Have Vagrant installed.
Clone a repo that has some beaker rspec tests:
git clone https://github.com/puppetlabs/puppetlabs-apt

Try to run a beaker test that uses the vagrant hypervisor:
bundle exec rspec spec/acceptance/apt_spec.rb

You get the following error message:
/opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:166:in `block (2 levels) in vagrant_cmd': Failed to exec 'vagrant up' (RuntimeError)
	from /opt/rubies/2.0.0-p451/lib/ruby/2.0.0/open3.rb:217:in `popen_run'
	from /opt/rubies/2.0.0-p451/lib/ruby/2.0.0/open3.rb:99:in `popen3'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:161:in `block in vagrant_cmd'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:159:in `chdir'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:159:in `vagrant_cmd'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:121:in `provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor.rb:68:in `create'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/network_manager.rb:48:in `block in provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/network_manager.rb:47:in `each_key'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/network_manager.rb:47:in `provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec/beaker_shim.rb:29:in `provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec/spec_helper.rb:40:in `block in <top (required)>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core.rb:154:in `configure'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec/spec_helper.rb:5:in `<top (required)>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec.rb:5:in `require'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec.rb:5:in `<module:BeakerRSpec>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec.rb:1:in `<top (required)>'
	from /Users/petersouter/projects/puppetlabs-apt/spec/spec_helper_acceptance.rb:1:in `require'
	from /Users/petersouter/projects/puppetlabs-apt/spec/spec_helper_acceptance.rb:1:in `<top (required)>'
	from /Users/petersouter/projects/puppetlabs-apt/spec/acceptance/apt_spec.rb:1:in `require'
	from /Users/petersouter/projects/puppetlabs-apt/spec/acceptance/apt_spec.rb:1:in `<top (required)>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `load'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `block in load_spec_files'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `each'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `load_spec_files'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/command_line.rb:18:in `run'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/runner.rb:103:in `run'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/runner.rb:17:in `block in autorun'

I believe this is because of the vagrant shim:
$ which vagrant
/opt/boxen/rbenv/shims/vagrant

Delete the shim:
$ rm -rf /opt/boxen/rbenv/shims/vagrant
$ which vagrant
/usr/bin/vagrant

Then you get a slightly different error:
/opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:166:in `block (2 levels) in vagrant_cmd': Failed to exec 'vagrant destroy --force' (RuntimeError)
	from /opt/rubies/2.0.0-p451/lib/ruby/2.0.0/open3.rb:217:in `popen_run'
	from /opt/rubies/2.0.0-p451/lib/ruby/2.0.0/open3.rb:99:in `popen3'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:161:in `block in vagrant_cmd'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:159:in `chdir'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:159:in `vagrant_cmd'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor/vagrant.rb:117:in `provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/hypervisor.rb:68:in `create'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/network_manager.rb:48:in `block in provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/network_manager.rb:47:in `each_key'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-2.1.0/lib/beaker/network_manager.rb:47:in `provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec/beaker_shim.rb:29:in `provision'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec/spec_helper.rb:40:in `block in <top (required)>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core.rb:154:in `configure'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec/spec_helper.rb:5:in `<top (required)>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec.rb:5:in `require'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec.rb:5:in `<module:BeakerRSpec>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/beaker-rspec-4.0.0/lib/beaker-rspec.rb:1:in `<top (required)>'
	from /Users/petersouter/projects/puppetlabs-apt/spec/spec_helper_acceptance.rb:1:in `require'
	from /Users/petersouter/projects/puppetlabs-apt/spec/spec_helper_acceptance.rb:1:in `<top (required)>'
	from /Users/petersouter/projects/puppetlabs-apt/spec/acceptance/apt_spec.rb:1:in `require'
	from /Users/petersouter/projects/puppetlabs-apt/spec/acceptance/apt_spec.rb:1:in `<top (required)>'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `load'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `block in load_spec_files'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `each'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `load_spec_files'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/command_line.rb:18:in `run'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/runner.rb:103:in `run'
	from /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/runner.rb:17:in `block in autorun'

Then add vagrant-wrapper gem to the Gemfile:
gem 'vagrant-wrapper', :require => false

Then everything works normally:
Beaker::Hypervisor, found some vagrant boxes to create
==> ubuntu-server-12042-x64: VM not created. Moving on...
Bringing machine 'ubuntu-server-12042-x64' up with 'virtualbox' provider...
==> ubuntu-server-12042-x64: Importing base box 'ubuntu-server-12042-x64-vbox4210-nocm'...
==> ubuntu-server-12042-x64: Matching MAC address for NAT networking...

I'm not super certain whats happening, I'm assuming it's a pathing issue somewhere. The shim seems to be the key thing I think.
https://github.com/sstephenson/rbenv/issues/388 and http://stackoverflow.com/questions/16496333/rbenv-continually-generating-vagrant-shim might help:
The SO question suggests
alias vagrant /usr/bin/vagrant

But I'd prefer not to have to change my dotfiles...

For what it's worth, this doesn't always happen to me, so it may depend on the version of beaker. E.g. I don't have this problem with a brand new module generated via garethr/puppet-module-skeleton but I do have the problem trying to run the acceptance tests for puppetlabs/inifile.

Ok, so this is happening with beaker master for me:
gem "beaker", :git => 'https://github.com/puppetlabs/beaker.git', :ref => '6776472eca29ee9526b3979362ea9690c0ca7261'

@zacharyalexstern can you paste the version of beaker from the Gemfile.lock you've got in that new module generated?

LOLcalhost :: src/Puppet/puppetlabs-pse ‹set_ntp_server› % cat Gemfile.lock|grep beaker
  remote: https://github.com/nrvale0/beaker.git
    beaker (2.1.0)
    beaker-rspec (4.0.0)
      beaker (~> 2.0)

I'm going to file an internal bug for tracking this as well.

Now that https://github.com/puppetlabs/beaker/pull/610/ has been merged, it gives the probable reason behind the failure:
Hypervisor for ubuntu-server-12042-x64 is vagrant
Beaker::Hypervisor, found some vagrant boxes to create
/opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/bundler/gems/beaker-7c88b74abbf1/lib/beaker/hypervisor/vagrant.rb:166:in `block (2 levels) in vagrant_cmd': Failed to exec 'vagrant destroy --force'. Error was /opt/rubies/2.0.0-p451/lib/ruby/gems/2.0.0/gems/bundler-1.7.9/lib/bundler/rubygems_integration.rb:256:in `block in replace_gem': vagrant-wrapper is not part of the bundle. Add it to Gemfile. (Gem::LoadError) (RuntimeError)

I've found this doesn't happen with a vanilla bash shell, only zsh...

Yep, I'm on a new machine without oh-my-zsh, using bash dotfiles and this works fine without having to delete the vagrant shim or install vagrant-wrapper, I think this is probably a pathing issue.

@kevpl can you take a look at this?  I don't run zsh...

Follow up here:
https://tickets.puppetlabs.com/browse/BKR-19


Is this project still being maintained?

It has been a while since an update was released. Is this project still alive?

Yes


Extension Host Terminated

Issue Type: Bug
I recently started receiving the Extension Host Terminated error (_onExtensionHostCrashed @ extensionService.ts:450). I removed all the extensions and still received the error. I uninstalled and deleted all related folders and reinstalled VSCode and still get this error.
Now I do not know what to do.
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.85GB (10.00GB free)

Process Argv
--open-url -- vscode://vscode.git/clone?url=https://ryder-vsts.visualstudio.com/SFDC/_git/sfdc

Screen Reader
no

VM
0%

Extensions: none

Can you see if there's information in any of the logs (View > Output > ...) and run with --verbose.

I do not see any logs. Should I be looking in a particular place?

From the global menu, invoke View > Output, then in the output view check the output logs

closing because this issue is without actionable information


Compiler assertion failure

Reproduction code:
actor Main
  new create(env: Env) =>
    None

  fun msg(s: String val = String) =>
    lambda()(s) =>
      None
    end

Compiler output:
ponyc: src/libponyc/ast/ast.c:425: ast_id: Assertion `ast != ((void *)0)' failed.
Aborted

Pulled ponyc 5 minutes ago on Debian Sid kernel 4.3.0 AMD64 with LLVM 3.6.2.

Confirmed. Backtrace from lldb:
(lldb) bt
* thread #1: tid = 0x1d6607e, 0x00007fff8c89f0ae libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x00007fff8c89f0ae libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff8963e500 libsystem_pthread.dylib`pthread_kill + 90
    frame #2: 0x0000000100bcb256 ponyc`abort + 22
    frame #3: 0x0000000100bcb240 ponyc`__assert_rtn + 81
    frame #4: 0x0000000100001e5d ponyc`ast_id(ast=0x0000000000000000) + 77 at ast.c:425
    frame #5: 0x00000001000b3862 ponyc`alias(type=0x0000000000000000) + 34 at alias.c:177
    frame #6: 0x000000010006ebdd ponyc`make_capture_field(opt=0x00007fff5fbff988, capture=0x000000010aada700) + 893 at lambda.c:53
    frame #7: 0x000000010006dc6c ponyc`expr_lambda(opt=0x00007fff5fbff988, astp=0x00007fff5fbff3c0) + 396 at lambda.c:96
    frame #8: 0x0000000100086ee5 ponyc`pass_expr(astp=0x00007fff5fbff3c0, options=0x00007fff5fbff988) + 1205 at expr.c:262
    frame #9: 0x000000010008aecf ponyc`ast_visit(ast=0x00007fff5fbff3c0, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 703 at pass.c:374
    frame #10: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff450, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #11: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff4e0, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #12: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff570, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #13: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff600, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #14: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff690, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #15: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff720, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #16: 0x000000010008ae1d ponyc`ast_visit(ast=0x00007fff5fbff848, pre=(ponyc`pass_pre_expr at expr.c:178), post=(ponyc`pass_expr at expr.c:195), options=0x00007fff5fbff988, pass=PASS_EXPR) + 525 at pass.c:349
    frame #17: 0x000000010008b806 ponyc`visit_pass(astp=0x00007fff5fbff848, options=0x00007fff5fbff988, last_pass=PASS_ALL, out_r=0x00007fff5fbff813, pass=PASS_EXPR, pre_fn=(ponyc`pass_pre_expr at expr.c:178), post_fn=(ponyc`pass_expr at expr.c:195)) + 182 at pass.c:164
    frame #18: 0x000000010008b284 ponyc`ast_passes(astp=0x00007fff5fbff848, options=0x00007fff5fbff988, last=PASS_ALL) + 692 at pass.c:227
    frame #19: 0x000000010008afc5 ponyc`ast_passes_program(ast=0x000000010afefcc0, options=0x00007fff5fbff988) + 37 at pass.c:244
    frame #20: 0x00000001000ab202 ponyc`program_load(path="issue-980", opt=0x00007fff5fbff988) + 194 at package.c:798
    frame #21: 0x00000001000014af ponyc`compile_package(path="issue-980", opt=0x00007fff5fbff988, print_program_ast=false, print_package_ast=false) + 47 at main.c:215
    frame #22: 0x0000000100001362 ponyc`main(argc=2, argv=0x00007fff5fbffa20) + 1138 at main.c:347
    frame #23: 0x00007fff9c0c15ad libdyld.dylib`start + 1

@Scramblejams there's actually an error in the code. It compiles if you recover the default assignment to s, since s is a val but String returns a ref:


Missing instructions for File Sync network throttling

Hey team, I've tried to find information regarding how to throttle Azure File Sync and couldn't locate any info. I found an externally published article here https://charbelnemnom.com/how-to-control-azure-file-sync-bandwidth-with-network-qos-azurefiles-azurefilesync/
Any chance we could have the full reference for the Powershell module added to docs?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 61bb35a5-e2f3-1ce8-1d6e-a926374de6c8
Version Independent ID: e4b3065a-5351-26ef-cdbb-ef2eaea3f301
Content: Deploy Azure File Sync
Content Source: articles/storage/files/storage-sync-files-deployment-guide.md
Service: storage
Sub-service: files
GitHub Login: @roygara
Microsoft Alias: rogarana

@LilacBrandy Thanks for your question. We are checking on this and will respond to you soon.

@LilacBrandy  Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.
Thanks for the feedback! Are you facing any kind of throttling issue are you facing? If so I would like to work closer on this issue.
I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/  We'll follow up there.  Based on your blog (suggestion) Let me check on that,  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Allow secret references to be full paths

This removes the limitation of forcing secrets to be in /var/run/secrets and allows arbitrary paths.  Note: these are still bind mounted and on tmpfs.
Refs https://github.com/docker/docker/pull/32336#issuecomment-293035306

ping @diogomonica
This also has the side effect of fixing https://github.com/docker/docker/issues/31897

LGTM

LGTM

There is a failing test
--- FAIL: TestSecretValidation (0.07s)
	Error Trace:	service_test.go:503
	Error:		Not equal: 0x3 (expected)
			        != 0x0 (actual)

	Error Trace:	service_test.go:503
	Error:		Not equal: 0x3 (expected)
			        != 0x0 (actual)

	Error Trace:	service_test.go:503
	Error:		Not equal: 0x3 (expected)
			        != 0x0 (actual)

	Error Trace:	service_test.go:503
	Error:		Not equal: 0x3 (expected)
			        != 0x0 (actual)

Other than one nitpick about the test, LGTM

Force pushed to rebase and add cases to the test, PTAL

LGTM, thanks @aaronlehmann and @ehazlett!


[SPARK-43356][K8S] Migrate deprecated createOrReplace to serverSideApply

What changes were proposed in this pull request?

The deprecation message of createOrReplace indicates that we should change createOrReplace to serverSideApply instead.
@deprecated please use {@link ServerSideApplicable#serverSideApply()} or attempt a create and edit/patch operation.

The change is not fully equivalent, but I believe it's reasonable.

With the caveat that the user may choose not to use forcing if they want to know when there are conflicting changes.
Also unlike createOrReplace if the resourceVersion is set on the resource and a replace is attempted, it will be optimistically locked.

See more details at https://github.com/fabric8io/kubernetes-client/pull/5073
Why are the changes needed?

Remove usage of deprecated API.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Pass GA.

cc @dongjoon-hyun @Yikun

How many PRs do you want to make

No overall estimate, I have been working on this area recently, and would like to propose change when I find something has room for improvement.

Then, let's hold on this PR for a while because we don't need to take any risk.

We are now using 6.7.0. Could you rebase it to the master branch?

rebased on the latest master branch

Looks reasonable to me pending @dongjoon-hyun's review


feat(CheatCode): roll(to)

The goal is to allow a dev to run cheatCodes.roll(to) in their test and have the global.blockNumber return to at next execution.
This must:

Change the constraints on the block number in the decoder
Change how the block number is retrieved in the globals

When you doglobal_variables.blocknumber in an open function in noir, public processer fetches the value from the archiver (specifically L2Source.getBlockHeight()). So we would need a new test client where we can set a block height at the archiver
On the contract side though it should be manageable since the contract doesn't store the block number. We just need the to re-compute the startStateHash with the new block number - 1  as seen here. And store this value in the rollup contract's rollupStateHash variable

On the archiver side - It boils down to adding empty blocks into the archiver store to fool archiver into thinking to is the nextExpectedL2BlockNum (ref here).
I can't see any good ways to add these empty blocks into the archiver store other than forcing the sequencer to post to - currL2Block number of empty blocks into the rollup contract, which can take a lot of time.
(Obviously, the other way is creating a test client that has an addEmptyL2BlocksIntoStore() which we can call but it requires us to create a test client)

Closed, see https://github.com/AztecProtocol/aztec-packages/issues/1259 for more information.


Few Changes Like File Upload and Paginator

Creating a PR to discuss required changes.

Also checked the Bulk upload, and it works. Just move that system into the students app.


LEXUS: Missing esp and engine FW versions in values.py

DongleId: 09ae96064ed85a14  | testRoute: 09ae96064ed85a14|2022-01-10--01-57-37

Looks like this is a hybrid and would throw can errors since it's looking for the ICE gas pedal signal.


Global Config errors

Hey,  just woke up today and im getting Global Config errors when trying to feed monsters!
Also  i get   Fail to load Wallet: Error while getting current Wallet

There was an issue with the nodeos that powers the game. Has been fixed by now.
Please verify if you still see problems.


Yuqingxie/add beir word piece

add arguana yaml and template

Codecov Report

Merging #1880 (051dfda) into master (2c70ebc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1880   +/-   ##
=========================================
  Coverage     57.74%   57.74%
  Complexity     1058     1058
=========================================
  Files           179      179
  Lines         10301    10301
  Branches       1417     1417
=========================================
  Hits           5948     5948
  Misses         3852     3852
  Partials        501      501

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 2c70ebc...051dfda. Read the comment docs.

Also remember to update README.md.

@lintool
Hi Jimmy, I uploaded the yaml and template for all the datasets, all python script passes the test. Could you double check and I will merge these changes.

For README.md, I will add in a separate PR.
Best,
Yuqing

Yes, please check in the auto-generated .md files also.


Create the ecms_api_recipient custom module

Summary
This PR adds the new ecms_api_recipient module to the system. Installing this module will create a new user, a new role, and a new consumer that is scoped with the created user and role. A later PR will manage enabling/disabling permission for the role above.
This is setting the groundwork for a site to receive content from a hub site via the JSON API.
Metadata

Question
Answer

Did you use a meaningful pull request title?
yes

Did you apply meaningful labels to the pull request?
yes

Did you perform a self review first?
yes

Documentation reflects changes?
yes

CHANGELOG reflects changes?
yes

Unit/Functional tests reflect changes?
yes

Did you perform browser testing?
yes

Risk level
Medium

Relevant links
RIG-55

@pfrilling Ok looks good after a rebase!
/approved


Locale switches back to default after setLocale

Version
nuxt-i18n: 6.13.12
nuxt: 2.12.2
Nuxt configuration
mode:

[x] universal
[x] spa

Nuxt-i18n configuration
  i18n: {
    lazy: true,
    langDir: '../locales/',
    locales: ..., // some dynamic code here
    strategy: 'prefix',
    defaultLocale: 'en',
    detectBrowserLanguage: {
      // If enabled, a cookie is set once a user has been redirected to his
      // preferred language to prevent subsequent redirections
      useCookie: true,
      // Cookie
      cookieKey: 'language',
      cookieSecure: true,
      // Set to always redirect to value stored in the cookie, not just once
      alwaysRedirect: true,
      // If no locale for the browsers locale is a match, use this one as a fallback
      fallbackLocale: 'en',
    },
  },

Steps to reproduce

I am on locale en
I select cs via $i18n.setLocale('cs');
cookie is successfuly updated to cs
nuxt-auth is redirecting to /cs
after next boot something - and I can't find it in the code (I put debugger to all places in plugin.main.js where redirection happens) - is redirecting back to /en
on visit of /en cookie is set back to en which is expected

What is Expected?
The redirect back to default locale does not happen

I can't really investigate without a reproduction repo.

@rchl
I did some more debugging and reading of docks and the issue is now clear to me.
It's the combination of alwaysRedirect and detectBrowserLanguage and useCookie.
When I setLocale that causes a redirect, after redirect the detectBrowserLanguage will prefer the browser language over the value from the cookie.
I'd expect the browser language would be used only if there's no cookie but the priority is different. I'm not sure if this is a bug or a feature though.
And then I found out that onlyOnRoot mostly fixes the issue for me.
But even still, even on / I'd expect that cookie has higher priority over browser language. Is that just me?

Is this clear? Should I still create the reproduction repo?

And then I found out that onlyOnRoot mostly fixes the issue for me.
But even still, even on / I'd expect that cookie has higher priority over browser language. Is that just me?

It's working fine. Redirecting based on cookie in the first place only on root path.

Yes, would need a repro to see what's wrong.

It's working fine. Redirecting based on cookie in the first place only on root path.

In my experience the cookie is read only if !finalLocale which comes from doDetectBrowserLanguage. So if the browser language detection succeeds, the cookie is not read.
https://github.com/nuxt-community/i18n-module/blob/master/src/templates/plugin.main.js#L265

In my experience the cookie is read only if !finalLocale which comes from doDetectBrowserLanguage. So if the browser language detection succeeds, the cookie is not read.

But doDetectBrowserLanguage will consider cookie before anything else: https://github.com/nuxt-community/i18n-module/blob/2e2658b3a061cf2a22ad216c357b344722a891a7/src/templates/plugin.main.js#L194
But it's possible that there is some logic error there with some combination of options. There are too many options...

So I couldn't reproduce in a different repo and it made me double check my main app code.
It turned out I had two cookies with different domains (somehow). I guess it was a leftover from much earlier. JsCookie.get(cookieKey) preferred it over the new one and that's why the language was switching wrongly for me.
Sorry for the time waste! I think this can be closed.


Build errors with GCC 13.2.0: no  in test/matrix_params.cc, and -fopenmp not passed to linker

Description
A clear and concise description of the bug and expected behavior.
Slate's tests failed to build in my environment. Specifically,
/home/chillenb/src/slate/test/matrix_params.cc: In constructor ‘MatrixParams::MatrixParams()’:
/home/chillenb/src/slate/test/matrix_params.cc:42:60: error: ‘INT64_MAX’ was not declared in this scope
   42 |     seed(       "seed",   0,    List,   -1,            -1, INT64_MAX,
      |                                                            ^~~~~~~~~
/home/chillenb/src/slate/test/matrix_params.cc:10:1: note: ‘INT64_MAX’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
    9 | #include <cmath>
  +++ |+#include <cstdint>
   10 |

The build progressed further when I added that line in, until the very end, when tester failed to link:
/easybuild/software/binutils/2.40-GCCcore-13.2.0/bin/ld: ../libslate.so: undefined reference to `__offload_func_table'
/easybuild/software/binutils/2.40-GCCcore-13.2.0/bin/ld: ../libslate.so: undefined reference to `__offload_vars_end'
/easybuild/software/binutils/2.40-GCCcore-13.2.0/bin/ld: ../libslate.so: undefined reference to `__offload_funcs_end'
/easybuild/software/binutils/2.40-GCCcore-13.2.0/bin/ld: ../libslate.so: undefined reference to `__offload_var_table'
collect2: error: ld returned 1 exit status
make[2]: *** [test/CMakeFiles/tester.dir/build.make:1212: test/tester] Error 1
make[1]: *** [CMakeFiles/Makefile2:428: test/CMakeFiles/tester.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

This went away when I set export CXXFLAGS=-fopenmp and started from the beginning, and then everything worked.
Steps To Reproduce

Occurred while following the installation instructions with CMake.

If it can be reproduced with SLATE's testers, that is best. Otherwise, including a minimal reproducer is super helpful.
Environment
The more information that you can provide about your environment, the simpler it is for us to understand and reproduce the issue.

SLATE version / commit ID (e.g., git log --oneline -n 1):
5b23aa5f (HEAD -> master, origin/master, origin/HEAD) Merge pull request #145 from Treece-Burgess/matgen

How installed:

[x] git clone
[ ] release tar file
[ ] Spack
[ ] module

How compiled:

[ ] makefile (include your make.inc)
[x] CMake (include your command line options)
 CXX=mpic++ FC=mpif90 cmake -Dblas=mkl --log-level=verbose ..

Compiler & version (e.g., mpicxx --version): g++ 13.2.0

BLAS library (e.g., MKL, ESSL, OpenBLAS) & version: Intel MKL 2023.2.0

CUDA / ROCm / oneMKL version (e.g., nvcc --version): None

MPI library & version (MPICH, Open MPI, Intel MPI, IBM Spectrum, Cray MPI, etc. Sometimes mpicxx -v gives info.): OpenMPI 4.1.6

OS: AlmaLinux 9.3 with EasyBuild gompi/2023b toolchain and kernel version 6.7.6

Hardware (CPUs, GPUs, nodes): One (Dell) node, 2 sockets, 48 cores, Intel Cascade Lake.

int64 is not supported in SLATE
From the installations instructions:
blas_int
    BLAS integer size to search for. One or more of:
    auto            search for both sizes (default)
    int             32-bit int (LP64 model)
    * int64         64-bit int (ILP64 model)
    * int64 is not currently supported in SLATE

I had to specify -Dblas_int=32 to compile against intel mkl correctly

Thanks for pointing that out!
Unfortunately, I still get the same compile error when I pass -Dblas_int=int. It happens with openblas too. The problem seems unrelated to ILP64 and is probably just because INT64_MAX didn't get defined.

mkl has 2 versions, ilp64 and lp64, you probably have to adjust your environment variables to point to the lp64 version
this can be done with the setvars.sh (or vars.sh) script in the intel mkl installation, if you followed their installation instructions it's not hard.
at the time I posted my first response I was able to compile slate using intel mkl (followed their webpage installation instructions, and how to set up the environment variables, it's not trivial without the documentation)
although I had issues compiling, they were not related to the project (ubuntu kernel is not compiled with gcc version 12.3, and the packet manager installs gcc 11.4 by default, this has caused a lot of headache for me)

Possibly related to #173.

@chillenb Is your OpenMP issue solved now in the master branch with #173 merged?

Hopefully yes. I will try it in an hour and let you know

Yes, it seems solved!

Thanks for your help


Timescaledb password error

I tried to install tobs using the CLI tool 'tobs install'. However, the promscale pod got a 'CrashLoopBackOff' status.
pod/tobs-promscale-6bc7f8f689-qltwh                    0/1     CrashLoopBackOff   5          4m35s
Checking the promscale pod log, I got some kind of authentication error
kubectl logs tobs-promscale-6bc7f8f689-qltwh
level=info ts=2021-06-25T16:33:20.098Z caller=runner.go:29 msg="Version:0.4.1; Commit Hash: level=info ts=2021-06-25T16:33:20.098Z caller=runner.go:30 config="&{ListenAddr::9201

 PgmodelCfg:{CacheConfig:{SeriesCacheInitialSize:250000 seriesCacheMemoryMaxFlag:{kind:0 value:50}
SeriesCacheMemoryMaxBytes:1625900646 MetricsCacheSize:10000 LabelsCacheSize:10000}<EMAIL_ADDRESS>Host:tobs.default.svc.cluster.local Port:5432 User:postgres password:**** Database:postgres SslMode:require DbConnectRetries:0
DbConnectionTimeout:1m0s IgnoreCompressedChunks:false AsyncAcks:false ReportInterval:0 WriteConnectionsPerProc:4
MaxConnections:-1 UsesHA:false DbUri: EnableStatementsCache:true} LogCfg:{Level:info Format:logfmt} APICfg:
{AllowedOrigin:^(?:.*)$ ReadOnly:false HighAvailability:false AdminAPIEnabled:false TelemetryPath:/metrics Auth:0xc000079c70
MultiTenancy:<nil> EnableFeatures: EnabledFeaturesList:[] MaxQueryTimeout:2m0s SubQueryStepInterval:1m0s
LookBackDelta:5m0s MaxSamples:50000000 MaxPointsPerTs:11000} LimitsCfg:{targetMemoryFlag:{kind:0 value:80}
TargetMemoryBytes:3251801292} TenancyCfg:{SkipTenantValidation:false EnableMultiTenancy:false AllowNonMTWrites:false
ValidTenantsStr:allow-all ValidTenantsList:[]} ConfigFile:config.yml TLSCertFile: TLSKeyFile: HaGroupLockID:0
PrometheusTimeout:-1ns ElectionInterval:5s Migrate:true StopAfterMigrate:false UseVersionLease:true InstallExtensions:true
UpgradeExtensions:true UpgradePrereleaseExtensions:false}"

level=error ts=2021-06-25T16:33:20.188Z caller=runner.go:40 msg="aborting startup due to error" err="failed to connect to
`host=tobs.default.svc.cluster.local user=postgres database=postgres`: server error (FATAL: password authentication failed for
user \"postgres\" (SQLSTATE 28P01))"

I am using the version 0.4.1
tobs version -d

Tobs CLI Version: 0.4.1, deployed tobs helm chart version: 0.4.1

The other components are running.
Any clues?
Thank you

@adonaiarruda It looks like Promscale password authentication is failing with TimescaleDB. Can you check the underlying secret that holds passwords are mounted properly in both Promscale & TimescaleDB?
I haven't seen this issue in our deployments or not heard from other users. Looks weird.
To know TimescaleDB password you can use below cmd:
tobs timescaledb get-password

Hello,
Seems all secrets are created sucessfully:
kubectl get secrets

NAME                                                        TYPE                                  DATA   AGE
alertmanager-tobs-kube-prometheus-alertmanager              Opaque                                1      57s
alertmanager-tobs-kube-prometheus-alertmanager-generated    Opaque                                1      52s
alertmanager-tobs-kube-prometheus-alertmanager-tls-assets   Opaque                                0      52s
default-token-lc5tn                                         kubernetes.io/service-account-token   3      3d2h
prometheus-tobs-kube-prometheus-prometheus                  Opaque                                1      52s
prometheus-tobs-kube-prometheus-prometheus-tls-assets       Opaque                                1      52s
sh.helm.release.v1.tobs.v1                                  helm.sh/release.v1                    1      59s
tobs-certificate                                            Opaque                                2      67s
tobs-credentials                                            Opaque                                3      67s
tobs-grafana                                                Opaque                                3      57s
tobs-grafana-datasources                                    Opaque                                1      57s
tobs-grafana-db                                             Opaque                                6      57s
tobs-grafana-test-token-v7nzv                               kubernetes.io/service-account-token   3      56s
tobs-grafana-token-gbxjn                                    kubernetes.io/service-account-token   3      57s
tobs-kube-prometheus-admission                              Opaque                                3      27m
tobs-kube-prometheus-alertmanager-token-tlxsl               kubernetes.io/service-account-token   3      56s
tobs-kube-prometheus-operator-token-67c25                   kubernetes.io/service-account-token   3      56s
tobs-kube-prometheus-prometheus-scrape-confg                Opaque                                1      57s
tobs-kube-prometheus-prometheus-token-7vcvg                 kubernetes.io/service-account-token   3      57s
tobs-kube-state-metrics-token-v2f8x                         kubernetes.io/service-account-token   3      57s
tobs-prometheus-node-exporter-token-48fj9                   kubernetes.io/service-account-token   3      56s
tobs-timescaledb-token-r82tz                                kubernetes.io/service-account-token   3      57s

checking if the password present in tobs-credentials secret and the corresponding timescaleDB password, there seems to be no problem either.
kubectl get secret tobs-credentials -o jsonpath='{.data}'

{"PATRONI_REPLICATION_PASSWORD":"a3REMGJQN3hNSQ==","PATRONI_SUPERUSER_PASSWORD":"cHFDemtlSmxXZg==","PATRONI_admin_PASSWORD":"NDhtSVB6eVp0Uw=="}

echo 'cHFDemtlSmxXZg==' | base64 --decode

pqCzkeJlWf

The timescaleDB password is:
tobs timescaledb get-password
pqCzkeJlWf
Also, seems the promscale deploy is using the correct key inside the credentials secret.
kubectl describe deploy tobs-promscale
...
Environment:
      PROMSCALE_DB_PORT:      5432
      PROMSCALE_DB_USER:      postgres
      PROMSCALE_DB_PASSWORD:  <set to the key 'PATRONI_SUPERUSER_PASSWORD' in secret 'tobs-credentials'>  Optional: false
      PROMSCALE_DB_HOST:      tobs.default.svc.cluster.local
      PROMSCALE_DB_NAME:      postgres
      PROMSCALE_DB_SSL_MODE:  require
    Mounts:                   <none>
  Volumes:                    <none>
...

Interesting.... Are you able to access the database using this password? It looks like TimescaleDB isn't mounted to the same secret that Promscale is using though the tobs timescaledb get-password is showing the same password.
I haven't encountered this issue anytime. Can we get on to a call to debug this issue? If you are already in TimescaleDB slack feel DM @Vineeth

The problem disappeared after upgrading the kubernetes cluster version from 1.20 to 1.21.2. I'm not sure this update solved the issue.
In time, how is it possible to use nodeSelector feature in tobs pods? I couldn't find an option for this using the configuration via values.yaml.

So tobs uses multiple helm charts like timescaledb-single, kube-prometheus you can configure nodeSelector under each of these components to configure scheduling per node basis.
For example timescaledb-single can be configured using:
timescaledb-single:
  nodeSelector:

So after jumping into the call with @adonaiarruda, We understood the issue is from creating pv, pvcs manually by the user.  The timescaledb helm chart will create persistent volume claims. which shouldn't be handled manually by the user. So the password mounting for timescaledb is disturbed here.
However, changing the timescaledb password to the password created by tobs CLI fixed this problem. So pv, pvcs creation shouldn't be handled manually by the user, timescaledb helm chart will create them for you.

Thank you @VineethReddy02 for your time helping to solve this issue!


Expose store state

Summary of Changes

Added logic to get proxy trap to facilitate store state retrieval.

Pull Request Test Coverage Report for Build 351

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 90.95%

Totals

Change from base Build 330:
0.2%

Covered Lines:
136

Relevant Lines:
148

💛  - Coveralls

Thank you 🙂


Fix/use auth methods

Fixes #25

I just realized this should probably go into master. Do you guys have a preference?

Thanks for submitting this fix. Develop branch is perfect, it will get automerged and tagged once it runs through CI successfully.
We will pull it in and it should make it into the next cfops release, sometime next week.


DM-40448: Restructure application config for environments

Previously, enabling and disabling environments was done via a top-level block for each application in values-.yaml, with one key (enabled) that controlled whether it was enabled. This meant changing the top-level keys every time a new application was added, and made it difficult to do schema checking for the values files for each environment.
Instead, move the application configuration under a top-level applications key, and adjust the Argo CD configuration accordingly. Enable some applications by default (cert-manager, gafaelfawr, ingress-nginx, vault-secrets-operator), and add argocd to the list of applications defined and enabled in values.yaml to make parsing easier and avoid needing that special case. The enabled applications are now represented by a merger of the values.yaml and values-.yaml file. Drop unnecessary overrides, so each environment no longer needs to list and explicitly disable every application that it doesn't want.
The current installer doesn't entirely understand the new structure. Hack around that for now by embedding assumptions about which applications are always enabled. The installer will be replaced with new code that's aware of this structure later.

This is mostly mechanical. The code changes are probably the interesting bits.


Missing ETH after RUNE to ETH Swap on ASGARDEX

Missing 3.7043 ETH after swap of RUNE using ASGARDEX Desktop APP in MAC/OS
https://thorchain.net/#/txs/F902AB5E597A6E17A79EAB055613E9355214D79E05A2C18A0CAF452B26E3AE20

updates...the ETH is showing on Etherscan but not on Asgardex.....some help would be appreciated.  This has been open 16 hours and no response as of yet.

funds have now appeared in wallet...thx


[14.0.x] ISPN-16302 Fails to read cache files inside cache folder in Infinispa…

https://issues.redhat.com/browse/ISPN-16302
…n with Java 21

Some related failures.

Integrated into 14.0.x, thanks @jabolina !


Fix field name syntax tree

There was an extraneous layer to identifier name AST nodes, in wasted anticipation of needing to grab the location of a field name for error reporting.

r @malandrew @jcorbin

less stutter, less problems; lgtm


Focus on people as the primary

Context and Problem Statement
People are primary to Social VR and not the environment.
Describe the proposed option and how it helps to overcome the problem or limitation
VR is social.
What is the environment?
We cannot take people out of the environment?
One observer?  Blossoms out because now you can synthesize new virtual realities to role-play on the fly through improvisation.
Three? a crowd. Chaotic?
We can not use a head-mounted display, but there is still value.
Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams
Pending design.
Positive Consequences
No response
Negative Consequences
No response
Option graveyard
No response
If this enhancement will not be used often, can it be worked around with a few lines of script?
This is a user story.
Is there a reason why this should be core and done by us?
Why do we create V-Sekai?
References

V-Sekai

License of the contribution
Copyright (c) 2022 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Need to write this as a format proposal because it's an aspiration essay and then close.

This is an aspirational manifesto.


No Frames Received & D455 go offline frequently

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 18.04)

Kernel Version (Linux Only)
JETPACK 4.5.1

Platform
NVIDIA Jetson

SDK Version
2.50

Language
C++

Segment
3D  measure

Issue Description
THIS CAMERA ARE DRIVING ME MAD QAQ.....................
I got 3 x realsense D455 connect to nvidia jetson nano via usb hub.
First of all, the usb hub got individual power support, I am sure that every camera got good power support.
Second, My project open D455 one by one, always close this one before next open streaming. So the situation that three cameras are turned on at the same time does not exist.
Everything seems ok but when I capture from three cameras one by one，something goes wrong.
It have two outcomes.
1.All realsense cameras "offline",It means u can not see them both via realsense-viewer or "lsusb"
2.You can see them online, also u can find them in realsense-viewer, but color frame goes wrong and "no frames arrived"

So in my programme i will got rs2::error no device connect or rs2::error frames time out.
These fatal errors have made my programme unusable.
How to avoid frames time out or camera offline?????Need help!

if realsense-viewer can not receive color frame,it pop out tons error like this:
04/03 03:01:08,552 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
04/03 03:01:08,583 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
04/03 03:01:08,617 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
04/03 03:01:08,648 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
04/03 03:01:08,715 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
04/03 03:01:08,750 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
04/03 03:03:24,716 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_STREAMON) failed for buf_type=1 Last Error: Cannot allocate memory
04/03 03:03:31,792 WARNING [548120019392] (ds5-timestamp.cpp:69) UVC metadata payloads not available. Please refer to the installation chapter for details.
04/03 03:03:34,009 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_STREAMON) failed for buf_type=1 Last Error: Cannot allocate memory
04/03 03:03:50,770 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_STREAMON) failed for buf_type=1 Last Error: Cannot allocate memory
04/03 03:03:54,238 ERROR [548435464208] (librealsense-exception.h:52) xioctl(VIDIOC_STREAMON) failed for buf_type=1 Last Error: Cannot allocate memory

Hi @Wilson-shuo  The xioctl(VIDIOC_G_CTRL) errors indicate that there may be a conflict with the kernel.  What method did you use to install the librealsense SDK on your Jetson, please?

I installed SDK by clone source code from github, makeinstall after cmake.

Installation of the SDK on Jetson boards from source code requires the application of a dedicated kernel patch for Jetson by running a script called ./scripts/patch-realsense-ubuntu-L4T.sh
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md
If the SDK is built from source code with CMake using the RSUSB Backend installation method detailed at https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-707501049 then the kernel is bypassed and it is not necessary to apply the patch.

Installation of the SDK on Jetson boards from source code requires the application of a dedicated kernel patch for Jetson by running a script called ./scripts/patch-realsense-ubuntu-L4T.sh
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md
If the SDK is built from source code with CMake using the RSUSB Backend installation method detailed at #6964 (comment) then the kernel is bypassed and it is not necessary to apply the patch.

Hi！ Deeply thanks for u reply.
I have tried this shell script, after that follow u instruction to install SDK again.
I found compile with “CUDA ON” do help with latency（I noticed that timestamp no more go deep red in realsense-viewer）
But the realsense camera still keeps go offline....................
Most of the situations is color frame do not arrive in 5s.
Also if one camera"s color frame time out, It will keep time out all the time no matter you reboot jetson how many times.
We could not plug out camera everytime, cause our device set on the ceiling.
Even use "handware reset" can not solve the problem.
Any other suggestions？

Size 214016 out of 814335 bytes (26%)
06/03 13:50:17,553 WARNING [547004346816] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 459776 out of 814335 bytes (56%)
06/03 13:50:17,621 WARNING [547004346816] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 590848 out of 814335 bytes (72%)
06/03 13:50:17,623 WARNING [547264389568] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 279552 out of 814335 bytes (34%)
06/03 13:50:17,685 WARNING [547004346816] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 525312 out of 814335 bytes (64%)
06/03 13:50:17,686 WARNING [547247604160] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 214016 out of 814335 bytes (26%)
06/03 13:50:17,794 WARNING [547255996864] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 246784 out of 814335 bytes (30%)
06/03 13:50:17,818 WARNING [546987561408] (backend-v4l2.cpp:1062) Incomplete frame received: Incomplete video frame detected!
Size 279552 out of 814335 bytes (34%)
06/03 13:50:25,879 WARNING [547264389568] (backend-v4l2.cpp:1127) Frames didn't arrived within 5 seconds
06/03 13:50:25,904 WARNING [547222426048] (backend-v4l2.cpp:1127) Frames didn't arrived within 5 seconds
06/03 13:50:25,904 WARNING [547004346816] (backend-v4l2.cpp:1127) Frames didn't arrived within 5 seconds
06/03 13:50:25,909 WARNING [547247604160] (backend-v4l2.cpp:1127) Frames didn't arrived within 5 seconds
06/03 13:50:25,929 WARNING [546987561408] (backend-v4l2.cpp:1127) Frames didn't arrived within 5 seconds
06/03 13:50:27,018 ERROR [546979168704] (librealsense-exception.h:52) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,018 ERROR [546979168704] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,031 ERROR [546953990592] (librealsense-exception.h:52) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,032 ERROR [546953990592] (error-handling.cpp:78) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,032 ERROR [546870129088] (librealsense-exception.h:52) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,054 ERROR [546870129088] (ds5-thermal-monitor.cpp:94) Error during thermal compensation handling: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,135 ERROR [546735911360] (librealsense-exception.h:52) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,136 ERROR [546735911360] (error-handling.cpp:78) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,136 ERROR [547272782272] (librealsense-exception.h:52) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,137 ERROR [547272782272] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,142 ERROR [546727518656] (librealsense-exception.h:52) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,142 ERROR [546727518656] (ds5-thermal-monitor.cpp:94) Error during thermal compensation handling: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,267 ERROR [547502670272] (librealsense-exception.h:52) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,267 ERROR [547502670272] (ds5-thermal-monitor.cpp:94) Error during thermal compensation handling: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,268 ERROR [546685555136] (librealsense-exception.h:52) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,269 ERROR [546685555136] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
06/03 13:50:27,269 ERROR [547373429184] (librealsense-exception.h:52) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device

The Incomplete video frame detected! warning is highly rare but more likely to occur on Jetson boards such as the one that you are using.  https://github.com/IntelRealSense/librealsense/issues/10379 offers advice for resolving it.

The Incomplete video frame detected! warning is highly rare but more likely to occur on Jetson boards such as the one that you are using. #10379 offers advice for resolving it.

Ok thanks, any more idea about color frame do not arrive in 5 seconds? we tried the kernel patch but it does not work.

检测到不完整的视频帧**！**警告非常罕见，但更可能发生在 Jetson 开发板上，例如您正在使用的开发板。 #10379提供了解决它的建议。

For the "Incomplete frame", I open 3 x depth streams (848x480,5FPS) and 3 x color streams(848x480,5FPS) ,after a while all camera will offline and I could not find them both in "lsusb" and realsense-viewer. I will try u suggestion.

The Incomplete video frame detected! warning is highly rare but more likely to occur on Jetson boards such as the one that you are using. #10379 offers advice for resolving it.

For the "Incomplete frame", I open 3 x depth streams (848x480,5FPS) and 3 x color streams(848x480,5FPS) ,after a while all camera will offline and I could not find them both in "lsusb" and realsense-viewer. I will try u suggestion.

If the cameras behave normally at first but time-out or disconnect later, it is possible that repeated stop-start of the three cameras may be causing a memory leak. This is where the available memory capacity is progressively consumed until a program becomes unstable.
You can test for a memory leak in Ubuntu by using a system monitoring tool such as htop and watching the available memory in real-time whilst the program is running. If the amount of memory is declining then this would be an indication that a memory leak is occurring on each stop of the camera and using up a further chunk of memory, thus destabilizing the program.

thank you! I will pay attention to memory leaks. However, the current problem is that if the camera is turned on once and turned off, the color frame will time out the next time when the camera is turned on. If it is a memory leak problem, it should be OK to turn on the camera after ”reboot“ jetson. But the fact is that the color frame still times out after ”reboot“.

Are all three cameras sharing the same pipeline and you have not created multiple pipelines (one for each camera)?
If you are using the same pipeline for all three cameras, are you identifying the cameras by their unique serial number so that the program knows which camera it is activating when one has been stopped and another of the three is started?
For example, after a Stop() instruction, use a cfg configuration instruction to define the serial number of the next camera to be activated and then Start() with that configuration, making sure to place the config / cfg name in the brackets so that the script knows to use the defined configuration.
pipe.stop();

cfg.enable_device(serial);

pipe.start(cfg);

Where 'serial' contains the serial number of the camera to be activated next, or you can hard-code the serial number into the brackets.
cfg.enable_device('123456789');

Thanks very much for the code listing.
You should not need to use m_pipeline_cfg.disable_all_streams(); as the pipeline stop instruction will close all the streams on that camera anyway.
The No Frames Received problem that your video demonstrates can occur if another program that is using the camera streams is already running. For example, if you run a program that you have created yourself and then afterwards open realsense-viewer and try to enable the depth or color stream then No Frames Received is displayed. If the first program is closed and then a stream in the realsense-viewer is activated, the stream enables.
The reverse is also true. If you first enable streams in realsense-viewer and then launch another program, the realsense-viewer streams will work but the streams in the secondly-launched program will not.
Below, this effect is demonstrated by launching rs-capture first and then secondly trying to enable RGB in realsense-viewer.

The reason why this occurs is that by the operating rules of the RealSense SDK, once a stream is enabled on a particular camera then the program that enabled it places a 'claim' on that stream. This prevents another program from accessing the same stream on that camera until the stream is disabled in the first program and the claim is released, allowing another program to use it.

I am sure that only one program is using realsense-sdk. My program will start at system boot up, but it will not open camera or do any operation until 20 mins later. My program is managed by a 20 min timer. So in my youtube viedo I use "ctl + c" killed my program immediately after reboot，then immediately launched realsense-viewer，So it is impossible to get multiple program use one sdk api at the sametime.

https://user-images.githubusercontent.com/24606639/223942151-07cf94f5-982b-4fcc-b81e-26fdda18ca7d.mp4
I could show u this video.  you can see that only realsense-viewer itself control all streams, after a while suddenly color frames go time out but depth frames go well as normal.

Looking at your YouTube video again and its warning message about the V4L2 backend, and also your mention of using the L4T shell script during installation, it looks as though you are installing the SDK from source code and building the SDK in V4L2 backend mode.  This mode relies on the Jetson kernel to operate correctly.
When performance with a kernel-based SDK build is unstable, building from source code with the RSUSB backend mode can often resolve the problem.  Whilst RSUSB is not as ideally suited to multiple camera applications as the V4L2 backend, it can work with multicam.  And as you are starting and stopping individual cameras rather than planning to have three cameras active simultaneously, RSUSB backend should be fine.
You can build in RSUSB backend mode by using the CMake build flag -DFORCE_RSUSB_BACKEND=true and not using the L4T shell script (as you do not need to patch the kernel with an RSUSB build).

Looking at your YouTube video again and its warning message about the V4L2 backend, and also your mention of using the L4T shell script during installation, it looks as though you are installing the SDK from source code and building the SDK in V4L2 backend mode. This mode relies on the Jetson kernel to operate correctly.
When performance with a kernel-based SDK build is unstable, building from source code with the RSUSB backend mode can often resolve the problem as it bypasses the kernel and so is not dependent on Linux versions or kernel versions. Whilst RSUSB is not as ideally suited to multiple camera applications as the V4L2 backend, it can work with multicam. And as you are starting and stopping individual cameras rather than planning to have three cameras active simultaneously, RSUSB backend should be fine.
You can build in RSUSB backend mode by using the CMake build flag -DFORCE_RSUSB_BACKEND=true and not using the L4T shell script (as you do not need to patch the kernel with an RSUSB build).
Also, if using a powered USB hub would be inconvenient for your project, you could first try using a passive USB hub (one that draws its power from the computer instead of the mains electricity socket). A USB hub should have a different brand of USB controller to the ones that the built-in ports use, so this can help to confirm whether a USB instability on built-in ports is caused by the particular brand of USB controller that the computer's ports use.

https://user-images.githubusercontent.com/24606639/224530074-3fa117e2-8c53-4482-9e71-1d747fed0d7e.mp4
Change USB backend seems helpless.......
Still get no frames arrived......

Looking at your latest video, the log error Failed to read busnum/devnum is a highly rare error.  On the occasions in the past when it has been reported, it has almost always been an issue that occurs on very small-sized single-board devices and is related to insufficient power being provided to the camera by the USB connection.
If the ports on the Nano are working correctly then it could also suggest a possible problem with the USB cable being used with the camera.  Are you using the official 1 meter cable supplied with the camera or a longer USB cable of your own choice, please?

We connect camera by USB-fibre-optical device. Our camera is connected to the USB-to-fiber module with independent power supply. The network signal is transmitted to the Jetson nano 50m away through the fiber, and then converted to USB.

It is possible to have a RealSense camera up to 100 meters away from the computer when using fiber-optic cable, as demonstrated by the premium-quality USB equipment supplier Newnex in the video below, by using an optical repeater device (a Firenex 5000H in the video).
https://www.youtube.com/watch?v=GLQgR1jT04M&t=129s
Is your USB-to-fiber module an optical repeater, please?

Yes，We use a fiber module to convert usb signal to light signal, so it could transport more than 50m. then convert light signal back to usb signal and plug into jetson nano.

On RUSB backend，We found that "Handware reset" on realsense-viewer could remove the “timeout status” of the realsense device. Could I use Cpp code to “Handware reset” a specific device（by SN number）?

https://github.com/IntelRealSense/librealsense/issues/9287#issuecomment-867826974 has a C++ script for looping through all attached RealSense cameras and performing hardware_reset() on them.
There is only a Python example available at https://github.com/IntelRealSense/librealsense/issues/5428#issuecomment-564482167 regarding resetting a specific device by serial number, though the C++ equivalent should be similar.

Hi we found a new bug.
When use RUSB backend, one of the three cameras will go offline. can not find it via realsense-viewer.
Through "lsusb" we can see 3x VIA Lab device,but only 2x Intel device. Reboot does not work.

We think that might be a random error,until both jetson nano goes wrong.

Hi @Wilson-shuo  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Can't find ModelReferences in documentation

In docs/getting_started.rst, last line tells about ModelsReference but there is no link or anything. Am I missing something?
Regards,
Carl

bump

bump

bump

Closing in favor of #720.


java file uses over overrides a deprecated API

whilst building the example app on an android device.
Resolving dependencies...
Running 'gradlew assembleDebug'...
Note: /Users/user/Development/flutter/.pub-cache/hosted/pub.dartlang.org/lamp-0.0.5/android/src/main/java/plugins/flutter/lamp/lamp/LampPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Built build/app/outputs/apk/debug/app-debug.apk.

the problem is, that for android this library uses the deprecated android.hardware.Camera, which is only supported up to android sdk version 20
for higher versions using android.hardware.camera2 is recommendet
on my side I tried to change the LampPlugin, and it compiles without errors, sadly the light still wont turn on


Fix/services links

Task: https://openforge.teamwork.com/#/tasks/15467718

Fixed the JuntoScope download links
Removed StartupWars download buttons (because there are no links)
Set DigiThermo download links
Fix copyright symbol on JunstoScope description

The apple link for Digithermo opens to Spanish page, remove /es from the URL

DigiThermo link fixed


Write unit-test cases for new/modified methods in scope/probe/kubernetes/reporter.go.

FEATURE REQUEST:

Write unit-test cases for the methods that are newly added or modified in the file: scope/probe/kubernetes/reporter.go.
The test-cases have to be written in scope/probe/kubernetes/reporter_test.go.
Ensure that the test cases are not too complicated. Follow the guidelines https://github.com/openebs/openebs/blob/master/contribute/CONTRIBUTING-TO-DEVELOPER-DOC.md

@hellozee Please feel free to pick this issue.

@satyamz nice


Get running and silence warnings

Change to path construction, use numpy errstate

@eccoope can't really view the diff here, because the notebook gets re-run and the figures are regenerated, so github thinks those lines are changed.
Here's what I changed:
from pvanalytics.features import clipping
base_dir = pathlib.Path('.')

I prefer to import the parent module rather than only the function, it's easier for me to know where geometric came from.
Changed comments about voltage limits to read "MPPT maximum" and "MPPT minimum"
In wrapper, silence divide by zero warnings
    # Calculate voltage ratio
    with np.errstate(divide='ignore'):
        vmp_ratio = np.divide(voltage, modeled_vmp, where=((voltage > 0) & (modeled_vmp>0)))

Next step is to separate the modeled_vmp and other modeled quantities so that a user isn't required to use SAPM.


Dot it work for telegram mini-app/web3 invite?

It depends how bot count invited referrals if /start command is enough then it works

but when you click /start there is a inbuild page will opened. please check with the link
https://t.me/hamstEr_kombat_bot/start?startapp=kentId6688189689


LightTable 0.7.2 silently refuses to start up

I am trying to run a binary version of LightTable 0.7.2 under Gentoo. I have downloaded the archive from here, extracted it in ~/LightTable and issued ~/LightTable/Lightable. Nothing happened.
The bash script itself did execute (the symlink to /lib64/libudev.so.1 was created), and the branch of if at the end detected that it was in the terminal, but the call to ltbin exited within half a second (I tried it without &). It produces an error message if I run it without changing LD_LIBRARY_PATH, so at least it checks for shared libraries.
$ LD_LIBRARY_PATH=$(pwd) gdb ./ltbin
GNU gdb (Gentoo 7.7.1 p1) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./ltbin...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/pastafarianist/LightTable/ltbin
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe991a700 (LWP 22601)]
[New Thread 0x7fffe9119700 (LWP 22602)]
[New Thread 0x7fffe8918700 (LWP 22603)]
[New Thread 0x7fffe8117700 (LWP 22604)]
[New Thread 0x7fffe7916700 (LWP 22605)]
[New Thread 0x7fffe78f5700 (LWP 22606)]
[New Thread 0x7fffe78d4700 (LWP 22607)]
[New Thread 0x7fffe4e31700 (LWP 22608)]
[New Thread 0x7fffe062f700 (LWP 22609)]
[New Thread 0x7fffdfe2e700 (LWP 22610)]
[New Thread 0x7fffdf62d700 (LWP 22611)]
[New Thread 0x7fffdee2c700 (LWP 22612)]
[New Thread 0x7fffde62b700 (LWP 22613)]
[New Thread 0x7fffdde2a700 (LWP 22614)]
[New Thread 0x7fffdd629700 (LWP 22615)]
[New Thread 0x7fffdce28700 (LWP 22616)]
[Thread 0x7fffdce28700 (LWP 22616) exited]
[Thread 0x7fffdde2a700 (LWP 22614) exited]
[Thread 0x7fffde62b700 (LWP 22613) exited]
[Thread 0x7fffdee2c700 (LWP 22612) exited]
[Thread 0x7fffdf62d700 (LWP 22611) exited]
[Thread 0x7fffdfe2e700 (LWP 22610) exited]
[Thread 0x7fffe062f700 (LWP 22609) exited]
[Thread 0x7fffdd629700 (LWP 22615) exited]
[Thread 0x7fffe78d4700 (LWP 22607) exited]
[Thread 0x7fffe4e31700 (LWP 22608) exited]
[Thread 0x7fffe8918700 (LWP 22603) exited]
[Thread 0x7fffe78f5700 (LWP 22606) exited]
[Thread 0x7fffe7916700 (LWP 22605) exited]
[Thread 0x7fffe8117700 (LWP 22604) exited]
[Thread 0x7fffe9119700 (LWP 22602) exited]
[Thread 0x7fffe991a700 (LWP 22601) exited]
[Inferior 1 (process 22580) exited normally]

@Pastafarianist If you would, please try to build and run the latest version of the master branch and let us know if you can reproduce the issue:

LightTable/developer-install.md at master · LightTable/LightTable

@kenny-evitt the latest version compiled from the repository does not have this issue.

@Pastafarianist thanks. We're working on the next release but there's no reason why you can't or shouldn't run the local build of the latest source version. We'll follow-up sometime after the next release is available and confirm this is resolved.

@Pastafarianist 0.8.0-alpha is available - https://groups.google.com/forum/#!topic/light-table-discussion/rkfHTplo4ss . Let us know if this is still an issue

Seeing that master did fix your issue, this should be fixed with the alpha release. Ping us if it's still an issue

@cldwalker 0.8.0-alpha works fine for me. Thanks!


The New feature of instagram makes --fast-update malfunction

Describe the bug
A clear and concise description of what the bug is.
In June/2022, instagram introduced a new feature 'pin post', this feature help user put some old post to the top of their profile, however this also make the --fast-update malfunction whe those pinned post is older than latest post.
To Reproduce
Steps to reproduce the behavior:
(e.g. Instaloader command line)
instaloader --login=username --fast-update target_profile
Expected behavior
A clear and concise description of what you expected to happen (even if it seems obvious).
All latest post will be downloaded.
Error messages and tracebacks
If applicable, add error messages and tracebacks to help explain your problem.
No error message is occurred, however when the target is set a pinned post (which posted in the past), the latest post cannot be downloaded
Instaloader version
instaloader --version output.
4.9.1
Additional context
Add any other context about the problem here.
Feature suggested: --no-pinned to skip the pinned post, or skip the pinned post when using --fast-update

Related to #1582 and #1584


Interval?

Hi,
to be honest: I didn't try your solution yet.
I am currently using the Vzlogger2Mqtt-addon.
For me it es quite important, that I can slower the pushed values to HA. My smart meter is sending in a 5-sec-interval. Too much data. And I don't' want to use HA filters to keep the database slim.
Is it possible to just send smart meter events in a 60s interval to HA?
Thank you.

This is not supported by the component itself, but should be feasible with the esphome sensor filters:
https://esphome.io/components/sensor/index.html#sensor-filters

Thank you.


Error while calling public.powa_wait_sampling_src: invalid memory alloc request size<PHONE_NUMBER>

master: Error while calling public.powa_wait_sampling_src: invalid memory alloc request size<PHONE_NUMBER>
CONTEXT: SQL statement
"SELECT now(), COALESCE(pgss.dbid, 0) AS dbid, s.event_type, s.event, s.queryid, sum(s.count) as count FROM pg_wait_sampling_profile s
-- pg_wait_sampling doesn't offer a per (userid, dbid, queryid) view,
-- only per pid, but pid can be reused for different databases or users
-- so we cannot deduce db or user from it. However, queryid should be
-- unique across differet databases, so we retrieve the dbid this way.
-- Note that the same queryid can exists for multiple entries if
-- multiple users execute the query, so it's critical to retrieve a
-- single row from pg_stat_statements per (dbid, queryid)
LEFT JOIN (SELECT DISTINCT s2.dbid, s2.queryid FROM pg_stat_statements(false) s2 ) pgss
ON pgss.queryid = s.queryid
WHERE s.event_type IS NOT NULL AND s.event IS NOT NULL AND COALESCE(pgss.dbid, 0) NOT IN (
SELECT oid FROM powa_databases WHERE dropped IS NOT NULL) GROUP BY pgss.dbid, s.event_type, s.event, s.queryid" PL/pgSQL function powa_wait_sampling_src(integer) line 4 at RETURN QUERY

No idea on the reason.

Okay, did it; should I cleanup something to get rid of the error?

I suppose calling pg_wait_sampling_reset_profile() should be enough

Yes, it works!

No error, no data. Should something be restarted/reconfigured?

It shouldn't be needed.
Do you see any row in the powa_wait_sampling_history_current table of the powa repository server?  If not, do you see rows in the powa_wait_sampling_src_tmp table on the same repository server?

powa=# select count(*) from powa_wait_sampling_history_current ;
 count
-------
 21745
(1 row)

and still nothing in web interface

Right after your comment, everything reappeared.
(actually, I went from the Home button and now it works)


Pygrep -p all with --counts

Error when combining --pyreg all with --counts. Works fine with numerical values.

--pyreg capture groups undertook an overhaul to include up to 3 calls for a capture group, or an easier to to manipulate all keyword. The overhaul allowed the --counts to work.


Failed rule because of a miswritten value

Greetings,
Mediaconch has rules to test the video bitrate (BitRate and BitRate_Nominal) and for some vide sources it failes because both of this data are stored in the same filed in the file header
MediaConch Test Failed : Min Video Bitrate Nominal - Required value : 600000 / Received value : Undefined
MediaConch Test Failed : Min Video Bitrate - Required value : 600000 / Received value : 6000000 / 6000000

Our rules are :
<policy type="or" name="Bit Rate">
      <rule name="Min Video Bitrate Nominal" value="BitRate_Nominal" tracktype="Video" occurrence="0" operator=">=">600000</rule>
      <rule name="Min Video Bitrate" value="BitRate" tracktype="Video" occurrence="*" operator=">=">600000</rule>
    </policy>

Is there a way to test this field or is it possible to update mediaconch to go through this problem ?
Thanks in advance

@EtienneChampion


easier interop with floats

Can TryFrom be implemented as well as FromPrimitive? This would make it easier to make conversions using .try_nto().
I would further propose to allow performing arithmetic between rationals and floats although this would mean that From would make more sense than TryFrom and errors would panic instead of returning an error.

TryFrom seems fine. It will need to be tested for compiler support, but you can see how num-bigint did that.
I think arithmetic between rationals and floats is a lot more problematic, so I'd rather leave that to explicit conversions.

Ok I see seems like I should be able to basically do exactly the same using cfg attributes and just forward to the FromPrimitive methods. The Results Error type would be empty though as they only return an Option.

I added methods for converting from ints as well (some require try_from/ some can be done through from as they should never fail). In some generic code I'm currently using them as they make it a bit less noisy.
Maybe you can take a look and say if this is too much or seems appropriate?


keyboard needs to be closed when going back from some fragments

i.e when going to search fragment, the keyboard opens up, then when clicking the back button, the keyboard is still present when it should be closed.
Fragments to close keyboard when clicking back:

SearchFragment
AddHabitFragment

Finished as of #149


GetSceneAt(0) assumes default scene

Not sure if this is a bug at this point so starting as a feature request. The below code assumes the 0th scene is one active scene. Shouldnt this instead use SceneManager.GetActiveScene().name?
Now:
// Only change scene if the requested online scene is not blank, and is not already loaded
string loadedSceneName = SceneManager.GetSceneAt(0).name;
if (!string.IsNullOrEmpty(onlineScene) && onlineScene != loadedSceneName && onlineScene != offlineScene)
{
    ServerChangeScene(onlineScene);
}

Suggested:
// Only change scene if the requested online scene is not blank, and is not already loaded
string loadedSceneName = SceneManager.GetActiveScene().name;
if (!string.IsNullOrEmpty(onlineScene) && onlineScene != loadedSceneName && onlineScene != offlineScene)
{
    ServerChangeScene(onlineScene);
}

It would help if you told us where in the code you're referring to.

probably a bug yea. will take a look in a while

Found it in NetworkManager

@uweenukr please submit a pull request :)

Sorry I started by clicking the Git Blame to create an issue. Figured it would link to the file too. Silly github.

:tada: This issue has been resolved in version 1.5.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adding CI for check and fixing some dependencies issue Issue/21

Codecov Report

Merging #192 (83df072) into main (5594fef) will increase coverage by 0.01%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##             main     #192      +/-   ##
==========================================
+ Coverage   75.34%   75.35%   +0.01%
==========================================
  Files          68       68
  Lines        5629     5637       +8
==========================================
+ Hits         4241     4248       +7
- Misses       1388     1389       +1

Impacted Files
Coverage Δ

quickwit-directories/src/debug_proxy_directory.rs
79.54% <85.71%> (-0.30%)
:arrow_down:

quickwit-cluster/src/cluster.rs
48.03% <100.00%> (ø)

quickwit-search/src/collector.rs
71.72% <0.00%> (+0.68%)
:arrow_up:

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 5594fef...83df072. Read the comment docs.


Blurry on Safari

Sometimes the treesaver publication viewed on Safari browser gets very blurry.
Steps to reproduce:

Go to http://demo.nomadeditions.com/real-eats/ on Safari
Go to page that includes a lot of text (the problem is less visible on pages with pictures)
Change slowly the browser's window width

At some point the whole page gets blurry.
(just a speculation: perhaps somewhere in the code that calculates layout, x-offset is not rounded?)
Observed on Safari 5.1.1 on Windows Vista and on Ipad. On ipad it is more difficult to reproduce, since you cannot freely change browser window width.

Have not been able to replicate in current builds. Closing for now.